Page History

...

•  DAS-1478: Adding regression tests for the PO.DAAC MUR collection.
•  DAS-1479: Ensuring a request for NetCDF-4 output and "all" variables includes a STAC item for the output.
•  DAS-1480: Ensuring a request for GeoTIFF output and "all" variables includes links to all bands, not just the colour bands for the first variable.
•  DAS-XXXX: General code clean-up (e.g., breaking down the transform.py monolith, and the HarmonyAdapter class within it).
  •  A potential separate module could contain all the GDAL command construction, within which we could gradually iterate away from the current subprocess architecture.
  •  Another separate module could handle coordinate-related utilities functions (e.g., deriving minimally encompassing bounding boxes, etc).
•  ASF to remove their GitHub repository and Docker images in DockerHub.
•  Any Bamboo CI/CD relating to the ASF artefacts should be removed.
•  Uninformative band names in .png output, currently "Band 1", "Band 2", etc.  Is it sufficient to assume that the output name will explicitly include the variable name - what if it's an all-variable request? (Discovered during DAS-1478)
•  Requests for MUR data with a whole-Earth bounding box (36,000 x 17,999 array elements) lead to containers running out of memory and therefore request failures. Do we need to assign more memory to the HGA containers via Harmony environment variables? Matt Savoie was able to get a request to run locally with 16 GB of memory. UAT was failing with 8 GB. (Discovered during DAS-1478)
•  requests for image/png with multiple variables fail to return multiple png files. Owen did a cursory glance and discovered "So from the quickest of grokking. I think that recolor gets called for all variables (via combin_transfer from this loop or this loop). But... there's only ever one call to stage the output (here). There's a separate call to stage the .wld file, but nothing to loop through multiple outputs."
•  NetCDF-4 file output is reconstructed to more closely match the input structure, this includes: variable names, file structure, persistence of metadata variables, array structure (e.g., recombining banded variables into a single variable output, rather than "Band 1", "Band 2" etc sub-variables). This will require consultation with ASF and PO.DAAC stakeholders, to ensure they agree this is an improvement.