-
Notifications
You must be signed in to change notification settings - Fork 135
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] Genetic Algorithm doesn't recognize constants and functions #1665
Labels
Comments
wangcj05
assigned aalfonsi and unassigned PaulTalbot-INL, joshua-cogliati-inl, wangcj05 and mandd
Sep 28, 2021
wangcj05
pushed a commit
that referenced
this issue
Sep 28, 2021
* Closes #1665 * modified test to test the constants * fixed implicit constraints * fix undefined variable * fixed pb wg * fix validation * Removed commented line from GeneticAlgorithm.py * Added <revisions> block for modified test Co-authored-by: ANDREA ALFONSI <alfoa@ANDREAs-MacBook-Pro.local>
@wangcj05 is this okay? if so, can you send it? |
wangcj05
pushed a commit
that referenced
this issue
Oct 25, 2021
* Closes #1665 * removed clearRunDir Co-authored-by: ANDREA ALFONSI <alfoa@ANDREAs-MacBook-Pro.local>
wangcj05
pushed a commit
that referenced
this issue
Oct 29, 2021
* Closes #1493 * removed print statement * minor other fixes * restart civet * Fixed issue #1520. Closes #1520 * Closes #1521 * fix * Closes #1665 * Fixed GA failures in case of failures * Update plugin_handler.py * Update GradientDescent.py * Update GradientDescent.py * added failure * Update GeneticAlgorithm.py * Update MultiRun.py added explanation * Update failureOfRuns.xml * for test * making the failures random and adding the test to tests after regolding * reverted files * since the new ROM API, this pickled rom needed to be regenerated * it seems that some of the user guide inputs did not get updated after ROM api update * fixed Dataset Co-authored-by: alfoa <andrea.alfonsi@inl.gov> Co-authored-by: ANDREA ALFONSI <alfoa@ANDREAs-MacBook-Pro.local> Co-authored-by: Jimmy-INL <52417034+Jimmy-INL@users.noreply.github.com>
wangcj05
pushed a commit
that referenced
this issue
Nov 9, 2021
* added spearman * fixed conversion script with current new hdf5 (no message handler) * fix basic statistics * fix conversion * fix duplication * Closes #1665 * removed commented code * manual * removed added test from other branch * regolded since there were NaN in the gold file but now the NaN are filled with zeros * fix bstat for nan * added weighted spearman coefficients calculation * added explaination of NaN * updated test description * added test in the test matrix * commented out the HistorySet duplicated tackling * added reference and manual updates * added ref to theory manual * moving spearman outside...draft * fixed spearman addressing Congjian's commets * reduced test to only spearman * Update HistorySet.py * Update BasicStatistics.py Co-authored-by: mandd <diego.mandelli@inl.gov> Co-authored-by: ANDREA ALFONSI <alfoa@ANDREAs-MacBook-Pro.local> Co-authored-by: aalfonsi <andrea.alfonsi86@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Defect Description
Genetic Algorithm optimizer doesn't recognize constants or functions.
What did you expect to see happen?
Expected the optimizer node to pass constants via multirun that could be accessed by an external model.
What did you see instead?
External model doesn't receive constants and throws an error when trying to access the constants.
Do you have a suggested fix for the development team?
Have GA send constants like gradient descent
Describe how to Reproduce
Steps to reproduce the behavior:
Screenshots and Input Files
Please attach the input file(s) that generate this error. The simpler the input, the faster we can find the issue.
Added Constant:
Manipulated in external model:
Error:
Platform (please complete the following information):
For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.
For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.
The text was updated successfully, but these errors were encountered: