Implement Experiment & Analysis Web p99 Dashboard

[Relm-Arrowny]

Goals

Acceptance criteria :

• Unified Authentication: User can log in via OIDC, with tokens successfully propagated through the to both Blueapi and Workflow services.
• Manual Task Submission: User can successfully submit a Blueapi task/plan via the Web UI.
• Manual Workflow Trigger: User can manually trigger a downstream workflow from the UI once a Blueapi plan is complete.
• Automated Pipeline (Desirable): An "Auto-run" toggle that automatically triggers the Workflow Service upon Blueapi plan success.
• Data Feedback Loop: The Web UI captures and displays artifacts/results returned by the Workflow Service.

Tasks

Frontend (Web UI)

• Bare-bone p99UI #315
• Implement/Adapt the workflow submission component from existing VISR. #325
• Create a results panel for rendering workflow output (plots, reconstruction resules).

Backend

• Implement the translation logic between Blueapi output parameters and Workflow Service input within the Supergraph layer?
• Set up a listener for the Workflow Service to push final results back to the UI?

Security & Auth

• OpenID Connect (OIDC).?
• Token Passing via supergrahp??

Test

• Submit a plan $\rightarrow$ Auto-trigger workflow $\rightarrow$ View results in new UI

Related Resources/Note

visr UI is avaiable in and kind of does
Blueapi
@EmsArnold will provide the temple of how visr setup auth.
It may be worth using GDA interface with blueapi backend for demo without the webUI?

[EmsArnold]

Currently, ViSR can query multiple subgraphs from the federated graph (though only session service and workflows have been tested), using the helm chart here. As mentioned earlier, this allows querying sessions and workflows subgraphs, and also kicking off a workflow via a mutation. As mentioned earlier, I haven't yet gotten websockets working, but can update when I do.

[DanPorter]

As mentioned by Douglas Winter, the frontend web ui can be created within in the Atlas 'monorepo':
https://github.com/DiamondLightSource/atlas
Deployment is a matter of creating a release to build the container and adding this to the instrument argo-cd. The VISR and waffle templates are already in there as examples.