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.
78
datasets available to search
ShareScore release 0.9.0
Dataset results
78 results for “Electron beams”
Upward, MeV-class electron beams over Jupiter's Main Aurora; Selected data for
<p>This submission provides selected ASCII data that is utilzed in a scientific study entitled: "Upward, MeV-class electron beams over Jupiter’s Main Aurora". A PDF of the manuscript is included here. The 13 authors of this study are identified in the PDF manuscirpt. The data files are labeled according to the figure numbers and panels used in the manuscript. The PDF of the paper serves to document the qualities of the data submitted. The abstract of the manuscript is as follows: </p> <p>Abstract: Jupiter’s poleward (Zone II) main aurora exhibits bi-directional electron acceleration; upward acceleration dominates but downward acceleration generates strong aurora. During Juno’s first perijove (PJ1), the upward acceleration manifested as narrow electron angular beams (within ~5 of the magnetic field) over the 30-1200 keV energy range of Juno’s Jupiter Energetic Particle Detector Investigation (JEDI). These beams can be simply connected (non-uniquely) to >10 to perhaps 100’s of MeV electrons that penetrated the radiation shielding of the camera head of the Magnetometer Investigation’s Advanced Stellar Compass (ASC). The most intense of those multiple MeV populations are shown to have been highly directional and propagating upwards. How auroral processes generate such beams is unknown. With azimuthal symmetry assumed (not demonstrated here), these beams provided >1026 s-1 of >30 keV electrons to Jupiter’s vast magnetosphere, a possibly critical and dominating source of energetic electrons to that region and ultimately to Jupiter’s radiation belts.</p>
Rotation of electron beams in the presence of localised, longitudinal magnetic fields
<p>Electron Bessel beams have been generated by inserting an annular aperture in the illumination system of a TEM.</p> <p>These beams have passed through a localised magnetic field.</p> <p>As a result a low amount of image rotation (which is expected to be proportional to the longitudinal component of the magnetic field) is observed in the far field.</p> <p>A measure of this rotation should give access to the magneti field.</p> <p>The two datasets have been acquired in a FEI Titan<sup>3</sup> microscope, operated at 300kV.</p> <p>The file focal_series.tif contains a series of images acquired varying the magnetic field through the objective lens.</p> <p>The file line_profile.ser contains a series of images acquired by scanning the beam over a sample with several magnetised nanopillars.</p> <p>For reference, check the associated publication:<br> <em>Giulio Guzzinati, Armand Béché, Damien McGrouther and Jo Verbeeck</em>, <strong>Prospects for out-of-plane magnetic field measurements through interference of electron vortex modes in the TEM, </strong><a href="https://doi.org/10.1088/2040-8986/ab51fc">Journal of Optics 21 124002 (2019)</a></p>
Animation to visualize the electron beam damage induced in calcium silicate hydrate phases
<p>This dataset visualizes the electron beam damage induced by a scanning electron microscope (SEM) in calcium silicate hydrates (C-S-H). The specimen used is 28 days hydrated alite (water/solid = 0.5). It was scanned using a thermofischer scientific Helios G4 UX microscope at 350 V/25 pA with a stage bias of 200 V.</p> <p>This animation was an afterthought. Therefore, the dataset provides multiple magnifications and resolutions and some of the images are not in focus. Nevertheless, It can be seen, that the C-S-H needle in the right half of the image significantly deformes within a timespan of 124 seconds of constant scanning of that region.</p> <p><strong>File content:</strong></p> <ul> <li>All images ending with "raw" are the raw images provided by the SEM software including all metadata.</li> <li>The file "C3S_CSH_e-beam-damage_aligned stack.tif" contains the aligned image set using the SIFT algorithm. It contains the correct scaling if opened with ImageJ.</li> <li>The file "C3S_CSH_e-beam-damage_animation.gif" provides the final animation including a overlayed scalebar.</li> </ul>
Crossed graphene nanoribbons as beam splitters and mirrors for electron quantum optics
<p>OPEN DATA related to the research publication:</p> <p>S. Sanz, P. Brandimarte, G. Giedke, D. Sánchez-Portal, and T. Frederiksen, <em>Crossed graphene nanoribbons as beam splitters and mirrors for electron quantum optics</em>, Phys. Rev. B <strong>102</strong>, 035436 (2020) [arXiv:2005.11391]</p> <p>Abstract: We analyze theoretically 4-terminal electronic devices composed of two crossed graphene nanoribbons (GNRs) and show that they can function as beam splitters or mirrors. These features are identified for electrons in the low-energy region where a single valence or conduction band is present. Our modeling is based on <em>pz</em> orbital tight-binding with Slater-Koster type matrix elements fitted to accurately reproduce the low-energy bands from density functional theory calculations. We analyze systematically all devices that can be constructed with either zigzag or armchair GNRs in AA and AB stackings. From Green's function theory the elastic electron transport properties are quantified as a function of the ribbon width. We find that devices composed of relatively narrow zigzag GNRs and AA-stacked armchair GNRs are the most interesting candidates to realize electron beam splitters with a close to 50-50 ratio in the two outgoing terminals. Structures with wider ribbons instead provide electron mirrors, where the electron wave is mostly transferred into the outgoing terminal of the other ribbon, or electron filters where the scattering depends sensitively on the wavelength of the propagating electron. We also test the robustness of these transport properties against variations in intersection angle, stacking pattern, lattice deformation (uniaxial strain), inter-GNR separation, and electrostatic potential differences between the layers. These generic features show that GNRs are interesting basic components to construct electronic quantum optical setups.</p>
Electron Bessel beam diffraction patterns, line scan of Si/SiGe multilayer
<p>Electron diffraction patterns taken with a conical illumination (electron Bessel beams) and can be used to measure strain.</p> <p>The experimental diffraction patterns, in DM3 format, are included in the file experimental_data.7z while FEM strain simulations for the same sample are in the file reference_strain_experimental.csv</p> <p>Simulated diffraction patterns are included in the file simulated_patterns.7z while the strain in the model used is in the file reference_strain_simulated_patterns.csv</p> <p> </p> <p>The two python scripts attached allow the extraction of the strain, and rely on the code published at:</p> <p>https://bitbucket.org/lutosensis/tem-thesis/</p> <p> </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>
Research data supporting for Application of electron tomography of dislocations in beam-sensitive quartz to the determination of strain components
<p>This archives contains all the raw data (micrographs) supporting the publication</p>
Quasilinear Analysis in the Source Region of Jovian Hectometric Emissions Associated with Upward Electron Beams
<p>This is the supporting data set for the paper by the same title published in AGU JGR Space Physics.</p> <p><strong>Key Points:</strong></p> <ol> <li>Upward electron beams detected in HOM source region excite low-frequency waves.</li> <li>One-sided loss-cone electron distribution excites extraordinary mode via cyclotron maser instability, which leads to HOM emission.</li> <li>The Observed wave spectra and particle characteristics can be modeled by employing quasilinear wave-particle analysis.</li> </ol> <p><strong>Plain Language Summary:</strong></p> <p>NASA’s Juno space probe orbiting the planet Jupiter measured energetic electrons streaming out from the northern polar region of the planet. These electrons were seen to travel in an environment permeated by high-frequency radio emission called the Jovian hectometric emission. By employing a mathematical model known as the quasilinear plasma kinetic theory the essential characteristics of the electrons and the electromagnetic wave spectra measured by the Juno space probe are theoretically replicated. This exercise helps scientists understand the nature of physical processes taking place in the space environment surrounding the planet Jupiter.</p> <p><strong>Abstract:</strong></p> <p>Intense upward electron beams were measured by the Juno JADE instrument in the northern hemisphere, low-latitude auroral zone source region. In this study we report on how these electron beams interact with plasma near and within the Jovian hectometric (HOM) emission (1 MHz < f < 5 MHz) source region. Within the source region large upward loss cones are observed in the northern polar region at radial distances of ∼ 2Rj, magnetic latitude of ∼ 70◦ . Intense, narrow electron beams (E < 3 keV) are then observed, but within one second wave-particle scattering is observed, filling the loss cone to energies > 50 keV. These energies persist for several seconds before fading, leaving an empty loss cone again. The loss cone provides a free-energy source for HOM emission resulting from the cyclotron maser instability. We use quasilinear analysis to examine the generation of HOM and the dynamics of wave-particle interaction of the electron beams with HOM, and the generation via Landau interaction of whistler mode emission. The dynamic spectrum of the HOM emission generated by the loss-cone electrons as well as that of the low-frequency whistler-mode waves generated by the up-going electron beam can be constructed by quasilinear theory, which compare well with observation. The saturated state of the energetic electron velocity distribution function constructed via quasilinear theory also compare reasonably with observation.</p>
Dataset for Using Your Beam Efficiently: Reducing Electron-dose in the STEM via Flyback Compensation
<p>Experimental scanning transmission electron microscopy dataset for the paper "Using Your Beam Efficiently: Reducing Electron-dose in the STEM via Flyback Compensation"</p>
FIB cleaned and reshaped Electrostatic electron vortex beam generators - dataset2
<p>Here is a second set of SEM images of Electrostatic electron vortex beam generators fabricated at the CNR-IMM in Bologna and FIB cleaned and reshaped at the CNR-NANO in Modena. The difference between this batch of devices and the first one is in the thickness of the electrode (the z-dimension), this batch has a electrode thickness of 30um, while the first batch is 10um thick.</p>
FIB cleaned an reshaped Electrostatic Electron Vortex Beam Generators
<p>Here are collected the SEM images (top-view and tilted-view) of the Electrostatic Electron Vortex Beam Generators fabricated at the CNR-IMM in Bologna and then cleaned and reshaped by FIB milling at the CNR-NANO in Modena. Different shapes of the main paired needles have been fabricated to try to optimize the reproduction the ideal phase profile as reported in https://doi.org/10.1103/PhysRevResearch.2.013185</p>
Open data for the article "Low-resistivity, high-resolution W-C electrical contacts fabricated by direct-write focused electron beam induced deposition"
<p>Open data for the article "Low-resistivity, high-resolution W-C electrical contacts fabricated by direct-write focused electron beam induced deposition", which will be published in Open Research Europe</p>
Real-time tilt undersampling optimization during electron tomography of beam sensitive samples using golden ratio scanning and RECAST3D
<p>This dataset contains experimental data related: "Real-time tilt undersampling optimization during electron tomography of beam sensitive samples using golden ratio scanning and RECAST3D", T.Craig, A. Kadu, K.J. Batenburg and S. Bals, <em><strong>Nanoscale</strong></em>, 2023,<strong>15</strong>, 5391-5402 (2023).</p>
3D Printing Titanium with a Conical Electron Beam
<p>We teamed up with xBeam 3D Metal Printing (https://xbeam3d.com/) to characterise Ti-6Al-4V (Ti64) parts 3D printed using wire and a conical electron beam. In this video, I analyse the β-grain structures of the xBeam test parts, built with 3 different deposition strategies, and present a post-build heat treatment trial to demonstrate that the xBeam process can replicate wrought titanium aerospace parts.</p> <p>Original research paper: https://doi.org/10.1016/j.mtla.2021.101202</p> <p>xBeam 3D Metal Printing: https://xbeam3d.com/</p> <p>Research credits: Alec. E Davis, J. R. Kennedy, D. Strong, D. Kovalchuk, S. Porter, P. B. Prangnell.</p> <p>Video credits: Produced, written, recorded, and performed by Alec E. Davis.</p>
Spin-polarizing electron beam splitter from crossed graphene nanoribbons
<p>OPEN DATA related to the research publication:</p> <p>S. Sanz, N. Papior, G. Giedke, D. Sánchez-Portal, M. Brandbyge, and T. Frederiksen, <br><em>Spin-polarizing electron beam splitter from crossed graphene nanoribbons</em>,<br><a href="https://journals.aps.org/prl/abstract/10.1103/PhysRevLett.129.037701" target="_blank" rel="noopener">Phys. Rev. Lett. <strong>129</strong>, 037701 (2022)</a> [arXiv:2201.07147]</p> <p>Abstract: Junctions composed of two crossed graphene nanoribbons (GNRs) have been theoretically proposed as electron beam splitters where incoming electron waves in one GNR can be split coherently into propagating waves in <em>two</em> outgoing terminals with nearly equal amplitude and zero back-scattering. Here we scrutinize this effect for devices composed of narrow zigzag GNRs taking explicitly into account the role of Coulomb repulsion that leads to spin-polarized edge states within mean-field theory. We show that the beam-splitting effect survives the opening of the well-known correlation gap and, more strikingly, that a <em>spin-dependent</em> scattering potential emerges which spin polarizes the transmitted electrons in the two outputs. By studying different ribbons and intersection angles we provide evidence that this is a general feature with edge-polarized nanoribbons. A near-perfect polarization can be achieved by joining several junctions in series. Our findings suggest that GNRs are interesting building blocks in spintronics and quantum technologies with applications for interferometry and entanglement.</p>
Simulation of convergent-beam low-energy electron diffraction on Si(001) reconstructions
<p>Research results based upon this code and data are published at <a href="http://doi.org/10.1016/j.apsusc.2019.05.274">http://doi.org/10.1016/j.apsusc.2019.05.274</a>.</p> <p>The image simulation of convergent beam low energy electron diffraction (CBLEED) patterns are used to determine the sensitivity of CBLEED to atomic-scale displacements of several reconstructed variants of the Si(001) surface. The CAVATN code is used to determine the dynamical LEED intensities as a function of the incident electron energy (E<sub>i</sub>), angle (theta, phi) and at each of the miller indices (h,k), up to the third order. The CBLEED code then maps these intensities into reciprocal space, allowing the visualisation of CBLEED patterns to be made as a function of incident electron energy (E<sub>i</sub>). The data files for the CBLEED simulations are stored in a .txt format, with an accompanying .png image displaying the result of the simulation. This data is then analysed to determine the sensitivity of CBLEED patterns to small atomic displacements.</p> <p><strong>CAVATN code:</strong> Relevant documentation, electron beam files and the crystal structure files are all included. The CAVATN dynamical LEED package, developed from the CAVLEED code, is also included, where the code employs the muffin-tin potential approximation and involves a set of phase shifts for each atom type (which are treated as spherically symmetric scatterers in a crystal) that can be evaluated using phase shift calculation packages or tables. In the simulations performed here, complex phase shifts were used to simulate temperature dependent scattering effects at T = 293<em>K</em>. The inner potential is treated as energy independent and is split into real U<sub>or</sub> = 5 <em>eV </em>and imaginary U<sub>oi</sub> = 10 <em>eV </em>parts to respectively treat refraction (via the vacuum and muffin-tin zero difference) and absorption (due to in- elastic processes). Multiple scattering between atoms within a layer is calculated using the chain method and the multiple scattering between layers is included by the renormalized forward scattering perturbation method to evaluate the wave amplitudes of diffracted beams at the surface, and hence the intensities of the LEED pattern.</p> <p><strong>CBLEED code:</strong> The dynamical CBLEED package is included as ‘cbleed_analysis_script.py’, where the CBLEED patterns are simulated by uniformly partitioning the convergent cone into square areas as shown in Figure 1. An incident electron beam is located at the centre of these squares and defined directionally by and . Each of the incident electron beams of the sampled convergent cone was then used as input to the dynamical LEED program CAVATN, so that the corresponding multiply scattered intensities could be determined and mapped into reciprocal space. All the output data files from the CBLEED code is available for the following structures in the ‘output’ folder; Si(001)-1x1-ideal, Si(001)-2x1-symmetric, Si(001)-2x1-buckled, Si(001)-2x1-dH (for dimer height displacements) and Si(001)-2x1-dL (for dimer length displacements). The data for the sensitivity to atomic-scale displacements is included in the ‘sensitivity_output’ folder, which determines both the partial and whole pattern sensitivities.</p>
Dataset for "VHEE beam dosimetry at CERN Linear Electron Accelerator for Research under ultra-high dose rate conditions"
<p>Dataset for "VHEE beam dosimetry at CERN Linear Electron Accelerator for Research under ultra-high dose rate conditions"</p> <p>Daniela Poppinga <em>et al</em> 2021 <em>Biomed. Phys. Eng. Express</em> 7 015012</p> <p>https://doi.org/10.1088/2057-1976/abcae5</p> <p> </p>
Dominance of Auger excitation in beam heating in transmission electron microscopy: Irradiation experiments and quantitative thermal analysis of α-Al2O3
<p>The collection of uploaded files constitutes a dataset supporting our findings, titled Dominance of Auger excitation in beam heating in transmission electron microscopy: Irradiation experiments and quantitative thermal analysis of α-Al<sub>2</sub>O<sub>3</sub>, to be submitted to a scientific journal.</p> <p>The co-authors are Jihye Kwon and Hyoung Seop Kim, both at Pohang University of Science and Technology (POSTECH), Republic of Korea</p>
Scaling of the electron temperature on the expansion ratio with plasma heating by Neutral Beams only (diamonds) and with both Neutral Beams and ECRH (square)
<p>Scaling of the electron temperature on the expansion ratio with plasma heating by Neutral Beams only (diamonds) and with both Neutral Beams and ECRH (square)</p>
Area Selective Chemical Vapor Deposition of Gold by Electron Beam Seeding
<p>Data used in the article "Area Selective Chemical Vapor Deposition of Gold by Electron Beam Seeding"</p> <p>v.3</p> <p>Now contains the experimental results on CVD at 120 °C.</p> <p>v.2</p> <p>Now in .zip folder and correctly sorted.</p> <p>Please read readme.txt for navigation.</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.