Submit COPASI 4.33.246 - Githubissues

Warnings

`cli.CliDescribesSupportedEnvironmentVariablesInline` (3.1 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.3 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/Tomida-EMBO-J-2003-NFAT-translocation` (3.7 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585 Algorithm: KISAO_0000560

Warnings:

Unexpected reports were produced:
BIOMD0000000678_sim.sedml/Figure_3c

Plots were not produced:
simulation.sedml/Figure_3c

Extra plots were produced:
BIOMD0000000678_sim.sedml/Figure_3c

Log:

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

- Model `BIOMD0000000678` may be invalid.

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

    - 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 <initialAssignment> <math> expression 'stim_duration' 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 <initialAssignment> <math> expression 'stim_frequency' 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 '1 - NFAT_phosphorylated - NFAT_dephosphorylated' 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 '100 * NFAT_phosphorylated' 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 '100 * NFAT_transported' 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 '100 * NFAT_dephosphorylated' 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 'piecewise(1, lt(time - floor(time / ModelValue_13) * ModelValue_13, ModelValue_17), 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 <kineticLaw> <math> expression 'Jurkat_cell * function_for_modified_reaction_1(NFAT_phosphorylated, k1, stimulus)' 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 'Jurkat_cell * k2 * NFAT_dephosphorylated' 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 'Jurkat_cell * k3 * NFAT_dephosphorylated' 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 'Jurkat_cell * k4 * NFAT_transported' 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 'k1' 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 'k2' 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 'k3' 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 'k4' 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 'stim_frequency' 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 'dNFAT' 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 'pNFAT' 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 'tNFAT' 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 'stim_duration' 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 'ModelValue_17' 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 'ModelValue_13' does not have a 'units' attribute.

      [0m

warnings.warn(termcolor.colored(message, Colors.warning.value), category)

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: [33mThe COMBINE/OMEX archive may be invalid.

- The SED-ML file at location `./BIOMD0000000678_sim.sedml` may be invalid.

  - Model `BIOMD0000000678` may be invalid.

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

      - 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 <initialAssignment> <math> expression 'stim_duration' 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 <initialAssignment> <math> expression 'stim_frequency' 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 '1 - NFAT_phosphorylated - NFAT_dephosphorylated' 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 '100 * NFAT_phosphorylated' 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 '100 * NFAT_transported' 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 '100 * NFAT_dephosphorylated' 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 'piecewise(1, lt(time - floor(time / ModelValue_13) * ModelValue_13, ModelValue_17), 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 <kineticLaw> <math> expression 'Jurkat_cell * function_for_modified_reaction_1(NFAT_phosphorylated, k1, stimulus)' 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 'Jurkat_cell * k2 * NFAT_dephosphorylated' 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 'Jurkat_cell * k3 * NFAT_dephosphorylated' 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 'Jurkat_cell * k4 * NFAT_transported' 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 'k1' 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 'k2' 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 'k3' 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 'k4' 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 'stim_frequency' 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 'dNFAT' 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 'pNFAT' 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 'tNFAT' 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 'stim_duration' 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 'ModelValue_17' 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 'ModelValue_13' does not have a 'units' attribute.

        [0m

warnings.warn(termcolor.colored(message, Colors.warning.value), category)

Archive contains 1 SED-ML documents with 1 models, 1 simulations, 1 tasks, 1 reports, and 1 plots:

BIOMD0000000678_sim.sedml:

  Tasks (1):

    BIOMD0000000678_task

  Reports (1):

    report: 5 data sets

  Plots (1):

    Figure_3c: 2 curves

Executing SED-ML file 0: BIOMD0000000678_sim.sedml ...

Bundling outputs ...

Cleaning up ...

============= SUMMARY =============

Executed 1 SED documents:

SED documents (1):

  Succeeded: 1

  Skipped: 0

  Failed: 0

Tasks (1):

  Succeeded: 1

  Skipped: 0

  Failed: 0

Outputs (2):

  Succeeded: 2

  Skipped: 0

  Failed: 0

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML` (4.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585 Algorithm: KISAO_0000560

Warnings:

Unexpected reports were produced:
LSODA.sedml/Figure_2c

Log:


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

- Model `model` may be invalid.

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

    - 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 'compartment * Henri_Michaelis_Menten__irreversible(IR, Km1, V1)' 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 'compartment * Henri_Michaelis_Menten__irreversible(pIR, Km2, V2)' 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 'compartment * HMM_Mod(k3c, IRS, pIR, Km3)' 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 'compartment * Henri_Michaelis_Menten__irreversible(pIRS, Km4, V4)' 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 'compartment * Function_for_v5(k5ca, pIRS, Akt, Km5a, k5cb, pmTORC2, Km5b)' 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 'compartment * Henri_Michaelis_Menten__irreversible(pAkt, Km6, V6)' 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 'compartment * HMM_Mod(k7c, mTORC1, pAkt, Km7)' 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 'compartment * Henri_Michaelis_Menten__irreversible(pmTORC1, Km8, V8)' 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 'compartment * HMM_Mod(k9c, mTORC2, pIR, Km9)' 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 'compartment * Henri_Michaelis_Menten__irreversible(pmTORC2, Km10, V10)' 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 'compartment * Function_for_v11(k11ca, pmTORC1, DEPTOR, Km11a, pDEPTOR, k11cb, pmTORC2, Km11b)' 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 'compartment * Henri_Michaelis_Menten__irreversible(pDEPTOR, Km12, V12)' 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 'compartment * (k13f * mTORC1 * DEPTOR - k13r * mTORC1_DEPTOR)' 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 'compartment * (k14f * mTORC2 * DEPTOR - k14r * mTORC2_DEPTOR)' 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 'compartment * HMM_Mod(k15c, IRS, pmTORC1, Km15)' 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 'compartment * Henri_Michaelis_Menten__irreversible(iIRS, Km16, V16)' 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 'compartment * Constant_flux__irreversible(ks17)' 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 'compartment * kd18 * pDEPTOR' 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 'V1' 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 'Km1' 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 'V2' 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 'Km2' 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 'k3c' 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 'Km3' 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 'V4' 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 'Km4' 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 'k5ca' 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 'Km5a' 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 'k5cb' 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 'Km5b' 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 'V6' 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 'Km6' 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 'k7c' 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 'Km7' 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 'V8' 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 'Km8' 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 'k9c' 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 'Km9' 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 'V10' 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 'Km10' 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 'k11ca' 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 'Km11a' 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 'k11cb' 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 'Km11b' 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 'V12' 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 'Km12' 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 'k13f' 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 'k13r' 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 'k14f' 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 'k14r' 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 'k15c' 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 'Km15' 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 'V16' 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 'Km16' 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 'ks17' 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 'kd18' does not have a 'units' attribute.

      [0m

warnings.warn(termcolor.colored(message, Colors.warning.value), category)

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: [33mThe COMBINE/OMEX archive may be invalid.

- The SED-ML file at location `./LSODA.sedml` may be invalid.

  - Model `model` may be invalid.

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

      - 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 'compartment * Henri_Michaelis_Menten__irreversible(IR, Km1, V1)' 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 'compartment * Henri_Michaelis_Menten__irreversible(pIR, Km2, V2)' 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 'compartment * HMM_Mod(k3c, IRS, pIR, Km3)' 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 'compartment * Henri_Michaelis_Menten__irreversible(pIRS, Km4, V4)' 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 'compartment * Function_for_v5(k5ca, pIRS, Akt, Km5a, k5cb, pmTORC2, Km5b)' 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 'compartment * Henri_Michaelis_Menten__irreversible(pAkt, Km6, V6)' 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 'compartment * HMM_Mod(k7c, mTORC1, pAkt, Km7)' 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 'compartment * Henri_Michaelis_Menten__irreversible(pmTORC1, Km8, V8)' 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 'compartment * HMM_Mod(k9c, mTORC2, pIR, Km9)' 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 'compartment * Henri_Michaelis_Menten__irreversible(pmTORC2, Km10, V10)' 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 'compartment * Function_for_v11(k11ca, pmTORC1, DEPTOR, Km11a, pDEPTOR, k11cb, pmTORC2, Km11b)' 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 'compartment * Henri_Michaelis_Menten__irreversible(pDEPTOR, Km12, V12)' 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 'compartment * (k13f * mTORC1 * DEPTOR - k13r * mTORC1_DEPTOR)' 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 'compartment * (k14f * mTORC2 * DEPTOR - k14r * mTORC2_DEPTOR)' 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 'compartment * HMM_Mod(k15c, IRS, pmTORC1, Km15)' 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 'compartment * Henri_Michaelis_Menten__irreversible(iIRS, Km16, V16)' 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 'compartment * Constant_flux__irreversible(ks17)' 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 'compartment * kd18 * pDEPTOR' 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 'V1' 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 'Km1' 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 'V2' 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 'Km2' 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 'k3c' 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 'Km3' 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 'V4' 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 'Km4' 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 'k5ca' 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 'Km5a' 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 'k5cb' 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 'Km5b' 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 'V6' 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 'Km6' 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 'k7c' 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 'Km7' 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 'V8' 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 'Km8' 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 'k9c' 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 'Km9' 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 'V10' 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 'Km10' 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 'k11ca' 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 'Km11a' 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 'k11cb' 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 'Km11b' 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 c ...

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-Fehlberg (0.0 s)

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

Reason for skip:
```
Case requires model formats format_2585 and simulation algorithms KISAO_0000086
```
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/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-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:sbml-qual/Irons-J-Theor-Biol-2009-yeast-cell-cycle (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.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes` (3.4 s)

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

Reason for skip:

Simulator did not produce the expected time course:

Not equal to tolerance rtol=0.0001, atol=0

Mismatched elements: 6 / 6 (100%)
Max absolute difference: 0.4
Max relative difference: 1.
 x: array([0.  , 0.08, 0.16, 0.24, 0.32, 0.4 ])
 y: array([0.4 , 0.48, 0.56, 0.64, 0.72, 0.8 ])

Log:

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

- Model `BIOMD0000000678` may be invalid.

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

    - 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 <initialAssignment> <math> expression 'stim_duration' 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 <initialAssignment> <math> expression 'stim_frequency' 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 '1 - NFAT_phosphorylated - NFAT_dephosphorylated' 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 '100 * NFAT_phosphorylated' 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 '100 * NFAT_transported' 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 '100 * NFAT_dephosphorylated' 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 'piecewise(1, lt(time - floor(time / ModelValue_13) * ModelValue_13, ModelValue_17), 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 <kineticLaw> <math> expression 'Jurkat_cell * function_for_modified_reaction_1(NFAT_phosphorylated, k1, stimulus)' 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 'Jurkat_cell * k2 * NFAT_dephosphorylated' 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 'Jurkat_cell * k3 * NFAT_dephosphorylated' 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 'Jurkat_cell * k4 * NFAT_transported' 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 'k1' 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 'k2' 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 'k3' 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 'k4' 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 'stim_frequency' 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 'dNFAT' 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 'pNFAT' 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 'tNFAT' 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 'stim_duration' 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 'ModelValue_17' 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 'ModelValue_13' does not have a 'units' attribute.

      [0m

warnings.warn(termcolor.colored(message, Colors.warning.value), category)

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: [33mThe COMBINE/OMEX archive may be invalid.

- The SED-ML file at location `./BIOMD0000000678_sim.sedml` may be invalid.

  - Model `BIOMD0000000678` may be invalid.

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

      - 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 <initialAssignment> <math> expression 'stim_duration' 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 <initialAssignment> <math> expression 'stim_frequency' 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 '1 - NFAT_phosphorylated - NFAT_dephosphorylated' 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 '100 * NFAT_phosphorylated' 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 '100 * NFAT_transported' 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 '100 * NFAT_dephosphorylated' 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 'piecewise(1, lt(time - floor(time / ModelValue_13) * ModelValue_13, ModelValue_17), 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 <kineticLaw> <math> expression 'Jurkat_cell * function_for_modified_reaction_1(NFAT_phosphorylated, k1, stimulus)' 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 'Jurkat_cell * k2 * NFAT_dephosphorylated' 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 'Jurkat_cell * k3 * NFAT_dephosphorylated' 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 'Jurkat_cell * k4 * NFAT_transported' 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 'k1' 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 'k2' 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 'k3' 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 'k4' 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 'stim_frequency' 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 'dNFAT' 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 'pNFAT' 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 'tNFAT' 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 'stim_duration' 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 'ModelValue_17' 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 'ModelValue_13' does not have a 'units' attribute.

        [0m

warnings.warn(termcolor.colored(message, Colors.warning.value), category)

Archive contains 1 SED-ML documents with 1 models, 1 simulations, 1 tasks, 1 reports, and 0 plots:

BIOMD0000000678_sim.sedml:

  Tasks (1):

    BIOMD0000000678_task

  Reports (1):

    report: 5 data sets

Executing SED-ML file 0: BIOMD0000000678_sim.sedml ...

Bundling outputs ...

Cleaning up ...

============= SUMMARY =============

Executed 1 SED documents:

SED documents (1):

  Succeeded: 1

  Skipped: 0

  Failed: 0

Tasks (1):

  Succeeded: 1

  Skipped: 0

  Failed: 0

Outputs (1):

  Succeeded: 1

  Skipped: 0

  Failed: 0

biosimulators / Biosimulators

Submit COPASI 4.33.246 #291

Summary of tests

Warnings

`cli.CliDescribesSupportedEnvironmentVariablesInline` (3.1 s)

`docker_image.HasBioContainersLabels` (0.3 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation` (3.7 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML` (4.0 s)

Skips

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

`published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:cellml/Lorenz-system` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-CVODE` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-Euler` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations` (0.0 s)

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

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

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-continuous` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-qual/Irons-J-Theor-Biol-2009-yeast-cell-cycle` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:smoldyn/Lotka-Volterra` (0.0 s)

`sedml.SimulatorProducesLinear3DPlots` (0.1 s)

`sedml.SimulatorProducesLogarithmic3DPlots` (0.1 s)

`sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes` (3.4 s)

biosimulators / Biosimulators

Submit COPASI 4.33.246 #291

Summary of tests

Warnings

cli.CliDescribesSupportedEnvironmentVariablesInline (3.1 s)

docker_image.HasBioContainersLabels (0.3 s)

published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation (3.7 s)

published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML (4.0 s)

Skips

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

published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl (0.0 s)

published_project.SimulatorCanExecutePublishedProject:cellml/Lorenz-system (0.0 s)

published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-CVODE (0.0 s)

published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-Euler (0.0 s)

published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations (0.0 s)

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

published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-continuous (0.0 s)

published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation (0.0 s)

published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution (0.0 s)

published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis (0.0 s)

published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock (0.0 s)

published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-continuous (0.0 s)

published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism (0.0 s)

published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling (0.0 s)

published_project.SimulatorCanExecutePublishedProject:sbml-qual/Irons-J-Theor-Biol-2009-yeast-cell-cycle (0.0 s)

published_project.SimulatorCanExecutePublishedProject:smoldyn/Lotka-Volterra (0.0 s)

sedml.SimulatorProducesLinear3DPlots (0.1 s)

sedml.SimulatorProducesLogarithmic3DPlots (0.1 s)

sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes (3.4 s)

`cli.CliDescribesSupportedEnvironmentVariablesInline` (3.1 s)

`docker_image.HasBioContainersLabels` (0.3 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation` (3.7 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML` (4.0 s)

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

`published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:cellml/Lorenz-system` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-CVODE` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-Euler` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations` (0.0 s)

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

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

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-continuous` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:sbml-qual/Irons-J-Theor-Biol-2009-yeast-cell-cycle` (0.0 s)

`published_project.SimulatorCanExecutePublishedProject:smoldyn/Lotka-Volterra` (0.0 s)

`sedml.SimulatorProducesLinear3DPlots` (0.1 s)

`sedml.SimulatorProducesLogarithmic3DPlots` (0.1 s)

`sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes` (3.4 s)