[MITgcm-support] build errors for llc_1080
Dimitris Menemenlis
dmenemenlis at gmail.com
Tue Nov 29 12:07:26 EST 2016
Hi Ryan, often when I have encountered similar error situation,
it was caused by a file that was incorrectly transferred and was either
incomplete or contained some nans.
Is it possible that your atmospheric fields were not transferred correctly?
Maybe a checksum of fields on pleiades vs those that you are using would help?
The other possibility is a configuration issue, especially with pkg/seaice
Some of these large values of fluxes that Jody points out below could be from melting or
freezing of sea ice on first time step. One quick way to exclude a pkg/seaice
problem is to temporarily set useSeaice=.FALSE. and see if you get past the first time step.
I have many more suggestions, but please try the first two above first,
before I bombard you — and if all else fails, I will try to reproduce your problem locally.
Dimitris Menemenlis
> On Nov 29, 2016, at 8:52 AM, Jody Klymak <jklymak at uvic.ca> wrote:
>
> Hi Ryan,
>
>> On 29 Nov 2016, at 8:15 AM, Ryan Abernathey <ryan.abernathey at gmail.com <mailto:ryan.abernathey at gmail.com>> wrote:
>>
>> (PID.TID 0000.0001) %MON forcing_qnet_max = 7.3720703674861E+04
>> (PID.TID 0000.0001) %MON forcing_qnet_min = -9.7387390132223E+05
>> (PID.TID 0000.0001) %MON forcing_qnet_mean = 2.4732599348323E+03
>> (PID.TID 0000.0001) %MON forcing_qnet_sd = 1.0522667085097E+04
>
>
> I’m sure someone more expert on forcing the model will step in, but quickly, these seem two to three orders of magnitude off, aren’t they? i.e. mW/m^2 instead of W/m^2? Not sure how they are specified (deltaT? or just as heat fluxes), or if maybe mW/m^2 are the right units, but…
>
> Cheers, Jody
>
> --
> Jody Klymak
> http://web.uvic.ca/~jklymak/ <http://web.uvic.ca/~jklymak/>
>
>
>
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20161129/584a2c47/attachment.htm>
More information about the MITgcm-support
mailing list