You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unit tests for makers, container and component modules (part 1/X) (#163)
* add arg to load only wfs and do not extract charges
* cleaner way to treat containers inside makers
* new methods to find computed calibration quatities
ds to find computed calibration quatities
* update to support new version of EvB v6
* -bug fix SPE combined : method use to update parameters was not the wanted one
-update pp and n values to last studies
-display wfs -> mean instead of sum
-Agg backend is not forced in Pstat calibnration
* add find photostat result method
* user scripts
* add workflow_display to CI
* change tests name in user_scripts which is not a test for pytest
* fix import errors in TRR
exluse user_scripts to pytest
* bugfix : logger
improvement split_run method
* static method decorator were missing
* bugfix test containers
* unit test fore nectarchain.makers .core
* bugfix with new version of LIghtNectarCAMEventSource from ctapipe_io_nectarcam
* very small code improvement
* Unit test for WaveformsNectarCAMCalibrationTool
* Unit test for the ChargesNectarCAMCalibrationTool
* formatting
* fix test core makers
* flake8 formatting
* refactoring following pep8
* continue refactoring
* dqm flake8
* refactoring containers
* fix bug formatting
* shitty python formatting
* test bugfix
* pedestal maker : implementation of I/O with containers
* remove LightNectarCamEventSource
* bugfix in toml file introduced in previous commits
* bugfix : __init__ file in tests repertory
* pytest don't like to have 2 test files with same names
* specific noqa for unused imports
---------
Co-authored-by: guillaume.grolleron <[email protected]>
Copy file name to clipboardExpand all lines: docs/user-guide/env-vars.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ However, some environment variables are needed for ``nectarchain`` to work prope
9
9
Mandatory
10
10
---------
11
11
12
-
:``NECTARCAMDATA``: path to local NectarCAM data. It can contain ``fits.fz`` run files, `~nectarchain.data.container.waveformsContainer.WaveformsContainer` or `~nectarchain.data.container.chargesContainer.ChargesContainer` HDF5 files. This is also where the `~nectarchain.data.management.DataManagement.findrun` method will automatically store NectarCAM run files when fetched from DIRAC.
12
+
:``NECTARCAMDATA``: path to local NectarCAM data. It can contain ``fits.fz`` run files, `~nectarchain.data.container.waveforms_container.WaveformsContainer` or `~nectarchain.data.container.charges_container.ChargesContainer` HDF5 files. This is also where the `~nectarchain.data.management.DataManagement.findrun` method will automatically store NectarCAM run files when fetched from DIRAC.
The data can be filtered based on time using the ``ucts_tmin`` and
30
30
``ucts_tmax`` parameters and to eliminate outlier waveforms using the ``filter_method`` parameter. Two different methods to exclude outlier
31
31
waveforms are implemented:
@@ -46,11 +46,11 @@ To run the example script:
46
46
Inspect the results
47
47
=========================
48
48
The results are stored in a
49
-
`~nectarchain.data.container.pedestalContainer.NectarCAMPedestalContainer`. The
49
+
`~nectarchain.data.container.pedestal_container.NectarCAMPedestalContainer`. The
50
50
results include information on pixels that were flagged as having
51
51
an abnormal behavior during the computation of the pedestals. The
52
52
flags are defined in in
53
-
`~nectarchain.data.container.pedestalContainer.PedestalFlagBits`. The
53
+
`~nectarchain.data.container.pedestal_container.PedestalFlagBits`. The
54
54
results are accessible on the fly if the tool is run interactively (as in the example above) and stored in a `.h5` file.
55
55
56
56
The user script `nectarchain/user_scripts/ltibaldo/show_pedestal_output.py` provides an example of how to access the results from disk and produce some plots:
0 commit comments