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

ncdio_pio.F90.in at line 2

Status
Not open for further replies.

MrIgnition

Member
Thanks. Indeed, there is an inconsistency in dimension sizes between fsurdat and fatmlndfrc. You need to ensure that the domain sizes are the same for both of these files.
This is a great relief. please can simple regridding do this?
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
No, I wouldn't regrid. I'm not sure where your domain file came from, but you should follow the User's Guide for creating surface datasets and domain files. I think the following text was a response to one of your previous posts. We still don't have the links fixed but the general workflow should still apply and the README files should be helpful

"This is the User's Guide page for the general flow for creating datasets.

1.3.5. Creating Surface Datasets — clmdoc release-clm5.0.01 documentation

The problems I see are that the links don't seem to work. But, paging through the User's Guide page by page seems to work. Do you see something different?

Also note that the README files in the checked out code are also helpful and should be correct. You might find the README files to be sufficient."
 

MrIgnition

Member
Thanks Oleson,
This, about anomalies in my domain file is correct. Truly 3 files were created. 2 domain.ocn files and 1 domain.lnd file. I renamed the domain.ocn files to domain.lnd and vise versa as taught (because of masks). But then i discover that out of the 2 domain.lnd files, 1 has the horizontal resolution and coverage I specified during SCRIPgrid generation but the other has a global domain with a different resolution. The problem has always been caused by this domain file with a global coverage. I will as advised now go all over the process again. Troubleshooting has taken so much time but I think going over again for the sake of correctness is worth it.

Thanks for your support always.
 
Status
Not open for further replies.
Top