raven
raven copied to clipboard
[DEFECT] Gradient Descent - Central Difference does not check for explicit constraints
Thank you for the defect report
- [X] I am using the latest version of
RAVEN
. - [X] I have read the Wiki.
- [X] I have created a minimum, reproducible example that demonstrates the defect.
Defect Description
Gradient Descent - Central Difference does not check if evaluation points (points selected for a gradient evaluation) violate Explicit Constraints (functional).
Steps to Reproduce
Create a test case that violate the constraint (explicit) for gradient evaluations.
Expected Behavior
If a constraint (explicit) is violated in the input space, Central difference is able to "handle" it (or at least to try to do so till an error is raised)
Screenshots and Input Files
No response
OS
Linux
OS Version
No response
Dependency Manager
PIP
For Change Control Board: Issue Review
- [ ] Is it tagged with a type: defect or task?
- [ ] Is it tagged with a priority: critical, normal or minor?
- [ ] If it will impact requirements or requirements tests, is it tagged with requirements?
- [ ] If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
- [ ] Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)
For Change Control Board: Issue Closure
- [ ] If the issue is a defect, is the defect fixed?
- [ ] If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
- [ ] If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
- [ ] If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
- [ ] If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@PaulTalbot-INL @dylanjm This is another issue related to Gradient Descent, please try to resolve it.