{"action":"created","issue":{"url":"https://api.github.com/repos/NSLS-II/bluesky/issues/247","labels_url":"https://api.github.com/repos/NSLS-II/bluesky/issues/247/labels{/name}","comments_url":"https://api.github.com/repos/NSLS-II/bluesky/issues/247/comments","events_url":"https://api.github.com/repos/NSLS-II/bluesky/issues/247/events","html_url":"https://github.com/NSLS-II/bluesky/issues/247","id":113467680,"number":247,"title":"_set/_unset_acquire_time needs a re-think","user":{"login":"dchabot","id":4429592,"avatar_url":"https://avatars.githubusercontent.com/u/4429592?v=3","gravatar_id":"","url":"https://api.github.com/users/dchabot","html_url":"https://github.com/dchabot","followers_url":"https://api.github.com/users/dchabot/followers","following_url":"https://api.github.com/users/dchabot/following{/other_user}","gists_url":"https://api.github.com/users/dchabot/gists{/gist_id}","starred_url":"https://api.github.com/users/dchabot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dchabot/subscriptions","organizations_url":"https://api.github.com/users/dchabot/orgs","repos_url":"https://api.github.com/users/dchabot/repos","events_url":"https://api.github.com/users/dchabot/events{/privacy}","received_events_url":"https://api.github.com/users/dchabot/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-10-26T22:49:56Z","updated_at":"2015-10-26T23:04:21Z","closed_at":null,"body":"I think there is a problem with `_set_acquire_time( )` in “simple_scans.py”, in the sense that nothing inheriting from `ScanBase` (“scan.py”) makes use of that.\r\n\r\nThis is part of the reason for the confusion at CSX today - users were running a `qscan`, which inherits from `ScanND` and displayed the unexpected behavior.\r\n\r\nWhen they ran `count( )`, all was as expected…\r\n\r\nSo, we could stuff `_set/_unset_acquire_time` into `ScanBase.pre/post_scan`.\r\nOr, we could wrangle something together using `configure`/`deconfigure`.\r\nOr maybe there is a better option?\r\n\r\nThoughts?"},"comment":{"url":"https://api.github.com/repos/NSLS-II/bluesky/issues/comments/151309490","html_url":"https://github.com/NSLS-II/bluesky/issues/247#issuecomment-151309490","issue_url":"https://api.github.com/repos/NSLS-II/bluesky/issues/247","id":151309490,"user":{"login":"danielballan","id":2279598,"avatar_url":"https://avatars.githubusercontent.com/u/2279598?v=3","gravatar_id":"","url":"https://api.github.com/users/danielballan","html_url":"https://github.com/danielballan","followers_url":"https://api.github.com/users/danielballan/followers","following_url":"https://api.github.com/users/danielballan/following{/other_user}","gists_url":"https://api.github.com/users/danielballan/gists{/gist_id}","starred_url":"https://api.github.com/users/danielballan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danielballan/subscriptions","organizations_url":"https://api.github.com/users/danielballan/orgs","repos_url":"https://api.github.com/users/danielballan/repos","events_url":"https://api.github.com/users/danielballan/events{/privacy}","received_events_url":"https://api.github.com/users/danielballan/received_events","type":"User","site_admin":false},"created_at":"2015-10-26T23:04:21Z","updated_at":"2015-10-26T23:04:21Z","body":"My take: this is an education issue. CSX scientists have not interacted much with the object-oriented API, where users are expected to manage configuration on individual objects, not through global state.\r\n\r\nWe added the set/unset functions so we could imitate the signatures of SPEC commands, which include a `time`. Via this convenient but restricted API, it isn't possible to set a variety of times or address a detector like AreaDetector which needs multiple settings to be fully defined.\r\n\r\nGiven the ongoing confusion (this isn't the first time) I am tempted to remove the all-purpose `time` entirely. It is too blunt an instrument. SPEC was written before area detectors -- we work in a more complicated world and we need more complicated APIs. :- )"}}