From 497c21563e75a4a004d5c6a49186cf94c6e75441 Mon Sep 17 00:00:00 2001 From: Ben Dichter Date: Tue, 11 May 2021 16:41:13 -0400 Subject: [PATCH] Add `DfOverF` to docs (#1351) Co-authored-by: Ryan Ly --- docs/gallery/domain/ophys.py | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/gallery/domain/ophys.py b/docs/gallery/domain/ophys.py index dc9ace87c..37d279908 100644 --- a/docs/gallery/domain/ophys.py +++ b/docs/gallery/domain/ophys.py @@ -133,6 +133,10 @@ #################### +# .. tip:: +# You can also store dF/F data using the :py:class:`~pynwb.ophys.DfOverF` class, which works the same way as +# :py:class:`~pynwb.ophys.Fluorescence`. +# # Because this data stores information about specific ROIs, you will need to provide a reference to the ROIs # that you will be storing data for. This is done using a :py:class:`~pynwb.core.DynamicTableRegion`, which can be # created with :py:func:`~pynwb.ophys.PlaneSegmentation.create_roi_table_region`. @@ -227,8 +231,6 @@ # one's life much simpler. NWB currently does not have the ability to read and parse native image formats. It # is up to downstream users to read these file formats. # -# .. [#] You can also store dF/F data using the :py:class:`~pynwb.ophys.DfOverF` class. -# # .. [#] Neurodata sets can be *very* large, so individual components of the dataset are only loaded into memory when # you request them. This functionality is only possible if closing of the :py:class:`~pynwb.NWBHDF5IO` # object is handled by the user.