<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">8172</controlfield>
  <controlfield tag="005">20260914101432.0</controlfield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="a">CTALK-2026-0140</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Rivoldini, Attilio</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Constraining Mercury’s Interior Structure From Geodesy Data And Thermal State</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2026</subfield>
  </datafield>
  <datafield tag="269" ind1=" " ind2=" ">
    <subfield code="c">2026-08-04</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Interior structure inferences of Mercury based on geodesy data can be strongly affected by prior assumptions about the detailed thermal structure of the core. In particular, the presence of a conductive, upper core thermally stratified layer (CTSL) is often neglected, although it directly affects the temperature profile of the core and, as a result, core composition and inner core radius inferences. The upper CTSL is a key ingredient in numerical dynamo simulations that are able to explain important features of Mercury’s magnetic field. Additional support for a CTSL layer also follows from thermal evolution studies using constraints on dynamo action in the core. In this study, we assess how core composition assumptions, the present-day thermal state, and theCTSLaffectMercury’sannuallibrationamplitude,long-periodlibration,obliquity,andtidal Love numbers. To determine the present-day thermal state, we use results from whole-planet thermal evolution simulations that are consistent with assumptions on core composition and are constrained by crustal thickness and past and present dynamo activity. We also investigate the effects of internal couplings and dynamical shape of the libration and obliquity.</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="a">3PRODPLANINT/</subfield>
    <subfield code="c">3PRODPLANINT/</subfield>
    <subfield code="f">3PRODPLANINT</subfield>
  </datafield>
  <datafield tag="594" ind1=" " ind2=" ">
    <subfield code="a">NO</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Tosi, Nicola</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Lécaille, Manon</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Van Hoolst, Tim</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Trinh, Anthony</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Baland, Rose-Marie</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Yseboodt, Marie</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Xiao, Haifeng</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="t">46th COSPAR Scientific Assembly 2026, Florence, Italy</subfield>
  </datafield>
  <datafield tag="856" ind1="0" ind2=" ">
    <subfield code="f">attilio.rivoldini@ksb-orb.be</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">5930568</subfield>
    <subfield code="u">http://publi2-as.oma.be/record/8172/files/Cospar 2026 Florence.pdf</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">10386</subfield>
    <subfield code="u">http://publi2-as.oma.be/record/8172/files/Cospar 2026 Florence.gif?subformat=icon</subfield>
    <subfield code="x">icon</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">8452</subfield>
    <subfield code="u">http://publi2-as.oma.be/record/8172/files/Cospar 2026 Florence.jpg?subformat=icon-180</subfield>
    <subfield code="x">icon-180</subfield>
  </datafield>
  <datafield tag="906" ind1=" " ind2=" ">
    <subfield code="a">Contributed</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">CTALKCONT</subfield>
  </datafield>
</record>
</collection>