[FLASH-USERS] Strange error from Driver

[Joshua Wall]

Klaus and Tomasz,

     It was indeed corrected by reducing the refinement. I had intended to
not push up to 30 levels on this particular machine, and may have just run
out of memory/procs. I am going to be using 30 levels soon however, and I'm
assuming that the umap subroutines can handle these levels of refinement
(when I have the requisite memory/procs)?

Thanks,

Josh

On Thu, Apr 23, 2015 at 12:53 PM Klaus Weide <klaus at flash.uchicago.edu>
wrote:

> On Thu, 23 Apr 2015, Joshua Wall wrote:
>
> > >     I'm receiving an odd error from FLASH and I'm not sure how to
> > > interpret it. Perhaps someone can enlighten me? Its:
> > >
> > >  **ERROR** - ierr from UMAPn is          421 , isg=           4
> > >  DRIVER_ABORT: ERROR - ierr from UMAPn is not 0
>
> The message indicates that the error occurs when interpolating data
> for block 4 (in some proc), and it is complainign about the X coordinate.
>
> As Tomek wrote, this may all be because of the high refinement level.
> Or...
>
> * Check your parfile, maybe xmin is the same as xmax? (forgotten /
>   duplicate sign ?)
>
> * Check that umap.F is compiled correctly, the compiler may somhow act
>   differently, this is about the only file that has a .F suffix instead
>   of .F90. In particular, check that flags promoting real to double
>   precision are there.
>
> Just some ideas.
>
> Klaus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://flash.rochester.edu/pipermail/flash-users/attachments/20150423/dd1ef4da/attachment.htm>