First login?
Lost password?
 
 
cellml-discussion AT lists.cellml.org 
CellML Discussion List

Text archives Help


[cellml-discussion] Include_in_CellML_1.2 requested: [Tracker Item 153] Allow multiple connections between the same pair of components


Chronological Thread 
  • From: alan.garny at dpag.ox.ac.uk (Alan Garny)
  • Subject: [cellml-discussion] Include_in_CellML_1.2 requested: [Tracker Item 153] Allow multiple connections between the same pair of components
  • Date: Wed, 29 Aug 2007 01:37:53 +0100
Agreed, but we should then also delete (?) the second point of rule 3.4.5.4
(Proper use of the component_1 and component_2 attributes for the
<map_components> element).

Alan.

> -----Original Message-----
> From: cellml-discussion-bounces at cellml.org [mailto:cellml-discussion-
> bounces at cellml.org] On Behalf Of Andrew Miller
> Sent: 29 August 2007 01:13
> To: CellML Discussion List
> Subject: Re: [cellml-discussion] Include_in_CellML_1.2 requested: [Tracker
> Item 153] Allow multiple connections between the same pair of components
>
> Hi all,
>
> Are there any objections to marking this as something we should include
> in CellML 1.2?
>
> Best regards,
> Andrew
>
> cellml-tracker at cellml.org wrote:
> > Andrew Miller <ak.miller at auckland.ac.nz> has asked for
> Include_in_CellML_1.2:
> > Tracker Item 153: Allow multiple connections between the same pair of
> > components
> > http://bowmore.elyt.com/bugzilla/show_bug.cgi?id=153
> >
> > ------- Additional Comments from Andrew Miller
<ak.miller at auckland.ac.nz>
> > Section 3.2.4 of CellML 1.1 states, in the second sentence of the second
> > paragraph: "Only one connection may be created between any given pair of
> > components in a model".
> >
> > This is a fairly pointless restriction from all fronts:
> > * From a model authors perspective, it creates a burden on the author
to
> > consolidate all their connections which may have been created for
> different
> > purposes, and current model authors claim that such consolidation is
time
> > consuming and error prone.
> > * From a model readability perspective, it is also burdensome because
> > connections between variables may not be in a logical order (this is
less
> of an
> > issue if tools are used, but the point still holds).
> > * Implementation experience suggests that it is no harder to allow
> multiple
> > connections between the same pair of components when writing simulation
> > software, but the extra constraint imposes more work on developers when
> writing
> > tools which try to validate the model.
> >
> > To fix this, we could simply drop the first two sentences of the second
> > paragraph of Section 3.2.4, and perhaps replace them with a short
> explanation.
> > _______________________________________________
> > cellml-discussion mailing list
> > cellml-discussion at cellml.org
> > http://www.cellml.org/mailman/listinfo/cellml-discussion
> >
>
> _______________________________________________
> cellml-discussion mailing list
> cellml-discussion at cellml.org
> http://www.cellml.org/mailman/listinfo/cellml-discussion



Archive powered by MHonArc 2.6.18.

Top of page