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

[Jonny Williams]

Thanks Dimitris

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?

Thanks!

Jonny


On 12 May 2014 15:32, Menemenlis, Dimitris (329D) <
Dimitris.Menemenlis at jpl.nasa.gov> wrote:

>  There is also a CPP_EEOPTIONS.h flag that can be used to write
> out a single STDOUT and STDERR file:
>
>  C--   Flag defined for eeboot_minimal.F, eeset_parms.F,
> C     and open_copy_data_file.F to write STDOUT, STDERR,
> C     and scratch files from process 0 only.
> #define SINGLE_DISK_IO
>
>   On May 12, 2014, at 4:58 AM, Jonny Williams <
> Jonny.Williams at bristol.ac.uk> wrote:
>
>  Hi there
>
>  I am trying to reduce the size of the output from my model because I am
> running on a very large number of processors and all the STDOUT* files (for
> example) are taking up too much space.
>
>  I've followed the instructions on this MITgcm support page...
>
>  http://mitgcm.org/pipermail/mitgcm-support/2009-April/006013.html
>
>  ... but I am still getting a STDOUT file for every processor (>1000)
> which is killing my disk space allowance! Is there something that I've
> missed? I thought that running with *useSingleCpuIO=.TRUE.* should mean
> that I only get 1 STDOUT file? I've attached my *data* file in case
> anyone has any ideas as to what is going wrong?!
>
>  Many thanks for your help.
>
>  Jonny
>
>
>
> _______________________________________________
> 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/ff4592de/attachment.htm>