Skip to content

Conversation

@vpec0
Copy link
Member

@vpec0 vpec0 commented Nov 5, 2025

This adds an analyzer module which extracts PDS raw waveforms and stores them into a simplified ROOT TTree, 1 waveform per tree entry.

I also added a fhicl file to run the DAPHNE decoder and the analyzer at one go for PDVD. This is to be used on PDVD raw data stored in hdf5 files. The output is only the ROOT file with the simplified TTree, the name of which can be specified on the command line with the option -T.

vpec0 added 4 commits October 7, 2025 11:52
…nvolution of streaming channels, where the waveforms are too long and the optimization takes too much time (minutes). For future, we may consider making an option to switch the optimization on/off, if it benefits the performance for the self-triggering channels.
…TTree. This is similar to what the decoder (duneprototypes/Protodune/hd/RawDecoding/DAPHNEReaderPDHD_module.cc) does, but there not all the branches are populated.
@vpec0 vpec0 requested review from JacobBoza, jroto and lpaulucc November 5, 2025 10:20
Copy link
Member

@lpaulucc lpaulucc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Viktor, I am starting to find the Optical Detector folder a bit crowded. What would you think about moving this module to duneopdet/OpticalDetector/Ana?

}

produce: [ rns,triggerrawdecoder,pdvddaphne ]
analyze: [ rawwfmana ]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume this analyzer can be run over the already centrally processed PDVD keep up data, right? Maybe create this fhicl as a ana job only and include in the header over what kind of output to run it?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure what you are asking for. Sure, this fhicl can be rewritten to be used on keep up data. However, I don't know how to make it universal. For the PDS system, this format is useful as not all PDS runs were processed in the keep up, or am I wrong here?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, it is fine to leave it as it is, with producers. It is not hard to adapt to whatever you need. Thanks, Viktor

@vpec0
Copy link
Member Author

vpec0 commented Nov 7, 2025

Moving this to subdir ana sounds good to me.

…e build. Adding Ana/CMakeLists.txt that allows build ing the code. Code not meant for being built is currently excluded explicitly.
@vpec0
Copy link
Member Author

vpec0 commented Nov 25, 2025

I have moved the module to the Ana subdir. I have tested it compiled and installed. Does this look OK, @lpaulucc?

@vpec0
Copy link
Member Author

vpec0 commented Nov 25, 2025

I have also created a prolog file to place standard configurations for the analyzer in there. Currently only configurations for PDHD/VD data is there. I plan to add sim versions too, though I am not sure if sims would have a dunedaq::trgdataformats2::TriggerCandidateData product, which is needed to get trigger type.

Copy link
Member

@lpaulucc lpaulucc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, Viktor. I hope this does not clash with my latest PR that already included a CMakeLists to this folder.

@vpec0
Copy link
Member Author

vpec0 commented Nov 26, 2025

I tested this with the head of develop. All seemed to have built OK.

I removed one line which your updates to the structure of Ana made obsolete.

@wyjang-uta
Copy link
Member

trigger build

@FNALbuild
Copy link
Collaborator

✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard

@FNALbuild
Copy link
Collaborator

❌ CI build for DUNE Failed at phase build DUNE on slf7 for c14:prof -- details available through the CI dashboard

🚨 For more details about the failed phase, check the build DUNE phase logs

parent CI build details are available through the CI dashboard

@FNALbuild
Copy link
Collaborator

✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard

@FNALbuild
Copy link
Collaborator

❌ CI build for DUNE Failed at phase ci_tests DUNE on slf7 for e26:prof - ignored warnings for build -- details available through the CI dashboard

🚨 For more details about the failed phase, check the ci_tests DUNE phase logs

parent CI build details are available through the CI dashboard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants