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
Maybe it would be a good idea to remove the Constraint enum from the interface to make it easier to write constitutive models in other languages. If I wanted to write a model in Rust, I would probably implement the methods evaluate and history_dim and then write a wrapper
Maybe it would be a good idea to remove the
Constraint
enum from the interface to make it easier to write constitutive models in other languages. If I wanted to write a model in Rust, I would probably implement the methodsevaluate
andhistory_dim
and then write a wrapperWe should still keep the
stress_strain_dim
geometric_dim
andhistory_dim
methods, butconstraint
could just return a string.Example:
The advantage would be that with this change any constitutive model would only need to handle
np.ndarray
andstr
and maybedict
as complex data types.The text was updated successfully, but these errors were encountered: