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

Is this CAM running in a standalone mode or not?

H

huangdzh@foxmail_com

New Member
Dear all,
Is this CAM running in a standalone mode or not?
I run a parallel CAM on my HP PC successfully, but, I'm not sure that it is running as a part of CCSM or running in a standalone mode. And I noted that my configure line via a cice-configure in the process. The command line and some output were added bellow. Could anybody can give me a hand? Any help will be greatly appreciated.
Thanks in advance!
Leo

!>-----------------------------------------------------<

Several namelists build by build-namelist utility:
atm_in, drv_flds_in, drv_in, ice_in, lnd_in, ocn_in.

!>-----------------------------------------------------<

%$CAMROOT/models/atm/cam/bld/configure -test -dyn fv -hgrid 1.9x2.5 -ntasks 4 -nosmp

Issuing command to the CICE configure utility:
/home/leo/models/CCSM4/ccsm4-2/models/ice/cice/bld/configure -hgrid 1.9x2.5 -cice_mode prescribed -ntr_aero 0 -ntr_pond 1 -ntr_iage 0 -ntasks 4 -nthreads 1 -cache config_cache_cice.xml -cachedir /home/leo/models/CCSM4/ccsm4-1/fv1.9x2.5_leo001
configure done.
creating /home/leo/models/CCSM4/ccsm4-2/fv1.9x2.5_leo001/Filepath
creating /home/leo/models/CCSM4/ccsm4-2/fv1.9x2.5_leo001/misc.h
creating /home/leo/models/CCSM4/ccsm4-2/fv1.9x2.5_leo001/preproc.h
creating /home/leo/models/CCSM4/ccsm4-2/fv1.9x2.5_leo001/Makefile
creating /home/leo/models/CCSM4/ccsm4-2/fv1.9x2.5_leo001/config_cache.xml
Looking for a valid GNU make... using gmake
Test linking to NetCDF library... ok
Test linking to MPI library... ok
configure done.

%gmake -j4 >&! makeout.txt

%$CAMROOT/models/atm/cam/bld/build-namelist -test -case fv1.9x2.5_leo001 -runtype startup -namelist "&camexp stop_option='ndays' stop_n=61 fincl2='T850:A','T300:A','V200:A','V850:A','U200:A','U850:A','Z500:A' /" >&! namelistout.txt

%mpirun -np 4 $blddir/cam >&! runoutput.txt

!>-----------------------------------------------------
 
H

huangdzh@foxmail_com

New Member
************ PROCESS 0 ( 0) ************

$Id: gptl.c,v 1.97 2008/09/24 16:03:03 rosinski Exp $
Underlying timing routine was MPI_Wtime.
Per-call utr overhead est: 1.06e-06 sec.
If overhead stats are printed, roughly half the estimated number is
embedded in the wallclock stats for each timer

If a '% of' field is present, it is w.r.t. the first timer for thread 0.
If a 'e6 per sec' field is present, it is in millions of PAPI counts per sec.

A '*' in column 1 below means the timer had multiple parents, though the
values printed are for all calls. Further down the listing is more detailed
information about multiple parents. Look for 'Multiple parent info'

Stats for thread 0:
(omit)
Multiple parent info (if any) for thread 0:
Columns are count and name for the listed child
Rows are each parent, with their common child being the last entry, which is indented
Count next to each parent is the number of times it called the child
Count next to child is total number of times it was called by the listed parents

2928 cice_prep_radiation
2928 cice_radiation
5856 Shortwave

2928 cice_therm1
2928 TimeLoop
5856 Column

84 clm_driver1
408 readMonthlyVeg
554 clm_driver_io_htapes
900 clm_driver_io_wrest
1946 ncd_lgs1d_total

64 wshist
1 cam_write_restart
65 dump_field

800 get_decomp
51 cam_write_restart
851 get_phys_decomp

2929 chk_en_gmean
488 fv_out
3417 gmean_fixed_repro

