Open taobrienlbl opened 4 hours ago
I'll take a look. I lean toward solution 2, but will see what makes the most sense.
that sounds good to me - thank you! If we do go with solution 2, it might be good to add an option to the CF writer to override the group for all variables (e.g., set the group to /
to avoid groups in the output file). If this is implemented as a BOOST command line option, then it could be specified for any TECA app through the advanced command line options.
@ghweber - great job on #799! I can now use
teca_metadata_probe
on output from HENS, and I can almost useteca_bayesian_ar_detect
. It looks like the coordinate nameglobal/lat
andglobal/lon
is passed on in the TECA metadata in a way that causes theteca_cf_writer
stage to fail:Two potential solutions come to mind, one simple, the other more complex:
global/
part from variable names and instead add a metadata key that stores the netCDF group of the variable; orteca_cf_writer
to handle groups: e.g., createlat
in theglobal
group if the variable name isglobal/lat
What do you think? And would you be able to take this on?