tomography/scanscripts

Issues

• Command-line interface to scripts

  #23 opened 2 years ago by canismarko
  2

• Verify the ``aps_32id.run.tomo_step_scan`` works in production

  #15 opened 2 years ago by canismarko
  1

• Have the calling script open a log-file based on the expected HDF file

  #9 opened 2 years ago by canismarko
  2

• Implement a script for tomo_fly_scan

  #22 opened 6 years ago by canismarko
  1

• Verify that fast-shutter hardware triggering works

  #21 opened 7 years ago by canismarko
  0

• Investigate why tomo_step_scan caused an outer loop to fail

  #20 opened 7 years ago by canismarko
  0

• Make the tomo_step_scan script work efficiently

  #19 opened 7 years ago by canismarko
  0

• Verify that ``aps_32id.run.energy_scan`` works in production

  #14 opened 7 years ago by canismarko
  1

• Make it so TXM._trigger_projections doesn't spam the trigger

  #6 opened 7 years ago by canismarko
  1

• Re-Implement the ``stop_scan()`` function for the ``energy_scan.py`` script

  #5 opened 7 years ago by canismarko
  1

• Convert ``aps_32id.run.energy_scan`` so it can be tested against a stubbed TXM object

  #16 opened 7 years ago by canismarko
  0

• Couple the DCM/BPM closed loop to shutter status

  #18 opened 7 years ago by canismarko
  2

• library module name starting with numbers are not allowed

  #12 opened 7 years ago by decarlof
  3

• Make sure the "Stop" button in the GUI stops the script cleanly

  #8 opened 7 years ago by canismarko
  0

• Test the TXM.move_energy() method with calculated value

  #4 opened 7 years ago by canismarko
  0

• Figure out why TXM.wait_pvs doesn't work in production

  #7 opened 7 years ago by canismarko
  1