Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File naming convention #1

Open
barlage opened this issue Apr 26, 2016 · 1 comment
Open

File naming convention #1

barlage opened this issue Apr 26, 2016 · 1 comment

Comments

@barlage
Copy link
Collaborator

barlage commented Apr 26, 2016

Hello Mike,

Sorry to disturb you again.
Now I'm trying to run single point forcing. Because the time interval of site observations is half an hour. So my forcing files look like this: 199805020930.LDASIN_DOMAIN1. But maybe the model now doesn't support the interval of half an hour, so hrldas.exe failed when reading my forcing files.

Prof.Yuan advised me to modify it myself, but I wonder whether you can help me with that. For one thing, others won't trust what I will modify. For another, if the release codes do not include that, when the newest version comes out again and again, we'll modify it again and again unless we don't use the newest.

Even though I don't know whether I should ask you for this help, I still ask you for a try because I think we users are eager for that.
By the way, if the codes can include the spinup option in the namelist like the old version of Offline 1D Noah-MP LSM v1.1, I think it could be more convenient.

I'm looking forward to your reply.
Thanks and best wishes!

@barlage
Copy link
Collaborator Author

barlage commented Apr 26, 2016

There have been discussions locally about changing the filename convention used in HRLDAS. This will include a longer date string, likely consistent with the WRF convention (if you are familiar with that).

It should be quite easy to add minutes to the date string in the READFORC_HRLDAS subroutine (this is what I have done before for flux tower data).

To do this correctly, we will need to modify the forcing file generation as well, plus make the old format backward compatible, so it will take some time to do it right.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant