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
Adding a new material, bulk rheology, fault kinematic source time function, or fault friction model involves adding several files. We need to redesign the code so that it is much easier to create a new material, etc.
Desired Solution
The ideal solution would be a user supplies kernels (pointwise functions) with a minimal amount of other code along with a parameter file that describes the auxiliary fields, derived fields, solution fields, etc. We should have code that implements the rest of the necessary functionality.
Additional context
Faults add complications because we have components like an arbitrary number of earthquake sources or an arbitrary number of traction perturbations.
The text was updated successfully, but these errors were encountered:
A new "material" (governing equation) requires the following:
Solution fields
Name, description, discretization
Auxiliary fields
Name, description, discretization, how to compute from spatial database
Diagnostic fields (optional)
Name, description, discretization, kernels
Derived fields (optional)
Name, description, discretization, how to compute from auxiliary field and solution field
Kernels for computing residual
field, equation part, kernel
interface kernels
Kernels for computing Jacobian
field i, field j, equation part, kernel
interface kernels
Kernels for updating state variables
Kernels for computing derived fields
Kernels for computing diagnostic fields
Default solver parameters (serial and parallel)
Rather than description and discretization information for each category of fields, we can provide a combined pool of description and discretization information that is used within the implementation.
Description
Adding a new material, bulk rheology, fault kinematic source time function, or fault friction model involves adding several files. We need to redesign the code so that it is much easier to create a new material, etc.
Desired Solution
The ideal solution would be a user supplies kernels (pointwise functions) with a minimal amount of other code along with a parameter file that describes the auxiliary fields, derived fields, solution fields, etc. We should have code that implements the rest of the necessary functionality.
Additional context
Faults add complications because we have components like an arbitrary number of earthquake sources or an arbitrary number of traction perturbations.
The text was updated successfully, but these errors were encountered: