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

Controlling domain size in CLM run

subha_s2s

New Member
Dear Sir/Madam,

I have prepared the boundary conditions dataset using the tools mkgriddata and mksurfdata over my domain of choice. However, keeping these boundary files intact I want to do some experiments by using different smaller domain sizes i.e. by excluding few grid points in the E-W and N-S boundaries. I shall be grateful to receive suggestions/help regarding making necessary changes in the code to choose different domain sizes.

Thanks and regards,

Subhadeep.
 

slevis

Moderator
Staff member
Have you confirmed that your boundary conditions work? Then, I believe that you will need to change one of the files in order to accomplish what you're asking. The easiest might be to keep the same grid but replace land points with ocean points in the appropriate file. I have not tried this in a while, and it is not a supported method, so I do not remember off the top of my head which file you should modify. Maybe the fracdata file? Maybe also the surface data file?

Sam Levis
CLM scientific liaison
 

subha_s2s

New Member
Yes, my boundary conditions work fine.
Now suppose I have chosen a domain of size mx grid points along E-W and ny grid points along N-S. So, my surface boundary files will be of size (mx X ny) grid points. What I want to know is which is/are the appropiate code in the src/main directory that may be modified if I want to exclude 2 grid points each along the N-S and E-W direction. So, my final output files would have a dimension of (mx-2) X (ny-2) grids.

thanks and regards,

Subhadeep
PhD student.
 

slevis

Moderator
Staff member
Instead of changing code, I would post-process the history output in such a way as to omit the rows and columns that you do not want in your figures. If you do not want the model to perform calculations in these rows and columns, then I would do what I suggested in my previous message. And if you insist on changing code to do this, then I'm afraid that I do not know off the top of my head what you should do.

Let's see if other users can come up with suggestions.

Sam
 
Top