Add back-end warning/error if aggregated tables are missing

[jorgenherje]

Some modules uses endpoints which fetches aggregated data/table collections from Sumo.

If no collections are found, aggregation might be missing - provide informative error message in such cases?

E.g.:

• Summary vector data?
• Inplace volumetrics tables?

[anders-kiaer]

We have a new report from user which was hit by this.

User report from Johan Sverdrup:

If several ensembles are picked to visualize and one of them is missing the aggregation data then nothing is visualized at all instead of visualizing the data for those ens that have aggregation and skipping the one without. This is a bit confusing cause when people add an ensemble and suddenly everything disappears they think that the module is broken, not that they forgot to run aggregation.

[jorgenherje]

not

This could be dependent on module implementation as well. Which module did they use when this occurred?

If each ensemble has its own query, it should be possible to handle the error per failed query and allow the front-end to assemble data based on retrieved data. But this has to be handled when implementing handling of query data in front-end.

[anders-kiaer]

not

This could be dependent on module implementation as well. Which module did they use when this occurred?

If each ensemble has its own query, it should be possible to handle the error per failed query and allow the front-end to assemble data based on retrieved data. But this has to be handled when implementing handling of query data in front-end.

This was the in-place volumes module.

The most important thing is that the user is told which ensemble(s) that have missing (aggregated) data. If we show as much data as possible, or none at all in the case some ensembles are missing the data, the user did not have strong opinions on (as long as they understand which ensembles are the ones who make the query/queries fail).