Problems with a leap-year (1996)

[lalvarez]

Hello to All

I´m trying to run the model from july 1996 to march 31 1997, but there is some trouble with this 1996 leap-year, the model blows up on the dec 31(the 366 day} and cannot go through to 1997

Is there any how to solve this situation?

I saw a few weeks ago that Dr. Arango post a tracktickt about this, can anyone give a hint please

Have a nice monday

[m.hadfield]

See this thread

viewtopic.php?f=19&t=4521&p=17727&hilit=y2k#p17727

and update your ROMS

[lalvarez]

Hello M.Hadfield

That' s what i was looking for

Thanks a lot

[lalvarez]

Hello M.Hadfield

I have some questions about the ROMS updating

Would there be any trouble with things I have done or perhaps with the configuration I already have?

Thanks in advance

[kate]

On the updating, it should keep your stuff and just update the files that changed. If there's a conflict, it will let you know. You can always save a copy of everything before the update.

So, for managing code versions, svn is OK if you have write permission on the server. There are newer tools which would allow you to keep your versions as well as update from the svn server. I've been using git and "git svn" for a long time now to keep track of my codes, but there are other choices now too. I'm not going back to svn, even with write permission on the server.

[m.hadfield]

+1 to what Kate said. Keeping your local modifications in a Subversion working copy is skating on thin ice. The modifications have no back-up and no history.

Personally I use Mercurial with the hgsubversion extension, but Git is more widely supported and Kate has written instructions for using it with the ROMS Subversion repository. Either way, you should manage your code with a distributed version control system.