Submit LibSBMLsim 1.4.0

id: libsbmlsim version: 1.4.0 specificationsUrl: https://raw.githubusercontent.com/biosimulators/libsbmlsim/08e124afca6f1378faa27b4caaf8f89c24ffaa1d/biosimulators.json specificationsPatch: version: 1.4.0 image: url: ghcr.io/biosimulators/libsbmlsim/libsbmlsim:1.4.0 validateImage: true commitSimulator: true

Changelog

Granting permissions to biosimulators-daemon
Added test case for Fehlberg method

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!

The BioSimulators validator bot is validating the specifications of your simulator, validating your Docker image and committing your simulator to the BioSimulators registry.

We will discuss any concerns with your submission in this issue.

A complete log of your simulator submission job will be available here. The results of the validation of your tool will also be saved as a JSON file.A link to this file will be available from the "Artifacts" section at the bottom of this page.

- You (@biosimulators-daemon) do not have permissions to update the specifications of LibSBMLSim. Only the members of @biosimulators/libsbmlsim can update the specifications of LibSBMLSim. Please contact the members of this group to request permissions to update LibSBMLSim.

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!

The BioSimulators validator bot is validating the specifications of your simulator, validating your Docker image and committing your simulator to the BioSimulators registry.

We will discuss any concerns with your submission in this issue.

The specifications of your simulator is valid!

Summary of tests

Executed 66 test cases
Passed 7 test cases:
- cli.CliDescribesSupportedEnvironmentVariablesInline
- cli.CliDisplaysHelpInline
- cli.CliDisplaysVersionInformationInline
- docker_image.DeclaresSupportedEnvironmentVariables
- docker_image.DefaultUserIsRoot
- docker_image.HasBioContainersLabels
- docker_image.HasOciLabels
Failed 0 test cases
Skipped 59 test cases:
- combine_archive.CombineArchiveHasSedDocumentsInNestedDirectories
- combine_archive.CombineArchiveHasSedDocumentsWithSameNamesInDifferentInNestedDirectories
- combine_archive.WhenACombineArchiveHasAMasterFileSimulatorOnlyExecutesThisFile
- combine_archive.WhenACombineArchiveHasNoMasterFileSimulatorExecutesAllSedDocuments
- docker_image.SingularityImageExecutesSimulationsSuccessfully
- log.SimulatorReportsTheStatusOfTheExecutionOfCombineArchives
- log.SimulatorReportsTheStatusOfTheExecutionOfSedDocuments
- log.SimulatorReportsTheStatusOfTheExecutionOfSedOutputs
- log.SimulatorReportsTheStatusOfTheExecutionOfSedTasks
- published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ
- published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl
- published_project.SimulatorCanExecutePublishedProject:cellml/Lorenz-system
- published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-CVODE
- published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-Euler
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-continuous
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-continuous
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-NRM
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-SSA
- published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism
- published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling
- published_project.SimulatorCanExecutePublishedProject:smoldyn/Lotka-Volterra
- results_report.SimulatorGeneratesReportsOfSimulationResults
- sedml.SimulatorCanResolveModelSourcesDefinedByUriFragments
- sedml.SimulatorCanResolveModelSourcesDefinedByUriFragmentsAndInheritChanges
- sedml.SimulatorProducesLinear2DPlots
- sedml.SimulatorProducesLinear3DPlots
- sedml.SimulatorProducesLogarithmic2DPlots
- sedml.SimulatorProducesLogarithmic3DPlots
- sedml.SimulatorProducesMultiplePlots
- sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions
- sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges
- sedml.SimulatorSupportsAlgorithmParameters
- sedml.SimulatorSupportsComputeModelChanges
- sedml.SimulatorSupportsDataGeneratorsWithDifferentShapes
- sedml.SimulatorSupportsDataSetsWithDifferentShapes
- sedml.SimulatorSupportsModelAttributeChanges
- sedml.SimulatorSupportsModelsSimulationsTasksDataGeneratorsAndReports
- sedml.SimulatorSupportsMultipleReportsPerSedDocument
- sedml.SimulatorSupportsMultipleTasksPerSedDocument
- sedml.SimulatorSupportsRepeatedTasksWithChanges
- sedml.SimulatorSupportsRepeatedTasksWithFunctionalRangeVariables
- sedml.SimulatorSupportsRepeatedTasksWithFunctionalRanges
- sedml.SimulatorSupportsRepeatedTasksWithLinearUniformRanges
- sedml.SimulatorSupportsRepeatedTasksWithLogarithmicUniformRanges
- sedml.SimulatorSupportsRepeatedTasksWithMultipleSubTasks
- sedml.SimulatorSupportsRepeatedTasksWithNestedFunctionalRanges
- sedml.SimulatorSupportsRepeatedTasksWithNestedRepeatedTasks
- sedml.SimulatorSupportsRepeatedTasksWithSubTasksOfMixedTypes
- sedml.SimulatorSupportsRepeatedTasksWithVectorRanges
- sedml.SimulatorSupportsSubstitutingAlgorithms
- sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes
- sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroOutputStartTimes

