Great. Thanks, Lucian and David. M
--------------------------------- Maxwell Neal Post-doctoral researcher University of Washington mn...@uw.edu (206) 543-8769 --------------------------------- On Oct 22, 2011, at 4:00 PM, cellml-discussion-requ...@cellml.org wrote: > Send cellml-discussion mailing list submissions to > cellml-discussion@cellml.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.cellml.org/mailman/listinfo/cellml-discussion > or, via email, send a message with subject or body 'help' to > cellml-discussion-requ...@cellml.org > > You can reach the person managing the list at > cellml-discussion-ow...@cellml.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cellml-discussion digest..." > > > Today's Topics: > > 1. Re: nested components in CellML (David Nickerson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 22 Oct 2011 14:30:37 +1300 > From: David Nickerson <david.nicker...@gmail.com> > Subject: Re: [cellml-discussion] nested components in CellML > To: CellML Discussion List <cellml-discussion@cellml.org> > Message-ID: > <CADizRjhqHMOpDDm=8xoZLAD=bcognsm0xdlfma6yeox20k-...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Sat, Oct 22, 2011 at 10:10 AM, Lucian Smith <lpsm...@spod-central.org> > wrote: >> * Maxwell Neal <mn...@u.washington.edu> [2011-10-21 22:03] writes: >>> Hi all, >>> >>> I was wondering - can CellML models have nested components? ?That is, are >>> there instances where some model component is a component in another model >>> component? >>> Thanks, >> >> Yes--this is covered by the concept of encapsulation. ?See >> http://www.cellml.org/getting-started/tutorials/tutorial/best_practice/#grouping >> for more detail, but basically you set up a whole tree of nested >> components, and this nesting determines the rules for how you can connect >> the variables in those components. >> >> Also, an imported component from another file that encapsulates other >> components brings those components (and corresponding connections) with >> it in the import. >> >> Is that a reasonable summary, list denizens? > > yep, I think that summarises it nicely. Importing along with > encapsulation allows the definition of models where some components > are components from another model. > > > Cheers, > Andre. > > > ------------------------------ > > _______________________________________________ > cellml-discussion mailing list > cellml-discussion@cellml.org > http://lists.cellml.org/mailman/listinfo/cellml-discussion > > > End of cellml-discussion Digest, Vol 87, Issue 9 > ************************************************ _______________________________________________ cellml-discussion mailing list cellml-discussion@cellml.org http://lists.cellml.org/mailman/listinfo/cellml-discussion
