-
Notifications
You must be signed in to change notification settings - Fork 0
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
Updates needed to run on-site #86
Comments
To be clear -- do you mean The ACU agent now has a notion of "default" scan params; those can be tweaked through set_scan_params. So nextline (or whatever) scripts could use that, at the top, to set the defaults. (Then, the defaults are a scheduler config thing, instead of a sorunlib config thing.) And it is easy to change the scan params, for a bunch of scans in a row, by adding one line to a script. |
I guess meant that since Yes to configurable in a config file in the future but right now I'd like like to be able to call the function at all. |
What's the ACU's default behavior, say if you haven't called |
Answered offline :) Agent default defaults, on startup, are here. |
Addressed in #88.
Addressed in #87.
This one requires some coordination with the scheduler. I'd still like the final script syntax to end up looking like:
Or something similar. Do we shift to just starting the scan in the middle then? This would mean instead we'd have:
And the first part of the scan would be moving towards the start point, then actually scanning. Alternatively the scripts move to a slightly more verbose:
And |
I think az - width/2 to az + width/2 would make the convention consistent with the scan parameters returned in the obsdb obsinfo. Keeping those consistent I think will prevent confusion. |
acu.generate_scan
accepts anaz_speed
andaz_accel
those need to be configurable (and the defaults should be 1 deg/s and 1 deg/s**2.)seq.scan
already assumes we're at a starting point whileacu.generate_scan
is happy to move us to the starting point. It'd be good to be able to look at the middle of the scan for detector setup and then move to the edge, especially when the edge is close to the sunsmurf.stream
needs to acceptsubtype
as well astag
andseq.scan
needs to pass those along.The text was updated successfully, but these errors were encountered: