Support hexadecimal values in settings_example
I tried setting max_fragment_size_bytes to 0x10000 in settings_example, but got an error from DAQInterface complaining about base-10. It might be nice to support setting some parameters in hex...
JCF: resolve Eric's Issue #21496 by allowing hexadecimal values for the max_fragment_size_bytes parameter in the DAQInterface settings file
Instead of a decimal value (e.g., 1024000) a hexadecimal value such as
0xfa000 or 0xFA000 can be used. For good measure / consistency, extend
this feature to the value used for the max_fragment_size_bytes FHiCL
parameter when advanced memory usage is selected.
#1 Updated by John Freeman 9 months ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
With commit cfd9044873b6a742d8427feb1da20f32eac1ffd1 on the develop branch, this request is satisfied. Now, values assigned to max_fragment_size_bytes which begin with an "0x" are understood by DAQInterface to be hex values. E.g.,
are equivalent to
...as I've confirmed with runs 1754 (1024000), 1755 (0xfa000) and 1759 (0xFA000) on mu2edaq01 (see mu2edaq01:/home/jcfree/run_records for details).
Note that with this commit, this hexadecimal support extends to the values of max_fragment_size_bytes in individual boardreader FHiCL documents when advanced memory usage is selected.