[MITgcm-support] Re?Re: OBCS errors in OB location vs Mask

[Dustin Carroll]

Easy fix, thats great. A useful point from this discussion is that it is always a good idea to sanity check your *.bin input files before diving too deep into debugging your model params.

Best wishes,
Dustin

On Sep 16, 2014, at 5:47 AM, 刘成彦 <killy at nuist.edu.cn> wrote:

> 
> Dear all
> 
> First of all, thanks a lot for the help of Carroll, Michael and Jean-Michel.
> At last, I have overcome the problem with OBCS now.
> I have found the reason why it happens finally, and I want to share the experiences with the others.
> The MITGCM judge the OBC from the topography file which we make it by writebin.m in matlab.
> When I create it in matlab, the topography data is written by NY*NX in matlab style, but in MITGCM it
> is read by NX*NY style. So the logical longitude and latitude are disturbed in the model.
> When I want specify a solid boundary by &OBCS_PARM01 in data.obcs, it may should be an open boundary in topography file.
> Then the error happens.
> Again, thanks a lot for all of your help!
>  
> Cheers
> Yours sincerely Liu
> 
> 
> ----------------
> *********************************************
> Dr. Chengyan Liu
> Nanjing University of Information
> Science & Technology
> No.219, Ningliu Road, Nanjing, Jiangsu,
> China(Postcode: 210044)
> Phone: 18251854735
> E-Mail: killy at nuist.edu.cn
> 
> *********************************************
>  
> 
> _______________________________________________
> 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/20140916/105f437d/attachment.htm>