Open dwfncar opened 8 years ago
EaSM if available otherwise AOP2017 VX1 NCAR by jensen
This functionality is also need for processing SWPC NetCDF files. See email history about this below:
Question for you. We had a telecon with some space weather folks this afternoon talking about their potential use of MET. They sent use some sample NetCDF files containing space weather data to see if/how it could be used in MET.
The data is on dakota in:
/d3/projects/NCEP_Vx/SWPC/netcdf_TEC_nov
We want to compare the GloTEC data to the WAM_TEC data. "TEC" stands for total electron content. Here's more info about this data:
WAM...
91 lats from -90 to 90 (every 2 deg)
90 lons from 0 to 356 (every 4 deg)
Output every 15 minutes means 96 timestamps per day (The space weather folks call this the "cadence".)
GloTec...
72 lats from -88.75 to 88.75
72 lons from -177.5 to 172.5
Output every 10 minutes means 144 timestamps per day.
The data is nice and smooth and would be a great candidate for using in MTD.
Here's what we'd want to do...
(1) Pass a single WAM and GloTec files for one day to MTD.
(2) Regrid the WAM data to the GloTec domain... using bilinear?
(3) Select every 2nd WAM timestep and every 3rd GloTec timestamp so that they can be compared every 30 minutes.
The question is, does MTD currently support the selection of every 2nd or every 3rd timestep from an input NetCDF file?
FYI, here's a command I used to plot one timestep:
/usr/local/met-7.0/bin/plot_data_plane \
WAM_TEC_2017_11_23.nc \
WAM_TEC_2017_11_23.ps \
'name="TEC"; level="(1,,)"; file_type=NETCDF_NCCF;'
by johnhg
This functionality was also requested by Ashley Payne at Univ Michigan via met-help:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=87632
by johnhg
The CF-Compliant NetCDF files used for the EaSM project contain multiple output times in a single file. Currently, running MODE-TD on these files requires some preprocessing. Update the configuration file logic to support a "range" for the time variable...
For example...
data(time, lon, lat)
Read a range of times as...
name="data"; level="(10-50:4,,)";
In MTD, make sure the data is in increasing order by time.
Also support some sort of "skip" option... i.e. 10-50, every 4th time. [MET-654] created by johnhg