Submit tellurium 2.2.8

id: tellurium
version: 2.2.8
specificationsUrl: https://raw.githubusercontent.com/biosimulators/Biosimulators_tellurium/8876681e038fc35a36775494642d7284579ab226/biosimulators.json
specificationsPatch:
version: 2.2.8
image:
url: ghcr.io/biosimulators/biosimulators_tellurium/tellurium:2.2.8
digest: "sha256:1cc95630dc5490ac1cf0752a703d2d989d9cfbe0a3ad42b7e7d4027b0f348db7"
validateImage: true
commitSimulator: true

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!
The BioSimulators validator bot is validating the specifications of your simulator, validating your Docker image, and committing your simulator to the BioSimulators registry.
We will discuss any concerns with your submission in this issue.
A complete log of your simulator submission job will be available for 90 days here. The results of the validation of your tool will also be saved as a JSON file. A link to this file will be available for 90 days from the "Artifacts" section at the bottom of this page.

The specifications of your simulator is valid!

Summary of tests

Executed 74 test cases

Passed 45 test cases:

cli.CliDescribesSupportedEnvironmentVariablesInline
cli.CliDisplaysHelpInline
cli.CliDisplaysVersionInformationInline
combine_archive.CombineArchiveHasSedDocumentsInNestedDirectories
combine_archive.CombineArchiveHasSedDocumentsWithSameNamesInDifferentInNestedDirectories
combine_archive.WhenACombineArchiveHasAMasterFileSimulatorOnlyExecutesThisFile
combine_archive.WhenACombineArchiveHasNoMasterFileSimulatorExecutesAllSedDocuments
docker_image.DeclaresSupportedEnvironmentVariables
docker_image.DefaultUserIsRoot
docker_image.HasBioContainersLabels
docker_image.HasOciLabels
docker_image.SingularityImageExecutesSimulationsSuccessfully
log.SimulatorReportsTheStatusOfTheExecutionOfCombineArchives
log.SimulatorReportsTheStatusOfTheExecutionOfSedDocuments
log.SimulatorReportsTheStatusOfTheExecutionOfSedOutputs
log.SimulatorReportsTheStatusOfTheExecutionOfSedTasks
published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations
published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-Fehlberg
published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-continuous
published_project.SimulatorCanExecutePublishedProject:sbml-core/Elowitz-Nature-2000-Repressilator
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-continuous
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-SSA
results_report.SimulatorGeneratesReportsOfSimulationResults
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragments
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragmentsAndInheritChanges
sedml.SimulatorProducesLinear2DPlots
sedml.SimulatorProducesLogarithmic2DPlots
sedml.SimulatorProducesMultiplePlots
sedml.SimulatorSupportsAlgorithmParameters
sedml.SimulatorSupportsDataGeneratorsWithDifferentShapes
sedml.SimulatorSupportsDataSetsWithDifferentShapes
sedml.SimulatorSupportsModelsSimulationsTasksDataGeneratorsAndReports
sedml.SimulatorSupportsMultipleReportsPerSedDocument
sedml.SimulatorSupportsMultipleTasksPerSedDocument
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithLinearUniformRanges
sedml.SimulatorSupportsRepeatedTasksWithLogarithmicUniformRanges
sedml.SimulatorSupportsRepeatedTasksWithMultipleSubTasks
sedml.SimulatorSupportsRepeatedTasksWithNestedFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithNestedRepeatedTasks
sedml.SimulatorSupportsRepeatedTasksWithSubTasksOfMixedTypes
sedml.SimulatorSupportsRepeatedTasksWithVectorRanges
sedml.SimulatorSupportsSubstitutingAlgorithms
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroOutputStartTimes

Failed 0 test cases

Skipped 29 test cases:

published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ
published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl
published_project.SimulatorCanExecutePublishedProject:cellml/Elowitz-Nature-2000-Repressilator
published_project.SimulatorCanExecutePublishedProject:cellml/Lorenz-system
published_project.SimulatorCanExecutePublishedProject:mass/Bordbar-Cell-Syst-2015-RBC-metabolism
published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-CVODE
published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-Euler
published_project.SimulatorCanExecutePublishedProject:rba/Escherichia-coli-K12-WT
published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution
published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis
published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-NRM
published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism
published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling
published_project.SimulatorCanExecutePublishedProject:sbml-qual/Irons-J-Theor-Biol-2009-yeast-cell-cycle
published_project.SimulatorCanExecutePublishedProject:smoldyn/Lotka-Volterra
published_project.SimulatorCanExecutePublishedProject:vcml/Powers-Pflugers-Arch-2016-Drosophila-synaptic-strength
published_project.SimulatorCanExecutePublishedProject:xpp/Wu-Biochem-Pharmacol-2006-pituitary-GH3-cells
sedml.SimulatorProducesLinear3DPlots
sedml.SimulatorProducesLogarithmic3DPlots
sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions
sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges
sedml.SimulatorSupportsComputeModelChanges
sedml.SimulatorSupportsModelAttributeChanges
sedml.SimulatorSupportsRepeatedTasksWithChanges
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRangeVariables

Warnings
docker_image.DeclaresSupportedEnvironmentVariables (0.4 s)

Test if a Docker image declares the environment variables that is supports
Warnings:
Docker images for simulation tools should declare the environment variables that they support.

The Docker image does not declare the following standard environment variables recognized by BioSimulators:
  - 'ALGORITHM_SUBSTITUTION_POLICY'
  - 'BUNDLE_OUTPUTS'
  - 'COLLECT_COMBINE_ARCHIVE_RESULTS'
  - 'COLLECT_SED_DOCUMENT_RESULTS'
  - 'DEBUG'
  - 'H5_REPORTS_PATH'
  - 'KEEP_INDIVIDUAL_OUTPUTS'
  - 'LOG_PATH'
  - 'OMEX_METADATA_INPUT_FORMAT'
  - 'OMEX_METADATA_OUTPUT_FORMAT'
  - 'OMEX_METADATA_SCHEMA'
  - 'PLOTS_PATH'
  - 'REPORTS_PATH'
  - 'REPORT_FORMATS'
  - 'SAVE_PLOT_DATA'
  - 'VALIDATE_IMAGES'
  - 'VALIDATE_IMPORTED_MODEL_FILES'
  - 'VALIDATE_OMEX_MANIFESTS'
  - 'VALIDATE_OMEX_METADATA'
  - 'VALIDATE_RESULTS'
  - 'VALIDATE_SEDML'
  - 'VALIDATE_SEDML_MODELS'
  - 'VIZ_FORMATS'

If the simulation tool implements these variables, they should be declared in the Dockerfile for the Docker image for the simulator.

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

Log: None

docker_image.HasBioContainersLabels (0.2 s)

Test that a Docker image has BioContainers labels with metadata about the image
Warnings:
Docker images are encouraged to have the following BioContainers labels:
  extra.identifiers.biotools

Log: None

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: None

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: None

