Dependencies need to be agreed upon about act HOT 12 CLOSED

We could always look and see if something better could take the place of astral. That's just what was used in the DQ Office for the shading.

We might also want to think about cartopy as well as I can see some contour plotting of data at SGP to be useful.

from act.

Just thinking, would there be a reason to have py-art as a dependency?

from act.

I would add it later when we flesh out some more stuff on the radars. I think the radar mentors will be a later adopter of this this technology.

from act.

If you want to use xr.open_mfdataset to read more than one file at a time or to use the parallel feature you will also need dask.

from act.

We apparently need to constrain the minimum version of dask. Jenni ran into an issue where after installing it didn't work because it was using an old version of dask that doesn't implement delayed objects.

from act.

OK do you know what version we need?

from act.

from act.

I have made MetPy an optional dependency for Skew-T plots, since the rest of ACT will work fine without MetPy. I figure this is the way to go unless we wind up having much more of ACT depend on MetPy.

from act.

Current list of dependencies

pandas
matplotlib
numpy
scipy
xarray
astral
dask
distributed
pint
cartopy
boto3
pyproj > '2.0.0'

Do we want to keep this open to track future dependencies, or can we close out and discuss future ones in the pull requests?

from act.

How do we handle dependencies. I see one with a version number. I had to manually update cartopy above a version number to get it to work. Should we pay more attention on version number minimums?

from act.

@kenkehoe yes, if we have a minimum version, we should have that indicated. Do you remember what version it was?

from act.

Closing this out as the base dependencies are pretty set and we will review with each new addition

from act.