Timepix3 Telescope Setup

These are the initial notes on how the telescope has been set up, carried out in the ECAL lab before moving to the NA (2nd Sep. 2015)

Telescope server

After restart of the server, do once:

  • sudo modprobe ni_usb_gpib (if necessary)
  • sudo gpib_config
  • sudo chmod a+rw /dev/gpib0
  • Then start the procedure below.
Start the telescope DAQ:
  • from pclcd25: ssh -Y telescope@clictelescope
  • To start processes for the TLU and telescope DACs
    • cd SPIDR/software/Telescope/Scripts
    • ./startTelescope.sh
  • To run the run control Gui:
    • cd SPIDR/software/Telescope/RunControl/RCGui
    • make (if any changes made)
    • python hv_server.py (for high voltage) or dummy_hv_server.py
    • python serial_server.py (for motion stage, not used for Investigator!)
    • ./RCGui
If no module "ni_usb_gpib" is available for the current kernel version, it has to be recompiled:
  • Go to "Downloads/linux-gpib-4.1.0" (or download the latest linux-gpib package)
  • ./configure
  • make
  • sudo make install
  • Check that your new kernel has the modulesby checking if this directory exists:
  • ls -l /lib/modules//gpib
  • Then continue with above steps of loading the module.
To move the telescope box using the motion stages:

Timepix3 data taking with Spidrman for finding beam spot etc.

  • ssh skulis@pcvertextb (same password as user vertextb)
  • cd ~/spidr/software/trunk/python
  • source spidr/bin/activate
  • ./ui/spidrman.py
  • Menu: File -> Connect -> Spidr. File -> Load Configuration. Select last configuration of the connected device.
  • Checke Threshold and change as appropriate (for example, should be 1230 for W2_J5)
  • Select for example ToT tab. Open shutter by clicking on "On". Change decay in visualisation tab to 99. Look at rate.
  • If tabs are missing: enable them in "View".

SPIDR board communication

The IP of each SPIDR board is determined by the chipboard plugged in to FMC connection 0 (the FMC connector closest to the 10 Gbit ethernet). The default IP is 192.168.100.10. To allow several SPIDR to be connected to the same computer, each of the boards should be assigned a separate IP. This assignment of IPs to chips is:

Chip ID IP
W13 E3 192.168.100.10
W13 G2 192.168.101.10
W13 G3 192.168.102.10
W13 J5 192.168.103.10
The ethernet ports by default are set to the IP address 192.168.10X.1, for connection ethX. Therefore in principle the SPIDR with chipboard W13 E3 should be connected to eth0. If this is not the case, then the network manager on the linux machine must be used to manually change the IP of the port (ipconfig will be overridden - do not use it!).

-- DanielHynds - 2015-09-02

SPIDR board reconfiguration and monitoring

The SPIDR boards can be reprogrammed and monitored remotely. The JTAG server listens on the default port 3121. The JTag chains monitoring UART mapping is the following:

Name of the JTag chain UART device Interface assigned to the given SPIDR card IP
Digilent/210203A0236FA /dev/LeonSerial102 eth0 192.168.102.10
Digilent/210203A023ADA /dev/LeonSerial103 eth5 192.168.103.10
Digilent/210203A02F16A /dev/LeonSerial101 eth11 192.168.101.10
Digilent/210203A02EF0A /dev/LeonSerial100 eth7 192.168.100.10
-- AdrianFiergolski - 2016-04-28

Telescope planes order in z:

Upstream

  • W0013_D04
  • W0013_E03
  • W0013_G02
DUT
  • W0013_G03
  • W0013_J05
  • W0013_L09
Downstream

PastedGraphic-2.png</verbatim>

InvestigatorDataTaking

HDMI to RJ45 cable (trigger system)

How to change to new run directory for new run period

  • Example: Preparing for August 2018 beam period:
    • new directory /data/tbAugust2018, /data/tbAugust2018/data, /data/tbAugust2018/log, /data/tbAugust2018/clicpix2, /data/tbAugust2018/atlaspix
    • copy directory /data/tbJune2018/config to /data/tbAugust2018/
    • changing DAQFilePath to /data/tbAugust2018/config and logpath to /data/tbAugust2018/data in /home/telescope/SPIDR/software/Telescope/RunControl/RCGui/config/test.cfg
    • Changing in ./home/telescope/SPIDR/software/Telescope/DAQ/Tpx3daq.cpp: #define CFG_PATH "/data/tbAugust2018/config" #define DATA_PATH "/data/tbAugust2018/data" #define LOG_PATH "/data/tbAugust2018/log"; run "make" in this directory to recompile

Copy data to EOS (updated 04/2018)

  • on clictelescope, make CVMFS available and then start the Docker image:
    • ls /cvmfs/clicdp.cern.ch/DIRAC
    • sudo docker run -i --rm -t -v ~/.globus:/root/.globus -v /:/root/local_machine -v /cvmfs:/cvmfs gitlab-registry.cern.ch/clicdp/ilcdirac/ilcdirac-ci-images:slc6 /bin/bash
  • In the the container do:
    • cd
    • source /cvmfs/clicdp.cern.ch/DIRAC/bashrc
    • dirac-proxy-init
  • password is similar as for the machine. However digits and character blocks changed places and number is increased by 1000. (untested: If it fails, try dirac-admin-get-CAs followed by dirac-proxy-init)
  • Make sure the destination folder on EOS exists - if not, create it like this:
    • dirac-dms-filecatalog-cli
    • cd /ilc/user/c/clictel/
    • mkdir CERN_TB_Month_20XX
    • exit
  • Use the following command to synchronize the local test beam directory to the grid space:
    • dirac-dms-directory-sync local_machine/__PATH_TO_TB_DATA__ /ilc/user/c/clictel/CERN_TB_Month_20XX CERN-DST-EOS
  • You have to prepend local_machine before the path since this is the mount point.
  • dirac-dms-directory-sync can be parallelized by using the flag -j same as in make.
  • Files cannot be overwritten. If a file changed since the last sync, it has to be removed manually, otherwise the synchronization will not complete. This happens mostly to the run logfile, e.g.:
    • dirac-dms-remove-files /ilc/user/c/clictel/CERN_TB_Month_20XX/data/global_log.txt
  • The Docker container can be run in the background by simply detaching form it with CTRL+P CTRL+Q. To reattach, get the list of running containers via "sudo docker ps" and then run "sudo docker attach "

Verify Copied Data

  • EOS does not support has sums currently, so simply check for the files and their size, e.g. run the following command on the telescope server and on EOS (e.g. via lxplus)
  • find . -type f -printf "%p %s\n" | sort > ~/files_on_EOS.txt
  • find . -type f -printf "%p %s\n" | sort > ~/files_on_TEL.txt
  • diff ~/files_on_EOS.txt ~/files_on_TEL.txt
  • If there's no difference (or only zero-byte log files, which are not copied to EOS) everything is in order.
Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng PastedGraphic-2.png r1 manage 99.2 K 2017-05-11 - 09:25 DominikDannheim Telescope planes
Edit | Attach | Watch | Print version | History: r23 < r22 < r21 < r20 < r19 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r23 - 2018-11-20 - SimonSpannagel
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CLIC All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback