[MITgcm-support] output.txt empty

[Martin Losch]

Nicolas,

once you use MPI, the stuff that is normally written to the screen  
("standart out") and that you redirect into "output.txt" in your  
script is now written to a file called "STDOUT.????", where ???? is  
the ID number of your CPU (with 2 CPU you'd get STDOUT.0000 and  
STDOUT.0001). The error is written into STDERR.????, so you need to  
save these files. "output.txt" in your script will not contain  
anything except for stuff that mpirun writes to "standard out".

To improve the performance on your SX8, there is sx8 template optfile:
tools/build_options/SUPER-UX_SX-8_sxf90+mpi_awi
that may be a good starting point for the SX-compiler on an SX8. Some  
of the paths are specific to "our" machine at the AWI, but in general  
you should be able to use this file.

Martin


On 9 Jun 2008, at 10:50, Nicolas Grisouard wrote:

> Hi everyone,
>
> Quite some time ago, I switched from using the MITgcm with a single  
> processor to using the code with MPI. The machine (NEC-SX8) hasn't  
> changed. I just realized that since then, my output.txt files are  
> completely empty, meaning that they are indeed created, put not a  
> single line is written. Since I'm not the one who actually made the  
> changes so that we could use the code on multi procs, I don't  
> really know what part of the process went wrong. I attached an  
> example of script I use to launch a computation as well as my  
> Makefile (which may have some other errors as I'm in the process of  
> updating the code and still have some troubles... the reason why  
> I'd like to have an output.txt file). I don't know if any of these  
> are relevant, just tell me what else you would need.
>