Project

General

Profile

Bug #15745

artdaq-database has difficulty with stale_request_timeout parameter

Added by John Freeman over 2 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Category:
artdaq-database
Target version:
-
Start date:
03/06/2017
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

The title of this issue might be overly specific, but the general idea is that it seems like not all integer types will get saved into the database as originally intended due to signed/unsigned issues. To recreate the issue I'm referring to, I can do the following on mu2edaq01:

. .database.bash.rc
mkdir exampleforissue
cp -p ~/artdaq-utilities-daqinterface/simple_test_config/demo/component01_hw_cfg.fcl exampleforissue
grep stale_request_timeout exampleforissue/component01_hw_cfg.fcl 

and the output of the last command will look like:
stale_request_timeout: 0xFFFFFFFF # How long to wait before discarding request messages that are outside the available data

Now, say I import this file to the database:
conftool.sh -o import_global_config -g exampleforissue100 -v ver001 -s exampleforissue

and then export this back out, and look at the same FHiCL parameter:
conftool.sh -o export_global_config -g exampleforissue100 -s exampleforissue_exported
grep stale_request_timeout exampleforissue_exported/exampleforissue/component01_hw_cfg.fcl

then in the output I see:
stale_request_timeout: -2147483648 # How long to wait before discarding request messages that are outside the available data

It looks like in the exported (recovered) version of the parameter, the bits are being interpreted as being those of a signed integer, resulting in a negative value for a timeout setting.

History

#1 Updated by Gennadiy Lukhanin about 1 year ago

  • Status changed from New to Resolved

Fixed in the version v1_04_46 of artdaq_database.



Also available in: Atom PDF