published_project.SimulatorCanExecutePublishedProject:cellml/Elowitz-Nature-2000-Repressilator (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: None

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: None

published_project.SimulatorCanExecutePublishedProject:mass/Bordbar-Cell-Syst-2015-RBC-metabolism (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: None

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: None

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: None

published_project.SimulatorCanExecutePublishedProject:rba/Escherichia-coli-K12-WT (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_9012
Algorithm: KISAO_0000669

Reason for skip:
Case requires model formats format_9012 and simulation algorithms KISAO_0000669

Log: None

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: None

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: None

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: None

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

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000560

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000560

Log: None

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

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000560

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000560

Log: None

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

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000019, KISAO_0000027

Log: None

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

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000027

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000027

Log: None

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: None

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: None

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: None

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: None

published_project.SimulatorCanExecutePublishedProject:vcml/Powers-Pflugers-Arch-2016-Drosophila-synaptic-strength (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_9000
Algorithm: KISAO_0000019

Reason for skip:
Case requires model formats format_9000 and simulation algorithms KISAO_0000019

Log: None

published_project.SimulatorCanExecutePublishedProject:xpp/Wu-Biochem-Pharmacol-2006-pituitary-GH3-cells (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_9010
Algorithm: KISAO_0000019

Reason for skip:
Case requires model formats format_9010 and simulation algorithms KISAO_0000019

Log: None

sedml.SimulatorProducesLinear3DPlots (0.2 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: None

sedml.SimulatorProducesLogarithmic3DPlots (0.2 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: None

sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions (0.2 s)

Test that that the curated number of output dimensions matches the actual number of output dimensions
Reason for skip:
No curated COMBINE/OMEX archives are available to generate archives for testing

Log: None

sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges (8.0 s)

Test that a simulator supports model changes that involve adding, replacing, and removing model elements.
Reason for skip:
The image 'ghcr.io/biosimulators/biosimulators_tellurium/tellurium:2.2.8' could not execute the archive:

  Unknown error

Log:
/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

COMBINE/OMEX archive has warnings.

  - The manifest does not include its parent COMBINE/OMEX archive. Manifests should include their parent COMBINE/OMEX archives.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The SED document is potentially incorrect.

  - This tool validates XPaths for model changes and variables against their unmodified target models. As a result, this tool does not fully validate these XPaths. These XPaths could be invalidated by changes to their target models.

  - Model `BIOMD0000000912` has warnings.

    - The model file `Caravagna2010.xml` has warnings.

      - 6 warnings of type SBML unit consistency (99505). The following is the first warning at line 570, column 8:

        - 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_induction_of_tumor(r2, T, b, V)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

      - 14 warnings of type Modeling practice (80701). The following is the first warning at line 525, column 6:

        - 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 'r2' does not have a 'units' attribute.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The COMBINE/OMEX archive has warnings.

  - The SED-ML file at location `./BIOMD0000000912_sim.sedml` has warnings.

    - This tool validates XPaths for model changes and variables against their unmodified target models. As a result, this tool does not fully validate these XPaths. These XPaths could be invalidated by changes to their target models.

    - Model `BIOMD0000000912` has warnings.

      - The model file `Caravagna2010.xml` has warnings.

        - 6 warnings of type SBML unit consistency (99505). The following is the first warning at line 570, column 8:

          - 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_induction_of_tumor(r2, T, b, V)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

        - 14 warnings of type Modeling practice (80701). The following is the first warning at line 525, column 6:

          - 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 'r2' does not have a 'units' attribute.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The SED document is potentially incorrect.

  - This tool validates XPaths for model changes and variables against their unmodified target models. As a result, this tool does not fully validate these XPaths. These XPaths could be invalidated by changes to their target models.

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

  BIOMD0000000912_sim.sedml:

    Tasks (1):

      BIOMD0000000912_task

    Reports (1):

      report: 4 data sets

Executing SED-ML file 1: BIOMD0000000912_sim.sedml ...

Bundling outputs ...

Cleaning up ...

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

Executed 1 SED documents:

  SED documents (1):

    Succeeded: 0

    Skipped: 0

    Failed: 1

  Tasks (1):

    Succeeded: 0

    Skipped: 0

    Failed: 1

  Outputs (1):

    Succeeded: 0

    Skipped: 1

    Failed: 0

The COMBINE/OMEX did not execute successfully:

  The SED document did not execute successfully:

    Model `BIOMD0000000912` is invalid.

      - The model file `/tmp/tmplkofkjuy/./Caravagna2010.xml` is invalid.

        - General SBML conformance (20201) at line 4, column 0: An SBML document must contain a <model> element. The <model> element is optional in L3V2 and beyond.

          Reference: L2V4 Section 4.1

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

COMBINE/OMEX archive has warnings.

  - The manifest does not include its parent COMBINE/OMEX archive. Manifests should include their parent COMBINE/OMEX archives.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The SED document is potentially incorrect.

  - This tool validates XPaths for model changes and variables against their unmodified target models. As a result, this tool does not fully validate these XPaths. These XPaths could be invalidated by changes to their target models.

  - Model `BIOMD0000000912` has warnings.

    - The model file `Caravagna2010.xml` has warnings.

      - 6 warnings of type SBML unit consistency (99505). The following is the first warning at line 570, column 8:

        - 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_induction_of_tumor(r2, T, b, V)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

      - 14 warnings of type Modeling practice (80701). The following is the first warning at line 525, column 6:

        - 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 'r2' does not have a 'units' attribute.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The COMBINE/OMEX archive has warnings.

  - The SED-ML file at location `./BIOMD0000000912_sim.sedml` has warnings.

    - This tool validates XPaths for model changes and variables against their unmodified target models. As a result, this tool does not fully validate these XPaths. These XPaths could be invalidated by changes to their target models.

    - Model `BIOMD0000000912` has warnings.

      - The model file `Caravagna2010.xml` has warnings.

        - 6 warnings of type SBML unit consistency (99505). The following is the first warning at line 570, column 8:

          - 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_induction_of_tumor(r2, T, b, V)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

        - 14 warnings of type Modeling practice (80701). The following is the first warning at line 525, column 6:

          - 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 'r2' does not have a 'units' attribute.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The SED document is potentially incorrect.

  - This tool validates XPaths for model changes and variables against their unmodified target models. As a result, this tool does not fully validate these XPaths. These XPaths could be invalidated by changes to their target models.

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

  BIOMD0000000912_sim.sedml:

    Tasks (1):

      BIOMD0000000912_task

    Reports (1):

      report: 4 data sets

Executing SED-ML file 1: BIOMD0000000912_sim.sedml ...

Bundling outputs ...

Cleaning up ...

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

Executed 1 SED documents:

  SED documents (1):

    Succeeded: 0

    Skipped: 0

    Failed: 1

  Tasks (1):

    Succeeded: 0

    Skipped: 0

    Failed: 1

  Outputs (1):

    Succeeded: 0

    Skipped: 1

    Failed: 0

The COMBINE/OMEX did not execute successfully:

  The SED document did not execute successfully:

    The targets for the following changes are not valid:

      - 1: /sbml:sbml/sbml:model: Caravagna2010___Tumour_suppression_by_immune_system

      - 2: /sbml:sbml: None

    Change targets must address one of the following SBML ids:

      - E

      - I

      - T

      - V

      - a

      - b

      - c

      - compartment

      - g1

      - g2

      - g3

      - mu2

      - mu3

      - p1

      - p2

      - r2

      - s1

      - s2

sedml.SimulatorSupportsComputeModelChanges (8.4 s)

Test that a simulator supports compute model changes
Reason for skip:
The image 'ghcr.io/biosimulators/biosimulators_tellurium/tellurium:2.2.8' could not execute the archive:

  Unknown error

Log:
/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

COMBINE/OMEX archive has warnings.

  - The manifest does not include its parent COMBINE/OMEX archive. Manifests should include their parent COMBINE/OMEX archives.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The SED document is potentially incorrect.

  - Model `BIOMD0000000912` has warnings.

    - The model file `Caravagna2010.xml` has warnings.

      - 6 warnings of type SBML unit consistency (99505). The following is the first warning at line 570, column 8:

        - 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_induction_of_tumor(r2, T, b, V)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

      - 14 warnings of type Modeling practice (80701). The following is the first warning at line 525, column 6:

        - 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 'r2' does not have a 'units' attribute.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The COMBINE/OMEX archive has warnings.

  - The SED-ML file at location `./BIOMD0000000912_sim.sedml` has warnings.

    - Model `BIOMD0000000912` has warnings.

      - The model file `Caravagna2010.xml` has warnings.

        - 6 warnings of type SBML unit consistency (99505). The following is the first warning at line 570, column 8:

          - 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_induction_of_tumor(r2, T, b, V)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

        - 14 warnings of type Modeling practice (80701). The following is the first warning at line 525, column 6:

          - 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 'r2' does not have a 'units' attribute.

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

  BIOMD0000000912_sim.sedml:

    Tasks (1):

      BIOMD0000000912_task

    Reports (1):

      report: 4 data sets

Executing SED-ML file 1: BIOMD0000000912_sim.sedml ...

Bundling outputs ...

Cleaning up ...

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

Executed 1 SED documents:

  SED documents (1):

    Succeeded: 0

    Skipped: 0

    Failed: 1

  Tasks (1):

    Succeeded: 0

    Skipped: 0

    Failed: 1

  Outputs (1):

    Succeeded: 0

    Skipped: 1

    Failed: 0

The COMBINE/OMEX did not execute successfully:

  The SED document did not execute successfully:

    The targets for the following changes are not valid:

      - 1: /sbml:sbml[1]/@level: None

      - 28: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@exponent: None

      - 29: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@multiplier: None

      - 2: /sbml:sbml[1]/@version: None

      - 30: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@scale: None

      - 31: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@exponent: None

      - 32: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@multiplier: None

      - 33: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@scale: None

      - 34: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@exponent: None

      - 35: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@multiplier: None

      - 36: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@scale: None

      - 3: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[6]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 4: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 5: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 6: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[3]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 7: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[2]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 8: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[1]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@stoichiometry: None

    Change targets must address one of the following SBML ids:

      - E

      - I

      - T

      - V

      - a

      - b

      - c

      - compartment

      - g1

      - g2

      - g3

      - mu2

      - mu3

      - p1

      - p2

      - r2

      - s1

      - s2

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

COMBINE/OMEX archive has warnings.

  - The manifest does not include its parent COMBINE/OMEX archive. Manifests should include their parent COMBINE/OMEX archives.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The SED document is potentially incorrect.

  - This tool validates XPaths for model changes and variables against their unmodified target models. As a result, this tool does not fully validate these XPaths. These XPaths could be invalidated by changes to their target models.

  - Model `BIOMD0000000912` has warnings.

    - The model file `Caravagna2010.xml` has warnings.

      - 6 warnings of type SBML unit consistency (99505). The following is the first warning at line 570, column 8:

        - 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_induction_of_tumor(r2, T, b, V)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

      - 14 warnings of type Modeling practice (80701). The following is the first warning at line 525, column 6:

        - 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 'r2' does not have a 'units' attribute.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The COMBINE/OMEX archive has warnings.

  - The SED-ML file at location `./BIOMD0000000912_sim.sedml` has warnings.

    - This tool validates XPaths for model changes and variables against their unmodified target models. As a result, this tool does not fully validate these XPaths. These XPaths could be invalidated by changes to their target models.

    - Model `BIOMD0000000912` has warnings.

      - The model file `Caravagna2010.xml` has warnings.

        - 6 warnings of type SBML unit consistency (99505). The following is the first warning at line 570, column 8:

          - 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_induction_of_tumor(r2, T, b, V)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

        - 14 warnings of type Modeling practice (80701). The following is the first warning at line 525, column 6:

          - 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 'r2' does not have a 'units' attribute.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The SED document is potentially incorrect.

  - This tool validates XPaths for model changes and variables against their unmodified target models. As a result, this tool does not fully validate these XPaths. These XPaths could be invalidated by changes to their target models.

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

  BIOMD0000000912_sim.sedml:

    Tasks (1):

      BIOMD0000000912_task

    Reports (1):

      report: 4 data sets

Executing SED-ML file 1: BIOMD0000000912_sim.sedml ...

Bundling outputs ...

Cleaning up ...

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

Executed 1 SED documents:

  SED documents (1):

    Succeeded: 0

    Skipped: 0

    Failed: 1

  Tasks (1):

    Succeeded: 0

    Skipped: 0

    Failed: 1

  Outputs (1):

    Succeeded: 0

    Skipped: 1

    Failed: 0

The COMBINE/OMEX did not execute successfully:

  The SED document did not execute successfully:

    The targets for the following changes are not valid:

      - 10: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 11: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[3]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 12: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[3]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 13: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[2]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 14: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[2]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 15: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[1]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 16: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[1]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 1: /sbml:sbml[1]/@level: None

      - 2: /sbml:sbml[1]/@level: None

      - 3: /sbml:sbml[1]/@version: None

      - 4: /sbml:sbml[1]/@version: None

      - 55: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@exponent: None

      - 56: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@exponent: None

      - 57: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@multiplier: None

      - 58: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@multiplier: None

      - 59: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@scale: None

      - 5: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[6]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 60: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@scale: None

      - 61: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@exponent: None

      - 62: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@exponent: None

      - 63: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@multiplier: None

      - 64: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@multiplier: None

      - 65: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@scale: None

      - 66: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@scale: None

      - 67: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@exponent: None

      - 68: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@exponent: None

      - 69: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@multiplier: None

      - 6: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[6]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 70: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@multiplier: None

      - 71: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@scale: None

      - 72: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@scale: None

      - 7: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 8: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 9: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@stoichiometry: None

    Change targets must address one of the following SBML ids:

      - E

      - I

      - T

      - V

      - a

      - b

      - c

      - compartment

      - g1

      - g2

      - g3

      - mu2

      - mu3

      - p1

      - p2

      - r2

      - s1

      - s2

sedml.SimulatorSupportsModelAttributeChanges (9.3 s)

Test that a simulator supports changes to the attributes of model elements
Reason for skip:
The image 'ghcr.io/biosimulators/biosimulators_tellurium/tellurium:2.2.8' could not execute the archive:

  Unknown error

Log:
/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

COMBINE/OMEX archive has warnings.

  - The manifest does not include its parent COMBINE/OMEX archive. Manifests should include their parent COMBINE/OMEX archives.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The SED document is potentially incorrect.

  - This tool validates XPaths for model changes and variables against their unmodified target models. As a result, this tool does not fully validate these XPaths. These XPaths could be invalidated by changes to their target models.

  - Model `BIOMD0000000912` has warnings.

    - The model file `Caravagna2010.xml` has warnings.

      - 6 warnings of type SBML unit consistency (99505). The following is the first warning at line 570, column 8:

        - 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_induction_of_tumor(r2, T, b, V)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

      - 14 warnings of type Modeling practice (80701). The following is the first warning at line 525, column 6:

        - 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 'r2' does not have a 'units' attribute.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The COMBINE/OMEX archive has warnings.

  - The SED-ML file at location `./BIOMD0000000912_sim.sedml` has warnings.

    - This tool validates XPaths for model changes and variables against their unmodified target models. As a result, this tool does not fully validate these XPaths. These XPaths could be invalidated by changes to their target models.

    - Model `BIOMD0000000912` has warnings.

      - The model file `Caravagna2010.xml` has warnings.

        - 6 warnings of type SBML unit consistency (99505). The following is the first warning at line 570, column 8:

          - 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_induction_of_tumor(r2, T, b, V)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.

        - 14 warnings of type Modeling practice (80701). The following is the first warning at line 525, column 6:

          - 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 'r2' does not have a 'units' attribute.

/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning:

The SED document is potentially incorrect.

  - This tool validates XPaths for model changes and variables against their unmodified target models. As a result, this tool does not fully validate these XPaths. These XPaths could be invalidated by changes to their target models.

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

  BIOMD0000000912_sim.sedml:

    Tasks (1):

      BIOMD0000000912_task

    Reports (1):

      report: 4 data sets

Executing SED-ML file 1: BIOMD0000000912_sim.sedml ...

Bundling outputs ...

Cleaning up ...

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

Executed 1 SED documents:

  SED documents (1):

    Succeeded: 0

    Skipped: 0

    Failed: 1

  Tasks (1):

    Succeeded: 0

    Skipped: 0

    Failed: 1

  Outputs (1):

    Succeeded: 0

    Skipped: 1

    Failed: 0

The COMBINE/OMEX did not execute successfully:

  The SED document did not execute successfully:

    The targets for the following changes are not valid:

      - 10: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[6]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@species: None

      - 11: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[6]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 12: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[6]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 134: /sbml:sbml[1]/sbml:model[1]/sbml:listOfSpecies[1]/sbml:species[3]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 135: /sbml:sbml[1]/sbml:model[1]/sbml:listOfSpecies[1]/sbml:species[3]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/bqbiol:hasProperty[1]/@rdf:resource: None

      - 136: /sbml:sbml[1]/sbml:model[1]/sbml:listOfSpecies[1]/sbml:species[3]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 137: /sbml:sbml[1]/sbml:model[1]/sbml:listOfSpecies[1]/sbml:species[3]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqbiol:hasProperty[1]/rdf:Bag[1]/rdf:li[1]/@rdf:resource: None

      - 13: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[6]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/CopasiMT:isVersionOf[1]/@rdf:resource: None

      - 145: /sbml:sbml[1]/sbml:model[1]/sbml:listOfSpecies[1]/sbml:species[2]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 146: /sbml:sbml[1]/sbml:model[1]/sbml:listOfSpecies[1]/sbml:species[2]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/bqbiol:hasProperty[1]/@rdf:resource: None

      - 147: /sbml:sbml[1]/sbml:model[1]/sbml:listOfSpecies[1]/sbml:species[2]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 148: /sbml:sbml[1]/sbml:model[1]/sbml:listOfSpecies[1]/sbml:species[2]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqbiol:hasProperty[1]/rdf:Bag[1]/rdf:li[1]/@rdf:resource: None

      - 14: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[6]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 156: /sbml:sbml[1]/sbml:model[1]/sbml:listOfSpecies[1]/sbml:species[1]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 157: /sbml:sbml[1]/sbml:model[1]/sbml:listOfSpecies[1]/sbml:species[1]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/CopasiMT:isVersionOf[1]/@rdf:resource: None

      - 158: /sbml:sbml[1]/sbml:model[1]/sbml:listOfSpecies[1]/sbml:species[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 159: /sbml:sbml[1]/sbml:model[1]/sbml:listOfSpecies[1]/sbml:species[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqbiol:isVersionOf[1]/rdf:Bag[1]/rdf:li[1]/@rdf:resource: None

      - 15: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[6]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqbiol:isVersionOf[1]/rdf:Bag[1]/rdf:li[1]/@rdf:resource: None

      - 165: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/@id: substance

      - 166: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/@name: substance

      - 167: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@exponent: None

      - 168: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@kind: None

      - 169: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@multiplier: None

      - 16: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/@id: Activation_of_interleukin_2

      - 170: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[3]/sbml:listOfUnits[1]/sbml:unit[1]/@scale: None

      - 171: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/@id: time

      - 172: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/@name: time

      - 173: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@exponent: None

      - 174: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@kind: None

      - 175: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@multiplier: None

      - 176: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[2]/sbml:listOfUnits[1]/sbml:unit[1]/@scale: None

      - 177: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/@id: volume

      - 178: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/@name: volume

      - 179: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@exponent: None

      - 17: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/@metaid: Activation_of_interleukin_2

      - 180: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@kind: None

      - 181: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@multiplier: None

      - 182: /sbml:sbml[1]/sbml:model[1]/sbml:listOfUnitDefinitions[1]/sbml:unitDefinition[1]/sbml:listOfUnits[1]/sbml:unit[1]/@scale: None

      - 183: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[6]/@id: Function_for_deactivation_and_removal_of_effector_cells_from_the_site_of_tumor

      - 184: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[6]/@metaid: Function_for_deactivation_and_removal_of_effector_cells_from_the_site_of_tumor

      - 185: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[6]/@name: Function_for_deactivation_and_removal_of_effector_cells_from_the_site_of_tumor

      - 186: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[6]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 187: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[5]/@id: Function_for_activation_and_transfer_of_effector_cells_to_the_tumor_site

      - 188: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[5]/@metaid: Function_for_activation_and_transfer_of_effector_cells_to_the_tumor_site

      - 189: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[5]/@name: Function_for_activation_and_transfer_of_effector_cells_to_the_tumor_site

      - 18: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/@name: Activation_of_interleukin_2

      - 190: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[5]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 191: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[4]/@id: Function_for_activation_of_interleukin_2

      - 192: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[4]/@metaid: Function_for_activation_of_interleukin_2

      - 193: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[4]/@name: Function_for_activation_of_interleukin_2

      - 194: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[4]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 195: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[3]/@id: Function_for_deactivation_of_interleukin_2

      - 196: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[3]/@metaid: Function_for_deactivation_of_interleukin_2

      - 197: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[3]/@name: Function_for_deactivation_of_interleukin_2

      - 198: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[3]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 199: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[2]/@id: Function_for_induction_of_tumor

      - 19: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/@reversible: Activation_of_interleukin_2

      - 1: /sbml:sbml[1]/@level: None

      - 200: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[2]/@metaid: Function_for_induction_of_tumor

      - 201: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[2]/@name: Function_for_induction_of_tumor

      - 202: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[2]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 203: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[1]/@id: Function_for_removal_of_the_tumor

      - 204: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[1]/@metaid: Function_for_removal_of_the_tumor

      - 205: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[1]/@name: Function_for_removal_of_the_tumor

      - 206: /sbml:sbml[1]/sbml:model[1]/sbml:listOfFunctionDefinitions[1]/sbml:functionDefinition[1]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 207: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 208: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/dcterms:bibliographicCitation[1]/rdf:Description[1]/CopasiMT:isDescribedBy[1]/@rdf:resource: None

      - 209: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/bqmodel:isDerivedFrom[1]/@rdf:resource: None

      - 20: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/sbml:listOfModifiers[1]/sbml:modifierSpeciesReference[2]/@species: None

      - 210: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/bqbiol:hasTaxon[1]/@rdf:resource: None

      - 211: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/bqbiol:hasProperty[1]/@rdf:resource: None

      - 212: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 213: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqmodel:is[1]/rdf:Bag[1]/rdf:li[2]/@rdf:resource: None

      - 214: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqmodel:is[1]/rdf:Bag[1]/rdf:li[1]/@rdf:resource: None

      - 215: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqbiol:hasProperty[1]/rdf:Bag[1]/rdf:li[1]/@rdf:resource: None

      - 216: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqbiol:hasTaxon[1]/rdf:Bag[1]/rdf:li[1]/@rdf:resource: None

      - 217: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqmodel:isDescribedBy[1]/rdf:Bag[1]/rdf:li[2]/@rdf:resource: None

      - 218: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqmodel:isDescribedBy[1]/rdf:Bag[1]/rdf:li[1]/@rdf:resource: None

      - 219: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqmodel:isDerivedFrom[1]/rdf:Bag[1]/rdf:li[3]/@rdf:resource: None

      - 21: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/sbml:listOfModifiers[1]/sbml:modifierSpeciesReference[1]/@species: None

      - 220: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqmodel:isDerivedFrom[1]/rdf:Bag[1]/rdf:li[2]/@rdf:resource: None

      - 221: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqmodel:isDerivedFrom[1]/rdf:Bag[1]/rdf:li[1]/@rdf:resource: None

      - 222: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/dcterms:modified[1]/@rdf:parseType: None

      - 223: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/dcterms:created[1]/@rdf:parseType: None

      - 224: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/dc:creator[1]/rdf:Bag[1]/rdf:li[1]/@rdf:parseType: None

      - 225: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/dc:creator[1]/rdf:Bag[1]/rdf:li[1]/vCard:ORG[1]/@rdf:parseType: None

      - 226: /sbml:sbml[1]/sbml:model[1]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/dc:creator[1]/rdf:Bag[1]/rdf:li[1]/vCard:N[1]/@rdf:parseType: None

      - 22: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@species: None

      - 23: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 24: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 25: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/CopasiMT:isVersionOf[1]/@rdf:resource: None

      - 26: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 27: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[5]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqbiol:isVersionOf[1]/rdf:Bag[1]/rdf:li[1]/@rdf:resource: None

      - 28: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/@id: Deactivation_and_removal_of_effector_cells_from_the_site_of_tumor

      - 29: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/@metaid: Deactivation_and_removal_of_effector_cells_from_the_site_of_tumor

      - 2: /sbml:sbml[1]/@version: None

      - 30: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/@name: Deactivation_and_removal_of_effector_cells_from_the_site_of_tumor

      - 31: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/@reversible: Deactivation_and_removal_of_effector_cells_from_the_site_of_tumor

      - 32: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@species: None

      - 33: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/sbml:listOfReactants[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 34: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 35: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/sbml:annotation[1]/COPASI:COPASI[1]/rdf:RDF[1]/rdf:Description[1]/CopasiMT:isVersionOf[1]/@rdf:resource: None

      - 36: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/@rdf:about: None

      - 37: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[4]/sbml:annotation[1]/rdf:RDF[1]/rdf:Description[1]/bqbiol:isVersionOf[1]/rdf:Bag[1]/rdf:li[1]/@rdf:resource: None

      - 38: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[3]/@id: Activation_and_transfer_of_effector_cells_to_the_action_site

      - 39: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[3]/@metaid: Activation_and_transfer_of_effector_cells_to_the_action_site

      - 3: /sbml:sbml[1]/sbml:model[1]/@id: Caravagna2010___Tumour_suppression_by_immune_system

      - 40: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[3]/@name: Activation_and_transfer_of_effector_cells_to_the_action_site

      - 41: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[3]/@reversible: Activation_and_transfer_of_effector_cells_to_the_action_site

      - 42: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[3]/sbml:listOfModifiers[1]/sbml:modifierSpeciesReference[2]/@species: None

      - 43: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[3]/sbml:listOfModifiers[1]/sbml:modifierSpeciesReference[1]/@species: None

      - 44: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[3]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@species: None

      - 45: /sbml:sbml[1]/sbml:model[1]/sbml:listOfReactions[1]/sbml:reaction[3]/sbml:listOfProducts[1]/sbml:speciesReference[1]/@stoichiometry: None

      - 46: /sbml:sbml[1]/sbml:model[1]/s ...

The image for your simulator is valid!

The validation/submission of your simulator failed.
- 504 Server Error: Gateway Time-out for url: https://api.biosimulations.org/images/refresh

The complete log of your validation/submission job, including further information about the failure, is available for 90 days here.
If you chose to validate your Docker image, the results of the validation of your image will be available shortly as a JSON file. A link to this file will be available for 90 days from the "Artifacts" section at the bottom of this page.
Once you have fixed the problem, edit the first block of this issue to re-initiate this validation.
The BioSimulators Team is happy to help. Questions and feedback can be directed to the BioSimulators Team by posting comments to this issues that reference the GitHub team @biosimulators/biosimulators (without the backticks).


couchdb disaster recovery

Description
i have a couchdb 3.1 cluster with 2 nodes VM and i backup daily data and etc folder
i would like to create, starting from backup same servers and data in a new environment (i would like to simulate a complete down on the old infrastructure)
i setup two couchdb, than i restore the 2 folder, than i change the ipaddress under vm.args
i add and remove the ip on the cluster to matching the actual configuration
https://docs.couchdb.org/en/stable/cluster/nodes.html#adding-a-node
in the interface i can see all the databases but are in status [This database failed to load.]
in the log file i have [Failed to ensure auth ddoc _users/_design/_auth exists for reason: read_failure]
if i try to browse _users/_design/_auth i receave
error	"internal_server_error"
reason	"No DB shards could be opened."
ref<PHONE_NUMBER>
there is a step by step guide to do this?
Steps to Reproduce
Expected Behaviour
disaster solution for a cluster starting from backup
Your Environment

CouchDB version used:3.1
Browser name and version:
Operating system and version:ubuntu 18

Additional Context

Hi there,
This is not a CouchDB bug. GitHub is for actual CouchDB bugs only. I will, however, keep this open as a request for more documentation.
If you are looking for general support with using CouchDB, please try one of these other options:

The user mailing list. Signup instructions are here
The Slack/IRC chat room. Joining instructions are here


WIP: Alternate implementation to only trigger on changes

This is an alternate method of detecting changes to PR #76.
It provides changes, old_state, and new_state to func_args.
It uses state_trig_ident to determine what the trigger cares about and only fires the function if one of these has changed.
It only fires once per state_changed event, since State.update() is only called once per state_changed event.
It does NOT fire if domain.entity.attribute has changed when only domain.entity is included in state_trigger.
This PR could be extended to provide only_on_change=False kwarg functionality like #76 did.
This PR could be extended to provide any_attribute_change=True kwarg to allow any attribute change to fire the function.
This PR could also be extended to provide domain.entity.old.attribute pseudo-variables for checking in state_trigger.

This looks much better - thanks for updating with the new approach.
While it's helpful to compute the changes and passing them to the trigger function, that will become unnecessary when value and old_value become magic objects, since the user can easily figure it out for themselves.  I'd prefer not to grow the function arguments unless it's really compelling.
On the multi-trigger question, I think this strikes the right balance.  The principle is this: each@state_trigger can only trigger at most once for a given state change event. So if a state value and multiple attributes are set together (so there is one state change event with multiple changes), then that should only cause each trigger to be evaluated once.  Of course, one state change event could cause many different triggers to be checked and potentially fired.  If instead a state variable value is set, and then right afterwards an attribute change is made, then there will be two state changed events, and that could cause two triggers if @state_trigger is true each time.  Note that the first eval will have the new state value, but the old attribute, and the 2nd one will have both new values.
For "trigger on any change", how about this:

state variable "domain.entity" triggers only when that state value changes. This will be a breaking change, but I think users can easily adapt; I doubt many users depend on the old behavior.
attribute "domain.entity.attr" triggers only when that attribute value changes. This is new.
"domain.entity.*" triggers when any attribute value changes (not value). This is new.

The third form could also include the state value changes too.  I could go either way.  Thoughts?
I don't think we need to have any additional kwargs options, unless we are really concerned about the breaking changes for trigger only on change (which is actually a bug we are fixing), and "domain.entity" meaning just the state value changed.
I'm happy to accept this PR as a stepping stone, and I'll start working on the states as objects, which I now have some idea about how to approach.  Then we can update after that.
BTW, the test fails because the trigger functions have new arguments which the tests aren't expecting.  The output is very verbose, but there are particular lines that show which assert failed and the differences between the expected and actual value at that point.

While it's helpful to compute the changes and passing them to the trigger function, that will become unnecessary when value and old_value become magic objects, since the user can easily figure it out for themselves. I'd prefer not to grow the function arguments unless it's really compelling.

I agree that growing the function arguments isn't ideal. Perhaps I can set some additional *.old variables and then cycle through them in trigger.py. I'll give that a shot.
I'll take a swing at implementing domain.entity.* as well as you described. And, while I'm not too opinionated on whether domain.entity.* should include the state as well, I can't imagine a situation where someone would want updates on all the attributes but not also the state. It seems like they'd either want to pick individual things or they'd just want EVERYTHING so they can sort it out themselves in code.
I'll dig through the test output again and see if I can correct it. Though, if I succeed at handling this change, it won't even be needed.

@craigbarratt I've updated this branch to attempt this in a new way. My limited testing shows that it works just fine. However, I made a change to state.notify_var_get to ensure that the data put on the queue includes all new_vars. It seems okay, but I'm not sure why it wasn't this way to begin with, so maybe I've overlooked something and this is a bad thing to do.

I made my "magic state object" commit f7169ac.  Turned out to be very simple and elegant. Now you can do things like:
x = input_sensor.test1
x.last_updated

I added some comments to the PR about how to use these new objects.  Hopefully they make sense.  The idea is that value and old_value will now be StateVar objects, which look like a string but contain the state attributes too.

Oooh. This new commit of yours will make this a lot easier. Excellent!
I'll rework this whole thing. And I can probably put state.notify_var_get back the way it was.

replaced by #82


Revert addition of Swift network

This PR reverts the following merged PRs:

https://github.com/openstack-k8s-operators/ci-framework/pull/2301
https://github.com/openstack-k8s-operators/ci-framework/pull/2390

For reasons documented in the Jira below we will not add the RGW network to va/hci.
Jira: https://issues.redhat.com/browse/OSPRH-10496

I recommend merging https://github.com/openstack-k8s-operators/architecture/pull/410 before this PR

recheck

/approve


Added raw data access

We have made small addition to library for our needs (and fixed some minor code style/format issues), we would love for this addition to be integrated and release via nuget if you find this addition worth including.

I'm not clear on what the need for this is? Seems to me we'll just be raising events for the same message twice?

@dotMorten Events are different:

First one is not parsed (so is emitted even if frame is corrupted/unknown),
Second one is emitted only for valid, known frames.

So first allows logging raw frames to file or detecting "uknown frames". Even for known frames it is safer and more efficient to log raw data instead of rendering frames from already parsed data.
Or maybe we just missed other way to do it?

I think the better solution is to return an UnknownMessage for any message that wasn't a known message type (that also avoid having to distinguish between valid and invalid messages in two different events). I don't really see the point in returning invalid/incomplete frames.
What use are these? We wouldn't even know if they are the complete message, so raising a message received isn't correct.

Returning UnknownMessage for unknown message types is not relevant to our problem (but good idea anyway). We use NMEA stream for navigation, and in parallel we must record whole NMEA stream for post mission diagnostics and postprocessing.
So introducing UnknownMessage would still not allow us to log messages in its "almost raw form".

@kwesolowski Why wouldn't that be possible? The sample apps logs all the data messages as in the output window. Only thing is that currently it skips the unknown ones, but proposed solution would handle that.

@dotMorten Ok, you are right - i can use ToString to convert back to single line format. I still feel bad with such roundtrips (we would need to store raw data/message parts in UnknownFrame).
I do not completely understand why you do not like "separate events", because with them, anyone can use only data he subscribed for (and therefore we can even pass newline separated messages not conforming to NMEA standard etc).
I was also considering creation of Stream Proxy duplicating all data read from port to file - so I can go this way to ensure all data is captured without modification to NmeaParser.

Logged issue #14. This is a solution that fits better with my API design in mind


Add KyberInterface for docstring.

Codecov Report
Patch coverage: 92.30% and project coverage change: +0.73% :tada:

Comparison is base (9861826) 93.27% compared to head (ac36ad0) 94.01%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #11      +/-   ##
==========================================
+ Coverage   93.27%   94.01%   +0.73%
==========================================
  Files           8        8
  Lines         997     1003       +6
  Branches       82       84       +2
==========================================
+ Hits          930      943      +13
+ Misses         67       60       -7

Flag
Coverage Δ

unittests
94.01% <92.30%> (+0.73%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

mod.ts
100.00% <ø> (ø)

src/kyberBase.ts
96.08% <83.33%> (+1.05%)
:arrow_up:

src/kyber1024.ts
100.00% <100.00%> (ø)

src/kyber512.ts
100.00% <100.00%> (ø)

src/kyber768.ts
100.00% <100.00%> (ø)

src/utils.ts
78.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add link to true-up review documentation

Summary
The True Up Review panel in the system console had no information or instruction on how to perform a quarterly true-up review.
Figma: https://www.figma.com/file/1qWr4RtBjwQZyGQMT7z9Jp/True-Up-Review?node-id=503%3A38649&t=DdEYP8hX03OTYhdy-0
Ticket Link
MM-50030
Related Pull Requests
True-Up Review Docs
Screenshots

before
after

Release Note
NONE

E2E tests not automatically triggered, because the PR is not in a mergeable state. Please update the branch with the base branch and resolve outstanding conflicts.


Sample/Example Request

Please include an 'official' sample that shows features that are so common t many forms.
The forms sample here just shows forms with a TextField. We need a 'comprehensive' example FORMS sample, including the following features:
a) TextField
b) CheckBox
c) Yes/No button
d) Dropdown
e) ListView (select)
f) Validation
g) Data-Binding with Ajax
h) Button for POSTing (should at least show the serialized input values)
I am coming from a Google Polymer environment and I have spent days reading and trying some samples. The samples I have found on the internet typically show one feature and introduce problems of their own.  It will be helpful to show a an integrated sample (similar to the Polymer iron-form element sample.
I stumbled upon Flutter recently from a visualstudiomagazine.com article.  I like what I see so far but I am finding it much more difficult to learn that Polymer.
BTW -- I have been 'playing around with it for less than a week -- so please pardon my ignorance.

Have you looked at the Flutter Gallery sample?
https://github.com/flutter/flutter/tree/master/examples/flutter_gallery
Builds of the sample are also available on the Android and iOS app stores.

@Hixie

The FORMS example in the sample was very limited; I finally found a good example at https://codingwithjoe.com/


jps: Watch prosmarketplace.com

jps requests the watch of the watch_keyword prosmarketplace\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

prosmarketplace\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Nick in Charcoal HQ


Training (translation) with new lines / line breaks.

I would like to train the t2t for translation, but to preserve newlines/line breaks.
The problem is that, from what I see, the before/after files supplied to the t2t (for example translate_ende.py) are defined as one training example per line, so if I add a new line it will be treated as two examples/instances.
What is the right way to solve it?
Is there an option to define some kind of special token, and then convert newline into special-token during training, and then during inference do the same thing, plus, reverse conversion of special-token to newline? If this is the right way to solve it, then the special token should either be a very-rarely-used UTF-8 character, otherwise there is a risk that it will genuinely appear in some real text?
Another option is do some URLencoding for the texts, so newlines will be encoded to some no-newline string.
What do you think is the right approach that will not confuse the training quality of the t2t?

maybe use unprintable ascii characters? or encode them as \n in the data and have "\n" as a reserved token in a problem? that might work.
See additional_reserved_tokens in QuestionAndContext2TextProblem in text_problems.py
unprintable ascii characters should definitely work though, just replace \n when you read the file in data_generator from \0 to \31 or something?
Hope this helps?

I think it's a great idea.


Replace "Facebook, Inc." with new name "Meta Platforms, Inc."

Summary
This pull request is opened, to make use of new name "Meta Platforms, Inc.", over the previous name in Jest's website.
Test plan
Test plan might not be necessary for this tiny text change.

Oh, ok! That sounds cool!


Error: Unable to update job

Description
Error Message in Logfile:
[2018-11-15 21:53:04.7521] [I] [Core] .NET Core 4.6.27019.06 on Linux 4.15.0 #1
SMP Thu Aug 23 19:33:51 MSK 2018 [X64]
[2018-11-15 21:53:04.8335] [I] [Core] 43 coins loaded from /usr/src/miningcore/b
uild/coins.json
[2018-11-15 21:53:04.9642] [I] [ShareRecorder] Online
[2018-11-15 21:53:05.2499] [I] [Core] API Access to /api/admin restricted to 127
.0.0.1,::1,::ffff:<IP_ADDRESS>
[2018-11-15 21:53:05.2499] [I] [Core] API Access to /metrics restricted to 127.0
.0.1,::1,::ffff:<IP_ADDRESS>
[2018-11-15 21:53:05.3622] [I] [Core] API access limited to 5 requests per 1s, e
xcept from <IP_ADDRESS>, ::1, ::ffff:<IP_ADDRESS>
[2018-11-15 21:53:05.3863] [I] [Core] API Online @ <IP_ADDRESS>:4000
[2018-11-15 21:53:05.3867] [I] [Core] Prometheus Metrics Online @ <IP_ADDRESS>:4000/m
etrics
[2018-11-15 21:53:05.3867] [I] [Core] WebSocket notifications streaming @ 0.0.0.
0:4000/notifications
[2018-11-15 21:53:05.3867] [I] [Core] Payment processing is not enabled
[2018-11-15 21:53:05.3917] [I] [StatsRecorder] Online
[2018-11-15 21:53:05.4279] [I] [xmr001] Starting Pool ...
[2018-11-15 21:53:05.4457] [I] [xmr001] Starting Job Manager ...
[2018-11-15 21:53:05.6149] [I] [xmr001] All daemons online
[2018-11-15 21:53:05.6818] [I] [xmr001] All daemons synched with blockchain
[2018-11-15 21:53:05.7862] [W] [xmr001] Error(s) refreshing network stats: One o
r more errors occurred. (Unexpected character encountered while parsing value: <
. Path '', line 0, position 0.) (Code -500)
[2018-11-15 21:53:05.8256] [I] [xmr001] Job Manager Online
[2018-11-15 21:53:06.4932] [I] [xmr001] Detected new block 1705863 via RPC polli
ng
[2018-11-15 21:53:06.5023] [I] [xmr001] Broadcasting job
[2018-11-15 21:53:07.2829] [I] [xmr001] Pool Online
[2018-11-15 21:53:07.2880] [I] [xmr001]
Mining Pool:            xmr001
Coin Type:              XMR [XMR]
Network Connected:      Main
Detected Reward Type:   POW
Current Block Height:   1705863
Current Connect Peers:  0
Network Difficulty:<PHONE_NUMBER>2
Network Hash Rate:      0 KH/s
Stratum Port(s):        3032, 3033, 3034
Pool Fee:               1,5%
[2018-11-15 21:53:07.2925] [I] [xmr001] Stratum ports <IP_ADDRESS>:3032, <IP_ADDRESS>:3033
, <IP_ADDRESS>:3034 online
[2018-11-15 21:53:06.5023] [I] [xmr001] Broadcasting job
[2018-11-15 21:53:07.2829] [I] [xmr001] Pool Online
[2018-11-15 21:53:07.2880] [I] [xmr001]
Mining Pool:            xmr001
Coin Type:              XMR [XMR]
Network Connected:      Main
Detected Reward Type:   POW
Current Block Height:   1705863
Current Connect Peers:  0
Network Difficulty:<PHONE_NUMBER>2
Network Hash Rate:      0 KH/s
Stratum Port(s):        3032, 3033, 3034
Pool Fee:               1,5%
[2018-11-15 21:53:07.2925] [I] [xmr001] Stratum ports <IP_ADDRESS>:3032, <IP_ADDRESS>:3033, <IP_ADDRESS>:3034 online
[2018-11-15 21:53:15.4037] [I] [StatsRecorder] Updating hashrates for pool xmr001
[2018-11-15 21:53:15.5925] [I] [StatsRecorder] Performing Stats GC
[2018-11-15 21:53:15.6047] [I] [StatsRecorder] Stats GC complete
[2018-11-15 21:53:29.7950] [I] [xmr001] [0HLIB7HISS412] Connection from ::ffff:<IP_ADDRESS>:57742 accepted on port 3034
[2018-11-15 21:53:29.8692] [I] [xmr001] [0HLIB7HISS412] Authorized miner XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
[2018-11-15 21:53:34.5159] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:55:08.5525] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:55:25.4928] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:55:47.2510] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:55:55.1305] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:56:17.2512] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:56:40.3727] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:56:44.3511] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:56:59.7143] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:57:02.1700] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:57:03.3910] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:57:04.9062] [I] [xmr001] Detected new block 1705864 via RPC polling
[2018-11-15 21:57:04.9066] [I] [xmr001] Broadcasting job
[2018-11-15 21:57:04.9547] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 21:57:36.8123] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 21:57:43.6506] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:57:54.0101] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 21:58:15.6050] [I] [StatsRecorder] Updating hashrates for pool xmr001
[2018-11-15 21:58:15.6206] [I] [StatsRecorder] Performing Stats GC
[2018-11-15 21:58:15.6206] [I] [StatsRecorder] Stats GC complete
[2018-11-15 21:58:17.8970] [I] [xmr001] Detected new block 1705865 via RPC polling
[2018-11-15 21:58:17.8970] [I] [xmr001] Broadcasting job
[...]
[2018-11-15 22:11:38.8930] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 22:11:38.9350] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 22:11:43.5666] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 22:12:01.3203] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 22:12:04.0181] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 22:12:23.2950] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 22:12:51.1532] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 22:12:51.2241] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 22:12:51.5297] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
[2018-11-15 22:13:10.4230] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 22:13:10.5050] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 22:13:10.5460] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 22:13:10.5870] [W] [xmr001] Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.)  Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500
[2018-11-15 22:13:19.9308] [I] [xmr001] [0HLIB7HISS412] Share accepted: D=200000
Steps to Reproduce

Build from current master branch
start daemon
start mining

Version
current version from master branch
OS Ubuntu 18.04
Additional Information
my config:
root@h2810139:~# cat /usr/src/miningcore/build/config.json
{
"logging": {
"level": "info",
"enableConsoleLog": true,
"enableConsoleColors": true,
// Log file name (full log) - can be null in which case log events are written to console (stdout)
"logFile": "core.log",
// Log file name for API-requests - can be null in which case log events are written to either main logFile or console (stdout)
"apiLogFile": "api.log",
// Folder to store log file(s)
"logBaseDirectory": "/var/log/monero", // or c:\path\to\logs on Windows
// If enabled, separate log file will be stored for each pool as .log
// in the above specific folder.
"perPoolLogFile": false
},
"banning": {
// "integrated" or "iptables" (linux only - not yet implemented)
"manager": "integrated",
"banOnJunkReceive": false,
"banOnInvalidShares": false
},
"notifications": {
"enabled": true,
"email": {
"host": "1111.1111.1111.111",
"port": 25,
"user": "xxxxx",
"password": "xxxxxxxxx",
"fromAddress"<EMAIL_ADDRESS>"fromName": "POOL-Server"
},
"admin": {
"enabled": false,
"emailAddress"<EMAIL_ADDRESS>"notifyBlockFound": true
}
},
// Where to persist shares and blocks to
"persistence": {
// Persist to postgresql database
"postgres": {
"host": "<IP_ADDRESS>",
"port": 5432,
"user": "miningcore",
"password": "xxxxxx",
"database": "miningcore"
}
},
// Generate payouts for recorded shares and blocks
"paymentProcessing": {
"enabled": false,
// How often to process payouts, in milliseconds
"interval": 600,
// Path to a file used to backup shares under emergency conditions, such as
// database outage
"shareRecoveryFile": "/home/monero/recovered-shares.txt"
},
// API Settings
"api": {
"enabled": true,
// Binding address (Default: <IP_ADDRESS>)
"listenAddress": "<IP_ADDRESS>",
// Binding port (Default: 4000)
"port": 4000,
// IP address whitelist for requests to Prometheus Metrics (default <IP_ADDRESS>)
"metricsIpWhitelist": [],
// Limit rate of requests to API on a per-IP basis
"rateLimiting": {
"disabled": false, // disable rate-limiting all-together, be careful
// override default rate-limit rules, refer to https://github.com/stefanprodan/AspNetCoreRateLimit/wiki/IpRateLimitMiddleware#defining-rate-limit-rules
"rules": [
{
"Endpoint": "*",
"Period": "1s",
"Limit": 5
}
],
// List of IP addresses excempt from rate-limiting (default: none)
"ipWhitelist": []
}
},
"pools": [
{
// DON'T change the id after a production pool has begun collecting shares!
"id": "xmr001",
"enabled": true,
"coin": "monero",
// Address to where block rewards are given (pool wallet)
"address": "xxxxxxxxxxxxxxxxxxx",
// Block rewards go to the configured pool wallet address to later be paid out
// to miners, except for a percentage that can go to, for examples,
// pool operator(s) as pool fees or or to donations address. Addresses or hashed
// public keys can be used. Here is an example of rewards going to the main pool
// "op"
"rewardRecipients": [
{
// Pool wallet
"address": "xxxxxxxxxxxxxxxxxxxxxx",
"percentage": 1.5
}
],
// How often to poll RPC daemons for new blocks, in milliseconds
"blockRefreshInterval": 500,
// Some miner apps will consider the pool dead/offline if it doesn't receive
// anything new jobs for around a minute, so every time we broadcast jobs,
// set a timeout to rebroadcast in this many seconds unless we find a new job.
// Set to zero to disable. (Default: 0)
"jobRebroadcastTimeout": 10,
// Remove workers that haven't been in contact for this many seconds.
// Some attackers will create thousands of workers that use up all available
// socket connections, usually the workers are zombies and don't submit shares
// after connecting. This features detects those and disconnects them.
"clientConnectionTimeout": 600,
// If a worker is submitting a high threshold of invalid shares, we can
// temporarily ban their IP to reduce system/network load.
"banning": {
"enabled": false,
// How many seconds to ban worker for
"time": 600,
// What percent of invalid shares triggers ban
"invalidPercent": 50,
// Check invalid percent when this many shares have been submitted
"checkThreshold": 50
},
// Each pool can have as many ports for your miners to connect to as you wish.
// Each port can be configured to use its own pool difficulty and variable
// difficulty settings. 'varDiff' is optional and will only be used for the ports
// you configure it for.
"ports": {
"3032": {
"listenAddress": "<IP_ADDRESS>",
"difficulty": 7500,
"name": "CPU Mining",
"varDiff": {
"minDiff": 1000,
"maxDiff": null,
"targetTime": 15,
"retargetTime": 90,
"variancePercent": 30
}
},
"3033": {
"listenAddress": "<IP_ADDRESS>",
"difficulty": 25000,
"name": "GPU Mining",
"varDiff": {
"minDiff": 10000,
"maxDiff": null,
"targetTime": 15,
"retargetTime": 90,
"variancePercent": 30
}
},
"3034": {
"listenAddress": "<IP_ADDRESS>",
"difficulty": 200000,
"name": "High-End Multi GPU Mining",
"varDiff": {
"minDiff": 200000,
"maxDiff": null,
"targetTime": 15,
"retargetTime": 120,
"variancePercent": 30
}
}
},
// Recommended to have at least two daemon instances running in case one drops
// out-of-sync or offline. For redundancy, all instances will be polled for
// block/transaction updates and be used for submitting blocks. Creating a backup
// daemon involves spawning a daemon using the "-datadir=/backup" argument which
// creates a new daemon instance with it's own RPC config. For more info on this,
// visit: https:// en.bitcoin.it/wiki/Data_directory and
// https:// en.bitcoin.it/wiki/Running_bitcoind
"daemons": [
{
"host": "<IP_ADDRESS>",
"port": 18081,
"user": "xxx",
"password": "xxx",
// Enable streaming Block Notifications via ZeroMQ messaging from Bitcoin
// Family daemons. Using this is highly recommended. The value of this option
// is a string that should match the value of the -zmqpubhashblock parameter
// passed to the coin daemon. If you enable this, you should lower
// 'blockRefreshInterval' to 1000 or 0 to disable polling entirely.
//"zmqBlockNotifySocket": "tcp://<IP_ADDRESS>:15101",
                // Enable streaming Block Notifications via WebSocket messaging from Ethereum
                // family Parity daemons. Using this is highly recommended. The value of this
                // option is a string that should  match the value of the --ws-port parameter
                // passed to the parity coin daemon. When using --ws-port, you should also
                // specify --ws-interface all and
                // --jsonrpc-apis "eth,net,web3,personal,parity,parity_pubsub,rpc"
                // If you enable this, you should lower 'blockRefreshInterval' to 1000 or 0
                // to disable polling entirely.
                //"portWs": 18545,
            },
            {
                  "host": "<IP_ADDRESS>",
                  "port": 18082,
                  "user": "xxx",
                  "password": "xxx",
                  "category": "wallet"
            }
        ],
        // Generate payouts for recorded shares
        "paymentProcessing": {
                "enabled": true,
                "minimumPayment": 0.25,
            "minimumPaymentToPaymentId": 1.0,
                "payoutScheme": "PPLNS",
                "payoutSchemeConfig": {
                  "factor": 2.0
                }
        }
    }
]

}

