Opened 7 years ago
Closed 5 years ago
#1872 closed Enhancement (invalid)
NESTING TOOLS AGRIF read updated bathymetry for creating agrif restarts
Reported by: | jharlass | Owned by: | jchanut |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | AGRIF | Version: | v3.6 |
Severity: | minor | Keywords: | AGRIF bathymetry nesting |
Cc: | sciliberti |
Description
Context
Use bathy_updated from base model to correctly compute masks (partial steps) for nest restart creation.
Changes
agrif_create_restart.f90
-
(a) Revision vs. (b) Working
a b 113 113 ! 114 114 CALL set_child_name(parent_coordinate_file,Childcoordinates) 115 115 CALL set_child_name(parent_meshmask_file,Childbathy) 116 116 CALL set_child_name(parent_bathy_meter,Childbathymeter) 117 ! use bathy_updated for base model ONLY, if bathy_update=true in namelist.input 118 IF (bathy_update) THEN 119 parent_bathy_meter=updated_parent_file 120 END IF 121 117 122 ! create this file 118 123 ! … … 164 170 ! 165 171 ENDIF 166 172 ! 173 WRITE(*,*) 'Reading Bathymetry: ',TRIM(parent_bathy_meter) 174 CALL Read_Ncdf_var('Bathymetry',parent_bathy_meter,G0%bathy_meter) 175 176 WRITE(*,*) 'Reading mbathy : ',TRIM(parent_meshmask_file) 167 177 CALL Init_mask(parent_meshmask_file,G0,x,y) 178 WRITE(*,*) 179 WRITE(*,*) 'Reading Bathymetry: ',TRIM(Childbathymeter) 180 CALL Read_Ncdf_var('Bathymetry',Childbathymeter,G1%bathy_meter) 181 WRITE(*,*) 'Reading mbathy : ',TRIM(childbathy) 168 182 CALL Init_mask(childbathy,G1,1,1) 169 183 170 184 G0%tmask = 1.
Commit History (0)
(No commits)
Change History (7)
comment:1 Changed 7 years ago by nemo
- Keywords nesting added; NESTING removed
comment:2 Changed 7 years ago by jchanut
- Component changed from OPA to AGRIF
comment:3 Changed 6 years ago by clevy
- Owner changed from nemo to jchanut
comment:4 Changed 6 years ago by clevy
- Cc sciliberti added
- Owner changed from jchanut to sciliberti
- Status changed from new to assigned
comment:5 Changed 5 years ago by jchanut
- Owner changed from sciliberti to jchanut
- Severity set to minor
comment:6 Changed 5 years ago by jharlass
You are right and I can not entirely recall the reason. From my current perspective it is indeed better to use bathy_meter.nc to treat the input fields equally. We came across this issue when adding the partial step support in the creation process of all masks (Init_mask). When a nested configuration starts and the first update takes place immediately, base values will be overwritten by nest values in any way. So either either bathy_updated would not fit not fit to the base restart or the base restart will not fit to 1_bathy_meter.
Ticket can be closed and proposed change dismissed.
comment:7 Changed 5 years ago by jchanut
- Resolution set to invalid
- Status changed from assigned to closed
Thanks Jan. I close the ticket.
Hi,
Could you please explain why you need the updated parent bathymetry ? Input restart matches the original (i.e. not updated domain) so that I don't understand why you advise this. Maybe I missed something ?
Thanks for your help,
Jerome