csps elphel audit_v0.4

Overview

The csps-elphel-audit, specific to Elphel manufacturer, allows to generate audits of camera logs-files provided by the camera records. The audit procedure consists in logs-files reading in order to extract important information that describe the logs-files.

Usage

The csps-elphel-audit software expects the following arguments and parameters :

--path -p

Directory that containing the logs-files to audit.

Demonstration

Considering a logs-file coming form an eyesis4pi camera device, the audit process dumps the following information :

Auditing file capture_example.log-00001
    General information summary
        UTC-begin       : 2014-05-21T15:17:23+00:00
        UTC-end         : 2014-05-21T15:21:26+00:00
        Size of file    : 38756352 Bytes
        CGC-64          : 0
        Records count   : 605568 records
    Master events summary
        Range : 1400685443.181311 - 1400685686.681311
        Span  : 0000000243.500000
        Steps : 0000000000.500000 - 0000000000.500000
        Synch : 1400685443.181289 - 0000000000.000022
    IMU events summary
        Range : 1400685443.112938 - 1400685686.997733
        Span  : 0000000243.884795
        Steps : 0000000000.000403 - 0000000000.000410
    GPS events summary
        Range : 1400685442.237720 - 1400685686.234573
        Span  : 0000000243.996853
        Steps : 0000000000.000000 - 0000000000.999988

Considering the general information block, the first information gives the initial and final time, in human readable form, of camera trigger (master event) found in the logs-file. The size, in bytes, and the 64-congruence condition are then given. The number of complete records found in the log-file is finally displayed.

The next three information blocks are related to the three different logged events. In each block, the fields give initial and final timestamps, the time range and the minimum and maximum time interval between successive events of the same type. In the master information block, the Synch field gives the initial master timestamps found in the logs-file and the time difference with its respective event-logger timestamps.

Compilation

The software binary can be build using its specific makefile by simply typing in its base directory :

$ make clean && make build [OPENMP=false]

The binary is placed in the local bin directory and is not copied in the main bin directory. To generate the documentation, use the command :

$ make clean-documentation && make documentation

To install or uninstall the binaries on the local computer, use the commands :

# make install
# make uninstall