3. Usage

The sections below constitute a “reference” for CO2MPAS - a tutorial is maintained in the wiki for this project at: https://github.com/JRCSTU/CO2MPAS-TA/wiki/CO2MPAS-user-guidelines

3.1. CO2MPAS GUI

From “Rally” release, CO2MPAS can be launched through a Graphical User Interface (GUI). Its core functionality is provided from within the GUI. Just ensure that the latest version of CO2MPAS is properly installed, and that its version is the latest released, by checking the “About” menu, as shown in the animation, below:

Check Co2mpas-ALLINONE Version

Alternatively, open the CONSOLE and type the following command:

## Check co2mpas version.
$ co2mpas -V
co2mpas-1.5.5

3.2. CO2MPAS command syntax

To get the syntax of the CO2MPAS console-command, open a console where you have installed CO2MPAS (see Installation above) and type:

## co2mpas help.
$ co2mpas --help

Predict NEDC CO2 emissions from WLTP.

:Home:         http://co2mpas.io/
:Copyright:    2015-2016 European Commission, JRC <https://ec.europa.eu/jrc/>
:License:       EUPL 1.1+ <https://joinup.ec.europa.eu/software/page/eupl>

Use the `batch` sub-command to simulate a vehicle contained in an excel-file.


USAGE:
  co2mpas gui         [-v | -q | --logconf=<conf-file>]
  co2mpas ta          [-f] [-O=<output-folder>] [<input-path>]...
  co2mpas batch       [-v | -q | --logconf=<conf-file>] [-f]
                      [--overwrite-cache] [-O=<output-folder>]
                      [--modelconf=<yaml-file>]
                      [-D=<key=value>]... [<input-path>]...
  co2mpas demo        [-v | -q | --logconf=<conf-file>] [-f]
                      [<output-folder>]
  co2mpas template    [-v | -q | --logconf=<conf-file>] [-f]
                      [<excel-file-path> ...]
  co2mpas ipynb       [-v | -q | --logconf=<conf-file>] [-f] [<output-folder>]
  co2mpas modelgraph  [-v | -q | --logconf=<conf-file>] [-O=<output-folder>]
                      [--modelconf=<yaml-file>]
                      (--list | [--graph-depth=<levels>] [<models> ...])
  co2mpas modelconf   [-v | -q | --logconf=<conf-file>] [-f]
                      [--modelconf=<yaml-file>] [-O=<output-folder>]
  co2mpas gui         [-v | -q | --logconf=<conf-file>]
  co2mpas             [-v | -q | --logconf=<conf-file>] (--version | -V)
  co2mpas             --help

Syntax tip:
  The brackets `[ ]`, parens `( )`, pipes `|` and ellipsis `...` signify
  "optional", "required", "mutually exclusive", and "repeating elements";
  for more syntax-help see: http://docopt.org/


OPTIONS:
  <input-path>                Input xlsx-file or folder. Assumes current-dir if missing.
  -O=<output-folder>          Output folder or file [default: .].
  <excel-file-path>           Output file.
  --modelconf=<yaml-file>     Path to a model-configuration file, according to YAML:
                                https://docs.python.org/3.5/library/logging.config.html#logging-config-dictschema
  --overwrite-cache           Overwrite the cached input file.
  --override, -D=<key=value>  Input data overrides (e.g., `-D fuel_type=diesel`,
                              `-D prediction.nedc_h.vehicle_mass=1000`).
  -l, --list                  List available models.
  --graph-depth=<levels>      An integer to Limit the levels of sub-models plotted.
  -f, --force                 Overwrite output/template/demo excel-file(s).


Model flags (-D flag.xxx, example -D flag.engineering_mode=True):
 engineering_mode=<bool>     Use all data and not only the declaration data.
 soft_validation=<bool>      Relax some Input-data validations, to facilitate experimentation.
 use_selector=<bool>         Select internally the best model to predict both NEDC H/L cycles.
 only_summary=<bool>         Do not save vehicle outputs, just the summary.
 plot_workflow=<bool>        Open workflow-plot in browser, after run finished.
 output_template=<xlsx-file> Clone the given excel-file and appends results into
                             it. By default, results are appended into an empty
                             excel-file. Use `output_template=-` to use
                             input-file as template.

Miscellaneous:
  -h, --help                  Show this help message and exit.
  -V, --version               Print version of the program, with --verbose
                              list release-date and installation details.
  -v, --verbose               Print more verbosely messages - overridden by --logconf.
  -q, --quite                 Print less verbosely messages (warnings) - overridden by --logconf.
  --logconf=<conf-file>       Path to a logging-configuration file, according to:
                                https://docs.python.org/3/library/logging.config.html#configuration-file-format
                              If the file-extension is '.yaml' or '.yml', it reads a dict-schema from YAML:
                                https://docs.python.org/3.5/library/logging.config.html#logging-config-dictschema


SUB-COMMANDS:
    gui             Launches co2mpas GUI (DEPRECATED: Use `co2gui` command).
    ta              Simulate vehicle in type approval mode for all <input-path>
                    excel-files & folder. If no <input-path> given, reads all
                    excel-files from current-dir. It reads just the declaration
                    inputs, if it finds some extra input will raise a warning
                    and will not produce any result.
                    Read this for explanations of the param names:
                      http://co2mpas.io/explanation.html#excel-input-data-naming-conventions
    batch           Simulate vehicle in scientific mode for all <input-path>
                    excel-files & folder. If no <input-path> given, reads all
                    excel-files from current-dir. By default reads just the
                    declaration inputs and skip the extra inputs. Thus, it will
                    produce always a result. To read all inputs the flag
                    `engineering_mode` have to be set to True.
                    Read this for explanations of the param names:
                      http://co2mpas.io/explanation.html#excel-input-data-naming-conventions
    demo            Generate demo input-files for the `batch` cmd inside <output-folder>.
    template        Generate "empty" input-file for the `batch` cmd as <excel-file-path>.
    ipynb           Generate IPython notebooks inside <output-folder>; view them with cmd:
                      jupyter --notebook-dir=<output-folder>
    modelgraph      List or plot available models. If no model(s) specified, all assumed.
    modelconf       Save a copy of all model defaults in yaml format.


EXAMPLES::

    # Don't enter lines starting with `#`.

    # View full version specs:
    co2mpas -vV

    # Create an empty vehicle-file inside `input` folder:
    co2mpas  template  input/vehicle_1.xlsx

    # Create work folders and then fill `input` with sample-vehicles:
    md input output
    co2mpas  demo  input

    # View a specific submodel on your browser:
    co2mpas  modelgraph  co2mpas.model.physical.wheels.wheels

    # Run co2mpas with batch cmd plotting the workflow:
    co2mpas  batch  input  -O output  -D flag.plot_workflow=True

    # Run co2mpas with ta cmd:
    co2mpas  batch  input/co2mpas_demo-0.xlsx  -O output

    # or launch the co2mpas GUI:
    co2mpas  gui

    # View all model defaults in yaml format:
    co2maps modelconf -O output

3.3. Input template

The sub-commands batch (Run) and ta (Run TA) accept either a single input-excel-file or a folder with multiple input-files for each vehicle. You can download an empty input excel-file from the GUI:

Generate |co2mpas| input template

Or you can create an empty vehicle template-file (e.g., vehicle_1.xlsx) inside the input-folder with the template sub-command:

$ co2mpas template input/vehicle_1.xlsx -f
Creating TEMPLATE INPUT file 'input/vehicle_1.xlsx'...

The generated file contains descriptions to help you populate it with vehicle data. For items where an array of values is required (e.g. gear-box ratios) you may reference different parts of the spreadsheet following the syntax of the “xlref” mini-language.

Tip

For an explanation of the naming of the fields, read the Excel input: data naming conventions section

3.4. Demo files

The simulator contains demo-files that are a nice starting point to try out. You can download the demo vehicles from the GUI:

Generate |co2mpas| demo files

Or you can create the demo files inside the input-folder with the demo sub-command:

