Skip to content

Commit

Permalink
Documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
frostedoyster committed Jun 13, 2024
1 parent 02c2ace commit 315f159
Show file tree
Hide file tree
Showing 4 changed files with 21 additions and 0 deletions.
1 change: 1 addition & 0 deletions docs/src/dev-docs/utils/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -23,3 +23,4 @@ This is the API for the ``utils`` module of ``metatrain``.
omegaconf
output_gradient
per_atom
units
7 changes: 7 additions & 0 deletions docs/src/dev-docs/utils/units.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
Unit handling
#############

.. automodule:: metatrain.utils.units
:members:
:undoc-members:
:show-inheritance:
1 change: 1 addition & 0 deletions docs/src/getting-started/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -12,3 +12,4 @@ This sections describes how to install the package, and its most basic commands.
advanced_base_config
override
checkpoints
units
12 changes: 12 additions & 0 deletions docs/src/getting-started/units.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
Units
=====

``metatrain`` will always work with the units as provided by the user, and all logs will
be in the same units. In other terms, ``metatrain`` does not perform any unit
conversion. The only exception is the logging of energies in ``meV`` if the energies are
declared to be in ``eV``, for consistency with common practice and other codes.

Although not mandatory, the user is encouraged to specify the units of their datasets
in the input files, so that the logs can be more informative and, more importantly, in
order to make the resulting exported models usable in simulation engines (which instead
require the units to be specified) without unpleasant surprises.

0 comments on commit 315f159

Please sign in to comment.