bluesky suitcase-specfile issues

bluesky / suitcase-specfile

write text file such as output by SPEC

Other

0 stars 8 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

v0.2.5. release notes

#22 gwbischof closed 2 years ago
0
Fix versioneer compat with py311

#21 tacaswell closed 2 years ago
0
Added workflow to publish to pypi

#20 MikeHart85 closed 2 years ago
0
Release notes for v0.2.4

#19 MikeHart85 closed 2 years ago
0
Multiple motors

#18 whs92 opened 3 years ago
0
Corrected SPEC header formation from bluesky start doc

#17 whs92 closed 2 years ago
5
_get_motor_name(start) returns 'seq_num' rather than motor name

#16 whs92 opened 3 years ago
0
Migrate from Travis-CI to GitHub Actions

#15 danielballan opened 3 years ago
0
Stop using special ophyd branch in test requirements.

#14 danielballan closed 3 years ago
0
DOC: Centralize documentation.md

#13 ke-zhang-rd opened 4 years ago
0
Write scan headers for each scan.

#12 danielballan closed 4 years ago
0
Do not mutate input data.

#11 danielballan closed 4 years ago
0
Accept stop documents with no 'reason'.

#10 danielballan closed 4 years ago
1
Test fixture update

#9 jklynch closed 4 years ago
0
compare with similar callback at APS

#8 prjemian opened 4 years ago
1
Resolve file mode issue from CHX

#7 danielballan opened 4 years ago
1
ENH: flush after each event and on stop

#6 tacaswell closed 4 years ago
5
updating to the new `file_prefix` API

#5 awalter-bnl closed 5 years ago
0
FIX: fix ophyd branch for testing; add readme content type

#4 mrakitin closed 5 years ago
0
Update requirements.txt to resolve a typo

#3 awalter-bnl closed 5 years ago
0
Change YY-->YYYY to be consistent with other repos

#2 mrakitin closed 5 years ago
0
Use f-strings instead of jinja2

#1 danielballan opened 5 years ago
0