RNO-G Data Tools issueshttps://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues2021-09-06T16:00:12+02:00https://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/14Classes of noise events seen in all channels2021-09-06T16:00:12+02:00Steffen HallmannClasses of noise events seen in all channelsSome very sinusoidal events are visible in station 21 / runs 450-460, with no indication of a special run being taken from the run config comments. Frequencies of these groups (level of higher, similar RMS; bursts) of events with similar...Some very sinusoidal events are visible in station 21 / runs 450-460, with no indication of a special run being taken from the run config comments. Frequencies of these groups (level of higher, similar RMS; bursts) of events with similar behaviour are ~123 MHz and ~144&152MHz
![Screenshot_2021-09-06_at_14.18.20](/uploads/9268180e6bdf7afa53eddc0bc26f7da8/Screenshot_2021-09-06_at_14.18.20.png)
![Screenshot_2021-09-06_at_14.08.53](/uploads/4e9aa668a94ce1bd49d1f155dea9de5b/Screenshot_2021-09-06_at_14.08.53.png)
![Screenshot_2021-09-06_at_14.10.57](/uploads/817334af341803e04263415f6c9a4199/Screenshot_2021-09-06_at_14.10.57.png)https://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/13Duplicated event numbers2021-09-06T15:42:59+02:00Steffen HallmannDuplicated event numbersSome of the event numbers appear twice with no obvious reason, traces/event times are different.
Example in combined.root: Station 21 / Run 455 / Event Number 1212
In the headers.root, there are several of these events per run.Some of the event numbers appear twice with no obvious reason, traces/event times are different.
Example in combined.root: Station 21 / Run 455 / Event Number 1212
In the headers.root, there are several of these events per run.https://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/12First and second part of forced trigger traces look different2021-08-31T11:51:55+02:00Steffen HallmannFirst and second part of forced trigger traces look differentWhen looking at only forced trigger events (selected as described [here](https://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/8)), the first and second part of the traces look different
To check:
- Is this due to read out o...When looking at only forced trigger events (selected as described [here](https://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/8)), the first and second part of the traces look different
To check:
- Is this due to read out of buffers in the same order for forced events?
- The second part is not only lower, but seems to have some kind of oscillation. Is this expected when triggering?
![trace_lab4d_drop](/uploads/9cef3675a2a5d511da5d72b1e92ee046/trace_lab4d_drop.png)https://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/11Add readout for environmental data2021-08-30T21:24:05+02:00Steffen HallmannAdd readout for environmental dataFigure out how to query mirrored database at https://rno-g.uchicago.edu:3000Figure out how to query mirrored database at https://rno-g.uchicago.edu:3000https://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/10Move runs from duplicated /runXX/runXX subdirectories and apply event timing ...2021-08-30T20:05:33+02:00Steffen HallmannMove runs from duplicated /runXX/runXX subdirectories and apply event timing fixes for early runsRun on desy cluster...Run on desy cluster...Steffen HallmannSteffen Hallmannhttps://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/7Integrate run config in root files2021-08-29T14:21:36+02:00Steffen HallmannIntegrate run config in root filesThe run config is transferred from greenland in a separate (small) file. Maybe it can be just added to the combined .root files, in order to reduce number of small files?The run config is transferred from greenland in a separate (small) file. Maybe it can be just added to the combined .root files, in order to reduce number of small files?https://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/6Sampling rate not in .root files2021-08-29T14:20:11+02:00Steffen HallmannSampling rate not in .root filesSampling rate is currently 3.2 GHz, eventually it will be changed to 2.4 GHz. This information is currently not contained in the .root files.
(In the RNO-G uproot readers of NuRadioReco it is hence hardcoded and set to 3.2 GHz at the mo...Sampling rate is currently 3.2 GHz, eventually it will be changed to 2.4 GHz. This information is currently not contained in the .root files.
(In the RNO-G uproot readers of NuRadioReco it is hence hardcoded and set to 3.2 GHz at the moment)https://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/5Station numbers zero in .root files2021-08-29T14:17:42+02:00Steffen HallmannStation numbers zero in .root filesStation numbers for station 11 for runs below 200 (and also first runs of other stations?) are zero. Should be fixed in the .root files.Station numbers for station 11 for runs below 200 (and also first runs of other stations?) are zero. Should be fixed in the .root files.https://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/4sysclk_last == sysclk_last_last2021-09-01T00:53:30+02:00Steffen Hallmannsysclk_last == sysclk_last_lastI saw few events where `sysclk_last` == `sysclk_last_last`, consequently the trigger time might be off significantly (division by zero -> subsecond part >> 1)
Maybe one could check if these events only occured right at the beginning of ...I saw few events where `sysclk_last` == `sysclk_last_last`, consequently the trigger time might be off significantly (division by zero -> subsecond part >> 1)
Maybe one could check if these events only occured right at the beginning of a run?https://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/3Run comments wrong2021-08-28T23:59:39+02:00Steffen HallmannRun comments wrongRun comments are sometimes wrong, e.g. runs 483-590 indicate "in-situ pulsing run" ([see runtable](https://www.zeuthen.desy.de/~shallman/rnog_run_summary.html); comment was not removed after pulsing ended.
Maybe someone involved in depl...Run comments are sometimes wrong, e.g. runs 483-590 indicate "in-situ pulsing run" ([see runtable](https://www.zeuthen.desy.de/~shallman/rnog_run_summary.html); comment was not removed after pulsing ended.
Maybe someone involved in deployment can check if comments are correct?
In the long term, maybe some safety measures can be taken, to help run selection (switch to pre-defined run setups, or -maybe quicker to implement - issue warning if the config has changed?)https://gitlab.desy.de/steffen.hallmann/rno-g-data-tools/-/issues/2Station 21, Channel 23 seems to behave odd2021-08-28T15:42:52+02:00Steffen HallmannStation 21, Channel 23 seems to behave oddLooking at the traces of station 21, channel 23 (hpol on helper) they look odd.
blocks of data seem to have lower voltage values than they should have. This can be seen from the attached screenshot of some randomly chosen traces (doesn't...Looking at the traces of station 21, channel 23 (hpol on helper) they look odd.
blocks of data seem to have lower voltage values than they should have. This can be seen from the attached screenshot of some randomly chosen traces (doesn't really matter which run/traces are chosen)[bugged_channel_23.pdf](/uploads/3c890a2e6e433f20530e2b253901162e/bugged_channel_23.pdf)
Maybe some problem with baseline subtraction or different?