J/A+A/583/A116 Mercury-T code (Bolmont+, 2015)
Mercury-T: A new code to study tidally evolving multi-planet systems.
Applications to Kepler-62.
Bolmont E., Raymond S.N., Leconte J., Hersant F., Correia A.C.M.
<Astron. Astrophys. 583, A116 (2015)>
=2015A&A...583A.116B 2015A&A...583A.116B (SIMBAD/NED BibCode)
ADC_Keywords: Models ; Stars, double and multiple ; Planets
Keywords: planets and satellites: dynamical evolution and stability -
planets and satellites: terrestrial planets -
planets and satellites: individual: Kepler 62 -
planet-star interactions
Abstract:
A large proportion of observed planetary systems contain several
planets in a compact orbital configuration, and often harbor at least
one close-in object. These systems are then most likely tidally
evolving. We investigate how the effects of planet-planet interactions
influence the tidal evolution of planets. We introduce for that
purpose a new open-source addition to the MercuryN-body code,
Mercury-T, which takes into account tides, general relativity and the
effect of rotation-induced flattening in order to simulate the
dynamical and tidal evolution of multi-planet systems. It uses a
standard equilibrium tidal model, the constant time lag model.
Besides, the evolution of the radius of several host bodies has been
implemented (brown dwarfs, M-dwarfs of mass 0.1M☉, Sun-like
stars, Jupiter). We validate the new code by comparing its output for
one-planet systems to the secular equations results. We find that this
code does respect the conservation of total angular momentum. We
applied this new tool to the planetary system Kepler-62. We find that
tides influence the stability of the system in some cases. We also
show that while the four inner planets of the systems are likely to
have slow rotation rates and small obliquities, the fifth planet could
have a fast rotation rate and a high obliquity. This means that the
two habitable zone planets of this system, Kepler-62e ad f are likely
to have very different climate features, and this of course would
influence their potential at hosting surface liquid water.
Description:
The major addition to Mercury provided in Mercury-T is the addition of
the tidal forces and torques. But we also added the effect of general
relativity and rotation-induced deformation. We explain in the
following sections how these effects were incorporated in the code.
We also give the planets and star/BD/Jupiter parameters which are
implemented in the code.
The link to this code and the manual can also be found here:
http://www.emelinebolmont.com/research-interests
File Summary:
--------------------------------------------------------------------------------
FileName Lrecl Records Explanations
--------------------------------------------------------------------------------
ReadMe 80 . This file
Mercury_manual.pdf 512 1420 Mercury-T manual
git_mercury.tar 512 49140 All Mercury-T code files
--------------------------------------------------------------------------------
Description of file: git_mercury.tar
Welcome to the git repository of Mercury-T!
Here are a few things to know:
- In order to compile the model, you need to execute the python script
Makefile.py
You can modify the compilation options to your liking. Right now, it's for
ifort.
- There are some files with the time evolution of the radius and some other
quantities for brown-dwarfs (mass_xx.xxxx.dat, where xx.xxxx is the mass of
the BD in Jupiter mass, i.e., 40.0000 corresponds to a 40 Mjup BD, or
0.04 Msun as you prefer; and rg2BD.dat with the moment of inertia
informations), for a 0.1 Msun Mdwarf (01Msun.dat), for a 1 Sun-mass star
(SRadSpliM-1_0000.dat).
- user_module.f90 is the place where tides are implemented
- tidesconstantGR.f90 is the file where the tidal parameters are and where
the initialization is done. If you modify this file, you have to
re-compile.
- There are 2 IDL scripts to charge and plot the data (charge_comp and
scriptplotcomp).
There is a makespin.sh script to create *.dat files out of the *.out files
(spin*.out, horb*.out, dEdt*.out). It also executes element.in to have the
PLANETi.aei files. This is used typically when you want to check a running
simulation.
- All the rest can be used as the normal Mercury code.
Acknowledgements:
Emeline Bolmont, emeline.bolmont(at)unamur.be
(End) Patricia Vannier [CDS] 03-Nov-2015