Graphical user interface to perform glacier simulations with PISM

Computer simulations of glacial dynamics help us understand how glaciers respond to changes in climate, such as warming temperatures and increased precipitation. Simulations are performed with PISM (Parallel Ice Sheet Model). To tackle the complexities of ice dynamics, PISM employs several sub-model...

Full description

Saved in:
Bibliographic Details
Published in2023 46th MIPRO ICT and Electronics Convention (MIPRO) pp. 315 - 320
Main Authors Urbanc, M., Depolli, M.
Format Conference Proceeding
LanguageEnglish
Published MIPRO Croatian Society 22.05.2023
Subjects
Computational modeling
Computer simulation
distributed execution
glacier simulations
Ice
jupyter
PISM
Precipitation
remote management
Remote working
Software
user interface
Workstations
Online AccessGet full text

Cover

More Information
Summary:Computer simulations of glacial dynamics help us understand how glaciers respond to changes in climate, such as warming temperatures and increased precipitation. Simulations are performed with PISM (Parallel Ice Sheet Model). To tackle the complexities of ice dynamics, PISM employs several sub-models for various aspects and thus exposes a plethora of parameters. There are also several options for setting parameter values, i.e. through config files, command line options or input files. To get a good handle on all the provided buttons and knobs, we developed a user interface for setting parameters of out simulations and for executing PISM with the selected set of parameters on a remote workstation.In this paper we present the GUI developed in Jupyter and deployed in a local JupyterLab installation. The environment contains DEM files, Python scripts and other inputs locally but connects to a 128-core workstation for simulation execution. The simulation inputs and outputs are transferred between the computers over an SSH connection. The GUI is publicly exposed in a single-user environment, only for use, while development is performed on a git repository which is then synchronized to the public through git. This approach is general enough to be used on other software as well.
ISSN:2623-8764
DOI:10.23919/MIPRO57284.2023.10159747