27832514520
65%

Ran 19 Jun 2026 02:48PM UTC

Jobs 1

Files 27

Run time 1min

Badge

Embed ▾

Committed 19 Jun 2026 02:46PM UTC coverage: 55.83%. Remained the same

Build # 27832514520

Build Type

push

github

Committed by

prjemian

Commit Message

docs: explain flyscan extra-frame count and paired-data HDF5 layout

Beam line reported flyscans consistently writing 306 frames when 301
were requested (omega -30..+30, 5 exposures/egu).  This is expected:
the cam runs continuous and captures a few pre-roll (before motor
launch) and post-stop tail frames around the useful window; the raw
HDF5 is a superset.  The useful 301 are selected and paired with omega
positions downstream and written into the NeXus master file.

Add explanation/flyscan_frame_count.md describing the frame-count
formula, where the extras come from, and -- early, per request -- where
to find the paired frames/positions in the master file
(/entry/positions, /entry/flyscan_data, /entry/images).  Add a
keep-in-sync note pointing at update_master_file and the geometry,
pre-roll, tail, over-allocation, and pairing code.  Add a matching
sync pointer comment at the hdf_num_capture allocation.

Coverage Stats

1221 of 2187 relevant lines covered (55.83%)

0.56 hits per line

Coverage Regressions

Lines	Coverage	∆	File
1	17.89	0.0%	src/id3c/plans/flyscan_3idc.py

Jobs

ID	Job ID	Ran	Files	Coverage
1	3.11 - 27832514520.1	19 Jun 2026 02:48PM UTC	27	55.83	GitHub Action Run

BCDA-APS / 3idc-bits / 27832514520
65%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Coverage Regressions

Jobs

Source Files on build 27832514520

BCDA-APS / 3idc-bits / 27832514520 65%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Coverage Regressions

Jobs

Source Files on build 27832514520

BCDA-APS / 3idc-bits / 27832514520
65%

README BADGES
x