$ co2mpas demo input -f
2016-11-14 16:33:07,520: INFO:co2mpas_main:Creating INPUT-DEMO file 'input\co2mpas_demo-0.xlsx'...
2016-11-14 16:33:07,525: INFO:co2mpas_main:Creating INPUT-DEMO file 'input\co2mpas_demo-1.xlsx'...
2016-11-14 16:33:07,530: INFO:co2mpas_main:Creating INPUT-DEMO file 'input\co2mpas_demo-2.xlsx'...
2016-11-14 16:33:07,535: INFO:co2mpas_main:Creating INPUT-DEMO file 'input\co2mpas_demo-3.xlsx'...
2016-11-14 16:33:07,540: INFO:co2mpas_main:Creating INPUT-DEMO file 'input\co2mpas_demo-4.xlsx'...
2016-11-14 16:33:07,546: INFO:co2mpas_main:Creating INPUT-DEMO file 'input\co2mpas_demo-5.xlsx'...
2016-11-14 16:33:07,551: INFO:co2mpas_main:Creating INPUT-DEMO file 'input\co2mpas_demo-6.xlsx'...
2016-11-14 16:33:07,556: INFO:co2mpas_main:Creating INPUT-DEMO file 'input\co2mpas_demo-7.xlsx'...
2016-11-14 16:33:07,560: INFO:co2mpas_main:Creating INPUT-DEMO file 'input\co2mpas_demo-8.xlsx'...
2016-11-14 16:33:07,565: INFO:co2mpas_main:Creating INPUT-DEMO file 'input\co2mpas_demo-9.xlsx'...
2016-11-14 16:33:07,570: INFO:co2mpas_main:Creating INPUT-DEMO file 'input\co2mpas_simplan.xlsx'...
2016-11-14 16:33:07,574: INFO:co2mpas_main:You may run DEMOS with:
    co2mpas batch input

3.4.1. Demo description

id AT cal WLTP-H cal WLTP-L S/S BERS trg NEDC-H trg NEDC-L plan
0   X       X    
1   X   X X X    
2 X   X       X  
3   X   X   X    
4 X   X   X   X  
5   X     X X    
6 X X   X   X    
7 X X   X X X    
8   X X     X X  
9 X X   X X X    
simplan   X       X   X

3.5. Synchronizing time-series

The model might fail in case your time-series signals are time-shifted and/or with different sampling rates. Even if the run succeeds, the results will not be accurate enough, because the data are not synchronized with the theoretical cycle.

As an aid tool, you may use the datasync tool to “synchronize” and “resample” your data, which have been acquired from different sources.

datasync tool

To get the syntax of the datasync console-command, open a console where you have installed CO2MPAS and type:

## datasync help.
$ datasync --help

Shift and resample excel-tables; see http://co2mpas.io/usage.html#Synchronizing-time-series.

Usage:
  datasync template [-f] [--cycle <cycle>] <excel-file-path>...
  datasync          [-v | -q | --logconf=<conf-file>] [--force | -f]
                    [--interp <method>] [--no-clone] [--prefix-cols]
                    [-O <output>] <x-label> <y-label> <ref-table>
                    [<sync-table> ...] [-i=<label=interp> ...]
  datasync          [-v | -q | --logconf=<conf-file>] (--version | -V)
  datasync          (--interp-methods | -l)
  datasync          --help

Options:
  <x-label>              Column-name of the common x-axis (e.g. 'times') to be
                         re-sampled if needed.
  <y-label>              Column-name of y-axis cross-correlated between all
                         <sync-table> and <ref-table>.
  <ref-table>            The reference table, in *xl-ref* notation (usually
                         given as `file#sheet!`); synced columns will be
                         appended into this table.
                         The captured table must contain <x_label> & <y_label>
                         as column labels.
                         If hash(`#`) symbol missing, assumed as file-path and
                         the table is read from its 1st sheet .
  <sync-table>           Sheets to be synced in relation to <ref-table>, also in
                         *xl-ref* notation.
                         All tables must contain <x_label> & <y_label> as column
                         labels.
                         Each xlref may omit file or sheet-name parts; in that
                         case, those from the previous xlref(s) are reused.
                         If hash(`#`) symbol missing, assumed as sheet-name.
                         If none given, all non-empty sheets of <ref-table> are
                         synced against the 1st one.
  -O=<output>            Output folder or file path to write the results
                         [default: .]:

                         - Non-existent path: taken as the new file-path; fails
                           if intermediate folders do not exist, unless --force.
                         - Existent file: file-path to overwrite if --force,
                           fails otherwise.
                         - Existent folder: writes a new file
                           `<ref-file>.sync<.ext>` in that folder; --force
                           required if that file exists.

  -f, --force            Overwrite excel-file(s) and create any missing
                         intermediate folders.
  --prefix-cols          Prefix all synced column names with their source
                         sheet-names. By default, only clashing column-names are
                         prefixed.
  --no-clone             Do not clone excel-sheets contained in <ref-table>
                         workbook into output.
  --interp=<method>      Interpolation method used in the resampling for all
                         signals [default: linear]: 'linear', 'nearest', 'zero',
                         'slinear', 'quadratic', 'cubic', 'barycentric',
                         'polynomial', 'spline' is passed to
                         scipy.interpolate.interp1d. Both 'polynomial' and
                         'spline' require that you also specify an order (int),
                         e.g. df.interpolate(--interp=polynomial4).
                         'krogh', 'piecewise_polynomial', 'pchip' and 'akima'
                         are all wrappers around the scipy interpolation methods
                         of similar names.
                         'integral' is respect the signal integral.
  -i=<label=interp>      Interpolation method used in the resampling for a
                         signal with a specific label
                         (e.g., `-i alternator_currents=integral`).
  -l, --interp-methods   List of all interpolation methods that can be used in
                         the resampling.
  --cycle=<cycle>        If set (e.g., --cycle=nedc.manual), the <ref-table> is
                         populated with the theoretical velocity profile.
                         Options: 'nedc.manual', 'nedc.automatic',
                         'wltp.class1', 'wltp.class2', 'wltp.class3a', and
                         'wltp.class3b'.

  <excel-file-path>      Output file.

Miscellaneous:
  -h, --help             Show this help message and exit.
  -V, --version          Print version of the program, with --verbose
                         list release-date and installation details.
  -v, --verbose          Print more verbosely messages - overridden by --logconf.
  -q, --quite            Print less verbosely messages (warnings) - overridden by --logconf.
  --logconf=<conf-file>  Path to a logging-configuration file, according to:
                         See https://docs.python.org/3/library/logging.config.html#configuration-file-format
                         Uses reads a dict-schema if file ends with '.yaml' or '.yml'.
                         See https://docs.python.org/3.5/library/logging.config.html#logging-config-dictschema

* For xl-refs see: https://pandalone.readthedocs.org/en/latest/reference.html#module-pandalone.xleash

SUB-COMMANDS:
    template             Generate "empty" input-file for the `datasync` cmd as
                         <excel-file-path>.


Examples::

    ## Read the full contents from all `wbook.xlsx` sheets as tables and
    ## sync their columns using the table from the 1st sheet as reference:
    datasync times velocities folder/Book.xlsx

    ## Sync `Sheet1` using `Sheet3` as reference:
    datasync times velocities wbook.xlsx#Sheet3!  Sheet1!

    ## The same as above but with integers used to index excel-sheets.
    ## NOTE that sheet-indices are zero based!
    datasync times velocities wbook.xlsx#2! 0

    ## Complex Xlr-ref example:
    ## Read the table in sheet2 of wbook-2 starting at D5 cell
    ## or more Down 'n Right if that was empty, till Down n Right,
    ## and sync this based on 1st sheet of wbook-1:
    datasync times velocities wbook-1.xlsx  wbook-2.xlsx#0!D5(DR):..(DR)

    ## Typical usage for CO2MPAS velocity time-series from Dyno and OBD
    ## (the ref sheet contains the theoretical velocity profile):
    datasync template --cycle wltp.class3b template.xlsx
    datasync -O ./output times velocities template.xlsx#ref! dyno obd -i alternator_currents=integral -i battery_currents=integral

3.5.1. Datasync input template

The sub-command datasync accepts a single input-excel-file. You can download an empty input excel-file from the GUI or you can use the template sub-command:

datasync template

Or you can create an empty datasync template-file (e.g., datasync.xlsx) inside the sync-folder with the template sub-command:

$ datasync template sync/datasync.xlsx --cycle wltp.class3b -f
2016-11-14 17:14:00,919: INFO:__main__:Creating INPUT-TEMPLATE file 'sync/datasync.xlsx'...

All sheets must share 2 common columns times and velocities (for datasync cmd are <x-label> and <y-label>). These describe the reference signal that is used to synchronize the data.

The ref sheet (<ref-table>) is considered to contain the “theoretical” profile, while other sheets (dyno and obd, i.e. <sync-table> for datasync cmd) contains the data to synchronize and resample.

3.5.2. Run datasync

Fill the dyno and obd sheet with the raw data. Then, you can synchronize the data, using the GUI as follows:

datasync

Or you can synchronize the data with the datasync command:

datasync times velocities template.xlsx#ref! dyno obd -i alternator_currents=integral -i battery_currents=integral

Note

The synchronized signals are added to the reference sheet (e.g., ref).

  • synchronization is based on the fourier transform;
  • resampling is performed with a specific interpolation method.

