Chronological Thread 

< Chronological >      < Thread >

---

Hi Alan,

My phrasing on my last post was rather clumsy. What I should have said
was something like:

All of these methods return all of the local components;
Model::localComponents returns nothing else, Model::allComponents
returns the local components plus the instantiated part of the import
hierarchy, and Model::modelComponents returns the local components
plus the components which are directly imported into the model.

Best Regards,
Justin.

Quoting Alan Garny <alan.garny at dpag.ox.ac.uk>:

> Maybe a dumb question, but why have modelComponents then, if it is
> the same as localComponents?
>
> On 29 Jul 2009, at 00:47, Justin Marsh <j.marsh at auckland.ac.nz> wrote:
>
>> Hi Lucian,
>>
>> Both methods return all local components; the difference is that
>> Model::allComponents returns the instantiated part of the import
>> hierarchy, wheras Model::modelComponents returns only the
>> components which are directly imported into the model.
>>
>> Best Regards,
>> Justin.
>>
>> Quoting Lucian Smith <lpsmith at spod-central.org>:
>>
>>> * Andrew Miller <ak.miller at auckland.ac.nz> [2009-07-28 02:27] writes:
>>>> Hi Lucian,
>>>>
>>>> I'm moving this to the cellml-tools-developers list; it is a good one
>>>> for questions relating to tools that process CellML as some people get
>>>> upset if there is too much software related discussion on
>>>> cellml-discussion.
>>>
>>> Sounds good! Moving further questions here...
>>>
>>>> We are a bit lacking on some aspects of documentation for API users, as
>>>> you have discovered. We have some information on the PCM - Physiome C++
>>>> Mapping in the docs subdirectory, but maybe not enough high-level
>>>> documentation to get people started. It is often difficult for people
>>>> already familiar with things to identify what new developers need to
>>>> know the most, and so if you have created any documentation / notes /
>>>> comments on what you discovered early on, it would be very useful to
>>>> other people starting out with the API (or at least to aid the process
>>>> of documentation), and so contributing it back would be useful. The
>>>> Physiome Tracker would be a good way to manage correspondence with
>>>> respect to documentation. See https://tracker.physiomeproject.org
>>>
>>> Sure, I'll keep notes as I go.
>>>
>>> My next question: I think I understand what Model::localComponents and
>>> Model::allComponents are, but where does Model::modelComponents fall on
>>> that scale?
>>>
>>> -Lucian
>>>
>>> ----- End forwarded message -----
>>> _______________________________________________
>>> cellml-tools-developers mailing list
>>> cellml-tools-developers at cellml.org
>>> http://www.cellml.org/mailman/listinfo/cellml-tools-developers
>>>
>>
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>> _______________________________________________
>> cellml-tools-developers mailing list
>> cellml-tools-developers at cellml.org
>> http://www.cellml.org/mailman/listinfo/cellml-tools-developers
> _______________________________________________
> cellml-tools-developers mailing list
> cellml-tools-developers at cellml.org
> http://www.cellml.org/mailman/listinfo/cellml-tools-developers
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

---

• [cellml-dev] The CellML library basics, Lucian Smith, 07/29/2009
  • [cellml-dev] The CellML library basics, Justin Marsh, 07/29/2009
    • [cellml-dev] The CellML library basics, Alan Garny, 07/29/2009
      • [cellml-dev] The CellML library basics, Justin Marsh, 07/30/2009
      • [cellml-dev] The CellML library basics, Jonathan Cooper, 07/30/2009

---

Archive powered by MHonArc 2.6.18.