[MITgcm-support] ARCHER, cray, mpi and STDOUT

[Dan Jones]

Hi Dan,

Yes, I have experienced this same issue using cray Fortran compilers on
ARCHER. My STDOUT* files update infrequently and inconsistently. In my
worst case scenarios, STDOUT* doesn't update at all.

ARCHER support suggests that this could be a memory issue. That is, running
low on memory at runtime can cause weird output behavior. My solution has
typically been to reduce the amount of memory per core required by the
executable, e.g. by making the individual tiles smaller in SIZE.h. This
seems to work.

I also tend to use these compiler flags by uncommenting the last two lines
in the build options file "tools/build_options/linux_ia64_cray_archer":

FFLAGS='-h pic -dynamic'

CFLAGS='-h pic -dynamic'

I hope that helps!

Best,
Dan

--------------------------------------------------------------
Dr Dan Jones
Polar Oceans Team
British Antarctic Survey
--------------------------------------------------------------

Hi All
>
> I wonder if i can ask a question of MITgcm users on ARCHER, who are using
> cray fortran compilers?
>
> I am used to monitoring the STDOUT.* files to monitor the progress of my
> runs. I have recently begun using ARCHER, and until now was using intel
> compilers, and this worked just fine -- the STDOUT.* files update
> frequently.
>
> But I am now using cray compilers (via the optfile
> tools/build_options/linux_ia64_cray_archer) and am finding that STDOUT.*
> are not updated until the batch is completed. Has anyone else had similar
> issues? Are there any settings which can be changed, or any other files
> which receive standard output streams and are updated more frequently?
>
> Many thanks if anyone has an answer!!!!
>
> Best
> Dan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20190219/003e13dd/attachment.html>