Skip to content
Eclipse eCAL™

eCAL Measurement Cutter

eCAL Measurement Cutter is a Command Line Application used to manipulate eCAL measurements. The executable is ecal_meas_cutter /.exe. It can trim measurements by time, exclude / include channels, modify base file names and split the measurement files by size.

Usage

meas_cutter_usage.txt
1
USAGE:
2


3
   ecal_meas_cutter.exe  [-s] [-q] -o <string> ... -i <string> ... -c
4
                         <string> [--] [--version] [-h]
5


6


7
Where:
8


9
   --enable-one-file-per-topic
10
     Whether to separate each topic in single HDF5 file.
11


12
   -s,  --save_log
13
     Enables log file creation in a folder called "log" next to the
14
     executable.
15


16
   -q,  --quiet
17
     Disables logging to console output.
18


19
   -o <string>,  --output <string>  (accepted multiple times)
20
     (required)  Path of the output measurement (Tip: one input measurement
21
     has to have a corresponding output).
22


23
   -i <string>,  --input <string>  (accepted multiple times)
24
     (required)  Path of the input measurement (Tip: one input measurement
25
     has to have a corresponding output).
26


27
   -c <string>,  --config <string>
28
     (required)  Path to the configuration file that contains operations to
29
     be done on the measurements.
30


31
   --,  --ignore_rest
32
     Ignores the rest of the labeled arguments following this flag.
33


34
   --version
35
     Displays version information and exits.
36


37
   -h,  --help
38
     Displays usage information and exits.
39


40


41
   eCAL Measurement Cutter

Now let’s take them one by one and explain.

1. Input path (-i, --input)

The path to the measurement that we want to process. It can also be a path pointing to an .ecalmeas file.

2. Output path (-o, --output)

The path where the converted measurement will be saved.

3. Configuration file (-c, --config)

The application uses a YAML configuration file that describes the changes to be applied on the given measurement.

Let’s see how this configuration file can look like.

config.yaml
1
basename: measurement
2
splitsize: 1024
3


4
trim:
5
  start:
6
    time:  10
7
    base:  start
8
    scale: s
9


10
  end:
11
    time: 20
12
    base: start
13
    scale: s
14


15
exclude:
16
   - re : .*Image.*
17
   - re : .*V2X.*
18
   - TrafficParticipantListPb

  • basename : the base name of the .hdf5 files

  • splitsize : maximum size of the .hdf5 files in Megabytes

  • trim : specifies the fact that we want to trim the measurement, either at the start, the end or both

    • start / end : specifies how the start/end will be calculated

      • time : the value that we want to use to trim the start/end
      • base : the reference point from where the new start/end is calculated
      • scale : the scale that we want to use
  • include/exclude (mutually exclusive) : a YAML list describing the channel names that we want to include or exclude from a measurement.

4. Save log (-s, --save_log)

When this flag is enabled, the application will also write its output in a log file. This file can be found in the folder log, next to the executable.

5. Disable verbose (-q, --quiet)

When this flag is enabled, console output is disabled except for error messages.

6. Enable one file per topic (--enable-one-file-per-topic)

When this flag is enabled, each topic will be written in its own HDF5 file.