Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

what is the status of my run?

S

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.
 
S

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.
 
S

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.
 
T

thibaut_lurton@cnrs-orleans_fr

Member
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.
 
T

thibaut_lurton@cnrs-orleans_fr

Member
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.
 
T

thibaut_lurton@cnrs-orleans_fr

Member
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.
 
You must log in or register to reply here.
Top