[0;36mThank you for using runBioSimulations![0m

[0;36m================================================ Loading Singularity ================================================[0m

[0;36m============================================ Downloading COMBINE archive ============================================[0m
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   139  100   139    0     0    518      0 --:--:-- --:--:-- --:--:--   516

100 92196  100 92196    0     0   234k      0 --:--:-- --:--:-- --:--:--  234k

[0;36m============================================= Executing COMBINE archive =============================================[0m
INFO:    Using cached SIF image
/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: [33mThe SED document is potentially incorrect.
  - Model `model` may be invalid.
    - The model file `BIOMD0000000012_url.xml` may be invalid.
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <assignmentRule> <math> expression 'tau_mRNA / log(2)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <assignmentRule> <math> expression 'tau_mRNA / tau_prot' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <assignmentRule> <math> expression 'eff / t_ave' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <assignmentRule> <math> expression '(ps_a - ps_0) * 60' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <assignmentRule> <math> expression 'ps_0 * 60' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <assignmentRule> <math> expression 'log(2) / tau_prot' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <assignmentRule> <math> expression 'log(2) / tau_mRNA' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <assignmentRule> <math> expression 'a_tr * eff * tau_prot / (log(2) * KM)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <assignmentRule> <math> expression 'a0_tr * eff * tau_prot / (log(2) * KM)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <kineticLaw> <math> expression 'kd_mRNA * X' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <kineticLaw> <math> expression 'kd_mRNA * Y' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <kineticLaw> <math> expression 'kd_mRNA * Z' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <kineticLaw> <math> expression 'k_tl * X' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <kineticLaw> <math> expression 'k_tl * Y' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <kineticLaw> <math> expression 'k_tl * Z' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <kineticLaw> <math> expression 'kd_prot * PX' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <kineticLaw> <math> expression 'kd_prot * PY' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <kineticLaw> <math> expression 'kd_prot * PZ' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <kineticLaw> <math> expression 'a0_tr + a_tr * pow(KM, n) / (pow(KM, n) + pow(PZ, n))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <kineticLaw> <math> expression 'a0_tr + a_tr * pow(KM, n) / (pow(KM, n) + pow(PX, n))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
         The units of the <kineticLaw> <math> expression 'a0_tr + a_tr * pow(KM, n) / (pow(KM, n) + pow(PY, n))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'beta' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'alpha0' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'alpha' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'eff' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'n' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'KM' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'tau_mRNA' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'tau_prot' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 't_ave' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'kd_mRNA' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'kd_prot' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'k_tl' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'a_tr' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'ps_a' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'ps_0' does not have a 'units' attribute.
        
      - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
         The <parameter> with the id 'a0_tr' does not have a 'units' attribute.
        
    - The changes of the model may be invalid.
      - Change 1 may be invalid.
        - XPath could not be validated.
  - Data generator `data_gen_px` may be invalid.
    - Variable `var_px` may be invalid.
      - XPath could not be validated.
  - Data generator `data_gen_py` may be invalid.
    - Variable `var_py` may be invalid.
      - XPath could not be validated.
  - Data generator `data_gen_pz` may be invalid.
    - Variable `var_pz` may be invalid.
      - XPath could not be validated.
  - Data generator `data_gen_x` may be invalid.
    - Variable `var_x` may be invalid.
      - XPath could not be validated.
  - Data generator `data_gen_y` may be invalid.
    - Variable `var_y` may be invalid.
      - XPath could not be validated.
  - Data generator `data_gen_z` may be invalid.
    - Variable `var_z` may be invalid.
      - XPath could not be validated.[0m
  warnings.warn(termcolor.colored(message, Colors.warning.value), category)
/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: [33mThe COMBINE/OMEX archive may be invalid.
  - The SED-ML file at location `simulation.sedml` may be invalid.
    - Model `model` may be invalid.
      - The model file `BIOMD0000000012_url.xml` may be invalid.
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <assignmentRule> <math> expression 'tau_mRNA / log(2)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <assignmentRule> <math> expression 'tau_mRNA / tau_prot' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <assignmentRule> <math> expression 'eff / t_ave' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <assignmentRule> <math> expression '(ps_a - ps_0) * 60' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <assignmentRule> <math> expression 'ps_0 * 60' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <assignmentRule> <math> expression 'log(2) / tau_prot' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <assignmentRule> <math> expression 'log(2) / tau_mRNA' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <assignmentRule> <math> expression 'a_tr * eff * tau_prot / (log(2) * KM)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <assignmentRule> <math> expression 'a0_tr * eff * tau_prot / (log(2) * KM)' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <kineticLaw> <math> expression 'kd_mRNA * X' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <kineticLaw> <math> expression 'kd_mRNA * Y' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <kineticLaw> <math> expression 'kd_mRNA * Z' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <kineticLaw> <math> expression 'k_tl * X' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <kineticLaw> <math> expression 'k_tl * Y' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <kineticLaw> <math> expression 'k_tl * Z' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <kineticLaw> <math> expression 'kd_prot * PX' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <kineticLaw> <math> expression 'kd_prot * PY' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <kineticLaw> <math> expression 'kd_prot * PZ' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <kineticLaw> <math> expression 'a0_tr + a_tr * pow(KM, n) / (pow(KM, n) + pow(PZ, n))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <kineticLaw> <math> expression 'a0_tr + a_tr * pow(KM, n) / (pow(KM, n) + pow(PX, n))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - In situations where a mathematical expression contains literal numbers or parameters whose units have not been declared, it is not possible to verify accurately the consistency of the units in the expression. 
           The units of the <kineticLaw> <math> expression 'a0_tr + a_tr * pow(KM, n) / (pow(KM, n) + pow(PY, n))' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'beta' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'alpha0' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'alpha' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'eff' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'n' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'KM' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'tau_mRNA' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'tau_prot' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 't_ave' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'kd_mRNA' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'kd_prot' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'k_tl' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'a_tr' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'ps_a' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'ps_0' does not have a 'units' attribute.
          
        - As a principle of best modeling practice, the units of a <parameter> should be declared rather than be left undefined. Doing so improves the ability of software to check the consistency of units and helps make it easier to detect potential errors in models.
           The <parameter> with the id 'a0_tr' does not have a 'units' attribute.
          
      - The changes of the model may be invalid.
        - Change 1 may be invalid.
          - XPath could not be validated.
    - Data generator `data_gen_px` may be invalid.
      - Variable `var_px` may be invalid.
        - XPath could not be validated.
    - Data generator `data_gen_py` may be invalid.
      - Variable `var_py` may be invalid.
        - XPath could not be validated.
    - Data generator `data_gen_pz` may be invalid.
      - Variable `var_pz` may be invalid.
        - XPath could not be validated.
    - Data generator `data_gen_x` may be invalid.
      - Variable `var_x` may be invalid.
        - XPath could not be validated.
    - Data generator `data_gen_y` may be invalid.
      - Variable `var_y` may be invalid.
        - XPath could not be validated.
    - Data generator `data_gen_z` may be invalid.
      - Variable `var_z` may be invalid.
        - XPath could not be validated.[0m
  warnings.warn(termcolor.colored(message, Colors.warning.value), category)
/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: [33mThe SED document is potentially incorrect.
  - Model `model` may be invalid.
    - The changes of the model may be invalid.
      - Change 1 may be invalid.
        - XPath could not be validated.
  - Data generator `data_gen_px` may be invalid.
    - Variable `var_px` may be invalid.
      - XPath could not be validated.
  - Data generator `data_gen_py` may be invalid.
    - Variable `var_py` may be invalid.
      - XPath could not be validated.
  - Data generator `data_gen_pz` may be invalid.
    - Variable `var_pz` may be invalid.
      - XPath could not be validated.
  - Data generator `data_gen_x` may be invalid.
    - Variable `var_x` may be invalid.
      - XPath could not be validated.
  - Data generator `data_gen_y` may be invalid.
    - Variable `var_y` may be invalid.
      - XPath could not be validated.
  - Data generator `data_gen_z` may be invalid.
    - Variable `var_z` may be invalid.
      - XPath could not be validated.[0m
  warnings.warn(termcolor.colored(message, Colors.warning.value), category)
 [34msucceeded[0m

  Executed 1 tasks and 2 outputs:
    Tasks:
      Succeeded: 1
      Skipped: 0
      Failed: 0
    Outputs:
      Succeeded: 2
      Skipped: 0
      Failed: 0

Bundling outputs ...
Cleaning up ...

============= SUMMARY =============
Executed 1 SED documents:
  SED documents (1):
    Succeeded: 1
    Skipped: 0
    Failed: 0
  Tasks (1):
    Succeeded: 1
    Skipped: 0
    Failed: 0
  Outputs (2):
    Succeeded: 2
    Skipped: 0
    Failed: 0


[0;36m=================================================== Saving results ==================================================[0m
creating group /simulation.sedml
creating dataset /simulation.sedml/Figure_1c, shape: (4, 601), type: float64
dataset created, uuid: d-88aeba64-00d1cf33-cbdf-af6436-5ae770, chunk_size: (4, 601)
creating dataset /simulation.sedml/report, shape: (7, 601), type: float64
dataset created, uuid: d-88aeba64-00d1cf33-0597-085d28-37c954, chunk_size: (7, 601)
creating attribute combineArchiveLocation in /simulation.sedml
creating attribute uri in /simulation.sedml
creating attribute _type in /simulation.sedml/Figure_1c
creating attribute sedmlDataSetDataTypes in /simulation.sedml/Figure_1c
creating attribute sedmlDataSetIds in /simulation.sedml/Figure_1c
creating attribute sedmlDataSetLabels in /simulation.sedml/Figure_1c
creating attribute sedmlDataSetNames in /simulation.sedml/Figure_1c
creating attribute sedmlDataSetShapes in /simulation.sedml/Figure_1c
creating attribute sedmlId in /simulation.sedml/Figure_1c
creating attribute sedmlName in /simulation.sedml/Figure_1c
creating attribute uri in /simulation.sedml/Figure_1c
creating attribute _type in /simulation.sedml/report
creating attribute sedmlDataSetDataTypes in /simulation.sedml/report
creating attribute sedmlDataSetIds in /simulation.sedml/report
creating attribute sedmlDataSetLabels in /simulation.sedml/report
creating attribute sedmlDataSetNames in /simulation.sedml/report
creating attribute sedmlDataSetShapes in /simulation.sedml/report
creating attribute sedmlId in /simulation.sedml/report
creating attribute sedmlName in /simulation.sedml/report
creating attribute uri in /simulation.sedml/report
create_links: /
got link: simulation.sedml
create_links: /simulation.sedml
got link: Figure_1c
got link: report
write_dataset src: /simulation.sedml/Figure_1c to tgt: /simulation.sedml/Figure_1c, shape: (4, 601), type: float64
iterating over chunks for /simulation.sedml/Figure_1c
writing dataset data for slice: (slice(0, 4, 1), slice(0, 601, 1))
done with dataload for /simulation.sedml/Figure_1c
write_dataset src: /simulation.sedml/report to tgt: /simulation.sedml/report, shape: (7, 601), type: float64
iterating over chunks for /simulation.sedml/report
writing dataset data for slice: (slice(0, 7, 1), slice(0, 601, 1))
done with dataload for /simulation.sedml/report
load_file complete
File outputs/reports.h5 uploaded to domain: /results/61fea4a08c1e3dc95a79802e

[0;36m================================================== Zipping outputs ==================================================[0m
  adding: outputs/ (stored 0%)