All tables are read from excel-sheets using the xl-ref syntax.

3.6. Run batch

The default sub-command (batch) accepts either a single input-excel-file or a folder with multiple input-files for each vehicle, and generates a summary-excel-file aggregating the major result-values from these vehicles, and (optionally) multiple output-excel-files for each vehicle run.

To run all demo-files (note, it might take considerable time), you can use the GUI as follows:

|co2mpas| batch

Note

the file co2mpas_simplan.xlsx has the flag.engineering_mode set to True, because it contains a “simulation-plan” with non declaration data.

Or you can run CO2MPAS with the batch sub-command:

$ co2mpas batch input -O output
2016-11-15 17:00:31,286: INFO:co2mpas_main:Processing ['../input'] --> '../output'...
  0%|          | 0/11 [00:00<?, ?it/s]: Processing ../input\co2mpas_demo-0.xlsx
...
...
Done! [527.420557 sec]

Note

For demonstration purposes, some some of the actual models will fail; check the summary file.

3.7. Run Type-Approval (ta) command

The Type Approval command simulates the NEDC fuel consumption and CO2 emission of the given vehicle using just the required declaration inputs (marked as compulsory inputs in input file version >= 2.2.5) and produces an NEDC prediction. If CO2MPAS finds some extra input it will raise a warning and it will not produce any result. The type approval command is the CO2MPAS running mode that is fully aligned to the WLTP-NEDC correlation Regulation.

The sub-command ta accepts either a single input-excel-file or a folder with multiple input-files for each vehicle, and generates a summary-excel-file aggregating the major result-values from these vehicles, and multiple output-excel-files for each vehicle run.

Note

The user can insert just the input files and the output folder.

To run the type approval command you can use the GUI as follows:

|co2mpas| ta

Or you can run CO2MPAS with the ta sub-command:

$ co2mpas ta input -O output
2016-11-15 17:00:31,286: INFO:co2mpas_main:Processing ['../input'] --> '../output'...
  0%|          | 0/1 [00:00<?, ?it/s]: Processing ../input\co2mpas_demo-0.xlsx
...
...
Done! [51.6874 sec]

3.8. Output files

The output-files produced on each run are the following:

  • One file per vehicle, named as <timestamp>-<inp-fname>.xls: This file contains all inputs and calculation results for each vehicle contained in the batch-run: scalar-parameters and time series for target, calibration and prediction phases, for all cycles. In addition, the file contains all the specific submodel-functions that generated the results, a comparison summary, and information on the python libraries installed on the system (for investigating reproducibility issues).
  • A Summary-file named as <timestamp>-summary.xls: Major CO2 emissions values, optimized CO2 parameters values and success/fail flags of CO2MPAS submodels for all vehicles in the batch-run.

3.8.1. Custom output xl-files as templates

You may have defined customized xl-files for summarizing time-series and scalar parameters. To have CO2MPAS fill those “output-template” files with its results, execute it with the -D flag.output_template=file/path.xlsx option.

To create/modify one output-template yourself, do the following:

  1. Open a typical CO2MPAS output-file for some vehicle.

  2. Add one or more sheets and specify/referring CO2MPAS result-data using named-ranges.

    Warning

    Do not use simple/absolute excel references (e.g. =B2). Use excel functions (indirect, lookup, offset, etc.) and array-functions together with string references to the named ranges (e.g. =indirect("output.prediction.nedc_h.pa!_co2_emission_value")).

  3. (Optional) Delete the old sheets and save your file.

  4. Use that file together with the -D flag.output_template=file/path.xlsx argument.

3.9. Simulation plan

It is possible to launch CO2MPAS once, and have it run the model multiple times, with variations on the input-data, all contained in a single (or more) input file(s).

The data for base model are contained in the regular sheets, and any variations are provided in additional sheets which names starting with the plan. prefix. These sheets must contain a table where each row is a single simulation, while the columns names are the parameters that the user want to vary. The columns of these tables can contain the following special names:

  • id: Identifies the variation id.
  • base: this is a file path of a CO2MPAS excel input, this model will be used as new base vehicle.
  • run_base: this is a boolean. If true the base model results are computed and stored, otherwise the data are just loaded.

You can use the GUI as follows:

|co2mpas| batch simulation plan

Note

the file co2mpas_simplan.xlsx has the flag.engineering_mode set to True, because it contains a “simulation-plan” with non declaration data.

