Skip to content

Conversation

@M7medS3d
Copy link

added a new reweigh function for the new hA2025 FSI model.

@M7medS3d M7medS3d marked this pull request as ready for review August 29, 2025 02:00
@M7medS3d M7medS3d closed this Aug 29, 2025
@M7medS3d M7medS3d reopened this Aug 29, 2025
@M7medS3d M7medS3d closed this Aug 29, 2025
@M7medS3d M7medS3d reopened this Aug 29, 2025
@M7medS3d M7medS3d changed the title H a2025 rw adding new Reweight calculator for new hA2025 FSI model Aug 29, 2025
Copy link
Member

@nusense nusense left a comment

Choose a reason for hiding this comment

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

This isn't a full review, but a few concerns that come up upon a semi-cursory look

temp_map[ kXSecTwkDial_CoulombCCQE ] = "CoulombCCQE";
temp_map[ kXSecTwkDial_NormCCCOHpi ] = "NormCCCOH";
temp_map[ kXSecTwkDial_NormNCCOHpi ] = "NormNCCOH";
temp_map[ kXSecTwkDial_ZExpELFF ] = "ZExpELFFCCQE";
Copy link
Member

Choose a reason for hiding this comment

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

Was it intended that kXSecTwkDial_ZExpELFF* be removed when adding kINukehA2025_cex; or are these being excised by accident from working with an outdated version of the code?

Copy link
Author

Choose a reason for hiding this comment

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

oh sorry these were removed by mistake.

if ( !fsi_enabled ) {
LOG( "ReW", pERROR ) << "FSIs are not enabled for the current tune."
<< " Refusing to reweight FSIs.";
std::exit( 1 );
Copy link
Member

Choose a reason for hiding this comment

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

If the code is going to exit(1) then the LOG message should be using pFATAL level.

AlgFactory* algf = AlgFactory::Instance();

Algorithm* alg = algf->AdoptAlgorithm( id );
fFSIModel = dynamic_cast< HAIntranuke2018* >( alg );
Copy link
Member

Choose a reason for hiding this comment

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

I want to understand what the intent of this code is. Is it to take HAIntranuke2018 to HAIntranuke2025? Is there code to check that the input was generated with HAIntranuke2018?

Copy link
Author

Choose a reason for hiding this comment

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

yes, given the FSI issue observed in hA2018, we want to Reweight from hA2018 to hA2025, the above code I think just check if the sample was generated with hA2018.

Physics changes are considered separately for pions and nucleons.
Unitarity is explicitly conserved.
\author Jim Dobson <J.Dobson07 \at imperial.ac.uk>
Copy link
Member

Choose a reason for hiding this comment

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

Again, a review of the author list.

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.

3 participants