{"sedDocuments":[{"outputs":[{"dataSets":[{"status":"SUCCEEDED","id":"data_set_time"},{"status":"SUCCEEDED","id":"data_set_L"},{"status":"SUCCEEDED","id":"data_set_A"},{"status":"SUCCEEDED","id":"data_set_AL"},{"status":"SUCCEEDED","id":"data_set_ALL"},{"status":"SUCCEEDED","id":"data_set_B"},{"status":"SUCCEEDED","id":"data_set_BL"},{"status":"SUCCEEDED","id":"data_set_BLL"},{"status":"SUCCEEDED","id":"data_set_D"},{"status":"SUCCEEDED","id":"data_set_DL"},{"status":"SUCCEEDED","id":"data_set_DLL"},{"status":"SUCCEEDED","id":"data_set_I"},{"status":"SUCCEEDED","id":"data_set_IL"},{"status":"SUCCEEDED","id":"data_set_ILL"}],"duration":0.139902,"output":"","skipReason":null,"exception":null,"status":"SUCCEEDED","id":"report"},{"curves":[{"status":"SUCCEEDED","id":"curve_B"},{"status":"SUCCEEDED","id":"curve_BL"},{"status":"SUCCEEDED","id":"curve_ALL"},{"status":"SUCCEEDED","id":"curve_ILL"},{"status":"SUCCEEDED","id":"curve_DLL"}],"duration":0.568779,"output":"/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: IllogicalVizWarning: \u001b[33mA title could not be inferred for the Y axis because the Y data generators have inconsistent names.\u001b[0m\r\n  warnings.warn(termcolor.colored(message, Colors.warning.value), category)\r\n","skipReason":null,"exception":null,"status":"SUCCEEDED","id":"Figure_4b"}],"tasks":[{"simulatorDetails":[{"value":"pysces.PyscesModel.Simulate","key":"method"},{"value":{"lsoda_atol":1e-12,"lsoda_h0":0,"lsoda_hmax":0,"lsoda_hmin":0,"lsoda_mesg":1,"lsoda_mxordn":12,"lsoda_mxords":5,"lsoda_mxstep":0,"lsoda_rtol":1e-7},"key":"arguments"}],"algorithm":"KISAO_0000088","duration":0.238179,"output":"/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: \u001b[33m- Variable `var_BL` may be invalid.\r\n  - XPath could not be validated.\r\n- Variable `var_DL` may be invalid.\r\n  - XPath could not be validated.\r\n- Variable `var_I` may be invalid.\r\n  - XPath could not be validated.\r\n- Variable `var_ALL` may be invalid.\r\n  - XPath could not be validated.\r\n- Variable `var_IL` may be invalid.\r\n  - XPath could not be validated.\r\n- Variable `var_AL` may be invalid.\r\n  - XPath could not be validated.\r\n- Variable `var_D` may be invalid.\r\n  - XPath could not be validated.\r\n- Variable `var_ILL` may be invalid.\r\n  - XPath could not be validated.\r\n- Variable `var_A` may be invalid.\r\n  - XPath could not be validated.\r\n- Variable `var_L` may be invalid.\r\n  - XPath could not be validated.\r\n- Variable `var_DLL` may be invalid.\r\n  - XPath could not be validated.\r\n- Variable `var_B` may be invalid.\r\n  - XPath could not be validated.\r\n- Variable `var_BLL` may be invalid.\r\n  - XPath could not be validated.\u001b[0m\r\n  warnings.warn(termcolor.colored(message, Colors.warning.value), category)\r\n/usr/local/lib/python3.9/site-packages/scipy/integrate/odepack.py:250: ODEintWarning: Integration successful.\r\n  warnings.warn(warning_msg, ODEintWarning)\r\n","skipReason":null,"exception":null,"status":"SUCCEEDED","id":"BIOMD0000000002_task"}],"duration":1.081471,"output":"Archive contains 1 SED-ML documents with 1 models, 1 simulations, 1 tasks, 1 reports, and 1 plots:\r\n  BIOMD0000000002_sim.sedml:\r\n    Tasks (1):\r\n      BIOMD0000000002_task\r\n    Reports (1):\r\n      report: 14 data sets\r\n    Plots (1):\r\n      Figure_4b: 5 curves\r\n\r\nExecuting SED-ML file 1: BIOMD0000000002_sim.sedml ...\r\n  Found 1 tasks and 2 outputs:\r\n    Tasks:\r\n      `BIOMD0000000002_task`\r\n    Outputs:\r\n      `Figure_4b`\r\n      `report`\r\n  Executing task 1: `BIOMD0000000002_task`\r\n    Executing simulation ...Check SBML support is at action level 2\r\nSBML file is L2V4\r\nINFO: Rescaling compartment with size 1e-16 to 1.0\r\nInfo: single compartment model: locating \"React0\" in default compartment\r\nInfo: single compartment model: locating \"React1\" in default compartment\r\nInfo: single compartment model: locating \"React2\" in default compartment\r\nInfo: single compartment model: locating \"React3\" in default compartment\r\nInfo: single compartment model: locating \"React4\" in default compartment\r\nInfo: single compartment model: locating \"React5\" in default compartment\r\nInfo: single compartment model: locating \"React6\" in default compartment\r\nInfo: single compartment model: locating \"React7\" in default compartment\r\nInfo: single compartment model: locating \"React8\" in default compartment\r\nInfo: single compartment model: locating \"React9\" in default compartment\r\nInfo: single compartment model: locating \"React10\" in default compartment\r\nInfo: single compartment model: locating \"React11\" in default compartment\r\nInfo: single compartment model: locating \"React12\" in default compartment\r\nInfo: single compartment model: locating \"React13\" in default compartment\r\nInfo: single compartment model: locating \"React14\" in default compartment\r\nInfo: single compartment model: locating \"React15\" in default compartment\r\nInfo: single compartment model: locating \"React16\" in default compartment\r\nWriting file: /tmp/tmp3m_ewjgm.psc\r\n\r\nSBML2PSC\r\nin : /tmp/tmp9ksmv8ux.xml\r\nout: /tmp/tmp3m_ewjgm.psc\r\nUsing model directory: /home/FCAM/crbmapi/Pysces/psc\r\n/tmp/tmp3m_ewjgm.psc loading ..... \r\nParsing file: /tmp/tmp3m_ewjgm.psc\r\nInfo: No reagents have been fixed\r\n \r\nCalculating L matrix . . . . . . .  done.\r\nCalculating K matrix . . . . . . . . . . .  done.\r\n \r\nLSODA time for 1001 points: 0.11375236511230469\r\n \u001b[34msucceeded\u001b[0m\r\n    Generating 2 outputs ...\r\n      Generating output 1: `report` ... \u001b[34msucceeded\u001b[0m\r\n      Generating output 2: `Figure_4b` ...","skipReason":null,"exception":null,"status":"SUCCEEDED","location":"BIOMD0000000002_sim.sedml"}],"duration":1.38336,"output":"\u001b[0;36mThank you for using runBioSimulations!\u001b[0m\n\n\u001b[0;36m================================================ Loading Singularity ================================================\u001b[0m\n\n\u001b[0;36m============================================ Downloading COMBINE archive ============================================\u001b[0m\n  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r100   139  100   139    0     0    456      0 --:--:-- --:--:-- --:--:--   457\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r100  184k  100  184k    0     0   427k      0 --:--:-- --:--:-- --:--:-- 2559k\n\n\u001b[0;36m============================================= Executing COMBINE archive =============================================\u001b[0m\nINFO:    Using cached SIF image\nCould not find GLIMDA.\nlibtk8.6.so: cannot open shared object file: No such file or directory\r\n\r\nPySCeS defaults to matplotlib's TKagg backend if not specified                          in the user configuration file, set \"matplotlib_backend = <backend>\" \r\nMatplotlib interface loaded (pysces.plt.m)\r\nPitcon routines available\r\nNLEQ2 routines available\r\nSBML support available\r\nYou are using NumPy (1.21.4) with SciPy (1.7.3)\r\nAssimulo CVode available\r\nRateChar is available\r\nParallel scanner is available\r\n\r\nPySCeS environment\r\n******************\r\npysces.model_dir = /home/FCAM/crbmapi/Pysces/psc\r\npysces.output_dir = /home/FCAM/crbmapi/Pysces\r\n\r\n\r\n***********************************************************************\r\n* Welcome to PySCeS (1.0.0) - Python Simulator for Cellular Systems   *\r\n*                http://pysces.sourceforge.net                        *\r\n* Copyright(C) B.G. Olivier, J.M. Rohwer, J.-H.S. Hofmeyr, 2004-2022  *\r\n* Triple-J Group for Molecular Cell Physiology                        *\r\n* Stellenbosch University, ZA and VU University Amsterdam, NL         *\r\n* PySCeS is distributed under the PySCeS (BSD style) licence, see     *\r\n* LICENCE.txt (supplied with this release) for details                *\r\n* Please cite PySCeS with: doi:10.1093/bioinformatics/bti046          *\r\n***********************************************************************\r\n/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: \u001b[33mThe SED document is potentially incorrect.\r\n  - Model `BIOMD0000000002` may be invalid.\r\n    - The model file `BIOMD0000000002_url.xml` may be invalid.\r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_0 * B * L - kr_0 * BL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_1 * BL * L - kr_1 * BLL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_2 * BLL - kr_2 * ALL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_3 * A * L - kr_3 * AL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_4 * AL * L - kr_4 * ALL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_5 * B - kr_5 * A)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_6 * BL - kr_6 * AL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_7 * I * L - kr_7 * IL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_8 * IL * L - kr_8 * ILL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_9 * A - kr_9 * I)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_10 * AL - kr_10 * IL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_11 * ALL - kr_11 * ILL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_12 * D * L - kr_12 * DL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_13 * DL * L - kr_13 * DLL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_14 * I - kr_14 * D)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_15 * IL - kr_15 * DL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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. \r\n         The units of the <kineticLaw> <math> expression 'comp1 * (kf_16 * ILL - kr_16 * DLL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_0' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_0' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_1' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_1' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_2' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_2' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_3' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_3' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_4' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_4' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_5' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_5' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_6' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_6' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_7' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_7' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_8' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_8' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_9' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_9' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_10' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_10' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_11' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_11' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_12' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_12' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_13' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_13' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_14' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_14' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_15' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_15' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kf_16' does not have a 'units' attribute.\r\n        \r\n      - 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.\r\n         The <parameter> with the id 'kr_16' does not have a 'units' attribute.\r\n        \r\n    - The changes of the model may be invalid.\r\n      - Change 1 may be invalid.\r\n        - XPath could not be validated.\r\n  - Data generator `data_generator_BLL` may be invalid.\r\n    - Variable `var_BLL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_IL` may be invalid.\r\n    - Variable `var_IL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_AL` may be invalid.\r\n    - Variable `var_AL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_A` may be invalid.\r\n    - Variable `var_A` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_BL` may be invalid.\r\n    - Variable `var_BL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_B` may be invalid.\r\n    - Variable `var_B` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_DLL` may be invalid.\r\n    - Variable `var_DLL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_D` may be invalid.\r\n    - Variable `var_D` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_ILL` may be invalid.\r\n    - Variable `var_ILL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_DL` may be invalid.\r\n    - Variable `var_DL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_I` may be invalid.\r\n    - Variable `var_I` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_ALL` may be invalid.\r\n    - Variable `var_ALL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_L` may be invalid.\r\n    - Variable `var_L` may be invalid.\r\n      - XPath could not be validated.\u001b[0m\r\n  warnings.warn(termcolor.colored(message, Colors.warning.value), category)\r\n/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: \u001b[33mThe COMBINE/OMEX archive may be invalid.\r\n  - The SED-ML file at location `./BIOMD0000000002_sim.sedml` may be invalid.\r\n    - Model `BIOMD0000000002` may be invalid.\r\n      - The model file `BIOMD0000000002_url.xml` may be invalid.\r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_0 * B * L - kr_0 * BL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_1 * BL * L - kr_1 * BLL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_2 * BLL - kr_2 * ALL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_3 * A * L - kr_3 * AL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_4 * AL * L - kr_4 * ALL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_5 * B - kr_5 * A)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_6 * BL - kr_6 * AL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_7 * I * L - kr_7 * IL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_8 * IL * L - kr_8 * ILL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_9 * A - kr_9 * I)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_10 * AL - kr_10 * IL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_11 * ALL - kr_11 * ILL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_12 * D * L - kr_12 * DL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_13 * DL * L - kr_13 * DLL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_14 * I - kr_14 * D)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_15 * IL - kr_15 * DL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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. \r\n           The units of the <kineticLaw> <math> expression 'comp1 * (kf_16 * ILL - kr_16 * DLL)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_0' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_0' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_1' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_1' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_2' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_2' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_3' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_3' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_4' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_4' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_5' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_5' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_6' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_6' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_7' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_7' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_8' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_8' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_9' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_9' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_10' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_10' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_11' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_11' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_12' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_12' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_13' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_13' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_14' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_14' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_15' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_15' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kf_16' does not have a 'units' attribute.\r\n          \r\n        - 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.\r\n           The <parameter> with the id 'kr_16' does not have a 'units' attribute.\r\n          \r\n      - The changes of the model may be invalid.\r\n        - Change 1 may be invalid.\r\n          - XPath could not be validated.\r\n    - Data generator `data_generator_BLL` may be invalid.\r\n      - Variable `var_BLL` may be invalid.\r\n        - XPath could not be validated.\r\n    - Data generator `data_generator_IL` may be invalid.\r\n      - Variable `var_IL` may be invalid.\r\n        - XPath could not be validated.\r\n    - Data generator `data_generator_AL` may be invalid.\r\n      - Variable `var_AL` may be invalid.\r\n        - XPath could not be validated.\r\n    - Data generator `data_generator_A` may be invalid.\r\n      - Variable `var_A` may be invalid.\r\n        - XPath could not be validated.\r\n    - Data generator `data_generator_BL` may be invalid.\r\n      - Variable `var_BL` may be invalid.\r\n        - XPath could not be validated.\r\n    - Data generator `data_generator_B` may be invalid.\r\n      - Variable `var_B` may be invalid.\r\n        - XPath could not be validated.\r\n    - Data generator `data_generator_DLL` may be invalid.\r\n      - Variable `var_DLL` may be invalid.\r\n        - XPath could not be validated.\r\n    - Data generator `data_generator_D` may be invalid.\r\n      - Variable `var_D` may be invalid.\r\n        - XPath could not be validated.\r\n    - Data generator `data_generator_ILL` may be invalid.\r\n      - Variable `var_ILL` may be invalid.\r\n        - XPath could not be validated.\r\n    - Data generator `data_generator_DL` may be invalid.\r\n      - Variable `var_DL` may be invalid.\r\n        - XPath could not be validated.\r\n    - Data generator `data_generator_I` may be invalid.\r\n      - Variable `var_I` may be invalid.\r\n        - XPath could not be validated.\r\n    - Data generator `data_generator_ALL` may be invalid.\r\n      - Variable `var_ALL` may be invalid.\r\n        - XPath could not be validated.\r\n    - Data generator `data_generator_L` may be invalid.\r\n      - Variable `var_L` may be invalid.\r\n        - XPath could not be validated.\u001b[0m\r\n  warnings.warn(termcolor.colored(message, Colors.warning.value), category)\r\n/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: \u001b[33mThe SED document is potentially incorrect.\r\n  - Model `BIOMD0000000002` may be invalid.\r\n    - The changes of the model may be invalid.\r\n      - Change 1 may be invalid.\r\n        - XPath could not be validated.\r\n  - Data generator `data_generator_BLL` may be invalid.\r\n    - Variable `var_BLL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_IL` may be invalid.\r\n    - Variable `var_IL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_AL` may be invalid.\r\n    - Variable `var_AL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_A` may be invalid.\r\n    - Variable `var_A` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_BL` may be invalid.\r\n    - Variable `var_BL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_B` may be invalid.\r\n    - Variable `var_B` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_DLL` may be invalid.\r\n    - Variable `var_DLL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_D` may be invalid.\r\n    - Variable `var_D` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_ILL` may be invalid.\r\n    - Variable `var_ILL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_DL` may be invalid.\r\n    - Variable `var_DL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_I` may be invalid.\r\n    - Variable `var_I` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_ALL` may be invalid.\r\n    - Variable `var_ALL` may be invalid.\r\n      - XPath could not be validated.\r\n  - Data generator `data_generator_L` may be invalid.\r\n    - Variable `var_L` may be invalid.\r\n      - XPath could not be validated.\u001b[0m\r\n  warnings.warn(termcolor.colored(message, Colors.warning.value), category)\r\n \u001b[34msucceeded\u001b[0m\n\n  Executed 1 tasks and 2 outputs:\n    Tasks:\n      Succeeded: 1\n      Skipped: 0\n      Failed: 0\n    Outputs:\n      Succeeded: 2\n      Skipped: 0\n      Failed: 0\n\nBundling outputs ...\nCleaning up ...\n\n============= SUMMARY =============\nExecuted 1 SED documents:\n  SED documents (1):\n    Succeeded: 1\n    Skipped: 0\n    Failed: 0\n  Tasks (1):\n    Succeeded: 1\n    Skipped: 0\n    Failed: 0\n  Outputs (2):\n    Succeeded: 2\n    Skipped: 0\n    Failed: 0\n\n\n\u001b[0;36m=================================================== Saving results ==================================================\u001b[0m\ncreating group /BIOMD0000000002_sim.sedml\ncreating dataset /BIOMD0000000002_sim.sedml/Figure_4b, shape: (6, 1001), type: float64\ndataset created, uuid: d-c2cec81a-92865efd-095b-a3a650-6435c9, chunk_size: (6, 1001)\ncreating dataset /BIOMD0000000002_sim.sedml/report, shape: (14, 1001), type: float64\ndataset created, uuid: d-c2cec81a-92865efd-b436-80e7c8-0a3ef1, chunk_size: (14, 1001)\ncreating attribute combineArchiveLocation in /BIOMD0000000002_sim.sedml\ncreating attribute uri in /BIOMD0000000002_sim.sedml\ncreating attribute _type in /BIOMD0000000002_sim.sedml/Figure_4b\ncreating attribute sedmlDataSetDataTypes in /BIOMD0000000002_sim.sedml/Figure_4b\ncreating attribute sedmlDataSetIds in /BIOMD0000000002_sim.sedml/Figure_4b\ncreating attribute sedmlDataSetLabels in /BIOMD0000000002_sim.sedml/Figure_4b\ncreating attribute sedmlDataSetNames in /BIOMD0000000002_sim.sedml/Figure_4b\ncreating attribute sedmlDataSetShapes in /BIOMD0000000002_sim.sedml/Figure_4b\ncreating attribute sedmlId in /BIOMD0000000002_sim.sedml/Figure_4b\ncreating attribute sedmlName in /BIOMD0000000002_sim.sedml/Figure_4b\ncreating attribute uri in /BIOMD0000000002_sim.sedml/Figure_4b\ncreating attribute _type in /BIOMD0000000002_sim.sedml/report\ncreating attribute sedmlDataSetDataTypes in /BIOMD0000000002_sim.sedml/report\ncreating attribute sedmlDataSetIds in /BIOMD0000000002_sim.sedml/report\ncreating attribute sedmlDataSetLabels in /BIOMD0000000002_sim.sedml/report\ncreating attribute sedmlDataSetNames in /BIOMD0000000002_sim.sedml/report\ncreating attribute sedmlDataSetShapes in /BIOMD0000000002_sim.sedml/report\ncreating attribute sedmlId in /BIOMD0000000002_sim.sedml/report\ncreating attribute uri in /BIOMD0000000002_sim.sedml/report\ncreate_links: /\ngot link: BIOMD0000000002_sim.sedml\ncreate_links: /BIOMD0000000002_sim.sedml\ngot link: Figure_4b\ngot link: report\nwrite_dataset src: /BIOMD0000000002_sim.sedml/Figure_4b to tgt: /BIOMD0000000002_sim.sedml/Figure_4b, shape: (6, 1001), type: float64\niterating over chunks for /BIOMD0000000002_sim.sedml/Figure_4b\nwriting dataset data for slice: (slice(0, 6, 1), slice(0, 1001, 1))\ndone with dataload for /BIOMD0000000002_sim.sedml/Figure_4b\nwrite_dataset src: /BIOMD0000000002_sim.sedml/report to tgt: /BIOMD0000000002_sim.sedml/report, shape: (14, 1001), type: float64\niterating over chunks for /BIOMD0000000002_sim.sedml/report\nwriting dataset data for slice: (slice(0, 14, 1), slice(0, 1001, 1))\ndone with dataload for /BIOMD0000000002_sim.sedml/report\nload_file complete\nFile outputs/reports.h5 uploaded to domain: /results/61fea4988c1e3dc95a79801c\n\n\u001b[0;36m================================================== Zipping outputs ==================================================\u001b[0m\n  adding: outputs/ (stored 0%)\n  adding: outputs/log.yml (deflated 92%)\n  adding: outputs/BIOMD0000000002_sim.sedml/ (stored 0%)\n  adding: outputs/BIOMD0000000002_sim.sedml/Figure_4b.pdf (deflated 29%)\n  adding: outputs/reports.h5 (deflated 15%)\n  adding: rawLog.txt (deflated 94%)\n\n\u001b[0;36m=================================================== Saving outputs ==================================================\u001b[0m\nCompleted 22.6 KiB/254.6 KiB (251.8 KiB/s) with 5 file(s) remaining\rupload: ./_pystmptmp3mewjgm_parsetab.py to s3://files.biosimulations.org/simulations/61fea4988c1e3dc95a79801c/_pystmptmp3mewjgm_parsetab.py\nCompleted 22.6 KiB/254.6 KiB (251.8 KiB/s) with 4 file(s) remaining\rCompleted 74.5 KiB/254.6 KiB (574.8 KiB/s) with 4 file(s) remaining\rupload: ./rawLog.txt to s3://files.biosimulations.org/simulations/61fea4988c1e3dc95a79801c/rawLog.txt\nCompleted 74.5 KiB/254.6 KiB (574.8 KiB/s) with 3 file(s) remaining\rCompleted 84.5 KiB/254.6 KiB (520.3 KiB/s) with 3 file(s) remaining\rupload: outputs/plots.zip to s3://files.biosimulations.org/simulations/61fea4988c1e3dc95a79801c/outputs/plots.zip\nCompleted 84.5 KiB/254.6 KiB (520.3 KiB/s) with 2 file(s) remaining\rCompleted 98.9 KiB/254.6 KiB (545.6 KiB/s) with 2 file(s) remaining\rupload: outputs/BIOMD0000000002_sim.sedml/Figure_4b.pdf to s3://files.biosimulations.org/simulations/61fea4988c1e3dc95a79801c/outputs/BIOMD0000000002_sim.sedml/Figure_4b.pdf\nCompleted 98.9 KiB/254.6 KiB (545.6 KiB/s) with 1 file(s) remaining\rCompleted 254.6 KiB/254.6 KiB (1.3 MiB/s) with 1 file(s) remaining \rupload: ./output.zip to s3://files.biosimulations.org/simulations/61fea4988c1e3dc95a79801c/output.zip\nCompleted 161.0 KiB/161.0 KiB (1.8 MiB/s) with 1 file(s) remaining\rupload: outputs/reports.h5 to s3://files.biosimulations.org/simulations/61fea4988c1e3dc95a79801c/outputs/reports.h5\nCompleted 57.5 KiB/57.5 KiB (388.9 KiB/s) with 1 file(s) remaining\rupload: outputs/log.yml to s3://files.biosimulations.org/simulations/61fea4988c1e3dc95a79801c/outputs/log.yml\n\n\u001b[0;36m=========================================== Post-processing simulation run ==========================================\u001b[0m\n\n\u001b[0;32mPost the SED-ML file to the API.....Succeeded\nProcess the SED-ML file in the combine archive.....Succeeded\nProcess and upload the outputs of the simulation run.....Succeeded\nPost thumbnails to the API.....Succeeded\nCreate thumbnails from the images specified in the manifest.....Succeeded\nRead the manifest and post the files to the API.....Succeeded\nProcess the manifest file in the combine archive.....Succeeded\nExtract the files in the combine archive.....Succeeded\nPost the Metadata to the API.....Succeeded\nProcess the Metadata in the combine archive.....Succeeded\nPost the logs to the API.....Succeeded\nRetrieve the logs of the simulation run.....Succeeded\u001b[0m\n\u001b[0;36m================================ Run complete. Thank you for using runBioSimulations! ===============================\u001b[0m","skipReason":null,"exception":null,"status":"SUCCEEDED"}