Project

General

Profile

Bug #6794

For files with no events, MetaDataRunTool reports a value that changes between invocations as the last event number

Added by Robert Illingworth about 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Start date:
08/13/2014
Due date:
% Done:

0%

Estimated time:
Duration:

Description

For example:

$ MetaDataRunTool /data-a/FarDet/fardet_r00016729_s36_unknown.raw | tail -n2
'firstEvent' : '0'
'lastEvent' : '139782573223936'
$ MetaDataRunTool /data-a/FarDet/fardet_r00016729_s36_unknown.raw | tail -n2
'firstEvent' : '0'
'lastEvent' : '139637769031680'

This looks like it's an uninitialized variable or similar. Even if the file contents aren't very interesting, this does put a bogus, non-deterministic, value into the metadata database.



Also available in: Atom PDF