Closed TeaganKing closed 3 months ago
The ADF tool just uses ncrcat and is not very flexible. The main things we want are chunking and compression. Should this be part of issue #18 ?
In our discussion during the CUPiD hackathon, with @nusbaume @brianpm @justin-richling @kafitzgerald and myself, we decided we'll want to pull out adf_diag.create_time_series()
; this will entail a slight rewriting.
We want to avoid circular dependencies. Let's plan to make a timeseries.py
file within CUPiD/cupid
. Eventually, if we pull in Brian Dobbins' timeseries repository (if it's actually useful to replace), we can replace the timeseries.py
file.
We could merge the ADF taylor diagram with GeoCat Viz taylor diagram.
Taylor_plot_setup
, plot_taylor_data
, and taylor_plot_finalize
could probably be replaced by geocat's function. We probably can't replace gathering data from ADF, selecting variables, subsetting for seasonal averaging, etc.
Overarching CUPiD needs: timeseries, regridding, climatology/time averaging, website generation functionality.
Prioritization:
ADF/lib/plotting_functions.py
, we may want to pull mask_land_or_ocean
into a centralized place.) See plots described in #6 Moving forward:
From a discussion with @mnlevy1981 regarding the timeseries note-- we'll eventually want to have all components be able to run on timeseries in order to use smaller model output files, but we should probably first focus on some of the other items from the ESDS event hackathon last week.
We should also be sure that this is not a duplicated effort (eg, with Brian Dobbin's tool).
This could also be an area where we could leverage GeoCAT.