New pages
Jump to navigation
Jump to search
- 15:24, 30 April 2025 Read result() (hist | edit) [2,305 bytes] Franz Hempel (talk | contribs) (Created page with "After the <code>measure()</code> function has triggered the data acquisition process, <code>request_result()</code> is called to query the results, which are retrieved by <code>read_result()</code> in the next step. === Functionality === Within the concept of unblocking parallelization, the methods <code>request_result()</code> and <code>read_result()</code> are designed to improve measurement efficiency by allowing instruments to operate concurrently. * <...")
- 16:01, 24 March 2025 Request result() (hist | edit) [2,319 bytes] Franz Hempel (talk | contribs) (Created page with "The <code>request_result()</code> function in SweepMe! is responsible for checking if the data from a measurement is ready after it has been triggered by the <code>measure()</code> function. It does not trigger the measurement but queries the results. This separation of concerns allows for efficient parallel processing of multiple measurements. === Functionality === * '''Wait for finished measurement''' If the measurement is expected to take extended time, a function...")
- 15:47, 24 March 2025 Measure() (hist | edit) [1,002 bytes] Franz Hempel (talk | contribs) (Created page with "== measure() == The `measure()` function in SweepMe! is used to trigger the acquisition of new data from an instrument. It is designed to initiate a measurement without waiting for the data to be ready. This non-blocking behavior allows multiple devices to be triggered in parallel, improving measurement efficiency. === Complementary Function - request_result() === The request_result() and read_result() functions work in conjunction with Measure (). While `Meas...")