Skip to content

Feature/howard v09 72 00 08 harps - #791

Draft
brucehoward-physics wants to merge 4 commits into
release/SBN2023A_NuMIfrom
feature/howard_v09_72_00_08_harps
Draft

brucehoward-physics wants to merge 4 commits into
release/SBN2023A_NuMIfrom
feature/howard_v09_72_00_08_harps

Conversation

@brucehoward-physics

Copy link
Copy Markdown
Contributor

I'm not sure the best way to have code for a data cross-check approved without actually merging it into the code base at the moment, but figure maybe getting some sort of branch which has undergone "approvals" or "checking over" might be a good start. Hence, making this draft PR as we don't actually want to merge it yet, but to have it checked out. Someone should let me know if they think of a better procedure.

Tagging Alice and Joseph as reviewers for the moment due to relevant reconstruction and icaruscode/larsoft expertise. Maybe someone like Dom Brailsford would also be a good reviewer especially on the Pandora side: perhaps we should add him.

This is the icaruscode repo version -- just tagging Alice for now on the Pandora repos, but with above caveat.

HARPS module put together largely by @hausnerh and myself. The XMLs are to run Pandora on the post-HARPS events. The calibration changes are from updates by @jedori0228 based on work by folks in the calibration group (I think London?) to allow the normalization data calibrations on planes other than collection. (Note that there is a database file missing from this branch which is needed for said normalization).

The fhicls I've used to control the HARPS and post-HARPS reco have typically been part of my tarballs that I send to the grid, but I would happy to provide some examples to look at as well as part of any checks here.

At some point we will actually want to merge this tool into icaruscode for broader use.

@jas1005

jas1005 commented Apr 3, 2026

Copy link
Copy Markdown
Contributor

@jzennamo, @acampani, and @absolution1

I'm going through old PRs and it looks like this one never got approved. I realize the number of changes is quite large, but I hope your relative familiarity with the code will make things easier. Do y'all have time to review this PR or should I ask someone else?

@jas1005

jas1005 commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

@jzennamo, @acampani, @absolution1, and @brucehoward-physics,

I'll message y'all on Slack about this as well. Feel free to respond here or there.

I've not heard anything regarding this PR since I first reached out to reviewers in early April of 2026. In an attempt to clean up the PR log for ICARUSCode, I'd like to close this PR. Opinions, thoughts, concerns?

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.

6 participants