-
Notifications
You must be signed in to change notification settings - Fork 10
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
Error when simulating CPP data with BeamProperty Config #343
Comments
I think that Justin will provide the luminosity, and I expect that he is waiting for all of the REST files to be processed; about 6% of the NERSC jobs failed and Igal is redoing those. |
Oh and I think Igal said last Wed that he expected it'd take 2-3 weeks to finish reprocessing the problem jobs. |
Yes, we don't fill the flux tables until after the production is complete. In the meantime you can use the cobrems generator and set the electron beam and coherent peak energies to match the setting you want. FLUX_TO_GEN=cobrems Those might actually get populated from RCDB if you leave them out of your MC.config file? Of course you can also specify what energy range you actually want to generate events over with the min/max flags. GEN_MIN_ENERGY=3 |
It would be great if the BeamProperties class could catch this case and print a useful error message. |
I thought a check already existed to thrown and error and print a message if the flux integral was zero. I added another check on the existence of the CCDB table here #344 |
When running MCWrapper there is an issue when the option for beamconfig:
define beamconfig TEMPBEAMCONFIG
MCWrapper crashes with this error:
It seems as though the luminosity is not entered into the database yet:
PHOTON_BEAM/pair_spectrometer/lumi/tagh/untagged
PHOTON_BEAM/pair_spectrometer/lumi/tagm/untagged
Commenting out the beamconfig line fixes issue for now, but I think we need this entered into the database which I am unsure of how to do
The text was updated successfully, but these errors were encountered: