Adding datetime in rpointer file with backward compatibility #486
Conversation
nmizukami
added
enhancement
route/build/src/io_rpointfile.f90
Outdated
|
|
||
| ierr=0; message='io_rpfile/' | ||
|
|
||
| if (present(curDatetime)) then | ||
| sec_in_day = curDatetime%hour()*60*60+curDatetime%minute()*60+nint(curDatetime%sec()) |
There was a problem hiding this comment.
Change 60*60 to nint(secphour) and 60 to nint(secpmin) in public_vars
route/build/cpl/RtmMod.F90
Outdated
| locfn = './'// trim(rpntfil)//trim(inst_suffix) | ||
| nio = getavu() ! get available unit number | ||
|
|
||
| ! construct rpoint file name with datetime - simDatetime has three datetime at previous(0), current(1) and next(2) time stamp |
There was a problem hiding this comment.
change rpoint to rpointer
| !-------------------------------------------------------- | ||
|
|
||
| if (masterproc) then | ||
| write(iulog,*) 'Reading restart pointer file....' | ||
| endif | ||
|
|
||
| nio = getavu() | ||
| locfn = './'// trim(rpntfil)//trim(inst_suffix) | ||
| nio = getavu() ! get available unit number |
There was a problem hiding this comment.
Note, that new FORTRAN constructs allow you to NOT need getavu() anymore. There's a way to open a file with an available unit.
This would be a good modernization effort to do. But, not completely required.
There was a problem hiding this comment.
I think the only thing in RtmFileUtils that is maybe useful is opnfil, but the use of getavu and relavu could be removed and handled within opnfil.
There was a problem hiding this comment.
Thanks for suggestions on ascii file handling (#490). I will clean this up with another PR. This RtmFileUtils and ascii_utils could be merged and several routines (getavu and relavu, getSpareUnit) can be removed.
Adding string of datetime (
yyyy-mm-dd-sssssformat) to the end ofrpointer.roffor only cesm-coupling mode. This is the backward compatibility. standalone does not use this for now.Resolve #484