Ask Your Question
0

Handling of tides on interannual run

asked 2022-05-31 15:13:14 +0100

this post is marked as community wiki

This post is a wiki. Anyone with karma >5 is welcome to improve it.

Hi there,

Just wondering what is best practice when using tides for an interannual run. In theory, the tides are included in croco_frc.nc, but if the tides are initialised at the beginning of a long interannual run, should the tides not be reinitialised once per year? If using bulk forcing, the interannual bash script isn't cycling through croco_frc.nc with a fresh tidal initialisation each month.

All comments would be appreciated.

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2022-06-01 14:29:22 +0100

MartinV gravatar image

Hi! I add the tides to the yearly bulk files and then use the same filename for the forcing file and the bulk file in the roms.in. I haven't tested this properly yet, but the model runs and at least the first impression looking at the results seems OK. Cheers!

edit flag offensive delete link more
0

answered 2022-05-31 15:44:50 +0100

This is a good point. Because of nodal corrections, the tides have to be recalculated at least once a year. I think the interannual bash script (run_croco_inter.bash) cycles through croco_frc.nc as well as croco_blk.nc, but there should be no problem adding the tides to the bulk forcing file. I think the idea originally was to save storage space by not adding the tides to all the monthly files, but I think we should rethink this strategy if the confusion is too much (and also recalculating the nodal corrections each month is not necessarily redundant)...

edit flag offensive delete link more
Login/Signup to Answer

Question Tools

1 follower

Stats

Asked: 2022-05-31 15:13:14 +0100

Seen: 124 times

Last updated: Jun 01