1 / 19

Fast Continuous Acquisitions Framework for Beamline Data

Explore a framework for continuous acquisitions in beamlines, covering various motor types, synchronization techniques, and data sources for efficient data handling and visualization. Learn how to set up Zapscans and configure ZAP for automatic acquisition.

eagan
Download Presentation

Fast Continuous Acquisitions Framework for Beamline Data

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Continuous / Fast AcquisitionsMotivation for a framework Vicente Rey Bakaikoa BLISS Day Out / 15 Jan. 2007

  2. Continuous Acquisitions • Beamlines: 25 • Total number of setups: 35 to 40

  3. V.Rey Bakaikoa BLISS Day Out – 15 Jan 2007

  4. V.Rey Bakaikoa BLISS Day Out – 15 Jan 2007

  5. V.Rey Bakaikoa BLISS Day Out – 15 Jan 2007

  6. V.Rey Bakaikoa BLISS Day Out – 15 Jan 2007

  7. Changing conditions • Motors • Programming • Reading of encoder input • Trigger for start • Constant speed • Start movement • Motor types: • Existing: Vpap+Smpap, Vscanner, Pm304, FlexMotion, Galil, Micos, ID19 Fasttomo • Coming soon: Icepap, Aerotech, SpaceFab, Newport • Special conditions: breathing, chopper • Time only

  8. Data sources • Sliced by sync: • Vct6 + hook • P201 + hook • Musst (counter, encoder, Mca) • Xia/XMAP • Frelon ( espiafamilly: Dalsa, Sarnoff, soon Medipix) • Dalsa (Coreco) • McaAIM: Master only • Other: Mar, Adsc (integration during oscil) • Gas Filled Detector

  9. Synchronization • Slicing: • Opiom • Vct6, P201, MUSST • Trigger signal from detector • McaAIM • Start / Stop

  10. Sequencer • Coordinate programming and configuration of all actors • Reads buffers during acquisition • Online data visualization • Reconstructation of data, save...

  11. Existing sequencers • Zap • Oscillation familly of macros • Set detector to integrate • Sync. Motor, shutter and acquire data during acquisition • Beamline specific macros V.Rey Bakaikoa BLISS Day Out – 15 Jan 2007

  12. Zapscans • Generalization of continuous acquisition • Handles configuration of data readers, motors • Provides modes, plot, data reconstruction… • Different scan types: zapline, zapimage… V.Rey Bakaikoa BLISS Day Out – 15 Jan 2007

  13. How to get your zap working With just 6 clicks and 35 cts!!

  14. How to get your zap working • Dial 2531 on your phone (4 clicks) • Pronounce the password: “café?” • Walk to the cafeteria with “He” • Enter 35cts in the coffee machine • Click item selected by “He” (5th click) • Now put your warmest clothes and get out of the cafeteria • Click on the lighter to light his cigarette (6th click) • Ask for you zap V.Rey Bakaikoa BLISS Day Out – 15 Jan 2007

  15. Automatic zap configuration • If you followed the previous method correctly “He”will: • Copy /users/blissadm/local/spec/macros/id21zap.mac from xrmd • Rename it in idxxzap.mac • Adapt the idxxzapsetup macro to your beamline • Remove the 2554 zap pseudo counters macros you don’t care from this file • Touch a lot of cables V.Rey Bakaikoa BLISS Day Out – 15 Jan 2007

  16. The idxxzap.mac file def idxxzapsetup '{ # zap framework setup zapconfig 3 # zap interruption generator zapintgenconfig "OPIOM" # zap hook configuration zaphookconfig "VCT6" "LINUX" "idxx/hook/10" "idxx/Vct6_00/2“ # define hook counter zapcntadd("arr_sdd2", "idxx/vct6_01/6","VCT6", "0“,"substract", 1) zapcntadd("arr_mono", "cc133_0","CC133", "0x00 9","encoder",1) # define pseudo counter zappseudoadd("arr_srcur", "idxx_zap_pseudo_srcur_read", "COUNTER", 0) # machine current zappseudoadd("arr_energy", "idxx_zap_pseudo_energy_read", "MOTOR", 0) # energy in KeV # ZAP motors (if constant speed needed) zapcstspeed 1 # constant speed zapmotconfig "OPIOM“ # motor multiplexer zapmotadd(dety, "MAXE", 0, 15000) # VPAP+SMPAP zapmotadd(sampz, "VSCANNER", 4, 100000) # piexo + VSCANNER # zap plotting ZAP_PLOT["plot1D"] = 1 }’

  17. The idxxzap.mac file(more likely) • def idxxzapsetup '{ • # zap framework setup • zapconfig • # zap interruption generator • zapintgenconfig “VCT6" “idxx/Vct6_00/1” • # zap hook configuration • zaphookconfig "VCT6" "LINUX" "idxx/hook/10" "idxx/Vct6_00/2“ • # define hook counter • zapcntadd("arr_sdd2", "idxx/vct6_01/6","VCT6", "0“,"substract", 1) • zapcntadd("arr_mono", "cc133_0","CC133", "0x00 9","encoder",1) • # No constant speed • zapcstspeed • # zap plotting • ZAP_PLOT["plot1D"] = 1 • }’

  18. Then just run: zaplinemne start stop time npoints

  19. And now with you…

More Related