You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basic Idea: Most if not all EAS experiments have the capability to read-in CONEX like shower profile files and then model florescence generation, propagation and detector responses. If NuSpaceSim has the option to export dE/dX as a function of slant depth along with zenith/azimuth for each simulated EAS, then NuSpaceSim can be immediately used in analyses preformed by established experiments.
This should be relatively simple as the electromagnetic content of the shower is already calculated in order to model the cherenkov emission. All that would be needed would be to calculate the dE/dX in 5-10g/cm2 steps and place it in a root structure that mirrors that of Conex with 0 populating un-needed / un-used data fields.
The text was updated successfully, but these errors were encountered:
emayotte
changed the title
Exporting EAS profile information for direct readin by any UV sensitive experiment
Exporting EAS profile information for direct read-in by any UV sensitive experiment
Mar 31, 2022
Can not upload a conex example file, but here is a list of the leafs in the conex shower and header root trees. Sonja and will write a simple uproot implementation of a conex root tree writer.
Basic Idea: Most if not all EAS experiments have the capability to read-in CONEX like shower profile files and then model florescence generation, propagation and detector responses. If NuSpaceSim has the option to export dE/dX as a function of slant depth along with zenith/azimuth for each simulated EAS, then NuSpaceSim can be immediately used in analyses preformed by established experiments.
This should be relatively simple as the electromagnetic content of the shower is already calculated in order to model the cherenkov emission. All that would be needed would be to calculate the dE/dX in 5-10g/cm2 steps and place it in a root structure that mirrors that of Conex with 0 populating un-needed / un-used data fields.
The text was updated successfully, but these errors were encountered: