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

Create run settings #110

Merged
merged 5 commits into from
Nov 21, 2021
Merged

Create run settings #110

merged 5 commits into from
Nov 21, 2021

Conversation

Spartee
Copy link
Contributor

@Spartee Spartee commented Nov 9, 2021

Implementation of the Experiment.create_run_settings function which is the first step towards better portability of driver scripts between system types.

See issue #91 for more details.

Sam Partee added 3 commits November 8, 2021 13:13
Experiment.create_run_settings has been implmented
which is a factory method for creating run settings
types.

The run_command default is "auto" which attempts
to automatically detect the run_command on the system
to use.
this functionality may be reused in other places
within the library, so the create_run_settings
function was placed inside smartsim/settings
and is now called from the experiment

Local tests have been adapted
Copy link
Collaborator

@al-rigazzi al-rigazzi left a comment

Choose a reason for hiding this comment

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

I added just a small comment, otherwise looks good. We can unify LSF too, or do that in another PR, let me know what you think is better.

from .control import Controller, Manifest
from .entity import Ensemble, Model
from .error import SmartSimError
from .generation import Generator
from .utils import get_logger
from .utils.helpers import colorize, init_default
from .utils.helpers import colorize, init_default, is_valid_cmd
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is is_valid_cmd used? I don't see it in the code

Sam Partee added 2 commits November 19, 2021 14:23
The default to create_run_settings is "auto", but the
case when the user explicitly did not want a run command
was not covered.

Users can now request that a command be run without a run
command by specifying run_command=None in the
create_run_settings function.
@Spartee Spartee merged commit 0248ffe into CrayLabs:develop Nov 21, 2021
@Spartee Spartee deleted the create_run_settings branch November 21, 2021 20:58
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.

None yet

2 participants