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

[DEFECT] Optimizer does not correctly work with Initial Points #2412

Open
8 of 13 tasks
JunyungKim opened this issue Dec 24, 2024 · 0 comments
Open
8 of 13 tasks

[DEFECT] Optimizer does not correctly work with Initial Points #2412

JunyungKim opened this issue Dec 24, 2024 · 0 comments

Comments

@JunyungKim
Copy link
Collaborator

Thank you for the defect report

Defect Description

There are two issues regarding to initial points submission in RAVEN Optimizer (i.e., ravenframework/Optimizers/Optimizer.py)

  1. Even though users provide the initial points in the RAVEN input deck, RAVEN uses randomly generated values for variables, not the ones provided by users.
  2. There is no test file, testing whether simulations with initial points written in RAVEN input deck are well performed.

Steps to Reproduce

  1. copy one of the test files such as... \raven\tests\framework\Optimizers\GeneticAlgorithms\discrete\constrained\testGAMinwRepConstrained.xml
  2. Rename the copied file as "testGAMinwRepConstrainedwInitialPoints.xml."
  3. Add block. (Please see the figure below)
    image
  4. Run the file.

Expected Behavior

RAVEN needs to run simulations with given initial values of variables.

Screenshots and Input Files

image

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?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant