Open tking53 opened 7 years ago
An alternative might be to add a flag the prevents zeroing of the histograms when utkscan starts up. So that you can run sequential ./utkscan ..
from bash.
That's actually the harder of the solutions. Since we're building the HRIBF based his files.
From @spaulaus on #179:
Bash scripts do not need #178 to be finished in order to be useful. You can build multiple ROOT files and chain them together fairly trivially.
And what about damm histograms?
From @spaulaus on #179:
DAMM histograms can also be added together using a program called hisadd.
I do not know why the histograms are zeroed when you start a new scan that would be a question for @cthornsb
Out of simplicity, any time I initialize a new histogram I initialize a giant block of zeros. A lot of checks would need to be done to ensure that a new histogram would have exactly the same size and layout as an existing one upon initialization. That feature is not implemented.
@cthornsb That makes sense. We're not trying to recreate DAMM here.
@tking53 The solution then would be to use hisadd.
@spaulaus Is this possible now that we have the ability to specify firmware and frequency in a config file? We could have something like:
utkscan -i file1 file2 file 3
It would be helpful to be able to pass a cmd file to utkscan from the bash prompt. This way we could scan large numbers of files sequentially. Currently you have to run this from the ncurses interface, which in a screen (or tmux) session becomes completely unreadable.