Difference: IFAEPixel (1 vs. 72)

Revision 722019-11-08 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel


Line: 156 to 156
 yarr software: https://github.com/Yarr/Yarr

yarr firmware: https://github.com/Yarr/Yarr-fw/blob/master/syn/xpressk7/README.md

Changed:
<
<

>
>
 

RD53A

see TWIKI: https://twiki.cern.ch/twiki/bin/viewauth/RD53/RD53ATesting

Line: 255 to 255
 
  • To bring your release up to date with the latest repository release:
    svn update
    svn update filename
    svn status -u (to see what the update will do, but without doing it)
  • To checkout a certain rev of a file:
    svn up -r revnumber filename
Added:
>
>

ITk Modules

  • ITk Module PDR indico (22 Oct 2019)
 

IBL Modules

Revision 712019-10-16 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel


Line: 174 to 174
 
  • EUtelescope: See the instructions to compile the Eudet software in the PIC or lxplus (UPDATED):
Deleted:
<
<
<!--/twistyPlugin twikiMakeVisibleInline-->
 Official instructions: http://eutelescope.web.cern.ch/content/installation

Official ITk testbeam instructions: https://twiki.cern.ch/twiki/bin/viewauth/Atlas/ITkPixelTestBeamReconstruction

Line: 314 to 312
 
    • newtxtext.sty
    • newtxtt.sty
Added:
>
>

Radiation source usage

  • There are two sources of the pixel group: an exempted Sr-90 one (37kBq), and a high activity Sr-90 one (3.7MBq) AN-7171.
  • There are also Am-241 and Cd-109 (exempted, but check)
  • The procedure to use the sources is:
    • Take source from safe box and put an entry in the log but with: name of the source, the date, if it is in or out (and destination if out) and the person.
    • If it is an exempted source: if you are using the source every day of the week, there is no need to bring it back to the bunker every day when you leave, so you lock it in the safe of the gray room and bring it to the bunker only for the week end. If you have to run tests that last more than one day, you can leave the source in the gray room with the area properly signaled as Controlled Area. But for a single use, it is best to bring the source back to the bunker after use.

 
META FILEATTACHMENT attachment="Screen_shot_2014-09-30_at_10.12.53_AM.png" attr="" comment="" date="1412065566" name="Screen_shot_2014-09-30_at_10.12.53_AM.png" path="Screen_shot_2014-09-30_at_10.12.53_AM.png" size="512718" user="sgrinste" version="1"
META FILEATTACHMENT attachment="FE-I4B_V2.3.pdf" attr="" comment="" date="1444742260" name="FE-I4B_V2.3.pdf" path="FE-I4B_V2.3.pdf" size="9468068" user="sgrinste" version="1"

Revision 702019-04-05 - StefanoTerzo

Line: 1 to 1
 

IFAE Pixel


Line: 177 to 178
  Official instructions: http://eutelescope.web.cern.ch/content/installation
Changed:
<
<
How to install at the pic or lxplus:
#source the most up-to-date atlas software (you can put this in your ~/.bashrc)
export ATLAS_LOCAL_ROOT_BASE=/cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase
alias setupATLAS='source ${ATLAS_LOCAL_ROOT_BASE}/user/atlasLocalSetup.sh'
setupATLAS --quiet
localSetupROOT

#you also need the latest cmake and git
lsetup cmake
lsetup git
# then define your working area:
export ILCSOFT=/directory/where/you/want/to/install
cd $ILCSOFT
# get the ilc installer (by now you can find it in stefano's github)
git clone --branch dev-cpp14 https://github.com/terzo/iLCInstall.git
# check the versions of the software to install, put "v1.8.0" in Eudaq_version
vim $ILCSOFT/iLCInstall/releases/v01-19/release-versions.py
# install and compile
cd $ILCSOFT/iLCInstall
./ilcsoft-install -i examples/eutelescope/release-atlascvmfs-lxplus.cfg
>
>
Official ITk testbeam instructions: https://twiki.cern.ch/twiki/bin/viewauth/Atlas/ITkPixelTestBeamReconstruction
 
Changed:
<
<
<!--/twistyPlugin-->
>
>
Installation script: https://cernbox.cern.ch/index.php/s/Mi6ijh2j8BYofqt
 

AIDA-1

Revision 692018-06-20 - StefanoTerzo

Line: 1 to 1
 

IFAE Pixel


Line: 179 to 179
  How to install at the pic or lxplus:
Changed:
<
<
# your working area:
>
>
#source the most up-to-date atlas software (you can put this in your ~/.bashrc) export ATLAS_LOCAL_ROOT_BASE=/cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase alias setupATLAS='source ${ATLAS_LOCAL_ROOT_BASE}/user/atlasLocalSetup.sh' setupATLAS --quiet localSetupROOT

#you also need the latest cmake and git lsetup cmake lsetup git # then define your working area:

 export ILCSOFT=/directory/where/you/want/to/install cd $ILCSOFT
Changed:
<
<
# get the ilc installer
>
>
# get the ilc installer (by now you can find it in stefano's github)
 git clone --branch dev-cpp14 https://github.com/terzo/iLCInstall.git # check the versions of the software to install, put "v1.8.0" in Eudaq_version vim $ILCSOFT/iLCInstall/releases/v01-19/release-versions.py
Line: 190 to 199
 cd $ILCSOFT/iLCInstall ./ilcsoft-install -i examples/eutelescope/release-atlascvmfs-lxplus.cfg
Changed:
<
<

</>
<!--/twistyPlugin-->
>
>
</>
<!--/twistyPlugin-->
 

AIDA-1

Revision 682018-06-20 - StefanoTerzo

Line: 1 to 1
 

IFAE Pixel


Line: 40 to 40
 
Changed:
<
<
>
>
 
Changed:
<
<
>
>
 
Line: 148 to 148
  HSIO board at SR1 used during Sept 2014 tests for AFP:
Added:
>
>

YARR

see instrutions at: https://yarr.readthedocs.io/en/latest/

yarr software: https://github.com/Yarr/Yarr

yarr firmware: https://github.com/Yarr/Yarr-fw/blob/master/syn/xpressk7/README.md

RD53A

see TWIKI: https://twiki.cern.ch/twiki/bin/viewauth/RD53/RD53ATesting

 

Testbeams

List of 3D/AFP testbeams.

Testbeam Reconstruction

Changed:
<
<
  • Judith reconstraction framework for FEi4 based telescopes:
>
>
  • Judith reconstraction framework for FEi4 based telescopes: (TO BE UPDATED)
 
Changed:
<
<
  • EUtelescope: See the instructions to compile the Eudet software in the PIC:
>
>
  • EUtelescope: See the instructions to compile the Eudet software in the PIC or lxplus (UPDATED):
 
<!--/twistyPlugin twikiMakeVisibleInline-->
Deleted:
<
<
These instructinos are mainly to compile the OnlineMonitor, though the last part shows how to compile everything.
 Official instructions: http://eutelescope.web.cern.ch/content/installation
Changed:
<
<
How to install at the pic:
>
>
How to install at the pic or lxplus:
 
# your working area:
Changed:
<
<
export ILCSOFT=/nfs/at3/scratch/sgrinstein/eudet_sl6
>
>
export ILCSOFT=/directory/where/you/want/to/install
 cd $ILCSOFT
Changed:
<
<
# co the ilc installer svn co https://svnsrv.desy.de/public/ilctools/ilcinstall/tags/v01-17-03-eutel ilcinstall_v01-17-03-eutel # edit the versions to install, put "trunk" in Eudaq_version vim $ILCSOFT/ilcinstall_v01-17-03-eutel/releases/v01-17/release-versions.py
>
>
# get the ilc installer git clone --branch dev-cpp14 https://github.com/terzo/iLCInstall.git # check the versions of the software to install, put "v1.8.0" in Eudaq_version vim $ILCSOFT/iLCInstall/releases/v01-19/release-versions.py
 # install and compile
Changed:
<
<
cd $ILCSOFT/ilcinstall_v01-17-03-eutel ./ilcsoft-install -i examples/eutelescope/release-standalone.cfg

NOTE 16 December 2013:

<span style="color: red;">
We had the following error when compiling at SL6 at301:
/nfs/atlas-data06/scratch/sgrinstein/eudet_sl6b/v01-17-03/root/5.34.05/ROOT/net/netx/src/TXNetFile.cxx:59:38: error: XrdClient/XrdClientConn.hh: No such file or directory
So, we changed the ROOT version in
$ILCSOFT/ilcinstall_v01-17-03-eutel/releases/v01-17/release-versions.py
to: 
ROOT_version = "5.30.01"
(See my working area: /nfs/pic.es/user/s/sgrinstein/scratch/eudet_sl6b)
However, the best solution might be to ask the admins to add the XrdClient/XrdClientConn.hh header file to: /usr/include/xrootd
</span>

# you will see most of the relevant executables at:
ls $ILCSOFT/v01-17-03/Eutelescope/v00-09-01/external/eudaq/trunk/bin/

However, the OnlineMonitor is missing!

cd $ILCSOFT/v01-17-03/Eutelescope/v00-09-01
source build_env.sh
cd $ILCSOFT/v01-17-03/Eutelescope/v00-09-01/external/eudaq/trunk
make clean &amp;&amp; make -j USE_LCIO=0 USE_EUTELESCOPE=0

Now you should have the OnlineMonitor:
cd $ILCSOFT/v01-17-03/Eutelescope/v00-09-01/external/eudaq/trunk/bin
./OnlineMon.exe -f ~/scratch/June2013_DESY/run012602.raw

The instructions below should compile the full eudaq software:

Tried them on 18 Dec 2013 on at301 (/nfs/at3/scratch/sgrinstein/eudet_sl6b/, SL6, with ROOT 5.30.01) and they worked (they compiled, but I did not run the executables yet).

#environment
cd v01-17-03/Eutelescope/v00-09-01
source build_env.sh
cd external/eudaq/trunk
# remove Timepix detector
rm main/src/Timepix*
rm main/include/eudaq/TimepixDummyProducer.hh
# compile first with LCIO and EUTELESCOPE flags off
make clean ; make -j USE_LCIO=0 USE_EUTELESCOPE=0
# regenerates all make files of EUTelescope project.
cd ../../../build
cmake ..
# build EUtelescope
make install
# compile with LCIO and EUTELESCOPE flags on
cd -
make clean ; make -j USE_LCIO=1 USE_EUTELESCOPE=1
# rebuild EUtelescope
cd ../../../build
make install
>
>
cd $ILCSOFT/iLCInstall ./ilcsoft-install -i examples/eutelescope/release-atlascvmfs-lxplus.cfg
 
<!--/twistyPlugin-->
Line: 250 to 209
 Examples:
Changed:
<
<
>
>
 
  • Create a new project:
    • go to the ifaepix page and click on the "New Project" button
    • insert the project name (ex. new_project) and click "Create Project"
Changed:
<
<
>
>
 
    • ...or follow the instructions on screen relative to your needs
  • Upload existing project:
    • go to the ifaepix page and click on the "New Project" button
    • insert the project name (ex. my_project) and click "Create Project"
Changed:
<
<
    • go in the folder of your existing project: cd my_project
    • initialise an empty repository: git init
    • link your project to the remote git repository: git remote add origin https://$CERN_USER@gitlab.cern.ch/ifaepix/my_project.git
    • add all the files in the folder to the local git repository: git add .
    • commit the changes: git commit -m"this is a comment fot the first commit of my project"
    • upload all the chages of the added files in the local repository to the remote repository: git push -u origin master
>
>
    • go in the folder of your existing project: cd my_project
    • initialise an empty repository: git init
    • link your project to the remote git repository: git remote add origin https://$CERN_USER@gitlab.cern.ch/ifaepix/my_project.git
    • add all the files in the folder to the local git repository: git add .
    • commit the changes: git commit -m"this is a comment fot the first commit of my project"
    • upload all the chages of the added files in the local repository to the remote repository: git push -u origin master
 
  • Typical workflow (good for small changes or simple projects with few people modifing the code at the same time):
Changed:
<
<
    • check the status of the repository: git status
    • update to the last version of the code: git pull origin master
    • make changes to the files (or create new files) (ex. changed_file.cpp, changed_file.h, new_class.h )
    • add the chenged files: git add changed_file.cpp changed_file.h new_class.h
    • commit changes: git commit -m"added new functionality for bla bla bla"
    • remove crappy file: git rm crappy_file.cpp
    • commit changes: git commit -m"removed crappy file"
    • push the changes to the master repository: git push origin master
>
>
    • check the status of the repository: git status
    • update to the last version of the code: git pull origin master
    • make changes to the files (or create new files) (ex. changed_file.cpp, changed_file.h, new_class.h )
    • add the chenged files: git add changed_file.cpp changed_file.h new_class.h
    • commit changes: git commit -m"added new functionality for bla bla bla"
    • remove crappy file: git rm crappy_file.cpp
    • commit changes: git commit -m"removed crappy file"
    • push the changes to the master repository: git push origin master
 
  • Advanced workflow (when making major changes to the code in a project with many people working at the same time)
Changed:
<
<
    • create a new local branch: git checkout -b new_branch
>
>
    • create a new local branch: git checkout -b new_branch
 
    • do stuff... add changed files ... and commit changes
Changed:
<
<
    • push the new branch to the remote repository: git push origin new_branch
    • when everything is working and is tested merge the new branch into the master branch: git merge new_branch master
>
>
    • push the new branch to the remote repository: git push origin new_branch
    • when everything is working and is tested merge the new branch into the master branch: git merge new_branch master
 
    • solve conflicts, commit and push them to the master remote repository
Changed:
<
<
    • check existing branches and current branch: git branch
    • switch to a branch: git checkout master
    • delete old/merged local branches: git branch -d new_branch
    • delete old/merged remote branches: git push origin :new_branch
>
>
    • check existing branches and current branch: git branch
    • switch to a branch: git checkout master
    • delete old/merged local branches: git branch -d new_branch
    • delete old/merged remote branches: git push origin :new_branch
 
 

SVN IFAE Pixel repository

Revision 652018-01-11 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel


Line: 11 to 11
 

Useful Links and Documentation

Deleted:
<
<
<!--Add the main topic here. i.e. create some new headings as follows:!-->
 
Line: 51 to 50
 
  • The general linux working areas are PIC (Barcelona) and LXPLUS (CERN).
Changed:
<
<
  • Tier 3 IFAE computing dashboard: here
>
>
  • Tier 3 IFAE computing dashboard: here.

  • To request a PIC account use this web interface.
 

Access to PIC and LXPLUS via ssh and sshfs

Revision 622017-06-08 - StefanoTerzo

Line: 1 to 1
 

IFAE Pixel


Line: 262 to 266
 
    • check the status of the repository: git status
    • update to the last version of the code: git pull origin master
    • make changes to the files (or create new files) (ex. changed_file.cpp, changed_file.h, new_class.h )
Changed:
<
<
    • add the chenged file: git add changed_file.cpp changed_file.h new_class.h
>
>
    • add the chenged files: git add changed_file.cpp changed_file.h new_class.h
 
    • commit changes: git commit -m"added new functionality for bla bla bla"
    • remove crappy file: git rm crappy_file.cpp
    • commit changes: git commit -m"removed crappy file"

Revision 612017-06-07 - StefanoTerzo

Line: 1 to 1
 

IFAE Pixel


Line: 243 to 243
 Examples:
Changed:
<
<
>
>
 
  • Create a new project:
    • go to the ifaepix page and click on the "New Project" button
    • insert the project name (ex. new_project) and click "Create Project"
Changed:
<
<
>
>
 
    • ...or follow the instructions on screen relative to your needs
  • Upload existing project:
    • go to the ifaepix page and click on the "New Project" button
    • insert the project name (ex. my_project) and click "Create Project"
Changed:
<
<
    • go in the folder of your existing project: cd my_project
>
>
    • go in the folder of your existing project: cd my_project
 
    • initialise an empty repository: git init
Changed:
<
<
>
>
 
    • add all the files in the folder to the local git repository: git add .
    • commit the changes: git commit -m"this is a comment fot the first commit of my project"
    • upload all the chages of the added files in the local repository to the remote repository: git push -u origin master
Changed:
<
<
  • Typical workflow:
>
>
  • Typical workflow (good for small changes or simple projects with few people modifing the code at the same time):
    • check the status of the repository: git status
 
    • update to the last version of the code: git pull origin master
Changed:
<
<
    • make changes to the files (ex. changed_file.cpp)
>
>
    • make changes to the files (or create new files) (ex. changed_file.cpp, changed_file.h, new_class.h )
    • add the chenged file: git add changed_file.cpp changed_file.h new_class.h
    • commit changes: git commit -m"added new functionality for bla bla bla"
    • remove crappy file: git rm crappy_file.cpp
    • commit changes: git commit -m"removed crappy file"
    • push the changes to the master repository: git push origin master
  • Advanced workflow (when making major changes to the code in a project with many people working at the same time)
    • create a new local branch: git checkout -b new_branch
    • do stuff... add changed files ... and commit changes
    • push the new branch to the remote repository: git push origin new_branch
    • when everything is working and is tested merge the new branch into the master branch: git merge new_branch master
    • solve conflicts, commit and push them to the master remote repository
    • check existing branches and current branch: git branch
    • switch to a branch: git checkout master
    • delete old/merged local branches: git branch -d new_branch
    • delete old/merged remote branches: git push origin :new_branch
 
 
Deleted:
<
<
 

SVN IFAE Pixel repository

Revision 602017-06-07 - StefanoTerzo

Line: 1 to 1
 

IFAE Pixel

Changed:
<
<
>
>

 

Introduction

Line: 11 to 11
 

Useful Links and Documentation

Changed:
<
<
<!--Add the main topic here. i.e. create some new headings as follows:!-->
>
>
<!--Add the main topic here. i.e. create some new headings as follows:!-->
 
Line: 41 to 41
 
Changed:
<
<
>
>
      • <a href="http://iopscience.iop.org/article/10.1088/1748-0221/11/01/C01012" rel="noreferrer" target="_blank">http://iopscience.iop.org/article/10.1088/1748-0221/11/01/C01012</a>
 
Line: 55 to 55
 

Access to PIC and LXPLUS via ssh and sshfs

Changed:
<
<
<!--/twistyPlugin twikiMakeVisibleInline-->
Login from a linux shell via ssh:
>
>

<!--/twistyPlugin twikiMakeVisibleInline-->
Login from a linux shell via ssh:
 
  •  ssh -Y picUserName@at3.pic.es 
  •  ssh -Y cernUserName@lxplus.cern.ch 
Attention! Make sure to be on the right pic machine! at303 has only SL 5.8, which sometimes leads to problems! E.g. at302 has SL 6.4.
Line: 69 to 68
 mkdir -p lxplus/home sshfs cernUserName@lxplusNOSPAMPLEASE.cern.ch:/afs/cern.ch/user/cernUserNameInitial(oneLetter)/cernUserName lxplus/home
Changed:
<
<
<!--/twistyPlugin-->
>
>

<!--/twistyPlugin-->
 

dCache

Line: 77 to 76
  Our dCache folder on the PIC is: /pnfs-disk/pic.es/at3/projects/Pixels
Changed:
<
<
<!--/twistyPlugin twikiMakeVisibleInline-->
The command to copy a file to dCache is:
dccp /bin/inputFile.xx /pnfs-disk/pic.es/at3/projects/Pixels/outputFolder
(answer from the help desk:) so far we haven't found a way to copy complete folder. Thus, to copy all files in a directory, you need to loop, e.g.:
for f in *.root; do dccp $f /pnfs-disk/pic.es/at3/projects/Pixels/outputFolder; done
>
>

<!--/twistyPlugin twikiMakeVisibleInline-->
The command to copy a file to dCache is:
dccp /bin/inputFile.xx /pnfs-disk/pic.es/at3/projects/Pixels/outputFolder
(answer from the help desk:) so far we haven't found a way to copy complete folder. Thus, to copy all files in a directory, you need to loop, e.g.:
for f in *.root; do dccp $f /pnfs-disk/pic.es/at3/projects/Pixels/outputFolder; done
  From the pic this command works directly. If you need to copy files from lxplus the trick is that you download your file in the /tmp directory of the at3 machine with your favourite command and then you copy the file to destination with dccp command.
Changed:
<
<
More information can be found here: https://giq.ifae.es/UsingdCache.pdf. If you cannot manage please call extension at IFAE 2822 and ask Alex Guinó for a joint session where he can debug what happens.
<!--/twistyPlugin-->
>
>
More information can be found here: https://giq.ifae.es/UsingdCache.pdf. If you cannot manage please call extension at IFAE 2822 and ask Alex Guinó for a joint session where he can debug what happens.
<!--/twistyPlugin-->
 

FE-I4B ASIC

Line: 127 to 122
 
    • If the RCE gets stuck, there is a reboot pin on the front that has to be pressed with a thin tool (the RCE leds flash when rebooted)
    • To reboot the HSIO board one has to press the SW1 next to the front green LEDs (it will flash 5sec later). After the reboot of the HSIO board, one needs to reboot the RCE.
    • More information on rebooting can be found in slides from TB
Changed:
<
<
    • To check the connection and status of the RCE (also reboot is possible) do:
      telnet rce16
      root (username)
      no password (just enter)
      To check the status enter: syslog
      For EXIT: exit
>
>
    • To check the connection and status of the RCE (also reboot is possible) do:
      telnet rce16
      root (username)
      no password (just enter)
      To check the status enter: syslog
      For EXIT: exit
 
  • Running:
    1. If not using existing account, setup own DAQ software as described in IBL SR1 Twiki
Changed:
<
<
    1. Make sure all the necessary directories and files are in place for data output, module configuration files and primlists (where 00-00-00 is your module name):
      mkdir -p data moduleconfigs/00-00-00 moduleconfigs/top primlists
      cd moduleconfigs/00-00-00
      mkdir configs fdacs masks tdacs
>
>
    1. Make sure all the necessary directories and files are in place for data output, module configuration files and primlists (where 00-00-00 is your module name):
      mkdir -p data moduleconfigs/00-00-00 moduleconfigs/top primlists
      cd moduleconfigs/00-00-00
      mkdir configs fdacs masks tdacs
 
    1. Copy template config file 00-00-00.cfg file to moduleconfigs/00-00-00/configs. Replace module ID and make sure no masks or maps are loaded. Optionally modify chip register values.

  • Running the RCE in the AFP testbeam
    • Starting from scratch, from the pcaidarc do the following:
Changed:
<
<
    • Connect to the iblecontest2 laptop (which is just outside the enclosure, on the Jura side):
      > ssh -Y 192.168.5.8 -l ibl (pass: iblecon)
>
>
    • Connect to the iblecontest2 laptop (which is just outside the enclosure, on the Jura side):
      > ssh -Y 192.168.5.8 -l ibl (pass: iblecon)
 
    • > cd work
Changed:
<
<
    • > source setup_rce.sh
      This does a killall (ei, kills all the RCE related servers/processes). It does not need to be done everytime you start the calibGui or the cosmicGui.
    • > source reload_rce.sh This loads the rce library (it is also done in the start_calib.sh below).
    • > cosmicGui
      This is the data taking gui, to start taking data, you just have to press "Start Run" (it will take the previous running configuration).
    • To run the pixel module scans and also to take data in "self-trigger" mode, use:
      > source start_calib.sh
>
>
    • > source setup_rce.sh
      This does a killall (ei, kills all the RCE related servers/processes). It does not need to be done everytime you start the calibGui or the cosmicGui.
    • > source reload_rce.sh This loads the rce library (it is also done in the start_calib.sh below).
    • > cosmicGui
      This is the data taking gui, to start taking data, you just have to press "Start Run" (it will take the previous running configuration).
    • To run the pixel module scans and also to take data in "self-trigger" mode, use:
      > source start_calib.sh
 
    • To reboot the HSIO board form the iblecontest2: > rebootHSIO (not always possible)
Changed:
<
<
HSIO board at SR1 used during Sept 2014 tests for AFP:
>
>
HSIO board at SR1 used during Sept 2014 tests for AFP:
 

Testbeams

Line: 194 to 173
 cd $ILCSOFT/ilcinstall_v01-17-03-eutel ./ilcsoft-install -i examples/eutelescope/release-standalone.cfg
Changed:
<
<
NOTE 16 December 2013:
>
>
NOTE 16 December 2013:
 
<span style="color: red;">
We had the following error when compiling at SL6 at301:
/nfs/atlas-data06/scratch/sgrinstein/eudet_sl6b/v01-17-03/root/5.34.05/ROOT/net/netx/src/TXNetFile.cxx:59:38: error: XrdClient/XrdClientConn.hh: No such file or directory
Line: 246 to 224
 cd ../../../build make install
Changed:
<
<
</>
<!--/twistyPlugin-->
>
>

</>
<!--/twistyPlugin-->
 

AIDA-1

Added:
>
>

GitLab IFAE Pixel repository

 
Changed:
<
<

SVN IFAE Pixel repository

