Parameter histograms not loaded in both webviz-ert and ert gui about webviz-ert

[hnformentin]

The error message (** Warning:: invalid node found at offset..) reminded @oyvindeide about an issue related to incompatibility between storage and config. His suggestion was to check that the steps to reproduce the issue reproduce the error message. After, try to check if the same happens in an earlier komodo version, say from the beginning of this year. With that we could identify if this was a regression...

[mortalisk]

I have found the error message first appears in komodo 2022.05

[mortalisk]

But other than the printed error message, I don't know if there are any other differences. The issue about missing data seems to be expected as there is no data in the "default" ensemble. I'll check a bit more.

[mortalisk]

I also get this: "[WARNING] res.enkf_fs: Index out of bounds. keyword_index=0 vector_size=0"
This happens when fetching from the cases with prefix "pred_"

The other error happens on the "default_" cases.

It seems that the storage in the drogon link in this issue is somwhat corrupted. @oysteoh should we report this somewhere?

[oysteoh]

I'm not sure - maybe someone with a better understanding of this could chime in? @berland do you have any idea what this warning is about and is it something wrong with the dataset or is this a bug introduced in our code?

[berland]

Nothing springs to mind 🤷🏻

[berland]

This is a new ERT version extracting data from storage as it was in the tar.gz file? Has it been tested to regenerate the storage data for the Drogon case in a newer ERT version?

[hnformentin]

I run the case drogon_ahm.ert, komodo (2022.08.02-py38), on the August 22th.
When I try to open it in webviz-ert, it presents a similar warning 2022-08-30 14:21:59,032 [WARNING] res.enkf_fs: Index out of bounds. keyword_index=2 vector_size=0.
Unless I did something wrong with the way I simulated, it seems the problem persists...

[hnformentin]

The initial issue is now outdated.
equinor/ert#3845 should be investigated instead, it is specific issue for invalid node.