Warnings

`cli.CliDescribesSupportedEnvironmentVariablesInline` (5.7 s)

Test that the inline help for a command-line interface describes the environment variables that the simulator supports.

Warnings:

  The inline help for a command-line interface for a simulation tool should describe the environment variables that the simulation tool supports.

  The command-line interface does not describe the following standard environment variables recognized by BioSimulators:
    - 'ALGORITHM_SUBSTITUTION_POLICY'

  If the simulation tool implements these variables, they should be described in the inline help for its command-line interface.

  Note, support for these environment variables is optional. Simulation tools are not required to support these variables.

Log:

`docker_image.HasBioContainersLabels` (0.5 s)

Test that a Docker image has BioContainers labels with metadata about the image

Warnings:

  The Docker image should have the following BioContainers labels:
    extra.identifiers.biotools

Log:

Skips

`combine_archive.CombineArchiveHasSedDocumentsInNestedDirectories` (0.0 s)

Test that SED documents in nested directories can be executed

Reason for skip:

  No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

`combine_archive.CombineArchiveHasSedDocumentsWithSameNamesInDifferentInNestedDirectories` (0.0 s)

Test that SED documents with the same names in nested directories can be executed and their outputs are saved to distinct paths

Reason for skip:

  No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

`combine_archive.WhenACombineArchiveHasAMasterFileSimulatorOnlyExecutesThisFile` (0.0 s)

Test that when a COMBINE/OMEX archive defines a (single) master file, the simulator only executes this file.

Reason for skip:

  No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

`combine_archive.WhenACombineArchiveHasNoMasterFileSimulatorExecutesAllSedDocuments` (0.0 s)

Test that when a COMBINE/OMEX archive does not have a defined master file, the simulator executes all SED-ML files.

Reason for skip:

  No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

`docker_image.SingularityImageExecutesSimulationsSuccessfully` (0.0 s)

Test that the Singularity version of a Docker image can sucessfully execute COMBINE archives

Reason for skip:

  No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

`log.SimulatorReportsTheStatusOfTheExecutionOfCombineArchives` (0.0 s)

Test that simulator logs the execution of COMBINE/OMEX archives

Reason for skip:

  No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

`log.SimulatorReportsTheStatusOfTheExecutionOfSedDocuments` (0.0 s)

Test that simulator logs the execution of individual SED document in COMBINE/OMEX archives

Reason for skip:

  No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

`log.SimulatorReportsTheStatusOfTheExecutionOfSedOutputs` (0.0 s)

Test that simulator logs the execution of individual SED outputs in COMBINE/OMEX archives

Reason for skip:

  No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

`log.SimulatorReportsTheStatusOfTheExecutionOfSedTasks` (0.0 s)

Test that simulator logs the execution of individual SED tasks in COMBINE/OMEX archives

Reason for skip:

  No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

`published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ` (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_3972 Algorithm: KISAO_0000263

Reason for skip:
```
Case requires model formats format_3972 and simulation algorithms KISAO_0000263
```
Log:
published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_3972 Algorithm: KISAO_0000019

Reason for skip:
```
Case requires model formats format_3972 and simulation algorithms KISAO_0000019
```
Log:
published_project.SimulatorCanExecutePublishedProject:cellml/Lorenz-system (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_3240 Algorithm: KISAO_0000019

Reason for skip:
```
Case requires model formats format_3240 and simulation algorithms KISAO_0000019
```
Log:
published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-CVODE (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_9004 Algorithm: KISAO_0000019

Reason for skip:
```
Case requires model formats format_9004 and simulation algorithms KISAO_0000019
```
Log:
published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-Euler (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_9004 Algorithm: KISAO_0000030

Reason for skip:
```
Case requires model formats format_9004 and simulation algorithms KISAO_0000030
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000019

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000019
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-continuous (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000019

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000019
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000088

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000088
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_000019

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_000019
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000496

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000496
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000560

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000560
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000560

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000560
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000019
Format: format_2585 Algorithm: KISAO_0000027
Format: format_2585 Algorithm: KISAO_0000030

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000019, KISAO_0000027, KISAO_0000030
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-continuous (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000019
Format: format_2585 Algorithm: KISAO_0000030

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000019, KISAO_0000030
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-NRM (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000027

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000027
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-SSA (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000029

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000029
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000437

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000437
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000449

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000449
```
Log:
published_project.SimulatorCanExecutePublishedProject:smoldyn/Lotka-Volterra (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_9001 Algorithm: KISAO_0000057

Reason for skip:
```
Case requires model formats format_9001 and simulation algorithms KISAO_0000057
```
Log:
results_report.SimulatorGeneratesReportsOfSimulationResults (0.0 s)

Test that when a COMBINE/OMEX archive defines a (single) master file, the simulator only executes this file.

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragments (0.0 s)

Test that a simulator can resolve model sources defined by URI fragments (e.g., #model1).

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragmentsAndInheritChanges (0.0 s)

Test that a simulator can resolve model sources defined by URI fragments (e.g., #model1) and inherit the changes of the model.

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorProducesLinear2DPlots (0.0 s)

Test that a simulator produces linear 2D plots

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorProducesLinear3DPlots (0.0 s)

Test that a simulator produces linear 3D plots

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorProducesLogarithmic2DPlots (0.0 s)

Test that a simulator produces logarithmic 2D plots

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorProducesLogarithmic3DPlots (0.0 s)

Test that a simulator produces logarithmic 3D plots

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorProducesMultiplePlots (0.0 s)

Test that a simulator produces multiple plots

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions (0.0 s)

Test that that the curated number of output dimensions matches the actual number of output dimensions

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges (0.0 s)

Test that a simulator supports model changes that involve adding, replacing, and removing model elements.

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsAlgorithmParameters (0.0 s)

Test that a simulator supports setting the values of parameters of algorithms

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsComputeModelChanges (0.0 s)

Test that a simulator supports compute model changes

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsDataGeneratorsWithDifferentShapes (0.0 s)

Test that a simulator supports data generators with different shapes

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsDataSetsWithDifferentShapes (0.0 s)

Test that a simulator supports data generators with different shapes

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsModelAttributeChanges (0.0 s)

Test that a simulator supports changes to the attributes of model elements

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsModelsSimulationsTasksDataGeneratorsAndReports (0.0 s)

Test that a simulator supports the core elements of SED: models, simulations, tasks, data generators for individual variables, and reports

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsMultipleReportsPerSedDocument (0.0 s)

Test that a simulator supports multiple reports per SED document

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsMultipleTasksPerSedDocument (0.0 s)

Test that a simulator supports multiple tasks per SED document

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsRepeatedTasksWithChanges (0.0 s)

Test that a simulator supports repeated tasks with multiple subtasks

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRangeVariables (0.0 s)

Test that a simulator supports repeated tasks over nested functional ranges based on model (specification) variables

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRanges (0.0 s)

Test that a simulator supports repeated tasks over functional ranges

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsRepeatedTasksWithLinearUniformRanges (0.0 s)

Test that a simulator supports repeated tasks over uniform ranges

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsRepeatedTasksWithLogarithmicUniformRanges (0.0 s)

Test that a simulator supports repeated tasks over uniform ranges

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsRepeatedTasksWithMultipleSubTasks (0.0 s)

Test that a simulator supports repeated tasks with multiple subtasks

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsRepeatedTasksWithNestedFunctionalRanges (0.0 s)

Test that a simulator supports repeated tasks over nested functional ranges based on model (specification) variables

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsRepeatedTasksWithNestedRepeatedTasks (0.0 s)

Test that a simulator supports nested repeated tasks

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsRepeatedTasksWithSubTasksOfMixedTypes (0.0 s)

Test that a simulator supports repeated tasks whose sub-tasks have mixed types. Also tests that sub-types executed in order of the values of their order attributes and that reports of the results of repeated tasks handle sub-tasks to produce results of different shapes.

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsRepeatedTasksWithVectorRanges (0.0 s)

Test that a simulator supports repeated tasks over vector ranges

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsSubstitutingAlgorithms (0.0 s)

Check that a simulator can substitute algorithms that it doesn't implement with similar algorithms when the algorithm substitution policy is less restrictive than :obj:AlgorithmSubstitutionPolicy.SAME_METHOD. Also check that a simulator ignores unsupported algorithm parameters when the algorithm substitution policy is less restrictive than :obj:AlgorithmSubstitutionPolicy.NONE.

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes (0.0 s)

Test that a simulator supports multiple time courses with non-zero initial times

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroOutputStartTimes (0.0 s)

Test that a simulator supports time courses with non-zero output start times

Reason for skip:
```
No curated COMBINE/OMEX archives are available to generate archives for testing
```
Log:

No test cases are applicable to your simulator. Please use this issue to share appropriate test COMBINE/OMEX files. The BioSimulators Team will add these files to this validation program and then re-review your simulator.

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!

The BioSimulators validator bot is validating the specifications of your simulator, validating your Docker image and committing your simulator to the BioSimulators registry.

We will discuss any concerns with your submission in this issue.

The specifications of your simulator is valid!

Summary of tests

Executed 67 test cases
Passed 44 test cases:
- cli.CliDescribesSupportedEnvironmentVariablesInline
- cli.CliDisplaysHelpInline
- cli.CliDisplaysVersionInformationInline
- combine_archive.CombineArchiveHasSedDocumentsInNestedDirectories
- combine_archive.CombineArchiveHasSedDocumentsWithSameNamesInDifferentInNestedDirectories
- combine_archive.WhenACombineArchiveHasAMasterFileSimulatorOnlyExecutesThisFile
- combine_archive.WhenACombineArchiveHasNoMasterFileSimulatorExecutesAllSedDocuments
- docker_image.DeclaresSupportedEnvironmentVariables
- docker_image.DefaultUserIsRoot
- docker_image.HasBioContainersLabels
- docker_image.HasOciLabels
- docker_image.SingularityImageExecutesSimulationsSuccessfully
- log.SimulatorReportsTheStatusOfTheExecutionOfCombineArchives
- log.SimulatorReportsTheStatusOfTheExecutionOfSedDocuments
- log.SimulatorReportsTheStatusOfTheExecutionOfSedOutputs
- log.SimulatorReportsTheStatusOfTheExecutionOfSedTasks
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-Fehlberg
- results_report.SimulatorGeneratesReportsOfSimulationResults
- sedml.SimulatorCanResolveModelSourcesDefinedByUriFragments
- sedml.SimulatorCanResolveModelSourcesDefinedByUriFragmentsAndInheritChanges
- sedml.SimulatorProducesLinear2DPlots
- sedml.SimulatorProducesLogarithmic2DPlots
- sedml.SimulatorProducesMultiplePlots
- sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions
- sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges
- sedml.SimulatorSupportsComputeModelChanges
- sedml.SimulatorSupportsDataGeneratorsWithDifferentShapes
- sedml.SimulatorSupportsDataSetsWithDifferentShapes
- sedml.SimulatorSupportsModelAttributeChanges
- sedml.SimulatorSupportsModelsSimulationsTasksDataGeneratorsAndReports
- sedml.SimulatorSupportsMultipleReportsPerSedDocument
- sedml.SimulatorSupportsMultipleTasksPerSedDocument
- sedml.SimulatorSupportsRepeatedTasksWithChanges
- sedml.SimulatorSupportsRepeatedTasksWithFunctionalRangeVariables
- sedml.SimulatorSupportsRepeatedTasksWithFunctionalRanges
- sedml.SimulatorSupportsRepeatedTasksWithLinearUniformRanges
- sedml.SimulatorSupportsRepeatedTasksWithLogarithmicUniformRanges
- sedml.SimulatorSupportsRepeatedTasksWithMultipleSubTasks
- sedml.SimulatorSupportsRepeatedTasksWithNestedFunctionalRanges
- sedml.SimulatorSupportsRepeatedTasksWithNestedRepeatedTasks
- sedml.SimulatorSupportsRepeatedTasksWithSubTasksOfMixedTypes
- sedml.SimulatorSupportsRepeatedTasksWithVectorRanges
- sedml.SimulatorSupportsSubstitutingAlgorithms
- sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroOutputStartTimes
Failed 0 test cases
Skipped 23 test cases:
- published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ
- published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl
- published_project.SimulatorCanExecutePublishedProject:cellml/Lorenz-system
- published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-CVODE
- published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-Euler
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-continuous
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-continuous
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-NRM
- published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-SSA
- published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism
- published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling
- published_project.SimulatorCanExecutePublishedProject:smoldyn/Lotka-Volterra
- sedml.SimulatorProducesLinear3DPlots
- sedml.SimulatorProducesLogarithmic3DPlots
- sedml.SimulatorSupportsAlgorithmParameters
- sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes

Warnings

`cli.CliDescribesSupportedEnvironmentVariablesInline` (3.5 s)

Test that the inline help for a command-line interface describes the environment variables that the simulator supports.

Warnings:

  The inline help for a command-line interface for a simulation tool should describe the environment variables that the simulation tool supports.

  The command-line interface does not describe the following standard environment variables recognized by BioSimulators:
    - 'ALGORITHM_SUBSTITUTION_POLICY'

  If the simulation tool implements these variables, they should be described in the inline help for its command-line interface.

  Note, support for these environment variables is optional. Simulation tools are not required to support these variables.

Log:

`docker_image.HasBioContainersLabels` (0.6 s)

Test that a Docker image has BioContainers labels with metadata about the image

Warnings:

  The Docker image should have the following BioContainers labels:
    extra.identifiers.biotools

Log:

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-Fehlberg` (9.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585 Algorithm: KISAO_0000086

Warnings:

Unexpected reports were produced:
simulation_1.sedml/Figure_3a
simulation_1.sedml/Figure_3b
simulation_1.sedml/Figure_3c
simulation_1.sedml/Figure_3d

Plots were not produced:
simulation.sedml/Figure_3a
simulation.sedml/Figure_3b
simulation.sedml/Figure_3c
simulation.sedml/Figure_3d

Extra plots were produced:
simulation_1.sedml/Figure_3a
simulation_1.sedml/Figure_3b
simulation_1.sedml/Figure_3c
simulation_1.sedml/Figure_3d

Log:


/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: [33mThe SED document is potentially incorrect.

- Model `Ciliberto2003_Morphogenesis` may be invalid.

  - The model file `BIOMD0000000297_url.xml` may be invalid.

    - The value of the 'sboTerm' attribute on a <species> is expected to be an SBO identifier (http://www.biomodels.net/SBO/). In SBML Level 2 prior to Version 4 it is expected to refer to a participant physical type (i.e., terms derived from SBO:0000236, "participant physical type"); in Versions 4 and above it is expected to refer to a material entity (i.e., terms derived from SBO:0000240, "material entity").

      Reference: L2V4 Section 5

       SBO term 'SBO:0000014' on the <species> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <species> is expected to be an SBO identifier (http://www.biomodels.net/SBO/). In SBML Level 2 prior to Version 4 it is expected to refer to a participant physical type (i.e., terms derived from SBO:0000236, "participant physical type"); in Versions 4 and above it is expected to refer to a material entity (i.e., terms derived from SBO:0000240, "material entity").

      Reference: L2V4 Section 5

       SBO term 'SBO:0000236' on the <species> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <species> is expected to be an SBO identifier (http://www.biomodels.net/SBO/). In SBML Level 2 prior to Version 4 it is expected to refer to a participant physical type (i.e., terms derived from SBO:0000236, "participant physical type"); in Versions 4 and above it is expected to refer to a material entity (i.e., terms derived from SBO:0000240, "material entity").

      Reference: L2V4 Section 5

       SBO term 'SBO:0000236' on the <species> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000336' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000336' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'kswe_prime * Swe1 + kswe_doubleprime * Swe1M + kswe_tripleprime * PSwe1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'kmih_prime * Mih_ast + kmih_doubleprime * Mih' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'IEtot - IE' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'Cdh1tot - Cdh1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'Mih1tot - Mih1a' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'Mcmtot - Mcm' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'SBFtot - SBF' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdiss * Trim' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Trim * (kdsic_prime * Cln + kdsic_doubleprime * Clb + kdsic)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Trim * (kdclb_doubleprime * Cdh1 + kdclb_tripleprime * Cdc20a + kdclb_prime)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Trim * kswe' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kass * Sic * Clb' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'PTrim * kmih' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Clb * (kdclb_doubleprime * Cdh1 + kdclb_tripleprime * Cdc20a + kdclb_prime)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kswe * Clb' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'ksclb * mass * Jm * (eps + Mcm) / (mass + Jm)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kmih * PClb' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'SBF * (kisbf_prime + kisbf_doubleprime * Clb) / (jisbf + SBF)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'SBFin * (kasbf_prime * mass + kasbf_doubleprime * Cln) / (jasbf + SBFin)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'IE * kiie / (jiie + IE)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kaie * IEin * Clb / (jaie + IEin)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Cdc20a * kicdc20 / (jicdc20 + Cdc20a)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdcdc20 * Cdc20a' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kacdc20 * Cdc20 * IE / (jacdc20 + Cdc20)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Cdh1 * (kicdh * Clb + kicdh_prime * Cln) / (jicdh + Cdh1)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Cdh1in * (Kacdh_prime + Kacdh_doubleprime * Cdc20a) / (jacdh + Cdh1in)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'khsl1 * BUD * Swe1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'khsl1 * BUD * PSwe1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Viwee * Swe1 * Clb / (Jiwee + Swe1)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Viwee * Swe1M * Clb / (Jiwee + Swe1M)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdswe_prime * Swe1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'khsl1r * Swe1M' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'khsl1r * PSwe1M' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'PSwe1 * Vawee / (Jawee + PSwe1)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'PSwe1M * Vawee / (Jawee + PSwe1M)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'ksswe * SBF' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kssweC' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdswe_prime * PSwe1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdiss * PTrim' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'PTrim * (kdclb_doubleprime * Cdh1 + kdclb_tripleprime * Cdc20a + kdclb_prime)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'PTrim * (kdsic_prime * Cln + kdsic_doubleprime * Clb + kdsic)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kass * PClb * Sic' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Mih1a * Vimih / (jimih + Mih1a)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Vamih * Mih1 * Clb / (Jamih + Mih1)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Mcm * kimcm / (jimcm + Mcm)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Mcmin * Clb * kamcm / (jamcm + Mcmin)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdbud * BE' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'ksbud * Cln' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Sic * (kdsic_prime * Cln + kdsic_doubleprime * Clb + kdsic)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kssic' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdcln * Cln' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kscln * SBF' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdswe_prime * Swe1M' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdcdc20 * Cdc20' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kscdc20_prime + kscdc20_doubleprime * pow(Clb, 4) / (pow(jscdc20, 4) + pow(Clb, 4))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdswe_doubleprime * PSwe1M' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'PClb * (kdclb_doubleprime * Cdh1 + kdclb_tripleprime * Cdc20a + kdclb_prime)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'mu * mass' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <event> <trigger> expression 'gt(Clb, 0.2)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <eventAssignment> <math> expression '1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <event> <trigger> expression 'and(lt(Clb, 0.2), gt(flag, 0))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <eventAssignment> <math> expression '0' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <eventAssignment> <math> expression '0.5 * mass' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <event> <trigger> expression 'or(geq(Clb, 0.2), geq(BE, 0.6))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <eventAssignment> <math> expression '1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <event> <trigger> expression 'and(lt(Clb, 0.2), lt(BE, 0.6))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <eventAssignment> <math> expression '0' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kswe' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kswe_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kswe_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kswe_tripleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kmih' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kmih_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Mih_ast' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kmih_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Mih' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'IEin' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'IEtot' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Cdh1in' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Cdh1tot' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Mih1' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Mih1tot' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Mcmin' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Mcmtot' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'SBFin' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'SBFtot' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdiss' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdsic_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdsic_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdsic' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdclb_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdclb_tripleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdclb_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kass' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'ksclb' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Jm' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'eps' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kisbf_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kisbf_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jisbf' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kasbf_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kasbf_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jasbf' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kiie' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jiie' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kaie' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jaie' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kicdc20' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jicdc20' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdcdc20' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kacdc20' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jacdc20' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kicdh' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kicdh_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jicdh' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Kacdh_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Kacdh_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jacdh' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'khsl1' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'BUD' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Viwee' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Jiwee' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdswe_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'khsl1r' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Vawee' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Jawee' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'ksswe' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kssweC' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Vimih' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jimih' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Vamih' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Jamih' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kimcm' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jimcm' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kamcm' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jamcm' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdbud' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a < ...

Skips

`published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ` (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_3972 Algorithm: KISAO_0000263

Reason for skip:
```
Case requires model formats format_3972 and simulation algorithms KISAO_0000263
```
Log:
published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_3972 Algorithm: KISAO_0000019

Reason for skip:
```
Case requires model formats format_3972 and simulation algorithms KISAO_0000019
```
Log:
published_project.SimulatorCanExecutePublishedProject:cellml/Lorenz-system (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_3240 Algorithm: KISAO_0000019

Reason for skip:
```
Case requires model formats format_3240 and simulation algorithms KISAO_0000019
```
Log:
published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-CVODE (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_9004 Algorithm: KISAO_0000019

Reason for skip:
```
Case requires model formats format_9004 and simulation algorithms KISAO_0000019
```
Log:
published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-Euler (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_9004 Algorithm: KISAO_0000030

Reason for skip:
```
Case requires model formats format_9004 and simulation algorithms KISAO_0000030
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000019

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000019
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-continuous (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000019

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000019
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000088

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000088
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_000019

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_000019
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000496

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000496
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000560

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000560
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000560

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000560
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000019
Format: format_2585 Algorithm: KISAO_0000027
Format: format_2585 Algorithm: KISAO_0000030

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000019, KISAO_0000027, KISAO_0000030
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-continuous (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000019
Format: format_2585 Algorithm: KISAO_0000030

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000019, KISAO_0000030
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-NRM (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000027

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000027
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-SSA (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000029

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000029
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000437

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000437
```
Log:
published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling (0.0 s)

Required model formats and simulation algorithms for SED tasks:
Format: format_2585 Algorithm: KISAO_0000449

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000449
```
Log:
published_project.SimulatorCanExecutePublishedProject:smoldyn/Lotka-Volterra (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_9001 Algorithm: KISAO_0000057

Reason for skip:

Case requires model formats format_9001 and simulation algorithms KISAO_0000057

Log:

`sedml.SimulatorProducesLinear3DPlots` (0.1 s)

Test that a simulator produces linear 3D plots

Reason for skip:

No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

`sedml.SimulatorProducesLogarithmic3DPlots` (0.1 s)

Test that a simulator produces logarithmic 3D plots

Reason for skip:

No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

`sedml.SimulatorSupportsAlgorithmParameters` (0.1 s)

Test that a simulator supports setting the values of parameters of algorithms

Reason for skip:

No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

`sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes` (4.4 s)

Test that a simulator supports multiple time courses with non-zero initial times

Reason for skip:

The image 'ghcr.io/biosimulators/libsbmlsim/libsbmlsim:1.4.0' could not execute the archive:

Unknown error

Log:


/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: [33mThe SED document is potentially incorrect.

- Model `Ciliberto2003_Morphogenesis` may be invalid.

  - The model file `BIOMD0000000297_url.xml` may be invalid.

    - The value of the 'sboTerm' attribute on a <species> is expected to be an SBO identifier (http://www.biomodels.net/SBO/). In SBML Level 2 prior to Version 4 it is expected to refer to a participant physical type (i.e., terms derived from SBO:0000236, "participant physical type"); in Versions 4 and above it is expected to refer to a material entity (i.e., terms derived from SBO:0000240, "material entity").

      Reference: L2V4 Section 5

       SBO term 'SBO:0000014' on the <species> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <species> is expected to be an SBO identifier (http://www.biomodels.net/SBO/). In SBML Level 2 prior to Version 4 it is expected to refer to a participant physical type (i.e., terms derived from SBO:0000236, "participant physical type"); in Versions 4 and above it is expected to refer to a material entity (i.e., terms derived from SBO:0000240, "material entity").

      Reference: L2V4 Section 5

       SBO term 'SBO:0000236' on the <species> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <species> is expected to be an SBO identifier (http://www.biomodels.net/SBO/). In SBML Level 2 prior to Version 4 it is expected to refer to a participant physical type (i.e., terms derived from SBO:0000236, "participant physical type"); in Versions 4 and above it is expected to refer to a material entity (i.e., terms derived from SBO:0000240, "material entity").

      Reference: L2V4 Section 5

       SBO term 'SBO:0000236' on the <species> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000336' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000336' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - The value of the 'sboTerm' attribute on a <parameter> is expected to be an SBO identifier (http://www.biomodels.net/SBO/) referring to a quantitative parameter defined in SBO (i.e., terms derived from SBO:0000002, "quantitative systems description parameter"). 

      Reference: L2V4 Sections 4.9.5 and 5

       SBO term 'SBO:0000393' on the <parameter> is not in the appropriate branch.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'kswe_prime * Swe1 + kswe_doubleprime * Swe1M + kswe_tripleprime * PSwe1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'kmih_prime * Mih_ast + kmih_doubleprime * Mih' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'IEtot - IE' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'Cdh1tot - Cdh1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'Mih1tot - Mih1a' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'Mcmtot - Mcm' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <assignmentRule> <math> expression 'SBFtot - SBF' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdiss * Trim' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Trim * (kdsic_prime * Cln + kdsic_doubleprime * Clb + kdsic)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Trim * (kdclb_doubleprime * Cdh1 + kdclb_tripleprime * Cdc20a + kdclb_prime)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Trim * kswe' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kass * Sic * Clb' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'PTrim * kmih' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Clb * (kdclb_doubleprime * Cdh1 + kdclb_tripleprime * Cdc20a + kdclb_prime)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kswe * Clb' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'ksclb * mass * Jm * (eps + Mcm) / (mass + Jm)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kmih * PClb' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'SBF * (kisbf_prime + kisbf_doubleprime * Clb) / (jisbf + SBF)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'SBFin * (kasbf_prime * mass + kasbf_doubleprime * Cln) / (jasbf + SBFin)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'IE * kiie / (jiie + IE)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kaie * IEin * Clb / (jaie + IEin)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Cdc20a * kicdc20 / (jicdc20 + Cdc20a)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdcdc20 * Cdc20a' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kacdc20 * Cdc20 * IE / (jacdc20 + Cdc20)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Cdh1 * (kicdh * Clb + kicdh_prime * Cln) / (jicdh + Cdh1)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Cdh1in * (Kacdh_prime + Kacdh_doubleprime * Cdc20a) / (jacdh + Cdh1in)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'khsl1 * BUD * Swe1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'khsl1 * BUD * PSwe1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Viwee * Swe1 * Clb / (Jiwee + Swe1)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Viwee * Swe1M * Clb / (Jiwee + Swe1M)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdswe_prime * Swe1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'khsl1r * Swe1M' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'khsl1r * PSwe1M' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'PSwe1 * Vawee / (Jawee + PSwe1)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'PSwe1M * Vawee / (Jawee + PSwe1M)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'ksswe * SBF' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kssweC' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdswe_prime * PSwe1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdiss * PTrim' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'PTrim * (kdclb_doubleprime * Cdh1 + kdclb_tripleprime * Cdc20a + kdclb_prime)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'PTrim * (kdsic_prime * Cln + kdsic_doubleprime * Clb + kdsic)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kass * PClb * Sic' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Mih1a * Vimih / (jimih + Mih1a)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Vamih * Mih1 * Clb / (Jamih + Mih1)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Mcm * kimcm / (jimcm + Mcm)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Mcmin * Clb * kamcm / (jamcm + Mcmin)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdbud * BE' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'ksbud * Cln' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'Sic * (kdsic_prime * Cln + kdsic_doubleprime * Clb + kdsic)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kssic' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdcln * Cln' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kscln * SBF' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdswe_prime * Swe1M' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdcdc20 * Cdc20' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kscdc20_prime + kscdc20_doubleprime * pow(Clb, 4) / (pow(jscdc20, 4) + pow(Clb, 4))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'kdswe_doubleprime * PSwe1M' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'PClb * (kdclb_doubleprime * Cdh1 + kdclb_tripleprime * Cdc20a + kdclb_prime)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <kineticLaw> <math> expression 'mu * mass' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <event> <trigger> expression 'gt(Clb, 0.2)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <eventAssignment> <math> expression '1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <event> <trigger> expression 'and(lt(Clb, 0.2), gt(flag, 0))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <eventAssignment> <math> expression '0' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <eventAssignment> <math> expression '0.5 * mass' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <event> <trigger> expression 'or(geq(Clb, 0.2), geq(BE, 0.6))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <eventAssignment> <math> expression '1' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <event> <trigger> expression 'and(lt(Clb, 0.2), lt(BE, 0.6))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 

       The units of the <eventAssignment> <math> expression '0' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kswe' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kswe_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kswe_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kswe_tripleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kmih' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kmih_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Mih_ast' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kmih_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Mih' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'IEin' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'IEtot' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Cdh1in' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Cdh1tot' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Mih1' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Mih1tot' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Mcmin' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Mcmtot' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'SBFin' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'SBFtot' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdiss' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdsic_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdsic_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdsic' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdclb_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdclb_tripleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kdclb_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kass' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'ksclb' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'Jm' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'eps' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kisbf_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kisbf_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jisbf' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kasbf_prime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kasbf_doubleprime' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jasbf' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kiie' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jiie' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'kaie' does not have a 'units' attribute.

    - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.

       The <parameter> with the id 'jaie ...

The image for your simulator is valid!

Your submission was committed to the BioSimulators registry. Thank you!

Future submissions of subsequent versions of libsbmlsim to the BioSimulators registry will be automatically validated. These submissions will not require manual review by the BioSimulators Team.

biosimulators / Biosimulators