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 while running CAM in single column mode

arti-14

Arti Jadav
New Member
Hi.
I am running the CAM simulation in single column mode.

I am using the large scale forcings from the observations as the IOP data. For the large scale forcings data I created a netcdf file and read data into the variables. Is there some error with the IOP forcing netcdf file I have created?

The initial conditions file was generated by CAM run using the F2000climo compset, (following the instructions given in : 4. Atmospheric configurations (compsets) — camdoc documentation ). I have regridded the initial file succesfully and then using it for the SCAM run.

But during the SCAM run, the model is stopping with a segmentation fault.
I have attached the log files generated during the run for reference.

I have attached initial data and the IOP file I am using for the run.

Initial file : f.e20.FHIST.f09_f09.cesm2_1.001_v2.cam.i.regrid.Gaus_48x96.nc
IOP data forcing : mc3e.nc

I really appreciate help regarding it.
Thank you
 

Attachments

  • atm.log.200504-121748.txt
    26.4 KB · Views: 3
  • cesm.log.200504-121748.txt
    8.4 KB · Views: 5
  • cpl.log.200504-121748.txt
    42.2 KB · Views: 2

jet

Member
Hi Arti:

I took an initial look at that datasets and didn't see anything that jumped out. I'll try to duplicate the error and follow up on it. Can you tell me what version of CESM you are using?

jt
 

arti-14

Arti Jadav
New Member
Hi,
Thank you for your reply. I am using the CESM 2.1.2 version.

Best Regards,
Arti Jadav
 

jet

Member
Hi Arti:

I don't know why yet but the model is dying because your initial file has 2 timesteps. If you remove one of them it seems to work ok. You can use ncks to grab the first timestep.

module add nco
ncks -d time,0 /scratch/cluster/jet/f.e20.FHIST.f09_f09.cesm2_1.001_v2.cam.i.regrid.Gaus_48x96.nc new.nc

jt
 
Top