-
404
+
+
404
-
Page not found :(
-
The requested page could not be found.
-
-
+
Page not found :(
+
The requested page could not be found.
+
+
+
+CRT Beam Telescope plots and images
+===================================
+
+1. Beam Substructure (June - December 2017, with sbndcode reconstruction)
+ - The 1.6us beam spill consists of 81 buckets with a period of roughly 19ns.
+ - Using a subset of the data collected between June 2017 and January 2019 we can see this structure in the timing of the reconstructed 2D hits.
+ - The data was collected using a different standalone DAQ setup.
+ - The time of the readouts were measured with respect to a beam signal delayed until after the beam arrivial. A shift was then applied to give the values seen in the plot.
+ - Corrections for cable length and light propagation, time walk and clock drift were applied.
+
+
+
+and zoomed in on a few buckets
+
+
+
+2. Beam Spot (June - December 2017, with sbndcode reconstruction)
+ - Using the upstream set of panels we are able to see the beam's radial intensity decrease or beam spot.
+ - The centre of the beam was to the RHS and slightly above the set of panels.
+ - Using data from the beam spill window (t1 from 4380ns - 5980ns) and a identical length section from before the beam arrival (t1 from 2000ns - 3600ns) the cosmic background is subtracted from the beam signal region.
+ - Note the x axis is inverted in order to reflect the "beam's eye view" entering the building.
+
+
diff --git a/sbndcode_wiki/commissioning/SBND_Commissioning_Get_Started.md b/sbndcode_wiki/commissioning/SBND_Commissioning_Get_Started.md
index 8bd1b7209..3d39e8d01 100644
--- a/sbndcode_wiki/commissioning/SBND_Commissioning_Get_Started.md
+++ b/sbndcode_wiki/commissioning/SBND_Commissioning_Get_Started.md
@@ -24,12 +24,12 @@ Log in to an SBND virtual machine, for example:
You will land in an area called `nashome`, from there you have two main
other areas available:
-- `/sbnd/app/users/$USER/`: Here you should store your software (if
+- `/exp/sbnd/app/users/$USER/`: Here you should store your software (if
this directory doesn't exist, you can create it with
- `mkdir /sbnd/app/users/$USER`).
-- `/sbnd/data/users/$USER/`: Here you should store your files (if this
+ `mkdir /exp/sbnd/app/users/$USER`).
+- `/exp/sbnd/data/users/$USER/`: Here you should store your files (if this
directory doesn't exist, you can create it with
- `mkdir /sbnd/data/users/$USER`).
+ `mkdir /exp/sbnd/data/users/$USER`).
Remember that the `app` area has limited disk space, so please do
not store any data file there, but only the code you need.
@@ -41,7 +41,7 @@ other areas available:
Go to the `app` area, where we can install and develop software:
```bash
- cd /sbnd/app/users/$USER/
+ cd /exp/sbnd/app/users/$USER/
```
Setup the SBND environment first:
diff --git a/sbndcode_wiki/commissioning/beampeak.png b/sbndcode_wiki/commissioning/beampeak.png
new file mode 100644
index 000000000..3e83e45b3
Binary files /dev/null and b/sbndcode_wiki/commissioning/beampeak.png differ
diff --git a/sbndcode_wiki/commissioning/files/beampeak.png b/sbndcode_wiki/commissioning/files/beampeak.png
new file mode 100644
index 000000000..722f4a750
Binary files /dev/null and b/sbndcode_wiki/commissioning/files/beampeak.png differ
diff --git a/sbndcode_wiki/commissioning/files/crt_sharps_run2100_beam_peak.png b/sbndcode_wiki/commissioning/files/crt_sharps_run2100_beam_peak.png
new file mode 100644
index 000000000..56a934422
Binary files /dev/null and b/sbndcode_wiki/commissioning/files/crt_sharps_run2100_beam_peak.png differ
diff --git a/sbndcode_wiki/commissioning/files/crthit_beam_spot_bt_2017.png b/sbndcode_wiki/commissioning/files/crthit_beam_spot_bt_2017.png
new file mode 100644
index 000000000..5cdb0168d
Binary files /dev/null and b/sbndcode_wiki/commissioning/files/crthit_beam_spot_bt_2017.png differ
diff --git a/sbndcode_wiki/commissioning/files/crthit_t1_beam_substructure_bt_2017.png b/sbndcode_wiki/commissioning/files/crthit_t1_beam_substructure_bt_2017.png
new file mode 100644
index 000000000..f7bfdac46
Binary files /dev/null and b/sbndcode_wiki/commissioning/files/crthit_t1_beam_substructure_bt_2017.png differ
diff --git a/sbndcode_wiki/commissioning/files/crthit_t1_beam_substructure_zoomed_bt_2017.png b/sbndcode_wiki/commissioning/files/crthit_t1_beam_substructure_zoomed_bt_2017.png
new file mode 100644
index 000000000..e9ec0cbb8
Binary files /dev/null and b/sbndcode_wiki/commissioning/files/crthit_t1_beam_substructure_zoomed_bt_2017.png differ
diff --git a/sbndcode_wiki/daq_errors.md b/sbndcode_wiki/daq_errors.md
new file mode 100644
index 000000000..db2c6d457
--- /dev/null
+++ b/sbndcode_wiki/daq_errors.md
@@ -0,0 +1,58 @@
+---
+layout: page
+title: List of DAQ Errors
+---
+
+
+This page lists various previously encountered DAQ errors and their possible solutions. Errors are sorted by subsystem.
+
+
+PTB
+==========================================================
+
+#### 1. Unable to get lock while trying to report the current state
+```Error / ptb01PUSH_BoardReaderCore
+ 06-Jan-2023 07:46:01 CST
+ sbnd-ptb01.fnal.gov (131.225.250.158)
+ UDPMessage 0 / PID 211609 / BoardReaderCore.cc:345
+ boardreader / Starting / Booted
+ Timeout (60 s) while waiting for Start after receive_fragments thread started!
+ Unable to get lock while trying to report the current state, returning busy
+```
+
+This error appeared after the PTB network was accidentally unplugged. A full reboot of the Microzed Linux solved the problem. Also tried restarting the ptb service which did not solve the problem.
+
+
+WR TDC
+==========================================================
+
+#### 1. Unable to get lock while trying to report the current state
+```
+ Warning / TDCChan
+ Wrong TDC sample time, check the NTP and WhiteRabbit timing system; host_time-sample_time=1seconds.
+```
+
+This error apears when the TDC timestamp is wrong. Sometimes you get 1 of these at the very beggining of a run as systems are setting up/configuring. If it's happening frequently and _exactly_ 1 second then it is most likely that the leap second parameters in the TDC configuration fcl are incorrect - check the current number of leap seconds and change the date to be the next possible one.
+
+
+
+#### 2. Timeout of SPECTDC
+``` Error/spectdc_BoardReaderCore
+14-Jul-2023 15:29:37 CDT
+sbnd-clk01.fnal.gov (131.225.250.162)
+UDPMessage / PID 34451 / BoardReaderCore.cc:348 boardreader/ Early / pre-events
+Timeout (60 s) while waiting for Start after receive fragments thread started!
+Error/spectdc_BoardReaderCore
+14-Jul-2023 15:29:37 CDT
+sbnd-clk01.fnal.gov (131.225.250.162)
+UDPMessage / PID 34451 / BoardReaderCore.cc:450 boardreader / Early / pre-events
+Timeout (60 s) while waiting for Start after send fragments thread started!
+Error/spectdc_xmlrpc_commander 14-Jul-2023 15:29:39 CDT
+sbnd-clk01.fnal.gov (131.225.250.162) UDPMessage / PID 34451/xmlrpc_commander.cc:792
+boardreader / Early / pre-events
+Unable to get lock while trying to report the current state, returning busy
+```
+
+This error appeared after running spectdc, ptb, and all 8 caen baords. During this run the board in slot 18 crashed (temperature issue we believe) and then we started to get the timeout error when trying to rerun without board 18.
+
+Will reboot to see if that fixes the error.
diff --git a/woke_mind_virus.sh b/woke_mind_virus.sh
new file mode 100755
index 000000000..c032d42b2
--- /dev/null
+++ b/woke_mind_virus.sh
@@ -0,0 +1,86 @@
+#!/bin/bash
+
+# @file: woke_mind_virus.sh
+# @bried: The true Gay Agenda (TM).
+# @description: Replaces gendered English pronouns with gender-neutral
+# equivalents. Notes and nuances are detailed below.
+
+# Note that the substitutions below do not take into account the context
+# in which these words appear in a sentence. Ex. 'her' is changed to 'them'
+# implicitly assuming 'her' appears as the indirect object of a sentence
+# (e.g. She gave her a cup of tea.); however, 'her' can also indicate ownership
+# (e.g. She put on her coat.). Feel free to adjust substitutions as needed.
+# We have decided to keep 'her' --> 'them' since it has the added benefit of
+# meshing well with reflexive pronouns (e.g. 'She herself did...' -->
+# 'They themselves did... ). These types of ambiguities (specifically with the
+# pronoun 'her', as it is used for many types of feminine pronouns) are less
+# prominent when changing instances of, e.g., his/her to their.
+
+# Further ambiguity arises when one considers how the singular 'they' varies
+# in a reflexive context. Some prefer to use 'themselves' while other prefer
+# to use 'themself' when utilizing the singular, reflexive they. We use
+# 'themselves' over 'themself' as it is more intuitive for non-native English
+# speakers.
+
+# he/she --> they, etc.
+grep -rlZ --include="*.txt" --include="*.md" --include="*.cpp" --include="*.h" --include="*.py" . | xargs -0 sed -i \
+ -e 's/\bhe\/she\b/they/g' \
+ -e 's/\bshe\/he\b/they/g' \
+ -e 's/\bHe\/She\b/They/g' \
+ -e 's/\bHe\/she\b/They/g' \
+ -e 's/\bShe\/He\b/They/g' \
+ -e 's/\bShe\/he\b/They/g' \
+ -e 's/\bhe\b/they/g' \
+ -e 's/\bshe\b/they/g' \
+ -e 's/\bHe\b/They/g' \
+ -e 's/\bShe\b/They/g'
+
+# him/her --> them, etc.
+# @note: her --> them conflicts with her --> their, etc.
+grep -rlZ --include="*.txt" --include="*.md" --include="*.cpp" --include="*.h" --include="*.py" . | xargs -0 sed -i \
+ -e 's/\bhim\/her\b/them/g' \
+ -e 's/\bher\/him\b/them/g' \
+ -e 's/\bHim\/Her\b/Them/g' \
+ -e 's/\bHim\/her\b/Them/g' \
+ -e 's/\bHer\/Him\b/Them/g' \
+ -e 's/\bHer\/him\b/Them/g' \
+ -e 's/\bhim\b/them/g' \
+ -e 's/\bher\b/them/g' \
+ -e 's/\bHim\b/Them/g' \
+ -e 's/\bHer\b/Them/g'
+
+# his/her --> their, etc.
+# @note: her --> their conflicts with her --> them, etc.
+grep -rlZ --include="*.txt" --include="*.md" --include="*.cpp" --include="*.h" --include="*.py" . | xargs -0 sed -i \
+ -e 's/\bhis\/her\b/their/g' \
+ -e 's/\bher\/his\b/their/g' \
+ -e 's/\bHis\/Her\b/Their/g' \
+ -e 's/\bHis\/her\b/Their/g' \
+ -e 's/\bHer\/His\b/Their/g' \
+ -e 's/\bHer\/his\b/Their/g' \
+ -e 's/\bhis\b/their/g' \
+ -e 's/\bHis\b/Their/g'
+
+# his/hers --> theirs, etc.
+grep -rlZ --include="*.txt" --include="*.md" --include="*.cpp" --include="*.h" --include="*.py" . | xargs -0 sed -i \
+ -e 's/\bhis\/hers\b/theirs/g' \
+ -e 's/\bhers\/his\b/theirs/g' \
+ -e 's/\bHis\/Hers\b/Theirs/g' \
+ -e 's/\bHis\/hers\b/Theirs/g' \
+ -e 's/\bHers\/His\b/Theirs/g' \
+ -e 's/\bHers\/his\b/Theirs/g' \
+ -e 's/\bhers\b/theirs/g' \
+ -e 's/\bHers\b/Theirs/g'
+
+# himself/herself --> themselves, etc.
+grep -rlZ --include="*.txt" --include="*.md" --include="*.cpp" --include="*.h" --include="*.py" . | xargs -0 sed -i \
+ -e 's/\bhimself\/herself\b/themselves/g' \
+ -e 's/\bherself\/himself\b/themselves/g' \
+ -e 's/\bHimself\/Herself\b/Themselves/g' \
+ -e 's/\bHimself\/herself\b/Themselves/g' \
+ -e 's/\bHerself\/Himself\b/Themselves/g' \
+ -e 's/\bHerself\/himself\b/Themselves/g' \
+ -e 's/\bhimself\b/themselves/g' \
+ -e 's/\bherself\b/themselves/g' \
+ -e 's/\bHimself\b/Themselves/g' \
+ -e 's/\bHerself\b/Themselves/g'