Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User group, tcspc offset and markers #46

Open
wants to merge 7 commits into
base: 0.5.dev
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -64,9 +64,9 @@
# built documents.
#
# The short X.Y version.
version = '0.4'
version = '0.5'
# The full version, including alpha/beta/rc tags.
release = '0.4'
release = '0.5'

# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
Expand Down
15 changes: 9 additions & 6 deletions docs/generic.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,9 @@ For measurement types which cannot be described by any other
it is possible to use the "generic" type and use the ``/setup``
fields to describe the exact configuration.

The "generic" type is the encouraged type for most experiments
going forward, as it supports arbitrary configurations.


Examples
--------
Expand All @@ -25,8 +28,8 @@ A setup detecting two polarizations in the detection path will be defined by::
and will also specify the detector used for each polarizations::

/photon_data/measurement_specs/detectors_specs/
polarization_ch1 = 0
polarization_ch2 = 1
polarization_ch1 = [0, ]
polarization_ch2 = [1, ]

(where the values 0 and 1 are only examples). In addition ``/setup/lifetime``
will indicate whether the measurement has TCSPC data or not. Finally, the optional field
Expand All @@ -46,8 +49,8 @@ in two using a non-polarizing beam splitter will be defined by::
and the measurement_specs will contain::

/photon_data/measurement_specs/detectors_specs/
split_ch1 = 0
split_ch2 = 1
split_ch1 = [0, ]
split_ch2 = [1, ]

(where the values 0 and 1 are only examples). In addition ``/setup/lifetime``
will indicate whether the measurement has TCSPC data or not. Finally, the optional
Expand All @@ -74,8 +77,8 @@ as in the "smFRET" ``measurement_type``. In particular::
and::

/photon_data/measurement_specs/detectors_specs/
spectral_ch1 = 0
spectral_ch2 = 1
spectral_ch1 = [0, ]
spectral_ch2 = [1, ]

TCSPC measurements
^^^^^^^^^^^^^^^^^^
Expand Down
2 changes: 1 addition & 1 deletion docs/limitations.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ please contact us.
Timestamps with rollover
------------------------

In Photon-HDF5 timestamps are always signed 64 bit integers. Thanks to
In Photon-HDF5 timestamps are usually signed 64 bit integers. Thanks to
compression, there is no size penalty compared to 32 bit integers. Most
timestamping hardware produce a timestamp with 24 or 32 bits
and a rollover flag in order to compute the full "unwrapped" timestamp.
Expand Down
Loading