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
This means that an additional attribute will have to be created, to keep track of which simulations had which postprocessing, unless we just don't care. But for reproducibility it is adviseable...
The text was updated successfully, but these errors were encountered:
This doesn't look easy, "storeing which postprocessing has been performed" on data, this means - automatically - saving the postprocessing python code in files while postprocessing. As i think storeing code is the only option, instead of just saying "what i did" as small version-changes in code do also change reproducibility ... ?
hm, I don't think it is complicated at all. It was mainly a reminder for a
feature I did not have time to implement :-)
I defined a Process class, that keeps track of all post processing that is
performed. So I just need to map the sim ID's with the Processes that have
been applied to it. For now I only apply Processes when I add a simulation
to a Simdex. This issue is about applying processes afterwards to the
simdex. Should be no problem. :-)
This doesn't look easy, "storeing which postprocessing has been performed"
on data, this means - automatically - saving the postprocessing python code
in files while postprocessing. As i think storeing code is the only option,
instead of just saying "what i did" as small version-changes in code do
also change reproducibility ... ?
Reply to this email directly or view it on GitHub:
This means that an additional attribute will have to be created, to keep track of which simulations had which postprocessing, unless we just don't care. But for reproducibility it is adviseable...
The text was updated successfully, but these errors were encountered: