Skip to content
This repository has been archived by the owner on Nov 3, 2021. It is now read-only.

one-point scan #1303

Open
dschick opened this issue Mar 4, 2020 · 4 comments · May be fixed by #1634
Open

one-point scan #1303

dschick opened this issue Mar 4, 2020 · 4 comments · May be fixed by #1634
Assignees
@jkotan
Labels
daq data acquisition related issues enhancement impact:high scans scans related issues size:S

Comments

@dschick
Copy link

dschick commented Mar 4, 2020

this is a rather stupid question, but I was wondering, if there is a simple way to do a step-scan with only one point?
I was not able to realize that with a simpe ascan, I always got two point.
I guess, I could use the ascan macro as a template and change it accordingly, but maybe you have a better advice?

The reason for my request is, that especially when worling with 2D detectors, I would like to write an alternative to a simple ct in order save also all meta data for an acquired image.
So instead of doing a ct and writing down the filename and all motor positons for that image in my labbook, I would like to do a onepointscan, or name it capture, which creates a full scan entry in the data file, including the snapshot, but with only one scan point, ideally with a dummy or the time as the movable.
@cpascual
Copy link

cpascual commented Mar 5, 2020

A comment regarding naming: IMHO the resulting macro's name should be more related to "ct" than to "scan" regardless of it being eventually implemented as a one-point scan. In other words: the name should reflect the function, not the implementation.

@guifrecuni
Copy link

I'd suggest something like "meas/measurement", "exp/expose" or "acq/acquire" which is what happens at each point of the scan. And it could include the position/s where this measure should take place.

@tiagocoutinho
Copy link

Hi,
I wrote a "hook" that uses the data produced by ct and calls pyplot. It is a customized code for my situation.
I'll be happy to share a snippet if you are interested.Here is a result:
image

An alternative could be to have ct write to Recorder(s) a "ct_record". The show_scan GUI could pick it up and show it.
Due to the potential amount of data I would propose to encode this with a more interesting codec like msgpack + msgpack_numpy instead of json

@johanfforsberg johanfforsberg added daq data acquisition related issues scans scans related issues question labels Jun 22, 2021
@reszelaz
Copy link
Collaborator

As discussed in #1501 we will go for allowing the ascanct and timescan to acquire one point less. So, timescan 1 0.1 would acquire just one point over 0.1 s. I think this is what @dschick asks for?

@jkotan jkotan self-assigned this Jul 7, 2021
@jkotan jkotan linked a pull request Jul 7, 2021 that will close this issue
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jkotan jkotan

Labels
daq data acquisition related issues enhancement impact:high scans scans related issues size:S
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Issue 1303: change the timescan first parameter to nb_points desy-fsec/sardana
7 participants
@johanfforsberg @guifrecuni @tiagocoutinho @cpascual @reszelaz @jkotan @dschick