[Mitgcm-support] Re: I try to follow the procedure

mitgcm-support at dev.mitgcm.org mitgcm-support at dev.mitgcm.org
Wed Jul 9 15:45:09 EDT 2003


If it has enough coverage to really do this and
it really works then you're right of course.
JMC - will it fix any of the issues of this sort 
      that have actually arisen in the past 6 months?
      

Chris
Patrick Heimbach wrote:
> 
> Clear answer:
> So that it will be more difficult for specific people to say
> "It doesn't work!" while nobody knows, what exactly it is
> that doesn't work (e.g. a screwed-up configuration).
> 
> I go with Jean-Michel.
> 
> Chris Hill wrote:
> >
> > Why do we need check_config in release1?
> > Can't it be part of release2?
> > I know I am a trouble maker!
> >
> > Chris
> >
> > -----Original Message-----
> > From: Jean-Michel Campin [mailto:jmc at gulf.mit.edu]
> > Sent: Thursday, January 31, 2002 9:31 AM
> > To: support at mitgcm.org
> > Subject: I try to follow the procedure
> >
> > Hello,
> >
> > I am going to check-in a new routine (config_check) that has to be in
> > release1-beta2.
> > will create tag chkpt44a_pre in few minutes, then check-in
> > a non up-to-date version of this routine, create tag chkpt44a_post,
> > and update the config_check routine.
> > The reason : since OBC+NLFS will not be in release1-beta2, I need
> > a different version of config_check in main-branch and release branch.
> >
> > estimated time : < 30 mn.
> >
> > See you.
> >
> > Jean-Michel
> 
> --
> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> 
> Patrick Heimbach ........................ FON: +1/617/253-5259
> Massachusetts Institute of Technology ... FAX: +1/617/253-4464
> EAPS, Room 54-1518 ...........................................
> 77 Massachusetts Avenue .............. mailto:heimbach at mit.edu
> Cambridge MA 02139, U.S.A. ..... http://www.mit.edu/~heimbach/



More information about the MITgcm-support mailing list