[MITgcm-devel] useMNC not in PARAMS.h ?
Patrick Heimbach
heimbach at MIT.EDU
Sun Oct 10 14:26:45 EDT 2004
Ed,
two things:
1.
Using ifc I don't get a seg. fault,
so this might be a good work around for people
wanting to use mnc.
2.
I think, unrelated to this issue is that, e.g. for
lab_sea, I no longer get monitor output:
grep dynstat output.txt
gives nothing, but
grep dynstat ../results/output.txt\
gives plenty of output.
-Patrick
> -----Original Message-----
> From: mitgcm-devel-bounces at mitgcm.org
> [mailto:mitgcm-devel-bounces at mitgcm.org] On Behalf Of Ed Hill
> Sent: Sunday, October 10, 2004 11:57 AM
> To: MITgcm-devel
> Subject: RE: [MITgcm-devel] useMNC not in PARAMS.h ?
>
>
> On Sun, 2004-10-10 at 10:12, Patrick Heimbach wrote:
> > Hi Ed,
> >
> > it's not clear to me how you got the clean testreport.
> > The seg. fault on lab_sea and dic_example persist
> > with an entirely fresh checkout as of now (9:36am).
> >
> > I've traced down the problem to S/R MNC_CW_RS_W_OFFSET
> > and within there to the loop over j2, ..., j7
> > but got lost then.
> >
> > -Patrick
> >
> > PS:
> > platform is sea.mit.edu
> > > uname -a
> > Linux sea 2.4.24-openmosix2 #1 Wed Jul 28 14:33:52 CEST 2004 i686
> > unknown
>
>
> Hi Patrick,
>
> Yes, this is a head-scratcher for me, too. I got the clean
> testreport
> runs on both my laptop and the black Athlon desktop in my
> office (both
> are running FC2) and thought I was done. Then this morning
> I saw the
> failed faulks tests and could reproduce the seg faults with
> gdb showing
> that it dies in mnc_cw_rl_w_offset().
>
> I'll keep at it and send news as soon as I can determine
> exactly whats
> b0rked and why. In the mean time, please either disable MNC or roll
> back to the MNC version in the last checkpoint if you need the MNC
> functionality.
>
> Ed
>
> --
> Edward H. Hill III, PhD
> office: MIT Dept. of EAPS; Rm 54-1424; 77 Massachusetts Ave.
> Cambridge, MA 02139-4307
> emails: eh3 at mit.edu ed at eh3.com
> URLs: http://web.mit.edu/eh3/ http://eh3.com/
> phone: 617-253-0098
> fax: 617-253-4464
>
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://dev.mitgcm.org/mailman/listinfo/mitgcm-devel
>
More information about the MITgcm-devel
mailing list