Skip to content

Conversation

@bamesserly
Copy link
Collaborator

@bamesserly bamesserly commented Jun 20, 2024

Addressing issue #10. Our flux stuff has no business in the MAT. It's currently holding up potential adoption by an external user. Where the rubber hits the road: HistWrappers require MAT-MINERvA 👎.

Flux Systematics can move over, trivially, I believe. This technically isn't a dependence issue, but it's related to FRW, so moving it now.

FluxReweighter, OTOH has a complicated use inside of HistWrapper construction. In my first commit on this branch, I've removed the complicated use and removed FRW and FluxSysts. Also modified the dict's and build's CMakeLists. Don't know what I was doing with all that, but it worked. MAT compiles. I also, trivially, move FRW and FluxSysts into MAT-MINERvA and that compiled as well. I'll link the PR when I make it.

For MAT's purposes, nothing else needs to be done. Though plumbing experts should make sure the dict and cmake stuff is all good.

BUT this also needs to wait on a merge until we've sorted out the solution in concert on the MAT-MINERvA end.

The only substantive use FRW was used in are the HistWrappers. This behavioris going to need to be readded in MAT-MINERvA if we want it.

I believe there was nothing stopping FluxSystematics from going to
MAT-MINERvA yesterday.

Also modified the dict's and build's CMakeLists. Don't know what
I was doing with that, but it worked.
@bamesserly
Copy link
Collaborator Author

Also: there are still several references to FluxReweighter in the macros and scripts folders. Those should be cleaned out and/or moved to MAT-MINERvA when this goes through.

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.

HistWrapper depends on MAT-MINERvA via useNuEConstraint and Flux-related stuff

2 participants