style: pre-commit fixes

legend-exp · Mar 11, 2024 · d4e594d · d4e594d
1 parent 1ec57ad
commit d4e594d
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 6 deletions.
diff --git a/docs/source/manuals/avail_pars.rst b/docs/source/manuals/avail_pars.rst
@@ -46,9 +46,9 @@ Available parameters
 
 .. warning::
 
-  It has been found out that no muon signals were being recorded in the auxiliary channel MUON01 for periods p08 and p09 (up to r003 included). 
+  It has been found out that no muon signals were being recorded in the auxiliary channel MUON01 for periods p08 and p09 (up to r003 included).
   This means the present code is not able to flag the germanium events for which there was a muon crossing the experiment.
-  In other words, the dataframe associated to the ``muon`` events here will be empty. 
+  In other words, the dataframe associated to the ``muon`` events here will be empty.
   Moreover, if you select ``phy`` entries, these will still contain muons since the cut over this does not work.
 
 

diff --git a/docs/source/manuals/get_sc_plots.rst b/docs/source/manuals/get_sc_plots.rst
@@ -56,7 +56,7 @@ An example of a config.json file is the following:
 The meaning of each entry is explained below:
 
 * ``output``: foldeer where to store output files;
-* ``dataset``: 
+* ``dataset``:
 
     * ``experiment``: either *L60* (to be checked) or *L200*
     * ``period``: period to inspect
@@ -97,4 +97,3 @@ We store SC data in the following way:
   - if ``{'timestamps': ['20230207T103123Z', '20230207T141123Z', '20230207T083323Z']}`` (multiple keys), then <time_selection> = ``20230207T083323Z_20230207T141123Z`` (min/max timestamp interval)
   - if ``{'runs': 1}`` (one run), then <time_selection> = ``r001``;
   - if ``{'runs': [1, 2, 3]}`` (multiple runs), then <time_selection> = ``r001_r002_r003``.
-
diff --git a/docs/source/manuals/inspect_plots.rst b/docs/source/manuals/inspect_plots.rst
@@ -11,7 +11,7 @@ the last two files are created for each inspected subsystem (pulser, geds, spms)
 .. warning::
 
   Shelve files are produced as an output as well, this was the first format chosen for the output.
-  The code still has to be fixed to remove these files from routines. 
+  The code still has to be fixed to remove these files from routines.
   At the moment, they are important when using the ``"saving": "append"`` option, so do not remove them if you are going to use it!
 
 Files are usually collected in the output folder specified in the ``output`` config entry:
@@ -81,5 +81,5 @@ Output hdf files for ``geds`` have the following dictionary structure, where ``<
 Inspect plots
 -------------
 
-- Some standard plots to monitor detectors' response can be found online on the `Dashboard <https://legend-exp.atlassian.net/wiki/spaces/LEGEND/pages/637861889/Monitoring+Dashboard+Manual>`_ 
+- Some standard plots to monitor detectors' response can be found online on the `Dashboard <https://legend-exp.atlassian.net/wiki/spaces/LEGEND/pages/637861889/Monitoring+Dashboard+Manual>`_
 - Some notebooks to interactively inspect plots can be found under the ``notebook`` folder