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
Implement MET's Filetype determination logic in METplus.
This is sort of a continuum from issue #72 and the relevant closing comments from
issue #72 are included below:
The overall determination of file type needs to be revisited to match MET's behavior.
That way there is consistency between applications.
Requirement) Review MET's logic on this.
Look at this function: grd_file_type()
In this file: ./src/libcode/vx_data2d_factory/data2d_factory_utils.cc
Requirement) Handle the following unique case ?
There is also the issue of a Grib file that did not have the magic-cookie information
in the first 4 bytes of the file. One could argue that it is not a valid grib file. However,
the individual records in the file were correctly identified and formatted. Also, the file was
able to be processed by MET, IF the "filetype=GRIB" option was passed to MET.
Requirement) ?
Add functionality to pass along "filetype" option to MET
Requirement) specify expected input FILETYPE in METplus conf file ?
There is some complication to this problem ... such as identifying the file type in the
METplus conf file where as the input in one step may be GRIB 1 or GRIB 2 .. the output is
NetCDF which will be input to the next step in the process list .... So what is the best way
to identify and handle this ?
The text was updated successfully, but these errors were encountered:
Implement MET's Filetype determination logic in METplus.
This is sort of a continuum from issue #72 and the relevant closing comments from
issue #72 are included below:
The overall determination of file type needs to be revisited to match MET's behavior.
That way there is consistency between applications.
Requirement) Review MET's logic on this.
Look at this function: grd_file_type()
In this file: ./src/libcode/vx_data2d_factory/data2d_factory_utils.cc
Requirement) Handle the following unique case ?
There is also the issue of a Grib file that did not have the magic-cookie information
in the first 4 bytes of the file. One could argue that it is not a valid grib file. However,
the individual records in the file were correctly identified and formatted. Also, the file was
able to be processed by MET, IF the "filetype=GRIB" option was passed to MET.
Requirement) ?
Add functionality to pass along "filetype" option to MET
Requirement) specify expected input FILETYPE in METplus conf file ?
There is some complication to this problem ... such as identifying the file type in the
METplus conf file where as the input in one step may be GRIB 1 or GRIB 2 .. the output is
NetCDF which will be input to the next step in the process list .... So what is the best way
to identify and handle this ?
The text was updated successfully, but these errors were encountered: