-
Notifications
You must be signed in to change notification settings - Fork 15
V2 clean state #64
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
base: v2
Are you sure you want to change the base?
V2 clean state #64
Conversation
Thanks Kris! I'll look into that later today or early next week. Could you please send me by email the latest version of your working notebook example? P.S. I changed the destination branch of this PR from |
Sorry, that's causing the conflicts of course. Github presented me with a PR proposal and I clicked on it... |
OK, I will clean up some stuff first. |
What is the name of the notebook I sent you earlier? |
I think it was Maybe we can iterate by mail on the notebook (and the required data) |
86135f1
to
df850d5
Compare
Clear state from possible previous run at beginning of ssp_run function.
c6e9218
to
b319216
Compare
Hi Kris, The most important thing is that the first option of Let me know if that's ok for you, so that I can merge this one. Thanks! |
Thanks for reopening this. I will inspect it next week. |
Claudio,
Here is a branch with a first version of a
ssp_clear_state
function.It resets some global variables caching information in different submodules. Optionally,
config.options
can be cleared andconfig
can be reset to the default values.More testing is still needed (involving multiple runs with different data/settings).
Can you have a look and improve it?