Skip to content

Commit

Permalink
doc
Browse files Browse the repository at this point in the history
  • Loading branch information
HajimeKawahara committed Aug 7, 2024
1 parent cd81d36 commit 27f1cb4
Showing 1 changed file with 11 additions and 1 deletion.
12 changes: 11 additions & 1 deletion documents/userguide/api.rst
Original file line number Diff line number Diff line change
@@ -1,14 +1,24 @@
ExoMol, HITEMP, HITRAN
--------------------------------------

*July 2th (2024) Hajime Kawahara, Yui Kawashima, Yui Kasagi*
*August 7th (2024) Hajime Kawahara, Yui Kawashima, Yui Kasagi*

Since version 1.2, the standard molecular database I/O for ExoMol, HITEMP, and HITRAN was shared with the `radis <https://github.com/radis/radis>`_ team.
We moved the I/O for these database to `exojax.spec.api <../exojax/exojax.spec.html#module-exojax.spec.api>`_.

.. contents::
:depth: 2

.. admonition:: On the radis engine: Vaex or pytables?

Up until radis 1.4, vaex was used as the file IO engine. However, since vaex has been unable to support Python 3.11 and beyond,
starting from radis 0.15, vaex has become optional, allowing users to choose between pytables and vaex. In response to this change,
ExoJAX adopts the same policy as radis. The choice of which engine to use is made automatically,
but users can specify their preference during the initialization of mdb
by setting ``engine = "vaex"`` or ``engine = "pytables"``. The file extension ``.hdf5`` is associated with vaex, while ``.h5`` is used for pytables.
Given that vaex supports lazy IO, it can provide faster loading times when available.



ExoMol
==========
Expand Down

0 comments on commit 27f1cb4

Please sign in to comment.