>
>
The IFAE Pixel Group Repository: https://gitlab.cern.ch/ifaepix

Documentation:

Examples:

  • Get an existing project:
  • Create a new project:
  • Upload existing project:
    • go to the ifaepix page and click on the "New Project" button
    • insert the project name (ex. my_project) and click "Create Project"
    • go in the folder of your existing project: cd my_project
    • initialise an empty repository: git init
    • link your project to the remote git repository: =git remote add origin https://$CERN_USER@gitlab.cern.ch/ifaepix/my_project.git=
    • add all the files in the folder to the local git repository: git add .
    • commit the changes: git commit -m"this is a comment fot the first commit of my project"
    • upload all the chages of the added files in the local repository to the remote repository: git push -u origin master
  • Typical workflow:
    • update to the last version of the code: git pull origin master
    • make changes to the files (ex. changed_file.cpp)
 
 
Added:
>
>

SVN IFAE Pixel repository

 
Line: 268 to 279
  Using SVN:
Changed:
<
<
  • To check out the "usbpix_analysis" project:
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/usbpix_analysis" usbpix_analysis
  • Make your changes and commit:
    svn ci . -m "Made some changes to usbpix_analysis"
  • Or copy the files to the project repository (most likely you want to do this in the "trunk"), add them, and commit:
    nifae04 ~/usbpix_analysis/trunk> cp /somepath/test.C .
    nifae04 ~/usbpix_analysis/trunk> cd ..
    nifae04 ~/usbpix_analysis> svn status
    ? trunk/test.C
    nifae04 ~/usbpix_analysis> svn add trunk/test.C
    A trunk/test.C
    nifae04 ~/usbpix_analysis> svn ci . -m "added test.C to usbpix_analysis"
  • To create a directory for a new project (example for "characterization"):
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/" .
    mkdir characterization
    mkdir characterization/trunk
    mkdir characterization/branches
    mkdir characterization/tags
    svn add characterization
    svn ci . -m "characterization project structure"
  • To check out everything:
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/" .
    To check out the "characterization" project:
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/characterization" characterization
  • To remove a file from svn repository, you have to tell svn to remove it and then commit the changes:
    svn rm path_to_file/file
    svn ci -m "removed crappy file"
  • To bring your release up to date with the latest repository release:
    svn update
    svn update filename
    svn status -u (to see what the update will do, but without doing it)
  • To checkout a certain rev of a file:
    svn up -r revnumber filename
>
>
  • To check out the "usbpix_analysis" project:
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/usbpix_analysis" usbpix_analysis
  • Make your changes and commit:
    svn ci . -m "Made some changes to usbpix_analysis"
  • Or copy the files to the project repository (most likely you want to do this in the "trunk"), add them, and commit:
    nifae04 ~/usbpix_analysis/trunk> cp /somepath/test.C .
    nifae04 ~/usbpix_analysis/trunk> cd ..
    nifae04 ~/usbpix_analysis> svn status
    ? trunk/test.C
    nifae04 ~/usbpix_analysis> svn add trunk/test.C
    A trunk/test.C
    nifae04 ~/usbpix_analysis> svn ci . -m "added test.C to usbpix_analysis"
  • To create a directory for a new project (example for "characterization"):
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/" .
    mkdir characterization
    mkdir characterization/trunk
    mkdir characterization/branches
    mkdir characterization/tags
    svn add characterization
    svn ci . -m "characterization project structure"
  • To check out everything:
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/" .
    To check out the "characterization" project:
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/characterization" characterization
  • To remove a file from svn repository, you have to tell svn to remove it and then commit the changes:
    svn rm path_to_file/file
    svn ci -m "removed crappy file"
  • To bring your release up to date with the latest repository release:
    svn update
    svn update filename
    svn status -u (to see what the update will do, but without doing it)
  • To checkout a certain rev of a file:
    svn up -r revnumber filename
 

IBL Modules

Line: 317 to 303
 

AFP

  • AFP Upgrade twiki (ATLAS upgrade web page)
Changed:
<
<
>
>
 
  • AFP data preparation: twiki.
Changed:
<
<
>
>
 

Miscellaneous

Telescope setup

Changed:
<
<
  • ifconfig on the DAQ PC

>
>
  • ifconfig on the DAQ PC
  telescope@pcaidarc:~$ ifconfig eth0 Link encap:Ethernet HWaddr 00:22:4d:a9:dd:d5 inet addr:137.138.113.254 Bcast:137.138.113.255 Mask:255.255.255.192

Revision 572016-11-02 - JoernLange

Line: 1 to 1
 

IFAE Pixel

Line: 348 to 348
 
Added:
>
>

Submitting JINST papers to arXiv

  • arXiv has problems with the new standard JINST latex template (jinstpub.sty)
  • To make arXiv compile, comment out
     \RequirePackage{newtxmath} 
    in jinstpub.sty
  • In addition, include the following files in your arXiv upload .zip or .tar file (in addition to your main.tex source file and the plots):
    • jinstpub.sty (modified as above)
    • newtxtext.sty
    • newtxtt.sty
 
META FILEATTACHMENT attachment="Screen_shot_2014-09-30_at_10.12.53_AM.png" attr="" comment="" date="1412065566" name="Screen_shot_2014-09-30_at_10.12.53_AM.png" path="Screen_shot_2014-09-30_at_10.12.53_AM.png" size="512718" user="sgrinste" version="1"
META FILEATTACHMENT attachment="FE-I4B_V2.3.pdf" attr="" comment="" date="1444742260" name="FE-I4B_V2.3.pdf" path="FE-I4B_V2.3.pdf" size="9468068" user="sgrinste" version="1"

Revision 542016-09-26 - StefanoTerzo

Line: 1 to 1
 

IFAE Pixel

Line: 29 to 29
 
Changed:
<
<
>
>
 
Added:
>
>
 
Line: 217 to 218
 cd $ILCSOFT/v01-17-03/Eutelescope/v00-09-01/external/eudaq/trunk/bin ./OnlineMon.exe -f ~/scratch/June2013_DESY/run012602.raw
Changed:
<
<
The instructions below should compile the full eudaq software:
>
>
The instructions below should compile the full eudaq software:
  Tried them on 18 Dec 2013 on at301 (/nfs/at3/scratch/sgrinstein/eudet_sl6b/, SL6, with ROOT 5.30.01) and they worked (they compiled, but I did not run the executables yet).
Added:
>
>
 
#environment
cd v01-17-03/Eutelescope/v00-09-01

Revision 532016-09-26 - StefanoTerzo

Line: 1 to 1
 

IFAE Pixel

Line: 29 to 29
 
Changed:
<
<
  • Material for students
>
>
 
Line: 308 to 312
 

AFP

Changed:
<
<
  • AFP Upgrade twiki (ATLAS upgrade web page)
  • AFP Detector twiki (includes AFP Data Preparation twiki).
  • AFP data preparation: twiki.
>
>
  • AFP Upgrade twiki (ATLAS upgrade web page)
  • AFP Detector twiki (includes AFP Data Preparation twiki).
  • AFP data preparation: twiki.
 

Miscellaneous

Revision 512016-06-14 - StefanoTerzo

Line: 1 to 1
 

IFAE Pixel

Line: 13 to 13
 
<!--Add the main topic here. i.e. create some new headings as follows:!-->
  • Other websites of the pixel group
Changed:
<
<
>
>
 
Changed:
<
<
>
>
 
Changed:
<
<
>
>
 

Line: 50 to 60
 sshfs picUserName@at3NOSPAMPLEASE.pic.es:/nfs pic/nfs

mkdir -p lxplus/home

Changed:
<
<
sshfs cernUserName@lxplusNOSPAMPLEASE.cern.ch:/afs/cern.ch/user/cernUserNameInitial(oneLetter)/cernUserName lxplus/home
>
>
sshfs cernUserName@lxplusNOSPAMPLEASE.cern.ch:/afs/cern.ch/user/cernUserNameInitial(oneLetter)/cernUserName lxplus/home
  </>
<!--/twistyPlugin-->
Line: 92 to 101
 

HSIO-II

Changed:
<
<
>
>
 

RCE

  • Documentation:
Changed:
<
<
>
>
 
  • Notes on running the RCE system:
    • Users need accounts on pixiblsr1daq1, ask Martin Kocian for one
Line: 110 to 119
 
    • The HitOr lemo, if not connected to the HSIO board (pin J1), also has to be connected to the common ground
    • If the RCE gets stuck, there is a reboot pin on the front that has to be pressed with a thin tool (the RCE leds flash when rebooted)
    • To reboot the HSIO board one has to press the SW1 next to the front green LEDs (it will flash 5sec later). After the reboot of the HSIO board, one needs to reboot the RCE.
Changed:
<
<
>
>
 
    • To check the connection and status of the RCE (also reboot is possible) do:
      telnet rce16
      root (username)
Line: 121 to 130
  exit

  • Running:
Changed:
<
<
    1. If not using existing account, setup own DAQ software as described in IBL SR1 Twiki
    2. Make sure all the necessary directories and files are in place for data output, module configuration files and primlists (where 00-00-00 is your module name):
>
>
    1. If not using existing account, setup own DAQ software as described in IBL SR1 Twiki
    2. Make sure all the necessary directories and files are in place for data output, module configuration files and primlists (where 00-00-00 is your module name):
  mkdir -p data moduleconfigs/00-00-00 moduleconfigs/top primlists
cd moduleconfigs/00-00-00
mkdir configs fdacs masks tdacs
Changed:
<
<
    1. Copy template config file 00-00-00.cfg file to moduleconfigs/00-00-00/configs. Replace module ID and make sure no masks or maps are loaded. Optionally modify chip register values.
>
>
    1. Copy template config file 00-00-00.cfg file to moduleconfigs/00-00-00/configs. Replace module ID and make sure no masks or maps are loaded. Optionally modify chip register values.
 
  • Running the RCE in the AFP testbeam
    • Starting from scratch, from the pcaidarc do the following:
    • Connect to the iblecontest2 laptop (which is just outside the enclosure, on the Jura side):
Changed:
<
<
> ssh -Y 192.168.5.8 -l ibl (pass: iblecon)
    • > cd work
    • > source setup_rce.sh
>
>
> ssh -Y 192.168.5.8 -l ibl (pass: iblecon)
    • > cd work
    • > source setup_rce.sh
  This does a killall (ei, kills all the RCE related servers/processes). It does not need to be done everytime you start the calibGui or the cosmicGui.
Changed:
<
<
    • > source reload_rce.sh
>
>
    • > source reload_rce.sh
  This loads the rce library (it is also done in the start_calib.sh below).
Changed:
<
<
    • > cosmicGui
>
>
    • > cosmicGui
  This is the data taking gui, to start taking data, you just have to press "Start Run" (it will take the previous running configuration).
    • To run the pixel module scans and also to take data in "self-trigger" mode, use:
Changed:
<
<
> source start_calib.sh
    • To reboot the HSIO board form the iblecontest2: > rebootHSIO (not always possible)
>
>
> source start_calib.sh
    • To reboot the HSIO board form the iblecontest2: > rebootHSIO (not always possible)
  HSIO board at SR1 used during Sept 2014 tests for AFP:
Changed:
<
<
>
>
 

Testbeams

Changed:
<
<
List of 3D/AFP testbeams.
>
>
List of 3D/AFP testbeams.
 

Testbeam Reconstruction

  • Judith reconstraction framework for FEi4 based telescopes:
Changed:
<
<
    • Info on how to install/use: Twiki
>
>
    • Info on how to install/use: Twiki
 
Line: 176 to 185
 vim $ILCSOFT/ilcinstall_v01-17-03-eutel/releases/v01-17/release-versions.py # install and compile cd $ILCSOFT/ilcinstall_v01-17-03-eutel
Changed:
<
<
./ilcsoft-install -i examples/eutelescope/release-standalone.cfg
>
>
./ilcsoft-install -i examples/eutelescope/release-standalone.cfg
  NOTE 16 December 2013:
<span style="color: red;">
Line: 189 to 197
 ROOT_version = "5.30.01" (See my working area: /nfs/pic.es/user/s/sgrinstein/scratch/eudet_sl6b) However, the best solution might be to ask the admins to add the XrdClient/XrdClientConn.hh header file to: /usr/include/xrootd
Changed:
<
<

>
>
 
Deleted:
<
<
 # you will see most of the relevant executables at: ls $ILCSOFT/v01-17-03/Eutelescope/v00-09-01/external/eudaq/trunk/bin/
Line: 206 to 211
  Now you should have the OnlineMonitor: cd $ILCSOFT/v01-17-03/Eutelescope/v00-09-01/external/eudaq/trunk/bin
Changed:
<
<
./OnlineMon.exe -f ~/scratch/June2013_DESY/run012602.raw

The instructions below should compile the full eudaq software:

>
>
./OnlineMon.exe -f ~/scratch/June2013_DESY/run012602.raw The instructions below should compile the full eudaq software:
  Tried them on 18 Dec 2013 on at301 (/nfs/at3/scratch/sgrinstein/eudet_sl6b/, SL6, with ROOT 5.30.01) and they worked (they compiled, but I did not run the executables yet).
Line: 233 to 236
 make clean ; make -j USE_LCIO=1 USE_EUTELESCOPE=1 # rebuild EUtelescope cd ../../../build
Changed:
<
<
make install
>
>
make install
  </>
<!--/twistyPlugin-->
Line: 255 to 255
  Documentation
Changed:
<
<
>
>
 

Using SVN:

Line: 265 to 265
 
  • Make your changes and commit:
    svn ci . -m "Made some changes to usbpix_analysis"
  • Or copy the files to the project repository (most likely you want to do this in the "trunk"), add them, and commit:
Changed:
<
<
nifae04 ~/usbpix_analysis/trunk> cp /somepath/test.C .
nifae04 ~/usbpix_analysis/trunk> cd ..
nifae04 ~/usbpix_analysis> svn status
>
>
nifae04 ~/usbpix_analysis/trunk> cp /somepath/test.C .
nifae04 ~/usbpix_analysis/trunk> cd ..
nifae04 ~/usbpix_analysis> svn status
  ? trunk/test.C
Changed:
<
<
nifae04 ~/usbpix_analysis> svn add trunk/test.C
>
>
nifae04 ~/usbpix_analysis> svn add trunk/test.C
  A trunk/test.C
Changed:
<
<
nifae04 ~/usbpix_analysis> svn ci . -m "added test.C to usbpix_analysis"
>
>
nifae04 ~/usbpix_analysis> svn ci . -m "added test.C to usbpix_analysis"
 
  • To create a directory for a new project (example for "characterization"):
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/" .
    mkdir characterization
Line: 304 to 304
 

HGTD

Changed:
<
<
>
>
 

Miscellaneous

Revision 452015-10-13 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 69 to 69
 More information can be found here: https://giq.ifae.es/UsingdCache.pdf. If you cannot manage please call extension at IFAE 2822 and ask Alex Guinó for a joint session where he can debug what happens. </>
<!--/twistyPlugin-->
Added:
>
>

FE-I4B ASIC

  • See the attachments below for the FEI4B manual.
 

USBPix Connectivity

Line: 319 to 323
 

META FILEATTACHMENT attachment="Screen_shot_2014-09-30_at_10.12.53_AM.png" attr="" comment="" date="1412065566" name="Screen_shot_2014-09-30_at_10.12.53_AM.png" path="Screen_shot_2014-09-30_at_10.12.53_AM.png" size="512718" user="sgrinste" version="1"
Added:
>
>
META FILEATTACHMENT attachment="FE-I4B_V2.3.pdf" attr="" comment="" date="1444742260" name="FE-I4B_V2.3.pdf" path="FE-I4B_V2.3.pdf" size="9468068" user="sgrinste" version="1"

Revision 392015-01-19 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 270 to 270
 
  • To bring your release up to date with the latest repository release:
    svn update
    svn update filename
Changed:
<
<
svn update -u (to see what the update will do, but without doing it)
>
>
svn status -u (to see what the update will do, but without doing it)
 
  • To checkout a certain rev of a file:
    svn up -r revnumber filename

Revision 382015-01-13 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 260 to 260
  mkdir characterization/tags
svn add characterization
svn ci . -m "characterization project structure"
Changed:
<
<
To check out everything:
>
>
  • To check out everything:
  svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/" .
To check out the "characterization" project:
svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/characterization" characterization
Line: 270 to 270
 
  • To bring your release up to date with the latest repository release:
    svn update
    svn update filename
Added:
>
>
svn update -u (to see what the update will do, but without doing it)
  • To checkout a certain rev of a file:
    svn up -r revnumber filename

 

IBL Modules

Revision 352014-11-20 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 119 to 119
 
    • To reboot the HSIO board form the iblecontest2: > rebootHSIO (not always possible)

HSIO board at SR1 used during Sept 2014 tests for AFP:

Changed:
<
<
<img width="480" alt="" src="https://twiki.cern.ch/twiki/pub/Main/IFAEPixel/Screen_shot_2014-09-30_at_10.12.53_AM.png" height="280" /
>
>
 

Testbeams

Revision 342014-11-19 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 104 to 104
 
    1. Copy template config file 00-00-00.cfg file to moduleconfigs/00-00-00/configs. Replace module ID and make sure no masks or maps are loaded. Optionally modify chip register values.

  • Running the RCE in the AFP testbeam
Changed:
<
<
    • From the pcaidarc do the following:
>
>
    • Starting from scratch, from the pcaidarc do the following:
 
    • Connect to the iblecontest2 laptop (which is just outside the enclosure, on the Jura side):
      > ssh -Y 192.168.5.8 -l ibl (pass: iblecon)
    • > cd work
    • > source setup_rce.sh
      This does a killall (ei, kills all the RCE related servers/processes). It does not need to be done everytime you start the calibGui or the cosmicGui.
Added:
>
>
    • > source reload_rce.sh This loads the rce library (it is also done in the start_calib.sh below).
 
    • > cosmicGui
      This is the data taking gui, to start taking data, you just have to press "Start Run" (it will take the previous running configuration).
    • To run the pixel module scans and also to take data in "self-trigger" mode, use:

Revision 332014-11-18 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 103 to 103
  mkdir configs fdacs masks tdacs
    1. Copy template config file 00-00-00.cfg file to moduleconfigs/00-00-00/configs. Replace module ID and make sure no masks or maps are loaded. Optionally modify chip register values.
Added:
>
>
  • Running the RCE in the AFP testbeam
    • From the pcaidarc do the following:
    • Connect to the iblecontest2 laptop (which is just outside the enclosure, on the Jura side):
      > ssh -Y 192.168.5.8 -l ibl (pass: iblecon)
    • > cd work
    • > source setup_rce.sh
      This does a killall (ei, kills all the RCE related servers/processes). It does not need to be done everytime you start the calibGui or the cosmicGui.
    • > cosmicGui
      This is the data taking gui, to start taking data, you just have to press "Start Run" (it will take the previous running configuration).
    • To run the pixel module scans and also to take data in "self-trigger" mode, use:
      > source start_calib.sh
    • To reboot the HSIO board form the iblecontest2: > rebootHSIO (not always possible)
  HSIO board at SR1 used during Sept 2014 tests for AFP:
Changed:
<
<
>
>
<img width="480" alt="" src="https://twiki.cern.ch/twiki/pub/Main/IFAEPixel/Screen_shot_2014-09-30_at_10.12.53_AM.png" height="280" /
 

Testbeams

Revision 322014-11-11 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 113 to 113
 

Testbeam Reconstruction

Added:
>
>
  • Judith reconstraction framework for FEi4 based telescopes:
 
  • EUtelescope: See the instructions to compile the Eudet software in the PIC:

<!--/twistyPlugin twikiMakeVisibleInline-->
Line: 195 to 200
 
<!--/twistyPlugin-->
Deleted:
<
<
  • Judith reconstraction framework for FEi4 based telescopes:
 

TBMon

AIDA

Revision 312014-10-20 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 253 to 253
 

Miscellaneous

Added:
>
>

Telescope setup

  • ifconfig on the DAQ PC
         telescope@pcaidarc:~$ ifconfig
         eth0      Link encap:Ethernet  HWaddr 00:22:4d:a9:dd:d5  
         inet addr:137.138.113.254  Bcast:137.138.113.255  Mask:255.255.255.192
         eth0:1    Link encap:Ethernet  HWaddr 00:22:4d:a9:dd:d5  
         inet addr:192.168.5.251  Bcast:192.168.5.255  Mask:255.255.255.0
         
  • sudo ifconfig eth0:1 192.168.5.251
 

Shuttle CERN to Previssin

  • Circuit 6 note: from CERN bld 33.
  • TREC, to be aothorized, do the SIT TREC training.

Revision 292014-10-05 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 51 to 51
  dCache is a file system for the storage of large data sets. It is e.g. used to backup the raw files and reconstructed files of our testbeams.
Changed:
<
<
Our dCache folder on the PIC is:
>
>
Our dCache folder on the PIC is: /pnfs-disk/pic.es/at3/projects/Pixels
 
Changed:
<
<
 /pnfs-disk/pic.es/at3/projects/Pixels 

<!--/twistyPlugin twikiMakeVisibleInline-->
The command to copy a file to dCache is:

  dccp /bin/inputFile.xx /pnfs-disk/pic.es/at3/projects/Pixels/outputFolder 

(answer from the help desk:) so far we haven't found a way to copy complete folder. Thus, to copy all files in a directory, you need to loop, e.g.:

  for f in *.root; do dccp $f /pnfs-disk/pic.es/at3/projects/Pixels/outputFolder; done 
>
>
<!--/twistyPlugin twikiMakeVisibleInline-->
The command to copy a file to dCache is:
dccp /bin/inputFile.xx /pnfs-disk/pic.es/at3/projects/Pixels/outputFolder
(answer from the help desk:) so far we haven't found a way to copy complete folder. Thus, to copy all files in a directory, you need to loop, e.g.:
for f in *.root; do dccp $f /pnfs-disk/pic.es/at3/projects/Pixels/outputFolder; done
  From the pic this command works directly. If you need to copy files from lxplus the trick is that you download your file in the /tmp directory of the at3 machine with your favourite command and then you copy the file to destination with dccp command.
Line: 91 to 86
 
    • If the RCE gets stuck, there is a reboot pin on the front that has to be pressed with a thin tool (the RCE leds flash when rebooted)
    • To reboot the HSIO board one has to press the SW1 next to the front green LEDs (it will flash 5sec later). After the reboot of the HSIO board, one needs to reboot the RCE.
    • More information on rebooting can be found in slides from TB
Changed:
<
<
    • To check the connection and status of the RCE (also reboot is possible) do:
       telnet rce16
       root # username 
       <ENTER> # no PW
       
>
>
    • To check the connection and status of the RCE (also reboot is possible) do:
      telnet rce16
      root (username)
      no password (just enter)
  To check the status enter:
Changed:
<
<
 syslog 
>
>
syslog
  For EXIT:
Changed:
<
<
 exit 
.
>
>
exit
 
  • Running:
Changed:
<
<
0) If not using existing account, setup own DAQ software as described in IBL SR1 Twiki

1) Make sure all the necessary directories and files are in place for data output, module configuration files and primlists (where 00-00-00 is your module name):

 mkdir -p data moduleconfigs/00-00-00 moduleconfigs/top primlists
 cd moduleconfigs/00-00-00
 mkdir configs fdacs masks tdacs

2) Copy template config file 00-00-00.cfg file to moduleconfigs/00-00-00/configs. Replace module ID and make sure no masks or maps are loaded. Optionally modify chip register values.

>
>
    1. If not using existing account, setup own DAQ software as described in IBL SR1 Twiki
    2. Make sure all the necessary directories and files are in place for data output, module configuration files and primlists (where 00-00-00 is your module name):
      mkdir -p data moduleconfigs/00-00-00 moduleconfigs/top primlists
      cd moduleconfigs/00-00-00
      mkdir configs fdacs masks tdacs
    3. Copy template config file 00-00-00.cfg file to moduleconfigs/00-00-00/configs. Replace module ID and make sure no masks or maps are loaded. Optionally modify chip register values.
 

HSIO board at SR1 used during Sept 2014 tests for AFP:

Revision 272014-10-01 - IvanLopezPaz

Line: 1 to 1
 

IFAE Pixel

Line: 122 to 122
 

Testbeam Reconstruction

Changed:
<
<
See the instructions to compile the Eudet software in the PIC:
>
>
  • EUtelescope: See the instructions to compile the Eudet software in the PIC:
 
<!--/twistyPlugin twikiMakeVisibleInline-->

These instructinos are mainly to compile the OnlineMonitor, though the last part shows how to compile everything.

Line: 200 to 201
 make install
Added:
>
>
 
<!--/twistyPlugin-->
Added:
>
>
  • Judith reconstraction framework for FEi4 based telescopes:
 

TBMon

AIDA

Revision 262014-09-30 - JoernLange

Line: 1 to 1
 

IFAE Pixel

Line: 90 to 90
 
    • The HitOr lemo, if not connected to the HSIO board (pin J1), also has to be connected to the common ground
    • If the RCE gets stuck, there is a reboot pin on the front that has to be pressed with a thin tool (the RCE leds flash when rebooted)
    • To reboot the HSIO board one has to press the SW1 next to the front green LEDs (it will flash 5sec later). After the reboot of the HSIO board, one needs to reboot the RCE.
Added:
>
>
    • More information on rebooting can be found in slides from TB
    • To check the connection and status of the RCE (also reboot is possible) do:
            telnet rce16
            root # username
            <ENTER> # no PW
            
      To check the status enter:
       syslog 
      For EXIT:
       exit 
      .

  • Running:
0) If not using existing account, setup own DAQ software as described in IBL SR1 Twiki

1) Make sure all the necessary directories and files are in place for data output, module configuration files and primlists (where 00-00-00 is your module name):

 mkdir -p data moduleconfigs/00-00-00 moduleconfigs/top primlists
 cd moduleconfigs/00-00-00
 mkdir configs fdacs masks tdacs

2) Copy template config file 00-00-00.cfg file to moduleconfigs/00-00-00/configs. Replace module ID and make sure no masks or maps are loaded. Optionally modify chip register values.

  HSIO board at SR1 used during Sept 2014 tests for AFP:

Revision 252014-09-30 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 89 to 89
 
    • It is important to ground the HSIO board and the module power supply to a common ground
    • The HitOr lemo, if not connected to the HSIO board (pin J1), also has to be connected to the common ground
    • If the RCE gets stuck, there is a reboot pin on the front that has to be pressed with a thin tool (the RCE leds flash when rebooted)
Added:
>
>
    • To reboot the HSIO board one has to press the SW1 next to the front green LEDs (it will flash 5sec later). After the reboot of the HSIO board, one needs to reboot the RCE.
 
Added:
>
>
HSIO board at SR1 used during Sept 2014 tests for AFP:
 

Testbeams

Line: 236 to 239
 
Added:
>
>
META FILEATTACHMENT attachment="Screen_shot_2014-09-30_at_10.12.53_AM.png" attr="" comment="" date="1412065566" name="Screen_shot_2014-09-30_at_10.12.53_AM.png" path="Screen_shot_2014-09-30_at_10.12.53_AM.png" size="512718" user="sgrinste" version="1"

Revision 242014-09-29 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 84 to 84
 
Added:
>
>
  • Notes on running the RCE system:
    • Users need accounts on pixiblsr1daq1, ask Martin Kocian for one
    • It is important to ground the HSIO board and the module power supply to a common ground
    • The HitOr lemo, if not connected to the HSIO board (pin J1), also has to be connected to the common ground
    • If the RCE gets stuck, there is a reboot pin on the front that has to be pressed with a thin tool (the RCE leds flash when rebooted)

 

Testbeams

List of 3D/AFP testbeams.

Revision 232014-09-26 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 213 to 213
 
  • To remove a file from svn repository, you have to tell svn to remove it and then commit the changes:
    svn rm path_to_file/file
    svn ci -m "removed crappy file"
Added:
>
>
  • To bring your release up to date with the latest repository release:
    svn update
    svn update filename
 

IBL Modules

Revision 192014-07-07 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 198 to 198
  svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/" .
To check out the "characterization" project:
svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/characterization" characterization
Added:
>
>
  • To remove a file from svn repository, you have to tell svn to remove it and then commit the changes:
    svn rm path_to_file/file
    svn ci -m "removed crappy file"
 

IBL Modules

Revision 162014-05-28 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 185 to 185
  nifae04 ~/usbpix_analysis> svn add trunk/test.C
A trunk/test.C
nifae04 ~/usbpix_analysis> svn ci . -m "added test.C to usbpix_analysis"
Changed:
<
<
>
>
  • To create a directory for a new project (example for "characterization"):
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/" .
    mkdir characterization
    mkdir characterization/trunk
    mkdir characterization/branches
    mkdir characterization/tags
    svn add characterization
    svn ci . -m "characterization project structure"
    To check out everything:
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/" .
    To check out the "characterization" project:
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/characterization" characterization
 

IBL Modules

Revision 142014-05-15 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 170 to 170
 
Changed:
<
<
>
>
Using SVN:

  • To check out the "usbpix_analysis" project:
    svn co "svn+ssh://$CERN_USER@svn.cern.ch/reps/ifaepix/usbpix_analysis" usbpix_analysis
  • Make your changes and commit:
    svn ci . -m "Made some changes to usbpix_analysis"
  • Or copy the files to the project repository (most likely you want to do this in the "trunk"), add them, and commit:
    nifae04 ~/usbpix_analysis/trunk> cp /somepath/test.C .
    nifae04 ~/usbpix_analysis/trunk> cd ..
    nifae04 ~/usbpix_analysis> svn status
    ? trunk/test.C
    nifae04 ~/usbpix_analysis> svn add trunk/test.C
    A trunk/test.C
    nifae04 ~/usbpix_analysis> svn ci . -m "added test.C to usbpix_analysis"

 

Miscellaneous

Revision 112014-05-14 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 176 to 176
 

Miscellaneous

TightVNC

Changed:
<
<
  • 172.16.15.6 (usbpix setup right of the chamber - pass: pixels)
  • 172.16.9.7 (usbpix setup left of the chamber - pass: pixels)
  • 172.16.15.7 (microsope PC - pass: pixelLAB)
>
>
  • 172.16.15.6 - usbpix setup right of the chamber
  • 172.16.9.7 - usbpix setup left of the chamber
  • 172.16.7.91 - pixel laptop
  • 172.16.15.7 - microsope PC
 

Twiki

Revision 102014-05-14 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 166 to 166
 
Added:
>
>

SVN IFAE Pixel repository

Service Account:
Name: IFAE Pixels
Login: ifaepix
Email: ifae.pixels .at. cern.ch

 

Miscellaneous

Added:
>
>

TightVNC

  • 172.16.15.6 (usbpix setup right of the chamber - pass: pixels)
  • 172.16.9.7 (usbpix setup left of the chamber - pass: pixels)
  • 172.16.15.7 (microsope PC - pass: pixelLAB)
 

Twiki

Revision 92014-01-14 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 9 to 9
  For the collection of measurement results, please refer to the IFAE Pixel Elog.
Deleted:
<
<
Contact information:
  • Sebastian: +34638458707 (cel) +34935814983 (off bcn) +41227674026 (off cern building 104)
  • Joern:
  • Ivan: +34654346572 (cel)
 

Useful Links and Documentation

<!--Add the main topic here. i.e. create some new headings as follows:!-->

Revision 82014-01-14 - IvanLopezPaz

Line: 1 to 1
 

IFAE Pixel

Line: 12 to 12
 Contact information:
  • Sebastian: +34638458707 (cel) +34935814983 (off bcn) +41227674026 (off cern building 104)
  • Joern:
Changed:
<
<
  • Ivan:
>
>
  • Ivan: +34654346572 (cel)
 

Useful Links and Documentation

Line: 87 to 87
 See the instructions to compile the Eudet software in the PIC:
<!--/twistyPlugin twikiMakeVisibleInline-->
Changed:
<
<
These instructinos are mainly to compile the OnlineMonitor, though the last part shows how to compile everything.
>
>
These instructinos are mainly to compile the OnlineMonitor, though the last part shows how to compile everything.
 
Changed:
<
<
Official instructions: http://eutelescope.web.cern.ch/content/installation
>
>
Official instructions: http://eutelescope.web.cern.ch/content/installation
 
Changed:
<
<
How to install at the pic:
>
>
How to install at the pic:
 
# your working area:
export ILCSOFT=/nfs/at3/scratch/sgrinstein/eudet_sl6
Line: 105 to 105
 ./ilcsoft-install -i examples/eutelescope/release-standalone.cfg
Changed:
<
<
NOTE 16 December 2013:
>
>
NOTE 16 December 2013:
<span style="color: red;">
 We had the following error when compiling at SL6 at301: /nfs/atlas-data06/scratch/sgrinstein/eudet_sl6b/v01-17-03/root/5.34.05/ROOT/net/netx/src/TXNetFile.cxx:59:38: error: XrdClient/XrdClientConn.hh: No such file or directory So, we changed the ROOT version in
Line: 115 to 115
 ROOT_version = "5.30.01" (See my working area: /nfs/pic.es/user/s/sgrinstein/scratch/eudet_sl6b) However, the best solution might be to ask the admins to add the XrdClient/XrdClientConn.hh header file to: /usr/include/xrootd