After some days mining and without any solution of the error message
"Unable to update job. Daemon responded with: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) Code -500"
I find out, that the pending shares of my test-miner are over 1 GB.
Maybe mining is not really working, because miningcore can't update the jobs?
Could s.o. help to find out a solution?
kindly regards, tro18

push


Add missing event emit

I forgot to actually emit the event from the previous issue that added more events to the contracts for easier analysis for the watchtower. I also went ahead and updated the predicate root to the latest version which isn't expected to change unless a major issue is found during testing.

Codecov Report

:exclamation: No coverage uploaded for pull request base (code-freeze-beta4@dc1793e). Click here to learn what that means.
The diff coverage is n/a.

@@                  Coverage Diff                  @@
##             code-freeze-beta4       #34   +/-   ##
=====================================================
  Coverage                     ?   100.00%
=====================================================
  Files                        ?         7
  Lines                        ?       139
  Branches                     ?        40
=====================================================
  Hits                         ?       139
  Misses                       ?         0
  Partials                     ?         0

Flag
Coverage Δ

unittests
100.00% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Feature/htk to mrtk porting guide.md

Overview
htk to mrtk porting guide.mdの日本語化
Changes

Fixes: # .

Verification

This optional section is a place where you can detail the specific type of verification
you want from reviewers. For example, if you want reviewers to checkout the PR locally
and validate the functionality of specific scenarios, provide instructions
on the specific scenarios and what you want verified.
If there are specific areas of concern or question feel free to highlight them here so
that reviewers can watch out for those issues.
As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

