what is the status of my run?

santos

Member
If you find out more, let us know. From the output, all we can see is that there is an error in allocating memory inside OpenMPI some place. The most obvious possibility is some form of out-of-memory error, but it could be related to how OpenMPI is being configured or used.
 

santos

Member
If you find out more, let us know. From the output, all we can see is that there is an error in allocating memory inside OpenMPI some place. The most obvious possibility is some form of out-of-memory error, but it could be related to how OpenMPI is being configured or used.
 

santos

Member
If you find out more, let us know. From the output, all we can see is that there is an error in allocating memory inside OpenMPI some place. The most obvious possibility is some form of out-of-memory error, but it could be related to how OpenMPI is being configured or used.
 
Hello,Test number 6 (namely ERI.f19_g16.B1850CN) eventually passed ok, in approx. 4 hours.The solution to our problem turned out to be (oddly) to set DEBUG to TRUE in env_build.xml. In that configuration, the run progressed fine throughout. This reminds me of what was pointed out by another user there: http://bb.cgd.ucar.edu/cesm-122-segmentation-fault-when-running-model.Note that I also slightly fiddled with symbolic links pointing to CAM initial files and CLM restart files (they lacked the absolute paths), but I don't reckon this is related, as the progression in the run was really only dependent on our activating the DEBUG flag.Cheers,Thibaut.
 
Hello,Test number 6 (namely ERI.f19_g16.B1850CN) eventually passed ok, in approx. 4 hours.The solution to our problem turned out to be (oddly) to set DEBUG to TRUE in env_build.xml. In that configuration, the run progressed fine throughout. This reminds me of what was pointed out by another user there: http://bb.cgd.ucar.edu/cesm-122-segmentation-fault-when-running-model.Note that I also slightly fiddled with symbolic links pointing to CAM initial files and CLM restart files (they lacked the absolute paths), but I don't reckon this is related, as the progression in the run was really only dependent on our activating the DEBUG flag.Cheers,Thibaut.
 
Hello,Test number 6 (namely ERI.f19_g16.B1850CN) eventually passed ok, in approx. 4 hours.The solution to our problem turned out to be (oddly) to set DEBUG to TRUE in env_build.xml. In that configuration, the run progressed fine throughout. This reminds me of what was pointed out by another user there: http://bb.cgd.ucar.edu/cesm-122-segmentation-fault-when-running-model.Note that I also slightly fiddled with symbolic links pointing to CAM initial files and CLM restart files (they lacked the absolute paths), but I don't reckon this is related, as the progression in the run was really only dependent on our activating the DEBUG flag.Cheers,Thibaut.
 
Back
Top