Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calibration ntuple improvements #427

Open
linyan-w opened this issue Mar 12, 2024 · 2 comments
Open

Calibration ntuple improvements #427

linyan-w opened this issue Mar 12, 2024 · 2 comments
Assignees

Comments

@linyan-w
Copy link
Contributor

linyan-w commented Mar 12, 2024

Reorganization into the Calibration directory

  • Fran kindly moved the 1d signal response modules out, so we can use that directory. I moved the PDS module and the CRT fcl file there. We should plan on having the CRT module there soon. The TPC module lives in sbncode. We can leave the module there and move the fcls to sbndcode (see next point).
  • This is pending the CRT breaking change by Henry and several iterations are expected.

2d simulation configuration

  • The skimmer fcl had simdrift for the SimChannelproducer, which means that even for the 2d sample in 2023B the calibration ntuple is still taking the 1d simulation.
  • For the next production, Lynn modified the reco2 stage configuration, so that it takes 2d producers.
  • We should still move the skimmer fcl from sbncode to sbndcode and switch to "simtpc2d:simpleSC" as the default for SimChannelproducer.

Trim the PDS/CRT trees

  • The TPC tree is only 0.5 MB/event, whereas the untrimmed file with PDS/CRT trees is 5 MB/event, mostly from PDS. We need to impose a narrower window for PDS [0, 10 us].
  • Should we include waveforms in the ntuple or in a separate file?
  • Work in progress and not resolved yet.
@VCLanNguyen
Copy link
Contributor

VCLanNguyen commented Mar 12, 2024

On point 2, the fcl for caloskim lives here.
I followed the convention from ICARUS when originally ported the code.

The fcl can be moved from sbncode to sbndcode since it's solely used by SBND only.

Just need to make sure we don't have duplicated fcls on both sbn/sbndcode.

@linyan-w
Copy link
Contributor Author

On point 2, the fcl for caloskim lives here. I followed the convention from ICARUS when originally ported the code.

The fcl can be moved from sbncode to sbndcode since it's solely used by SBND only.

Just need to make sure we don't have duplicated fcls on both sbn/sbndcode.

Thanks Lan. I updated the issue accordingly.

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

No branches or pull requests

4 participants