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

Error inn running 3d SP CAM - help required

abhisheklodh

abhisheklodh

Dr. Abhishek Lodh
New Member
Hi all,
I am successfully able to execute the SP-CAM in 2D mode within the CESMv2.2 model. The CAM super-parameterized double moment m2005 SAM micro physics is enabled to run the model (COMPSET used is: FSPCAMM i.e 2000_CAM%SPCAMM_CLM50%SP_CICE%PRES_DOCN%DOM_RTM_SGLC_SWAV)

Now with the same model settings but enabling 3D configuration I am trying to run the 3D SP-CAM (super parameterized) model. The "env_build.xml" file is modified, to ---- "-spcam_nx 32 -spcam_ny 32 -spcam_dx 4000 -spcam_dt 20 -phys spcam_m2005", to introduce the dimensions both in the NS direction. But, I am getting the following error.

[0] calcsize j,iq,jac, lsfrm,lstoo 2 1 2 13 17
[0] calcsize j,iq,jac, lsfrm,lstoo 2 2 1 7 14
[0] calcsize j,iq,jac, lsfrm,lstoo 2 2 2 7 14
[0] calcsize j,iq,jac, lsfrm,lstoo 2 3 1 9 15
[0] calcsize j,iq,jac, lsfrm,lstoo 2 3 2 9 15
[0] calcsize j,iq,jac, lsfrm,lstoo 2 4 1 12 16
[0] calcsize j,iq,jac, lsfrm,lstoo 2 4 2 12 16

===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= RANK 0 PID 404746 RUNNING AT abhishekl
= KILLED BY SIGNAL: 9 (Killed)
===================================================================================

===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES

This error seems to be due to memory taken during the model run. I will be thankful if anyone can let me know how to get rid of this error ?

Thanks in advance.
 
C

cacraig

Cheryl Craig
CSEG and Liaisons
Staff member
abhisheklodh said:
Hi all,
I am successfully able to execute the SP-CAM in 2D mode within the CESMv2.2 model. The CAM super-parameterized double moment m2005 SAM micro physics is enabled to run the model (COMPSET used is: FSPCAMM i.e 2000_CAM%SPCAMM_CLM50%SP_CICE%PRES_DOCN%DOM_RTM_SGLC_SWAV)

Now with the same model settings but enabling 3D configuration I am trying to run the 3D SP-CAM (super parameterized) model. The "env_build.xml" file is modified, to ---- "-spcam_nx 32 -spcam_ny 32 -spcam_dx 4000 -spcam_dt 20 -phys spcam_m2005", to introduce the dimensions both in the NS direction. But, I am getting the following error.

[0] calcsize j,iq,jac, lsfrm,lstoo 2 1 2 13 17
[0] calcsize j,iq,jac, lsfrm,lstoo 2 2 1 7 14
[0] calcsize j,iq,jac, lsfrm,lstoo 2 2 2 7 14
[0] calcsize j,iq,jac, lsfrm,lstoo 2 3 1 9 15
[0] calcsize j,iq,jac, lsfrm,lstoo 2 3 2 9 15
[0] calcsize j,iq,jac, lsfrm,lstoo 2 4 1 12 16
[0] calcsize j,iq,jac, lsfrm,lstoo 2 4 2 12 16

===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= RANK 0 PID 404746 RUNNING AT abhishekl
= KILLED BY SIGNAL: 9 (Killed)
===================================================================================

===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES

This error seems to be due to memory taken during the model run. I will be thankful if anyone can let me know how to get rid of this error ?

Thanks in advance.
Click to expand...

Unfortunately, we CAM developers never ran with anything other than spcam_ny=1 (based on what the original SPCAM developers gave us a settings). While we tried to set the hooks up for using spcam_ny at settings other than 1, it was never tested as far as I remember.
 
abhisheklodh

abhisheklodh

Dr. Abhishek Lodh
New Member
Hi Cheryl,

