Description
(1) While generating the testing files, it appear to me that the input sTEC data have multiple variables to be clarified and, if necessary, a naming convention for some of these variables should be set up. I am recording these variables using this issue.
(2) when geoval files provide integration weights, we need to make sure the weights are ready to be used, instead of being a secondary variable requiring further processing inside UFO. I noticed the original testing files I received contain path_length, which is the reference length relative to a starting point. It is not yet converted to weights.
Requirements
Require upstream code to be updated
Acceptance Criteria (Definition of Done)
UFO tests and model interface-UFO tests are properly set up with the naming convention.
Description
(1) While generating the testing files, it appear to me that the input sTEC data have multiple variables to be clarified and, if necessary, a naming convention for some of these variables should be set up. I am recording these variables using this issue.
(2) when geoval files provide integration weights, we need to make sure the weights are ready to be used, instead of being a secondary variable requiring further processing inside UFO. I noticed the original testing files I received contain path_length, which is the reference length relative to a starting point. It is not yet converted to weights.
Requirements
Require upstream code to be updated
Acceptance Criteria (Definition of Done)
UFO tests and model interface-UFO tests are properly set up with the naming convention.