There is some confusion about the axes along which the data is stored in TDMS files, ie is it
A) x and then y, or
B) pixels_per_line and then lines.
Note that these are equivalent in all our current test data bar the variable ROI one (200228_14_15_57), as the angle is 0 in all these samples.
One the one hand, in the docstring of read_functional_data, it says
"""... Within this array, we have data first for all pixels in the first ROI at time 0,
then the second ROI at time 0, and so on through all ROIs, before moving to
data from the next cycle. For 2d ROIs, it scans first over the X dimension then
over Y."""
which suggests A)
On the other hand, in order to match the MatLab fluorescence data for Lena's example (200228_14_15_57), the only way we managed is by assuming B)
My suspicion is that B) is correct, but best to double-check.
There is some confusion about the axes along which the data is stored in TDMS files, ie is it
x
and theny
, orpixels_per_line
and thenlines
.Note that these are equivalent in all our current test data bar the variable ROI one (
200228_14_15_57
), as the angle is 0 in all these samples.One the one hand, in the docstring of
read_functional_data
, it sayswhich suggests A)
On the other hand, in order to match the MatLab fluorescence data for Lena's example (
200228_14_15_57
), the only way we managed is by assuming B)My suspicion is that B) is correct, but best to double-check.