[MITgcm-devel] version of code used in r2_web_testing ?

[Jean-Michel Campin]

Hi Stephanie,

I don't know how precisely which version of the code is 
described in the (new) documentation.
It's definitively not the latest code (and it might require 
some work to use the latest code, since few things might be 
broken in the process of building the calling tree), but
it's far more recent than release-1 code.

Looks like it corresponds to July 18, 2006 code (was it our 
last doc-fest ?)
> cd /net/orwell/export/export-9/mitgcm-web/html/r2_web_testing/latest/code_reference
> ls -l callTree.html
> -rw-r--r-- 1 cnh gcmpack 36028 Jul 18  2006 callTree.html

Does anyone (Chris ?) has an idea how this part of the documentation
is built ?
(the reason why I move this discussion to the development list).

Thanks,
Jean-Michel

On Mon, Nov 19, 2007 at 04:32:21PM -0500, Stephanie Dutkiewicz wrote:
> 
> Jean-Michel -
> Not sure who to send this too - but the link Christopher
> mentions below is to some horribly outdated code -- and
> the link should probably be updated or the link broken.
> 
> Who would know how to do this?
> 
> steph
> 
> ---------- Forwarded message ----------
> Date: Mon, 19 Nov 2007 13:10:44 -0800
> From: Christopher L. Wolfe <clwolfe at ucsd.edu>
> To: Stephanie Dutkiewicz <stephd at ocean.mit.edu>
> Subject: Re: [MITgcm-support] Bug in rbcs_fields_load.F
> 
> Hi Stephanie,
> 
> The problem does seem to be fixed in the latest release.
> 
> I've been using checkpoint58q_post because I've made some modifications to 
> the vertical grid that get broken by newer updates. The code posted online 
> (http://mitgcm.org/r2_web_testing/latest/code_reference/callTree.html) 
> still contains the broken code and I had assumed that this listing 
> reflected the latest available code. However, if it still contains errors 
> fixed in version 1.5, it must be at least a year out of date. Does anybody 
> know which version of the code is posted at the above link?
> 
> Thanks,
> Christopher
> 
> Stephanie Dutkiewicz wrote:
> >
> >this problem seems to have been taken care of just
> >after checkpoint58q_post.. (see CVS revision 1.5
> >for this routine)
> >
> >Christopher - could you check and see if the
> >latest code takes care of these problems for you.
> >
> >thanks
> >steph
> >
> >On Fri, 16 Nov 2007, Christopher L. Wolfe wrote:
> >
> >>
> >>Hi modelers,
> >>
> >>There is a bug in rbcs_fields_load.F that causes parts of the ptracer 
> >>relaxation fields to be loaded into the tile overlap region instead of 
> >>the tile interior. This can cause obscure errors in the relaxation 
> >>pattern.
> >>
> >>Here is a diff of the incorrect, old file (<) compared to the new, 
> >>corrected file (>):
> >>
> >>162c162
> >><      &       'RS', Nr, rbcptracer0(1,1,1,1,1,iTracer), intime0, myThid )
> >>---
> >>>     &       'RS', Nr, rbcptracer0(1-Olx,1-Oly,1,1,1,iTracer), intime0, 
> >>>myThid )
> >>164c164
> >><      &       'RS', Nr, rbcptracer1(1,1,1,1,1,iTracer), intime1, myThid )
> >>---
> >>>     &       'RS', Nr, rbcptracer1(1-Olx,1-Oly,1,1,1,iTracer), intime1, 
> >>>myThid )
> >>182,183c182,183
> >><            _EXCH_XYZ_R4(rbcptracer0(1,1,1,1,1,iTracer),myThid)
> >><            _EXCH_XYZ_R4(rbcptracer1(1,1,1,1,1,iTracer),myThid)
> >>---
> >>>           _EXCH_XYZ_R4(rbcptracer0(1-Olx,1-Oly,1,1,1,iTracer),myThid)
> >>>           _EXCH_XYZ_R4(rbcptracer1(1-Olx,1-Oly,1,1,1,iTracer),myThid)
> >>
> >>This diff is against checkpoint58q_post, but I don't believe that this 
> >>file has changed in the recent updates.
> >>
> >>If anyone knows who maintains the RBCS package, please give them a heads 
> >>up for me.
> >>
> >>Christopher
> >>
> >>
> >>-----------------------------------------------------------
> >>Dr. Christopher L. Wolfe                   858-534-4560
> >>Physical Oceanography Research Division    OAR 357
> >>Scripps Institution of Oceanography, UCSD  clwolfe at ucsd.edu
> >>-----------------------------------------------------------
> >>
> >>
> >>
> >>
> >>_______________________________________________
> >>MITgcm-support mailing list
> >>MITgcm-support at mitgcm.org
> >>http://mitgcm.org/mailman/listinfo/mitgcm-support
>