Update chgres_cube for mixed land/non-land points #123
Comments
|
Can this be closed since chgres_cube has been deleted? |
Do you mean global_chgres? |
|
Whoops! Got confused. ;-) |
|
@GeorgeGayno-NOAA George, are you still planning to update chgres-Cube for fractional grid ? The current process of creating cold start ICs for the coupled model documented in #145 is rather clumsy. (Including @arunchawla-NOAA and @shansun6 for their input ) |
If this is still a requirement, I can work on it, or help someone else do the work. |
|
@GeorgeGayno-NOAA Making CHGRES consistent with the fractional grid used by the model is necessary. It also helps streamline the creation of ICs and avoids confusion. (@arunchawla-NOAA ) |
|
@yangfanglin and @shansun6 - Do you have a sample coldstart file for running with mixed land/non-land? A sample file you create from this procedure - https://docs.google.com/document/d/15FtEHUoN9JTmt_q4Qt1kdSb1rSbjQDYMpMiKaxtn404/edit?usp=sharing |
For non-fractional grids, the soil temperature field was used for both land and non-land. Now points can have both land and sea ice. Fixes ufs-community#123.
@shansun6 I was looking at your document. You are adding only two new variables, a skin temperature and roughness for land. What about soil temperature (stc)? At lake/sea ice points, the ice model uses that record for its column temperatures. For a point that is both land and ice, separate records will be needed. |
|
Currently, chgres places a roughness value of 1 cm at ice points? Does the model actually use this value from the coldstart file? If so, we will need three 'zorl' records. A similar question for the snow-free albedo (alvsf/alvwf/alnsf/anfwf). Flag values of 0.06 are placed at non-land points (both water and ice). Does the model uses these values from the coldstart file. If so. additional albedo records will be needed. @barlage who on the land team should I ask? |
|
@GeorgeGayno-NOAA Hopefully @shansun6 and @barlage can address questions. Bing Fu might be able to point you to the ICs you need as well. For the roughness over ice, please see the discussion in NCAR/ccpp-physics#808 . Helin and Weizhong can also help answer the question. |
@GeorgeGayno-NOAA You can find sample IC here on Hera: /scratch2/NCEPDEV/stmp3/Bing.Fu/o/p7ic/com/gens/dev/merge_fix/C384_025 |
@GeorgeGayno-NOAA Here includes both model level IC data as well as surface IC data. |
|
Some clarification from @shansun6 concerning the definition of 'fice' with fractional grids:
|
|
Clarification from @shansun6 concerning the 'stc' array - it is only used at points with land. It is not used for ice or open water. |
|
Hi George,
I spoke too soon regarding "stc". In the non-fractional case, 'stc'
contains both 4-layer soil temp and 2-layer internal ice temp.
Now in the fractional case, 'stc' contains soil temp only, which means we
would lose info of 2-layer internal ice temp, right?
Do we need to add an additional array (:,:,2) to store the 2-layer internal
ice temp?
The corresponding part of FV3GFS_io.F90 would need to be modified as well:
if (nint(sfc_var3ice(1,1,1)) == -9999) then !--- initialize internal
ice temp from layer 1 and 2 soil temp
if (Model%me == Model%master ) call mpp_error(NOTE,
'gfs_driver::surface_props_input - computing tiice')
do nb = 1, Atm_block%nblks
do ix = 1, Atm_block%blksz(nb)
Sfcprop(nb)%tiice(ix,1) = max(timin, min(con_tice,
Sfcprop(nb)%stc(ix,1)))
Sfcprop(nb)%tiice(ix,2) = max(timin, min(con_tice,
Sfcprop(nb)%stc(ix,2)))
enddo
enddo
endif
I can modify FV3GFS_io.F90 when the time comes.
Sorry for not thought of this in the first time,
Shan
…On Thu, Mar 10, 2022 at 2:19 PM GeorgeGayno-NOAA ***@***.***> wrote:
Clarification from @shansun6 <https://github.com/shansun6> concerning the
'stc' array - it is only used at points with land. It is not used for ice
or open water.
—
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALORMVX6W44367T3K4OY673U7JRPBANCNFSM4PF2TESA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I will output a separate 'stc' array for sea ice.
On Thu, Mar 10, 2022 at 6:02 PM ShanSun-NOAA ***@***.***>
wrote:
… Hi George,
I spoke too soon regarding "stc". In the non-fractional case, 'stc'
contains both 4-layer soil temp and 2-layer internal ice temp.
Now in the fractional case, 'stc' contains soil temp only, which means we
would lose info of 2-layer internal ice temp, right?
Do we need to add an additional array (:,:,2) to store the 2-layer internal
ice temp?
The corresponding part of FV3GFS_io.F90 would need to be modified as well:
if (nint(sfc_var3ice(1,1,1)) == -9999) then !--- initialize internal
ice temp from layer 1 and 2 soil temp
if (Model%me == Model%master ) call mpp_error(NOTE,
'gfs_driver::surface_props_input - computing tiice')
do nb = 1, Atm_block%nblks
do ix = 1, Atm_block%blksz(nb)
Sfcprop(nb)%tiice(ix,1) = max(timin, min(con_tice,
Sfcprop(nb)%stc(ix,1)))
Sfcprop(nb)%tiice(ix,2) = max(timin, min(con_tice,
Sfcprop(nb)%stc(ix,2)))
enddo
enddo
endif
I can modify FV3GFS_io.F90 when the time comes.
Sorry for not thought of this in the first time,
Shan
On Thu, Mar 10, 2022 at 2:19 PM GeorgeGayno-NOAA ***@***.***>
wrote:
> Clarification from @shansun6 <https://github.com/shansun6> concerning
the
> 'stc' array - it is only used at points with land. It is not used for ice
> or open water.
>
> —
> Reply to this email directly, view it on GitHub
> <
#123 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ALORMVX6W44367T3K4OY673U7JRPBANCNFSM4PF2TESA
>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
>
> or Android
> <
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
>.
>
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMSYBTF5HFRVRRMFWEZXHODU7J5P7ANCNFSM4PF2TESA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
George Gayno
IMSG at NOAA/NWS/NCEP/EMC
5830 University Research Ct., Rm. 2882
College Park, MD 20740
***@***.***
301-683-3658
|
fractional grid option. Fixes ufs-community#123.
latest fractional orog and grid files. Fixes ufs-community#123
the fractional orog and grid files. Fixes ufs-community#123.
regional test cases. Fixes ufs-community#123.
fractional 'oro' and 'grid' files. Fixes ufs-community#123.
'oro' and 'grid' files. Fixes ufs-community#123.
all points with at least some land. Fixes ufs-community#123.
data at all points with some land. Fixes ufs-community#123.
…ectory than the one used by the orion script. Fixes ufs-community#123.
Update chgres_cube for fractional (partial land/non-land) grids. Outputs a new surface coldstart file (called version 2). Update the sfc_climo_gen program to always map surface data to points with at least some land. Prevously, that only was done for grids with lakes. Fixes #123.
The grid generation is being updated to output lake fraction and lake depth (#111). As a result, some model grid points will be a mix of land and non-land. Currently,
chgres_cubeassumes that points can only be land or non-land, not both. Updatechgres_cubeaccordingly.The text was updated successfully, but these errors were encountered: