[WISE Bug]: Missing value in lut file results in odd error messages and failed validation.

[spydmobile]

Contact Details

spydmobile@gmail.com

What happened?

when launching a model (or validating) that has a lut file with aa missing value eg. no Zero, the system fails with odd errors.

80000000000032c7: Invalid/unknown file format.
root@c6d959b9cec5:/usr/src/app# 

Version

(Linux) 2021.11.xx

What component are you seeing the problem on?

PSaaS Binary, JS Api

Relevant log output

{
 "success": true,
 "valid": false,
 "validation_tree": {
  "error_level": "SEVERE",
  "protobuf_name": "CWFGM.PSaaS",
  "error_values": [
   {
    "name": "/usr/src/app/psaas_data/dipjobs/job_20220530162836509/job.fgmj"
   }
  ],
  "children": [
   {
    "error_level": "SEVERE",
    "protobuf_name": "CWFGM.ProjectProto.Project",
    "error_values": [
     {
      "name": "project"
     }
    ],
    "children": [
     {
      "error_level": "SEVERE",
      "protobuf_name": "CWFGM.GridProto.CwfgmGrid",
      "error_values": [
       {
        "name": "grid"
       }
      ],
      "children": [
       {
        "error_level": "SEVERE",
        "protobuf_name": "CWFGM.GridProto.CwfgmGrid",
        "error_values": [
         {
          "name": "fuelmap.file",
          "value": "Inputs/fuels.tif"
         }
        ],
        "children": [],
        "error_id": "Import.Fuelmap:Invalid"
       }
      ]
     }
    ]
   }
  ]
 },
 "load_warnings": "Error: CWFGM.GridProto.CwfgmGrid: Fuel grid could not be imported."
}

[spydmobile]

SpyD (Franco) — 05/31/2022
Ok, update. the problem was not the raster it was the lut file, after I resampled and rebuilt all the datasets to first int32 (Which failed like float) and then int16, which also failed, I pulled some hair out then had Brett open the dataset in Prometheus which immediately choked and said the lut was invalid because it did not have an entry for 0. I added an entry for pixel value zero to the master LUT file and reran the cutter and modeller and and it fired right up. you guys have some work to do on those error messages and validation log messages I think

[RobBryce]

This plan is straightforward, construct some input data that exhibits the problem, test and add in logic that reports better error messages.

[RobBryce]

I've improved the load warnings message, as well as the exception message emitted upon exit.
The JSON layout for the error reporting was designed with input so that it could be programmatically parsed to gain information on what's wrong. So we're limited to what we can put there, but the information there was unique to identify the problem you reported. Best discussed for determining an efficient long-term resolution here.