Skip to content
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

Add KISAO and TEDDY and COMBINE archive info #7

Open
matthiaskoenig opened this issue Jul 13, 2017 · 3 comments
Open

Add KISAO and TEDDY and COMBINE archive info #7

matthiaskoenig opened this issue Jul 13, 2017 · 3 comments

Comments

@matthiaskoenig
Copy link
Collaborator

Currently these concepts are not well documented/linked on the homepage.

@jonrkarr
Copy link
Collaborator

KiSAO is described in the specifications. I think this is sufficient explanation.

One thing that would be helpful is to indicate the simulation type(s) and algorithm(s) involved in each example archive. This is helpful for quickly finding examples that are relevant to a particular type of simulation.

Why does TEDDY need to be mentioned?

@nickerso
Copy link
Collaborator

The idea was to use TEDDY to describe expected behaviour from a given SED-ML; i.e., so that you can search for experiments that are expected to produce particular dynamic characteristics. I'm not sure if anyone or any tool is actually doing this yet. And probably better nowadays to look more at annotating simulation results archived in a database such as biosimulators?

@jonrkarr
Copy link
Collaborator

I agree annotation of simulation results is a big hole in SED-ML. Given that TEDDY or other possible resources aren't yet used, I don't think they need to be mentioned on the website at this point. They should be documented when there is a scheme for using them.

RunBioSimulations includes database of simulation results. As we fully migrate to HDF5, we will have the flexibility to store a variety of metadata. TEDDY could be used. Annotations could be embedded into HDF5 files or annotations could be kept in a separate file linked via metaids which are saved into HDF5 files. HDF5 isn't XML, but otherwise we could make this work fairly similarly to how OMEX meta works with SBML and CellML.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants