dataesr/scientific-paragraphs-categorization huggingface dataset:
Thermodynamic Properties These are listed in the file eos. thermo. It contains three entries in the first line, namely, the masses of the neutron and proton in MeV, and an integer that indicates if the EoS contains leptons  (1)  or not (0). The remaining lines contain the following entries i T i n B i Y q p n B s µ b m n -1 µ q m n µ l m n f n B m n -1 e n B m n -1 N add q 1 q 2. N add quantities corresponding to the indices for temperature, baryon number density, and charge fraction, followed by seven mandatory thermodynamic quantities. These are An integer follows, indicating the absence (0) or presence (N add ) of N add additional optional thermodynamic quantities to be specified in the data sheet. If the table contains repeated rows with identical indices i T , i n B , i Y q , only the last row is used.
Composition of Matter (Optional) This is listed in the file eos. compo containing in all lines the entries i T i n B i Y q I phase N pairs I 1 Y I 1. N pairs pairs N quad I 1 A av I 1 Z av I 1 Y I 1. N quad quadruples corresponding again to the indices for temperature, baryon number density, and charge fraction, followed by an index encoding the type of phase (chosen by provider and identified in the data sheet), number of particles (pairs) for which the composition is given, particle pairs in no particular order (particle indices from Table  1  followed by the respective particle charge fractions), number of particle quadruples, particle quadruples (particle indices from Table  1  followed by the respective average mass and charge numbers of the representative nucleus and respective combined charge fraction).
Instructions for Users There are two equivalent ways to handle and customize data provided by the COMPOSE website. Both are based on the compose software, which is free and anyone can download it. A very convenient way to handle and customize data is thus to use it directly. Alternatively, there is a web interface to the software, accesible via the "Compute" button for each EoS table, which is free but password restricted. This quick guide describes the basic procedures to obtain a table with EoS data with the help of a number of examples by direct use of the software. It is prepared in particular for first-time users in order to get familiar with the files, the program and the handling. See Appendix A for a summary of the notation we use. In this quick guide only the preparation of data tables in ASCII format is described using a LINUX based operation system.
Instructions for users There are two equivalent ways to handle and customize data provided by the COM-POSE website. Both are based on the compose software, which is free and anyone can download it. A very convenient way to handle and customize data is thus to use it directly. Alternatively, there is a web interface to the software, accesible via the "Compute" button for each EoS table, which is free but password restricted. This quick guide describes the basic procedures to obtain a table with EoS data with the help of a number of examples by direct use of the software. It is prepared in particular for first-time users in order to get familiar with the files, the program and the handling. See Appendix A for a summary of the notation we use. In this quick guide only the preparation of data tables in ASCII format is described using a LINUX based operation system.
EoS Data There are presently four families of EoS tables available in COMPOSE: General Purpose EoS, Neutron Matter EoS, Cold Neutron Star EoS, and Cold Matter EoS. You will see this option when clicking on "EoS" and then on "Families" in the left column of the COMPOSE web page. The code should run with each of them. Alternatively, you can find the EoS model of your preferred author with the help of the bibliography search on the web page. The files for download can be found by clicking on 'Details' for each EoS model. Download the files for your preferred EoS table and move them to the same directory as the code. Note that by default the data from all EoS models have the same name. Thus, you should either remove all previous EoS data files before running a new model or create a different directory for each model.
EoS Data There are presently four families of EoS tables available in COMPOSE, i. e. , General Purpose EoS, Neutron Matter EoS, Cold Neutron Star EoS, and Cold Matter EoS. You will see this option when clicking on "EoS" and then on "Families" in the left column of the COMPOSE web page. The code should run with each of them. Alternatively, you can find the EoS model of your preferred author with the help of the bibliography search on the web page. The files for download can be found by clicking on 'Details' for each EoS model. Download the files for your preferred EoS table and move them to the same directory as the code. Note that, by default, the data from all EoS models have the same name. Thus, you should either remove all previous EoS data files before running a new model or create a different directory for each model.
EoS Data There are presently four families of EoS tables available in COMPOSE: General Purpose EoS, Neutron Matter EoS, Cold Neutron Star EoS, and Cold Matter EoS. You will see this option when clicking on "EoS" and then on "Families" in the left column of the COMPOSE web page. The code should run with each of them. Alternatively, you can find the EoS in a terminal. You will then be prompted to select from three options. Selecting task '1' will guide you to the generation of the eos. quantities file, specifying the needed output. Task '2' will guide you to the generation of the eos. parameters file, specifying the grid in thermodynamic variables. Just follow the instructions. Keep in mind that the code is interpolating the EoS data, it is thus not possible to calculate outside the ranges given by your EoS data tables.
195 In this quick guide only the preparation of data tables in ASCII format is described 196 using a LINUX based operation system. For an output of data in the HDF5 format, please 197 refer to the full CompOSE manual [2,3]. The code allows to calculate many different quantities, and surely not every user needs 222 all of them. In addition, some of them are only available for selected EoS tables. Therefore, 223 before running the code, the grid in thermodynamic variables (temperature T, baryon 224 number density n B , and charge fraction Y q ), as well as the desired output quantities have 225 to be specified. This is done with two input parameter files, eos. parameters for the grid 226 and eos. quantities for the output. Three examples, described below, are available on the 227 web page in the 'software' section.
EoS Data There are presently four families of EoS tables available in COMPOSE EoS, Neutron Matter EoS, Cold Neutron Star EoS, and Cold Matter EoS option when clicking on "EoS" and then on "Families" in the left column web page. The code should run with each of them. Alternatively, you model of your preferred author with the help of the bibliography search The files for download can be found by clicking on 'Details' for each EoS the files for your preferred EoS table and move them to the same dire Note that by default the data from all EoS models have the same name. either remove all previous EoS data files before running a new model or directory for each model.
195 In this quick guide only the preparation of data tables in ASCII format is described 196 using a LINUX based operation system. For an output of data in the HDF5  The code allows to calculate many different quantities, and surely not every user needs 222 all of them. In addition, some of them are only available for selected EoS tables. Therefore, 223 before running the code, the grid in thermodynamic variables (temperature T, baryon 224 number density n B , and charge fraction Y q ), as well as the desired output quantities have 225 to be specified. This is done with two input parameter files, eos. parameters for the grid 226 and eos. quantities for the output. Three examples, described below, are available on the 227 web page in the 'software' section. Note that if you do not remove the older versions of the 228 input files eos.
Download the compose code from the software section on the COM where a link to the COMPOSE gitlab can be found 4. You will need the fi composemodules. f90 and Makefile. Copy them to the same directo executable by typing: make compose The provided version of the Makefile employs the gfortran compiler, a LINUX systems. For another compiler, you have to modify the Makefil If during compilation an error related to HDF5 appears, check Makefile. Ensure that it reads HDF5 = 0 3. 1. 1. EoS Data There are presently four families of EoS tables available in COMPOSE EoS, Neutron Matter EoS, Cold Neutron Star EoS, and Cold Matter EoS option when clicking on "EoS" and then on "Families" in the left column web page. The code should run with each of them. Alternatively, you model of your preferred author with the help of the bibliography search The files for download can be found by clicking on 'Details' for each EoS the files for your preferred EoS table and move them to the same dire Note that by default the data from all EoS models have the same name.
Funding: COMPOSE would not be possible without the financial and organisatorial support from a large number of institutions and individual contributors. We gratefully acknowledge support by the CompStar network of the European Science Foundation (ESF), the birthplace of the COMPOSE project, the COST actions NewCompStar, and PHAROS, a grant from the Polish Ministry for Science and Higher Education (MNiSW) supporting the "CompStar" activity, by the Instytut Fizyki Teoretycznej of the Uniwersytet Wrocławski, the National Science Centre Poland (Narodowe Centrum Nauki, NCN) within the "Maestro" programme under contract No. DEC-2011/02/A/ST2/00306, by the "hadronphysics3" network within the seventh framework program of the European Union, by the GSI Helmholtzzentrum für Schwerionenforschung GmbH, by the Helmholtz International Center for FAIR within the framework of the LOEWE program launched by the state of Hesse via the Technical University Darmstadt, by the Helmholtz Association (HGF) through the Nuclear Astrophysics Virtual Institute (VH-VI-417), by the ExtreMe Matter Institute EMMI in the framework of the Helmholtz Alliance "Cosmic Matter in the Laboratory", by the DFG cluster of excellence "Origin and Structure of the Universe", by the DFG through grant SFB 1245, by the SN2NS project ANR-10-BLAN-0503.
L. T. also acknowledges support from CEX2020-001058-M (Unidad de Excelencia "María de Maeztu"), PID2019-110165GB-I00 financed by the spanish MCIN/AEI/10. 13039/501100011033/, as well as by the EU STRONG-2020 project, under the program H2020-INFRAIA-2018-1 grant agreement no. 824093, and the CRC-TR 211 "Strong-interaction matter under extreme conditions"-project No. 315477589-TRR 211. V. D. acknowledges support from the National Science Foundation under grants PHY1748621, MUSES OAC-2103680, and NP3M PHY-2116686. C. P. acknowledges support from the Fundação para a Ciência e Tecnologia under the Projects UIDP/04564/2020 and UIDB/04564/2020.
The paper is structured as follows. In Sect. 2, we describe the contributing facilities and datasets used in the validation and characterisation of the system. We infer the properties of the host star in Sect. 3 and validate the planetary nature of the two transit signals in Sect. 4. In Sect. 5, we present our detailed analysis of the photometry, including a global transit analysis to derive the system's properties (Sect. 5. 1), a search for additional transiting planets in the TESS and SPECULOOS-South data and an assessment of their detection limits (Sect. 5. 2), as well as a study of the stellar variability  (Sect. 5. 3). Section 6 describes our analysis of Subaru/IRD radial velocities and derivation of preliminary mass constraints. In Sect. 7, we present a dynamical analysis of the system, including studies of its tidal evolution and long-term stability.
Lick/Kast We obtained a low-resolution optical spectrum of LP 890-9 with the Kast Double Spectrograph on the 3m Shane Telescope at Lick Observatory on 14 November 2021 (UT) in clear conditions with 2 seeing. This instrument provides simultaneous blue and red optical spectra with parallel spectrograph cameras. Our analysis focussed on red optical data obtained with the 600/7500 grating and 1. 5 -wide slit, providing 6000-9000 Å spectra at an average resolution of λ/∆λ ≈ 2500. The source was observed with 6 exposures of 600 s each within an hour of transit and at an average airmass of 2. 5. The flux calibrator Feige 110  (Hamuy et al. 1992 (Hamuy et al. , 1994) )  was observed on the same night, and dome illuminated flat field and arc lamp exposures were obtained at the start of the night for pixel response and wavelength calibration.
258), the exposure times were set to 1800 s for all frames. We reduced the raw IRD data as per the reduction procedure in  Hirano et al. (2020) , and extracted both stellar and LFC spectra, whose wavelengths were calibrated using the Thorium-Argon hollow cathode lamp. The reduced stellar spectra had a typical S/N of ≈25 per pixel at 1000 nm. Using IRD's analysis pipeline for RV measurements  (Hirano et al. 2020) , we computed relative RVs for the individual stellar spectra. In doing so, both Y J and H-band spectra were analysed for all frames except the ones (three frames) in January 2022, for which we were only able to measure RVs for H-band spectra. The resulting RV measurements are given in Table  A. 1. The typical measurement errors are 10-15 and 7-10 m s -1 for the Y J-band and the H-band spectra, respectively.
Search for transit timing variations As mentioned in Sect. 5. 1. 1, the system is within 10% of the second-order 3:1 mean motion resonance. To explore A59, page 13 of 31 our photometric dataset for possible transit timing variations (TTVs), we repeated the same global analysis as in Sect. 5. 1. 1, but allowing this time for each transit of the two planets a timing offset with respect to the reference transit ephemerides defined by the P and T 0 values reported in Table  3. We limited our search for TTVs to the ground-based transit photometry, as TESS individual transits do not have a high enough S/N to allow precise measurements of their timings. Table  5  presents the timings and corresponding TTVs that we obtained for the 13 transits of planet b and 4 transits of planet c that were observed from the ground.
TESS photometry As mentioned in Sect. 2. 1, LP 890-9 was observed by TESS in four sectors. While the TESS Science Office issued an alert for TOI-4306. 01 (LP 890-9 b), it did not report any other transit signal that could be related to LP 890-9 c or other planets in the system. However, due to the detection threshold (MES = 7. 1σ) to issue an alert by the automatic SPOC and Quick Look (QLP) pipelines, some lower S/N transit signals may have gone unnoticed. We thus performed our own search for transit signals in the TESS data using our custom SHERLOCK 9  pipeline  (Pozuelos et al. 2020; Demory et al. 2020). SHERLOCK is an end-to-end pipeline that combines six different modules that allow exploring the TESS data fast and robustly. These six modules consist of (1) downloading   is found, it is stored and masked, and then the search keeps running until no more signals above a user-defined S/N threshold are found in the dataset.
Following  Wells et al. (2021) , several scenarios may explain the lack of extra signals in TESS data: (1) no other planets exist in the system; (2) if they do exist, they do not transit; or (3) they do exist, but the photometric precision of the data is not good enough to detect them, or they have periods longer than the ones explored in this study. If scenario (2) or (  3 ) is true, extra planets might be detected by means of RV follow-up as discussed in Sect. 8. 2. On the other hand, we know from the ground-based photometric follow-up that there is at least a second transiting planet in the system, LP 890-9 c. The fact that it was undetected by both the SPOC and SHERLOCK transit searches suggests that we are limited in this case by its detectability in the TESS data (scenario 3). To explore the detection limits of the TESS data, we used our MATRIX ToolKit 10  (Dévora-Pajares & Pozuelos 2022), which was used successfully in a number of previous studies (see, e.
Radial velocity analysis We analysed the Subaru/IRD data using the juliet package  (Espinoza et al. 2019) , which is built over radvel  (Fulton et al. 2018)  for the modelling of radial velocities and the dynesty (Speagle 2020) dynamic nested sampling algorithm for estimating Bayesian posteriors and evidences. We modelled the RVs using a sum of two Keplerians (one for each planet) and assumed circular orbits. We imposed normal priors on the orbital period P and mid-transit time T 0 of each planet based on the results of our global transit analysis reported in Table  3. We assumed wide uniform priors between 0 and 500 m s -1 for the RV semi-amplitudes K. We treated the Y J-band and H-band RVs as independent datasets, thus fitting for each of them a different zero point (systemic RV) and extra jitter term.
For each dataset, this jitter is added quadratically to the measurement errors of the data points, to account for any underestimation of the uncertainties or any excess noise not captured by the model. Figure  16  shows the results of our RV fit. The data are plotted with both their original error bars (thick solid lines) and the error bars enlarged by the best-fit jitter terms (thinner transparent lines). These jitters are large (33. 0 +10. 5 -7. 4 m s -1 for the Y J-band and 19. 6 +5. 7 -4. 3 m s -1 for the H-band) and the datasets are rather limited, so that the RV semi-amplitudes of the two planets are poorly constrained and we were only able to derive upper limits: K < 25. 1 m s -1 for planet b and K < 33. 0 m s -1 for planet c (2σ upper limits). The derived upper limits on the planetary masses (using the orbital inclinations from our transit analysis, Table  3 ) are M p < 13.
2 M ⊕ for planet b and M p < 25. 3 M ⊕ for planet c at 2σ. Both are well within the planetary regime. The large extra jitters returned by our 2-planet fit suggest that there is some variability in the data that is not captured by the model. One possible explanation is that there may be an additional planet in the system which produces a detectable RV signal but was not detected in our photometry (either because it is not transiting or because it is beyond the detection limits of our photometric dataset). We thus tried adding a third planet as a third Keplerian in the model, using a wide uniform prior between 1 and 125 days (the time baseline of the RV data) for its orbital period. Comparing the Bayesian evidences Z of the two models, we found that the 3-planet model is only weakly disfavoured compared to the 2-planet one (∆ ln Z = -0.
65). The orbital period found for the third Keplerian is 64 +11 -9 days, with a 2σ upper limit on its semi-amplitude of 49 m s -1. Instead of adding a third Keplerian in the model, we also tried including a linear trend that could be created by a third planet with an orbital period longer than the time baseline of the RV data. We found this model to be marginally disfavoured (∆ ln Z = -3. 72) compared to the 2planet model. Since the 2-planet model is the simplest of the three models we tested and it has the highest Bayesian evidence, it appears to be the best model given the data at hand. However, additional planets in the system might be revealed with more RV data. The variability seen in the current RV dataset may also be (at least partly) related to stellar activity. In this context, it is worth noting that the period of 64 +11 -9 days found for the third Keplerian in the above 3-planet fit is within the range of the possible rotation period of 50-55 days suggested by the SSO photometry (Sect.
Expected TTVs As described in Sect. 5. 1. 3, we do not detect any significant TTVs in the current photometric dataset, although the two planets are close to the second-order 3:1 mean motion resonance (but not exactly within: P c /P b = 3. 098). In general, the lack of observed TTVs might be caused by either their low amplitude or the poor baseline coverage provided by the observational data. In our case, the ground-based observations that we used to explore TTVs were obtained over ∼150 days, which is much longer than the super-period of 2. 64 days  (Lithwick et al. 2012)  for LP 890-9 b and c. Hence, our ground-based data should show any TTVs if they were large enough. To test the expected TTV amplitudes in the system, we used the TTVFast2Furious package  (Hadden 2019)  following the strategy presented by  Cloutier et al.
Stability From the current dataset, we concluded that the LP 890-9 system is composed of at least two planets orbiting in nearly circular orbits and with similar planetary sizes. To assess the global stability of the system, we used the Mean Exponential Growth factor of Nearby Orbits (MEGNO;  Cincotta & Simó 1999 , 2000; Cincotta et al. 2003) , Y(t) parameter. This chaos index is widely used to explore the stability of extrasolar planetary systems (e. g. ,  Hinse et al. 2015; Jenkins et al. 2019; Delrez et al. 2021 ). In short, its time-averaged mean value, Y(t) , amplifies any stochastic behaviour, which can be used to distinguish between quasiperiodic orbits, if Y(t → ∞) → 2, or chaotic trajectories, if Y(t → ∞) → ∞. We made use of the MEGNO implementation with the N-body integrator REBOUND  (Rein & Liu 2012) , which employs the Wisdom-Holman WHfast code  (Rein & Tamayo 2015).
In our Solar System, that translates to 1. 76 current Earth's incident irradiation (S ⊕ ) for Venus around 1 billion years ago and 0. 32 S ⊕ for Mars about 3. 8 billion years ago, providing empirical proxies for the incident flux limits of habitability. The inner edge of the empirical HZ is not well known because of the geological active history of Venus' surface. The outer edge of the HZ in 3D models agrees with incident stellar flux for Early Mars insulation. The empirical HZ provides an empirical dataset for the search for habitable planets, complementary to modelling efforts. Cool stars warm an Earth-like planet's surface more effectively than hotter stars (see, e. g. ,  Kasting et al. 1993 ). Thus, for LP 890-9, the inner limits of the HZ are 1. 49 S ⊕ for the empirical and 0. 92 S ⊕ for the conservative HZ respectively  (Kopparapu et al.
BJD TDB -2 450 000 RV (km/s) σ RV (km/s) Table A. 1. Subaru/IRD radial velocity measurements. We recommend treating the Y J-band and H-band RVs as independent datasets, as done in the analysis presented in Sect. 6. A59, page 28 of 31 L. Delrez et al. : Two temperate super-Earths transiting LP 890-9.
TRAPPIST is funded by the  Belgian Fund for Scientific Research (Fond National de la Recherche Scientifique, FNRS)  under the grant  PDR T. 0120. 21 ,with the participation of the Swiss National Science Fundation (SNF). This work is partly supported by  MEXT/JSPS KAKENHI  Grant Numbers  JP15H02063 ,  JP17H04574 ,  JP18H05439 ,  JP18H05442 ,  JP19K14783 ,  JP21H00035 ,  JP21K13975 ,  JP21K20376 ,  JP22000005 ,  Grant-in-Aid for JSPS Fellows Grant Number   JP20J21872 ,  JST CREST  Grant Number  JPMJCR1761 , the  Astrobiology Center of National Institutes of Natural Sciences (NINS)  (Grant Numbers  AB031010 ,  AB031014 ), and Social welfare juridical person SHIYUKAI (chairman MASAYUKI KAWASHIMA). This paper is based on data collected at the  Subaru Telescope , which is located atop Maunakea and operated by the  National Astronomical Observatory of Japan (NAOJ).