「コンフィギュレーション」でも良さそう

Configuration -> コンフィギュレーション は、ちょっと直訳しすぎかなと思ってます。
ちょっとこの辺、ほかのメンバーの意見も聞きましょう。統一したほうがよいと思いますし。


Investigate interface for shareable one-off forms

Idea:
I want to send the happiness index form to a specific patient for them to fill out.
They should get a clickable URL that sends them straight to the form, which is pre-filled (or perhaps the state is pre-filled, but the fields are hidden), they then complete the form. The URL after this is no longer valid.
Are there libraries for this?

This should be possible to do with Next but as far as I can reason would require authentication (which I want to try and implement today). Is this workflow along what you have in mind?

Clinician goes to page to creates URL for subject (entering names, dob)
This generates a hash and stores it in the database
They then copy-paste the URL which contains this hash
The link is valid until submitted (or potentially a timeout), at which point the hash will be dropped from the database

I would call that "authentication" per-se, but yes, this is what I'm thinking about.


DOC changelog entry for #557

Pull Request Test Coverage Report for Build 3001

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.6%

Totals

Change from base Build 2999:
0.0%

Covered Lines:
585

Relevant Lines:
625

💛  - Coveralls


Distribute SComparator docs across all wrapper docs

... the way it's described in Python now.

@karenswry is there any progress with SComparator docs?

Would be cool to have it, TBH


[AutoPR automation/resource-manager] Updating PUT operation requirements for SourceControls and SourceControlSyncJobs, updating streams’ value property, and updating examples.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3580

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/1959


How to infer from jetson nano with a camera using deep stream

I followed the tlt flow provided by GitHub.
Docker pool nvcr.io/nvidia/tlt-streamanalytics:v2.0_py3
I was trained in the docker container above.
I trained on Tesla V100 SXM2 32G multi-GPU environment.
Of the cells provided by face-mask-detection.ipynb, all cells except tlt-evaluate and tlt-infer ran without error.
I would like to use the face mask detection model provided by GitHub on jetson nano for real-time inference via webcam.
What docker should i use
I ran tlt-convert but it still failed to create the .engine file.
How do I create .engine file?

@KOOKDONGHUN Did you solve this? If yes, could you please elaborate on the steps.