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

Command history save and load #304

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

amnona
Copy link
Collaborator

@amnona amnona commented Jun 24, 2024

  • Add a command history file to the Experiment save and load, so user can view the commands used to reach the saved Experiment.
  • Add to changelog
  • Bump version

@amnona
Copy link
Collaborator Author

amnona commented Jul 4, 2024

@RNAer can you go over/merge?

@@ -345,6 +345,7 @@ def _read_metadata(ids, f, kwargs):

@ds.get_sectionsf('io.read')
def read(data_file, sample_metadata_file=None, feature_metadata_file=None,
call_history_file=None,
Copy link
Collaborator

Choose a reason for hiding this comment

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

why do we need it in read()? it seems a separate logic from read(). let's not make the already complicated function api even more complicated?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think important since otherwise you get partial/missing history
We can do that if call_history is True (which we set as default instead of None), can try to automatically load the call history based on the data_file filename (as created in the save() ) if it exists.
I am afraid if we do it a separate function, people will be lazy/not know about it and then they lose the history once they load a saved file and continue working

What to you think?

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.

2 participants