[MITgcm-support] mnc pickups

[jeff polton]

Hi.
Firstly, yes I did rerun genmake2. I deleted all the old files in my 
build directory just to make sure. This led to 3 new files appearing in 
pkg/mnc at the time of compilation:
MNC_CW_READWRITE_RS.F
MNC_CW_READWRITE_RL.F
MNC_CW_READWRITE_I.F
I guess these came from the similarly named template file.

Below are the files that live in code/
and the files that live in input/

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: MNC_SIZE.h
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20050919/22b5d1ce/attachment.h>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: SIZE.h
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20050919/22b5d1ce/attachment-0001.h>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: packages.conf
Type: application/octet-stream
Size: 160 bytes
Desc: not available
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20050919/22b5d1ce/attachment.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: DIAGNOSTICS_SIZE.h
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20050919/22b5d1ce/attachment-0002.h>
-------------- next part --------------



-------------- next part --------------
A non-text attachment was scrubbed...
Name: data.diagnostics
Type: application/octet-stream
Size: 2051 bytes
Desc: not available
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20050919/22b5d1ce/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: data.pkg
Type: application/octet-stream
Size: 65 bytes
Desc: not available
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20050919/22b5d1ce/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: data.mnc
Type: application/octet-stream
Size: 1147 bytes
Desc: not available
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20050919/22b5d1ce/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: data
Type: application/octet-stream
Size: 2164 bytes
Desc: not available
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20050919/22b5d1ce/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gendata.m
Type: application/octet-stream
Size: 1730 bytes
Desc: not available
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20050919/22b5d1ce/attachment-0005.obj>
-------------- next part --------------


I hope that this helps you reproduce the error.

Thanks,

Jeff


On Sep 19, 2005, at 2:04 PM, Ed Hill wrote:

>
> Hi Jeff,
>
> I've added comments in-line below:
>
> On Mon, 2005-09-19 at 13:06 -0700, jeff polton wrote:
>> In summary I tried the new mnc files on 3 similar runs which stopped
>> for 2 different reasons after a number of hours running (one of which 
>> I
>> don't understand). The diagnostics output files however all have the
>> same time stamp as the error files.
>> I'll decribe what happened.
>> "cvs -n update" told me I needed 2 files from pkg/mnc so I got them
>> $cvs update mnc_cw_readwrite.template
>> $cvs update mnc_cw_cvars.F
>
> This is good, but please check that you re-ran genmake2 when you
> re-built things since the *.template files need to be "expanded" and
> this is done by genmake2.  I think you did the right thing, but I just
> want to be clear that the safest thing is to completely re-build your
> executable.
>
>
>> I restarted the runs from pickups, changing only the chkptFreq to
>> something nonzero and nIter0 and nTimeSteps.
>>
>> The 1st to fail failed with the following error
>>> forrtl: severe (66): output statement overflows record, unit -5, file
>>> Internal Formatted Write
>>> Image              PC                  Routine            Line
>>> Source
>>> mitgcmuv           0x4000000000408ab0  Unknown               Unknown
>>> Unknown
>
> ...snip...
>
>>> Unknown
>>> libc.so.6.1        0x20000000003b2970  Unknown               Unknown
>>> Unknown
>> and STDERR.0000:
>>> (PID.TID 0000.0001) *** ERROR *** NetCDF ERROR: Numeric conversion 
>>> not
>>> representable
>
> The "internal formatted write" is a character string formatting issue.
> And the "numeric conversion not representable" is an error reported by
> the netCDF library.  It would be really helpful if I could somehow
> reproduce your errors.  Any chance that I could have a set of your 
> input
> files that triggers the above error messages?
>
>
>> I had previously encountered this error and resolved 
>> ("circumnatigated"
>> might be more appropriate) by reducing the number of diagnostics in
>> data.diagnotics. Clearly that was not the real problem as that error
>> has arisen again.
>
> Again, its going to be hard to find the problem if I can't reproduce 
> the
> error(s).  Please help me by giving me a set of input files that causes
> the above problem(s).
>
>
>> The other 2 runs both died later because I filled my 500GB limit! Doh!
>> Though interestingly both made it further than the above run and both
>> completing a successful pickup dump. The above failed run completed
>> only a checkpoint dump.
>
> Well, I'm glad that you're making some progress!  ;-)
>
> 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-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support
>