andreww / slurry

Simple calculations on a slurry in the F-layer
MIT License
0 stars 0 forks source link

Supplementary material: modelling the F-layer in Earth’s core as a non-equilibrium slurry

These files are part of the supplementary material for the manuscript "Modelling the F-layer in Earth’s core as a non-equilibrium slurry" by A. M. Walker, C. J. Davies, A. J. Wilson and M. I. Bergman to be submitted to Proceedings of the Royal Society A. A preprint of this manuscript can be found EarthArXiv.

The files are source code files in python which implement the model described in the manuscript along with Jupyter notebook files that demonstrate aspects of the model, provide additional information on its derivation, and generate the figures shown in the paper. All software is made available under an MIT license which permits reuse subject to conditions found in the LICENSE file.

Jupyter notebooks

This repository contains the following notebooks implementing or describing the model:

F-layer cases

For the cases reported in the manuscript (in Table 1 of the SI, and in Figures 7 amd 8) we ran the models in "batch" mode, stored the results, and use the final notebook to plot these. The command line programme used to run a single set of cases (fixed parameters, but a grid search over DT and DX looking for "Earth like" models) is layer_models.py which is intended to run in a directory and populate this with output for different temperature and composition profiles. These directories (and the input parameter sets) are set up by cases/run_cases.py which copies and modifies the files in cases/template before launching the shell script cases/template/run.sh. It takes a week or two (on a M1 Mac Min) to run all cases and this process generates approximatly 4 GB of data once compressed. We do not include this data alongside the code.

Other files and further development

Some of the code (and notebooks inside development_work) are not used to create the models presented in this manuscript. These represent several alternitive lines of development and possible future work. Notably, much of the code in the repository is in need of refactoring ahead of further development of the work presented here.