Forums

Hello Lucian,

On Fri, 25 Jun 2010 17:50:34 +0100
Lucian Smith <lpsmith@spod-central.org> wrote:

> I think we're saying the same thing? The firing of the X's in indeed
> undefined. Because they are undefined (but *some* order must be
> chosen) any of my four examples are possibilities. In fact, there
> are 20 possibilities, and all of them are legal (120, if you include
> the possible permutations of the X's). The simulator may choose any
> method it wants to choose between them--the specification leaves it
> undefined.

No we are not saying the same thing. It is not possible to mix
undefined and ordered. Undefined behavior as in L2V4 and L3 is not the
same as a random order. I may be the same order every time you simulate
or it may change from simulation to simulation, it may even lead to
stopping the simulation.

Again, we should avoid defining a resolution of a situation which
should be avoided to begin with. If someone decides that the order of
simultaneous events is important for the correct simulation of a model
than they need to define the priority of all events which may occur
simultaneously. If that is not done the outcome is undefined.

Thanks,
Stefan


--
Stefan Hoops, Ph.D.
Senior Project Associate
Virginia Bioinformatics Institute - 0477
Virginia Tech
Bioinformatics Facility II
Blacksburg, Va 24061, USA

Phone: (540) 231-1799
Fax: (540) 231-2606
Email: shoops@vbi.vt.edu
____________________________________________________________
To manage your sbml-discuss list subscription, visit
https://utils.its.caltech.edu/mailman/listinfo/sbml-discuss

For a web interface to the sbml-discuss mailing list, visit
http://sbml.org/Forums/

For questions or feedback about the sbml-discuss list,
contact sbml-team@caltech.edu