Dataset Restricted Access
Ratliff, Hunter;
Blangiardi, Francesco;
Kögler, Toni
<?xml version='1.0' encoding='utf-8'?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:adms="http://www.w3.org/ns/adms#" xmlns:cnt="http://www.w3.org/2011/content#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dct="http://purl.org/dc/terms/" xmlns:dctype="http://purl.org/dc/dcmitype/" xmlns:dcat="http://www.w3.org/ns/dcat#" xmlns:duv="http://www.w3.org/ns/duv#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:frapo="http://purl.org/cerif/frapo/" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:gsp="http://www.opengis.net/ont/geosparql#" xmlns:locn="http://www.w3.org/ns/locn#" xmlns:org="http://www.w3.org/ns/org#" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:prov="http://www.w3.org/ns/prov#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:schema="http://schema.org/" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:vcard="http://www.w3.org/2006/vcard/ns#" xmlns:wdrs="http://www.w3.org/2007/05/powder-s#">
<rdf:Description rdf:about="https://doi.org/10.14278/rodare.3997">
<rdf:type rdf:resource="http://www.w3.org/ns/dcat#Dataset"/>
<dct:type rdf:resource="http://purl.org/dc/dcmitype/Dataset"/>
<dct:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">https://doi.org/10.14278/rodare.3997</dct:identifier>
<foaf:page rdf:resource="https://doi.org/10.14278/rodare.3997"/>
<dct:creator>
<rdf:Description rdf:about="http://orcid.org/0000-0003-3761-5415">
<rdf:type rdf:resource="http://xmlns.com/foaf/0.1/Agent"/>
<foaf:name>Ratliff, Hunter</foaf:name>
<foaf:givenName>Hunter</foaf:givenName>
<foaf:familyName>Ratliff</foaf:familyName>
<org:memberOf>
<foaf:Organization>
<foaf:name>Department of Computer science, Electrical engineering and Mathematical sciences, Western Norway University of Applied Sciences, Inndalsveien 28, Bergen, 5063, Vestland, Norway</foaf:name>
</foaf:Organization>
</org:memberOf>
</rdf:Description>
</dct:creator>
<dct:creator>
<rdf:Description rdf:about="http://orcid.org/0009-0006-7725-6751">
<rdf:type rdf:resource="http://xmlns.com/foaf/0.1/Agent"/>
<foaf:name>Blangiardi, Francesco</foaf:name>
<foaf:givenName>Francesco</foaf:givenName>
<foaf:familyName>Blangiardi</foaf:familyName>
<org:memberOf>
<foaf:Organization>
<foaf:name>Technology Methods and Systems Data Based Methods, Fraunhofer ENAS, Technologie Campus 3, Chemnitz, 09126, Saxony, Germany</foaf:name>
</foaf:Organization>
</org:memberOf>
</rdf:Description>
</dct:creator>
<dct:creator>
<rdf:Description rdf:about="http://orcid.org/0000-0002-9501-0898">
<rdf:type rdf:resource="http://xmlns.com/foaf/0.1/Agent"/>
<foaf:name>Kögler, Toni</foaf:name>
<foaf:givenName>Toni</foaf:givenName>
<foaf:familyName>Kögler</foaf:familyName>
<org:memberOf>
<foaf:Organization>
<foaf:name>Helmholtz-Zentrum Dresden - Rossendorf</foaf:name>
</foaf:Organization>
</org:memberOf>
</rdf:Description>
</dct:creator>
<dct:title>PHITS simulations of neutron and gamma-ray production from and transport of 70–250 MeV protons in heterogeneous 1D tissue phantoms</dct:title>
<dct:publisher>
<foaf:Agent>
<foaf:name>Rodare</foaf:name>
</foaf:Agent>
</dct:publisher>
<dct:issued rdf:datatype="http://www.w3.org/2001/XMLSchema#gYear">2025</dct:issued>
<dcat:keyword>proton therapy</dcat:keyword>
<dcat:keyword>treatment verification</dcat:keyword>
<dcat:keyword>particle transport calculations</dcat:keyword>
<dcat:keyword>PHITS</dcat:keyword>
<dct:issued rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2025-09-24</dct:issued>
<dct:language rdf:resource="http://publications.europa.eu/resource/authority/language/ENG"/>
<owl:sameAs rdf:resource="https://rodare.hzdr.de/record/3997"/>
<adms:identifier>
<adms:Identifier>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">https://rodare.hzdr.de/record/3997</skos:notation>
</adms:Identifier>
</adms:identifier>
<owl:sameAs rdf:resource="https://www.hzdr.de/publications/Publ-43014"/>
<dct:isVersionOf rdf:resource="https://doi.org/10.14278/rodare.3996"/>
<dct:isPartOf rdf:resource="https://rodare.hzdr.de/communities/novo"/>
<dct:isPartOf rdf:resource="https://rodare.hzdr.de/communities/rodare"/>
<owl:versionInfo>1.0.0</owl:versionInfo>
<dct:description><p><strong>Introduction</strong></p> <p>This dataset corresponds to the PHITS simulation data used in &quot;Fast Phase Space Reconstruction for Proton Beam Traversal and Neutron Emission in Proton Therapy using Fourier Neural Operators&quot;.<br> A concise description of the simulation setup is provided here; please refer to the paper for detailed discussion, discription, analysis, and further results derived from this dataset.</p> <p><br> <strong>Description of simulations</strong></p> <p>This dataset consists of <a href="https://phits.jaea.go.jp/">PHITS</a> simulations for 47 different proton energies from 70 MeV to 250 MeV incident upon different &quot;1D&quot; heterogeneous cylindrical phantoms (varied materials every 0.5 mm in length, uniform radially and rotationally) whose composition (materials and sequence along length) are taken from randomly sampled rays cast through a 3D CT phantom [CITE] with CT number mapped to material composition and density via the&nbsp;<em>HumanVoxelTable-KumamotoUniv.data</em>&nbsp;conversion table within the RT-PHITS utilitydistributed with PHITS.&nbsp;<br> Included tallies score spatial distributions of energy deposition, LET, proton current (with an additional angular dimension), neutron production, gamma-ray production, and a variety of diagnostic tallies.&nbsp;<br> Event-by-event &quot;list-mode&quot; data is scored for neutron and gamma-ray production, called &quot;dump&quot; tallies in PHITS.</p> <p>Given the objective of these simulations was for AI model development, the 47 energies are divided into 37 <strong>training</strong> energies (70 MeV to 250 MeV in 5 MeV steps) and 10 <strong>testing</strong> energies (73 MeV to 245.8 MeV in 19.2 MeV steps).&nbsp;<br> For each energy, two simulations were ran: (1) a simulation with <strong>1E8</strong> protons simulated where all <strong>tallies</strong> (including <strong>dump</strong> tallies) were included/enabled and (2) a simulation with <strong>1E9</strong> protons simulated (available on request) but with only <strong>dump</strong> tallies enabled (other tallies disabled to reduce memory consumption and increase simulation speed).&nbsp;<br> Furthermore, all of the above was actually performed twice: (1) initially with purely <strong>monoenergetic</strong> beam energies and with a spatial spread of 2.5 mm and (2) a second &quot;more realistic&quot; set with <strong>Gaussian-distributed</strong> energies (with energy-dependent FWHM) and slightly wider 4.0 mm beam spread.</p> <p>All simulation outputs were automatically processed from the plaintext and binary files produced by PHITS into compressed pickle file objects (NumPy arrays, Pandas DataFrames, dictionaries) using the <a href="https://github.com/Lindt8/PHITS-Tools">PHITS Tools</a>&nbsp;</p> <p>Python utility.&nbsp;<br> These Python objects were then utilized in the subsequent analysis of the paper this simulation set was generated for.</p> <p><br> <strong>Structure of this repository</strong></p> <p>The volume of data present in this repository is quite substantial (~ 700 GB).&nbsp;<br> Therefore, the repository has been structured in a way to allow flexibility in only downloading data of interest.</p> <p>The root directory of this repository consists of 39 top-level directories whose names indicate their contents.<br> Within each are two directories:&nbsp;<em>training</em> and&nbsp;<em>testing</em>.<br> Within each of these are directories of the format <em>???_MeV</em>, where <em>???</em> is replaced by three digits specifying the nominal beam energy in MeV.&nbsp;<br> (This is <em>???p?</em> for the energies of the testing dataset, with <em>p</em> in place of a decimal point.)<br> Thus, each <em>training</em> directory contains 37 subdirectories, and each <em>testing</em> directory contains 10 subdirectories.<br> (One should note that there are no setup differences between <em>training</em> and <em>testing</em> data; they are simply divided here in the same way as in the paper.)<br> Each <em>???_MeV</em>/<em>???p?_MeV</em> directory contains simulation input/output and/or PHITS Tools processed output, depending on the top-level directory it is contained within.<br> Input and output file names do not differ between different energies; directory structure is used to keep them distinguished/separated.</p> <p><strong>PHITS input information</strong></p> <p>One top-level directory differs from all of the others, and this is common_inputs.<br> As the name suggests, this directory contains all PHITS input information used in generating all of the simulation outputs.&nbsp;</p> <p>The core two PHITS input files used are <em>beam-on-target_phits-input_MonoE.inp</em> for the monoenergetic beam simulation set and <em>beam-on-target_phits-input_GaussE.inp</em> for the Gaussian-distributed beam energy simulation set.<br> Within these inputs are lines using the PHITS insert file function <em>infl:{*}</em>; all inserted files used in the PHITS simulations are also contained within this <em>common_inputs</em> directory.<br> The single exception to this is <em>PARAMETERS_files-1-and-7.txt</em>, which is simply the <em>file(1)</em> and <em>file(7)</em> PHITS <em>[Parameters]</em> arguments and will be system-specific paths to PHITS installation/data files.<br> Also note that relative paths are used in the <em>infl:{*}</em> commands; these relative paths differ to how this repository is structured given the repository has been restructured in post for distribution convenience.&nbsp;<br> File names are still unique and can be found in this <em>common_inputs</em> directory.<br> The <em>CELL</em> subdirectory contains the <em>[Cell]</em> sections used for the varied phantom compositions, and the <em>MAPPINGS_OF_ENERGY_TO_CELL_FILES.csv</em> file details how these files are paired with the 47 different beam energies.</p> <p><strong>PHITS outputs (raw and processed)</strong></p> <p>The remaining 38 top-level directories contain simulation/processed output.<br> When these simulations were ran, all output was contained in each <em>???_MeV</em> directory.&nbsp;<br> As detailed earlier, these have been split into various top-level directories here to allow more convenient download of only desired files.<br> Nominally, each of these <em>???_MeV</em> directories contained the following before being split:</p> <ul> <li>a <em>beam-on-target_phits-input.inp</em> PHITS input file (and a simple <em>phits.in</em> pointing to this input file, needed for parallel running of PHITS); note that these inputs have all specific source energy information populated within this file</li> <li>a <em>phantom_composition_info.csv</em> file also detailing the phantom composition used for that beam energy</li> <li><em>tphits*.out</em> file(s),<strong>&nbsp;raw</strong>&nbsp;summary output files generated by PHITS</li> <li><em>*.out</em> <strong>raw</strong> plaintext tally output files from PHITS</li> <li><em>*.eps</em> <strong>graphical</strong> visualizations of tally output, generated by PHITS</li> <li><em>*_dmp.out*</em> <strong>raw</strong> binary tally <strong>dump</strong> files from PHITS</li> <li><em>*.pickle.xz</em> <strong>processed</strong> tally output (and <em>phits.out</em> metadata) from PHITS Tools, LZMA-compressed pickle files</li> <li><em>*_dmp_namedtuple_list.pickle.xz</em> <strong>processed</strong> tally <strong>dump</strong> output from PHITS Tools, formatted as a NumPy record array (np.recarray)</li> <li><em>*_dmp_Pandas_df.pickle.xz</em> <strong>processed</strong> tally <strong>dump</strong> output from PHITS Tools, formatted as a Pandas DataFrame (same numerical data as in NumPy recarray)</li> <li><em>*.png</em> and <em>*.pdf</em> <strong>graphical</strong> visualizations of tally output, generated by PHITS Tools</li> </ul> <p>The top-level directories of this repository are named in a way to detail (1) which simulations their contents pertain to and (2) which output files are contained within them.<br> The directories are named using an underscore-delimited pattern whose components have the following names and meanings:</p> <ul> <li>Beam type:&nbsp; <ul> <li>&nbsp;<strong>MonoE</strong> refers to simulations with the monoenergetic beams with 2.5 mm spread</li> <li>&nbsp;<strong>GaussE</strong>&nbsp;refers to simulations with the Gaussian-distributed energies and 4.0 mm spread</li> </ul> </li> <li>Simulated number of protons: <ul> <li><strong>1E8</strong>&nbsp;refers to simulations with 10<sup>8</sup> (one hundred million) protons simulated&nbsp;</li> <li><strong>1E9</strong> refers to simulations with 10<sup>9</sup> (one billion) protons simulated (only available on request)</li> </ul> </li> <li>Output source/type: <ul> <li><strong>raw</strong> refers to the PHITS input and PHITS-generated output&nbsp;</li> <li><strong>processed</strong>&nbsp;refers to the Python-formatted processed output produced by PHITS Tools</li> <li><strong>plots</strong> refers to the <em>*.eps</em> files produced by PHITS and the <em>*.png</em> and <em>*.pdf</em> files produced by PHITS Tools, all containing graphical plots of tally output (only relevant to <strong>1E8</strong> simulations)</li> </ul> </li> <li>Other labels: <ul> <li><strong>proton-tally</strong>&nbsp;refers to output from the huge <em>[T-Cross]</em> tally used only in <strong>1E8</strong>&nbsp;simulations for scoring proton phase space as a function of energy, position, and direction (separated from others owing to its considerable size)</li> <li><strong>neutron-dump</strong> refers to the event-by-event neutron production data scored by a <em>[T-Product]</em> tally&#39;s &quot;dump&quot; option</li> <li><strong>NumPy</strong> and <strong>Pandas</strong>&nbsp;to denote if <strong>processed</strong>&nbsp;contents are formatted as NumPy record arrays or Pandas Dataframes&nbsp;</li> <li><strong>gamma-dump</strong> refers to the event-by-event gamma-ray production data scored by a <em>[T-Product]</em> tally&#39;s &quot;dump&quot; option</li> <li><strong>NumPy</strong>&nbsp;and <strong>Pandas</strong> to denote if <strong>processed</strong>&nbsp;contents are formatted as NumPy record arrays or Pandas Dataframes&nbsp;</li> <li><strong>other</strong> refers to output from all other tallies aside from the above three (energy deposition, LET, diagnostic tallies, etc.; only relevant to <strong>1E8</strong>&nbsp;simulations given all tallies except dump tallies were disabled for <strong>1E9</strong> simulations) along with (for <strong>raw</strong>&nbsp;directories) PHITS input-related files and <em>phits*.out</em> file(s).</li> </ul> </li> </ul> <p>All put together, this results in the following top-level directories contained in this repository:</p> <ul> <li><em>common_inputs</em></li> <li><em>GaussE_1E8_raw_proton-tally</em></li> <li><em>GaussE_1E8_raw_neutron-dump</em></li> <li><em>GaussE_1E8_raw_gamma-dump</em></li> <li><em>GaussE_1E8_raw_other</em></li> <li><em>GaussE_1E9_raw_neutron-dump&nbsp;<strong>(upon request)</strong></em></li> <li><em>GaussE_1E9_raw_gamma-dump&nbsp;<strong>(upon request)</strong></em></li> <li><em>GaussE_1E9_raw_other</em></li> <li><em>GaussE_1E8_processed_proton-tally</em></li> <li><em>GaussE_1E8_processed_neutron-dump_NumPy</em></li> <li><em>GaussE_1E8_processed_neutron-dump_Pandas</em></li> <li><em>GaussE_1E8_processed_gamma-dump_NumPy</em></li> <li><em>GaussE_1E8_processed_gamma-dump_Pandas</em></li> <li><em>GaussE_1E8_processed_other</em></li> <li><em>GaussE_1E9_processed_neutron-dump_NumPy <strong>(upon request)</strong></em></li> <li><em>GaussE_1E9_processed_neutron-dump_Pandas<strong>&nbsp;(upon request)</strong></em></li> <li><em>GaussE_1E9_processed_gamma-dump_NumPy<strong>&nbsp;(upon request)</strong></em></li> <li><em>GaussE_1E9_processed_gamma-dump_Pandas&nbsp;<strong>(upon request)</strong></em></li> <li><em>GaussE_1E9_processed_other&nbsp;</em></li> <li><em>GaussE_1E8_plots</em></li> <li><em>MonoE_1E8_raw_proton-tally</em></li> <li><em>MonoE_1E8_raw_neutron-dump</em></li> <li><em>MonoE_1E8_raw_gamma-dump</em></li> <li><em>MonoE_1E8_raw_other</em></li> <li><em>MonoE_1E9_raw_neutron-dump<strong>&nbsp;(upon request)</strong></em></li> <li><em>MonoE_1E9_raw_gamma-dump&nbsp;<strong>(upon request)</strong></em></li> <li><em>MonoE_1E9_raw_other</em></li> <li><em>MonoE_1E8_processed_proton-tally</em></li> <li><em>MonoE_1E8_processed_neutron-dump_NumPy</em></li> <li><em>MonoE_1E8_processed_neutron-dump_Pandas</em></li> <li><em>MonoE_1E8_processed_gamma-dump_NumPy</em></li> <li><em>MonoE_1E8_processed_gamma-dump_Pandas</em></li> <li><em>MonoE_1E8_processed_other</em></li> <li><em>MonoE_1E9_processed_neutron-dump_NumPy&nbsp;<strong>(upon request)</strong></em></li> <li><em>MonoE_1E9_processed_neutron-dump_Pandas&nbsp;<strong>(upon request)</strong></em></li> <li><em>MonoE_1E9_processed_gamma-dump_NumPy&nbsp;<strong>(upon request)</strong></em></li> <li><em>MonoE_1E9_processed_gamma-dump_Pandas<strong>&nbsp;(upon request)</strong></em></li> <li><em>MonoE_1E9_processed_other</em></li> <li><em>MonoE_1E8_plots</em></li> </ul> <p>And, as stated earlier, each of these top-level directories is divided into a <em>training</em> subdirectory (containing 37 <em>???_MeV</em> directories) and a <em>testing</em> subdirectory (containing 10 <em>???p?_MeV </em>directories), where the <em>???[p?]_MeV</em> directories only (1) contain particular files (2) relevant to certain simulations&amp;mdash;as specified by the top-level directory&#39;s name.</p> <p>&nbsp;</p> <p>As a note to anyone surveying the <em>raw</em> files, all <em>GaussE</em> simulations were ran with OpenMP parallelization with 10 processes.<br> For<em> 1E8 </em>simulations, this was conducted as ten PHITS runs of 1E7 protons each; for<em> 1E9 </em>simulations, this was conducted as twenty runs of 5E7 protons each.<br> (PHITS runs can be &quot;chained&quot; as &quot;restart calculations&quot;, where one run can resume from where a previous run ended.)<br> In these simulations, the generated<em> phits.out</em> files from each run were renamed to <em>phits-#.out</em> (where <em>#</em> is the run number,<em> 0</em> to<em> 19</em>) and moved into a <em>phitsout</em> subdirectory after each run&#39;s completion.<br> However, this was less uniform for the <em>MonoE</em> simulations; for those, the strategy was to complete each simulation in a single run of PHITS.&nbsp;<br> This generally involved using a hybrid OpenMP + MPI parallelization with anywhere from 80 to 160 processes each, split between OMP and MPI (noting that some<em> 1E9 </em>runs were conducted with only MPI parallelization).<br> None of this influences the output format of the standard tally outputs.<br> However, the number of dump files produced is equal to the number of MPI processes utilized.<br> This means that each <em>GaussE</em> simulation only has one dump file per dump tally owing to only using OpenMP parallelization (which merges its dump files at the end of calculation) while the<em> MonoE </em>simulations contain a varied number of dump files per dump tally owing to varriations in parallelization strategies employed in those simulations.<br> PHITS Tools ultimately merges all dump outputs back together in its processing, meaning if looking at the <em>processed</em> output this quirk of how simulations were conducted should not be apparent at all.</p> <p><br> Given PHITS Tools was under ongoing development as this dataset was being produced, the <em>GaussE</em> directories contain some extra output not present in the <em>MonoE</em> directories.&nbsp; Most notably, only for the <em>GaussE</em> simulations do the <em>plot</em> directories contain PNG and PDF plot files generated by PHITS Tools and the <em>*_processed_*</em> directories contain dictionary objects of the processed <em>phits*.out</em> files.</p> <p>Note that, for convenience, the <em>phits*.out</em> file(s) for each simulation are also copied to all <em>*_raw_*</em> directories.&nbsp; The <em>phits*.out</em> file(s) contain the full PHITS input echo, among other information about the simulation.&nbsp; For the <em>GaussE</em> simulations, these are within a further <em>phitsout</em> subdirectory for each beam energy.&nbsp; Also for all <em>GaussE_*_processed_*</em> directories, the processed <em>phits*.out</em> file(s), <em>phits*_out.pickle.xz</em>, are included too.</p> <p><strong>References</strong></p> <p><em>TO BE POPULATED</em></p> <p><strong>Acknowledgements</strong></p> <p>The NOVO project has received funding from the European Innovation Council (EIC) under grant agreement No. 101130979. The EIC receives support from the European Union&#39;s Horizon Europe research and innovation programme. Partners from The University of Manchester has received funding from UK Research and Innovation under grant agreement No. 10102118&nbsp;</p></dct:description>
<dct:accessRights rdf:resource="http://publications.europa.eu/resource/authority/access-right/RESTRICTED"/>
<dct:accessRights>
<dct:RightsStatement rdf:about="info:eu-repo/semantics/restrictedAccess">
<rdfs:label>Restricted Access</rdfs:label>
</dct:RightsStatement>
</dct:accessRights>
<dcat:distribution>
<dcat:Distribution>
<dcat:accessURL rdf:resource="https://doi.org/10.14278/rodare.3997"/>
</dcat:Distribution>
</dcat:distribution>
</rdf:Description>
</rdf:RDF>
| All versions | This version | |
|---|---|---|
| Views | 851 | 369 |
| Downloads | 851 | 0 |
| Data volume | 21.3 TB | 0 Bytes |
| Unique views | 756 | 343 |
| Unique downloads | 525 | 0 |