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-fit parameters from RasCAL-1 projects now have their constraints adjusted #314

Merged
merged 3 commits into from
Jan 14, 2025

Conversation

alexhroom
Copy link
Collaborator

Fixes #291. If a RasCAL-1 project has a non-fit parameter with min > value or max < value, as was allowed in RasCAL-1, this is adjusted and the user is warned.

@alexhroom alexhroom requested a review from DrPaulSharp January 14, 2025 11:03
Copy link
Collaborator

@DrPaulSharp DrPaulSharp left a comment

Choose a reason for hiding this comment

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

The function solving this problem is good, alongside the comment below, I think you'll need to apply this to the standard params block (i.e., problem.params), and the substrate roughness.

utilities/misc/r1ToProjectClass.m Outdated Show resolved Hide resolved
@alexhroom
Copy link
Collaborator Author

@DrPaulSharp it is applied to the standard params block (including substrate roughness) on line 37.

@alexhroom alexhroom merged commit 7d06bf4 into RascalSoftware:master Jan 14, 2025
5 checks passed
@alexhroom alexhroom deleted the 291-non-fit-parameters branch January 14, 2025 14:49
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.

Allow invalid non-fit parameters in RasCAL-1 conversion
2 participants