mx/AareDAQ
0
1
Fork 0
Code Issues 52 Pull Requests 2 Actions Packages Projects Releases 63 Wiki Activity

Feedback from Katherine after testing #163

New Issue
Open
opened 2026-08-24 08:36:38 +02:00 by duan_j · 0 comments
duan_j commented 2026-08-24 08:36:38 +02:00
Owner
Copy Link
Copy Source

I’ve found a few niggles over the past couple of days.

When an automated queue is started, the software should switch to sample alignment without prompting the user to do it.

  • I encountered a ‘no pin in gripper error’, but it wasn’t obvious. I noticed the robot had gone to dry, but could only see there had been an error by checking the console log. It’s quite a subtle place to put an error message; I don’t think many users would see it. It’s clear in the database, though.
  • The ‘park and dry when automation finishes’ tickbox is not working.
  • I’d set the transmission to 1% in the spreadsheet; the data were collected at 100%. #167
  • The collimator does not always move to the saved positions; sometimes it does, but other times it reverts to an old value. This happens without restarting any software, so I’m not sure why. For debugging, can AareGUI show what it thinks are the saved positions for collimator x and y, beamstop x and y, and Aerotech y?
  • At 17:14 the queue stopped after sample lyso_8. Console log says the automation queue is empty. It’s not. There are still samples lyso_9 to lyso_16 in the queue window.

I’ve just restarted the queue to do lyso_9 to lyso_16, there may be more feedback later. And now after restarting the queue – the correct collimator position is being used for the data collections. If you want to debug, look carefully at the diffraction images; you can see when the wrong value is used because it produces rings in the image.

I’ve found a few niggles over the past couple of days. When an automated queue is started, the software should switch to sample alignment without prompting the user to do it. - I encountered a ‘no pin in gripper error’, but it wasn’t obvious. I noticed the robot had gone to dry, but could only see there had been an error by checking the console log. It’s quite a subtle place to put an error message; I don’t think many users would see it. It’s clear in the database, though. - The ‘park and dry when automation finishes’ tickbox is not working. - I’d set the transmission to 1% in the spreadsheet; the data were collected at 100%. #167 - The collimator does not always move to the saved positions; sometimes it does, but other times it reverts to an old value. This happens without restarting any software, so I’m not sure why. For debugging, can AareGUI show what it thinks are the saved positions for collimator x and y, beamstop x and y, and Aerotech y? - At 17:14 the queue stopped after sample lyso_8. Console log says the automation queue is empty. It’s not. There are still samples lyso_9 to lyso_16 in the queue window. I’ve just restarted the queue to do lyso_9 to lyso_16, there may be more feedback later. And now after restarting the queue – the correct collimator position is being used for the data collections. If you want to debug, look carefully at the diffraction images; you can see when the wrong value is used because it produces rings in the image.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
buntschu_d (buntschu_d) duan_j (duan_j) glettig_w (glettig_w) gobbo_a (gobbo_a) gotthard_g (gotthard_g) leonarski_f (leonarski_f) mx-gitea olieric (olieric) perl_d (perl_d) takaba_k (takaba_k) wang_m (wang_m)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mx/AareDAQ#163