sntools is a Monte Carlo event generator for supernova neutrino interactions.
It is a command line application that uses detailed time- and energy-dependent neutrino fluxes (provided by various supernova models) to generate interactions within the detector volume and write them to event files that can be used as an input for a full detector simulation. sntools was originally developed for Hyper-Kamiokande and later extended to support different detectors and detector materials.
Additionally, sntools can be used as a Python library that implements neutrino cross sections.
This README file should give a brief overview over sntools and help you get started. For more information, see the full documentation for each release on GitHub.
First, make sure you have Python 3.8 or higher installed on your computer. Then, in a terminal, run
pip install sntools
to install the latest version of sntools and all dependencies.
Finally, run
python -c 'import sntools; sntools.setup()'
to check whether sntools is working and to download the sample input file for the usage examples below.
To generate your first supernova neutrino events with sntools, open a terminal window and type in the following command:
sntools fluxes/intp2001.data --format nakazato --endtime 50
This generates events for the first 50 ms of a supernova based on the neutrino flux given in the input file fluxes/intp2001.data (which is in the nakazato format) and writes them to a file named outfile.kin in the current directory.
(This sample input file is included in the sntools repository. See this web page for more information.)
A more realistic usage that demonstrates more of sntools’ capabilities looks like this:
sntools fluxes/intp2001.data --format nakazato --channel es --detector SuperK --distance 20 --verbose --output intp2001es.kin
This uses the neutrino flux given in the same input file to generate neutrino-electron elastic scattering events in Super-Kamiokande for a supernova at 20 kpc distance. It also produces more verbose output, which lets you see that sntools generates events separately for different neutrino flavours (which have different fluxes and cross sections), before merging them into an output file named intp2001es.kin.
You can also run
sntools -h
to get an overview over all of sntools’ options.
Text file(s) containing information about neutrino fluxes produced by the supernova. sntools distinguishes between three flavours: nu_e, anti-nu_e and nu_x (where nu_x stands for nu_mu or nu_tau or their respective antineutrinos). The following input formats are supported.
Used by recent simulations by the Nakazato group. Fluxes for 13 and 20 solar mass progenitors are included as fluxes/intp1301.data and fluxes/intp2001.data. A description of the format and fluxes for more progenitors are available online.
If you use these included models in your work, please cite Nakazato et al., ApJ Supp. 205 (2013) 2.
Text file containing time, mean energy, mean squared energy and luminosity. These parameters describe a Gamma distribution, which is a good fit to the true spectrum. See fluxes/sample-gamma.txt for an unphysical sample file.
Similar to the Gamma format, but in an HDF5 file instead of plain text. Data available online.
Used in recent simulations by the Princeton group.
Used in historical simulation by Totani et al., which is the baseline model in the Hyper-Kamiokande Design Report.
sntools supports the main interaction channels in water and liquid scintillator.
For water Cherenkov detectors, like Hyper-Kamiokande, these are inverse beta decay, elastic scattering on electrons and charged-current interactions of nu_e and anti-nu_e on oxygen-16 nuclei.
For liquid scintillator detectors, these are inverse beta decay, elastic scattering on electrons, charged-current interactions of nu_e and anti-nu_e on carbon-12 nuclei and neutral-current interactions on carbon-12 nuclei.
Water-based liquid scintillator, a mixture of the two materials, is also supported.
A text file in the NUANCE format (used by the /mygen/vecfile options in WCSim) or the RATPAC format.
To report problems or ask for help, open an issue on GitHub or email the lead developer.
Contributions to sntools are welcome! See instructions in the full documentation for help on common ways to extend sntools (e. g. by adding a new detector, input format or interaction channel) and please submit a pull request with your contributions!
Please note that this project is released with a Contributor Code of Conduct (see CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.