Thanks for your reply. Even after increasing the spatial and temporal resolution

"-chem trop_mam3 -spcam_nx 32 -spcam_ny 32 -spcam_dx 16000 -spcam_dt 80 -phys spcam_m2005 ""

the same error is coming.

[0] MCT::m_Router::initp_: RGSMap indices not increasing...Will correct
[0] MCT::m_Router::initp_: RGSMap indices not increasing...Will correct
[0] MCT::m_Router::initp_: GSMap indices not increasing...Will correct
[0] calcsize j,iq,jac, lsfrm,lstoo 1 1 1 17 13
[0] calcsize j,iq,jac, lsfrm,lstoo 1 1 2 17 13
[0] calcsize j,iq,jac, lsfrm,lstoo 1 2 1 14 7
[0] calcsize j,iq,jac, lsfrm,lstoo 1 2 2 14 7
[0] calcsize j,iq,jac, lsfrm,lstoo 1 3 1 15 9
[0] calcsize j,iq,jac, lsfrm,lstoo 1 3 2 15 9
[0] calcsize j,iq,jac, lsfrm,lstoo 1 4 1 16 12
[0] calcsize j,iq,jac, lsfrm,lstoo 1 4 2 16 12
[0] calcsize j,iq,jac, lsfrm,lstoo 2 1 1 13 17
[0] calcsize j,iq,jac, lsfrm,lstoo 2 1 2 13 17
[0] calcsize j,iq,jac, lsfrm,lstoo 2 2 1 7 14
[0] calcsize j,iq,jac, lsfrm,lstoo 2 2 2 7 14
[0] calcsize j,iq,jac, lsfrm,lstoo 2 3 1 9 15
[0] calcsize j,iq,jac, lsfrm,lstoo 2 3 2 9 15
[0] calcsize j,iq,jac, lsfrm,lstoo 2 4 1 12 16
[0] calcsize j,iq,jac, lsfrm,lstoo 2 4 2 12 16

===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= RANK 0 PID 491040 RUNNING AT abhishekl
= KILLED BY SIGNAL: 9 (Killed)

Any clue in this regard will be helpful.
 
C

cacraig

Cheryl Craig
CSEG and Liaisons
Staff member
The MCT messages you are reporting are normal in any CAM run. I did confirm that the "indices not increasing" messages appear in a run which runs normally. I believe the calcsize messages also appear in runs which are working fine, but since we no longer support MCT, this response is based off of memory.

Have you looked in all of the *log* files to see if you can find an error. Note that sometimes the error may appear a little bit higher than the absolute end of the file.

Try setting "./xmlchange DEBUG=TRUE." This may give you a traceback which will indicate where the actual error is occurring.

Again, note that you could be running into a coding bug because as I indicated, I don't believe we ever tested with anything other than spcam_ny=1.

As for the SPCAM settings you will need to refer to published literature or contact the spcam developers directly for help in that area.
 
abhisheklodh

abhisheklodh

Dr. Abhishek Lodh
New Member
cacraig said:
The MCT messages you are reporting are normal in any CAM run. I did confirm that the "indices not increasing" messages appear in a run which runs normally. I believe the calcsize messages also appear in runs which are working fine, but since we no longer support MCT, this response is based off of memory.

Have you looked in all of the *log* files to see if you can find an error. Note that sometimes the error may appear a little bit higher than the absolute end of the file.

Try setting "./xmlchange DEBUG=TRUE." This may give you a traceback which will indicate where the actual error is occurring.

Again, note that you could be running into a coding bug because as I indicated, I don't believe we ever tested with anything other than spcam_ny=1.

As for the SPCAM settings you will need to refer to published literature or contact the spcam developers directly for help in that area.
Click to expand...
Thanks Cheryl for your help. Now, I am able to solve my problem of running the 3D SPCAM by reducing the nx and ny.
 
You must log in or register to reply here.
Top