Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors parsing SBML Spatial using the experimental package #16

Open
danv61 opened this issue Apr 14, 2022 · 0 comments
Open

Errors parsing SBML Spatial using the experimental package #16

danv61 opened this issue Apr 14, 2022 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@danv61
Copy link
Contributor

danv61 commented Apr 14, 2022

The following models fail, with the message "... Failed to create file .....sedml
The real causes, reported by python, are as follows:

ValueError: The SED document is invalid.

  • Model without_PDE4A is invalid.
    • The model file biomodel_32579611_without_PDE4A.xml is invalid.

There are 3 categories of errors:

  - The arguments to the following MathML constructs must have a numeric type: <plus>, <minus>, <times>, <divide>, <power>, <root>, <abs>, <exp>, <ln>, <log>, <floor>, <ceiling>, <factorial>, <sin>, <cos>, <tan>, <sec>, <csc>, <cot>, <sinh>, <cosh>, <tanh>, <sech>, <csch>, <coth>, <arcsin>, <arccos>, <arctan>, <arcsec>, <arccsc>, <arccot>, <arcsinh>, <arccosh>, <arctanh>, <arcsech>, <arccsch>, <arccoth>. 
    Reference: L3V1 Section 3.4.9
     The formula '832.169866109964 * and(gt(y, 1), lt(y, 20.9))' in the math element of the <initialAssignment> uses an argument to a operator that expects a numeric value.

  - The MathML formulas in the following elements must yield numeric expressions: <math> in <kineticLaw>, <stoichiometryMath> in <speciesReference>, <math> in <initialAssignment>, <math> in <assignmentRule>, <math> in <rateRule>, <math> in <algebraicRule>, and <delay> in <event>, and <math> in <eventAssignment>. 
    Reference: L3V1 Sections 4.8, 4.9, 4.11 and 4.12
     The formula '832.169866109964 * and(gt(y, 1), lt(y, 20.9))' in the math element of the <initialAssignment> does not return a numeric result.

  - The value of the attribute 'spatial:coordinateBoundary' of a <boundaryCondition> object must be the identifier of an existing <boundary> object defined in the enclosing <model> object.
    Reference: L3V1 Spatial V1 Section
     A <boundaryCondition> has a value of 'Xmin' for its 'coordinateBoundary', but the <geometry> does not contain a <boundaryMax> or <boundaryMin> with that id.

biomodel_6436213
biomodel_12119723
biomodel_26454052
biomodel_27071354
biomodel_27072412
biomodel_27072419
biomodel_27072426
biomodel_28730491
biomodel_32579611
biomodel_36275161
biomodel_40883478
biomodel_50584157
biomodel_61340695
biomodel_74924130
biomodel_82065439
biomodel_82798486
biomodel_82799056
biomodel_82799247
biomodel_82799266
biomodel_84985561
biomodel_91986407
biomodel_92705462
biomodel_95674618
biomodel_95686613
biomodel_95693513
biomodel_95693624
biomodel_95706942
biomodel_95707047
biomodel_101963252
biomodel_102061382
biomodel_116704767
biomodel_116898182
biomodel_123269480
biomodel_123465498
biomodel_123465505
biomodel_124562627
biomodel_147699816
biomodel_156134818
biomodel_189321805
biomodel_200301683
biomodel_201022999
biomodel_203656156

@danv61 danv61 added the bug Something isn't working label Apr 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants