Difference: July2019DESYTBlog (8 vs. 9)

Revision 92019-07-25 - AtlasjSilicon

  META TOPICPARENT 
 name="July2019DESYTestbeam" 

 July 2019 DESY Testbeam log page 

 July 22, 2019 

8:00 breakfast meeting with Andre

8:40 registered DACHS card at bld. 6

9:30 received DACHS card

13:00 safety training (only listen, no test)

15:00 setup (there were many problem)

24:00 completed YARR system setup
 July 23, 2019 

1:00 YARR producer lauched.

1:30 RunControl PC could communicate with NI crate (telescope)

2:00 Norway 3D module did not work. it did not give signal.

3:00 revealed that RunControl PC could not communicate with YARR producer. (YARR producer did not accept orders from RC PC.)

10:00 the above issues is resolved. we were able to go with combines telescope + FEI4 system into auto trigger run.

16:00 issues about communication with RC PC and BDAQ is resolved. But issue about Event Build happened. It was that the data from BDAQ is different with data by making from Event Build.)

17:00 confirm whether KEK53-9 by using BDAQ system work

18:00 instead of Norway 3D module, installed KEK53-13 into cooling box.

19:30 exchange YARR PC to our laptop PC because YARR PC memory is too small to work properly. copy config file from YARR PC to that one. but could not download YarrEudaqProducer.

21:30 reload dry ice. temperature ~-1℃ -> -33℃

22:00 KEK53-13 tuning by using BDAQ. for tuning, supply KEK53-13 High Voltage=-200V.
 July 24, 2019 

2:00? could not catch signal from BDAQ system. so data taking by YARR system. but the data is not normal(?).

22:00 Run Control PCからremote controlできなくなった．<- UPS?が全て落ちていた．

22:30 data taking used YARR system connecting KEK53-9 applied -50 V (0.034uA). Run120~132.

23:30 stage which is boarded cooling box had been gone down.
 July 25, 2019
- META TOPICPARENT
+ name="July2019DESYTestbeam"
->
>
+:00 workshop:How to reconstract by using EUTelescope.
  YARR system 

constraction YARR system

login user:testbeam

the YARR PC IP address -> 192.168.22.199

( BDAQ PC IP -> 192.168.22.198 )

( Run Control PC IP -> 192.168.22.1 )

( NI crate IP -> 192.168.22.2 )

install new software ( https://yarr.readthedocs.io/en/latest/install/ )

and

install new firmware ( https://yarr.web.cern.ch/yarr/firmware/ -> "2019_07_21-rd53a_ohio_3chip_1tlu-xpressk7_325.bit" )
-<
<
+source /opt/Xilinux/Vivado/2016.02/settings64.sh
->
>
+$ source /opt/Xilinux/Vivado/2016.02/settings64.sh
-<
<
+python flash.sh (@ ~/work/yarr_rd53a/YARR-FW(Yarr is a symbolic link with Yarr-fw_20190722)/script)
->
>
+$ python flash.sh (@ ~/work/yarr_rd53a/YARR-FW(Yarr is a symbolic link with Yarr-fw_20190722)/script)
 select #6 (rd53a_ohio_3chip_1tlu_xpressk7_160.bit)
-<
<
+if finish, reboot.
->
>
+if finish, $ reboot.
-<
<
+./bin/scanConsole -r configs/controller/specCfg.json -c configs/connectivity/example_rd53a_setup.json -s configs/scans/rd53a/std_digitalscan.json -p (@ ~/work/yarr_rd53a/Yarr) <- this is like rd53a_test
->
>
+$ ./bin/scanConsole -r configs/controller/specCfg.json -c configs/connectivity/example_rd53a_setup.json -s configs/scans/rd53a/std_digitalscan.json -p (@ ~/work/yarr_rd53a/Yarr) <- this is like rd53a_test
 if some problems happened, check below things.this is when regulator mode working. 
 jumper is inserted at VINA (at PWR A) and VIND (at PWR D).
  cables cnnecting with RD53A power is propely hot or GND side.
  current 480~500 mA (KEK53-9 1.85V)
  voltage drop between ~~~ and ~~~
  if it happends that voltage difference between 2 hot side pins of 4 pin, you do short by jumper inserting at JP PWR.
  GND of XpressK7 need to be GND of RD53A power
 
nothing problem -> tune RD53A

this time, we used automatically tuning software by using below command.
-<
<
+./scripts/tune_rd53a.sh 1500 1500 10000 10 configs/controller/specCfg.json configs/connectivity/example_rd53a_setup.json
->
>
+$ ./scripts/tune_rd53a.sh 1500 1500 10000 10 configs/controller/specCfg.json configs/connectivity/example_rd53a_setup.json
 wait for 15~20min. if finish, do noise scan.
-<
<
+./primlist/scan53.sh noisescan KEK53-9 -m 1
->
>
+$ ./primlist/scan53.sh noisescan KEK53-9 -m 1
-<
<
+./primlist/scan53.sh noisescan KEK53-9
->
>
+$ ./primlist/scan53.sh noisescan KEK53-9
 RD53A tuning finish!!

 set producer, communicate with Run Control PC 

How to set YARR producer

read "README.md @~/work/yarr_rd53a/YarrEudaqProducer_20190722/

communicate with Run Control PC (The HOSTNAME variable needs to be set)

Run Control PCが命令を出すと，YARR producerがdescript? figure?を書き，memoryがoverflowして動作が重くなった．

->YARR producerを立てるPCを，Desktop->Laptopに変更した．

->Laptopで，Euteleproducerのsoftwareをうまくダウンロードできなかった

->Euteleproducerが問題で，その問題解決と同時にdiscriptionを書かないように修正

->producerのPCをDesktopに変更した

Can NOT communicate BDAQ producer and RunControl PC

 BDAQ 

How to tune RD53A by using BDAQ system

 TLU tutrial
-<
<
+first, install and setup software. please see https://twiki.cern.ch/twiki/bin/view/Atlas/ITkPixelTestBeamReconstruction .
->
>
+install and setup software. please refer https://twiki.cern.ch/twiki/bin/view/Atlas/ITkPixelTestBeamReconstruction .
->
>
+use data which is in /eos/atlas/atlascerngroupdisk/pixel-upgtade/itk/BeamTest/desy_2018_december_itk/native @ cern.ch, so it is better that you work in xlplus.cern.ch, for instance. you don't forget your lxplus working capacity increase. ( https://resources.web.cern.ch/resources/Manage/AFS/Settings.aspx )

for example...

$ mkdir work　

$ ln work /afs/cern.ch/work/?/[user name]

you work in the "work" directory

$ wget https://cernbox.cern.ch/index.php/s/KofU5oNLeGDQHGA/download?x-access-token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkcm9wX29ubHkiOmZhbHNlLCJleHAiOiIyMDE5LTA3LTI1VDIxOjUzOjIwLjEyNzMwMjg1NyswMjowMCIsImV4cGlyZXMiOjAsImlkIjoiMTY1NTQxIiwiaXRlbV90eXBlIjowLCJtdGltZSI6MTU1MTEwNjk3Mywib3duZXIiOiJzdGVyem8iLCJwYXRoIjoiZW9zaG9tZS1zOjQ1MDAzODUyNzM4NDYxNjk2IiwicHJvdGVjdGVkIjpmYWxzZSwicmVhZF9vbmx5Ijp0cnVlLCJzaGFyZV9uYW1lIjoiaW5zdGFsbF9ldXRlbGVzY29wZS5zaCIsInRva2VuIjoiS29mVTVvTkxlR0RRSEdBIn0.0chS7LWzcuxH7nh585DS7hWXTD_z5-UikMi4mOwxlmg -O install_telescope.sh ( -O is naming option. download "install_eutelescope")

$ source install_telescope.sh (for 40min?)

$ source ilcsoft/v01-19-02/Eutelescope/v2.0.0/build_env.sh (build environment)

$ source setup.sh

(good idea : add build_env.sh into setup.sh)

=$ wget https://cernbox.cern.ch/index.php/s/7KbNZEtbrgqSVhD/download?x-access-token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkcm9wX29ubHkiOmZhbHNlLCJleHAiOiIyMDE5LTA3LTI1VDIyOjA1OjE1LjYzMzc4ODA2KzAyOjAwIiwiZXhwaXJlcyI6MCwiaWQiOiIxNjU1NDIiLCJpdGVtX3R5cGUiOjAsIm10aW1lIjoxNTUxMTA3MDEzLCJvd25lciI6InN0ZXJ6byIsInBhdGgiOiJlb3Nob21lLXM6Mjk3Nzc4OTU0NDIzNTAwODAiLCJwcm90ZWN0ZWQiOmZhbHNlLCJyZWFkX29ubHkiOnRydWUsInNoYXJlX25hbWUiOiJjaGFuZ2VSRDUzQWdlby5zaCIsInRva2VuIjoiN0tiTlpFdGJyZ3FTVmhEIn0.aftGeKo6jgWQ86QIzhgRSdIx2BcETUkjayDEyi2i408==

-O chargeRD53Ageo.sh

$ source chargeRD53Ageo.sh

$ wget https://cernbox.cern.ch/index.php/s/fNLtd3l8LyE5WdO/download?path=%2F&x-access-token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkcm9wX29ubHkiOmZhbHNlLCJleHAiOiIyMDE5LTA3LTI1VDIyOjA5OjQwLjMzMjA4MTMwOCswMjowMCIsImV4cGlyZXMiOjAsImlkIjoiMTkzNjIzIiwiaXRlbV90eXBlIjoxLCJtdGltZSI6MTU2Mzg5NjM2OSwib3duZXIiOiJtd2VlcnMiLCJwYXRoIjoiZW9zaG9tZS1tOjIxNzIzMzg5IiwicHJvdGVjdGVkIjpmYWxzZSwicmVhZF9vbmx5Ijp0cnVlLCJzaGFyZV9uYW1lIjoiRVVUZWxXb3Jrc2hvcCIsInRva2VuIjoiZk5MdGQzbDhMeUU1V2RPIn0.s0AIhyq2RYlr7xIxbzdj64UYdyP-KNpBFBddqAs0clM&files=GBL_RD53a.tar.gz -O GBL_RD53a.tar.gz

$ tar -zxvf GBL_RD53a.tar.gz

$ cd GBL_RD53a

$ mkdir output, raw

$ cd output

$ mkdir database, histograms, lcio, steering

$ emacs -nw config.cfg 

 BasePath -> ???/GBL_RD53a
  NativePath -> /eos/atlas/atlascerngroupdisk/pixel-upgtade/itk/BeamTest/desy_2018_december_itk/native
  ???/GBL_RD53a/steering-templates
  NoOfEvents -> 25000
 
$ jobsub -c config.cfg -csv runlist.csv XXXX YYY 
 XXXX -> converter, clustering, hitmaker, alignGBL, alignGBL1, alignGBL2, fitGBL
  YYY -> run# (for example 272)
 
$ cd output/histgrams

$ root -l run000YYY-XXXX-histo.root

root[ ] new TBrowser

you can check histgrams.
  memo 

producer, communication between run control PC and BDAQ PC

cards for read out some module by creating Nakamura working test

multi module working test

--   Koji Nakamura  - 2019-07-22 

 Comments 

 
  (Edit - Preview)
 
<--/commentPlugin-->




 META FILEATTACHMENT 
 attachment="BDAQ53_TravellingModule.pdf" attr="" comment="BDAQ manual" date="1563921897" name="BDAQ53_TravellingModule.pdf" path="BDAQ53_TravellingModule.pdf" size="1196039" user="AtlasjSilicon" version="1"
- META FILEATTACHMENT
+ attachment="BDAQ53_TravellingModule.pdf" attr="" comment="BDAQ manual" date="1563921897" name="BDAQ53_TravellingModule.pdf" path="BDAQ53_TravellingModule.pdf" size="1196039" user="AtlasjSilicon" version="1"

View topic | History: r18 < r17 < r16 < r15 | More topic actions...