Chronological Thread 

< Chronological >      < Thread >

---

Forgive me if I'm getting this wrong, but looking at today's meeting
minutes the topic which initiated this thread is a bit off target. All
the CellML models which read into JSim are simply curated versions
(mostly by Penny Noble) of published models. They should definitely not
be variants, given the way I (and others) have been using versions to
date. These versions of the models are all still intended to be accurate
representations of the original model we are just working our way toward
a version that will produce the simulation results as published in the
original papers. There is also the argument that in some cases Penny may
not have started from the version01 version of the model encoding from
the repository, so her curated version of the model shouldn't be assumed
to be a variant of an existing version of a CellML model.

If we are going to to say that improving the curation of an existing
version of a CellML encoded model results in a new variant of the model
rather than a new version, then we need to go back through the
repository and turn most of the version increments into variant increments.

Having said all that, as long as all the models are annotated
sufficiently and the model repository provides access to that annotation
then it shouldn't really make any difference whether its a version or a
variant increment - apart from a slightly longer URI if you append a
variant number to the model identifier. Although if it is the variant
being incremented then the version number shouldn't be incremented.


Andre.

Andrew Miller wrote:
> Tommy Yu wrote:
>> Hi Poul,
>>
>> The model variant is supported by the repository, but version number is
>> automatically incremented if the model with the same base name (as
>> according to naming convention) is found. However, the quirk is that
>> the uri is [name]_version#_variant#, giving the sense that version is
>> the 'parent' of a given variant. I was also under the impression that
>> there are going to be multiple versions of models, and then (according
>> to what was said in the meeting) variant is just variations in starting
>> conditions.
> Hi Tommy,
>
> Please see Matt's document at
> http://www.cellml.org/wiki/cellmlrepositories.pdf/download.
>
> A version fixes an error in the CellML coding of a paper, while a
> variant creates a new model which is a modification of the original and
> differs in content from the published paper. Adding initial conditions
> which were not in the original paper is therefore one way to create a
> new variant.
>
> Best regards,
> Andrew
>
> _______________________________________________
> cellml-discussion mailing list
> cellml-discussion at cellml.org
> http://www.cellml.org/mailman/listinfo/cellml-discussion

--
David Nickerson, PhD
Research Fellow
Division of Bioengineering
Faculty of Engineering
National University of Singapore
Email: david.nickerson at nus.edu.sg

---

• [cellml-discussion] Model Variant, Andrew Miller, 09/11/2006
  • [cellml-discussion] Model Variant, David Nickerson, 09/11/2006

---

Archive powered by MHonArc 2.6.18.