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

Extend scenario metadata #2037

Merged
merged 18 commits into from
May 29, 2023
Merged

Extend scenario metadata #2037

merged 18 commits into from
May 29, 2023

Conversation

Gamenot
Copy link
Collaborator

@Gamenot Gamenot commented May 25, 2023

This PR adds additional information to the metadata. This allows for constrained and unconstrained arguments to be included in the metadata.

I am considering adding additional serialization support.

@Gamenot Gamenot force-pushed the tucker/extend_metadata branch from 01abb75 to b12916e Compare May 25, 2023 15:22
@Gamenot Gamenot force-pushed the tucker/extend_metadata branch from f1da575 to e15df7a Compare May 26, 2023 14:05
@dataclass(frozen=True)
class ScenarioMetadata:
"""Scenario data that does not have influence on simulation."""
"""Deprecated. Scenario data that does not have influence on simulation."""
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a reason we didn't just change this class? I like the original name better.

Copy link
Collaborator Author

@Gamenot Gamenot May 26, 2023

Choose a reason for hiding this comment

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

Right, I had changed this already by the time you commented. I forgot to push the updates here. I decided to just use the old name since the way the new class works still acts like the old one.

smarts/sstudio/types/scenario.py Outdated Show resolved Hide resolved
smarts/sstudio/types/scenario.py Outdated Show resolved Hide resolved
smarts/sstudio/types/scenario.py Outdated Show resolved Hide resolved
@Gamenot
Copy link
Collaborator Author

Gamenot commented May 26, 2023

Something odd is happening with the build/ now. I wonder if it has to do with using yaml instead of pickle.

edit: One of the scenario builds was failing and that resulted build/ not getting generated.

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.

3 participants