forcing to include data to timings folder

[aketh_tm@gmail_com]

Hi,I have been running CESM1.2.2 on my local cluster for the past few weeks. I was suggeested by one of the members that adding  call t_startf('unique name').//interested region.call t_stopf('unique name') helps for timing region of interest.However I added it to the radae file for radabs routine, but unable to see any related/relavent data.I tried changing Drv_in profile option of depth to 3 and profile barrier set to true in the run folder, but it doesn't seem to help.Below are the attachments of Radae file and timings folder.Any suggestions? 

 

[santos]

Are you sure that the ccsm_timing_stats file you sent was made *after* you set profile_detail_limit = 3? There should be much more output if profile_detail_limit is >= 1.What CAM physics were you using? I think that radae is only used in CAM3 and CAM4, not CAM5.

 

[aketh_tm@gmail_com]

I ran another function (barotropic) to check if the timing data does show up.This was done with DEBUG flag as FALSE(I hope its irrelavent) and profile_detail_limit=3 (Which was done after the build in the RUNDIR folder). Interestingly it did show timing for Barotropic driver(see baro_driver in ccsm timings file) but not for barotropic init module.Thia time I am sure it was set to profile_detail_limit was set to 3.How do I resolve this issue?With respect to CAM3 or 4 or 5. How do I know which one is being used. I used the B compset with res f45g37. I think its cam4 as per the README.Below are the attachments.   

 

[santos]

I am confused. In your new drv_in, you have:profile_detail_limit = 0

 

[santos]

Oh, and if the compset is just "B", with nothing else, it is CAM4. You can check by looking in atm_in, at the value of "cam_physpkg".

 

[aketh_tm@gmail_com]

Hi,This seems to confuse me too.Everytime I set it to 3 , just before a build in the run directory, but it changes back to 0.Then I reset it to 3, just before job submission.It changes back to 0 after a run is complete. Is this possible?There was a drv_in in ./Buildconf/cplconf folder and ./Casedocs folder. I changed it in all these folders.Still it seems to revert.Also can you look into why baro_init was not included.I guess because if the function returned at some conditional statement without, encountering the call t_stopf(...) 

 

[aketh_tm@gmail_com]

Hi Santos sir,I checked again.I changed the profile_detail_limit=3 and performed ./def_prof.submit.and immediately checked run/drv_in folder.As expected there is some script rewriting the value.

 

[santos]

For CESM 1.0.6 and earlier, you have to edit "Buildconf/cpl.buildnml.csh" to change the namelist values. Any other namelist file you change will be overwritten.In later versions, you can add setting changes to "user_nl_cpl" in your case directory, which is a little easier, but in CESM 1.0, the coupler did not support this file.

 

[aketh_tm@gmail_com]

Hi Santos sir,That helped.Can you tell me what is that count option in the ccsm_stats?Is it the number times that block was entered? 

 

[santos]

Yes, the "count" is the number of times the block was executed during the run.