Tue Apr 19 19:09:25 2016, James Bynes, Instructions, Obtaining data from XRM development boardstack
|
Here are the instructions to obtain data from XRM boardstack. This has currently been tested with 1 carrier board, but little modifications will allow multiple
boards. Currently the data
taken is raw data, a pedestal extractor is currently under works.
|
Sun May 1 01:45:45 2016, James Bynes, Instructions, Setting up Ubuntu 14.04 to take data from XRM boardstack
|
This ELOG shows how to obtain data from XRM boardstack from a fresh install of Ubuntu 14.04
[B]
i) Freshly install Ubuntu 14.04[/B]
|
Tue May 3 08:11:06 2016, M. Andrew, documentation, what was done in January 2016 19x
|
Here is a data dump of everything that happened on the asus laptop while getting the laste 2015 / early 2016 incarnation of the XRM tested before being
delivered to KEK on the weekend of January 24th. Everything was done in bash and the firmware only addressed one carrier at a time, so the purpose
of this elog entry is simply to archive the information. |
Sat May 7 20:52:24 2016, James Bynes III, Instructions, Plotting data from XRM boardstack
|
[SIZE=3]The following package will allow you to parse binary data from TargetX and output pedestal subtracted plots as well as a separate pedestal subtract
text file in tabbed column format.[/SIZE]
|
Tue May 17 16:03:12 2016, Gary Varner, report, compilation log
|
Following up on James` suggestion, have posted transcript of compilation log below.
Not sure if there is anything should worry about here.
Strangely, the ton of warnings saw the first time I tried went away... |
Wed May 18 01:13:55 2016, Chris Ketter, Gary Varner, analysis, first data sets 6x
|
After getting data logging earlier in the day, Chris installed the detector and we took a look at data.
The amp board gain is set to lowest setting. Still, when looking at pedestal subtracted data, the preamps were picking up clear noise.
This may have impacted the pedestals, which were still noisy with preamps off, but long cables/detector connected. |
Wed May 18 21:32:21 2016, Gary Varner, noise during RF conditioning(?), carrier 0, asic 0   
|
There is bursts of noise seen in the longer record lengths (1).
Some channels are quieter (2), though all see hints of 500MHz (3).
Channels 6&7 have pick-up that looks very much like 500MHz. (4). |
Thu May 19 02:08:09 2016, Gary Varner, analysis, statistics during RF on run   
|
Summary statistics for short [1 run @ 64 windows] (1) and longer [100x] (2) show rather similar responses, where channels 6&7 are clearly noisier,
while all others are in decent agreement.
It becomes clearer in the larger statistics that the distribution looks bimodal. This could be due to amplifier chain instability/oscillation. |
Thu May 19 13:49:23 2016, Gary Varner, data taking problem report, morning 20-MAY-2016 JST
|
After beam came back on overnight, wanted to get a background reference data set.
However when trying to log data via GUI, the trigger number wasn't incrementing, nor a non-zero .bin file being created.
Restarted the GUI and confirmed that registers could be read, but still no response to triggers. |
Thu May 19 19:48:14 2016, John Flanagan, Gary Varner, network documentation, APC network configuration
|
host name : psxrd08
IP address : 172.19.62.89
MAC address: 00:c0:b7:b8:94:f9
> SuperKEKB ネットワーク
登録申請を受け付けました。
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>
申請日 : 2016-05-19 15:49:00
> 申請内容 : 新規
> 登録者名 |
Thu May 19 23:01:35 2016, Gary Varner, analysis, first try 
|
Started a 1Hz run and let it run, the tail end of which might have had the detector in the xray beam.
Stopped run, but the GUI crashed when trying to close the very large (>1.5k event) run.
Large files bit unwieldy to work with, but first time series plot for channel 0 attached (1). |
Fri May 20 16:08:46 2016, John Flanagan, Gary Varner, hardware documentation, APC and PDU AC-power settings
|
Controlling remotely via separate laptop, with connections on the 2 subnets .0 and .1
APC is currently Default IP 192.168.1.201
apc/apc |
Fri May 20 23:30:23 2016, Chris Ketter, information, Configuration of XRM   
|
Attachment 1 is a block diagram of the XRM setup for the Low Energy Ring (LER). Physically, this is located underneath the right wing of Fuji Hall,
tens of meters away from the crossing point of the beams (180deg around ring from interaction point). Directly upstairs is the optics hut where the readout
PC is located. |
Sat May 21 01:02:13 2016, John Flanagan, Gary Varner, run report, First Light! 
|
After a battle to sort out the networking issues with the APC (on loan) and PDU, able to get all working fine, and logged in separate Elog.
The ability to power cycle XRM proved essential as periodically something is happening in the tunnel which causes the network connections (both
for XRM and APC) to get cycled. |
Tue Jun 18 11:29:30 2019, M. Andrew, documentation, raspberry pi
|
to install:
cd
mkdir -p build |
Mon Sep 30 09:36:16 2019, M. Andrew, documentation, measurements of accelerator clock and revolution marker  
|
Following Nuclear Instruments and Methods in Physics Research A 499 (2003) 138–166, we know that the distributed accelerator clock is 508.8875
MHz (508.91 MHz measured) and that there are 5120 RF buckets. So the revolution marker should come at 99.3921 kHz (99.39 kHz measured).
Furthermore, it should be noted that the revolution marker is a 50% duty cycle NIM signal and the accelerator clock is about 600 mVpp. |
Mon Sep 30 10:59:35 2019, M. Andrew, documentation, Althea/RAFFERTY
|
The firmware running on Althea/RAFFERTY https://github.com/mzandrew/hdl/blob/master/verilog/src/mza-test032.pll_509divider_and_revo_encoder_plus_calibration_serdes.althea.v
takes a 508.8875 MHz clock input, and uses a PLL to generate 4 phases of a 127.221875 MHz clock (input/4). Then it uses a 4-bit iserdes on the input
clock to register the phase of the revolution marker on the output clock. It takes about 1 second worth of these and populates a histogram. |
Thu Oct 17 08:06:01 2019, M. Andrew, documentation, what was brought to KEK (2019-09)   
|
photographic record of equipment delivered to KEK in September |
Thu Oct 17 09:28:32 2019, M. Andrew, documentation, what was installed for HER (2019-09)
|
|
Tue Jan 22 07:56:56 2019, M. Andrew, documentation, instructions for setup, compiling and data acquisition
|
File XRM.instructions.txt gives the 2019-era details on running the XRM. |
Fri Oct 4 08:55:23 2019, M. Andrew, documentation, instructions for pdu control
|
Control of the power distribution unit (pdu) is done from xrd04rp2. The script pdu.sh is in the $PATH.
to get pdu status:
|
Fri Oct 4 10:04:12 2019, M. Andrew, documentation, instructions for programming boardstack
|
Programming the boardstack is done from xrd04rp2. The script boardstack.sh is in the $PATH.
To make sure the svn repo is up to date, run svnup.sh (also in $PATH) before programming:
|
Fri Oct 4 10:18:44 2019, M. Andrew, documentation, instructions for checking boardstack status and temperature
|
This is done from sixrmlaptop02 (a.k.a. balrog017). These scripts are not in the $PATH, so you must cd to ~/build/uh-svn-repo/trunk/software/b2l/scripts_dev
before running them.
|
Fri Oct 4 10:33:53 2019, M. Andrew, documentation, instructions for boardstack configuration
|
This is done from sixrmlaptop02 (a.k.a. balrog017). These scripts are not in the $PATH, so you must cd to ~/build/uh-svn-repo/trunk/software/b2l/scripts_dev
before running them.
|
Tue Oct 29 09:27:14 2019, M. Andrew, documentation, instructions on taking a full revolution of waveforms 
|
This may be useful when steering the sensor into x-ray beam for instance.
First, ensure the boardstack is powered, programmed and configured.
|
Wed Oct 30 15:23:57 2019, M. Andrew, documentation, sample waveform files 8x
|
A sample waveform file from the reference boardstack at UH and the boardstack in the HER at KEK are attached (in tar bzip2 file).
The format of the files is as in the attached spreadsheet (start from cell C29 for the waveform data).
|
Mon Nov 18 13:30:44 2019, M. Andrew, documentation, first light!
|
A video of a time series of waveforms for first light (recorded 2019-11-15) is posted here:
https://www.youtube.com/watch?v=IVVIYGwrBqI |
Wed Nov 6 13:35:45 2024, M. Andrew, documentation, sample waveform files  
|
Attached is a sample datafile (in raw, root and waveforms formats) showing self-pulser data taken in April 2024, along with the most recent version of the
xrm.py script. |
Tue Nov 5 11:47:36 2019, M. Andrew, documentation, instructions on taking data around a desired RF bucket
|
This mode of operation is useful when you've located your RF bucket of interest and want to focus on taking data at that position.
First, ensure the boardstack is powered, programmed and configured.
|
Mon Nov 18 14:06:31 2019, M. Andrew, documentation, config file
|
Below is a list of all possible config file options that are interpreted/used by the xrm.py code. The filename is ".config" and it must be located in "${HOME}/build/uh-svn-repo/trunk/software/b2l/scripts_dev/"
For svn checkouts where (re)parsing & (re)plotting data is going to be the only valid operation, be sure to set fake_it="yes" and xrm_mode="parse" among |
Mon Feb 3 08:22:06 2025, M. Andrew, documentation, config file
|
Attached is the updated .config file for 2025. |