You will be never be able to reproduce the results because bugs have been corrected in file u2dbc_im.F
since version 92. For example, see ticket 118
. We update the code to either correct bugs or add new development/improvements. So will always advice the Users to keep the codes up to date.
I highly recommend Users to check trac
when questions like the one raised here is asked. The trac web interface has a complete history of the changes of each file in ROMS repository. See Browse Source
menu bottom. You will notice that you enter into the ROMS repository directory tree (trunk
) and can browse any of the files. The web page for the file in question is here
. Then, in the upper right side you will see the link for Last Change
in red. If you click on this link you will be able to browse the entire history of changes to this file, one change at the time backwards. You can customize how to display the differences between revisions for this routine. I like to set the side by side
menu when displaying the differences. If you want to know why that change was done, click on the trac ticket under the Message
heading. Everything that you need to know about the evolution of ROMS is in the trac web site. I wonder how many user actually check this...
I see that you have hacked this routine because we never have the following directive:
Code: Select all
# if !defined SSH_TIDES && !defined UV_TIDES
As Kate mentioned, there is a lot of flexibility here. If only SSH_TIDES
is activated, the tidal forcing velocities are approximated by reduced physics. We actually do not recommend this in realistic applications. There has been a lot of discussions about this in the forum.
If you don't activate both SSH_TIDES
, why are you setting Flather boundary conditions like this? I will use the values in the open boundary structure arrays. Seems to me that you need instead any of the ****_M2REDUCED
options. Please, check this routine carefully and you will see what I am taking about. As John mentioned, there are countless options by manipulating the open boundary structure arrays BOUNDARY(ng)%
. We use this extensively in nesting.