U-Pb isotope ratio data set for numerous phosphate (apatite) grains in two thin section samples of the LL5 S4-6 Chelyabinsk meteorite. One section is of the S4-6 light lithology, and another of the S5-6 dark lithology. Samples analysed were section ‘A' (light lithology) and section ‘B’ (dark lithology) of Chelyabinsk, both from the Open University School of Physical Sciences sample collection. The results demonstrate variability in degree of Pb-loss during collisional reheating from pristine versus damaged apatite crystal domains. These results are reported for a meteorite fall which originally happened near Chelyabinsk in Russia. The results otherwise have no geographic location, as this is a sample of an asteroid. All measurements were made in December 2020. These data were collected using Secondary Ionisation Mass Spectrometry (SIMS) with a CAMECA IMS 1280 at the Institute of Geology and Geophysics, Chinese Academy of Sciences (IGGCAS). The thin sections were polished with colloidal silica, cleaned, and coated with gold prior to analysis. Microtextural information was obtained prior to analysis using a combination of back-scatter-electron, cathodoluminescence, and electron-back-scatter-diffraction analysis. Data were obtained to test hypotheses relating to the competition between macro-to-meso-scale thermally-driven variation in Pb-loss rates versus microscale variation driven by grain-specific features, e.g., fracture networks. An article describing and discussing these results, including further methodological steps in their collection and processing, is due for publication. This information is currently available in preprint form on arXiv: https://arxiv.org/abs/2112.06038
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.