Changed:
<
<
>
>

 
# you will see most of the relevant executables at:
Line: 134 to 135
 ./OnlineMon.exe -f ~/scratch/June2013_DESY/run012602.raw
Changed:
<
<
The instructions below should compile the full eudaq software:
>
>
The instructions below should compile the full eudaq software:
  Tried them on 18 Dec 2013 on at301 (/nfs/at3/scratch/sgrinstein/eudet_sl6b/, SL6, with ROOT 5.30.01) and they worked (they compiled, but I did not run the executables yet).

Revision 72014-01-14 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 9 to 9
  For the collection of measurement results, please refer to the IFAE Pixel Elog.
Added:
>
>
Contact information:
  • Sebastian: +34638458707 (cel) +34935814983 (off bcn) +41227674026 (off cern building 104)
  • Joern:
  • Ivan:
 

Useful Links and Documentation

<!--Add the main topic here. i.e. create some new headings as follows:!-->

Revision 52013-12-20 - SebastianGrinstein

Line: 1 to 1
 

IFAE Pixel

Line: 78 to 78
 

Testbeam Reconstruction

Added:
>
>
See the instructions to compile the Eudet software in the PIC:
<!--/twistyPlugin twikiMakeVisibleInline-->

These instructinos are mainly to compile the OnlineMonitor, though the last part shows how to compile everything.

Official instructions: http://eutelescope.web.cern.ch/content/installation

How to install at the pic:

# your working area:
export ILCSOFT=/nfs/at3/scratch/sgrinstein/eudet_sl6
cd $ILCSOFT
# co the ilc installer
svn co https://svnsrv.desy.de/public/ilctools/ilcinstall/tags/v01-17-03-eutel ilcinstall_v01-17-03-eutel
# edit the versions to install, put "trunk" in Eudaq_version
vim $ILCSOFT/ilcinstall_v01-17-03-eutel/releases/v01-17/release-versions.py
# install and compile
cd $ILCSOFT/ilcinstall_v01-17-03-eutel
./ilcsoft-install -i examples/eutelescope/release-standalone.cfg

NOTE 16 December 2013:

We had the following error when compiling at SL6 at301:
/nfs/atlas-data06/scratch/sgrinstein/eudet_sl6b/v01-17-03/root/5.34.05/ROOT/net/netx/src/TXNetFile.cxx:59:38: error: XrdClient/XrdClientConn.hh: No such file or directory
So, we changed the ROOT version in
$ILCSOFT/ilcinstall_v01-17-03-eutel/releases/v01-17/release-versions.py
to: 
ROOT_version = "5.30.01"
(See my working area: /nfs/pic.es/user/s/sgrinstein/scratch/eudet_sl6b)
However, the best solution might be to ask the admins to add the XrdClient/XrdClientConn.hh header file to: /usr/include/xrootd

# you will see most of the relevant executables at:
ls $ILCSOFT/v01-17-03/Eutelescope/v00-09-01/external/eudaq/trunk/bin/

However, the OnlineMonitor is missing!

cd $ILCSOFT/v01-17-03/Eutelescope/v00-09-01
source build_env.sh
cd $ILCSOFT/v01-17-03/Eutelescope/v00-09-01/external/eudaq/trunk
make clean &amp;&amp; make -j USE_LCIO=0 USE_EUTELESCOPE=0

Now you should have the OnlineMonitor:
cd $ILCSOFT/v01-17-03/Eutelescope/v00-09-01/external/eudaq/trunk/bin
./OnlineMon.exe -f ~/scratch/June2013_DESY/run012602.raw

The instructions below should compile the full eudaq software:

Tried them on 18 Dec 2013 on at301 (/nfs/at3/scratch/sgrinstein/eudet_sl6b/, SL6, with ROOT 5.30.01) and they worked (they compiled, but I did not run the executables yet).

#environment
cd v01-17-03/Eutelescope/v00-09-01
source build_env.sh
cd external/eudaq/trunk
# remove Timepix detector
rm main/src/Timepix*
rm main/include/eudaq/TimepixDummyProducer.hh
# compile first with LCIO and EUTELESCOPE flags off
make clean ; make -j USE_LCIO=0 USE_EUTELESCOPE=0
# regenerates all make files of EUTelescope project.
cd ../../../build
cmake ..
# build EUtelescope
make install
# compile with LCIO and EUTELESCOPE flags on
cd -
make clean ; make -j USE_LCIO=1 USE_EUTELESCOPE=1
# rebuild EUtelescope
cd ../../../build
make install

<!--/twistyPlugin-->
 

TBMon

AIDA

Revision 22013-12-19 - JoernLange

Line: 1 to 1
 

IFAE Pixel

Line: 9 to 9
  For the collection of measurement results, please refer to the IFAE Pixel Elog.
Changed:
<
<

Useful links

>
>

Useful Links and Documentation

 
<!--Add the main topic here. i.e. create some new headings as follows:!-->
Added:
>
>
 

General Computing

Line: 42 to 46
 

dCache

Changed:
<
<
dCache is a file system for the storage of large data sets. It is e.g. used to backup the raw files and reconstructed files of our testbeams. Our dCache folder on the PIC is: /pnfs-disk/pic.es/at3/projects/Pixels .
>
>
dCache is a file system for the storage of large data sets. It is e.g. used to backup the raw files and reconstructed files of our testbeams.

Our dCache folder on the PIC is:

 /pnfs-disk/pic.es/at3/projects/Pixels 
 
<!--/twistyPlugin twikiMakeVisibleInline-->
The command to copy a file to dCache is:
Line: 68 to 76
 

Testbeam Reconstruction

TBMon

Added:
>
>

Miscellaneous

Twiki

Revision 12013-12-19 - JoernLange

Line: 1 to 1
Added:
>
>

IFAE Pixel

Introduction

This page is created by the pixel group of IFAE Barcelona. It is supposed to collect information about the pixel activities at IFAE, especially documentation, links, useful tips etc.

For the collection of measurement results, please refer to the IFAE Pixel Elog.

Useful links

<!--Add the main topic here. i.e. create some new headings as follows:!-->

General Computing

The general linux working areas are PIC (Barcelona) and LXPLUS (CERN).

Access to PIC and LXPLUS via ssh and sshfs

<!--/twistyPlugin twikiMakeVisibleInline-->
Login from a linux shell via ssh:
  •  ssh -Y picUserName@at3.pic.es 
  •  ssh -Y cernUserName@lxplus.cern.ch 
Attention! Make sure to be on the right pic machine! at303 has only SL 5.8, which sometimes leads to problems! E.g. at302 has SL 6.4.
  •  ssh -Y at302 
It is also possible to mount the pic or lxplus directories via sshfs to a previously created directory on the local machine. By this, you can e.g. use your advanced editor of choice that is installed locally to open the code that is saved remotely on pic/lxplus. The sshfs command has to be repeated every time the machine is started again, so it is helpful to create an alias in the profile (e.g. .bashrc).

 
mkdir -p pic/nfs 
sshfs picUserName@at3.pic.es:/nfs pic/nfs

mkdir -p lxplus/home
sshfs cernUserName@lxplus.cern.ch:/afs/cern.ch/user/cernUserNameInitial(oneLetter)/cernUserName lxplus/home

<!--/twistyPlugin-->

dCache

dCache is a file system for the storage of large data sets. It is e.g. used to backup the raw files and reconstructed files of our testbeams. Our dCache folder on the PIC is: /pnfs-disk/pic.es/at3/projects/Pixels .

<!--/twistyPlugin twikiMakeVisibleInline-->
The command to copy a file to dCache is:

  dccp /bin/inputFile.xx /pnfs-disk/pic.es/at3/projects/Pixels/outputFolder 

(answer from the help desk:) so far we haven't found a way to copy complete folder. Thus, to copy all files in a directory, you need to loop, e.g.:

  for f in *.root; do dccp $f /pnfs-disk/pic.es/at3/projects/Pixels/outputFolder; done 

From the pic this command works directly. If you need to copy files from lxplus the trick is that you download your file in the /tmp directory of the at3 machine with your favourite command and then you copy the file to destination with dccp command.

More information can be found here: https://giq.ifae.es/UsingdCache.pdf. If you cannot manage please call extension at IFAE 2822 and ask Alex Guinó for a joint session where he can debug what happens.

<!--/twistyPlugin-->

USBPix and STControl

Testbeams

Testbeam Reconstruction

TBMon

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