How to run PyGEM on a watershed scale?

[cullenkate]

Hello PyGEM community and David @drounce !

What is the best way to run PyGEM on an individual watershed scale? Currently I am running it with RGI 7.0, specifying in config.yaml to run in my region, subregion, and for the specific RGI IDs that I identified in my basin (list of 354 glacier IDs). However, I keep running into various bugs and have tried various configurations and iterations of this without avail. So, I wonder if there's an easier and established way to do this? Alternatively, I could run it for my full subregion and clip the outputs to my watershed. Thanks for your insight on the best way forward!

code I'm using in config.yaml:

#===== GLACIER SELECTION ====
setup:
rgi_region01:
[-] 17 #dash in brackets here bc the word processor creates a bulleted list
rgi_region02: "02"
rgi_glac_number_fn: maipo_glaciers_rgi7.txt # file I created using geopandas with the list of RGI glacier IDs in my basin to run

[drounce]

We're working on updating datasets to enable the use of RGI 7.0; however, we're not there (no global model is yet) because of all the datasets that need to be converted first. Hopefully by the end of this summer.

Regarding the config.yaml file, @btobers should be able to provide some guidance (I'm heading out onto the glacier tomorrow and will be offline), but you appear to be using it correctly. Are you sure it's not running the correct glaciers? If not, then it could be an RGIv7 issue that's not considered.

[cullenkate]

Looping back to this, is PyGEM v1.0.4 enabled to use RGI 7.0? Thank you!

[drounce]

We ended up not pursuing this yet as we're in a bit of a holding pattern until all the datasets are available (e.g., debris, mass balance). Those who are producing those data have said they should be available by the start of next year, so we should be fully operational with RGIv7 around then (subject to any delays of course)

[cullenkate]

Great, makes sense and thanks for the update!