Skip to content

Restore the lakes on a dynamic-mesh regeneration - #59

Open
JanStreffing wants to merge 1 commit into
masterfrom
feat/lakes-on-the-dynamic-mesh
Open

Restore the lakes on a dynamic-mesh regeneration#59
JanStreffing wants to merge 1 commit into
masterfrom
feat/lakes-on-the-dynamic-mesh

Conversation

@JanStreffing

Copy link
Copy Markdown
Owner

The lake restore from #58 is off by default, which is right for a static regeneration: it changes published files, so it has to be asked for. The dynamic path is the opposite case. There the coastline moves with the ice sheet and the mask is rebuilt every cycle, so the flip destroys the lake fields again on every leg and nobody is there to ask.

Measured on the TCO95 cavity submesh, both the pool chunk-1 ICMGG and the file couple_in regenerated for ismtest36 carry cl >= 0.5 at zero cells, against 70 in the pristine input. The Caspian and the Great Lakes are among them, so FLake had nothing to integrate anywhere, on every -is run so far.

Set through setdefault, so a template that has already decided still wins.

The lake restore added in 437fdeb is off by default, which is right for a
static regeneration: it changes published files, so it has to be asked for.
The dynamic path is the opposite case. There the coastline moves with the ice
sheet and the mask is rebuilt every cycle, so the flip destroys the lake
fields again on every leg and nobody is there to ask.

Measured on the TCO95 cavity submesh, both the pool chunk-1 ICMGG and the file
couple_in regenerated for ismtest36 carry cl >= 0.5 at zero cells against 70 in
the pristine input. The Caspian and the Great Lakes are among them, so FLake
had nothing to integrate anywhere, on every -is run so far.

Set through setdefault, so a template that has already decided still wins.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant