Dan Allan

Results 394 issues of Dan Allan

https://travis-ci.org/github/bluesky/bluesky/jobs/689702588 ``` _______________________________ test_simple_fly ________________________________ RE = hw = namespace(ab_det=ABDetector(prefix='', name='det', read_attrs=['a', 'b'], configuration_attrs=[]), bool_sig=Signal(nam...name='signal', value=0, timestamp=1590076825.2563176), trivial_flyer=) def test_simple_fly(RE, hw): hw.flyer1.loop = RE.loop RE(fly_gen(hw.flyer1)) > assert hw.flyer1._future.done() E AttributeError:...

Copied from the Nikea Slack: > The concern about running bluesky in Jupyter for real experiments (as opposed to teaching/training/simulation with synthetic data) is two-fold: > 1. Since notebooks allow...

In the built-in plans and in high-quality user-written plans, we use and encourage the pattern: ```py def my_plan(detectors, a, b, c=some_default, md=None): _md = { 'detectors': [det.name for det in...

documentation
user IO

Every other preprocessor has a decorator form, including its cousin finalize_decorator. I believe we added this in a rush and just forgot to make a decorator-based one. Provisionally assigning to...

The `contingency_wrapper` is better than the `finalize_wrapper` because the "final plan" takes in the exception that was raised as the argument, which allows the clean up to target specific failure...

good first issue
hackathon

Just as we currently have a simulator to check whether a plan will exceed motor limits, it would be useful to have simulator to estimate the required storage for a...

good first issue
hackathon

The suspender docstrings provide a type for `pre_plan` and `post_plan` that confused one of our more software-savvy beamline staff and I think could be improved. We describe them as "an...

documentation
suspenders

This PR added a `Bundler` class but has no docstrings or API docs https://github.com/bluesky/bluesky/pull/1248.

documentation

A conversation in the Nikea ophd Slack channel resurfaced some old ideas that I thought might be worth writing down. I am not advocating to _do_ anything, I just want...

The tests under the [`bluesky/tests/interactive` directory](https://github.com/NSLS-II/bluesky/tree/master/bluesky/tests/interactive) are intended to be checked via a human, but there's no reason we can't at least check that they _run_ in the CI tests...

maintenance
design-discussion