Comments (4)
Export and simulate are similar processes. In both cases, the commit hash would be an almost-sufficient way to make the state of the code reproducible. To be a complete solution, all repos that the model depends on would have to be committed at the moment of export. Otherwise the hashes would not reliably convey the exact state of the code.
To make simulations reproducible, the current solution is to save a snapshot of the models in the job dir. The user can choose (as a application-wide setting) whether to save just the model, or model + dependencies. The default is to save both. There is a function in the app to reconstruct the model from this snapshot as if it were a self-standing repo.
This approach is potentially expensive (though N2A models are notably concise compared to other formats). It may make sense to offer automatic-commit + hashes as an alternate way to reconstruct a model at a given point in time.
from n2a.
That makes sense to me. IMO almost-sufficient commit hashes may still be a useful supplement to snapshotting, e.g. to provide traceability back to the model repos (with appropriate caveats or "dirty" flags)
from n2a.
We could start by embedding the hashes as metadata in the snapshot file. As for exports, it would depend on the export format. We could dump a separate hash file. Basically, it would list each repo (just by name) and its associated hash.
from n2a.
That makes sense to me too, or perhaps a separate hash file named for each repo would make for extremely simple parsing. I rolled my own version of this in documentation as a stopgap for another app. Happy to change / replace that (probably a separate discussion).
from n2a.
Related Issues (20)
- UI: Restore focus to graph node that gets dragged
- UI: Undo inherit causes graph to shift unexpectedly
- UI: Visualize non-local connection bindings
- Backend: Explicit progress indicator
- UI: Select git revision and show differences
- UI: Equation tree should scroll to edit full height of field HOT 1
- UI: Highlight references to variable HOT 1
- UI: Allow multiple selection in equation tree
- Python: Create pybind11 wrapper for C
- Language: Allow keyword arguments in functions
- Use Maven build system HOT 1
- Git rebase during pull
- Reduce size of model snapshots HOT 1
- UI: a delete that merely releases override is effectively not undoable
- UI: ability to zoom the model graph HOT 1
- Add `numpy` dependency to setupy.py HOT 1
- Consider removing absolute paths from `model.sh` HOT 4
- Fail export when requested model isn't found HOT 2
- Export model params as JSON HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from n2a.