Aquileo | Recent changes to feature-requests

Aquileo | Raise warning when trying to convert non-kinetic SBML models to other ODE formats

2021-04-26T23:03:16.968000Z

For example, the conversion tool converts SBML-qual models to MATLAB and XPP files without any warning. While this conversion is possible, the conversion substantially distorts the meaning of the model. I think a warning would be helpful for people not familiar with these formats who may not be aware the SBML-qual files don't describe ODE simulations.

Aquileo | Expand Testing for SBML to/from BioPAX

2018-10-11T20:24:47.728000Z

The SBML to BioPAX and BioPAX to SBML converter test cases needs to be cleaned and improved. Currently, the test cases in these converteres are limited to testing roundtripping data to ensure data are not lost. However, more test cases must be applied to represent the core data that are being translated between the two standards.

Aquileo | Support SBML Group Annotation

2018-10-09T19:49:10.986000Z

The current BioPAX to SBML conversion does not convert duplicate BioPAX entities to it's equivalent SBML SBase object. The decision that was made in the GSoC 2016 project is to make use of the SBML Group Extension package to support these BioPAX information. This feature has yet to be supported in the converter.

Aquileo | Lost Stoichiometry in SBMLtoBioPAX

2018-10-09T18:30:33.227000Z

SBO terms found on SBML Reactions do not all map to the SBO terms that are supported in BioPAX. The discussion that came out of this problem for the GSoC 2016 program was to suggest to have BioPAX annotate the SBO terms that are unable to map from SBML to BioPAX. Currently, the SBML2BioPAX conversion will drop these SBO terms in SBML Reactions that do not directly map over to BioPAX.

Aquileo | Request MIRIAM Qualifiers for SBML Custom Annotations

2018-10-09T17:54:33.421000Z

In the SBML to BioPAX conversion, MIRIAM Qualifiers are used for SBML elements with CVTerms to annotate BioPAX information.
The MIRIAM qualifiers that are currently available to use are not capable of capturing all information needed for the conversion. Qualifier.BQB_UNKNOWN is currently used in the conversion as a temporary fix. It would be good to update this qualifier with the new terms that were requested for the GSoC 2016 project related to this conversion.

Aquileo | Custom Annotation in BioPAX to SBML

2018-10-09T15:46:25.630000Z

Not all BioPAX entity’ properties could directly map to an SBML element. We should considere using custom annotations to store information that cannot be mapped directly for both conversion. SBML has a variety of different ways to annotate external models and its property such as using CVTerm annotation using MIRIAM qualifiers or creating a customize annotation.

Aquileo | Converting SBML with Multiple Levels of Hierarchy

2018-10-09T15:43:46.798000Z

If an SBML file has more than 2 levels of hierarchy for nested submodules, the current SBML to BioPAX converter will flatten the first two layers of the SBML model the converter encounters and ignore the remaining nested models. It would be great if the conversion can perform flattening of all SBML nested models before conversion is performed from SBML to BioPAX.

Aquileo | Octave Module's Resulting Code Structure split

2017-04-19T10:04:37.172000Z

Hi,
I think that the Octave Code could be structured in a more useful way:
A function that calculates the reaction fluxes and collects them in the vector "Flux", given an arbitarray parametrisation, which is necessary for parameter estimation:
function Flux=ModelFlux(x,t,p)
A second function calculates the right hand side of the ODE, using those fluxes, and possibly additional parameters, if necessary:
function xdot=ModelRHS(Flux,p)
then define f and use it like this:

p=get_model_parameters();
x0=get_model_init();
f=@(x,t) ModelRHS(ModelFlux(x,t,p))
lsode(f,x0,t=linspace(0,T,n));
This will perhaps not be as fast as hard-coding everything but a lot more useful for optimisation purposes.

Analytically calculating the jacobian and parameter derivative would be a nice feature as well, as lsode runs better if you supply a jacobain function:

lsode({f,J},x0,t);

It's generally not great that the fluxes are never collected in a vector I think.
All the Best,
Andrei

Aquileo | being able to change the output extension

2014-11-24T15:32:01.569000Z

It would be convenient to allow the user to specify which extension he want the resulting file to be saved with.
Even, specifying where the output file should be saved and with which name would be good options.

Aquileo | octave variable names

2011-04-21T02:58:13Z

Dear Nico,
It would be great to have a list of names next to the state variables x. Mabe it could be next to the initialisation:

#Initial conditions vector
x0=zeros(19,1);
x0(1) = 0.0; # species id: blub name: bla
x0(2) = 0.0; # species id: blob name: bli
x0(3) = 0.0; # parameter id: truc name: troc

Also it would be great to include that at the start of the file as a comment.

all the best
lukas