-
Notifications
You must be signed in to change notification settings - Fork 67
Frank ice #694
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frank ice #694
Conversation
|
Should we merge this as is, or wait till the next major release and change the default settings for standalone FESOM? |
|
I will clean it a bit - there are a couple of variables that we can delete. Then we can merge. The plan is also to do some tests with new namelist in a separate issue, but it is irrelevant for this merge. Change to WIP. |
|
@JanStreffing I cleaned up a bit. In order to be able to use Frank's new settings, though, we have to solve the problem with h0. Now it is hardcoded, and setting in namelist do not have an effect: Lines 283 to 290 in d1fa4f6
I am for having two separate h0 values. We can add |
|
it was practically used, to have different h0 values for NH and SH, if needed. |
Sure, but:
|
|
I'd say we should
I'm not too knowledge with the standalone model, but with coupled model I found years ago that lead closing parameter tuning, especially hemispherical was getting me the better sea ice concentration and thickness, but worse T2M. I ended up tuning all three to better values with hemispherical albedo changes, parameterizing the different melt pond states. The SO albedo is higher than Arctic at the height of summer. See: https://github.com/AWI-ESM/project_management/issues/14 In a second step, I then took the hemispherical albedo out again. Instead, I increased snow on ice albedo, while decreasing bare ice melting albedo. The effect was the same, but it's more physical. |
….ice_ERA5 to config
|
I did the split of h0, and add namelist for ERA5. |
|
ready for merge? |
|
Yes we can merge it. |
No description provided.