Overview

This is the homepage of the Tsunami Lab taught at Friedrich Schiller University Jena by the Scalable Analyses lab. Most information will be shared here. However, some data, e.g., data concerning exams, will be shared only through respective FSU channels: e-mail, Moodle or Friedolin.

Let me know if you get stuck, stumble over errors, or have any other feedback:

_images/mpi_scaled.png

Fig. 1 Visualization of an MPI-parallelized tsunami simulation of the March 11, 2011 M 9.1 Tohoku event running on 16 ranks.

Format

Our meetings take place in the following time slot:

  • Mon, 12:15PM - 03:15PM

All meetings are face-to-face in room 3220, EAP2.

The lab has a Matrix room hosted on the university’s Matrix server. You may join the channel with any Matrix account, including those registered with other servers. The Matrix invite to the class’s room is shared in Moodle. The room is not encrypted, and you will only see the room’s history from the time since you joined.

Schedule

Lectures

Date(s)

Welcome, f-wave Solver

10/16

Riemann Problems and Solutions

10/30

Digital Elevation Models

11/06

Dimensional Splitting

11/13

NetCDF

11/20

Okada Model, Map Projections, Bathymetry

11/27

Benchmarking

12/04

Optimization and Instrumentation

12/11

Get Together 🍕 (starts at 6PM)

02/05

Project Phases

Due Date

Presentation

Riemann Solver

10/29

10/30

Finite Volume Discretization

11/05

11/06

Bathymetry & Boundary Conditions

11/12

11/13

Two-Dimensional Solver

11/19

11/20

Large Data Input and Output

11/26

11/27

Tsunami Simulations

12/03

12/04

Checkpointing and Coarse Output

12/10

12/11

Optimization

12/17

12/18

Individual Phase (10.1’s draft)

12/17

individual

Parallelization

01/07

01/08

Individual Phase (10.2’s proposal)

01/07

01/08

Individual Phase (status)

01/22

Individual Phase (final)

02/04

02/05

Submissions

Our lab follows good software engineering practices. In short: Have a keen eye on the quality of your software, future you will be thankful! Do the following:

  • Document your source code, especially all functions you introduce.

  • Write meaningful commit messages.

  • Develop and maintain unit tests for all software pieces. Make it a habit to introduce unit tests together with new features, this makes this requirement painless.

  • Take “issues” seriously, e.g., compiler warnings, and do not take shortcuts: no hacks!

  • Test your software and your user guides on the reference-machine(s).

If not stated otherwise, the following deliverables have to be handed for every phase of the project:

  • Code in a hosted git repository. You may use the university’s GitLab server git.uni-jena.de or any other hosting solution, e.g., GitHub. Source code documentation and unit tests are mandatory.

  • Visualizations of conducted runs.

  • User documentation using Sphinx on how to build and use your code. Include a compiled version of your documentation. You may host your documentation as well, for example, by using Read the Docs.

  • Project report using Sphinx with 1-2 pages addressing the respective submission. Briefly address the individual contributions of each group member.

  • Slides for your presentation at the next meeting. Remember to address all questions in the tasks.

We use Moodle for all submissions:

  1. Upload a single tar.xz file to Moodle which contains all files of your submission.

  2. Submit links to the public or private git repository containing the code of your submission. Include links to other data where appropriate. Note: You must submit the links every week, even they stay unchanged.