nansencenter / nansencenter/nextsim

model crashing in forecast depending on restart

Open
#39 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10
Forks
1
Avg merge
9d 2h
Merged PRs (30d)
1

Description

The forecast sometimes crashes when using the latest restart.

One example is in:
/mnt/10.11.12.232/nextsimf/nextsimf_forecasts/Kara_forecast/20180408-bak

It crashed on the 2nd time step, but I got it to run by manually modifying the config file to use the restart from /mnt/10.11.12.232/nextsimf/nextsimf_forecasts/Kara_forecast/20180406/restart/field_2.bin (instead of 20180407/restart/field_1.bin)

Speed got up to 160m/s in a very small opening (with 20% conc):
field_substepping_time_step_1_substep_1-m_vt-zoom
field_substepping_time_step_1_substep_1-concentration-zoom

Could be a problem with the Laplacian drift thing or something inconsistent with the assimilation. I'll test it without assimilation to see if it crashes still

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the crash in the Kara forecast at the reported path, comparing the 20180407 restart with the 20180406/restart/field_2.bin workaround. Test the forecast without assimilation as proposed and inspect the reported speed and concentration behavior. Done means identifying the restart or assimilation condition that causes the crash and validating its resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
hpc
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.