Convert output of INIT_CONDS parameter to list of trajectories
#87
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes the result of the
INIT_CONDS.get()method so that it always returns a list of a trajectories. Since this is usually then consumed byscheme.initial_conditions_from_trajectories, this approach will always give a workable result. This is an API break, but since the result on the typical consumer is to allow more input types, I'm not concerned with backward compatibility.The issue was that sometimes, if calling the
INIT_CONDSparameter multiple times (e.g.,SampleSetorTrajectoryobjects from different interface sets/interfaces), this would break the input ofscheme.initial_conditions_from_trajectories. While it might be good to also modify that function to allow multipleSampleSets and a mixture of types in the input list, it seemed easier to make that change in the CLI for now. Usually, a Python library-level user has more ability to fix up their input types, whereas a CLI user has no such ability.