Opened 10 years ago
Closed 7 years ago
#1310 closed Enhancement (wontfix)
Allow specification of start hour
Reported by: | djlea | Owned by: | djlea |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | OCE | Version: | trunk |
Severity: | Keywords: | ||
Cc: |
Description
NEMO is hard-wired to always start a run at the start of the day (at 0z). I propose to extend the option of setting the start date to allow for the setting of a start hour via a namelist option.
Commit History (1)
Changeset | Author | Time | ChangeLog |
---|---|---|---|
4771 | djlea | 2014-09-17T17:52:23+02:00 | #1310: Create a new branch for allowing arbitrary start hours in NEMO rather than just 00:00. |
Attachments (1)
Change History (7)
Changed 10 years ago by djlea
comment:1 Changed 10 years ago by djlea
comment:2 Changed 10 years ago by djlea
comment:3 Changed 9 years ago by djlea
Code fixed to work with tides. There was a merge to the trunk (r5072) at revision 5075. So to look at the code differences it might be easier to look before and after the merge as follows:
comment:4 Changed 8 years ago by djlea
Update to the code to allow restartability for runs of less than one day. This was tested by modifying the AMM12 and ORCA2LIM3 SETTE tests. I've also made a small update to the SETTE test to retain the flexibility to run those tests with different run lengths. Updated diff (after the trunk merge)
comment:5 Changed 8 years ago by djlea
See review wiki at https://forge.ipsl.jussieu.fr/nemo/wiki/2014WP/ticket/1310
comment:6 Changed 7 years ago by clevy
- Resolution set to wontfix
- Status changed from new to closed
Suppressing tickets opened on the trunk since more than 2 years... cleaning started!
There is a related ticket at #1037 which can start NEMO at a different start time by changing the initial time step (I believe).
I've attached a version of daymod.F90 relative to NEMO 3.2 with the changes for our method which involves setting at start hour using nn_time0.