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.
316
datasets available to search
ShareScore release 0.9.0
Dataset results
316 results for “gamma rays”
Data in New $^{63}$Ga(p,$\gamma$)$^{64}$Ge and $^{64}$Ge(p,$\gamma$)$^{65}$As reaction rates corresponding to the temperature regime of thermonuclear X-ray bursts
<p>Abstract quoted from <a href="https://doi.org/10.1103/PhysRevC.110.065804" target="_blank" rel="noopener">Physical Review C 110 (2024) 065804</a> [<a href="https://arxiv.org/abs/2406.14624">arXiv:2406.14624</a>] </p> <p>We compute the $^{63}$Ga(p,$\gamma$)$^{64}$Ge and $^{64}$Ge(p,$\gamma$)$^{65}$As thermonuclear reaction rates using the latest experimental input supplemented with theoretical nuclear spectroscopic information. The experimental input consists of the latest proton thresholds of $^{64}$Ge and $^{65}$As, and the nuclear spectroscopic information of $^{65}$As, whereas the theoretical nuclear spectroscopic information for $^{64}$Ge and $^{65}$As are deduced from the full <em>pf</em>-shell space configuration-interaction shell-model calculations with the GXPF1A Hamiltonian. Both thermonuclear reaction rates are determined with known uncertainties at the energies that correspond to the Gamow windows of the temperature regime relevant to type I x-ray bursts, covering the typical temperature range of the thermonuclear runaway of the GS 1826$-$24 periodic bursts and SAX J1808.4$-$3658 photospheric radius expansion bursts. </p>
Simulation of the Galactic field millisecond pulsar population and its gamma- and X-ray emission
<p>Monte Carlo simulation of the millisecond pulsar population in the Galactic field. The simulation includes four spatial components:</p> <ul> <li>the disk;</li> <li>the boxy bulge;</li> <li>the nuclear stellar cluster;</li> <li>the nuclear stellar disk.</li> </ul> <p>The last 3 components together form the Galactic bulge. There is one file per component, each containing at least 100 Monte Carlo simulations. Each line contains:</p> <ul> <li>the longitude L in deg;</li> <li>the latitude B in deg;</li> <li>the line of sight S in kpc;</li> <li>the 0.1-100 GeV gamma-ray flux in erg/cm^2/s;</li> <li>the X-ray spectral index;</li> <li>the gamma-to-X flux ratio, where the gamma-ray flux is the same as in the fourth column and the X-ray flux is the 2-10 keV unabsorbed one</li> </ul> <pre>of a simulated MSP. More information about the simulation can be found in the related paper. </pre>
The short gamma-ray burst population in a quasi-universal jet scenario: MCMC chains
<p>The paper "The short gamma-ray burst population in a quasi-universal jet scenario" (https://arxiv.org/abs/2306.15488) described an effort in modelling the short gamma-ray burst population under the assumption that all jets share the same angular profile.</p> <p>This repository contains <strong>emcee </strong>hdf5 files with the MCMC chains corresponding to the "full sample" and "flux-limited sample" analyses described in the paper.</p>
Data suppporting Thomas, Atri & Melott "Gamma Ray Bursts: Not so Much Deadlier than We Thought"
<p>This data supports publication Thomas, Atri, and Melott 2020 "Gamma Ray Bursts: Not so Much Deadlier than We Thought"</p> <p><em>Monthly Notices of the Royal Astronomical Society</em>, Volume 500, Issue 2, January 2021, Pages 1970–1973, <a href="https://doi.org/10.1093/mnras/staa3364">https://doi.org/10.1093/mnras/staa3364</a></p> <p>The paper can be found as a pre-print: https://arxiv.org/abs/2009.14078</p> <p>Data included here are:</p> <ul> <li>Photon spectra for high-energy photon afterglow of GRB</li> <li>Ionization rate profiles calculated from photon spectra</li> <li>Surface-level muon flux</li> <li>Selected (post-processed) output from the GSFC atmosphere model, in netCDF format. </li> </ul> <p>Full raw data may be obtained upon request of the first author (Brian Thomas brian.thomas@washburn.edu).</p>
Corrected IODP Gamma Ray Attenuation (GRA) densities and calculated porosities derived from the LILY Database
<div>The dataset <strong>GRA_Densities_Corrected_and_Porosities_2023-12-26.csv</strong> is derived from an analysis of data from the LILY Database (<a href="https://doi.org/10.5281/zenodo.8408296">https://doi.org/10.5281/zenodo.8408296</a>) as described in Childress et al. (2024, <a href="https://doi.org/10.1029/2023GC011287">https://doi.org/10.1029/2023GC011287</a>). The file contains over 3.7 million corrected gamma ray attenuation (GRA) bulk density data derived from the LILY database file GRA_DataLITH.csv. It also contains over 3.7 million porosity estimates that are computed from the corrected GRA bulk density using grain densities computed for each lithology from Moisture and Density (MAD) grain densities (derived from LILY file MAD_DataLITH.csv).</div> <div> </div> <div><strong>Citation: </strong>Please cite Childress et al. (2024) when using these data:</div> <div>Childress, L.B., Acton, G.D., Percuoco, V.P., Hastedt, M., 2024. The LILY Database: Linking Lithology to IODP Physical, Chemical, and Magnetic Properties Data, <em>Geochemistry, Geophysics, Geosystems, 25</em>, <a href="https://doi.org/10.1029/2023GC011287">https://doi.org/10.1029/2023GC011287</a>.</div> <div> </div> <div><strong>GRA_Densities_Corrected_and_Porosities_2023-12-26.csv</strong> file size uncompressed is 950 Mb.</div> <div> </div> <div><strong>Data File format:</strong></div> <ul> <li>Exp: expedition number</li> <li>Site: site number</li> <li>Hole: hole number</li> <li>Core: core number</li> <li>Type: Type indicates the coring tool used to recover the core (typical types are F, H, R, X; see Table S3 in Childress et al., 2024, <a href="https://doi.org/10.1029/2023GC011287">https://doi.org/10.1029/2023GC011287</a>).</li> <li>Sect: section number</li> <li>Offset (cm): position of the observation, measured relative to the top of a section.</li> <li>Depth CSF-A (m): location of the observation expressed relative to the top of a hole.</li> <li>Bulk density (GRA): bulk GRA density measured on whole core sections in g/cm^3.</li> <li>Timestamp (UTC): date and time the observation was made.</li> <li>Instrument: abbreviation or mnemonic for the GRA sensing device used to make this observation (GRA1 or GRA2).</li> <li>Instrument group: abbreviation or mnemonic for the data collection device (logger) used to acquire this observation (WRMSL).</li> <li>Text ID: automatically generated unique database identifier for a sample, visible on printed labels.</li> <li>Prefix: Prefix of the lithology</li> <li>Principal: Principal lithology</li> <li>Suffix: Suffix of the lithology</li> <li>Full Lithology: full lithologic name = Prefix + Principal + Suffix</li> <li>Simplified Lithology: categorization of lithologies (see Supporting Information in Childress et al., 2024, <a href="https://doi.org/10.1029/2023GC011287">https://doi.org/10.1029/2023GC011287</a>)</li> <li>Lithology Type: Sedimentary, Igneous, or Metamorphic</li> <li>Degree of Consolidation: consolidation state of the lithology.</li> <li>Lithology Subtype: categorization of lithologies (see Supporting Information in Childress et al., 2024, <a href="https://doi.org/10.1029/2023GC011287">https://doi.org/10.1029/2023GC011287</a>).</li> <li>Expanded Core Type: the actual coring type used, because some coring types were incorrectly grouped in the "Type" column (see Childress et al., 2024 for an explanation)</li> <li>Latitude (DD): Latitude in decimal degrees</li> <li>Longitude (DD): Longitude in decimal degrees</li> <li>Water Depth (mbsl): water depth in meters below sea level</li> <li>Grain Density: grain density associated with the Principal lithology, computed from MAD data</li> <li>Mean MAD Bulk Density: mean MAD bulk density associated with the Principal lithology.</li> <li>Std MAD Bulk Density: standard deviation in the MAD bulk densities for each Principal lithology.</li> <li>Correction Basis: the GRA bulk densities are corrected based on coring tool used. If the RCB was used, then the lithology cored by the RCB is used in determining the size of the correction.</li> <li>Median Difference: The correction that will be applied based on the median difference between the raw GRA bulk density and the colocated MAD bulk density for a specific Correction Basis.</li> <li>GRA Bulk Density Corrected: The corrected GRA bulk density in g/cm^3.</li> <li>Porosity: porosity computed from the corrected GRA bulk densities and grain density.</li> <li>Deviation: difference between "GRA Bulk Density Corrected" and "Mean MAD Bulk Density", which is the deviation the corrected density has from that expected for its Principal lithology.</li> <li>N Deviations: The number of standard deviations by which the observation differs from the expected value (= Deviation/(Std MAD Bulk Density)), which is useful for identifying outliers.</li> </ul> <h3>GitHub Repository:</h3> <ul> <li>Contains a few notebooks to demonstrate how to work with the LILY database</li> <li><a title="IODP LILY GitHub Repository" href="https://github.com/IODP?tab=repositories">IODP LILY GitHub Repository</a> </li> </ul>
Resources for Mitigating Chemotherapy Side Effects through Targeted Gamma-Ray Delivery and CNNs
<p>This repository includes datasets and code used in the study "Mitigating Chemotherapy Side Effects through Targeted Gamma-Ray Delivery and Convolutional Neural Networks." The resources comprise:<br>- Binding Affinity Data: Used for simulations.<br>- Brain Tumor MRI and Chest CT Scan Datasets: Used for model training.<br>- Lightweight Deep CNN: Code for building and testing models.</p>
Gamma-ray picture book.
<p>A set of plots related to gamma-ray and hadron initated air showers.</p> <p>Note that this is a rather random selection of plots and prepared a long time ago (in 2005).</p> <p><a href="https://github.com/GernotMaier/gamma-ray-picturebook/blob/main/gamma_picturebook.pdf">gamma_picturebook.pdf</a> gives an overview of typical distributions important for ground-based gamma-ray astronomy. Additional distributions can be found in the folder <a href="https://github.com/GernotMaier/gamma-ray-picturebook/blob/main/shower-distributions">shower-distributions</a>.</p>
VTSCat: The VERITAS Catalog of Gamma-Ray Observations
<p><strong>VTSCat</strong> is the catalog of high-level data products from all publications of the <a href="https://veritas.sao.arizona.edu/">VERITAS collaboration</a>.</p> <p><strong>Most recent versions of VTSCat are available through https://doi.org/10.5281/zenodo.6988967</strong></p> <p>The <strong>VTSCat</strong> data collection contains:</p> <ul> <li>high-level data like spectral flux points, light curves, spectral fits in human- and machine-readable yaml and ecsv file format</li> <li>tabled data like upper limits tables from dark matter searches or results on the extragalactic background in ecsv file format</li> <li>sky maps (wherever available) in FITS file format</li> </ul> <p>The data collection contains results from gamma-ray measurements only. This is a pre-release for testing and early publications.</p> <p>A forthcoming research note will provide more details on the catalog. Please check the README file and all documentation linked to the README.</p> <p>VTSCat supplements the HEASARC catalogue of VERITAS results (to be published). VTSCat is inspired and derived from <a href="https://github.com/gammapy/gamma-cat">gamma-cat</a>.</p> <p>If you are a previous VERITAS author and would like to be associated with this repository, please send an email to G. Maier.</p> <p><strong>Access</strong>:</p> <ul> <li>GitHub: <a href="https://github.com/VERITAS-Observatory/VERITAS-VTSCat">https://github.com/VERITAS-Observatory/VERITAS-VTSCat</a></li> </ul> <p><strong>References</strong>:</p> <ul> <li>VERITAS: <a href="https://veritas.sao.arizona.edu/">https://veritas.sao.arizona.edu/</a></li> <li>VER Dictionary of Nomenclature: <a href="https://cds.u-strasbg.fr/cgi-bin/Dic-Simbad?/17350620">https://cds.u-strasbg.fr/cgi-bin/Dic-Simbad?/17350620</a></li> </ul>
Characterizing the gamma-ray variability of the brightest flat spectrum radio quasars observed with the Fermi LAT
<p>The FITS files contain light curves (prefix "lc"), spectral energy distributions (prefix "sed") and best-fit parameters for the whole region of interest (prefix "bestfit_roi") for the gamma-ray analyses of the six brightest flat spectrum radio quasars observed over 9.5 years with the Fermi Large Area Telescope (LAT). The file names also indicate the considered binning (weekly, daily, orbit, sub-orbital) and the considered time range in MJD.<br> The data products have been generated using the fermipy software, please see the documentation for further explanations of the columns provided in these files: <a href="https://fermipy.readthedocs.io/en/latest/">https://fermipy.readthedocs.io/en/latest/</a></p> <p>The analysis catalog are described in detail in the accompanying paper, which is submitted for publication in the Astrophysical Journal. The preprint of the submitted manuscript can be found here: <a href="https://arxiv.org/abs/1902.02291">https://arxiv.org/abs/1902.02291</a></p> <p>Additionally, the code for high level analysis including the light curves and the gamma-ray absorption in the broad line region can be found on github: <a href="https://github.com/me-manu/GaRLiC">https://github.com/me-manu/GaRLiC </a>and <a href="https://github.com/me-manu/blrabsorption">https://github.com/me-manu/blrabsorption</a></p> <p> </p>
Data from: Improved STEREO simulation with a new gamma ray spectrum of excited gadolinium isotopes using FIFRELIN
<p>Supplemental material to the article “Improved STEREO simulation with a new gamma ray spectrum of excited gadolinium isotopes using FIFRELIN”</p> <p>The files available are aimed to simulate the de-excitation cascade following neutron capture on<sup> 155</sup>Gd and <sup>157</sup>Gd. Therefore, the FIFRELIN simulation was done for the <sup>156</sup>Gd and <sup>158</sup>Gd isotopes, with the initial condition of an excitation energy of E* = S<sub>n</sub>, the neutron separation energy.</p> <p>Please cite this publication when using the files provided below:<br> H. Almazán et al., <a href="http://doi.org/10.1140/epja/i2019-12886-y">Eur. Phys. J. A 55 (2019) 183</a>, <a href="http://doi.org/10.48550/arXiv.1905.11967">arXiv:1905.11967 [physics.ins-det]</a></p> <p>Please see <a href="http://doi.org/10.5281/zenodo.6861341">Zenodo 6861341</a> for an improved version of the provided data.</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>
7 years of Fermi-LAT Gamma-ray data
<p>This is binned data for all Source-class photons from the first 7 years of Fermi-LAT. It is a special compact format used by the poiintlke application. It contains 447 M photons, in 14 M bins. Energy bins are 4/decade from 10 MeV to 1 TeV. Angular bins use HEALPix, with nside varying according to the PSF for the energy and event type (front or back).</p> <p>For details see</p> <p>https://github.com/tburnett/Fermi-LAT/blob/master/pointlike_document/Data%20Format.ipynb.</p>
Gamma Ray Bursts X-ray afterglow spectra from Swift/XRT
<p>Swift/XRT X-ray spectra of Gamma Ray Bursts. These are taken from swift.ac.uk, but time intervals from the light curves have been selected to remove flares and prompt emission. These spectra therefore show Gamma Ray Burst afterglow only.</p> <p> </p> <p>Reference: http://adsabs.harvard.edu/abs/2016arXiv161009379B</p> <p>Please cite Evans et al (2009, 2010) and Buchner et al (2016a).</p> <p> </p>
Data package for paper "DeepGlow: an efficient neural-network emulator of physical afterglow models for gamma-ray bursts and gravitational-wave events
<p>This is a data package accompanying the paper "DeepGlow: an efficient neural-network emulator of physical afterglow models for gamma-ray bursts and gravitational-wave events".</p>
A Study of Primordial Very Massive Star Evolution II: Stellar Rotation and Gamma-Ray Burst Progenitors
<p>Wind ejecta tables of rotating very massive stars from the paper:</p> <p><a href="https://iopscience.iop.org/article/10.3847/1538-4357/ad1185">A Study of Primordial Very Massive Star Evolution II: Stellar Rotation and Gamma-Ray Burst Progenitors</a></p>
Probabilistic classification of Fermi LAT gamma-ray sources (effect of covariate shift)
<p>Version 1:</p> <p>These are data products connected to <a href="https://arxiv.org/abs/2307.09584">https://arxiv.org/abs/2307.09584</a>, where an analysis of the effect of covariate shift on the probabilistic classification of the Fermi LAT gamma-ray sources from the 4FGL-DR3 catalog is performed.</p> <p>The files </p> <p>4FGL-DR3_6class_GMM_nmin100_prob_cat.csv<br>4FGL-DR3_6class_GMM_nmin100_weighted_prob_cat.csv</p> <p>contain probabilistic classification into 6 classes (determined in <a href="https://arxiv.org/abs/2307.09584">https://arxiv.org/abs/2301.07412</a>) with random forest and neural networks methods. The catalog in "4FGL-DR3_6class_GMM_nmin100_weighted_prob_cat.csv" is constructed including weights for associated sources used in training in order to account for the difference in the distribution of associated (training dataset) and unassociated (target dataset) sources. The catalog in "4FGL-DR3_6class_GMM_nmin100_prob_cat.csv" is constructed with unweighted training samples.</p> <p>The files</p> <p>4FGL-DR3_6class_GMM_nmin100_summary.csv<br>4FGL-DR3_6class_GMM_nmin100_weighted_summary.csv</p> <p>contain the corresponding summaries of the definition of classes and predicted numbers of sources for the RF and NN algorithms for associated sources (averaged over cases when the sources are in the testing samples) and unassociated sources.</p> <p>Detailed description of the construction of the catalogs can be found in <a href="https://arxiv.org/abs/2307.09584">https://arxiv.org/abs/2307.09584</a>.</p> <p>Version 2: update for the Fermi LAT 4FGL-DR4 catalog.</p> <p>The filenames slightly change.<br>Probabilistic catalogs with unweighted and weighted training respectively:<br>4FGL-DR4_6classes_GMM_prob_cat.csv<br>4FGL-DR4_6classes_GMM_weighted_prob_cat.csv<br><br>The corresponding summary files:<br>4FGL-DR4_6classes_GMM_summary.csv<br>4FGL-DR4_6classes_GMM_weighted_summary.csv</p> <p>Version 3: catalogs corresponding to the published version of the paper. The filenames and the format are the same as in Version 2.</p>
Search for merger ejecta emission in Short Gamma Ray Bursts from very late time radio observations
<p>Coalescence of inspiral binary neutron stars (BNS) system, giving rise to short Gamma Ray Bursts (GRBs), are one of the most probable candidates for Gravitational Waves (GWs). If the resultant product of the merger is a millisecond magnetar, a significant proportion of the rotational energy deposited to emerging ejecta that produce late time radio brightening from the interaction with the surrounding ambient medium. Detection of this late-time radio emission from short GRBs can have profound implications for understanding the physics of the progenitor. This study presents the deepest and an extensive search for radio emission at late times following a short GRB to date incorporating proper frequency regime, wider observation span and relativistic correction. Five short GRBs were observed with the Giant Meter Wave Radio Telescope (GMRT) at 1250, 610, and 325 MHz band $\sim$ 2 - 11 years since the burst to search for radio emission from the merger ejecta. The estimated upper limits at the burst location are used to constrain the parameters of the burst and its surrounding environment. The magnetar model, with appropriate modifications, constrains the number density of the ambient medium for these bursts to be between $10^{-4}$ - $10^{-2}$ $cm^{-3}$. Our analysis rules out a stable magnetar with an energy of $10^{53}$ erg for four out of the five GRBs in our sample.</p>
Novel polarimetric technique to constrain the magnetic field structure and strength of Gamma-ray burst jets
<p>Gamma-ray bursts (GRBs) are extremely energetic events of cosmological origin. Observed GRBs have high luminosity and rapid variability that requires ultra-relativistic motion in the production mechanism which drive the synchrotron radiation associated with the relativistic jets and their shocked interactions with the local ambient medium. They are broadly divided into two types based on the gamma-ray duration; long GRBs (>2 seconds), and short GRBs (<2 seconds). Long GRBs are thought to be originated from explosions of very massive stars and short GRBs are thought to be produced by the merger of compact binaries. Several key open questions about our understanding of GRB physics remain: What is the driving mechanism of GRB jets? What is the origin and role of magnetic fields in driving the explosion? Since these events happen at cosmological distances, they can not be resolved using traditional astronomical techniques. However, polarimetric observations of GRBs have allowed us to start the exploration of the structure and magnetic field configurations of their relativistic jets. Generally, polarization is measured via the ratio of fluxes by taking consecutive exposures, however for rapidly varying objects such as GRBs, it is not an effective way to observe polarization. Liverpool Telescope (LT) has utilized rapidly rotating polaroids to overcome this problem and created a series of polarimeters that have successfully detected early-time optical polarimetry of various GRBs. I will present photometric and polarimetric results of various GRBs observed by RINGO3. 10 GRBs were bright enough to perform analysis and we were able to perform polarimetric analysis for 7 GRBs. I will discuss how polarimetric detection for a long GRB 191016A along with photometric data constraint the energy injection mechanism for the central engine. In addition, I will present how polarization depends on various properties of GRBs such as photometric decay index, isotropic energy of GRBs, redshift etc.</p>
Supporting information for the paper: Terrestrial Gamma-ray Flashes with Accompanying Elves Detected by ASIM
<p>Supporting data to the paper "Terrestrial Gamma-ray Flashes with Accompanying Elves Detected by ASIM"</p>
Fermi-GBM Data Release Related to Searches for Neutrinos from Gamma-Ray Bursts using the IceCube Neutrino Observatory
<p>This data release includes Fermi Gamma-ray Burst Monitor (GBM) localizations used in searches for neutrinos from gamma-ray bursts (GRB) by the IceCube Neutrino Observatory. These localizations are provided publicly to the community since they are generally useful for any analysis that needs the Fermi-GBM localization for a GRB.</p> <p><strong>Full Details:</strong></p> <p>The files contained herein are HEALPix representations of GRB localizations from the Fermi-GBM stored as FITS files and produced according to the automated method described in [1]. Each file represents the probability density (statistical + systematic) for the true source location. By definition, this excludes the Earth occulted region of the sky, which is set to 0 due to the fact that real sources are not visible through the Earth. These files cover a time range spanning the first detection of GRBs by GBM in July 2008 through July 2019 and should be considered preliminary. The files are preliminary in the sense that they contain some key differences to the official files hosted at HEASARC FTP server through the Fermi Science Support Center (FSSC; <a href="https://fermi.gsfc.nasa.gov/ssc/data/access/gbm/">https://fermi.gsfc.nasa.gov/ssc/data/access/gbm/</a>). We list the key differences here:</p> <ul> <li>Fermi began production HEALPix FITS files in early 2018, and files prior to that have not been officially provided. The files in this archive are currently the only version of HEALPix files pre-2018.<br> </li> <li>These files were not produced via the standard GBM operational pipeline; however they were produced with the same functional code that is used to make the files. The result of this is that the standard quality checks on the FITS headers by uploading to the FSSC were skipped. The primary header is most affected, with some null values, but these null values do not affect the HEALPix data.<br> </li> <li>These localizations may have centroids that are slightly different than reported in the online catalog. This is because an automated algorithm for localization (RoboBA) was used to localize the GRBs and produce these files as opposed to the manual Human-in-the-Loop localization performed for every GRB prior to 2016, and ~15% of GRBs thereafter [1].<br> </li> <li>These localizations contain an updated and improved systematic uncertainty model compared to the pre-July 2019 localizations at the FSSC. The new systematic uncertainty model is explained in [1], while the older localizations at the FSSC contain a systematic uncertainty model from [2].<br> </li> <li> In general, the official localizations hosted at the FSSC currently do not remove localization probability that overlaps the Earth, but these files do remove the probability that overlaps the Earth and renormalizes the remaining PDF. This encodes the assertion that the localization is indeed of an astrophysical nature.</li> </ul> <p>The FITS files are organized with two HDUs:</p> <ul> <li> PRIMARY HDU with some basic metadata about the mission from which the data originated<br> </li> <li> HEALPIX HDU containing header information about the GBM detector pointings, as well as the Sun and Geocenter localizations with respect to Fermi. There are two data fields contained in the extension: <ul> <li> PROBABILITY: the differential localization probability per pixel (NSIDE=128)</li> <li> SIGNIFICANCE: integrated probability for estimating confidence intervals (NSIDE=128)</li> </ul> </li> </ul> <p>Furthermore, we provide images of each localization. The images are a Mollweide projection of the sky, with the 50% and 90% localization confidence regions marked in shaded purple. The location of the Earth from Fermi's perspective is marked in shaded blue.</p> <p>The GBM trigger number associated with each FITS file and image is listed in the filename.</p> <p><strong>References:</strong></p> <p><a href="https://iopscience.iop.org/article/10.3847/1538-4357/ab8bdb">[1] Goldstein, A. et al. 2020, ApJ, 895, 40</a><br> <a href="https://iopscience.iop.org/article/10.1088/0067-0049/216/2/32/meta">[2] Connaughton, V. et al. 2015, ApJS, 216, 32</a></p>
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.