First login?
Lost password?
 
 
cellml-tools-developers AT lists.cellml.org 
A list for the developers of CellML tools

Text archives Help


[[cellml-dev] ] libCellML handling of non-valid CellML - discussion request


Chronological Thread 
  • From: Randall Britten <r.britten AT auckland.ac.nz>
  • To: "cellml-tools-developers AT cellml.org" <cellml-tools-developers AT cellml.org>
  • Subject: [[cellml-dev] ] libCellML handling of non-valid CellML - discussion request
  • Date: Thu, 15 Jan 2015 20:46:47 +0000
  • Accept-language: en-NZ, en-US
Hi all

Firstly, Happy New Year, hope you have a great 2015!

I had some conversations yesterday around the ABI about how libCellML should
handle non-valid CellML models. We are especially envisaging model-editing
software that uses libCellML, progressively building and modifying models,
meaning that as the model is worked on step-by-step, there will often be
steps that are part of a group of steps, and only once the group of steps is
complete is the model in a valid state. Another likely scenario is using
software that uses libCellML to load models that were created independently
of libCellML, and it would be necessary to handle the case where the loaded
model might be invalid (e.g. still under construction, or pa).

Within reason, we’d like libCellML to support the corresponding use cases,
although it might make sense to defer them till later.

An example that has arisen is how connections are represented. While the XML
has a “connection” element that is a child of the “model” element, the design
that I’ve followed so far aimed to hide that, treating it as an
implementation detail, so that variables would simply allow for a query
regarding which other variables they are connected to.

Some options considered so far:
1) Phantom Variables (and similarly for other situations, e.g. Phantom
Units), which serve as place-holders.
2) Reinstate “connection” class in the object model to handle the case where
the connection is not valid (e.g. refers to variables or components that
don’t exist in the model).
3) Defer consideration of partially defined and invalid models (80/20 rule).

Please provide feedback on this. I’ll be responding to feedback received
today and next week on the same day it is received (within reason).

Thanks in advance.

Regards,
Randall


Archive powered by MHonArc 2.6.18.

Top of page