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

output from history files

Hi,
I'm trying to cut down the output from the history files (all components active), but Im getting a variety of errors when I exclude certain fields.
Are certain output fields compulsory? Is there a list of the compulsory ones - I can';t seem to find mention of this in the user guides.
Thanks
Alex
 

njn01

Member
Alex,

For the ocean model, there are no required history fields. In order to change the default setup, you'll need to do the following:

1) copy $ccsm3/models/ocn/pop/input_template/${OCNRES}_tavg_contents into $ccsm3/scripts/$case/SourceMods/src.pop

Here $ccsm3 is your root directory, $case is your casename, and $OCNRES is
your ocn resolution, either gx3v5 or gx1v3

2) edit $ccsm3/scripts/$case/SourceMods/src.pop/${OCNRES}_tavg_contents to remove any ocean time-averaged history field that you do not want

Note that each of the 3D ocean history fields is either 25 or 40 times larger than each of the 2D fields.
 
Thanks for your reply.
Thats pretty much what Ive done. However for each combination of fields that I remove Im getting errors such as:
FATAL ERROR:
init_lat_aux_grid: When moc is true, WVEL and VVEL must also be selected in tavg_contents

or

FATAL ERROR: init_tavg: SU and SV must be defined if BSF is requested

So it looks like I've got various dependencies that restrict what I can or can't remove.

As a result its taking a large amount of time to come up with workable configurations of output.

Is there an easy way to find out what depends on what?
Thanks
Alex
 

njn01

Member
Alex,

Unfortunately, there is no one place where all of these dependencies are documented.

There are some warnings in subroutine POP-warnings in module initial.F, but there are also others spread throughout the code. The message you list in your post , for example, originates in the MOC computation module; depending on your research focus, you might want to turn this diagnostic off. (This would be done in your pop_in file, in namelist transports_nml. If you do this, you probably would also want to turn off the heat and salt transport diagnostics as well.)
 
Top