<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=big5">
<META content="BOX Webmail" name=GENERATOR>
</HEAD>
<BODY bgColor="#ffffff">
Thanks Rob and Wei-keng,<BR>It will be a good idea to make this check as a warming only. In most realistic applications (including Community Atmospheric Model, within CCSM development), it's almost impossible to have the same dimension for the same array variable within different processes. Usually, 1 or 2 shift. Cheers,<BR>
<HR>
Yu-heng Tseng<BR>Department of Atmospheric Sciences<BR>National Taiwan University<BR>No. 1, Sec. 4, Roosevelt Rd, Taipei 106, Taiwan<BR>tel: 886-2-33663918<BR>email: <A href="mailto:yhtseng@as.ntu.edu.tw" mce_href="mailto:yhtseng@as.ntu.edu.tw">yhtseng@as.ntu.edu.tw</A><BR><BR>
<DIV>----- Original Message ----- </DIV>
<DIV style="BACKGROUND: #e4e4e4"><B>From:</B> wkliao@ece.northwestern.edu</DIV>
<DIV><B>To:</B> wkliao@ece.northwestern.edu;parallel-netcdf<parallel-netcdf@lists.mcs.anl.gov></DIV>
<DIV><B>Sent:</B> 2009-06-16 03:00:01</DIV>
<DIV><B>Subject:</B> Re: Problem on Blue Gene/P</DIV>
<DIV><BR></DIV><!-- default_view_charset = big5 | EXT -->
<STYLE type=text/css>
<!--
BODY
{
font-size: 12pt;
color: #000000;
SCROLLBAR-FACE-COLOR: #eeeeee;
SCROLLBAR-ARROW-COLOR: #000000;
SCROLLBAR-TRACK-COLOR: #eeeeee;
SCROLLBAR-SHADOW-COLOR: white;
SCROLLBAR-3DLIGHT-COLOR: black;
}
-->
</STYLE>
<PRE>For example, when defining a new 2D array variable and the number of
processes is 2, P0 and P1.
The metadata (array dimensions, attributes, etc. in define mode) must
be the same between P0
and P1. If P0 uses 10x10 dimension values and P1 uses 10x11, then this
error message will
appear.
Wei-keng
On Jun 15, 2009, at 12:57 PM, Julien Bodart wrote:
> Thanks everybody for your help.
>
> I am afraid I don't get the point "your code is defining netcdf
> variables and attributes in
> a slightly different way on some MPI processes than others"...
> depending on what?
>
> Another test I could try is to unable the check made by ncpmi_enddef
> if it is possible, and see which kind of output file I get.
> I don't know if it is possible to do it easily without recompiling
> the library.
>
> I will try anyway the binary debugging.
>
>
> 2009/6/15 Rob Latham <ROBL@MCS.ANL.GOV>
> On Fri, Jun 12, 2009 at 02:19:33PM +0200, Julien Bodart wrote:
> > While it does not create any problems on small cases, bigger cases
> stop at
> > the ncmpi_enddef call on some files (randomly, even with
> synchronisation in
> > between), saying that there is a mismatch between dimensions.
> After many
> > check it does not seems that there is something wrong with the
> dimensions. I
> > have no idea of how to solve the problem. Did anyone had similar
> problem?
> > Thanks for your help.
>
> Hi Julien. Wei-keng is right: I know you've checked carefully, but
> some part of your code is defining netcdf variables and attributes in
> a slightly different way on some MPI processes than others.
>
> The main way people debug this is through binary search: comment out
> half of the define-mode portion; if the problem persists, comment out
> half of the remainder, else, try with the other half.
>
> You're not the first to encounter this problem. Maybe this could be a
> warning and not an error, and maybe we should just have the define
> mode view as rank 0 sees it be the one that wins if there's a
> discrepancy. I don't know how many people (if any) rely on the
> current behavior to find problems.
>
> ==rob
>
> --
> Rob Latham
> Mathematics and Computer Science Division
> Argonne National Lab, IL USA
>
</PRE><BR></BODY></HTML>