openwfm / wrfxpy

WRF-SFIRE data acquisitiion, forecasting, data assimilation, and visualization in Python.
MIT License
37 stars 17 forks source link

What is the production status of wrfxy? #79

Open jordancaraballo opened 1 year ago

jordancaraballo commented 1 year ago

Hi All,

We are trying to run WRF-SFIRE at a production level on our cluster, and wrfxpy seems to be a great solution for it. However, I am trying to figure out if wrfxpy is in a production state and if there are components where you might need some open source collaboration.

I noticed that the readthedocs page for this package is outdated, but could not find any updated documentation on how to best leverage the package (I see some small API changes from the master branch not included in the latest documentation).

I also see an open issues #67 that seemed to start addressing it, but with no traction. I believe I have encountered this GDAL problem in the past and will try to find my solution from my repos to post a pull request.

Are there any plans on publishing a pip or conda package in the future? I can probably help on that using Github actions given that it would be extremely useful for our container infrastructure to install things via package managers.

Are there plans on publishing a new release soon? Last release I see is from 2020 and the repo seems to have been largely updated since then.

Lastly, is the plan to continue supporting Python2?

Thank you very much! Jordan (jordan.a.caraballo-vega@nasa.gov)

Fergui commented 11 months ago

Hi Jordan,

We currently use wrfxpy and WRF-SFIRE to run operational forecasts. So, it is at a producing level that can handle that. We would love to collaborate and improve the code through open-source collaboration.

You are right, we need to update readthedocs but we were having some issues with it. The current most comprehensive and updated documentation can be found here: https://wiki.openwfm.org/wiki/Running_WRF-SFIRE_with_real_data_in_the_WRFx_system

We were thinking of creating a pip or conda package but never had time to do so. That would be interesting because we would need to refactor slightly the code, but it could be worth it.

Yes, we are planning on doing a major release soon. We have accumulated some developments in the develop branch that would need to be tested and pushed into a release.

Python2 support is not necessary moving forward.

Thank you so much,

Angel Farguell Post Doctoral Research Associate Department of Meteorology and Climate Science Wildfire Interdisciplinary Research Center San Jose State University