Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flying scan with stage. #33

Open
1 of 5 tasks
Relm-Arrowny opened this issue Jun 26, 2024 · 0 comments
Open
1 of 5 tasks

Flying scan with stage. #33

Relm-Arrowny opened this issue Jun 26, 2024 · 0 comments

Comments

@Relm-Arrowny
Copy link
Collaborator

Relm-Arrowny commented Jun 26, 2024

Goals

Acceptance criteria :

  • Flying scan where the motor moves to the starting point and start toward the end point, during which the detector keep measuring as fast as it can until the endpoint is reached or stopped.
  • Each measurement should matches with the motor position as closely as possible but do not have to be exact like step scan.

Tasks

base on the goals, deduce the tasks required. check them off once they're done

  • Make a plan that:
  1. Check motor limits
  2. Move the motor to the start position.
  3. read the current speed and store it
  4. change the motor speed
  5. set the detector running
  6. change motor set point to the final destination
  7. At destination stop collection reset speed.
  8. clean up, set speed back to before scan, even if scan failed.

Ref:
There are two ways to get this done.

    • The hardware trigger fly scan with panda (correct way).
  • This require correct wiring into panda (ref /tutorial1_blinking_leds.html)
    • Hit and hope fly scan. (Less accurate but can work on any motor and detector without the need of panda or wiring) Hit and hope fly scan. #34
  • No hardware trigger, we just set the motor going and monitor the position and take data as fast as possible.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant