FSU Fox's Lab Wiki - User contributions [en]

Pixie16 digitizer

2026-05-05T19:51:19Z

Sbalak:

= Introduction =

[[File:Pixie16HardwareConnection.png|500px|thumb|right|Illustration of Pixie16 Crate to DAQ PC connection]]

In order to control the Pixie16 digitizer, the DAQ computer needs to recognize the digitizer via a PCIe card( for example NI PCI-8366).

The '''digitizer crate''' (XIA PXI CompactPCI) has 14-slot. The 1st slot must be the communication card (for example, NI PXI-8366). The remaining 13 slots can be used for digitizer and other modules.

The PCIe card and PXI Board requires no driver. The DAQ computer will treat it as a bridge.

In the computer (LINUX), using the command lspci to show the PCI connection

>lspci

as an example, part of the output:

04:00.0 PCI bridge: Intel Corporation 41210 [Lanai] Serial to Parallel PCI Bridge (A-Segment Bridge) (rev 09)
04:00.2 PCI bridge: Intel Corporation 41210 [Lanai] Serial to Parallel PCI Bridge (B-Segment Bridge) (rev 09)
<span style="color:blue">05:0f.0 Unassigned class [ff00]: National Instruments PXI-8368 </span>
06:05.0 PCI bridge: Texas Instruments PCI2050 PCI-to-PCI Bridge (rev 02)
<span style="color:green">06:0f.0 Bridge: PLX Technology, Inc. PCI9054 32-bit 33MHz PCI <-> IOBus Bridge (rev 0b)</span>

In the above output, the NI PXI-8368 board on the crate is detected. Also the PCI9054 communication chip is detected.

[[File:Pixie16 PCI9054 chip location.png|500px|thumb|right|The location of the PCI9054 communication chip on Pixie16 digitizer.]]
The '''PCI9054''' (or PLX9054) chip is located at the corner of the Pixie16 digitizer.

The PCI9054 chip requires a driver. The driver is provided by Broadcom, and the package is called [[Pixie16_digitizer#Broadcom_PlxSDK | '''PlxSDK''']].

After the driver for the PCI9054 chip is done, the DAQ PC can talk to the digitizer. Next, the [[Pixie16_digitizer#Pixie_SDK |'''PixieSDK''']] has to be installed for controlling the digitizer. The PixieSDK provides methods to control the digitizer.

= Versions of Pixie16 Digitizer =

In FSU, we have 100MHz (sampling rate) models and 250 MHz models.

500 MHz models are also used in Clarion2.

Each model has 16 channels. <span style="color:red">Using connector ?? </red>

= Pixie16 firmware =

The firmware can be downloaded from http://download.xia.com/#products/pixie16/firmware/

= Data Structure =

The recorded data is stored in the extern FIFO (first-in first-out) memory or '''ExtFIFO''' on the digitizer. A block of Data is formed by '''word''', each word is 32 bit long. A minimum data block contains 4 words. When extra information is switched on, they will be stored afterward. The total length of a data block is called '''event length'''.

The data structure shown below and taken from the [https://xia.com/wp-content/uploads/2018/04/Pixie16_UserManual.pdf XIA Pixie-16 User Manual version 3.06] (a copy of the [[:File:Pixie16 UserManual.pdf |Manual]]), page 72.

[[File:Pixie16DataStructure.png|600px|frameless|none|Data structure of Pixie-16. Taken from XIA Pixie-16 User Manual version 3.06.]]

The trace (if enabled) is stored after the header.

The data usually saved in a binary format. The [[Pixie16_digitizer#evtReader_Class|evtReader]] from XIAEventBuilder package can read the binary format in root or in C++.

== Incomplete data block when retrieving ==

It is possible that an incomplete data block may be retrieved at the beginning or at the end of ExtFIFO.

If the data is saved continuously, that will be not a problem.

== Reading data ==

Timothy Gray developed code https://github.com/belmakier/libpixie.

=== XIAEventReader ===

XIA Event Reader is a command line-based data analysis program developed by Ryan Tang from FSU.

The program can be downloaded from https://github.com/goluckyryan/XIAEventBuilder

==== evtReader Class ====
A very useful code is the [https://github.com/goluckyryan/XIAEventBuilder/blob/master/armory/evtReader.h evtReader.h]

This define the evtReader Class and can be loaded with root.
<div class="toccolours mw-collapsible mw-collapsed">
<div style="line-height:1.6;">Example</div>
<div class="mw-collapsible-content">
~>root -e '.L evtReader.h'
root$<span style="color:blue">evtReader</span> * evt = new <span style="color:blue">evtReader</span>("data_file")
root$evt->ReadBlock();evt->data->Print()
root$evt->ScanNumberOfBlock()
</div></div>

= Broadcom PlxSDK =

The chip was a product of [https://en.wikipedia.org/wiki/PLX_Technology PLX Technology], acquired by Broadcom Inc in 2014. The chipset driver is now called the [https://www.broadcom.com/products/pcie-switches-bridges/software-dev-kits Broadcom PCI/PCIe Software Development Kits ]. The package provides complete documentation and driver. The last release is on 2020.

Because of that, it only support Linux kernel around that time. I tested on

{|class="wikitable"
|'''OS''' || '''Status'''
|-
| Debian 10 || OK
|-
| Debian 11 || Error
|-
| Ubuntu 20 || Error
|}

== Installation ==

After downloaded the package (here is a [[:File:Broadcom PCI PCIe SDK Linux v8 23 Final 2020-11-18.zip| backup copy]]), unzip it, and we have

<div class="toccolours mw-collapsible mw-collapsed" style="width:400px; overflow:auto;">
<div style="line-height:1.6;"> File lists </div>
<div class="mw-collapsible-content">
├── Documentation
│   ├── PLX API DLL with Visual Basic.htm
│   ├── PLX_LegacyAPI.pdf
│   ├── PlxRdkReferenceGuide.htm
│   ├── PLX_SDK_General_FAQ.pdf
│   ├── PLX_SDK_Linux_Release_Notes.htm
│   ├── PLX_SDK_Release_Notes.htm
│   └── PlxSdkUserManual.pdf
└── PlxSdk.tar
</div></div>
The tarball contains the driver. I extract the tarball into '''/usr/opt/PlxSdk'''. To setup the package (make) and also make the driver:

~>cd /usr/opt/PlxSdk/
PlxSdk>export PLX_SDK_DIR=$(pwd)
PlxSdk>sudo make # This shold make everything, including things in Samples
PlxSdk>cd Driver
PlxSdk/Driver>export PLX_CHIP=9054
PlxSdk/Driver>sudo ./builddriver 9054
PlxSdk>cd ../Bin
PlxSdk/Bin>sudo ./Plx_load 9054
Install: Plx9054
Load module......... Ok (/usr/opt/PlxSdk/Driver/Source.Plx9000/Output)
Verify load......... Ok
Get major number.... Ok (MajorID = 243)
Create node path.... Ok (/dev/plx)
Create nodes........ Ok (/dev/plx/Plx9054)

In the last step, it loads the 9054 driver to the Linux Kernel. Fro more detail, see [https://fsunuc.physics.fsu.edu/elog/Pixie_NSCLDAQ/18 | elog]

We can use '''lsmod''' to check the driver is loaded.

~>lsmod | grep "Plx9054"

=== Load 9054 driver on start up ===
To make the driver get loaded on start up, create a file at '''/etc/systemd/system/''', say broadcom.service

<div class="toccolours mw-collapsible mw-collapsed">
<div style="line-height:1.6;">File content</div>
<div class="mw-collapsible-content">
[Unit]
Description=Broadcom PCI/PCIe 9054 Driver
After=network.target

[Service]
Type=oneshot
Environment=PLX_SDK_DIR=/usr/opt/PlxSdk/
ExecStart=/bin/bash /usr/opt/PlxSdk/Bin/Plx_load 9054
ExecStop=/bin/bash /usr/opt/PlxSdk/Bin/Plx_unload 9054
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
</div></div>
and then

sudo systemctl daemon-reload
sudo systemctl enable broadcom.service

= Pixie SDK =

'''PixieSDK''' provides all methods to control the digitizer, from parameters setting, writing/reading control register, starting and stopping the DAQ, to retrieving recorded data from its Extern FIFO (first-in-first-out) memory.

The SDK can be downloaded from GitHub in [https://github.com/xiallc/pixie_sdk here].

The methods are listed in [https://docs.pixie16.xia.com/group__PIXIE16__API.html this web page].

[https://docs.pixie16.xia.com/namespacexia_1_1pixie_1_1error.html Pixie API error code]

== PixieSDK 3.2 ==

== PixieSDK 3.3 ==

PixieSDK 3.3 is similar to 3.2.

A copy of the programmer's manual is
[[:File:Pixie16 ProgrammerManual.pdf|here]]

== Legacy PixieSDK ==

= DAQ Programs =

== NSCL DAQ (DDAS) ==

Pixie16 digitizer is supported by NSCL DAQ via the [https://docs.nscl.msu.edu/daq/newsite/ddas-1.1/pages.html '''DDAS'''] (digital data acquistion system) package.

In here, we are using the <b><span style="color:orange;font-size:20px;">Singularity container</span></b> method. To setup the NSCL DAQ, please check '''[[NSCL DAQ]]'''. After the setup, we assume the file structure is

{|class='wikitable'
! Path !! function
|-
| /usr/opt/nscl-buster.img || Singularity container image
|-
| /usr/opt/opt-buster/ || NSCL DAQ pre-compiled files
|}

=== Load the PLX 9054 driver ===

In order to let the singularity recognize the PLX driver. We have to '''''UNLOAD''''' the Broadcom Driver v8.0 from above, and '''''LOAD''''' the driver in <b>/usr/opt/opt-buster/plx</b>.

==== To unload the 9054 Driver ====

/usr/opt/PlxSDK/Bin>sudo ./Plx_unload 9054

==== Compilation of the driver in the singularity shell ====
export env variable
Singularity nscl-buster.img:/usr/opt/plx>export PLX_SDK_DIR=$(pwd)

create Driver-<kernal> directory
Singularity nscl-buster.img:/usr/opt/plx>./mkdrivertree

compile the driver
Singularity nscl-buster.img:/usr/opt/plx/Driver-4.19.0-20-amd64>./builddriver 9054

<div class="toccolours mw-collapsible mw-collapsed">
<div style="line-height:1.6;">Should able to see something like this:</div>
<div class="mw-collapsible-content">
Build: Plx9054

- PLA: Linux ver ??
- KER: ver 4.19.0-20-amd64
- INC: /lib/modules/4.19.0-20-amd64/build/include
- CPU: x86_64 (64-bit Little Endian)
- CMP: gcc
- TYP: Driver
- PLX: 9054
- CFG: Release

make[1]: Entering directory '/usr/src/linux-headers-4.19.0-20-amd64'
CC [M] /usr/opt/plx/Driver-4.19.0-20-amd64/Source.Plx9000/ApiFunc.o
CC [M] /usr/opt/plx/Driver-4.19.0-20-amd64/Source.Plx9000/Dispatch.o
CC [M] /usr/opt/plx/Driver-4.19.0-20-amd64/Source.Plx9000/Driver.o
CC [M] /usr/opt/plx/Driver-4.19.0-20-amd64/Source.Plx9000/Eep_9000.o
CC [M] /usr/opt/plx/Driver-4.19.0-20-amd64/Source.Plx9000/ModuleVersion.o
CC [M] /usr/opt/plx/Driver-4.19.0-20-amd64/Source.Plx9000/PciFunc.o
CC [M] /usr/opt/plx/Driver-4.19.0-20-amd64/Source.Plx9000/SuppFunc.o
CC [M] /usr/opt/plx/Driver-4.19.0-20-amd64/Source.Plx9000/Chip/9054/PlxChipApi.o
CC [M] /usr/opt/plx/Driver-4.19.0-20-amd64/Source.Plx9000/Chip/9054/PlxChipFn.o
CC [M] /usr/opt/plx/Driver-4.19.0-20-amd64/Source.Plx9000/Chip/9054/PlxInterrupt.o
LD [M] /usr/opt/plx/Driver-4.19.0-20-amd64/Plx9054.o
Building modules, stage 2.
MODPOST 1 modules
CC /usr/opt/plx/Driver-4.19.0-20-amd64/Plx9054.mod.o
LD [M] /usr/opt/plx/Driver-4.19.0-20-amd64/Plx9054.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.19.0-20-amd64'

Driver "Source.Plx9000/Output/Plx9054.ko" built sucessfully
</div></div>

==== Load the driver in the host system ====

In the host system, due to the file structure, we need to create a symbolic link

/usr/opt>ln -s opt-buster/plx

go to the plx

/usr/opt>cd opt-buster/plx/Bin
/usr/opt/opt-buster/plx/Bin>sudo ./Plx_load 9054

Install: Plx9054
Load module......... Ok (Plx9054.ko)
Verify load......... Ok
Get major number.... Ok (MajorID = 243)
Create node path.... Ok (/dev/plx)
Create nodes........ Ok (/dev/plx/Plx9054)

<div class="toccolours mw-collapsible mw-collapsed">
<div style="line-height:1.6;">To check, we can</div>
<div class="mw-collapsible-content">
~>sudo lspci -vvv

06:0f.0 Bridge: PLX Technology, Inc. PCI9054 32-bit 33MHz PCI <-> IOBus Bridge (rev 0b)
Subsystem: PLX Technology, Inc. PCI9054 32-bit 33MHz PCI <-> IOBus Bridge
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at f7100000 (32-bit, non-prefetchable) [size=256]
Region 2: Memory at f6800000 (32-bit, non-prefetchable) [size=8M]
Region 3: Memory at f7000000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [40] Power Management version 1
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [48] CompactPCI hot-swap <?>
Capabilities: [4c] Vital Product Data
pcilib: sysfs_read_vpd: read failed: Input/output error
Not readable
<span style="color:Blue">Kernel driver in use: Plx9054</span>

With this, in the singularity shell, the PLX9054 driver is OK. To test, we use the NSCOPE to check
</div></div>

=== NSCOPE ===

[https://docs.nscl.msu.edu/daq/newsite/ddas-1.1/nscope.html nscope] is a GUI program for setting digitizer parameters, developed by Jeromy Tompkins (modified by David Caussyn). The program used the PLX Driver 7.0, Legacy PixieSDK, CERN ROOT 5.

In the <b>/usr/opt/opt-buster/ddas/5.0-004/bin</b>, there is a nscope.

In order to run nscope, we need other setting files
{|class='wikitable' style='width 550px;'
! file !! function
|-
| cfgPixie16.txt || setting
|-
| pxisys.ini || required by Legacy PixieSDK, no need to change
|-
| XXXX.set || parameters setting file
|}

Those files can be copied from <b>/usr/opt/opt-buster/ddas/5.0-004/share/readout/crate_1</b>.

I created <b>/home/ryan/readout</b> to store those files.

===== cfgPixie16.txt =====

We have only 1 crate and 1 digitizer at slot 2.

1 #crateID
1 #number of modules
2 #slot for mod 0
/home/ryan/readout/create_1.set

<span style="color:red">How to set firmware location? </span>

===== Run NSCOPE =====
[[File:Nscope entrance screen.png|270px|thumb|right|The initial window of NSCOPE]]
run in Singularity shell

Singularity:~/readout>/usr/opt/ddas/5.0-004/bin/nscope
current working directory /home/ryan/readout

A window will pop out.

click the <b>Boot</b>, in the terminal, we have

------------------------
Initializing PXI access...
System initialized successfully.
Found Pixie-16 module #0, Rev=15, S/N=1314, Bits=16, MSPS=250

Booting Pixie-16 module #0
ComFPGAConfigFile: /usr/opt/ddas/firmware/2.1-000/firmware/syspixie16_current_16b250m.bin
SPFPGAConfigFile: /usr/opt/ddas/firmware/2.1-000/firmware/fippixie16_current_16b250m.bin
DSPCodeFile: /usr/opt/ddas/firmware/2.1-000/dsp/Pixie16_current_16b250m.ldr
DSPVarFile: /usr/opt/ddas/firmware/2.1-000/dsp/Pixie16_current_16b250m.var
DSPParFile: /home/ryan/readout/crate_1.set
--------------------------------------------------------

Start to boot Communication FPGA in module 0
Start to boot signal processing FPGA in module 0
Start to boot DSP in module 0
All modules ok

It correctly recognize the model, and load the corresponding firmware.

=== Taking Data ===

Make sure
* the '''DaqPortManager''' and '''RingMaster''' are running.
* the NSCOPE can run.
* the parameters is adjusted for trigger (using NSCOPE).

In this section, we need 3 terminals
# for checking the '''ringbuff'''
# for running the '''DDASReadout'''
# for running the '''dumper'''

Check the RingMaster statue

Singularity-00:~>/usr/opt/daq/11.4-013/bin/ringbuffer status
+----+------------+-------+-------------+--------+---------+---------+------+-------------+
|Name|data-size(k)|free(k)|max_consumers|producer|maxget(k)|minget(k)|client|clientdata(k)|
+----+------------+-------+-------------+--------+---------+---------+------+-------------+
|ryan|8194 |8194 |100 |-1 |0 |0 |- |- |
+----+------------+-------+-------------+--------+---------+---------+------+-------------+

The default name of a ring is the user name (so ryan). There is no process as '''producer''' and '''client''', as no process is producing data (producer), and no process is getting the data from the ring buffer (client).

==== producer : DDASReadout ====
To run a (data) producer or the DDASReadout, in a new terminal, we run another singularity shell
Singularity-01:~/readout>/usr/opt/daq/11.4-013/bin/DDASReadout
<div class="toccolours mw-collapsible mw-collapsed">
<div style="line-height:1.6;">Output</div>
<div class="mw-collapsible-content">
The new event buffer size will be: 16934
Using a FIFO threshold of 10240 words
Trying to initialize pixie16
Crate number 1: 1 modules, in slots:2 DSPParFile: /home/ryan/readout/crate_1.set
Module event lengths: 4
------------------------
Initializing PXI access...
System initialized successfully.
Found Pixie-16 module #0, Rev=15, S/N=1314, Bits=16, MSPS=250

Booting Pixie-16 module #0
ComFPGAConfigFile: /usr/opt/ddas/firmware/2.1-000/firmware/syspixie16_current_16b250m.bin
SPFPGAConfigFile: /usr/opt/ddas/firmware/2.1-000/firmware/fippixie16_current_16b250m.bin
DSPCodeFile: /usr/opt/ddas/firmware/2.1-000/dsp/Pixie16_current_16b250m.ldr
DSPVarFile: /usr/opt/ddas/firmware/2.1-000/dsp/Pixie16_current_16b250m.var
DSPParFile: /home/ryan/readout/crate_1.set
--------------------------------------------------------

Start to boot Communication FPGA in module 0
Start to boot signal processing FPGA in module 0
Start to boot DSP in module 0
All modules ok
Module #0 : module id word=0xf1000fa, clock calibration=8
Resetting last channel timestamps on module: 0
Reader created
setup scalers for 1 modules
Scalers know crate ID = 1
%៛ <span style="color:grey"><=== prompt for enter command to control the readout</span>

It will leave us in the prompt.
</div></div>

==== client : dumper ====
We also need a (data) client to get the data from the ring buffer.

In a new terminal, open another Singularity shell, run the [https://docs.nscl.msu.edu/daq/newsite/nscldaq-11.4/r14117.html dumper] program.

Singularity-02:~/readout>/usr/opt/daq/11.4-013/bin/dumper --count=50

If we go to the 1st terminal and check the ringbuffer

Singularity-00:~> /usr/opt/daq/11.4-013/bin/ringbuffer status
+----+------------+-------+-------------+--------+---------+---------+------+-------------+
|Name|data-size(k)|free(k)|max_consumers|producer|maxget(k)|minget(k)|client|clientdata(k)|
+----+------------+-------+-------------+--------+---------+---------+------+-------------+
|ryan|8194 |8194 |100 |482 |0 |0 |- |- |
|- |- |- |- |- |- |- |584 |0 |
+----+------------+-------+-------------+--------+---------+---------+------+-------------+

We can see that the producer (ID 482) and client (ID 584) are there, and we are ready to take data.

==== Start and Stop ====

At the '''DDASReadout''' terminal, there are 3 commands:

{|class='wikitable
! !! command !!
|-
|to start data taking ||begin || the '''dumper''' terminal will show a lot of binary data stream.
|-
|to stop data taking || end
|-
|to exit the DDASReadout|| exit
|}

==== the data ====

The dumper program will store data to lmdata_mod0.bin, which is [[Pixie16_digitizer#Data_Structure|Pixie data format]].

=== ReadOutShell ===
[[File:ReadoutShell Window.png|270px|thumb|right|Window of the ReadoutShell]]
We are still using the Singularity-container method in here. The files are located in

{|class='wikitable' style="width: 400px;"
! !! host system !! Singularity
|-
| NSCL DAQ || /usr/opt/opt-buster || /usr/opt/
|}

The ReadoutShell is located at

Singularity>/usr/opt/daq/11.4-013/bin/ReadoutShell

The ReadOutShell will load the ReadOutGUI. See the right picture.

===== SSH Pipe for Data Source =====
[[File:DateProvider.png|600px|thumb|right|Screenshot of Data Provider from '''Data source >> List ''' ]]
On the manual bar of the ReadoutGUI, '''Data Source >> Add..''', Select SSHPipe.
{|class='wikitable'
| Host name :|| localhost
|-
| Readout program : || /usr/opt/nscldaq/11.4-013/bin/DDASReadout
|-
|Working directory : || Click the Same as Readout
|-
|Command line options : || --ring=ryan --sourceid = 0
|}

Since we are using '''ryan''' ring. See [[Pixie16_digitizer#Taking_Data hee]].

To check, '''Data Source >> List''', you should see the setting.

Since we are using ssh to connect the data source, even it is localhost, it will ask you password. So, better use command
~>ssh-copy-id localhost
To copy the ssh key. To create an ssh key if you don't have one, please see [Place holder]

A problem for ssh pipe with Singularity container is that, after ssh, it will not run Singularity shell but normal bash shell. To tackle this, two things must be done
#<pre>export export SING_IMAGE=/usr/opt/nscl-buster.img</pre>
#<pre>echo /usr/opt/opt-buster/:/usr/opt > ~/.singularity_bindpoints</pre>
The '''SING_IMAGE''' and '''~/.singularity_bindpoints''' are recognized by the SSHPipe, so that it will go to Singularity constainer.

<div class="toccolours mw-collapsible mw-collapsed">
<div style="line-height:1.6;">So, I make a '''ReadOut.sh''' script to simplify to job.</div>
<div class="mw-collapsible-content">
<syntaxhighlight lang="Bash" line>
#!/bin/bash
export VERSION=11.4-013
export USROPT=/usr/opt/opt-buster/
export SINGULARITY_CONTAINER=/usr/opt/nscl-buster.img
export DAQPORTMANAGER=/usr/opt/daq/${VERSION}/bin/DaqPortManager
export DAQPORTMANAGERLOGFILE=$HOME/nscl_daq.log
export DAQPORTMANAGERPIDFILE=$HOME/nscl_daq.pid
export RINGMASTER=/usr/opt/daq/${VERSION}/bin/RingMaster
export RINGMASTERLOGFILE=$HOME/nscl_ring.log
export READOUT=/usr/opt/daq/${VERSION}/bin/ReadoutShell

## these two lins are important for ReadOut ssh know to use singularity
export SING_IMAGE=$SINGULARITY_CONTAINER
echo $USROPT:/usr/opt > ~/.singularity_bindpoints

singularity exec --shell /bin/bash --bind ${USROPT}:/usr/opt/ ${SINGULARITY_CONTAINER} ${READOUT}
</syntaxhighlight>
</div></div>

===== Start & Begin =====

#'''To boot the Pixie16, or run DDASReadout''', click the '''Start''' button.
#'''To Run''', click the '''Begin''' button

To set the run name, '''Settings >> Event Recording...'''. You can set the '''Run file prefix'''.

The data will be stored at the '''Stagearea'''.

== used in Clerion2 ==

A special terminal-based [[Clarion2#DAQ | DAQ]] program used in '''[[Clarion2]]''' are developed by Jame M. Allmond and Tim Gray from ORNL.

== PixieDAQ ==
[[File:PixieDAQ entrance.png|270px|thumb|right|initial window of PixieDAQ]]

PixieDAQ is a GUI program for completely controlling and taking data from Pixie16 digitizer, developed by Ryan Tang. The program used the [[#Broadcom PlxSDK | Boardcom PlxSDK 8.0]], PixieSDK 3.3 and ROOT 6.24.

I assume the Boardcom PlxSDK, PixieSDK 3.3 are located at
{|
| Boardcom PlxSDK 8.0 || : <b>/usr/opt/PlxSdk</b>
|-
| PixieSDK 3.3 || : <b>/usr/opt/xia/PixieSDK</b>
|}

The program can be downloaded at https://github.com/goluckyryan/Pixie16_GUI_DAQ. Its target platform is '''Debian 10''', using '''CERN ROOT 6.24.06'''. Once downloaded the program. Unless the PlxSDK and PixieSDK are in different locations, using make should be able to compile the program.

There is only 1 configuration file <b>[[#Pixie16.conf | Pixie16.conf]]</b>

<b><span style="color:green">PixieDAQ will boot the digitizer when start.</span></b>

To run,

~/pixieDAQ>./pixieDAQ

A window will pop-out.
<div class="toccolours mw-collapsible mw-collapsed">
<div style="line-height:1.6;">Terminal Ouput</div>
<div class="mw-collapsible-content">
Welcome to pixie16 DQ
Removing Pixie16Msg.log
======= check PLX PCI 9054 ...
Found PLX PCI 9054 driver.
Found PLX PCI 9054 card.
PLX PCI 9054 card does not detected problem.
======= Loading Configuration file : Pixie16.config
##########################
Number of Module : 1
Slot Map : 2
Module ID : 0
--- configuration files for module-00 (slot-02)
ComFPGA : ./firmware/pixie16_revf_general_16b250m_35921_2017-01-09/firmware/syspixie16_revfgeneral_adc250mhz_r33339.bin
SPFPGA : ./firmware/pixie16_revf_general_16b250m_35921_2017-01-09/firmware/fippixie16_revfgeneral_16b250m_r36563.bin
DSP Code : ./firmware/pixie16_revf_general_16b250m_35921_2017-01-09/dsp/Pixie16DSP_revfgeneral_16b250m_r35921.ldr
DSP Var : ./firmware/pixie16_revf_general_16b250m_35921_2017-01-09/dsp/Pixie16DSP_revfgeneral_16b250m_r35921.var
DSP Par : test_ryan.set
======= Booting Pixie16 System ...
Init Ok
Booting module ...
------------ Module-0
Revision : 15
Serial Num : 1314
ADC Bits : 16
ADC sampling rate : 250
# channels : 16
Boot Ok
</div></div>

===== Pixie16.conf =====
<div class="toccolours mw-collapsible mw-collapsed">
<div style="line-height:1.6;">File content</div>
<div class="mw-collapsible-content">
###########################################
## Pixie16 Configuration File: ##
###########################################

### only for 1 crate for the moment

#Slot Number for Each Module
#This must start at 2 and proceed sequentially at the moment
# slot modID fpgaID
S 2 0 25
#S 3 1 25

##########################################################################################################
## FPGA Files ID ##
## F Y X File, where Y = fpgaID < 100 ##
## X = 0 (sys*.bin), 1 (fip*.bin), 2 (DSP*.ldr), 3 (DSP*.var), 4(*.set) ##
## Use this to save various FPGA files or to use a mixed board system ##
##########################################################################################################

#250MHz 16-bit
F 25 0 ./firmware/pixie16_revf_general_16b250m_35921_2017-01-09/firmware/syspixie16_revfgeneral_adc250mhz_r33339.bin
F 25 1 ./firmware/pixie16_revf_general_16b250m_35921_2017-01-09/firmware/fippixie16_revfgeneral_16b250m_r36563.bin
F 25 2 ./firmware/pixie16_revf_general_16b250m_35921_2017-01-09/dsp/Pixie16DSP_revfgeneral_16b250m_r35921.ldr
F 25 3 ./firmware/pixie16_revf_general_16b250m_35921_2017-01-09/dsp/Pixie16DSP_revfgeneral_16b250m_r35921.var
F 25 4 test_ryan.set
########################################################################################################################
#120 space buffer limit
########################################################################################################################
</div></div>

= Contact =
: Ryan Tang mailto:rtang@fsu.edu
: Sudarsan Balakrishnan mailto:sb25ce@fsu.edu

ANASEN

2026-02-24T21:31:29Z

Sbalak:

'''A'''rray for '''N'''uclear '''A'''strophysics and '''S'''tructure with '''E'''xotic '''N'''uclei ('''ANASEN''') is an active target detector. FSU, LSU, and TAMU are joined in the development of the project.

= First Generation =

NIM paper : https://doi.org/10.1016/j.nima.2017.07.030
PRC paper : https://doi.org/10.1103/PhysRevC.105.055806

= Second Generation =
[[File:Section of ANASEN with twisted wire configuration.jpg|500px|thumb|right|Section of ANASEN with twisted wire configuration]]

[[File:ANASEN simulation.png|500px|thumb|right|A simulation, showed the Anode wires, the Cathode wites, the SuperX3 Silicon Detector, and QQQ Silicon Detector. The simulation is generated with the analysis and simulation package. The black dot is the reaction vertex, the red dot is the hit position of the superX3, the blue wire is the anode, and the red wire is the cathode. The red line is the track, and the orange line is the reconstructed track only using the SuperX3 position, anode wire ID, and the cathode wire ID.]]

The main difference from the 1st generation is the Twisted Anode and Cathode wires.

== Gas Handling ==

== Basics Geometry ==

[[File:ANASEN PCB board for wires.png|400px|frameless|none|ANASEN PCB board for wires]]

There are 5 Layers on the radial position of the ANASEN.

{|class='wikitable'
! Structure !! Radius [mm]
|-
| ionizing wires || 23
|-
| Guard wires || 33
|-
| Anode wires || 38
|-
| Cathode wires || 43
|-
| SuperX3 Silicon || 88
|}

== Twisted Anode and Cathodes ==

=== Readout ===

== SuperX3 Silicon Detector Array==
[[File:SuperX3 Silicon detector.png|500px|thumb|right|A drawing of SuperX3 silicon detector]]
There are 24 Super-X3 double-sided Silicon detectors on the wall of the ANASEN. They are placed 88 mm away from the beam axis. Each of them has 75 mm X 40 mm sensitive area. Thus, the super-X3 covers a forward and backward angle of 40 deg.

=== Readout ===

On the front side, each strip has 2 readouts. On the back side, each strip has 1 readout for total energy.

== Tracking for the twisted wire configuration ==

[[File: Illustration of the beam reconstruction of ANASEN in twisted wire configuration.png|600 px|thumb|right|Illustration of the beam reconstruction of ANASEN in twisted wire configuration. (Left) First-order beam reconstruction. (right) uncertainty cone of the beam direction vector.]]

A beam trace consists of 5 parameters: 3 from a point <math> (x_0, y_0, z_0)</math> and 2 from the trace angle <math> (\theta, \phi)</math>. Thus, to reconstruct the beam trace, we need at least 5 pieces of information.

Suppose we know the position on the SuperX3, thus, we have 3 pieces of information <math> \vec{p_0} = (x_0, y_0, z_0)</math>. And We have 2 wires ID. Each wire and the <math>\vec{p_0} </math> will form a plan, the intersection line of the 2 plans will give us the first approximation of the beam trace.

Each wire is constructed from 2 points, let them be <math> \vec{a_i} </math> and <math> \vec{b_i} </math>, where <math> i </math> is the wire ID. The plane formed by the points <math> \vec{p_0}, \vec{a_i}, \vec{b_i} </math> has normal <math> \vec{n_i} = (\vec{p_0} - \vec{a_i}) \times (\vec{p_0} - \vec{b_i}) </math>. The vector for the line intersects between the 2 planes constructed by wire ID <math> i, j</math> and point </math> \vec{p_0}</math> is <math> \vec{N_{ij}} = \vec{n_i} \times \vec{n_j} : (\theta, \phi)</math>. Thus, the beam trace has an equation of <math> \vec{r} = \vec{p_0} + s \vec{N_{ij}} </math>, where <math> s </math> is the coordinate on the line.

=== uncertainty ===
Since the beam is not hit directly on the wires, but a distance <math> d_i </math> from the wire. This will rotate the plane on <math> \vec{p_0} </math> along the direction <math> \vec{a_i} - \vec{b_i} </math> by <math> \pm \arctan{d/l} </math>, where <math> l </math> is the perpendicular distance of the point <math> \vec{p_0} </math> and the line. This creates 2 additional planes with normal vectors that are rotated along the line by angle <math> \pm \arctan{d/l} </math>. The 4 additional planes form the uncertainty boundaries of the beam. In other words, the normal vector of the plane has uncertainty <math> \vec{n_i} \pm \vec{d_i} </math> that translates to the beam direction vector <math> \vec{N_{ij}} : (\theta \pm \delta\theta, \phi \pm \delta\phi) </math>.

Additional uncertainty comes from the position of the SuperX3.

== 3D model and Simulation ==

A simulation code and 3D model using CERN root can be found https://fsunuc.physics.fsu.edu/git/rtang/ANASEN_analysis/src/branch/master/Armory.

The core is the ANASEN class (ClassAnasen.h). This class contains the geometry (the endpoints of the anode and cathode wire, the edges of the SuperX3). The class can simulate the anode and cathode wire and the position at the SuperX3 with a track. Or, it can deduce the track using the SuperX3, anode, and cathode information.

A Monte Carlo simulation is constructed with the TransferReaction class (ClassTransfer.h).

== DAQ ==

The DAQ consists of 7 CAEN V1740D for the SuperX3, 3 CAEN V1735 for the proportional wires.

=== triggering ===

Any of the SuperX3 is the trigger. The trig-out of each V1740D will be sent to the input of a Fan-In-Fan-Out (FI-FO), the output of the FIFO will be sent to the TRG-IN of the V1735 digitizers.

=== Clock Zeroing and Time Sync ===

one of the V1740D is the master of the reference clock, all other digitizers are slave and use diasy chain CLK-IN CLK-OUT. We a proper PLL firmware settings for the clock, the clock phase of all digitizers would be the same.

To have the same time clock zeroing, we use a Gate generator to generate a clock-zeroing pulse. The pulse will be sent to a FI-FO, and the duplicated clock-zeroing pulse will be sent to all S-IN of the digitizers.

=== FSUDAQ setting ===

The [[CAEN_digitizer#FSUDAQ_(using_Qt6) | FSUDAQ]] is used for the DAQ control and data taking. {{Notice | need to fill}}

Radiation Safety

2025-12-04T20:30:05Z

Sbalak: Sbalak moved page Internal:Radiation Safety to Radiation Safety over redirect: Requested by Ingo

== General Procedures and Access to Accelerator Areas ==
Considerations of safety to personnel and minimization of risk to the accelerator have led to the following procedures,
which will be adhered to at all times:

1. When the accelerator is operating there will be a qualified operator and a second person in the Control Room, Computer Room Accelerator Room or
Target Room at all times. The only exception is for a short period (not exceeding 20 minutes) when one of the two will be away from the accelerator area.
During this period the remaining person will stay in the Control Room. There will be a person experienced in the "start up" and "shut down" of the source
on duty at all times.

2. Radiation dosimeters have to be worn every time a person enters the Tandem Hall, Linac Hall or Target Rooms, whether beam is present or not.

3.a. For beams with Z<4 (H,He,Li): Access to the Tandem Hall, the Linac Hall or/and the Target Rooms is not allowed while a beam with Z<4 is present in the area. Before a beam with Z<4 is allowed into an area, all persons have to leave the respective areas. The operator in charge has to verify that no person remains in the area before the doors are closed and the door interlock
alarms in the control room are activated. If a door is opened while the beam is present, the interlock system will automatically interrupt the beam at the LE end of the Tandem. The operator in charge will investigate the reason the doors were opened. Only after verifying that nobody is present in the protected area, the operator will close the affected door and re-activate the beam.

3.b. For beams with Z>=4: Access to the Tandem Hall, the Linac Hall and/or the Target rooms is only allowed while the Gamma and Neutron dose rates in the area are below 2.0 mrem/h. Before access is granted to a given area, the radiation levels will be verified at the installed area radiation monitors and with portable gamma and neutron radiation monitors,
which are placed near the location where a person works. Make entry to the log book with the results of the radiation levels and of the fact that access to the area was granted and to whom.
If radiation levels are above these limits, access to the areas is prohibited, all persons have to leave the affected areas and the operator in charge has to verify that no person remains in the areas before the doors are closed and the door interlock alarm in the control room is activated. The same rules as in 3.a apply in the case of access doors being opened.

4. In all cases, the Tandem HE shield door should be closed if a beam is being accelerated, independent of the radiation levels.

5. If the Tandem is being conditioned and/or levels of X-rays above 2.0 mRem/h are observed on the Tandem Area x-ray monitor, the Tandem shield door has to be closed, the LE Shield door has to be locked and the door alarm has to be activated in the control room.

6. Any time a beam delivery is initiated into the Tandem, the Linac Hall or the Target rooms, the operator will announce the intent to inject beam into a new area through the laboratory intercom before injecting it.

More detailed procedures addressing specific areas of the laboratory are listed below.

== Sources of Radiation around the Tandem ==

In the Tandem area the sources of radiation are the Tandem itself, the accelerated ion beam, activated material and the ion sources. In the target room there is the ion beam and the possibility of activated material.
=== Ion Sources ===
The high voltages involved with ion sources result in some x-rays during operation. For example, 2 mREM/h is typically measured near the injection magnet when the sputter source is operating at 120 kV (However, as with all high voltage equipment, a greater hazard by far is the possibility of electrocution).

=== Tandem ===
The terminal and acceleration tubes near the terminal can be a strong source of x-rays, depending on the operating conditions (terminal voltage, beam current, etc.). Radiation levels at the tank wall near the terminal of 100 mREM/h are not uncommon.
During Conditioning and whenever the radiation doses exceed 2.0 mRem/h, the Tandem access doors have to be closed and secured through the interlock alarm panel in the control room.

=== Accelerated Ion Beam ===
The main factors on which the level of radiation resulting from the accelerated ion beam depend have been mentioned above. As regards to the Tandem, little nuclear radiation (as opposed to x-rays) is to be expected at the Low Energy end – except for proton, deuteron and 3He, 4He beams. Significant levels of γ-rays and neutrons are to be generally expected at the High Energy end of the Tandem. And at various places along the beam path into the target room and to the experimenters target. Again, in general, higher currents, higher energies and lighter projectiles all tend to produce more radiation. Usually the strongest sources will be the entrance and exit slits of the 90◦ magnet.

'''Procedures'''
# Do not use the route past the H.E. end of the Tandem to access the Linac hall when there is a beam from the Tandem. If beam is being run in the Linac area, use the route through the target room 1. If beam is being run in the Target room 1, enter and exit the Linac through the door in the hallway.
# If radiation at the entrance to the H.E. end of the Tandem exceeds 2.0 mREM/h, the radiation door will be closed to prevent access.
# If radiation at the entrance to the Target Room 1 area exceeds 2.0 mREM/h, the radiation door will be closed to prevent access.

== Sources of Ionizing Radiation In the Linac ==

There are three distinct sources of radiation in the Linac area: the resonators, the accelerated ion beam, and any material (slits, etc.) which has been activated by bombardment with the ion beam.

=== Resonators ===
The superconducting resonators, which make up the Linac, produce x-rays when operating. The production of x-rays increases sharply with the R.F. field level at which the resonators are operating. For example, with a portable Geiger counter placed against the cryostat wall, the radiation from resonators running at 2 MV/m or less was found to be barely detectable (<0.04 mREM/h), while a resonator running at 2.25 MV/m gave 7 mREM/h measured against the cryostat wall.

In the “shadow” of the blue radiation shields, x-ray radiation is currently barely detectable. However, this is not the case during resonator conditioning, nor will it be the case as operating field levels of 3 MV/m are approached.

'''Procedure''': A series of Geiger counters have been placed under the cryostats to detect x-rays from the resonators. When the resonators are excited and emitting x-rays, these Geiger counters cause red lights mounted on top of the cryostats to illuminate.
# Whenever these lights are on, the walkway beside the cryostats, the tunnel under the cryostats and the tops and ends of the cryostats are out of bounds. Anyone needing to work in these areas with the resonators excited should use a Geiger counter to monitor the radiation level first.
# Whenever working in the shadow of the radiation shield, but near a resonator operating at “high field”, or being conditioned, use a Geiger counter to monitor the radiation level. If in doubt, use a Geiger counter.

=== Sources of radiation due to the accelerated ion beam or activated parts are the same as those described for the experimental areas ===

== Sources of Radiation in the Experimental Areas ==
=== Accelerated Ion Beam ===
One source of radiation is the accelerated ion beam, or rather, the nuclear reactions produced when the beam strikes various objects. The effective sources are therefore the various slits, apertures, beam stops, magnets boxes along the path of the beam, and finally the experimenters target chamber. Because large fractions of the ion beam are usually rejected at the entrance and exit slits of the 90<sup>◦</sup> magnet, these are usually the strongest sources. The intensity of radiation from a small source (such as a set of slits) fall off with distance according to the “inverse square law” – often the radiation level measured against a set of slits may be quite high, but is negligible a few feet away.

This beam-induced radiation consists mainly of fast neutrons and gamma-rays, and is properly detected with a neutron monitor and Geiger-counter respectively. Although often the radiation will be emitted roughly equally in all directions from the object being bombarded, in some cases the neutron radiation will be much stronger in the directions close to that of the ion beam, that is the neutrons are “forward peaked”. In general, because of their greater penetrating power, and because of their greater biological effectiveness, neutrons pose the greater hazard.

The amount of radiation produced depends on the type of beam, the beam energy, the beam current and on the material being bombarded, and so obviously varies greatly from experiment to experiment. In general, however, one can expect the radiation to increases as the beam energy increases and as the mass of the ion decreases. For example, the first Linac run used a ∼20 nA <sup>29</sup>Si beam at 95 MeV. Except near slits, the beam induced radiation was undetectable using the Geiger counter and neutron monitor. By contrast, a high-current 6Li or proton beam could produce levels of around 100 mREM/h (= 1 mSv/h).

'''Procedures''': A beacon on the switching magnets in either Target-room 1 or Target-room 2 will flash whenever there is an ion beam in the experimental hall (the beacon will come on when BS-1 or BS-2, respectively are open).
# When a beam is being run in the Linac area, the doors to the hallway will be locked from the inside, independent of the radiation levels. All access will be through the control room and target room 1 and is to be controlled by the accelerator operator.
# Once an experiment is running, a radiation survey will be carried out. If the radiation exceeds 2.0 mREM/h ( = 20 uSv/h), access to the experimental area is prohibited, the access doors to the Tandem, Target Room 1 and the Linac Hall/Target Room 2 will be closed and the door interlock will be activated while the beam is delivered.

=== Activated Material ===
The third source of radiation is the radioactivity induced in material (slits, targets, etc.) that has been bombarded by an ion beam for a period of time. The radiation, mainly γ-rays and β-rays, can be detected with a Geiger counter. The amount of activity depends on the type, energy and currents of the bombarding beams, on the material being bombarded, and the length of time for which it was bombarded, and the length of time elapsed since bombardment.

'''Procedure''': Use a Geiger counter before working on, or handling any device that has been bombarded by an accelerated ion beam. Be especially careful to contain any loose radioactive material. For proper disposal, contact Radiation Safety.

== Source of Ionizing radiation from RESOLUT ==
The operation of the RESOLUT radioactive-beam facility creates a combination of radiation sources, which are also present in other experiments and beam lines. Since it operates at higher beam intensity than most experiments, heightened precautions are advised. Radiation sources include X-rays from the superconducting resonator. Neutron and Gamma-radiation from the area of the production target, Neutron and Gamma-radiation from the area near the focal plane, where the primary beam is separated from the secondary beam products. Beam line parts may be activated during extended operation.

== Radiation Doses and Dosimetry ==
Radiation Dose: The statutory limit for “radiation workers” – anyone with a film badge, over 18, and not pregnant, is a dose of 1.25 REM (12.5 mSv) per quarter. This is the dose you would receive if while you were at work, you were continuously exposed to a radiation level of 2.5 milliREM (25 uSv) per hour throughout the 500 working hours of the quarter:

2.5 mREM/h * 500 h = 1.25 REM = 12.5 mSv

The dose limit for access to radiation areas at the Tandem-Linac lab is set at 2.0 mREM/h = 20 uSv/h.
However, there is no reason for anyone in the Tandem-Linac lab to receive even a small fraction of this dose. In fact, except under exceptional circumstances no one should need to receive a dose above the detection threshold of the film badge, namely 20 mRem (200 uSv) (the rough equivalent of a chest x-ray) in any quarter.

A very helpful radiation chart is here: https://xkcd.com/radiation/

== Apply for a Dosimeter ==

https://safety.fsu.edu/form/dosimetry.php

FSU Fox's Lab Wiki

2025-10-21T15:53:23Z

Sbalak:

= Introduction =

*This is the wiki for all details about FSU [[John D Fox]]' Lab for nuclear physics.
*The original manual can be found in [[:File:FoxManual20200415.pdf]].
*This wiki is <b><span style="color:red">OPEN TO PUBLIC</span></b>. Any confidential material should be put in <b>[http://elog.physics.fsu.edu elog]</b> or use internal pages.
*For [https://www.lsu.edu/physics/research/nuclear-physics.php Louisiana State University] users, please see [https://fsunuc.physics.fsu.edu/elog/2022_04_SPS_Blocker/2 this elog] for acessing the [[Fox's Lab Network]].
*New account may like to see the wiki syntax in [[Wiki_Edit_Cheat_Sheet | here]].

= Accelerator Operation Procedures =
● [[Radiation Safety]]

= Hardware =
{|style="width: 100%;"
|● [[Tandem Accelerator]] || ● [[LINAC]]
|-
|● [[SF6 Gas Handling System]] || ● [[Vacuum Systems]]
|-
|● [[Water Cooling System]] || ● [[He refrigerator]]
|-
|● [[Computers Network]] || ● [[Hardware/Cable Changes for Switching Target Rooms]]
|-
|● [[Ion Sources]]: This includes the [[Ion Sources#Sputter Source|Sputter Source]] and [[Ion Sources#RF Source|RF Source]] || ● [[Target Lab]]
|-
|● [[RESOLUT]]: In-flight radioactive beam facility
|-
|● [[Triton Beam Project]]: Multi-SNICS with Tritium Cathodes
|}

== Detector stations ==

{|style="width: 100%;"
|● [[ANASEN]] || ● [[CATRiNA]]
|-
|● [[Clarion2]] || ● [[ENCORE]]
|-
|● [[Gamma Station]] || ● [[RESONEUT]]
|-
|● [[Split-Pole Spectrograph]]
|-
|● [[Penning Trap]]
|}

== DAQ systems==
{|style="width: 100%;"
|● [[Pixie16 digitizer]] || ● [[CAEN digitizer]] (for 1st-gen)
|-
|● [[NSCL DAQ]] / [[NSCL SpecTcl]] || ● [[FSU SOLARIS DAQ]] (for CAEN 2nd-gen)
|-
|● [[Mesytec]] ||
|}

= Software & Resources =

{|style="width: 100%;"
|◆[[Online Resources]]: Web server, Elog, Grafana, Wiki, InfluxDB || ◆[[Data Server]]
|-
|◆[https://fsunuc.physics.fsu.edu/git/explore/repos Git repository] by Gitea || ◆[[Github repositories]]
|-
|◆[[SSH tunneling]] || ◆[[VNC viewer]]
|-
|◆[[Slack Channel]] || ◆[[gnuscope]]
|-
|◆[[SolidWorks]] || ◆[[Online Analysis]]
|-
| ◆[[Raspberry Pi Camera]] || ◆[[Python Iseg HV controller]]
|-
|◆[https://fsunuc.physics.fsu.edu/research/publication_list/ List of Publications] || ◆[[Ptolmey GUI]]
|}

= Layout of the Laboratory =
{|
|[[File:Lab Model.png|450px|frameless|none]] || [[File:JohnDFoxLayout.png|550px|frameless|none]]
|}


= External Collaborations =

* [[LSU Collaboration]]
* [[ORNL Collaboration]]
* [[TRIUMF Collaboration]]
* [[FRIB FDSi e21062]]
* [[FRIB SOLARIS Collaboration]]
* [[ANL MUSIC Collaboration]]

= Past Experiments =

[[List of Past Experiments]]

= Other Resources =

* [[Journal Club]]

* [[Help Call List for Evenings, Weekends, Holidays]]

* [[Laboratory Infrastructure]]

* [[Wiki Edit Cheat Sheet]]

* [[Guide for using this wiki]]

* [https://www.qr-code-generator.com/ QR code generator]

* [[Weekly Tandem Maintenance]]

* [[Tandem Maintenance Checklist Photos]]

* [[Source Sign Out Sheet]]

* [[Xilinx FPGA]]

* [[Gamma Calibration Sources]]

= Contacts =

{|
| for accelerator ||: Lagy Baby mailto:lbaby@fsu.edu <br>: Ingo Wiedenhoever mailto:iwiedenhoever@fsu.edu
|-
| for vacuum ||: Powell Barber mailto:pbarber@fsu.edu
|-
| for ion sources || : Brian Schmidt mailto:bschmidt@fsu.edu
|-
| for LINAC || : David Spinger mailto:dspingler@fsu.edu
|-
| for IT and DAQ ||: Sudarsan Balakrishnan mailto:sb25ce@fsu.edu
|-
|}

FSU Fox's Lab Wiki

2025-10-21T15:51:54Z

Sbalak:

= Introduction =

*This is the wiki for all details about FSU [[John D Fox]]' Lab for nuclear physics.
*The original manual can be found in [[:File:FoxManual20200415.pdf]].
*This wiki is <b><span style="color:red">OPEN TO PUBLIC</span></b>. Any confidential material should be put in <b>[http://elog.physics.fsu.edu elog]</b> or use internal pages.
*For [https://www.lsu.edu/physics/research/nuclear-physics.php Louisiana State University] users, please see [https://fsunuc.physics.fsu.edu/elog/2022_04_SPS_Blocker/2 this elog] for acessing the [[Fox's Lab Network]].
*New account may like to see the wiki syntax in [[Wiki_Edit_Cheat_Sheet | here]].

= Accelerator Operation Procedures =
● [[Radiation Safety]]

= Hardware =
{|style="width: 100%;"
|● [[Tandem Accelerator]] || ● [[LINAC]]
|-
|● [[SF6 Gas Handling System]] || ● [[Vacuum Systems]]
|-
|● [[Water Cooling System]] || ● [[He refrigerator]]
|-
|● [[Computers Network]] || ● [[Hardware/Cable Changes for Switching Target Rooms]]
|-
|● [[Ion Sources]]: This includes the [[Ion Sources#Sputter Source|Sputter Source]] and [[Ion Sources#RF Source|RF Source]] || ● [[Target Lab]]
|-
|● [[RESOLUT]]: In-flight radioactive beam facility
|-
|● [[Triton Beam Project]]: Multi-SNICS with Tritium Cathodes
|}

== Detector stations ==

{|style="width: 100%;"
|● [[ANASEN]] || ● [[CATRiNA]]
|-
|● [[Clarion2]] || ● [[ENCORE]]
|-
|● [[Gamma Station]] || ● [[RESONEUT]]
|-
|● [[Split-Pole Spectrograph]]
|-
|● [[Penning Trap]]
|}

== DAQ systems==
{|style="width: 100%;"
|● [[Pixie16 digitizer]] || ● [[CAEN digitizer]] (for 1st-gen)
|-
|● [[NSCL DAQ]] / [[NSCL SpecTcl]] || ● [[FSU SOLARIS DAQ]] (for CAEN 2nd-gen)
|-
|● [[Mesytec]] ||
|}

= Software & Resources =

{|style="width: 100%;"
|◆[[Online Resources]]: Web server, Elog, Grafana, Wiki, InfluxDB || ◆[[Data Server]]
|-
|◆[https://fsunuc.physics.fsu.edu/git/explore/repos Git repository] by Gitea || ◆[[Github repositories]]
|-
|◆[[SSH tunneling]] || ◆[[VNC viewer]]
|-
|◆[[Slack Channel]] || ◆[[gnuscope]]
|-
|◆[[SolidWorks]] || ◆[[Online Analysis]]
|-
| ◆[[Raspberry Pi Camera]] || ◆[[Python Iseg HV controller]]
|-
|◆[https://fsunuc.physics.fsu.edu/research/publication_list/ List of Publications] || ◆[[Ptolmey GUI]]
|}

= Layout of the Laboratory =
{|
|[[File:Lab Model.png|450px|frameless|none]] || [[File:JohnDFoxLayout.png|550px|frameless|none]]
|}


= External Collaborations =

* [[LSU Collaboration]]
* [[ORNL Collaboration]]
* [[TRIUMF Collaboration]]
* [[FRIB FDSi e21062]]
* [[FRIB SOLARIS Collaboration]]
* [[ANL MUSIC Collaboration]]

= Past Experiments =

[[List of Past Experiments]]

= Other Resources =

* [[Journal Club]]

* [[Help Call List for Evenings, Weekends, Holidays]]

* [[Laboratory Infrastructure]]

* [[Wiki Edit Cheat Sheet]]

* [[Guide for using this wiki]]

* [https://www.qr-code-generator.com/ QR code generator]

* [[Weekly Tandem Maintenance]]

* [[Tandem Maintenance Checklist Photos]]

* [[Source Sign Out Sheet]]

* [[Xilinx FPGA]]

* [[Gamma Calibration Sources]]

= Contacts =

{|
| for accelerator ||: Lagy Baby mailto:lbaby@fsu.edu <br>: Ingo Wiedenhoever mailto:iwiedenhoever@fsu.edu
|-
| for vacuum ||: Powell Barber mailto:pbarber@fsu.edu
|-
| for ion sources || : Brian Schmidt mailto:bschmidt@fsu.edu
|-
| for LINAC || : David Spinger mailto: dspingler@fsu.edu
|-
| for IT and DAQ ||: Sudarsan Balakrishnan mailto:sb25ce@fsu.edu
|-
|}

List of Past Experiments

2025-10-15T14:46:55Z

Sbalak:

{| class='wikitable'
! Start Date !! End Date !! Beam !! PI !! Device !! Reaction !! Elog Link !! Raw data Location !! Git/Analysis code
|-
| 2023-Jan-31 || 2023-Feb-07 || 9Be || Chris Esparza (FSU) || [[Split-Pole Spectrograph]] || 6Li(9Be,d) || [https://fsunuc.physics.fsu.edu/elog/2023_01_30_6Li/ 2023_01_30_6Li] || pauli:/mnt/data0/2023_02_9Be_6Li_d_jce18b
|-
| 2022-Nov-15 || 2022-Nov-22 || 10B || Eli Temanson (FSU) || [[RESONEUT]] || 10B(d,n) || || pauli:/mnt/data0/2022_11_10B_dn_est18c ||
|-
| 2022-Oct-10 || 2022-Oct-19 || 3He || Ashton Morelock (FSU) || [[CATRiNA]] || 16O(3He,p) || || Hades ||
|-
| 2022-Sep-26 || TBA || d || Spieker-Group (FSU) || [[CeBrA]] || 12C(d,pg); 49Ti(d,pg); 61Ni(d,pg) || [https://fsunuc.physics.fsu.edu/elog/2022_09_10_CeBrA/ ] || spieker-group computer || SPS_CEBRA_EventBuilder ||
|-
| 2022-Sep-06 || 2022-Sep-14 || d || Ashton Morelock (FSU) || [[CATRiNA]] || 16O(d,n) || || Hades ||
|-
| 2022-Jul-07 || 2022-Jul-08|| d || Anthony Kuchera (Davidson Colleges) || [[Split-Pole Spectrograph]] || 34S(d,p)35S || [https://fsunuc.physics.fsu.edu/elog/2022_07_REU_dp/ 2022_07_REU_dp] || pauli:/mnt/data0/2022_06_REU_dp ||
|-
| 2022-Jun-22 || 2022-Jun-30 || d || Paul (FSU) + other people from colleges || [[Split-Pole Spectrograph]] || 52Cr, 34S, 51V (d,p) || || pauli:/mnt/data0/2022_06_REU_dp ||
|-
| 2022-Jun-13 || 2022-Jun-17 || 14N || Jeff Blackmon (LSU) || [[ANASEN]] || || || ||
|-
| 2022-Jun-07 || 2022-Jun-10 || || Mitch Allmond (ORNL) || [[Clarion2]] || || || ||
|-
| 2022-May-31 || 2022-Jun-6 || 7Li || Eliens Lopez Saavedra (FSU) || [[Split-Pole Spectrograph]] || (7Li, t) || [https://fsunuc.physics.fsu.edu/elog/2022_06_11B_alpha_transfer/ 2022_06_11B_alpha_transfer] || pauli:/mnt/data0/2022_06_11B ||
|-
| 2022-May-23 || 2022-May-25 || 3He, d || Gemma Wilson (LSU) || [[Split-Pole Spectrograph]] || (3He,d) and (d,p) reaction to populate mirror nuclei || [https://fsunuc.physics.fsu.edu/elog/2022_05_mirror_transfer/ 2022_05_mirror_transfer] || pauli:/mnt/data0/2022_05_LSU_dp ||
|-
| 2022-May-10 || 2022-May-19 || Cock-tail || Vandana || FRIB || [[FRIB_FDSi_e21062]] || [https://fsunuc.physics.fsu.edu/elog/2022_05_e21062_FRIB/ 2022_05_e21062_FRIB/ ] || pauli:/mnt/data0/2022_05_e21062 || [https://fsunuc.physics.fsu.edu/git/rtang/FRIB_e21062 FRIB_e21062]
|-
| 2022-May-9 || 2022-May-13|| || Gordon McCann || [[Split-Pole Spectrograph]] || || [https://fsunuc.physics.fsu.edu/elog/2022_05-06_3He_2H/ 2022_05-06_3He_2H ] || pauli:/mnt/data0/2022_05_10B_3Hea_gwn17 ||
|-
|2022 || 2022 || || Catherine Deibel (LSU) || [[Split-Pole Spectrograph]] || || [https://fsunuc.physics.fsu.edu/elog/2022_04_SPS_Blocker/ 2022_04_SPS_Blocker] || ||
|-
|2022- || 2022 || || Eli Temanson|| [[RESOLUT ]] || || [https://fsunuc.physics.fsu.edu/elog/2022_12Cdn13N/ 2022_12Cdn13N] || pauli:/mnt/2022_04_12C_dn_est18c ||
|-
|2022-Mar-8 || 2022-Mar-18 || 7Li || Soumik Bhattacharya || [[Clarion2]] || 64Ni(7Li, pn)69Zn || [https://fsunuc.physics.fsu.edu/elog/202203_64Ni_7Li/ 202203_64Ni_7Li] || ||
|-
|2022 || 2022 || || Mitch Allmond (ORNL) || [[Clarion2]] || || || ||
|-
|2022 || 2022 || || Catur Wibisono || [[Clarion2]] || 16O(18O, p)32P || || nucx8:/data1/202112_16O_clarion2 ||
|-
| || || || || || || || nucx8:/data1/ZnMar2022 ||
|-
| || || || || || || || nucx8:/data1/Dec2021_16O||
|-
| || || || || || || || nucx8:/data1/Clarion2_calib ||
|-
| || || || || || || || nucx8:/data1/Aug2021_16O ||
|-
| || || || || || || || nucx8:/data1/NOv2021_Li7 ||
|-
| || || || || || || || nucx8:/data1/40K_decay ||
|-
| || || || || || || || nucx8:/data1/Apr2020_11B ||
|-
| || || || || || || || nucx8:/data1/Aug2021_13C ||
|-
| || || || || || || || nucx8:/data1/248CmFission ||
|-
| || || || || || || || nucx8:/data1/A127adSi29 ||
|}

User talk:Rtang

2025-10-09T15:41:33Z

Sbalak: Created page with "Hello Ryan - Thank you for the welcome, I just saw your message. Best, Sudarsan."

Hello Ryan - Thank you for the welcome, I just saw your message. Best, Sudarsan.