Skip to content
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

Inconsistent 'calendar' parameter used in model_configure templates #942

Closed
DusanJovic-NOAA opened this issue Dec 2, 2021 · 17 comments · Fixed by #1471
Closed

Inconsistent 'calendar' parameter used in model_configure templates #942

DusanJovic-NOAA opened this issue Dec 2, 2021 · 17 comments · Fixed by #1471

Comments

@DusanJovic-NOAA
Copy link
Collaborator

Various model_configure templates in tests/parm directory are setting calendar parameter to 'julian' while other are not (commented out):

esg_HAFS_v0_hwrf-model_configure.IN:calendar:                'julian'
model_configure_hafs_shared.IN:calendar:                'julian'
model_configure_hafs.IN:calendar:                'julian'
cpt.nml.IN:#       calendar = 'julian'
wam.nml.IN:#       calendar = 'julian'
model_configure_regional.IN:calendar:                'julian'
csawmg3shoc127.nml.IN:#       calendar = 'julian'
model_configure_fhout.IN:calendar:                'julian'
csawmgshoc.nml.IN:#       calendar = 'julian'
gsd_sar-model_configure.IN:calendar:                'julian'
stretched-nest-quilt-model_configure.IN:calendar:                'julian'
datm_cdeps_configure.IN:calendar:                'julian'
model_configure.IN:calendar:                'julian'

The default value is 'gregorian' (set in fv3_cap.F90) which is consistent with the default calendar set during ESMF initialization (see main program). Why are we using Julian calendar?

@junwang-noaa
Copy link
Collaborator

@DusanJovic-NOAA I think this is because the UFS is using GFS physics, in which the physics schemes such as radiation and land surface schemes are using Julian date. Unless we can use the 'Gregorian' date there, we have to use 'Julian' date for consistency.

@DusanJovic-NOAA
Copy link
Collaborator Author

@DusanJovic-NOAA I think this is because the UFS is using GFS physics, in which the physics schemes such as radiation and land surface schemes are using Julian date. Unless we can use the 'Gregorian' date there, we have to use 'Julian' date for consistency.

Julian day and Julian calendar are different things. If physics schemes are using Julian calendar (which I doubt) they are incorrect and should be using Gregorian calendar.

@DusanJovic-NOAA
Copy link
Collaborator Author

I think we should remove:
calendar: 'julian'
from all model_configure files a just set 'gregorian' as a default.

@climbfuji
Copy link
Collaborator

climbfuji commented Mar 18, 2022 via email

@junwang-noaa
Copy link
Collaborator

junwang-noaa commented Mar 18, 2022 via email

@climbfuji
Copy link
Collaborator

climbfuji commented Mar 18, 2022 via email

@yangfanglin
Copy link
Collaborator

Julian days are used in astronomical / radiation calculations in the current physics.

@junwang-noaa
Copy link
Collaborator

@climbfuji Sorry, what I mean is to remove the following line as Dusan suggested:

calendar: 'julian'

@climbfuji
Copy link
Collaborator

climbfuji commented Mar 23, 2022 via email

@DusanJovic-NOAA
Copy link
Collaborator Author

Are we ever going to use calendar that is not Gregorian? If not, then I suggest that we remove the code that reads this option from configure file. Also all history files have two attributes specifying calendar:

        double time(time) ;
                time:calendar = "JULIAN" ;
                time:calendar_type = "JULIAN" ;

which is redundant. One is enough. We can leave calendar and remove calendar_type, or simply remove both.

@junwang-noaa
Copy link
Collaborator

The PR was committed, the issue will be closed.

1 similar comment
@junwang-noaa
Copy link
Collaborator

The PR was committed, the issue will be closed.

@DusanJovic-NOAA
Copy link
Collaborator Author

This was not resolved in #1265

#1265 (comment)

@junwang-noaa
Copy link
Collaborator

Thanks, we may need to update the code to write out consistent calendar type in the restart files.

@DusanJovic-NOAA
Copy link
Collaborator Author

Consistent calendar type will be written out in the restart files. But because the restart files (coupler.res) in the baselines have 'incorrect' calendar type we need updated input data.

@junwang-noaa
Copy link
Collaborator

I see, maybe we need to update the input data directory then.

@DeniseWorthen
Copy link
Collaborator

Need update input data which is used for warm start tests (gdas, gdas-wave).

@DusanJovic-NOAA DusanJovic-NOAA mentioned this issue Oct 26, 2022
16 tasks
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 a pull request may close this issue.

5 participants