simphony-osp
simphony-osp copied to clipboard
simphony
Compare a simulation wrapper against its schema before a run
In GitLab by @pablo-de-andres on Oct 31, 2019, 11:47
Most simulation engines have some minimum requirements in order to run. To avoid unnecessary errors, this should be checked before calling the run in an engine. For that, each wrapper will define a "schema" yml file named schema.<wrapper>.yml. See simlammps for an example
In GitLab by @pablo-de-andres on Oct 31, 2019, 11:48
changed title from C{-heck that the cuds in a simulation wrapper match the specific schema before the-} run to C{+ompare a simulation wrapper against its schema before a+} run
In GitLab by @urbanmatthias on Nov 19, 2019, 15:42
marked #148 as a duplicate of this issue
In GitLab by @urbanmatthias on Nov 21, 2019, 08:03
removed milestone
In GitLab by @yoavnash on Apr 24, 2020, 15:14
For a dataspace wrapper, a team leader might require additional checks to be performed when a team member pushes data (see more info here). Could this be supported as well?
In GitLab by @pablo-de-andres on Apr 24, 2020, 16:49
Currently there is nothing supported. So maybe @urbanmatthias could work on this soon.
And my idea was to check the data on every call to the session.run().
Which I guess could match with what you want but with a session.commit()?
In GitLab by @abahde on May 15, 2020, 10:02
Taking a look at #406 might help here.
The link to issue 300 is wrong (it does not refer to GitLab). I actually want to say that having a look at the utility function validate_tree_against_schema
The link to issue 300 is wrong (it does not refer to GitLab). I actually want to say that having a look at the utility function validate_tree_against_schema might help
