-
Notifications
You must be signed in to change notification settings - Fork 0
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
Variable Reuse via global var store #45
Comments
Shelve Probably does what we need. Some care will need to be taken to make sure everything is serializable but that's not a huge barrier. |
I suspect that global variable usage will be low risk in this app because people won't be using this with new variables to write new code. they'll just be hitting go and get things out of it. |
shelf (as a dictionary-like thing) looks better (less complicated?) than a db. |
I think the only variables that people may want to change will be plot formatting parameters; maybe those shouldn't be globalized? |
I was thinking more about how calculating metrics would be horribly inefficient to re-do for multiple calculations. So storing them in that shelf-like lookup table would help reduce redundancy internally, the users wouldn't interact with it at all. |
agree. the shelf dilly looks baller. |
Certainly metrics will use the same data/inference over and over again. The modular approach in PR #43 will mean that calculations are probably going to be replicated.
Should we implement some sort of global variable store (something akin to a light-weight sql db) to avoid repeat work?
The text was updated successfully, but these errors were encountered: