* addable generic filter with smart auto-completion (string and/or tree view) metainfo entries (like nexus.NXapm.ENTRY….high_voltage)

[sherjeelshabih]

• [ ] A fancier custom quantity widget
• [ ] Tree view to see how many hits of metainfo.nexus and click to add filter
• [x] Add all metainfo.nexus values to the index
• [x] Get custom quantities to show in new widget
• [ ] Get histogram preview working
• [ ] Add H5Web Widget

  • [ ] Left lane browser for metainfo
  • [x] N h5Web components in one widget all pointing to their respective hdf5 paths (saved in metainfo)
  • [x] Find where to get upload details on the search page and send it to H5WebWidget
  • [ ] H5Web has issues in re-render. Plot looks bad. Should we use our own plotting component instead?

[sherjeelshabih]

H5web devs recommend to try out the lower level components and see if the issues disappear. It could be that the higher level components have a bug.

[sherjeelshabih]

Most of the code we need is in @h5web/app. This includes the nexus visualizer components. The ones in the @h5web/lib can be used as we would expect them. But that will just be the plot without many of the features in @h5web/app. It takes auxilary signals as a prop. We will need to make API calls ourselves. I could try to use this for a demo for example:

https://github.com/silx-kit/h5web/blob/main/packages/lib/src/vis/line/LineVis.tsx

This is what's available in @h5web/app: https://github.com/silx-kit/h5web/blob/main/packages/app/src/vis-packs/nexus/containers/NxSpectrumContainer.tsx

Another approach would be to not have a "gallery" widget with pagination at the bottom. But more of a results list like we have currently. And the more you tap "Show more" . More h5Web widgets will get added on the page without any disappearing. This will make API calls only once per h5web instance.

The last to thing to discuss is that we are already working on a downscaled preview to be baked into Nomad. I can setup our NexusParser to actually do that. Then we will have a single downscaled preview per file. So for any Nexus Archive entry, we will not request to h5grove/hdf5 file. But instead, we request nomad.metainfo for the preview. This will be great for performance and coherency in the UI.

I plan to meet Hampus on Monday to discuss the array implementation in metainfo.

[sherjeelshabih]

• [ ] Add on-the-fly downscaling to the archive API