Closed sjdolan closed 1 year ago
I tested the new implementation. With the fix, the warning is not showing up, and I can successfully run events.
The lines below demonstrate that the hadron tensor is loaded correctly:
1686209133 NOTICE Ntp : [n] <NtpWriter.cxx::NtpWriter (45)> : Run number: 1110000601200
1686209133 NOTICE Ntp : [n] <NtpWriter.cxx::NtpWriter (46)> : Requested G/ROOT tree format: [NtpMCEventRecord]
1686209133 NOTICE Ntp : [n] <NtpMCJobConfig.cxx::Load (47)> : Converting configuration registries to TFolders
1686209133 NOTICE Ntp : [n] <NtpMCJobEnv.cxx::TakeSnapshot (46)> : Taking environment snapshot and saving it in a TFolder
1686209133 INFO TabulatedHadronTensorModelI : [n] <TabulatedHadronTensorModelI.cxx::BuildTensor (312)> : Loading the hadron tensor data file /sps/gdrnu/jtena/Software/Genie/generator/Sources/vCRPAFix/data/evgen/hadron_tensors/crpa_susav2/SuSAv2_1000060120_QE_EM.dat
TabulatedLabFrameHadronTensor: reading hadron tensor table
table_file_name: /sps/gdrnu/jtena/Software/Genie/generator/Sources/vCRPAFix/data/evgen/hadron_tensors/crpa_susav2/SuSAv2_1000060120_QE_EM.dat
Z: 6
A: 12
num_q0: 401
num_q_mag: 401
1686209133 NOTICE INukeNucle```
Julia tested the updated SuSAv2 and co models with EM scattering and found an issue. We quickly traced this down to a silly typo when I was expanding the SuSA code to work for CRPA as well. This is now fixed.