From roark at jlab.org  Tue May 13 18:12:44 2025
From: roark at jlab.org (Torri Jeske)
Date: Tue, 13 May 2025 22:12:44 +0000
Subject: [HydraTeam] Fw: hydra
In-Reply-To: <PH0PR09MB82999C480DAB6C92F670E070D496A@PH0PR09MB8299.namprd09.prod.outlook.com>
References: <PH0PR09MB11837FB008899CA7E3043A837CE96A@PH0PR09MB11837.namprd09.prod.outlook.com>
 <PH0PR09MB829968804CE69ADE5CC7D042D496A@PH0PR09MB8299.namprd09.prod.outlook.com>
 <PH0PR09MB82999C480DAB6C92F670E070D496A@PH0PR09MB8299.namprd09.prod.outlook.com>
Message-ID: <PH0PR09MB11837A7594D0BF634812F0B12CE96A@PH0PR09MB11837.namprd09.prod.outlook.com>

hi hydra team ?

i've been asking shift takers to give me (us) feedback on hydra. here's what i got from Richard Tyson. I think its valuable feedback we can use for UI/UX stuff.
________________________________
From: Richard Tyson <tyson at jlab.org>
Sent: Tuesday, May 13, 2025 5:40 PM
To: Torri Jeske <roark at jlab.org>
Subject: Re: hydra

Hi Torri,

Here are my thoughts from when I was on shift:

When the DAQ is not running, the plots on the main page stay open from the last successful update, then if the page is refreshed they are empty with "Nothing from HYDRA Yet". Same with the Beam Status, Run Number & Last Update entries that go from the last successful update to unknown. In both cases there is a timer since the last attempted update. It's sort of unclear what's going on, especially as the change after refreshing looks like something went wrong. I guess it doesn't matter too much since there is no data coming in anyway but maybe there could be a status like "Not connected to DAQ", and loading either the last successful update (clearly indicating its the last update) or empty plots.

  *


It could be nice showing previous predictions from HYDRA for given subsystems. I might of missed it but found something similar in the training report for the library page but what I had in mind would be more a summary of images flagged as bad by HYDRA. This might give more of a feel of how HYDRA works and what to keep an eye out for.

  *


A shift taker who hasn't taken shifts in Hall B in a while and so hadn't heard of HYDRA was asking me what the greyed images were. It was sort of not straightforward to get across the idea of having enough training data. His initial reaction was that these were subsystems that weren't as important otherwise we would've gotten HYDRA working for them. I know there's a label at the top but maybe the grey images could be moved to a different section?

In general though I find the HYDRA interface generally really clear and informative.

Cheers,
Richard

________________________________
From: Richard Tyson <tyson at jlab.org>
Sent: Tuesday, May 13, 2025 12:21 PM
To: Torri Jeske <roark at jlab.org>
Subject: Re: hydra

Hi Torri,

Sounds good, if anything comes to mind I will let you know!

Cheers,
Richard
________________________________
From: Torri Jeske <roark at jlab.org>
Sent: Tuesday, May 13, 2025 12:08 PM
To: Richard Tyson <tyson at jlab.org>
Subject: hydra


Hi Richard ? if you are bored on shift while we do not have beam, if you have any thoughts on the run page or if anything is confusing or unexpected or you don?t know what it means, could you send me a brain dump of that? I?m trying to work on documentation specific to our shift crews and being both a developer and an end user is hard.



Feel free to also not do this and work on anything else ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/hydrateam/attachments/20250513/1b8b956f/attachment.htm>