Or you can run CO2MPAS with the batch sub-command:

$ co2mpas batch input/co2mpas_simplan.xlsx -O output
2016-11-15 17:00:31,286: INFO:co2mpas_main:Processing ['../input/co2mpas_simplan.xlsx'] --> '../output'...
  0%|          | 0/4 [00:00<?, ?it/s]: Processing ../input\co2mpas_simplan.xlsx
...
...
Done! [180.4692 sec]

3.10. Launch CO2MPAS from Jupyter(aka IPython)

You may enter the data for a single vehicle and run its simulation, plot its results and experiment in your browser using IPython.

The usage pattern is similar to “demos” but requires to have ipython installed:

  1. Ensure ipython with notebook “extra” is installed:

    Warning

    This step requires too many libraries to provide as standalone files, so unless you have it already installed, you will need a proper http-connectivity to the standard python-repo.

    $ pip install ipython[notebook]
    Installing collected packages: ipython[notebook]
    ...
    Successfully installed ipython-x.x.x notebook-x.x.x
    
  2. Then create the demo ipython-notebook(s) into some folder (i.e. assuming the same setup from above, tutorial/input):

    $ pwd                     ## Check our current folder (``cd`` alone for Windows).
    .../tutorial
    
    $ co2mpas ipynb ./input
    
  3. Start-up the server and open a browser page to run the vehicle-simulation:

    $ ipython notebook ./input
    
  4. A new window should open to your default browser (AVOID IEXPLORER) listing the simVehicle.ipynb notebook (and all the demo xls-files). Click on the *.ipynb file to “load” the notebook in a new tab.

    The results are of a simulation run already pre-generated for this notebook but you may run it yourself again, by clicking the menu:

    "menu" --> `Cell` --> `Run All`
    

    And watch it as it re-calculates cell by cell.

  5. You may edit the python code on the cells by selecting them and clicking Enter (the frame should become green), and then re-run them, with Ctrl + Enter.

    Navigate your self around by taking the tutorial at:

    "menu" --> `Help` --> `User Interface Tour`
    

    And study the example code and diagrams.

  6. When you have finished, return to the console and issue twice Ctrl + C to shutdown the ipython-server.

3.11. Debugging and investigating results

  • Make sure that you have installed graphviz, and when running the simulation, append also the -D flag.plot_workflow=True option.

    $ co2mpas batch bad-file.xlsx -D flag.plot_workflow=True
    

    A browser tab will open at the end with the nodes processed.

  • Use the modelgraph sub-command to plot the offending model (or just out of curiosity). For instance:

    $ co2mpas modelgraph co2mpas.model.physical.wheels.wheels
    
    digraph dmap {
	node [style=filled]
	label = <dmap>
	splines = ortho
	style = filled
		34784 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">accelerations</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Vehicle acceleration [m/s2]."]
		34785 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/bypass.html">bypass</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Returns the same arguments."]
		34786 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/calculate_r_dynamic.html">calculate_r_dynamic</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Calculates the dynamic radius of the wheels [m]."]
		34787 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/calculate_r_wheels.html">calculate_r_wheels</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Calculates the radius of the wheels [m] from the tyre dimensions."]
		34788 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/calculate_tyre_dimensions.html">calculate_tyre_dimensions</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Calculates the tyre dimensions from the tyre code."]
		34789 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/calculate_wheel_powers.html">calculate_wheel_powers</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Calculates power at the wheels [kW]."]
		34790 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/calculate_wheel_speeds.html">calculate_wheel_speeds</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Calculates rotating speed of the wheels [RPM]."]
		34791 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/calculate_wheel_torques.html">calculate_wheel_torques</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Calculates torque at the wheels [N*m]."]
		34792 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">change_gear_window_width</TD></TR><TR><TD align="RIGHT" border="1">default</TD><TD align="LEFT" border="1">4.0</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Time window used to apply gear change filters [s]."]
		34793 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/default_tyre_code.html">default_tyre_code</TD></TR><TR><TD align="RIGHT" border="1">weight</TD><TD align="LEFT" border="1">5</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Return one of the most popular tyre code according to the r dynamic."]
		34794 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/define_tyre_code.html">define_tyre_code</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Returns the tyre code from the tyre dimensions."]
		34795 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">engine_speeds_out</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Engine speed [RPM]."]
		34796 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">final_drive_ratios</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Final drive ratio [-]."]
		34797 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">gear_box_ratios</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Gear box ratios [-]."]
		34798 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">gears</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Gear vector [-]."]
		34799 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/identify_r_dynamic.html">identify_r_dynamic</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Identifies the dynamic radius of the wheels [m]."]
		34800 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/identify_r_dynamic_v1.html">identify_r_dynamic_v1</TD></TR><TR><TD align="RIGHT" border="1">weight</TD><TD align="LEFT" border="1">10</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Identifies the dynamic radius of the wheels [m]."]
		34801 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/identify_r_dynamic_v2.html">identify_r_dynamic_v2</TD></TR><TR><TD align="RIGHT" border="1">weight</TD><TD align="LEFT" border="1">11</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Identifies the dynamic radius of the wheels [m]."]
		34802 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2" href="./dispatcher-406e6308d0bf447f4f58e2bb55c0dc3fc46c1bba/identify_tyre_dynamic_rolling_coefficient.html">identify_tyre_dynamic_rolling_coefficient</TD></TR></TABLE>> fillcolor=springgreen shape=box tooltip="Identifies the dynamic rolling coefficient [-]."]
		34803 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">idle_engine_speed</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Engine speed idle median and std [RPM]."]
		34804 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">motive_powers</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip=motive_powers]
		34805 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">plateau_acceleration</TD></TR><TR><TD align="RIGHT" border="1">default</TD><TD align="LEFT" border="1">0.10000011920928956</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Maximum acceleration to be at constant velocity [m/s2]."]
		34806 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">r_dynamic</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Dynamic radius of the wheels [m]."]
		34807 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">r_wheels</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Radius of the wheels [m]."]
		34808 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">stop_velocity</TD></TR><TR><TD align="RIGHT" border="1">default</TD><TD align="LEFT" border="1">1.0000001192092896</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Maximum velocity to consider the vehicle stopped [km/h]."]
		34809 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">times</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Time vector [s]."]
		34810 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">tyre_code</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Tyre code (e.g.,P225/70R14)."]
		34811 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">tyre_dimensions</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Tyre dimensions."]
		34812 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">tyre_dynamic_rolling_coefficient</TD></TR><TR><TD align="RIGHT" border="1">default</TD><TD align="LEFT" border="1">0.9713375796178343</TD></TR><TR><TD align="RIGHT" border="1">initial_dist</TD><TD align="LEFT" border="1">50</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Dynamic rolling coefficient [-]."]
		34813 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">velocities</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Vehicle velocity [km/h]."]
		34814 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">velocity_speed_ratios</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Constant velocity speed ratios of the gear box [km/(h*RPM)]."]
		34815 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">wheel_powers</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Power at the wheels [kW]."]
		34816 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">wheel_speeds</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Rotating speed of the wheel [RPM]."]
		34817 [label=<<TABLE border="0" cellspacing="0"><TR><TD border="0" colspan="2">wheel_torques</TD></TR></TABLE>> fillcolor=cyan shape=box style="rounded,filled" tooltip="Torque at the wheel [N*m]."]
			34811 -> 34794
			34797 -> 34801
			34793 -> 34810
			34789 -> 34815
			34815 -> 34791
			34788 -> 34811
			34790 -> 34816
			34814 -> 34799
			34796 -> 34799
			34808 -> 34801
			34807 -> 34802
			34802 -> 34812
			34806 -> 34790
			34813 -> 34800
			34792 -> 34801
			34799 -> 34806
			34795 -> 34801
			34784 -> 34801
			34809 -> 34801
			34794 -> 34810
			34807 -> 34801
			34810 -> 34788
			34801 -> 34806
			34798 -> 34800
			34806 -> 34793
			34811 -> 34787
			34803 -> 34801
			34817 -> 34789
			34787 -> 34807
			34800 -> 34806
			34786 -> 34806
			34806 -> 34802
			34812 -> 34786
			34797 -> 34799
			34807 -> 34786
			34804 -> 34785
			34796 -> 34801
			34813 -> 34801
			34816 -> 34791
			34795 -> 34800
			34808 -> 34800
			34816 -> 34789
			34813 -> 34790
			34805 -> 34801
			34791 -> 34817
			34796 -> 34800
			34785 -> 34815
			34797 -> 34800
}
  • Inspect the functions mentioned in the workflow and models and search them in CO2MPAS documentation ensuring you are visiting the documents for the actual version you are using.