================================================================================
README FOR SHIFTERS - Station 35, Runs: [260000, 260001, 260002, 260003, 260004, 260005, 260006, 260007, 260008, 260009, 260010, 260011, 260012, 260013, 260014, 260015, 260016, 260017, 260018, 260019, 260020, 260021, 260022, 260023, 260024, 260025, 260026, 260027, 260028, 260029, 260030, 260031, 260032, 260033, 260034, 260035, 260036, 260037, 260038, 260039, 260040, 260041, 260042, 260043, 260044, 260045, 260046, 260047, 260048, 260049, 260050, 260051, 260052, 260053, 260054, 260055, 260056, 260057, 260058, 260059, 260060, 260061, 260062, 260063, 260064, 260065, 260066, 260067, 260068, 260069, 260070, 260071, 260072, 260073, 260074, 260075, 260076, 260077, 260078, 260079, 260080, 260081, 260082, 260083, 260084, 260085, 260086, 260087, 260088, 260089, 260090, 260091, 260092, 260093, 260094, 260095, 260096, 260097, 260098, 260099, 260100, 260101, 260102, 260103, 260104, 260105, 260106, 260107]
Time Range: 2026-08-18T09:06:25 to 2026-08-24T17:28:35
================================================================================

IMPORTANT: This README is intended for shifters to understand the results of
the channel health analysis. Please read it carefully before interpreting the
results.

This directory contains the results of the channel health analysis for
station 35 over the specified runs. The analysis includes spectral
analysis, SNR analysis, Vrms analysis, glitching and block offset analysis
(for RADIANT digitizer type), and generates various plots and summary files,
which will be explained below.

WHAT TO DO AS A SHIFTER
--------------------------------------------------------------------------------
1. Check the Summary CSV File

   The summary CSV file (channel_health_summary.csv) contains the overall
   health status of each channel based on the various tests performed. The
   columns indicate the results of each test:
       X   - Test failed with serious deviation from the expected behavior.
       !!  - Test failed with minor deviation from the expected behavior.
       OK  - Channel passed the test.
   The overall channel health is determined based on the results of the
   FORCE trigger tests, and is given in the column "Channel Health (FORCE)".
   This combines the results of the SNR, Galaxy, Vrms stability, and Vrms
   modality tests for the FORCE trigger (glitching as well for stations with
   RADIANT digitizer type - 11, 12, 13, 14, 21, 22, 23, 24).
   If a channel fails any of these tests, it is marked as "X" in the overall
   health column. If it passes all tests, it is marked as "OK". If it has
   minor issues, it may be marked as "!!".
   YOU CAN CHECK THE "Channel Health (FORCE)" COLUMN FIRST TO QUICKLY IDENTIFY
   CHANNELS THAT NEED ATTENTION AND INVESTIGATE INDIVIDUAL TEST COLUMNS IF
   NEEDED.

2. Look at the Standard Plots

   The standard plots (plots/standard_plots/) are always produced, regardless
   of whether any channel failed a test. They give a quick visual overview of
   the station's behavior for the time period: normalized/unnormalized
   surface and deep spectra, SNR vs. time, Vrms vs. time, and trigger rates
   over time. It's a good idea to skim these even if the summary CSV shows
   all channels as "OK".

3. Investigate Flagged Channels

   If the summary CSV flags a channel as "X" or "!!", check
   plots/failed_test_plots/ and test_results/failed_test_results/ first:
   these directories only get populated for tests that failed for at least
   one channel (e.g. SNR/z-score distributions, galaxy ratio distributions,
   Vrms distributions with the modality fit, glitching, block offsets), so
   you can go straight to the relevant plot/report for the failing test.
   If a test passed for all channels, its plots and detailed numbers are
   still saved (nothing is discarded), just under plots/detailed_plots/ and
   test_results/detailed_results/ instead.

4. Always Check the Failed-Runs File

   If any of the requested runs could not be read (missing/corrupt files,
   invalid timestamps, or runs you excluded with -ex/--exclude-runs), they
   are listed with a reason in
   test_results/station35_failed_runs_in_runrange_runs_260000_260107.csv.
   This file is only created when at least one run failed, but you should
   always check for its presence, as it means the analysis is based on fewer
   runs than requested and might indicate issues with the data.

5. Check the Log File

   The log file
   (logs/logging_science_verification_analysis_station35_runs_260000_260107.log)
   records warnings about missing/invalid runs, low event counts, and
   borderline channels that may not be fully captured by the summary CSV.

6. Report on the Monday Call

   If you are a shifter, please report any channels that are flagged as "X"
   or "!!" in the summary CSV, and any runs that failed to be read, on the
   Monday shifter call. This helps the station experts and data quality team
   to investigate and address any issues.

If you are unsure how to interpret a result, or a channel's health looks
suspicious, please reach out to Zeynep Su Selcuk (zeynep.su.selcuk@desy.de).