You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, the FastScape interface does it's own checkpointing and restarting. Its current implementation means that:
The FastScape and ASPECT restart files could be out of sync if a crash occurs after calling FastScape and before writing an ASPECT checkpoint.
fastscape.cc doesn't read in the restart files during its initialization, but during the first call to compute_velocity_constraints_on_boundary(). However, other plugins might want to query the interface for the value of checkpointed variables before that. For example, I'm setting compositional field boundary conditions based on FastScape info, and these constraints are computed before mesh deformation.
Checkpointing FastScape interface variables only works if 'Steps between checkpoint' are used instead of 'Time between checkpoint'.
The text was updated successfully, but these errors were encountered:
At the moment, the FastScape interface does it's own checkpointing and restarting. Its current implementation means that:
compute_velocity_constraints_on_boundary()
. However, other plugins might want to query the interface for the value of checkpointed variables before that. For example, I'm setting compositional field boundary conditions based on FastScape info, and these constraints are computed before mesh deformation.The text was updated successfully, but these errors were encountered: