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
Other way of skipping steps - this integer indicator may be very cumbersome in later stages. 2. Checking whether the code was changed.
Both things should be simple. My suggestion for now is:
We iterate over all checks and if all are passed we consider step to be passed. 2. As step is being run we save model's code to some hidden folder and calculate it's hash. When step is run the next time. We compare hashes. We show warning to the user that this step should be rerun.
If anyone solving this task will have better ideas please suggest them
Acceptance Criteria:
Checking progress within experiment is no longer done based on integer counter Some primitive method for checking whether code changed and experiment should be done is implemented
The text was updated successfully, but these errors were encountered:
2 Things were suggested:
2. Checking whether the code was changed.Both things should be simple. My suggestion for now is:
2. As step is being run we save model's code to some hidden folder and calculate it's hash. When step is run the next time. We compare hashes. We show warning to the user that this step should be rerun.If anyone solving this task will have better ideas please suggest them
Acceptance Criteria:
Some primitive method for checking whether code changed and experiment should be done is implementedThe text was updated successfully, but these errors were encountered: