Forums

F.A.Q. F.A.Q.    Register Register    Login Login    Home Home
Search Search
SBML Discussions » sbml-discuss » Dealing with large models
Show: Today's Posts  :: Message Navigator
Switch to threaded view of this topic Create a new topic Submit Reply
AuthorTopic
mvacher


Posts: 2
Registered:
April 2011
Dealing with large models 01 May '11 22:05 Go to next message

Hi All,

First of all, thank you for the effort put into the development of SBML.
I am new to the field and although I have been reading/learning a lot lately, I apologize if my question is trivial.

As part of a project, I 'd like to build genome-scale model.
At the moment, using the SBML api, I wrote a perl script that extracts data (metabolites, reactions, etc...) from a local mysql database to produce a SBML file. (I also tried SBML-shorthand and QT Antimony, but they were not as flexible as an in-house script in that case).
This works very well, the resulting file is a proper xml that can be imported in tools that support the SBML format whithout any problem.

-> The model I work on is quite large and I found pretty hard to analyze/visualize/modify. I was wondering if there was a way to break-up a model into small pieces :
- Reactions can be localized into compartments, which is great, but is it possible to group a set of reactions together (for example, reactions that belongs to a same pathway) to simplify a model ?
That would be very helpful to work on a piece of a model independently to identify potential problems or refine a pathway. It could also be used to improve the graphical representation of models (like the 'nested graph' in cytoscape for example).
I found some slides by L. Smith about 'sub-models' here : http://sbml.org/images/6/69/Smith_combine_HierarchicalModelComp_2010-10-09.pdf but I didn't find any example.
There is also a presentation here : http://sbml.org/images/6/64/20041015-raman-merging.pdf but I 'm not sure this has been implemented yet.

Thanks a lot for your help.

Regards

      
Lucian Smith


Posts: 187
Registered:
July 2008
Re: Dealing with large models 02 May '11 10:11 Go to previous messageGo to next message

* mvacher <michael.vacher@edu.uwa.au> [2011-05-02 07:05] writes:
>
> Hi All,
>
> First of all, thank you for the effort put into the development of SBML.
> I am new to the field and although I have been reading/learning a lot lately, I apologize if my question is trivial.
>
> As part of a project, I 'd like to build genome-scale model.
> At the moment, using the SBML api, I wrote a perl script that extracts data (metabolites, reactions, etc...) from a local mysql database to produce a SBML file. (I also tried SBML-shorthand and QT Antimony, but they were not as flexible as an in-house script in that case).
> This works very well, the resulting file is a proper xml that can be imported in tools that support the SBML format whithout any problem.
>
> -> The model I work on is quite large and I found pretty hard to analyze/visualize/modify. I was wondering if there was a way to break-up a model into small pieces :
> - Reactions can be localized into compartments, which is great, but is it possible to group a set of reactions together (for example, reactions that belongs to a same pathway) to simplify a model ?
> That would be very helpful to work on a piece of a model independently to identify potential problems or refine a pathway. It could also be used to improve the graphical representation of models (like the 'nested graph' in cytoscape for example).
> I found some slides by L. Smith about 'sub-models' here : http://sbml.org/images/6/69/Smith_combine_HierarchicalModelComp_2010-10-09.pdf but I didn't find any example.
> There is also a presentation here : http://sbml.org/images/6/64/20041015-raman-merging.pdf but I 'm not sure this has been implemented yet.

As you found, it sounds like the hierarchical composition package is
indeed what you want, which suffers from the very minor drawback of not
yet existing. But it's getting closer! At the latest meeting in New
York, we managed to achieve consensus on the remaining unresolved
questions, and I've now incorporated those changes into the existing
specification:

https://sbml.svn.sourceforge.net/svnroot/sbml/trunk/specifications/sbml-level-3/version-1/comp/Hierarchical%20Model%20Composition%20Proposal.pdf

Any comments you have on the proposal would be welcomed!

I'm now working on getting these changes into libSBML, and from there, to
tools that use hierarchy.

Which brings me to a stop-gap solution: my own 'Antimony' tool, at

http://antimony.sourceforge.net/

can be used at least to prototype your modular solution. As an example,
if you wanted to lump a reaction pathway in a submodule, you could do
something like:

model onepath(A, E)
A -> B;
B + P -> C;
C -> D;
D -> E + P;
end

model branches()
M1: onepath(A, E);
i1 -> A;
i2 -> A;
E -> o1;
E -> o2;
end

Today, this would be output as 'flattened' SBML with all the reactions in
one big model. But once I get the libSBML API up and running, the next
step is to get Antimony to output hierarchical SBML instead. And of
course, once there's a libSBML API, you would be able to create
hierarchical models yourself, as well, and could 'visualize' (in text)
these models in Antimony. I believe Chris Meyers is also planning to
implement hierarchy in his iBioSim--again, pending the 'comp' libSBML API.

-Lucian
____________________________________________________________
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

      
myers


Posts: 140
Location:
University of Utah
Registered:
May 2008
Re: Dealing with large models 02 May '11 10:34 Go to previous messageGo to next message

We do have hierarchy in iBioSim as Lucian points out, but just for genetic regulatory models at this time.

Chris

Sent from my iPhone

On May 2, 2011, at 11:11 AM, Lucian Smith <lpsmith@spod-central.org> wrote:

> * mvacher <michael.vacher@edu.uwa.au> [2011-05-02 07:05] writes:
>>
>> Hi All,
>>
>> First of all, thank you for the effort put into the development of SBML.
>> I am new to the field and although I have been reading/learning a lot lately, I apologize if my question is trivial.
>>
>> As part of a project, I 'd like to build genome-scale model.
>> At the moment, using the SBML api, I wrote a perl script that extracts data (metabolites, reactions, etc...) from a local mysql database to produce a SBML file. (I also tried SBML-shorthand and QT Antimony, but they were not as flexible as an in-house script in that case).
>> This works very well, the resulting file is a proper xml that can be imported in tools that support the SBML format whithout any problem.
>>
>> -> The model I work on is quite large and I found pretty hard to analyze/visualize/modify. I was wondering if there was a way to break-up a model into small pieces :
>> - Reactions can be localized into compartments, which is great, but is it possible to group a set of reactions together (for example, reactions that belongs to a same pathway) to simplify a model ?
>> That would be very helpful to work on a piece of a model independently to identify potential problems or refine a pathway. It could also be used to improve the graphical representation of models (like the 'nested graph' in cytoscape for example).
>> I found some slides by L. Smith about 'sub-models' here : http://sbml.org/images/6/69/Smith_combine_HierarchicalModelComp_2010-10-09.pdf but I didn't find any example.
>> There is also a presentation here : http://sbml.org/images/6/64/20041015-raman-merging.pdf but I 'm not sure this has been implemented yet.
>
> As you found, it sounds like the hierarchical composition package is
> indeed what you want, which suffers from the very minor drawback of not
> yet existing. But it's getting closer! At the latest meeting in New
> York, we managed to achieve consensus on the remaining unresolved
> questions, and I've now incorporated those changes into the existing
> specification:
>
> https://sbml.svn.sourceforge.net/svnroot/sbml/trunk/specifications/sbml-level-3/version-1/comp/Hierarchical%20Model%20Composition%20Proposal.pdf
>
> Any comments you have on the proposal would be welcomed!
>
> I'm now working on getting these changes into libSBML, and from there, to
> tools that use hierarchy.
>
> Which brings me to a stop-gap solution: my own 'Antimony' tool, at
>
> http://antimony.sourceforge.net/
>
> can be used at least to prototype your modular solution. As an example,
> if you wanted to lump a reaction pathway in a submodule, you could do
> something like:
>
> model onepath(A, E)
> A -> B;
> B + P -> C;
> C -> D;
> D -> E + P;
> end
>
> model branches()
> M1: onepath(A, E);
> i1 -> A;
> i2 -> A;
> E -> o1;
> E -> o2;
> end
>
> Today, this would be output as 'flattened' SBML with all the reactions in
> one big model. But once I get the libSBML API up and running, the next
> step is to get Antimony to output hierarchical SBML instead. And of
> course, once there's a libSBML API, you would be able to create
> hierarchical models yourself, as well, and could 'visualize' (in text)
> these models in Antimony. I believe Chris Meyers is also planning to
> implement hierarchy in his iBioSim--again, pending the 'comp' libSBML API.
>
> -Lucian
> ____________________________________________________________
> 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
____________________________________________________________
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

      
mvacher


Posts: 2
Registered:
April 2011
Re: Dealing with large models 02 May '11 19:21 Go to previous messageGo to next message

Thanks a lot for your replies.

I will read the new specifications carefully and follow the integration of this new feature closely. Hierarchical models would be a great improvement to the current release.

In the meantime, as suggested, I will try to work with Antimony to break-up the model in submodules.

Thank you for your help,

Michael

      
S. Soliman


Posts: 10
Location:
Paris, FRANCE
Registered:
November 2004
Re: Dealing with large models 03 May '11 02:08 Go to previous messageGo to next message

____________________________________________________________
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,
c

      
Mike Hucka


Posts: 967
Registered:
October 2003
Re: Dealing with large models 30 Aug '11 16:22 Go to previous message

Regarding the location of the proposal for the 'comp' package: the location of the PDF file has moved. It is *now*

https://sbml.svn.sourceforge.net/svnroot/sbml/trunk/specifications/sbml-level-3/version-1/comp/proposal/Hierarchical%20Model%20Composition%20Proposal.pdf

instead of the *previous*

https://sbml.svn.sourceforge.net/svnroot/sbml/trunk/specifications/sbml-level-3/version-1/comp/Hierarchical%20Model%20Composition%20Proposal.pdf

MH


On Mon, 2 May 2011 18:11:40 +0100, Lucian Smith wrote:
> * mvacher <michael.vacher@edu.uwa.au> [2011-05-02 07:05] writes:
>>
>> Hi All,
>>
>> First of all, thank you for the effort put into the development of SBML.
>> I am new to the field and although I have been reading/learning a
>> lot lately, I apologize if my question is trivial.
>>
>> As part of a project, I 'd like to build genome-scale model.
>> At the moment, using the SBML api, I wrote a perl script that
>> extracts data (metabolites, reactions, etc...) from a local mysql
>> database to produce a SBML file. (I also tried SBML-shorthand and QT
>> Antimony, but they were not as flexible as an in-house script in
>> that case).
>> This works very well, the resulting file is a proper xml that can be
>> imported in tools that support the SBML format whithout any problem.
>>
>> -> The model I work on is quite large and I found pretty hard to
>> analyze/visualize/modify. I was wondering if there was a way to
>> break-up a model into small pieces :
>> - Reactions can be localized into compartments, which is great, but
>> is it possible to group a set of reactions together (for example,
>> reactions that belongs to a same pathway) to simplify a model ?
>> That would be very helpful to work on a piece of a model
>> independently to identify potential problems or refine a pathway. It
>> could also be used to improve the graphical representation of models
>> (like the 'nested graph' in cytoscape for example).
>> I found some slides by L. Smith about 'sub-models' here :
>> http://sbml.org/images/6/69/Smith_combine_HierarchicalModelComp_2010-10-09.pdf
>> but I didn't find any example.
>> There is also a presentation here :
>> http://sbml.org/images/6/64/20041015-raman-merging.pdf but I 'm not
>> sure this has been implemented yet.
>
> As you found, it sounds like the hierarchical composition package is
> indeed what you want, which suffers from the very minor drawback of not
> yet existing. But it's getting closer! At the latest meeting in New
> York, we managed to achieve consensus on the remaining unresolved
> questions, and I've now incorporated those changes into the existing
> specification:
>
> https://sbml.svn.sourceforge.net/svnroot/sbml/trunk/specifications/sbml-level-3/version-1/comp/Hierarchical%20Model%20Composition%20Proposal.pdf
>
> Any comments you have on the proposal would be welcomed!
>
> I'm now working on getting these changes into libSBML, and from there, to
> tools that use hierarchy.
>
> Which brings me to a stop-gap solution: my own 'Antimony' tool, at
>
> http://antimony.sourceforge.net/
>
> can be used at least to prototype your modular solution. As an example,
> if you wanted to lump a reaction pathway in a submodule, you could do
> something like:
>
> model onepath(A, E)
> A -> B;
> B + P -> C;
> C -> D;
> D -> E + P;
> end
>
> model branches()
> M1: onepath(A, E);
> i1 -> A;
> i2 -> A;
> E -> o1;
> E -> o2;
> end
>
> Today, this would be output as 'flattened' SBML with all the reactions in
> one big model. But once I get the libSBML API up and running, the next
> step is to get Antimony to output hierarchical SBML instead. And of
> course, once there's a libSBML API, you would be able to create
> hierarchical models yourself, as well, and could 'visualize' (in text)
> these models in Antimony. I believe Chris Meyers is also planning to
> implement hierarchy in his iBioSim--again, pending the 'comp' libSBML API.
>
> -Lucian
> ____________________________________________________________
> 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
____________________________________________________________
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

      
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic:20th release of BioModels Database
Next Topic:Release of SBMLToolbox-4.0.1
Go to forum:
-=] Back to Top [=-

Powered by FUDforum. (Copyright Advanced Internet Designs Inc.)

Please use our issue tracking system for any questions or suggestions about this website.