Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
2,895
datasets available to search
ShareScore release 0.9.0
Dataset results
2,895 results for “rays”
X-ray tomographic datasets associated with the article "Pore space of in-situ semi-dense asphalt: A characterization by X-ray tomography" (DOI: 10.1016/j.conbuildmat.2024.139091)
<p>This Zenodo repository provides two sets of 3D images, which constitute part of the dataset base for the article titled "Pore space of in-situ semi-dense asphalt: A characterization by X-ray tomography", written by the same authors cited here, together with other co-authors. The article is published in the journal "Construction and Building Materials". It can be reached <em>via</em> the following URL: <a href="https://doi.org/10.1016/j.conbuildmat.2024.139091" target="_blank" rel="noopener">https://doi.org/10.1016/j.conbuildmat.2024.139091</a>.</p> <p>The core specimens were obtained in 2019 from semi-dense asphalt (SDA) pavement sections located in the Swiss Canton of Zürich. For each of three pavement sections, labelled in the following as SDA4-1yr, SD4-5yr and SDA8, 100 mm diameter cores were extracted, both inside (I) and outside (O) of the wheel path, in order to see the effect of the traffic load on the pore space characteristics. Out of the original cores for the SDA4 pavements, 5 30 mm diameter sub-cores were drilled out of their centers, both in- and out-of the wheel path, and investigated with X-ray tomography. Only 1 30 mm core was analyzed for SDA8, both in- and out- of the wheel path. The asphalt in that pavement type has lower porosity, making it less interesting from the sound absorption viewpoint.</p> <p>The whole dataset consists of .7z archive files. Such files have the following designations: SDA_J_K_L_Tomogram.7z or SDA_J_K_L_PoreSpaceBinTomogram.7z, where J = 1,2, K = I,O and L = 1,2,3,4,5. When referring to the specimen naming within the corresponding article, the first index, J, refers to the specimen "age": J = 1 indicates the 1-year old specimens (called SDA4-1yr within the article); J = 2 refers to the 5-year old ones (SDA4-5yr). The second index, K, refers to the location of the specimen within the pavement section course ("I" for in-wheel path and "O" for out-of-wheel path). The final index L just enumerates the distinct specimens of the same group.</p> <p>There are two additional groups of archive files: LNA_I_Tomogram.7z/LNA_I_PoreSpaceBinTomogram.7z refers to the single in-wheel-path, 7-year old specimen (called SDA8 within the article); LNA_O_Tomogram.7z/LNA_O_PoreSpaceBinTomogram.7z refers to the single out-of-wheel path, 7-year old specimen.</p> <p>The two sets/types of 3D images can be recognized by the different file naming.</p> <p>The first set includes the raw X-ray tomograms of the 22 specimens analyzed. Each tomogram is stored in the form of a "stack" (or series) of 16-bit unsigned integer 2D TIFF image file, being one 2D cross-section (also called "slice", in tomographic jargon) from the "tomographed" volume. Such slices are contained in a folder. The folder was then archived in a .7z archive file.</p> <p>The second set of 3D images is characterized by the filename pattern SDA_J_K_L_PoreSpaceBinTomogram.7z. Each zipped folder contains the slices of the binary tomogram of the whole pore space of the respective specimen, segmented according with the 3d image analysis workflow described within the article. Each slice of such tomogram was stored as a 8-bit unsigned integer 2D TIFF image file, whose pixels can have only two possible values: 255, if the pixel is inside the segmented pore space; 0 if the pixel is outside it.</p> <p>Almost all of the acquired tomograms have an isotropic voxel size of 0.0214 mm, meaning that each slice is separated in space from the next one by such distance. The samples SDA_2_O_1 and SDA_2_I_1 have a voxel size of 0.0220 mm, while the sample LNA_I has a voxel size of 0.0223 mm.</p>
Dataset for article "From X-rays to physical parameters: a comprehensive analysis of thermal tidal disruption event X-ray spectra"
<p>This repository contains the data used in the modeling of TDE X-ray emission within the article: Mummery et al. 2023, " From X-rays to physical parameters: a comprehensive analysis of thermal<br> tidal disruption event X-ray spectra" published as Mummery et al. 2023, MNRAS, 519, 5828</p>
Diffuse Emission of High-Energy Neutrinos from a Global Fit to Cosmic Rays
<p>Model of diffuse emission of high-energy neutrinos from a global fit of cosmic rays and model of high-energy neutrino emission from unresolved pulsar-powered sources.</p> <p>The maps presented in the form of <em>HEALPix </em>maps (Gorski et al 2005, ApJ, 622, 759) of per-flavor intensity in units of GeV<sup>-1</sup> cm<sup>-2</sup> s<sup>-1</sup> sr<sup>-1</sup> at 50 logarithmically spaced energies between 10 GeV and 10<sup>8</sup> GeV. We use a value of NSIDE=256 and the RING binning scheme.</p> <p>We here make available our fiducial model, which is calculated assuming the <em>Ferrière 2001</em> cosmic ray source distribution, the <em>AAfrag</em> hadronic production cross sections and the <em>GALPROP</em> gas maps. We calculated the emission from unresolved sources following Vecchiotti et al. 2022, ApJ, 928, 19.</p> <p>In Version 2 of this dataset, we also make available the local cosmic ray fluxes of our fiducial model obtained from a global fit to cosmic ray data together with the corresponding 68% and 95% uncertainty bands. These are shown in figure 6 of <a href="https://arxiv.org/abs/2211.15607">arXiv:2211.15607</a>. The nuclear fluxes are in (GeV/n)<sup>-1</sup> m<sup>-2</sup> s<sup>-1</sup> sr<sup>-1</sup>, the fluxes of electrons and positrons are in GeV<sup>-1</sup> m<sup>-2</sup> s<sup>-1</sup> sr<sup>-1</sup> . The fluxes are local interstellar fluxes without solar modulation.</p> <p>In Version 3 of this dataset, we add the fiducial diffuse gamma ray model calculated assuming the <em>Ferrière 2001</em> cosmic ray source distribution, the <em>AAfrag</em> hadronic production cross sections as well as the <em>GALPROP</em> gas maps and ISRF model. We separately make available 3 maps: The hadronic emission on neutral atomic gas, the hadronic emission on molecular gas and the leptonic emission from Inverse Compton Scattering. </p> <p>Similar to the dataset of the fiducial neutrino model, the maps are presented in the form of <em>HEALPix </em>maps (Gorski et al 2005, ApJ, 622, 759) in units of GeV<sup>-1</sup> cm<sup>-2</sup> s<sup>-1</sup> sr<sup>-1</sup>. We use a value of NSIDE=256 and the RING binning scheme. For the hadronic maps, the intensity is given at 50 logarithmically spaced energies between 10 GeV and 10<sup>8</sup> GeV. For the leptonic maps from Inverse Compton Scattering, the intensity is given at 48 logarithmically spaced energies between 1 GeV and 10<sup>6</sup> GeV.</p> <p>The structure of the files is somewhat different from the file containing the fiducial neutrino model. This is to allow for easy use of the gamma ray maps with the <em>gammapy</em> package (Deil et al. 2017, <a href="https://arxiv.org/abs/1709.01751"> arXiv:1709.01751</a>).</p> <p>Also available in Version 3 are the full spatio-spectral cosmic ray distributions in the Milky Way as predicted by our fiducial model. The nuclear fluxes are given for each species in (GeV/n)<sup>-1</sup> m<sup>-2</sup> s<sup>-1</sup> sr<sup>-1</sup> at 63 energies between 1 GeV and 10<sup>9</sup> GeV. The leptonic fluxes are given for each species in GeV<sup>-1</sup> m<sup>-2</sup> s<sup>-1</sup> sr<sup>-1</sup> at 36 energies between 1 GeV and 10<sup>5</sup> GeV. </p> <p>All fluxes are given on a spatial grid at 81 galactocentric radii from 0 kpc to 20 kpc and 61 distances perpendicular to the galactic plane between -6 kpc and 6 kpc.</p> <p>Finally, a word of caution about the extra component of cosmic ray leptons included in our model: This component is contained in the last <em>HDUnit</em> of the <em>fits</em> file containing the leptonic cosmic ray distributions. It is there denoted as a flux of electrons. It must, however, also be added to the flux of positrons to achieve correct results.</p> <p>Please refer to <a href="https://arxiv.org/abs/2211.15607">arXiv:2211.15607</a> for further details.</p> <p>When using these models in your research work, please refer to this Zenodo dataset and the publication.</p>
Supporting Information for "The First GECAM Observation Results on Terrestrial Gamma-ray Flashes and Terrestrial Electron Beams"
<p><strong>Additional Supporting Information</strong></p> <ol> <li>GECAM_TGF_Catalog.xls</li> <li>GECAM_TEB_Catalog.xls</li> <li>Fig1AC_UT2021-07-05T07-45-41.783530_CPD.xls</li> <li>Fig1AC_UT2021-07-05T07-45-41.783530_GRD.xls</li> <li>Fig1AC_UT2021-07-05T07-45-41.783530_Sim.xls</li> <li>Fig1BD_UT2021-04-26T12-16-34.637228_CPD.xls</li> <li>Fig1BD_UT2021-04-26T12-16-34.637228_GRD.xls</li> <li>Fig1BD_UT2021-04-26T12-16-34.637228_Sim.xls</li> <li>Fig4A_UT2021-02-01T02-09-25.691512_CPD.xls</li> <li>Fig4A_UT2021-02-01T02-09-25.691512_GRD.xls</li> <li>Fig4A_UT2021-02-01T02-09-25.691512_Sim.xls</li> <li>Fig4B_UT2021-07-10T21-19-04.519543_CPD.xls</li> <li>Fig4B_UT2021-07-10T21-19-04.519543_GRD.xls</li> <li>Fig4B_UT2021-07-10T21-19-04.519543_Sim.xls</li> <li>Fig4C_UT2022-01-22T22-24-49.664579_CPD.xls</li> <li>Fig4C_UT2022-01-22T22-24-49.664579_GRD.xls</li> <li>Fig4C_UT2022-01-22T22-24-49.664579_Sim.xls</li> <li>Fig4D_UT2021-03-07T19-13-49.995485_CPD.xls</li> <li>Fig4D_UT2021-03-07T19-13-49.995485_GRD.xls</li> <li>Fig4D_UT2021-03-07T19-13-49.995485_Sim.xls</li> <li>Fig4E_UT2021-03-29T06-56-37.831848_CPD.xls</li> <li>Fig4E_UT2021-03-29T06-56-37.831848_GRD.xls</li> <li>Fig4E_UT2021-03-29T06-56-37.831848_Sim.xls</li> <li>Fig4F_UT2021-08-14T09-54-29.177203_CPD.xls</li> <li>Fig4F_UT2021-08-14T09-54-29.177203_GRD.xls</li> <li>Fig4F_UT2021-08-14T09-54-29.177203_Sim.xls</li> <li>Fig4G_UT2021-08-16T17-02-27.908009_CPD.xls</li> <li>Fig4G_UT2021-08-16T17-02-27.908009_GRD.xls</li> <li>Fig4G_UT2021-08-16T17-02-27.908009_Sim.xls</li> <li>Fig4H_UT2022-03-29T08-56-28.599361_CPD.xls</li> <li>Fig4H_UT2022-03-29T08-56-28.599361_GRD.xls</li> <li>Fig4H_UT2022-03-29T08-56-28.599361_Sim.xls</li> <li>Fig5C_UT2021-09-11T18-34-40.551997_CPD.xls</li> <li>Fig5C_UT2021-09-11T18-34-40.551997_GRD.xls</li> <li>Fig5C_UT2021-09-11T18-34-40.551997_Sim.xls</li> <li>Fig5D_UT2021-07-10T01-46-36.709997_CPD.xls</li> <li>Fig5D_UT2021-07-10T01-46-36.709997_GRD.xls</li> <li>Fig5D_UT2021-07-10T01-46-36.709997_Sim.xls</li> <li>Fig5A_UT2021-10-27T22-49-33.082008_CPD.xls</li> <li>Fig5A_UT2021-10-27T22-49-33.082008_GRD.xls</li> <li>Fig5A_UT2021-10-27T22-49-33.082008_Sim.xls</li> <li>Fig5B_UT2022-07-26T00-16-13.728010_CPD.xls</li> <li>Fig5B_UT2022-07-26T00-16-13.728010_GRD.xls</li> <li>Fig5B_UT2022-07-26T00-16-13.728010_Sim.xls</li> <li>Fig5EF_WWLLN_Lightning.txt</li> <li>GLD360data_forTGFUTC2021-02-22T00-17-18.034461.xlsx</li> <li>GLD360data_forTGFUTC2021-03-07T19-13-49.995436.xlsx</li> <li>GLD360data_forTGFUTC2021-03-25T09-48-08.785508.xlsx</li> <li>GLD360data_forTGFUTC2021-03-29T06-56-37.830006.xlsx</li> <li>GLD360data_forTGFUTC2021-04-17T20-10-34.446509.xlsx</li> <li>GLD360data_forTGFUTC2021-04-25T23-07-27.616005.xlsx</li> <li>GLD360data_forTGFUTC2021-04-29T18-12-43.227007.xlsx</li> <li>GLD360data_forTGFUTC2021-05-09T19-50-01.720689.xlsx</li> <li>GLD360data_forTGFUTC2021-05-10T21-38-43.498955.xlsx</li> <li>GLD360data_forTGFUTC2021-05-10T21-43-27.914962.xlsx</li> <li>GLD360data_forTGFUTC2021-05-12T09-58-08.470159.xlsx</li> <li>GLD360data_forTGFUTC2021-05-15T08-38-22.505997.xlsx</li> <li>GLD360data_forTGFUTC2021-05-16T08-43-35.339273.xlsx</li> <li>GLD360data_forTGFUTC2021-06-20T15-37-51.777130.xlsx</li> <li>GLD360data_forTGFUTC2021-06-21T22-38-57.377719.xlsx</li> <li>GLD360data_forTGFUTC2021-07-22T23-38-31.513009.xlsx</li> <li>GLD360data_forTGFUTC2021-08-16T15-11-40.193070.xlsx</li> <li>GLD360data_forTGFUTC2021-09-24T13-55-59.153000.xlsx</li> <li>GLD360data_forTGFUTC2021-10-05T10-16-04.302001.xlsx</li> <li>GLD360data_forTGFUTC2021-11-09T03-10-44.188748.xlsx</li> <li>GLD360data_forTGFUTC2021-12-04T01-37-23.893950.xlsx</li> <li>GLD360data_forTGFUTC2021-12-06T12-15-46.564243.xlsx</li> <li>GLD360data_forTGFUTC2021-12-12T21-41-33.038999.xlsx</li> <li>GLD360data_forTGFUTC2021-12-13T23-34-18.149995.xlsx</li> <li>GLD360data_forTGFUTC2021-12-22T19-36-38.765547.xlsx</li> <li>GLD360data_forTGFUTC2021-12-28T03-16-31.018224.xlsx</li> <li>GLD360data_forTGFUTC2022-02-16T15-26-20.379956.xlsx</li> <li>GLD360data_forTGFUTC2022-03-09T04-37-21.765997.xlsx</li> <li>GLD360data_forTGFUTC2022-03-11T04-56-30.604005.xlsx</li> <li>GLD360data_forTGFUTC2022-03-17T23-01-55.158520.xlsx</li> <li>GLD360data_forTGFUTC2022-03-26T20-48-39.098469.xlsx</li> <li>GLD360data_forTGFUTC2022-03-27T19-13-33.058448.xlsx</li> <li>GLD360data_forTGFUTC2022-03-30T19-35-55.714452.xlsx</li> <li>GLD360data_forTGFUTC2022-04-20T20-47-17.811510.xlsx</li> <li>GLD360data_forTGFUTC2022-05-03T03-38-25.725991.xlsx</li> <li>GLD360data_forTGFUTC2022-05-13T20-32-32.157110.xlsx</li> <li>GLD360data_forTGFUTC2022-05-13T20-36-38.126223.xlsx</li> <li>GLD360data_forTGFUTC2022-06-15T18-06-04.110702.xlsx</li> <li>GLD360data_forTGFUTC2022-06-24T10-42-13.680445.xlsx</li> <li>GLD360data_forTGFUTC2022-06-25T09-09-44.289205.xlsx</li> <li>GLD360data_forTGFUTC2022-07-20T20-59-28.784931.xlsx</li> </ol> <p> </p> <p><strong>Data </strong><strong>D</strong><strong>escription</strong></p> <p>We have uploaded 86 data files. These are:</p> <ol> <li>The list of 147 TGFs observed by GECAM from December 10, 2020 until August 31, 2022. The file includes information about a) the UTC time of observation, b) the longitude, latitude and altitude of the GECAM position, c) the duration calculated by the Bayesian Block algorithm, d) the number of net counts, e) the hardness ratio (energy limitation 200 keV), f) the CPD/GRD counts ratio. These data were used to produce Figure 1 and Figure 2.</li> <li>The list of 2 typical TEBs and 2 TEB-like events observed by GECAM from December 10, 2020 until August 31, 2022. The file includes information about a) the UTC time of observation, b) the longitude, latitude and altitude of the GECAM position, c) the duration calculated by the Bayesian Block algorithm, d) the CPD/GRD counts ratio, e) the longitude and latitude of the northern and sourthern magnetic footpoint. These data were used to produce Figure 1 and Figure 2.</li> <li>The CPD data of a cosmic-ray event. The CPD data include: a) the relative time to reference time (UT 2021-07-05T07:45:41.783530), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure S1A&S1C.</li> <li>The GRD data of a cosmic-ray event. The GRD data include: a) the relative time to reference time (UT 2021-07-05T07:45:41.783530), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure S1A&S1C.</li> <li>The SimEvt data of a cosmic-ray event. The CPD data include: a) the relative time to reference time (UT 2021-07-05T07:45:41.783530), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure S1A&S1C.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-04-26T12:16:34.637228), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure S1B&S1D.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-04-26T12:16:34.637228), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure S1B&S1D.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-04-26T12:16:34.637228), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure S1B&S1D.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-02-01T02:09:25.691512), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3A.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-02-01T02:09:25.691512), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3A.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-02-01T02:09:25.691512), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3A.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-07-10T21:19:04.519543), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3B.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-07-10T21:19:04.519543), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3B.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-07-10T21:19:04.519543), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3B.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2022-01-22T22:24:49.664579), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3C.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2022-01-22T22:24:49.664579), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3C.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2022-01-22T22:24:49.664579), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3C.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-03-07T19:13:49.995485), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3D.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-03-07T19:13:49.995485), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3D.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-03-07T19:13:49.995485), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3D.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-03-29T06:56:37.831848), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3E.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-03-29T06:56:37.831848), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3E.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-03-29T06:56:37.831848), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3E.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-08-14T09:54:29.177203), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3F.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-08-14T09:54:29.177203), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3F.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-08-14T09:54:29.177203), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3F.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-08-16T17:02:27.908009), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3G.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-08-16T17:02:27.908009), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3G.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-08-16T17:02:27.908009), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3G.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2022-03-29T08:56:28.599361), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3H.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2022-03-29T08:56:28.599361), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3H.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2022-03-29T08:56:28.599361), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3H.</li> <li>The CPD data of a TEB-like event. The CPD data include: a) the relative time to reference time (UT 2021-09-11T18:34:40.551997), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 4C.</li> <li>The GRD data of a TEB-like event. The GRD data include: a) the relative time to reference time (UT 2021-09-11T18:34:40.551997), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 4C.</li> <li>The SimEvt data of a TEB-like event. The CPD data include: a) the relative time to reference time (UT 2021-09-11T18:34:40.551997), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 4C.</li> <li>The CPD data of a TEB-like event. The CPD data include: a) the relative time to reference time (UT 2021-07-10T01:46:36.709997), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 4D.</li> <li>The GRD data of a TEB-like event. The GRD data include: a) the relative time to reference time (UT 2021-07-10T01:46:36.709997), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 4D.</li> <li>The SimEvt data of a TEB-like event. The CPD data include: a) the relative time to reference time (UT 2021-07-10T01:46:36.709997), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 4D.</li> <li>The CPD data of a typical TEB event. The CPD data include: a) the relative time to reference time (UT 2021-10-27T22:49:33.082008), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 4A.</li> <li>The GRD data of a typical TEB event. The GRD data include: a) the relative time to reference time (UT 2021-10-27T22:49:33.082008), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 4A.</li> <li>The SimEvt data of a typical TEB event. The CPD data include: a) the relative time to reference time (UT 2021-10-27T22:49:33.082008), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 4A.</li> <li>The CPD data of a typical TEB event. The CPD data include: a) the relative time to reference time (UT 2022-07-26T00:16:13.728010), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 4B.</li> <li>The GRD data of a typical TEB event. The GRD data include: a) the relative time to reference time (UT 2022-07-26T00:16:13.728010), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 4B.</li> <li>The SimEvt data of a typical TEB event. The CPD data include: a) the relative time to reference time (UT 2022-07-26T00:16:13.728010), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 4B.</li> <li>The specific WWLLN data of the TEB-like event UT 2021-09-11T18:34:40.551997. The WWLLN data include: a) WWLLN Lighning UT Time, b) WWLLN Lighning UNIX Time, c) WWLLN Lighning Longitude (deg) , d) WWLLN Lighning Latitude (deg) , e) WWLLN Lighning Energy (J) , f) WWLLN Lighning Energy Error (J). Data are used in Figure 4E&4F.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-02-22T00:17:18.034461 +/- 1 minute. The GECAM-B nadir (129.7E, 10.9N) of this TGF is located in the east Asia region (EAR, 77E-138E, 13S-30N). The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg) , c) Lighning Peak Current (kA) , d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-03-07T19:13:49.995436 +/- 1 minute. The GECAM-B nadir (92.2E, 4.7N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-03-25T09:48:08.785508 +/- 1 minute. The GECAM-B nadir (101.4E, 3.5N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-03-29T06:56:37.830006 +/- 1 minute. The GECAM-B nadir (105.0E, 2.4S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-04-17T20:10:34.446509 +/- 1 minute. The GECAM-B nadir (131.0E, 2.4N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>51) The specific GLD360 data near GECAM TGF UT 2021-04-25T23:07:27.616005 +/- 1 minute. The GECAM-B nadir (117.1E, 29.0N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>52) The specific GLD360 data near GECAM TGF UT 2021-04-29T18:12:43.227007 +/- 1 minute. The GECAM-B nadir (77.9E, 5.3N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-05-09T19:50:01.720689 +/- 1 minute. The GECAM-B nadir (119.4E, 15.5N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-05-10T21:38:43.498955 +/- 1 minute. The GECAM-B nadir (105.2E, 5.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-05-10T21:43:27.914962 +/- 1 minute. The GECAM-B nadir (119.5E, 3.5S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-05-12T09:58:08.470159 +/- 1 minute. The GECAM-B nadir (122.8E, 12.9N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-05-15T08:38:22.505997 +/- 1 minute. The GECAM-B nadir (115.3E, 10.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-05-16T08:43:35.339273 +/- 1 minute. The GECAM-B nadir (103.6E, 8.5N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-06-20T15:37:51.777130 +/- 1 minute. The GECAM-B nadir (128.0E, 21.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-06-21T22:38:57.377719 +/- 1 minute. The GECAM-B nadir (124.4E, 13.3N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-07-22T23:38:31.513009 +/- 1 minute. The GECAM-B nadir (117.2E, 16.3N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-08-16T15:11:40.193070 +/- 1 minute. The GECAM-B nadir (126.9E, 28.8N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-09-24T13:55:59.153000 +/- 1 minute. The GECAM-B nadir (131.1E, 5.2N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-10-05T10:16:04.302001 +/- 1 minute. The GECAM-B nadir (115.3E, 10.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-11-09T03:10:44.188748 +/- 1 minute. The GECAM-B nadir (114.8E, 6.6N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-12-04T01:37:23.893950 +/- 1 minute. The GECAM-B nadir (126.7E, 10.5S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-12-06T12:15:46.564243 +/- 1 minute. The GECAM-B nadir (128.9E, 10.6N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-12-12T21:41:33.038999 +/- 1 minute. The GECAM-B nadir (119.0E, 11.2S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-12-13T23:34:18.149995 +/- 1 minute. The GECAM-B nadir (117.0E, 7.2N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-12-22T19:36:38.765547 +/- 1 minute. The GECAM-B nadir (104.2E, 3.4N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-12-28T03:16:31.018224 +/- 1 minute. The GECAM-B nadir (117.7E, 3.4N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-02-16T15:26:20.379956 +/- 1 minute. The GECAM-B nadir (102.0E, 3.6S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-03-09T04:37:21.765997 +/- 1 minute. The GECAM-B nadir (109.5E, 5.3S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-03-11T04:56:30.604005 +/- 1 minute. The GECAM-B nadir (114.3E, 8.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-03-17T23:01:55.158520 +/- 1 minute. The GECAM-B nadir (120.4E, 9.7S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-03-26T20:48:39.098469 +/- 1 minute. The GECAM-B nadir (111.5E, 3.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-03-27T19:13:33.058448 +/- 1 minute. The GECAM-B nadir (113.7E, 5.0S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-03-30T19:35:55.714452 +/- 1 minute. The GECAM-B nadir (102.1E, 4.0N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-04-20T20:47:17.811510 +/- 1 minute. The GECAM-B nadir (104.9E, 1.8S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-05-03T03:38:25.725991 +/- 1 minute. The GECAM-B nadir (109.0E, 11.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>81) The specific GLD360 data near GECAM TGF UT 2022-05-13T20:32:32.157110 +/- 1 minute. The GECAM-B nadir (115.8E, 0.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-05-13T20:36:38.126223 +/- 1 minute. The GECAM-B nadir (128.2E, 7.4N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-06-15T18:06:04.110702 +/- 1 minute. The GECAM-B nadir (109.7E, 10.9S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-06-24T10:42:13.680445 +/- 1 minute. The GECAM-B nadir (116.8E, 10.4N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-06-25T09:09:44.289205 +/- 1 minute. The GECAM-B nadir (127.3E, 13.2N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-07-20T20:59:28.784931 +/- 1 minute. The GECAM-B nadir (97.4E, 22.8N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> </ol>
Platinum-Iron(II) Oxide Sites Directly Responsible for Preferential Carbon Monoxide Oxidation at Ambient Temperature: An Operando X-ray Absorption Spectroscopy Study
<p>Open data for "Platinum-Iron(II) Oxide Sites Directly Responsible for Preferential Carbon Monoxide Oxidation at Ambient Temperature: An Operando X-ray Absorption Spectroscopy Study" Angew. Chem.Int. Ed. 2023,62, e202214032(1 of 11) <a href="https://doi.org/10.1002/anie.202214032">https://doi.org/10.1002/anie.202214032</a></p>
X-ray Fluorescence Ghost Imaging - CuSn mask - Three Wires (Fe & Cu)
<p>X-ray Fluorescence Ghost Imaging (XRF-GI) dataset of three wires (one Fe, and two Cu) in a plastic capillary. The capillary contains trace elements like Zn, Zr, etc.</p> <p>The GI scan is presented in the following article <a title="Synchrotron-based x ray fluorescence ghost imaging" href="https://doi.org/10.1364/OL.499046">10.1364/OL.499046</a>. A total of 896 GI realizations were taken, organized into 16 vertical translations and 56 horizontal translations of the structuring element (CuSn mask).<br>The dataset contains both the sample transmission images and the masks plus sample transmission images. No images of the masks are provided (they need to be computed).</p> <p>The data is organized in an HDF5 file, under the following structure:</p> <pre><code>dataset_CuSn-mask_3wires.h5 │ ├data │ ├flat_panel │ │ ├dark [float32: 16 × 170 × 350] │ │ ├empty_beam [float32: 170 × 350] │ │ ├sample [float32: 16 × 170 × 350] │ │ └sample_and_masks [float32: 16 × 56 × 170 × 350] │ └xrf [float32: 16 × 56 × 4096] │ └metadata └xrf ├bias_keV [float64: scalar] ├gain_keV [float64: scalar] └ranges ├Ca [int64: 2] ├Cu [int64: 2] ├Fe [int64: 2] ├Si [int64: 2] ├Ti [int64: 2] ├Zn [int64: 2] └Zr [int64: 2] </code></pre> <p>The meaning of the paths is:</p> <ul> <li><code>/data/xrf</code> contains the XRF spectra for each GI realization</li> <li><code>/data/flat_panel/dark</code> contains the dark images of each scan line (no beam)</li> <li><code>/data/flat_panel/empty_beam</code> contains the empty beam (no sample & no masks) intensity distribution</li> <li><code>/data/flat_panel/sample</code> contains the transmission images of the sample at each scan line</li> <li><code>/data/flat_panel/sample</code>_and_masks contains the transmission images of the sample and masks at each GI realization</li> <li><code>/metadata/xrf/bias_keV</code> contains the bias in keV of the XRF spectrum</li> <li><code>/metadata/xrf/gain_keV</code> contains the gain in keV of each XRF energy bin</li> <li><code>/metadata/xrf/ranges/</code> contains the bin ranges for interesting K<sub>alpha</sub> elemental emission lines in the XRF spectrum</li> </ul> <p>For further information we refer to the associated publication.</p> <p>The data can be processed with structured illumination routines of the code at: <a href="https://github.com/cicwi/PyCorrectedEmissionCT">https://github.com/cicwi/PyCorrectedEmissionCT</a>.</p>
Probability of Detection applied to X-ray inspection using numerical simulations
<p>In this work, we apply and adapt established Probability of Detection (POD) methods on inline inspection of aluminium cylinder heads using X-ray computed tomography. The CT simulation tool SimCT [4] is used to acquire virtual images of the specimens including artificial defects, which avoids the manufacturing of calibrated defects of known type (e.g., pore, inclusion, crack etc.), size and location. One of the exemplary defects is discussed as representative result together with the generated POD curves as well as its characteristics (i.e., the minimum detected defect, the maximum missed defect, POD(a90) =0.90 and a90/95).</p>
Out-of-equilibrium charge redistribution data in a copper-oxide based superconductor by time-resolved X-ray photoelectron spectroscopy
<p>This dataset was measured using a momentum microscope by time-resolved X-ray photoelectron spectroscopy (XPS) on the prototypical high-temperature superconductor: optimally doped BSCCO at FEL FLASH, DESY in Hamburg. With time-resolved XPS, unique access to the dynamics of individual atoms in the unit cell is granted by means of chemical shifts of the core levels. Though the induced changes are small, with a rigorous fitting procedure, it is possible to extract significant changes observed mainly at the oxygen atoms in the copper oxide planes, while other oxygen atoms as well as strontium remain largely unaffected. Although it was acquired not in the superconducting phase, the observed dynamics point to a significant coupling of energy scales involving charge-transfer processes and optical excitations. Such findings can thus provide another puzzle piece for a better understanding of high-temperature superconductivity.</p>
A high-throughput 3D X-ray histology facility for biomedical research and preclinical applications - Underlying Data
<p><strong>Video files and logs</strong></p> <p>Single-slice and thick-slice roll* source videos are included. Each video is accompanied by a .txt log that contains information about the source file, slice thickness, and a brief description of the visualization mode.</p> <p>List of files:</p> <ul> <li>20211019-23h59m_20xAvgInt.mp4</li> <li>20211019-23h59m_20xAvgInt.txt</li> <li>20211019-23h59m_20xMaxInt.mp4</li> <li>20211019-23h59m_20xMaxInt.txt</li> <li>20211019-23h59m_20xStDev.mp4</li> <li>20211019-23h59m_20xStDev.txt</li> <li>20211019-23h59m_XYSliceRoll.mp4</li> <li>20211019-23h59m_XYSliceRoll.txt</li> <li>20211019-23h59m_XZSliceRoll.mp4</li> <li>20211019-23h59m_XZSliceRoll.txt</li> <li>20211019-23h59m_YZSliceRoll.mp4</li> <li>20211019-23h59m_YZSliceRoll.txt</li> </ul> <p>* <em>Thick-slice rolling is a 2D thick-slice viewing that allows rolling of a pre-selected number of slices (n) along the z-axis of the 3D data. A single thick-slice roll forwards is accomplished by translating the thick-slice by one single slice forwards; that is moving forward by one (+1) slice from the first and nth element and reapplying the criteria or operations to the new slice sub-stack.</em></p> <p><strong>Volume XRH data</strong><br> These are processed raw volume file saved in .raw and/or .tiff format, which are resliced to a histology-relevant orientation and/or have been enhanced using noise reduction (3D median filter) and/or ct-artefact removal techniques (e.g. cBC identifies a bandpass filter used to remove intensity variations originating from the histology cassette).</p> <p>List of volume files:</p> <ul> <li><strong>32220_20200703_XRH_2504_OLK_DEMO02019-FFPE_1620x1959x164x16bit.raw</strong> <ul> <li>sample: Human lung adenocarcinoma</li> <li>histology-relevant resliced volume (2x2x2 3D medial filter applied)</li> <li>import as 1620 x 1959 x 164 x 16-bit, big-endian; voxel edge size (mm): 0.0160042 isotropic</li> </ul> </li> <li><strong>cBC_32220_20200703_XRH_2504_OLK_DEMO02019-FFPE_1588x1674x164x16bit.raw</strong> <ul> <li>sample: Human lung adenocarcinoma</li> <li>cassette artefacts background correction (bandpass) of volume 32220_20200703_XRH_2504_OLK_DEMO02019-FFPE_1620x1959x164x16bit.raw</li> <li>import as 1620 x 1959 x 164 x 16-bit, big-endian; voxel edge size (mm): 0.0160042 isotropic</li> </ul> </li> <li><strong>Med3D_HPass_2111_20190606_MEDX_2234_EH_HN2_recon_2000x1952x501x32bit.raw</strong> <ul> <li>sample: Human head and neck tumour</li> <li>histology-relevant resliced volume (1x1x1 3D medial filter applied)</li> <li>import as 2000 x 1952 x 501 x 32-bit, big-endian; voxel edge size (mm): 0.00999782 isotropic</li> </ul> </li> </ul> <p><strong>Conventional Histology and correlative imaging</strong></p> <ul> <li><strong>HN2_Level001_MEDX080_Manual_BW_Series4.tif</strong> <ul> <li>H&E histology slice of the human head and neck tumour sample shown in "Med3D_HPass_2111_20190606_MEDX_2234_EH_HN2_recon_2000x1952x501x32bit.raw"</li> </ul> </li> <li><strong>HN2_Level001_MEDX080_Manual_BW</strong> <ul> <li>manual landmark selection used for registering the conventional histology slice onto the μCT slice</li> </ul> </li> <li><strong>HN2_MEDX_rotated_0080.tif</strong> <ul> <li>Slice 80 from volume "Med3D_HPass_2111_20190606_MEDX_2234_EH_HN2_recon_2000x1952x501x32bit.raw" that corresponds to histological slice "HN2_Level001_MEDX080_Manual_BW"</li> </ul> </li> </ul>
Supplementary Data for Low-loss stable storage of 1.2 Angstrom X-ray pulses in a 14 m Bragg cavity
<p>Supplementary Data for Margraf, R. et al. "Low-loss stable storage of 1.2 Angstrom X-ray pulses in a 14 m Bragg cavity," Nature Photonics, 2023.</p>
PTX-498: A multi-center pneumothorax segmentation chest X-ray image dataset
<p>Pneumothorax is a common medical emergency defined as the abnormal collection of air in the pleural space between the lung and chest wall. Its typical symptoms include chest pain and dyspnea, leading to oxygen deficiency or even life-threatening in severe cases. Therefore, an efficient and automatic pneumothorax diagnosis algorithm would be useful in many clinical scenarios. Recently, deep learning methods have achieved impressive progress in medical image segmentation tasks. However, a large-scale dataset is one of the critical components for the success of deep learning. On the other hand, there are few public chest X-ray images with pneumothorax.</p> <p>To stimulate the researchers' interest in the pneumothorax diagnosis algorithm, <strong>we released a new data set PTX-498 here. It contains 498 chest X-ray images of pneumothorax collected from three hospitals, and each image contains pixel-level annotations.</strong> All images were resized to 1024×1024. The raw image intensity was clipped according to the window width and level inside the dicom tag and then normalized to 0 to 255. The contours of the pneumothorax area were labelled by two senior radiologists using ITK-SNAP. The dataset was anonymized and every record related to patients' privacy was removed. Only the image data and the corresponding labels were included in PTX-498.</p> <p><strong>Please use the latest v2-fix version which removes duplicate images and uses the window width and level from the original dicom tag for normalization.</strong></p> <p><strong>Citation: If you are interested in this dataset and applying it in your research, please cite the following article.</strong><br> Paper link: https://doi.org/10.1016/j.neucom.2021.05.029<br> Cite this article as Yunpeng Wang, Kang Wang, Xueqing Peng, Lili Shi, Jing Sun, Shibao Zheng, Fei Shan, Weiya Shi, Lei Liu*. DeepSDM: Boundary-aware pneumothorax segmentation in chest X-ray images [J]. Neurocomputing, 2021, 454: 201-211.</p> <div> <div class="gtx-trans-icon"> </div> </div>
Hyperspectral 2D fan-beam X-ray CT dataset of 5 materials
<p>Hyperspectral X-ray CT dataset acquired at the DTU 3D imaging center. The phantom consists of 5 materials: Aluminium (10 mm) and PVC (7.8 mm) in solid blocks. Sugar, H2O2, and H2O in circular glass containers.</p> <p>3D array with dimension: 128 x 370 x 258 < channel, angle, horizontal ></p> <p> </p> <p>Detector parameters:</p> <p>Number of detector pixels: 258 (concatenated from 2 detector modules with 128 pixels each and 2 pixel interpolated across a gap between detectors)</p> <p>Pixel size: 0.077 cm</p> <p>Sep=0.153 Pixels' gap length (cm)</p> <p>det_space=(ndet)*pixel_size+Sep # physical width of detector in cm (pixels*pixel_size), including the gap</p> <p> </p> <p>Acquisition Parameters</p> <p>360 # Angular span of projections in degrees</p> <p>370 # Number of projections. note: last projection taken is not a duplicate of the first projection. At angle: 360/370 degrees from first projection.</p> <p>115.0 # Source-Detector distance in cm</p> <p>0 # Vertical source shift from perfect placement</p> <p>0 # Vertical detector shift from perfect placement</p> <p>57.5 # Source-AxisOfRotation distance in cm</p> <p> </p> <p>rot_axis_x = 0 # x-position offset of AxisOfRotation</p> <p>rot_axis_y = 0 # y-position offset of AxisOfRotation</p>
small angle x-ray scattering from Zr-Cu-Ag metallic glass coatings
<p>small angle x-ray scattering from Zr-Cu-ag metallic glass coating to confirm whether they became amorphous or not. The coating is on PBT substrate. </p>
X-ray and optical light curves of the M dwarf dipper star TIC 234284556
<p>We observed the star TIC 234284556 with XMM-Newton in soft X-rays and in the optical for ca. 35 hours (127.8 ks), starting 2022-04-16 22:58:46, ObsID 0881050101.</p> <p>We provide here two extracted soft X-ray light curves (energy band 0.2-2 keV) collected with XMM-Newton's PN camera, namely for a circular extraction region with 20 arcsec radius centered on the position of the M dwarf star TIC 234284556 (pn_lca_02_2.fits) with 100 seconds time binning, and a background light curve with the same energy range and time binning extracted for a PN background region with a three times larger radius (pn_lcabg_02_2.fits). We also provide optical light curves in the V band, collected with XMM-Newton's Optical Monitor with 10 seconds cadence (file names P0881050101OMS0**TIMESR0000.FIT).</p> <p>A barycentric correction, using the XMM-SAS task "barycen", has been applied to the PN and OM time columns. The time coordinate is given in seconds since BJD 2450814.5 (1998-01-01 00:00:00).</p>
Diffraction data underpinning the structure of StayGold determined by X-ray crystallography (PDB code 8BXT)
<p>Raw diffraction data underpinning the crystal structure of StayGold fluorescent protein.</p> <p>This is the raw data underpinning PDB entry 8BXT.</p>
Reproduction package for the publication 'Prospects for detecting the circum- and intergalactic medium in X-ray absorption using the extended intracluster medium as a backlight'
<p>The uploaded files can be used to reproduce the dataset and figures in the paper<strong> Prospects for detecting the circum- and intergalactic medium in X-ray absorption using the extended intracluster medium as a backlight</strong> by Lýdia Štofanová, Aurora Simionescu, Nastasha A. Wijers, Joop Schaye, Jelle Kaastra, Yannick M. Bahé, and Andrés Arámburo-García.</p><p>NOTE: Files will be published with a new version. </p>
Supplementary Materials for "Simultaneous single-shot radiographic imaging using a laser-driven x-ray and proton micro-source"
<p>Simulation Data Repository, please read the contained README file in the contained simulation/ directory.</p> <p>This directory contains a copy of the used PIConGPU source code, version 0.5.0-dev-60ad9eb85 and analysis scripts.</p> <p>The PIConGPU source code is archived including its complete git history (git version 2.17.1) in source/picongpu.tar.gz with the input parameter template inside in share/picongpu/examples/Wneedle .</p> <p>Generally, PIConGPU source code is available via <a href="https://doi.org/10.5281/zenodo.591746">https://doi.org/10.5281/zenodo.591746</a> with its public git repository being maintained on <a href="https://github.com/ComputationalRadiationPhysics/picongpu">https://github.com/ComputationalRadiationPhysics/picongpu</a> .</p> <p>The two simulations’ exact input is modified accordingly in the directory input/ inside: 2D_a0-45_Z-10_ppc-20_002_light.tar.gz (p-polarized; along X) 2D_a0-45_Z-10_ppc-20_003_light.tar.gz (s-polarized; along Z).</p> <p>“Heavy” simulation data (checkpoints in simOutput/checkpoints/, full-resolution field and particle output in simOutput/bp/ ) has been stripped from this archive and are archived on NERSC’s HPSS tape archive.</p> <p>Analysis scripts are provided as Jupyter notebooks (DensityPlot_polX.ipynb and DensityPlot_polZ.ipynb) and depend on the following software:</p> <p>- adios 1.13.1 python bindings with enabled c-blosc transformations<br> - numpy 1.17.1<br> - matplotlib 3.1.1<br> - PIConGPU post-processing helper modules located in each simulation root directory under “input/lib/python/”<br> <br> The detailed conda environment can be found in the README.</p>
IODP Expedition 361 X-ray diffraction (XRD)
<p>X-ray diffraction (XRD) is used to identify minerals and their proportions in sediment or hard rock sample powders on a Bruker AXS D4 Endeavor X-ray diffractometer. Results are returned as diffractograms in a viewable format (either PDF or PNG).</p>
Data Accompanying "Dynamics of Water Absorption in Callovo-Oxfordian Claystone Revealed With Multimodal X-Ray and Neutron Tomography"
<p>These are the datasets analysed in the publication "Dynamics of Water Absorption in<br> Callovo-Oxfordian Claystone Revealed With Multimodal X-Ray and Neutron Tomography" by Stavropoulou <em>et al.</em> in 2020 in Frontiers in Earth Science, DOI: <a href="https://doi.org/10.3389/feart.2020.00006">https://doi.org/10.3389/feart.2020.00006</a></p> <ol> <li>File 1 contains the 3D reconstructed x-ray and neutron tomography volumes analysed in the paper. State 002 is taken as a reference and the greylevels of all images in the times series for both x-ray and neutrons are rescaled using two characteristic image features (top-cap and air in the case of x-rays) linearly to align with 002. Neutron volumes are rescaled to the same pixel size as 2-bin x-ray volumes, and a mean registration is applied to align neutrons with x-rays.<br> Furthermore, a bilateral filter is applied to the neutron tomographies (domain sigma = 1, range sigma=3000).<br> Full scale images are available at <a href="https://doi.ill.fr/10.5291/ILL-DATA.UGA-42">https://doi.ill.fr/10.5291/ILL-DATA.UGA-42</a><br> </li> <li>File 2 contains the joint histograms for registered pairs of images, as visible in Figure 4 and Figure 5.<br> </li> <li>File 3 contains the results of the digital volume correlation performed with the <a href="https://ttk.gricad-pages.univ-grenoble-alpes.fr/spam/intro.html">spam</a> tookit.<br> The overall "registration" is used to create Figure 6<br> The global correlations available in "gdic" are used to create Figures 7, 8 and 9.</li> </ol>
Fig. 3 in Use of a nursery area by cownose rays (Rhinopteridae) in southeastern Brazil
Fig. 3. Methods to collect data of individuals: (top) information provided by fishermen (reports, pictures, and videos) and (down) field sampling by researchers.
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.