3.2. Log Parser Parameters

The log parser is located here: ./bin/fmdt-log-parser.

The following table summarizes the available parameters:

Argument	Type	Details
--log-path	STRING	See Section 3.2.1.
--trk-roi-path	STRING	See Section 3.2.2.
--log-flt	STRING	See Section 3.2.3.
--fra-path	STRING	See Section 3.2.4.
--ftr-name	STRING	See Section 3.2.5.
--ftr-path	STRING	See Section 3.2.6.
--trk-path	STRING	See Section 3.2.7.
--trk-json-path	STRING	See Section 3.2.8.
--trk-bb-path	STRING	See Section 3.2.9.

3.2.1. --log-path

Type

STRING

Default

[empty]

Example

--log-path detect_logs/

Path of the input logs. These logs should be firstly generated by fmdt-detect. This path is mandatory and can be a file or a directory. The contents of these logs are fully detailed in Section 3.1.34.

3.2.2. --trk-roi-path

Type

STRING

Default

[empty]

Example

--trk-roi-path trk2roi.txt

Path to the input file containing lists of the RoI ids per tracked object. This is mandatory if you want to generate the BBs (see the --trk-bb-path parameter) or to extract a specific feature (see the --ftr-path and the --ftr-name parameters). The contents of this file is detailed in Section 3.1.33.

3.2.3. --log-flt

Type

STRING

Default

“^[0-9]{5}.txt”

Example

--log-flt .*

This is a regular expression to select the files to parse as fmdt-detect logs. It allows to skip files that are not related to the logs.

3.2.4. --fra-path

Type

STRING

Default

[empty]

Example

--fra-path frames.json

Path to store the frames in a Json format. Each frame contains fmdt-detect log tables (RoIs, Assocs, Motion, Tracks). It is required to fill the --log-path parameter.

3.2.5. --ftr-name

Type

STRING

Default

[empty]

Example

--ftr-name mag

This option allows to tell which specific feature you want to extract. It is required to fill both the --log-path and the --trk-roi-path parameters.

3.2.6. --ftr-path

Type

STRING

Default

[empty]

Example

--ftr-path mag.txt

The path to store the extracted feature. It is required to fill both the --log-path and the --trk-roi-path parameters.

The output file will contain the features per tracked object. Each line corresponds to a track/object and here is the corresponding line format:

{tid} {otype} {ftr1} {ftr2} {...} {ftrn}

{ftr1} is the first feature value of the track/object of {tid} id. {ftr2} is the second feature value (in the second frame where the object has been tracked). And so on, until the last feature value {ftrn}. Note that sometime the feature value can be 0, it means that the object has been extrapolated on this frame, thus the feature cannot be returned.

3.2.7. --trk-path

Type

STRING

Default

[empty]

Example

--trk-path tracks.txt

Path to the output file containing the list of the final tracks. The contents of this file is detailed in Section 3.1.1. This option requires to fill the --log-path input file.

3.2.8. --trk-json-path

Type

STRING

Default

[empty]

Example

--trk-json-path tracks.json

Path to the output file containing a dictionary of the final tracks in Json format. This is very similar to the --trk-path parameter but the data format differs.

3.2.9. --trk-bb-path

Deprecated

--out-bb

Type

STRING

Default

[empty]

Example

--trk-bb-path bb.txt

Path to the output bounding boxes file required by fmdt-visu to draw detection rectangles. Each bounding box defines the area of an object, frame by frame. This option requires to fill both the --log-path and the --trk-roi-path parameters.

Here is the corresponding line format:

{frame_id} {x_radius} {y_radius} {center_x} {center_y} {track_id} {is_extrapolated}

Each line corresponds to a frame and to an object, each value is separated by a space character.