VisionEval/VisionEval-Dev

Need to Refactor framework management of Datastores to keep out of .GlobalEnv

Closed this issue · 2 comments

The current approach to managing model Datastores (either RD or H5) is extremely difficult to manage and relies on placing necessary functions and data structures in the global environment.

Design goal is to leave the global environment untouched when a model is run, and to be able to run models and reload their results without trampling on each other.

We need a proper dispatch pattern for the datastore access functions (which loads and accesses all model-specific elements in the CURRENT environment, not the GLOBAL environment). Running or otherwise accessing a model state (and through it everything else) should take place in an environment constructed for that purpose.

P{lease discuss in comments!

This issue should be fixed at the same time as #29

Done in VEModel, release beta-release-0.1