[MITgcm-support] reducing the size of STDOUT files etc

Jonny Williams Jonny.Williams at bristol.ac.uk
Tue May 13 11:54:10 EDT 2014


That's great, thanks. Much appreciated as always!

Jonny


On 13 May 2014 16:07, Menemenlis, Dimitris (329D) <
Dimitris.Menemenlis at jpl.nasa.gov> wrote:

>  No.  You need to copy MITgcm/eesupp/inc/CPP_EEOPTIONS.h in your code or
> build directory then modify it,  But please do pay attention to warning:
>
>  C--   Flag defined for eeboot_minimal.F, eeset_parms.F,and
> open_copy_data_file.F
> C     to write STDOUT, STDERR, and scratch files from process 0 only.
> C WARNING: to use only when absolutely confident that the setup is working
> C     since any message (error/warning/print) from any proc <> 0 will be
> lost.
> #undef SINGLE_DISK_IO
>
>  On May 13, 2014, at 1:39 AM, Jonny Williams <Jonny.Williams at bristol.ac.uk>
> wrote:
>
>  In my code directory I don't have a CPP_EEOPTIONS.h file, but I do have
> a CPP_OPTIONS.h file. Can I put these lines in there instead?
>
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support
>
>


-- 
Dr Jonny Williams
School of Geographical Sciences
University of Bristol
University Road
BS8 1SS

+44 (0)117 3318352
jonny.williams at bristol.ac.uk
bit.ly/jonnywilliams
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20140513/60a1d3be/attachment.htm>


More information about the MITgcm-support mailing list