[MITgcm-support] Diagnostics Package

[Kirk Bryan]

Dear Jean-Michel and Patrick:
                                             I edited the data.diagnostics and the DIAGNOSTICS_SIZE.h files as you suggested and it took care of the problem!  Many thanks!  I am impressed. You seem to be always on the job. Next time
I won't ask for help just at the start of a weekend.
                                                                                 Kirk
Kirk Bryan
Sayre Hall, AOS Program
Princeton University
Princeton, NJ 08544
tel  609-258-3688
fax 609-258-2850

________________________________________
From: Jean-Michel Campin [jmc at ocean.mit.edu]
Sent: Sunday, April 27, 2014 11:19 AM
To: mitgcm-support at mitgcm.org
Subject: Re: [MITgcm-support] Diagnostics Package

Hi Kirk,

two comments:
1) regarding "DIAGNOSTICS_SIZE.h", it is not necessary to double so
 many dimensions, but just to make sure that
   numdiags is not smaller than 12*Nr (to enable the use of 12 3-D diagnostics)
 and similarly diagSt_size if you want to use some stats-diags.
2) From the STDOUT report you sent, it seems that the issue is
 coming from reading the namelist "diagnostics_list" in "data.diagnostics":
you should get:
(PID.TID 0000.0001)  Fields:    UVEL     VVEL     Um_dPHdx Um_Advec Um_Diss  Um_Ext   Vm_Ext   Vm_dPHdy Vm_Advec Vm_Diss
(PID.TID 0000.0001)  Fields:    AB_gU    AB_gV

instead of:
(PID.TID 0001.0001) Fields: UVEL VVEL Um_dPHdx Um_Advec Um_Diss Um_Ext   Vm_Ext Vm_dPHdy Vm_Advec
(PID.TID 0001.0001) Fields: Vm_Diss AB_gU AB_gV

and from there, a blank diagnostic name is found which causes the model to stop:
*** ERROR *** DIAGNOSTICS_SET_POINTERS:   is not a Diagnostic

I would recommend to try Patrick's suggestion, and, in case it does not work,
to report back the error you get.

Cheers,
Jean-Michel

On Sat, Apr 26, 2014 at 11:10:54PM -0400, Patrick Heimbach wrote:
>
> Kirk,
>
> not sure (and not easily reproduced), but you might give below syntax a try
> (although you may have tried it already following Dimitris’ suggestion):
>
>  fields(1:12,1) = 'UVEL    ','VVEL    ','Um_dPHdx',
>                   'Um_Advec','Um_Diss ','Um_Ext  ',
>                   'Vm_Ext  ','Vm_dPHdy','Vm_Advec',
>                   'Vm_Diss ','AB_gU   ','AB_gV   ‘,
>
> -Patrick
>
> On Apr 26, 2014, at 7:00 PM, Kirk Bryan <kbryan at Princeton.EDU> wrote:
>
> > Dear Dimitris:
> >                            Thanks very much for you help.  I tried editing the data.diagnostics file as you suggested.  It didn't seem to make a difference.   I will try to rewrite it some other ways.
> >                                                                          Kirk
> >
> > Kirk Bryan
> > Sayre Hall, AOS Program
> > Princeton University
> > Princeton, NJ 08544
> > tel  609-258-3688
> > fax 609-258-2850
> > From: Dimitris Menemenlis [dmenemenlis at gmail.com]
> > Sent: Friday, April 25, 2014 9:46 PM
> > To: MITgcm Support
> > Subject: Re: [MITgcm-support] Diagnostics Package
> >
> > Try adding two blank spaces after Vm_Ext
> > I am not 100% sure it is needed but in defining
> > "fields", I have always used 8 characters
> >
> >> < 'Um_Advec','Um_Diss','Um_Ext ',
> >> <   'Vm_Ext' ,'Vm_dPHdy','Vm_Advec',
> >
> > _______________________________________________
> > MITgcm-support mailing list
> > MITgcm-support at mitgcm.org
> > http://mitgcm.org/mailman/listinfo/mitgcm-support
>



> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support


_______________________________________________
MITgcm-support mailing list
MITgcm-support at mitgcm.org
http://mitgcm.org/mailman/listinfo/mitgcm-support