You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be nice for reproducibility to also keep track of the state of the code when an experiment is done. This could be done by one of the following:
Copying the active code and saving it
Doing an automatic git commit when an experiment is run
Just saving the current hash and leaving it up to the user to commit.
Option 2 looks most reasonable to me, but may pollute the commit history with a ton of tiny commits. Maybe a solution is to have Artemis keep a separate <current_branch>.experiments branch, so every time you run an experiment, Artemis:
stash current branch
checks out the <current_branch>.experiments branch
commits
checks out <current_branch>.
load the stashed state.
The text was updated successfully, but these errors were encountered:
It'd be nice for reproducibility to also keep track of the state of the code when an experiment is done. This could be done by one of the following:
Option 2 looks most reasonable to me, but may pollute the commit history with a ton of tiny commits. Maybe a solution is to have Artemis keep a separate
<current_branch>.experiments
branch, so every time you run an experiment, Artemis:<current_branch>.experiments
branch<current_branch>
.The text was updated successfully, but these errors were encountered: