Binary core API - Revision history

HudecekP: /* Data-driven special settings */

2026-04-16T15:29:20Z

Data-driven special settings

← Older revision		Revision as of 17:29, 16 April 2026
Line 3,942:		Line 3,942:
	Received data is continuously stored to the buffer.		Received data is continuously stored to the buffer.
	* Every reaching next block, the callback New data occurs or data saved to file.		* Every reaching next block, the callback New data occurs or data saved to file.
	* At a low event rate, the callback is also called regularly, e.g. 500 ms on MiniPIX, or 1,7 s ~~on AdvaPIX~~.		* At a low event rate, the callback is also called regularly, e.g. 500 ms on MiniPIX, or more on AdvaPIX (1.7 s with defaults).
	* When the buffer runs out, the measurement ends with an error.		* When the buffer runs out, the measurement ends with an error.
	* If file saving is used, data is not accumulated in the buffer, callbacks do not occur, the buffer never runs out and measurement may by very long.		* If file saving is used, data is not accumulated in the buffer, callbacks do not occur, the buffer never runs out and measurement may by very long.

HudecekP: /* Data-driven special settings */

2026-04-16T12:02:59Z

Data-driven special settings

← Older revision		Revision as of 14:02, 16 April 2026
Line 3,935:		Line 3,935:
	== Data-driven special settings ==		== Data-driven special settings ==
	{\|		{\|
	\|-		\|- style="vertical-align:top;"
	\|		\| <br>
	The Pixet core has a circular buffer in memory to receiving new pixels.		The Pixet core has a circular buffer in memory to receiving new pixels.
	* Size of whole buffer is named '''buffer size'''.		* Size of whole buffer is named '''buffer size'''.

HudecekP: /* Data-driven special settings */

2026-04-16T12:00:07Z

Data-driven special settings

HudecekP: /* Data-driven special settings */

2026-04-16T11:08:59Z

Data-driven special settings

← Older revision		Revision as of 13:08, 16 April 2026
Line 3,963:		Line 3,963:
	\| '''DDDummyDataSpeed'''<br>Virtual data speed of dummy device \|\| (has no) \|\| 24831		\| '''DDDummyDataSpeed'''<br>Virtual data speed of dummy device \|\| (has no) \|\| 24831
	\|-		\|-
	\| '''DataOverflowCheck'''<br>If overflow occurs and check is on, measurement ~~immediatelly end~~ with error. If off, overflow indicated in data and measuring to normal end. \|\| [bool] \|\| (has no)		\| '''DataOverflowCheck'''<br>If overflow occurs and check is on, measurement immediately ends with error. If off, overflow indicated in data and measuring to normal end. \|\| [bool] \|\| (has no)
	\|}		\|}
	\|}		\|}

HudecekP: /* Data-driven special settings */

2026-04-16T09:24:18Z

Data-driven special settings

← Older revision		Revision as of 11:24, 16 April 2026
Line 3,942:		Line 3,942:
	Received data is continuously stored to the buffer.		Received data is continuously stored to the buffer.
	* Every reaching next block, the callback New data occurs.		* Every reaching next block, the callback New data occurs.
	* At a low event rate, the callback is also called regularly, e.g. 500 ms on ~~Minipix~~.		* At a low event rate, the callback is also called regularly, e.g. 500 ms on MiniPIX, or 1,7 s on AdvaPIX.
	* When the buffer runs out, the measurement ends with an error.		* When the buffer runs out, the measurement ends with an error.
	* If file saving is used, data is not accumulated in the buffer, callbacks do not occur, the buffer never runs out and measurement may by very long.		* If file saving is used, data is not accumulated in the buffer, callbacks do not occur, the buffer never runs out and measurement may by very long.
Line 3,962:		Line 3,962:
	\|-		\|-
	\| '''DDDummyDataSpeed'''<br>Virtual data speed of dummy device \|\| (has no) \|\| 24831		\| '''DDDummyDataSpeed'''<br>Virtual data speed of dummy device \|\| (has no) \|\| 24831
			\|-
			\| '''DataOverflowCheck'''<br>If overflow occurs and check is on, measurement immediatelly end with error. If off, overflow indicated in data and measuring to normal end. \|\| [bool] \|\| (has no)
	\|}		\|}
	\|}		\|}

HudecekP: /* Data-driven special settings */

2026-04-15T12:07:30Z

Data-driven special settings

← Older revision		Revision as of 14:07, 15 April 2026
Line 3,959:		Line 3,959:
	\| '''DDBlockSize'''<br>Size of each block \|\| [B]<br>default 66000 \|\| [MB]<br>default 5		\| '''DDBlockSize'''<br>Size of each block \|\| [B]<br>default 66000 \|\| [MB]<br>default 5
	\|-		\|-
	\| '''~~DDBlockSizeDivider~~'''<br>Unit divider for smaller blocks on AdvaPIX \|\| (has no) \|\| [/MB]<br>default 1		\| '''DDBlockDivider'''<br>Unit divider for smaller blocks on AdvaPIX \|\| (has no) \|\| [/MB]<br>default 1
	\|-		\|-
	\| '''DDDummyDataSpeed'''<br>Virtual data speed of dummy device \|\| (has no) \|\| 24831		\| '''DDDummyDataSpeed'''<br>Virtual data speed of dummy device \|\| (has no) \|\| 24831

HudecekP: /* DD functions list */

2026-04-14T08:22:22Z

DD functions list

← Older revision		Revision as of 10:22, 14 April 2026
Line 3,997:		Line 3,997:
	\| deviceIndex – index of the device, starting from zero		\| deviceIndex – index of the device, starting from zero
	\| measTime – the total time of the measurement in seconds. Use 0 for infinite.		\| measTime – the total time of the measurement in seconds. Use 0 for infinite.
	\| filename – output file name and path (extensions must ~~end~~ .t3pa, .~~trp~~, *.t3r)		\| filename – output file name and path (extensions must be .t3pa, .t3p, *.t3r)
	\| trgStg – settings of external trigger - one of the PXC_TRG_XXX values. Default PXC_TRG_NO		\| trgStg – settings of external trigger - one of the PXC_TRG_XXX values. Default PXC_TRG_NO
	\| callback – pointer to function of acqEventFunc type		\| callback – pointer to function of acqEventFunc type

HudecekP: /* Pixel matrix and masks management */

2026-04-13T12:14:27Z

Pixel matrix and masks management

@@ Line 2,731: / Line 2,731: @@
 | War =
 | Exa =
 }}

HudecekP: /* Multi-frame and data-driven with callback */

2026-04-07T14:00:24Z

Multi-frame and data-driven with callback

@@ Line 920: / Line 920: @@
 === Multi-frame and data-driven with callback ===
 See:
 * [[Binary_core_API#Multiple_frames_using_callbacks|#Multiple frames using callbacks]]
@@ Line 1,161: / Line 1,156: @@
 </syntaxhighlight>
 </div></div>
 === Beam-hardenning correction ===

HudecekP: /* Data-driven special settings */

2026-04-07T10:59:19Z

Data-driven special settings

← Older revision		Revision as of 12:59, 7 April 2026
Line 3,834:		Line 3,834:

	== Data-driven special settings ==		== Data-driven special settings ==
			{\|
			\|-
			\|
	The Pixet core has a circular buffer in memory to receiving new pixels.		The Pixet core has a circular buffer in memory to receiving new pixels.
	* Size of buffer is named '''buffer size'''.		* Size of buffer is named '''buffer size'''.
Line 3,842:		Line 3,845:
	* When the buffer runs out, the measurement ends with an error.		* When the buffer runs out, the measurement ends with an error.
	* If file saving is used, data is not accumulated in the buffer, callbacks do not occur, the buffer never runs out and measurement may by very long.		* If file saving is used, data is not accumulated in the buffer, callbacks do not occur, the buffer never runs out and measurement may by very long.

			Default values are optimized for maximum performance on developper's computer. Normally, it is enough to leave these values, but it is possible that by changing them you will speed up the measurement a little or reduce the CPU load on Your computer.

			See: [[Binary_core_API#pxcSetDeviceParameter\|'''pxcSetDeviceParameter''']], [[Binary_core_API#pxcGetDeviceParameter\|'''pxcGetDeviceParameter''']]
			\|
	{\| class="wikitable"		{\| class="wikitable"
	\|+ DD settings in named (readout) parameters		\|+ DD settings in named (readout) parameters
Line 3,855:		Line 3,863:
	\| '''DDDummyDataSpeed'''<br>Virtual data speed of dummy device \|\| (has no) \|\| 24831		\| '''DDDummyDataSpeed'''<br>Virtual data speed of dummy device \|\| (has no) \|\| 24831
	\|}		\|}
	Default values are optimized for maximum performance on developper's computer. Normally, it is enough to leave these values, but it is possible that by changing them you will speed up the measurement a little or reduce the CPU load on Your computer.		\|}

	~~See: [[Binary_core_API#pxcSetDeviceParameter~~\|~~'''pxcSetDeviceParameter''']], [[Binary_core_API#pxcGetDeviceParameter\|'''pxcGetDeviceParameter''']]~~

	== Data-driven basic measurement flow ==		== Data-driven basic measurement flow ==

← Older revision		Revision as of 14:00, 16 April 2026
Line 3,938:		Line 3,938:
	\|		\|
	The Pixet core has a circular buffer in memory to receiving new pixels.		The Pixet core has a circular buffer in memory to receiving new pixels.
	* Size of buffer is named '''buffer size'''.		* Size of whole buffer is named '''buffer size'''.
	* Buffer is divided to blocks with '''block size'''.		* Buffer is divided to blocks with '''block size'''.
	Received data is continuously stored to the buffer.		Received data is continuously stored to the buffer.
	* Every reaching next block, the callback New data occurs.		* Every reaching next block, the callback New data occurs or data saved to file.
	* At a low event rate, the callback is also called regularly, e.g. 500 ms on MiniPIX, or 1,7 s on AdvaPIX.		* At a low event rate, the callback is also called regularly, e.g. 500 ms on MiniPIX, or 1,7 s on AdvaPIX.
	* When the buffer runs out, the measurement ends with an error.		* When the buffer runs out, the measurement ends with an error.
Line 3,959:		Line 3,959:
	\| '''DDBlockSize'''<br>Size of each block \|\| [B]<br>default 66000 \|\| [MB]<br>default 5		\| '''DDBlockSize'''<br>Size of each block \|\| [B]<br>default 66000 \|\| [MB]<br>default 5
	\|-		\|-
	\| '''DDBlockDivider'''<br>Unit divider for smaller blocks on AdvaPIX \|\| (has no) \|\| [/MB]<br>default 1		\| '''DDBlockDivider'''<br>Unit divider for smaller blocks on AdvaPIX<br>Divider can shorten the timeout downto ~500 ms. \|\| (has no) \|\| [/MB]<br>default 1
	\|-		\|-
	\| '''DDDummyDataSpeed'''<br>Virtual data speed of dummy device \|\| (has no) \|\| 24831		\| '''DDDummyDataSpeed'''<br>Virtual data speed of dummy device \|\| (has no) \|\| 24831
	\|-		\|-
	\| '''DataOverflowCheck'''<br>If overflow occurs and check is on, measurement immediately ~~ends~~ with error. If off, overflow ~~indicated~~ in data and ~~measuring~~ to normal end. \|\| [bool] \|\| (has no)		\| '''DataOverflowCheck'''<br>If an overflow occurs and the check is on, the measurement is immediately terminated with an error. If it is off, the overflow is displayed in the data and the measurement continues to the normal end. \|\| [bool]<br>default 0 \|\| (has no)
			\|-
			\| '''BlockCount'''<br>Count of occupied blocks after measurement.<br>(zeroed at start and updated at the end of the measurement) \|\| (has no) \|\| (read)
	\|}		\|}
	\|}		\|}