TACTIC: Difference between revisions

From DaqWiki
Jump to navigation Jump to search
No edit summary
Line 3: Line 3:
* computer: daq18.triumf.ca
* computer: daq18.triumf.ca
* midas: https://daq18.triumf.ca
* midas: https://daq18.triumf.ca
* elog: https://elog.triumf.ca/Tactic/General/
* elog: https://elog.triumf.ca/Tactic/General/ (has a "tactic" user account)
* digitizers: 2x V1740 via CAEN USB interface
 
* rebuild fetactic.exe
== Old v1740 DAQ ==
 
=== Overview ===
 
Uses 2x V1740 via CAEN USB interface. 64 channels each - can read out 2 of the 8 TACTIC "sectors".
 
These [https://daq18.triumf.ca/?cmd=Programs programs] should be running:
* mhttpd (web server)
* Logger (writing data to disk)
* feMKS (gas mixer)
* fetactic (data readout from digitizers)
* ana (online analysis of data)
 
=== Wiring diagram and trigger logic ===
 
[[File:Tactic-v1740-trigger.jpg]]
 
Trigger and v1740 connections:
* both v1740 trigger outputs go to logic OR. pulser goes into the same OR
* from this OR, they fan out to v1740 trigger inputs
* analog output of first v1740 provides the run gate (via polarity inverting kludge)
* analog output of second v1740 provides a "buffer-half-full" trigger veto (via polarity inverting kludge)
 
Trigger notes: (KO 7-oct-2024)
* trigger signal is not synched with the v1740 clock, actual "adc stop" time will have a jitter between the two v1740 of 1-2 clock periods
* actual event time jitter between the two v1740 is around 2 clock (from looking at event timestamps).
* because v1740 busy are not synced (and busy from first v1740 is missing), the second v1740 often has extra events. sometimes the first v1740 has an extra event. fetactic.exe has workaround against this, mostly by dropping mismatched data.
 
=== Analyzer notes ===
 
* Code is in /home/tactic/newTACTIC/manalyzer.
* Not source-controlled.
* Contains many hard-coded thresholds/settings/limits. Also includes a hard-coded mapping between digitizer channel number and hardware sector/pad number.
* Used for both online and offline analysis of data.
 
=== Re-compilation ===
 
<pre>
<pre>
# Rebuild fetactic.exe
cd /home/tactic/newTACTIC/v1740mt
cd /home/tactic/newTACTIC/v1740mt
make
make
ls -l fetactic.exe
ls -l fetactic.exe
</pre>
 
* rebuild analyzer
# Rebuild analyzer
<pre>
cd /home/tactic/newTACTIC/manalyzer
cd /home/tactic/newTACTIC/manalyzer
make
make
ls -l ./tacticana.exe
ls -l ./tacticana.exe
</pre>
</pre>
* trigger and v1740 connections:
 
 
== New V2745 DAQ ==
 
=== Overview ===
 
Uses 6x CAEN V2745 digitizers, with option for reading 8 digitizers if needed. With 8 digitizers can read all 8 sectors from the hardware.
 
Digitizers are readout over 1G ethernet, and run DPP_ZLE firmware to reduce the data rate significantly. Future versions of TACTIC may run DPP_PHA or custom firmware to further reduce the data rate.
 
=== Wiring diagram and trigger logic ===
 
Digitizer configuration is done via the [https://daq18.triumf.ca/?cmd=custom&page=VX%20settings VX settings] webpage.  The concept is that the "default" value is applied to all digitizers, unless you specifically override the value for a certain digitizer. This means it's more efficient to change settings, as you only have to change one "default" parameter rather than 8 separate board-specific parameters. Settings that have been overridden for one or more boards appear with a YELLOW background on the webpage.
 
Settings that users may want to configure:
* Readout channel mask
* Ch over thresh A en mask
* Chan over thresh thresholds
* Ch over thresh A gate width(ns)
* Scope/ZLE waveform length
* Pre-trigger for ZLE mode
* ZLE threshold (ADC)
* ZLE look back (samples)
* ZLE look forward (samples)
* DC offset (pct)
* Signal offset (uV)
* VGA gain - 0-40dB in 0.5dB increments
 
Important settings that are different for the first digitizer in the chain:
 
{| class="wikitable"
! Setting !! First board !! Other boards
|-
| Run start source || Start acq on midas run start || Start acq on encoded CLKIN
|-
| Use external clock || True || False
|}
 
Other important settings that shouldn't be changed:
* Run start delay (ns) - 0 for the last board, increasing by 48ns for each board in the chain (240, 192, 144, 96, 49, 0).
* Trigger out mode - ITLA
* Trigger on external signal - True
* ZLE enable
* Ch over thresh A multiplicity
* Chan over thresh rising edge
* Veto source / Veto when source is high -
* Use NIM IO - True
* Enable clock out - True
* GPIO mode - Busy
* Busy in source - SIN
* Sync out mode - Run
* Enable DC offsets - True
 
=== Analyzer notes ===
 
* Code is in /home/tactic/newTACTIC/tacticana on daq18, and https://bitbucket.org/ttriumfdaq/tacticana/src/master/ on bitbucket.
* Uses JSON files to define histogram limits, channel mapping etc. See README.md file in the repository for details.
* Specify which config file to use via the --config flag.
 
<pre>
<pre>
- both v1740 trigger outputs go to logic OR. pulser goes into the same OR
# Run online using the v2745.json config file:
- from this OR, they fan out to v1740 trigger inputs
/home/tactic/newTACTIC/tacticana/tacticana.exe --midas-progname tacticana -R8081 -- --conf /home/tactic/newTACTIC/tacticana/v2745.json
- analog output of first v1740 provides the run gate (via polarity inverting kludge)
 
- analog output of second v1740 provides a "buffer-half-full" trigger veto (via polarity inverting kludge)
# Run offline using the v2745.json config file:
/home/tactic/newTACTIC/tacticana/tacticana.exe /path/to/something.mid -- --conf /home/tactic/newTACTIC/tacticana/v2745.json
 
# NOTE THE --config FLAG MUST COME AFTER A '--'!!!!!
</pre>
</pre>
* trigger notes: (KO 7-oct-2024)
 
=== Re-compilation ===
 
<pre>
<pre>
- trigger signal is not synched with the v1740 clock, actual "adc stop" time will have a jitter between the two v1740 of 1-2 clock periods
# Rebuild vx2740_group_fe.exe
- actual event time jitter between the two v1740 is around 2 clock (from looking at event timestamps).
cd /home/tactic/newTACTIC/dsproto_vx2740/build
- because v1740 busy are not synched (and busy from first v1740 is missing), the second v1740 often has extra events. sometimes the first v1740 has an extra event. fetactic.exe has workaround against this, mostly by dropping mismatched data.
make install -j
 
# Rebuild analyzer
cd /home/tactic/newTACTIC/tacticana
make -j
</pre>
</pre>

Revision as of 20:37, 4 September 2025

TACTIC

Old v1740 DAQ

Overview

Uses 2x V1740 via CAEN USB interface. 64 channels each - can read out 2 of the 8 TACTIC "sectors".

These programs should be running:

  • mhttpd (web server)
  • Logger (writing data to disk)
  • feMKS (gas mixer)
  • fetactic (data readout from digitizers)
  • ana (online analysis of data)

Wiring diagram and trigger logic

Tactic-v1740-trigger.jpg

Trigger and v1740 connections:

  • both v1740 trigger outputs go to logic OR. pulser goes into the same OR
  • from this OR, they fan out to v1740 trigger inputs
  • analog output of first v1740 provides the run gate (via polarity inverting kludge)
  • analog output of second v1740 provides a "buffer-half-full" trigger veto (via polarity inverting kludge)

Trigger notes: (KO 7-oct-2024)

  • trigger signal is not synched with the v1740 clock, actual "adc stop" time will have a jitter between the two v1740 of 1-2 clock periods
  • actual event time jitter between the two v1740 is around 2 clock (from looking at event timestamps).
  • because v1740 busy are not synced (and busy from first v1740 is missing), the second v1740 often has extra events. sometimes the first v1740 has an extra event. fetactic.exe has workaround against this, mostly by dropping mismatched data.

Analyzer notes

  • Code is in /home/tactic/newTACTIC/manalyzer.
  • Not source-controlled.
  • Contains many hard-coded thresholds/settings/limits. Also includes a hard-coded mapping between digitizer channel number and hardware sector/pad number.
  • Used for both online and offline analysis of data.

Re-compilation

# Rebuild fetactic.exe
cd /home/tactic/newTACTIC/v1740mt
make
ls -l fetactic.exe

# Rebuild analyzer
cd /home/tactic/newTACTIC/manalyzer
make
ls -l ./tacticana.exe


New V2745 DAQ

Overview

Uses 6x CAEN V2745 digitizers, with option for reading 8 digitizers if needed. With 8 digitizers can read all 8 sectors from the hardware.

Digitizers are readout over 1G ethernet, and run DPP_ZLE firmware to reduce the data rate significantly. Future versions of TACTIC may run DPP_PHA or custom firmware to further reduce the data rate.

Wiring diagram and trigger logic

Digitizer configuration is done via the VX settings webpage. The concept is that the "default" value is applied to all digitizers, unless you specifically override the value for a certain digitizer. This means it's more efficient to change settings, as you only have to change one "default" parameter rather than 8 separate board-specific parameters. Settings that have been overridden for one or more boards appear with a YELLOW background on the webpage.

Settings that users may want to configure:

  • Readout channel mask
  • Ch over thresh A en mask
  • Chan over thresh thresholds
  • Ch over thresh A gate width(ns)
  • Scope/ZLE waveform length
  • Pre-trigger for ZLE mode
  • ZLE threshold (ADC)
  • ZLE look back (samples)
  • ZLE look forward (samples)
  • DC offset (pct)
  • Signal offset (uV)
  • VGA gain - 0-40dB in 0.5dB increments

Important settings that are different for the first digitizer in the chain:

Setting First board Other boards
Run start source Start acq on midas run start Start acq on encoded CLKIN
Use external clock True False

Other important settings that shouldn't be changed:

  • Run start delay (ns) - 0 for the last board, increasing by 48ns for each board in the chain (240, 192, 144, 96, 49, 0).
  • Trigger out mode - ITLA
  • Trigger on external signal - True
  • ZLE enable
  • Ch over thresh A multiplicity
  • Chan over thresh rising edge
  • Veto source / Veto when source is high -
  • Use NIM IO - True
  • Enable clock out - True
  • GPIO mode - Busy
  • Busy in source - SIN
  • Sync out mode - Run
  • Enable DC offsets - True

Analyzer notes

  • Code is in /home/tactic/newTACTIC/tacticana on daq18, and https://bitbucket.org/ttriumfdaq/tacticana/src/master/ on bitbucket.
  • Uses JSON files to define histogram limits, channel mapping etc. See README.md file in the repository for details.
  • Specify which config file to use via the --config flag.
# Run online using the v2745.json config file:
/home/tactic/newTACTIC/tacticana/tacticana.exe --midas-progname tacticana -R8081 -- --conf /home/tactic/newTACTIC/tacticana/v2745.json

# Run offline using the v2745.json config file:
/home/tactic/newTACTIC/tacticana/tacticana.exe /path/to/something.mid -- --conf /home/tactic/newTACTIC/tacticana/v2745.json

# NOTE THE --config FLAG MUST COME AFTER A '--'!!!!!

Re-compilation

# Rebuild vx2740_group_fe.exe
cd /home/tactic/newTACTIC/dsproto_vx2740/build
make install -j

# Rebuild analyzer
cd /home/tactic/newTACTIC/tacticana
make -j
Retrieved from "https://daq00.triumf.ca/DaqWiki/index.php?title=TACTIC&oldid=8560"