-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add Xopt and Badger version into routine #101
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, can you add a small test to verify that the badger and xopt versions are properly added in when saving the routine from the routine page?
I'm reviewing this now, @wenatuhs can you add more details to the PR description? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, please add a description to the PR + the test I requested before and then we can accept
@@ -48,6 +48,10 @@ def test_routine_generation(qtbot): | |||
assert routine.vocs.objectives == {"f": "MINIMIZE"} | |||
assert routine.initial_points.empty | |||
|
|||
# test if badger and xopt version are embedded |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we make this test stronger by comparing it to the current version? (same goes for the tests in test_db)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ie. routine.badger_version == str(badger.__version__)
and similar for xopt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure! Unfortunately we cannot do the same for test_db
because we didn't add version numbers there -- there are corresponding fields but the value would be None
. We of course can add version numbers first in the test but then it doesn't make sense to verify the just-added version numbers
This PR contains the following changes:
open docs
button on env config panel to show the readme of the corresponding env