3417 gmean_fixed_repro
488 gmeanxy_repro_sum
244 fv_out_repro_sum
112 physpkg_st1
4261 repro_sum_int

632664 stratiform_tend
632664 stratiform_microphys
1.3e+06 cldfrc

2 History
3 Total
5 ReadWrite

1387 ncd_lgs1d_wgath
220 clm_driver_io_wrest
1607 gather_1darray_real_total

67 ncd_lgs1d_wgath
220 clm_driver_io_wrest
287 gather_1darray_int_total


thread 0 had some hash collisions:
hashtable[0][286] had 2 entries: d_p_coupling DRIVER_RESTART
hashtable[0][362] had 2 entries: energy_fixer DRIVER_ATMPOST
hashtable[0][1717] had 2 entries: driver_ocnprep_atm2ocn small_ts_init
hashtable[0][2199] had 2 entries: cice_pice_readLBUB_filemgt hylake
hashtable[0][2906] had 2 entries: bgplake driver_atmprep_ocn2atm2
hashtable[0][3094] had 2 entries: drvinit dyn_run
hashtable[0][3375] had 2 entries: driver_c2i_infoexch aero_optics_sw
Total collisions thread 0 = 14

************ PROCESS 1 ( 1) ************
(omit)

************ PROCESS 2 ( 2) ************
(omit)
Multiple parent info (if any) for thread 0:
Columns are count and name for the listed child
Rows are each parent, with their common child being the last entry, which is indented
Count next to each parent is the number of times it called the child
Count next to child is total number of times it was called by the listed parents

2928 cice_prep_radiation
2928 cice_radiation
5856 Shortwave

2928 cice_therm1
2928 TimeLoop
5856 Column

84 clm_driver1
408 readMonthlyVeg
554 clm_driver_io_htapes
900 clm_driver_io_wrest
1946 ncd_lgs1d_total

64 wshist
1 cam_write_restart
65 dump_field

800 get_decomp
51 cam_write_restart
851 get_phys_decomp

2929 chk_en_gmean
488 fv_out
3417 gmean_fixed_repro

3417 gmean_fixed_repro
488 gmeanxy_repro_sum
244 fv_out_repro_sum
112 physpkg_st1
4261 repro_sum_int

632664 stratiform_tend
632664 stratiform_microphys
1.3e+06 cldfrc

2 History
3 Total
5 ReadWrite

1387 ncd_lgs1d_wgath
220 clm_driver_io_wrest
1607 gather_1darray_real_total

67 ncd_lgs1d_wgath
220 clm_driver_io_wrest
287 gather_1darray_int_total


thread 0 had some hash collisions:
hashtable[0][286] had 2 entries: d_p_coupling DRIVER_RESTART
hashtable[0][362] had 2 entries: energy_fixer DRIVER_ATMPOST
hashtable[0][1717] had 2 entries: driver_ocnprep_atm2ocn small_ts_init
hashtable[0][2199] had 2 entries: cice_pice_readLBUB_filemgt hylake
hashtable[0][2906] had 2 entries: bgplake driver_atmprep_ocn2atm2
hashtable[0][3094] had 2 entries: drvinit dyn_run
hashtable[0][3375] had 2 entries: driver_c2i_infoexch aero_optics_sw
Total collisions thread 0 = 14



************ PROCESS 3 ( 3) ************
(omit)
 
E

eaton

CSEG and Liaisons
When you execute CAM's configure and build-namelist commands the way you have done, you're running CAM standalone. It is possible to run the CESM in a configuration with the identical components used in the standalone CAM configuration by running from the CESM scripts and specifying one of the "F" compsets. So think of standalone CAM as just a special configuration of the CESM; one that uses the CAM atmosphere, the CLM land component, the docn data ocean component, and a thermodynamic only mode of the CICE sea ice component. Another restriction of standalone CAM is that all these component are assumed to be using the same grid. It is possible using the CESM scripts to run the atmosphere, land, and ocn/ice components on different grids.
 
You must log in or register to reply here.
Top