webgeodyn

webgeodyn is a web-based plot tool to visualize Earth core flows and scalar fields at the Core Mantle Boundary (CMB). It consists in a Tornado web server, that can be started locally, that provides a set of visualisations tools on a variety of data formats.

Installation

Requirements

The installation of webgeodyn requires Python 3 to be installed.

The other dependencies will be automatically installed by the next step but are listed here for the sake of completeness:

• numpy
• scipy
• h5py
• tornado

Installing the package

webgeodyn can be installed

• from pip:

pip3 install webgeodyn [--user]

Put the --user flag if you are not installing in a virtual environment.

• from the git repository :

Clone first the webgeodyn repository

git clone https://gricad-gitlab.univ-grenoble-alpes.fr/Geodynamo/webgeodyn

Then install the package:

cd webgeodyn
python3 setup install [--user]

Again, put the --user if needed.

Whatever the method used, you can test if the install succeed by importing webgeodyn in Python3:

python3 -c "import webgeodyn; print(webgeodyn.__version__)"

This command should return the installed version.

Running the example

You can give a first try at starting the web server by running the example:

python3 webgeodyn/example.py

or in the Python console:

>>> import webgeodyn.example

This starts the server locally and should open your browser and display a page ressembling the one at https://geodyn.univ-grenoble-alpes.fr/. If not, try to type http://localhost:8080 in your browser.

You can try the different visualisations tools provided on the loaded example model (CHAOS-6).

Note that this example will also try to load the result from the latest pygeodyn computation (if present in ~/pygeodyn_results/Current_computation/).

Running the server with your data

The server can be used to visualise any data of supported format. For that, it is necessary to follow the template of example.py:

• First, load the data under the form of Model objects, of a given name and format, in a Models dictionary.
• Then, the server must be started with the loaded Models.

This is shown in details below:

# 0.Import the necessary submodules
import webgeodyn.server
import webgeodyn.models

# 1.Initialising the Models dictionary
models = webgeodyn.models.Models()

# 2.Loading your data in the Models dictionary
# Syntax: models.loadModel('/path/to/the/model/directory', "Name of the model", "Format of the model")
models.loadModel('pygeodyn_results/Current_computation', 'Current pygeodyn computation', 'pygeodyn_hdf5')
# Several models can be loaded. Example for CHAOS
models.loadModel('webgeodyn/webgeodyn/example_data/CHAOS-6-x4', 'CHAOS-6-x4 model', 'CHAOS')

# 3.Start the server with the loaded Models
webgeodyn.server.startServer(models)

By copying this code in a Python file of your own, you should be able to use the visualisation tools on data of supported formats.

The format of the models, that define the format of the files to read, are the modules of webgeodyn.inout. Here are a few:

• pygeodyn_hdf5: to read HDF5 files generated by pygeodyn
• chaos: to read CHAOS splines files
• covobs: to read COVOBS realisations files

A list of the formats can be displayed by running:

import webgeodyn.inout
print(webgeodyn.inout._formats)

If you need the support of a new format of file, you can follow the templates given in webgeodyn/inout to implement your own loading function. Otherwise, you can contact us using the information given below.

Developer documentation

Documentation of the submodules and methods of the package are available on line.

If Sphinx is installed and the files were cloned from the repository, it is possible to generate the documentation locally using:

cd doc && ./make_all_doc.sh

The documentation will then be available in HTML format for both Python and JavaScript at doc/html/index.html.

Conditions of use

The work is licensed under the GNU GPLv3.

Git repository

The source code is stored on a Git repository (https://gricad-gitlab.univ-grenoble-alpes.fr/Geodynamo/pygeodyn) which can also be used to give feedbacks through Issues.

Contact information

For scientific inquiries, contact Nicolas Gillet. For technical problems, contact Loïc Huder or Franck Thollard.