Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non linear softening #158

Merged
merged 1 commit into from
Jan 27, 2024
Merged

Non linear softening #158

merged 1 commit into from
Jan 27, 2024

Conversation

albert-de-montserrat
Copy link
Member

@albert-de-montserrat albert-de-montserrat commented Jan 26, 2024

Adds non linear softening from Thibault et al 21

@albert-de-montserrat albert-de-montserrat merged commit 595dd0f into main Jan 27, 2024
17 of 18 checks passed
@albert-de-montserrat albert-de-montserrat deleted the adm/nonlinsoft branch January 27, 2024 09:07
@boriskaus
Copy link
Member

why is this called NoLinearSoftening instead of NonlinearSoftening? Typo?

@@ -29,3 +30,22 @@ LinearSoftening(min_max_values::NTuple{2, T}, lo_hi::NTuple{2, T}) where T = Lin

return fma((one(T) - softening_var), softening.slope, softening.min_value)
end

## Non linear softening
# (Thibault et al 2021; https://agupubs.onlinelibrary.wiley.com/doi/pdfdirect/10.1029/2021GC009675)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duretz et al.

@@ -62,7 +62,8 @@ export param_info,
iselastic,
AbstractSoftening,
NoSoftening,
LinearSoftening
LinearSoftening,
NoLinearSoftening
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would be better to call it NonlinearSoftening

@albert-de-montserrat
Copy link
Member Author

why is this called NoLinearSoftening instead of NonlinearSoftening? Typo?

it is indeed a typo... i'm patching it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants