You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an extraction date range includes the date on which a variable was added to a dataset, the added variable is included in the extracted dataset regardless of whether or not it is in the list of requested variables. Known occurrences of this are:
HRDPS-2.5km-operational.yaml profile for percentcloud variable added to dataset on 8-Jul-2017
HRDPS-2.5km-operational.yaml profile for variables LHTFL_surface, PRATE_surface, and RH_2maboveground added to dataset on 6-Dec-2018
This issue is demonstrated for the 1st of those cases by the extraction config:
Use the 1st and last dataset paths to calculate a more complete set of all
variables in the dataset. That avoids the inclusion in the extracted dataset of
variables that were added to the dataset during the extraction time span.
Fixes issue #51
Use the 1st and last dataset paths to calculate a more complete set of all
variables in the dataset. That avoids the inclusion in the extracted dataset of
variables that were added to the dataset during the extraction time span.
Fixes issue #51
Discovered during investigation of issue #43.
When an extraction date range includes the date on which a variable was added to a dataset, the added variable is included in the extracted dataset regardless of whether or not it is in the list of requested variables. Known occurrences of this are:
HRDPS-2.5km-operational.yaml
profile forpercentcloud
variable added to dataset on 8-Jul-2017HRDPS-2.5km-operational.yaml
profile for variablesLHTFL_surface
,PRATE_surface
, andRH_2maboveground
added to dataset on 6-Dec-2018This issue is demonstrated for the 1st of those cases by the extraction config:
The extracted dataset contains variables
precip
as requested, andpercentcloud
, with the latter havingNaN
values prior to 2017-07-08.The text was updated successfully, but these errors were encountered: