Elmer/Ice Challenge

Owned by Ophir Maor
Last updated: Jun 01, 2020 by Thomas Zwinger (Unlicensed)
3 min read

Elmer/Ice is a full-Stokes, finite element, ice sheet / ice flow model. The aim of this website is to present the capabilities of Elmer/Ice and to distribute course materials and tutorials.
Elmer/Ice is an add-on package to Elmer, which is a multi-physics FEM suite mainly developed by CSC-IT Center for Science Ltd., Espoo, Finland. Initially started by CSC,  IGE and ILTS, currently multiple institutions and individuals contribute to the development of Elmer/Ice.

The assignment will be lead by Senior Application Scientist, Thomas Zwinger from CSC-IT Center for Science Ltd. in Finland.

In this assignment you will be analyzing ice movement in Greenland.

Task 1: Build and run Elmer/Ice on the given input. submit the output results and log files.

You will be provided with a so-called Solver Input File (SIF), Stokes_steady_vec_lua.sif, declaring the applied numerical and physical parameters for the finite element analysis. The main SIF imports the partial SIF's containing definitions for the mesh database, header.sif, and for numerical settings solversettings.sif of the Stokes solver. It also reads a LUA file for physical parameters and functions, stokes.lua. The provided setup has been verified to converge on a 4-node (96 core) Haswell system, but there is room for optimization under the given constraints:

  • You are not allowed to edit the main Solver Input File (SIF), Stokes_steady_vec_lua.sif

  • You are not allowed to edit the definition file stokes.lua

  • You are allowed to make changes to existing settings in header.sif and solversettings.sif.

  • You are not allowed to add additional lines in header.sif and solversettings.sif. You may comment whole existing lines by an exclamation mark ! at the beginning of the line or uncomment commented lines by removing it

  • You are allowed to modify third-party libraries linked into Elmer (Lapack, BLAS, ...)

We are expecting the following files to be delivered (output and all necessary files to reproduce your run):

  • Output file of one run with unaltered settings (i.e., the original files provided to you), elmer_orig_temanme.txt

  • The whole set of solver input files (in case you applied changes): solversettings.sif, header.sif and (for control, as it should remain unchanged) Stokes_steady_vec_lua.sif

  • The whole output of the run in a text file, elmer_teamname.txt

  • The job submission script (PBS)

  • The configuration and compilation script of Elmer on the system

  • If applicable, changes to source code in terms of changed source code files (with respect to the tagged version on GitHub)

  • If applicable, the configuration and compilation script as well as the source of all libraries that have been compiled by the team and linked with Elmer

We will be looking on the exact output of the whole run and in particular on the SOLVER TOTAL TIME at the end of this file:

... SOLVER TOTAL TIME(CPU,REAL): 34.49 45.64

 

To get started see: https://hpcadvisorycouncil.atlassian.net/wiki/spaces/HPCWORKS/pages/1169784836.

Task 2: Use Paraview or other mechanism to create the visualization of the velocity of the ice sheet output out of the *.vtu files written.

Task 3: Add a team name-tag with/or team photo in small into the image (to mark it) and post to your team’s twitter account if you have, or linkedIn account with the hashtags “#ISC20 #ISC20_SCC @ElmerIce1 @elmerfem” . If you don’t use social media, you can submit the file via the flash memory.

Task 4: Run the application again with IPM profile tool, and submit the profiling results for the given input.

References