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

multiple forcing variables in a single ncf file #228

Open
markstro-usgs opened this issue Jul 31, 2023 · 2 comments
Open

multiple forcing variables in a single ncf file #228

markstro-usgs opened this issue Jul 31, 2023 · 2 comments
Assignees
Milestone

Comments

@markstro-usgs
Copy link
Collaborator

I'm trying to run something based on examples/02_prms_legacy_models.ipynb. I already have the variables prcp, tmax, and tmin in a single netcdf file that was written by Parker with his Bandit extraction code. I don't need to convert ascii CBH files into NCF files. I've been looking in the pywatershed code trying to figure out how to specify multiple variables that reside in one .nc but I can't figure it out. Is it possible to do this, or do I need to split them into three files with one variable in each?

@jmccreight
Copy link
Member

@markstro-usgs It's not something that's currently supported. But it can be if Parker's netcdf file is stable. It's not much work.

The quickest path forward is to split them. I can help you do that if you like, should take me a bout 5 minutes to give you a script, so no big deal.

@markstro-usgs
Copy link
Collaborator Author

Good. Thanks James. Splitting up Parker's single netcdf files is the same idea I eventually came to. Before I spent much time on this, I wanted to make sure that I wasn't missing something.

I've got a notebook that I'm working up now. I just need to make sure the variables get named correctly and I've got the format of dates wrong -- minor stuff. When I get this working maybe it's a tool/utility that I could check in for others that are trying to run bandit extractions in pywatershed.

@jmccreight jmccreight added this to the v0.3.0 milestone Sep 26, 2023
@jmccreight jmccreight mentioned this issue Sep 26, 2023
23 tasks
@jmccreight jmccreight removed this from the v0.3.0 milestone Oct 25, 2023
@jmccreight jmccreight added this to the 1.1.0 milestone Dec 1, 2023
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

2 participants