Difference: SciFiFibreModulesQA (1 vs. 62)

Revision 622019-09-12 - ValeryZhukov

Line: 1 to 1
 
META TOPICPARENT name="UpgradeSciFiTracker"

SciFi Module Assembly and Quality Assurance tests

Line: 794 to 794
  To perform a LIS scan:
    Added:
    >
    >
  1. save existing board36/37.cfg in sw/scifiusbboard/cfgFiles , they will be overwritten by the scan. One can restore them after the scan.
  2.  
  3. Go to your working directory (FAM_FAM)
  4. Go to lis/ and create a sub-directory for output data, e.g. scan/, cd into it. Alternatively, you can use any directory in any place.
  5. Run the scanning script: root -l -q '$USBBOARDPATH/cern_scripts/lis_tuning/scan_lis.c("../../config.root")'.
    If you run from different directory as stated above, please ensure that you have supplied a correct path to your config.root file or leave this parameter empty("") to make the script ask for bias settings..
  6. Changed:
    <
    <
  7. You get a number of files: lis_raw_??.root (with raw histograms) and lisAnalysis_??.root (with calculated pedestals, gains and LYs), where ?? is a decimal number with current modulation setting for all LIS channels. Bias settings are taken from config.root or from manual input if you don't specify the file.
  8. >
    >
  9. You get a number of files: lis_raw_??.root (with raw histograms) and lisAnalysis_??.root (with calculated pedestals, gains and LYs), where ?? is a decimal number with current modulation setting for all LIS channels. Ibias for LIS driver settings are taken from config.root or from manual input if you don't specify the file.
  10.  

    Remark: The original modulation values in the board.cfg files will be overwritten. Therefore, you should run tune_lis after the scanning procedure or manually recover these settings.

    Revision 612019-09-11 - ValeryZhukov

    Line: 1 to 1
     
    META TOPICPARENT name="UpgradeSciFiTracker"

    SciFi Module Assembly and Quality Assurance tests

    Line: 224 to 224
     
  11. Open ELOG. Register the modules to be tested in the System->Module. You need to have an account, and the link should be in the browser. Write all related information about the modules(new, retested, BTC modification,etc) setup(if changed) and all problems during the test.
  12. Set Spiroc DACs (offsets to SiPM HV). Use Vbreakdown from Db for each SiPM. For this power LV PS for all USB boxes and run ./dac_from_db. Check the error messages if appeared (should not). Check content of vbd/ folder.
  13. Deleted:
    <
    <
  14. Perform LighTightness tests (LT). Fill data by running ./check_LT, check content of LT/ folder.
  15.  
  16. Perform connectivity test. Use 'old' LIS settings, by first coping existing board36/37 cfg ./copy_cfgfiles , then go to test/ folder and run modqacern module. Put meanfull prefix, start run, check Pedestal, LIS, and some cosmics, then stop the run and save summary.
  17. Tune LIS. Use Ibias from Db to get optimised Imod by running ./tune_lis. This takes about 30min and produce cfg file in sw/ folder and txt files in lis/ folder.
  18. Changed:
    <
    <
    Copy new cfg files to local folders ./copy_cfgfiles , go to test/ folder and repeat test run to check LIS settings in new cfg files.
    >
    >
  19. Perform another test with tuned LIS settings, after ./copy_cfgfiles , go to test/ folder and run, with prefix afterlis.
  20. Perform LighTightness tests (LT). Fill data by running ./check_LT, check content of LT/ folder.
  21.  
  22. Run cosmic QA. Usually for >= 6 hours through the night. For this go to QA/ folder and run modqacern module setting QA prefix for files.
  23. Post-process data . After QA is finished, run ./sum_QA that creates root and txt files in the sum/ folder, check the files.
  24. Upload to Db. Put data into the database by running ./upload_db
  25. Revision 602019-08-26 - ValeryZhukov

    Line: 1 to 1
     
    META TOPICPARENT name="UpgradeSciFiTracker"

    SciFi Module Assembly and Quality Assurance tests

    Line: 20 to 20
      Contact persons for operation:
    Changed:
    <
    <
    Valery Zhukov joukov@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 78188 Cell(CERN): +41 76 487 6537
    >
    >
    Valery Zhukov joukov@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 78188 Cell(CERN): +41 75 411 6537
     
    Michal Dziewiecki mdziewie@cernNOSPAMPLEASE.ch Office: Cell(CERN): +48 791 221 186
    Andreas Guth andreas.guth@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 75750 Cell(CERN):
    Changed:
    <
    <
    Sebastian Bachmann bachmann@uphysiNOSPAMPLEASE.uni-heidelberg.de Office: Cell(CERN): +48 791 221 186
    >
    >
    Sebastian Bachmann sebastian.bachmann@cernNOSPAMPLEASE.ch Office: Cell(CERN): +48 791 221 186
    Alexander Malinin malinin@cernNOSPAMPLEASE.ch Office: Cell(CERN): +41 75 4110546
    Alexander Chuzo alexander.chuzo@cernNOSPAMPLEASE.ch    
    Alexander Grigoryev alexander.grigoryev@cernNOSPAMPLEASE.ch    
      Module Assembly:

    Revision 592019-08-26 - ValeryZhukov

    Line: 1 to 1
     
    META TOPICPARENT name="UpgradeSciFiTracker"

    SciFi Module Assembly and Quality Assurance tests

    Line: 451 to 451
     
  26. It takes about 30min to calibrate both modules
  27. Text files with report will be generated at the end (module_name.lis.txt) and put into lis subdirectory. Check the files and fill the check list.
  28. Config files will be configured for the last tuned setting and stored in the $USBBOARDPATH/cfgFiles.
  29. Added:
    >
    >
  30. Repeat the test run using new lis tuning parameters. Do to the main folder ./copy_cfgfiles, do to the test/ and run modqacern module (put prefix afterlistun), check the LIS spectra and decide to use it or not. (In case of the bad spectra may change Ibias, see FAQ).
  31.  

    Note that the LIS driver are connected in the staggered way to the mats, that is the mats 0 and 2 are connected to one LIS, and 1,3 to another one LIS board.

    Revision 582019-08-21 - ValeryZhukov

    Line: 1 to 1
     
    META TOPICPARENT name="UpgradeSciFiTracker"

    SciFi Module Assembly and Quality Assurance tests

    Line: 8 to 8
     Grey Room in LHCB Hall (ask for key's LHCb secretariat)
    Added:
    >
    >
    It has airconditioning/heating and overpressure (can be switched off during work, but ON during night). The shows protection is obligatory in the Grey Room. The dust and dirty work is not allowed in the room

    To operate one would need:

    • valid CERN access to the LHCb P8 surface building, control room, and Assembly hall
    • lxplus account and LHCb ELOG registration
    • Access to SciFi ProdDB
     Contact persons for operation:

    Valery Zhukov joukov@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 78188 Cell(CERN): +41 76 487 6537
    Line: 67 to 77
     SciFi Status uptodate
    Changed:
    <
    <

    Module Assembly

    >
    >

    Module Assembly at CERN

     
    Changed:
    <
    <
    The procedure steps can be seen in the assembly datasheet :
    >
    >
    The module produced from Fiber Mats in HD and NIKHEF (here MOD) are shiped to CERN and finally assembled in the Grey Room. The Cold Box (CB) Shell is connected and sealed, then the SiPM Top Cover(BTC) is attached. The assembled with cold box modue (MODCB) is checked with a few gas tightness tests and then passed to the QA tests in cosmic bench. After QA tests the MODCB are packed in the boxes and transported to the Assembly Hall for the Cframe integration.
     
    Changed:
    <
    <
    https://twiki.cern.ch/twiki/pub/LHCb/SciFiFibreModulesQA/Modassembly_v4.pdf
    >
    >
    The assembly procedure steps can be seen in the assembly checklist : https://twiki.cern.ch/twiki/pub/LHCb/SciFiFibreModulesQA/Modassembly_v4.pdf
     
    Changed:
    <
    <
    For more information contact Antonio, Lara and Robin
    >
    >
    For more information contact Antonio, Lara and Robin.
     

    CERN Cosmic Bench

    Line: 235 to 246
     
  32. Remove previous modules from the bench. Move hodoscope beneath the modules on the shell, carefully (with HV on)
  33. if needed move the rack to the side for tests. For this disconnect power (without switching off PC) and ground pin. Keep the trigger cables connected(going to hodoscope) and carefully move the rack, holding the SPIROC boards.
  34. Changed:
    <
    <
  35. Install a new module on down position, ensure module position and flatness. Put hodoscope in between to the right place (close to the center)
  36. >
    >
  37. Install a new module on down position, ensure module position and flatness. Put hodoscope in between to the right place (close to the center) using stoppers on the rails.
  38.  
  39. Ground yourself using braclet, touching the metallic parts.
  40. Mount SPIROC readout boards to the module using two M8 screws (for upper and down modules)
  41. Connect SiPM flexes. Handle them with care. Ensure that all connectors are fully pushed in. Recommended to clean up the
  42. Line: 503 to 515
     
  43. sumgaps_FAM_xxxxx_X.txt - a text file with a summary of mat-SiPM gap calculation
  44. Added:
    >
    >
    The script will also create in QA/ folder a final dualtree.root file with all dualtree merged. If there is some copied, delete it prior running the script. It will be also a link created to the last Summary.root file. (in case of modqacern crashes, see FAQ)
      The summary root files after processing contains results from the current tests(modcb), as well as from FSM test in module production centers(mod), and SIPM testing.: %TWISTY{
    Line: 626 to 642
     

    FAQ and Troubleshouting

    Deleted:
    <
    <

    No connection to USB boxes

    If during access to readout (USB boxes) program crashes (any program) the most likely reason is the LV PS. Check that their are powered on. If yes, disconnect connector and carefully check all voltages, there are fuses inside can be broken.

    Another reason can be problem with software, eg. related libs are broken. Then one can recompile the program, see above

     

    Bad SiPM-SPIROC connections and bad channels

    These connectors are critical, the used connectors are supposed to sustain ~50 connections. On the SiPM flex side the connectors are used only a few times for BTC testing, while on the SPIROC motherboard side many times, hence can have loose contacts.
    Line: 695 to 704
     
  45. do nothing, noting in ELOG
  46. Changed:
    <
    <
    Note that all operation should be registered in the ELOG.
    >
    >
    Note that all operations should be registered in the ELOG.
     

    Large SiPM current

    Line: 735 to 744
     repetition if previous data are lost/corrupt, some more extensive testing, etc. Important that the previous information is not lost, that is, the existing folder with the same name should be renamed. If only one module is retested, and the latest data should be used for QA, one has to move/rename the old summary files for related module. The upload_db should be repeated for corresponding entries to overwrite the old one. All changes should be written in the ELOG.
    Changed:
    <
    <
    >
    >

    Crashed QA cosmic test

    Most likely not enough space on the main disk (250Gb). Dont forget to move folders from tested modules to archive to clean up the space/ After cleaning can restart the run. After the crash the last summary files and dualtree.root should be available, try to open the files in root. Starting new run would not overwrite the existing one, the dualtree will be appended in postprocessing. The summary files are stored with the timestamp, i.e. status can be recovered. However in this case only last run statistics will be used. In principle the last summary file from crashed run can be merged with the new run, but one has to account for increase of statistics in LIS runs.
     

    System maintenance (for experts only)

    Line: 771 to 784
     

    Taking LIS global scan

    The LIS scan is a procedure to collect data for a specified range of LIS settings. It is not intended to be used for every module, it's just for studying LIS properties.

    Added:
    >
    >
    The existing board.cfg has to be backuped before the scan, because will be overwritten.
      To perform a LIS scan:
      Line: 781 to 795
       
    1. You get a number of files: lis_raw_??.root (with raw histograms) and lisAnalysis_??.root (with calculated pedestals, gains and LYs), where ?? is a decimal number with current modulation setting for all LIS channels. Bias settings are taken from config.root or from manual input if you don't specify the file.
    2. Changed:
      <
      <
      Remark: The original modulation values in the config files will be overwritten. Therefore, you should run tune_lis after the scanning procedure or manually recover these settings.
      >
      >
      Remark: The original modulation values in the board.cfg files will be overwritten. Therefore, you should run tune_lis after the scanning procedure or manually recover these settings.
       

      Revision 572019-08-21 - ValeryZhukov

      Line: 1 to 1
       
      META TOPICPARENT name="UpgradeSciFiTracker"

      SciFi Module Assembly and Quality Assurance tests

      Line: 118 to 118
       

      There HV line is connected to the SPIROC boards via sophisticated switch box. It allows to measure HV current precisely for each module.

      Added:
      >
      >
      The switches(4) on the SPIROC board allows to disconnect(switch up) HV from each mat SiPMs.
       

      Software

      Line: 183 to 184
        The templates for the scripts used for the running and analysis are in scifiusbboard/cern_scripts/
      Added:
      >
      >

      SciFi production Db

      One would need an account to access it Db There is a common account, ask S,Bachmann. One can access it in lhcbscifi computer by runing dblogin . The final modules after QA are in the Final Module Assemblys/F-Modules the results are at the QA on F-modules The modification (eg. LIS board or BTC) have to be registered in the Db, click Modify, Change things, and reload the modified page. Then use the restart to recreate the configs in the same folder, or start from scratch.
       

      QA test procedure

      All operation with hardware:moving modules, connections, etc should be performed only by qualified personals (see contact persons for operations)
      Changed:
      <
      <
      Most of operations on software are done with the scripts, but operator should know the procedure behind.
      >
      >
      Most of operations on software are done with scripts, but operator should know the procedure behind.
        Never switch ON SiPM HV WITHOUT LV PS ON!
      Line: 354 to 362
       The procedure will follow.

      DAC from GainAnalysis

      Added:
      >
      >
      Have to run hrdreadoutForGainCalibration (copy it from scifiusbboard/Builds/ and can modify setting inside) for each USB box separately (enter 36 or 37, and power it). The code will scan HV and estimate HV for each value iteratively. It will create the itx/ folder with iteration, you can check inside if the iterations are converged (by lokking on rms), Then select iteration there and upload to DAC as setSpirocDac $USBBOARDPATH/cfgFiles ./itx/DacFile*
       

      Connectivity test

      Line: 416 to 428
       

      LIS tuning

      Changed:
      <
      <
      INITIAL STATE: both USB-Box PS OFF, HV PS OFF
      >
      >
      INITIAL STATE: both USB-Box PS OFF, HV PS OFF
       
      1. Switch both LV ON, then HV ON (V=58V)
      Line: 429 to 441
       
    3. Config files will be configured for the last tuned setting and stored in the $USBBOARDPATH/cfgFiles.
    4. Added:
      >
      >
      Note that the LIS driver are connected in the staggered way to the mats, that is the mats 0 and 2 are connected to one LIS, and 1,3 to another one LIS board. The connection of fibers (o or 2, and 1 or 3) in each LIS boards is not defined during assembly, but determined after the LIS tune procedure, and stored as a mapping in the file.
       

      Advanced LIS tuning

      This will ask for the Ibias, allowing to change it from the nominal values read from Db. Note that the Ibias and Imod after lis tune are stored in the /home/lhcb-cern/sw/scifiusbboard/cfgFiles/board*cfg and then can be copied to the QA and test folders using ./copy_cfgfiles script. These Ibias and Imod will appear in the lis/ folder in the results files.
      Added:
      >
      >
      Note that the used Ibias are not stored in the SiPM Db section, but as listuning txt files after the QA test.
       

      QA cosmic test

      Changed:
      <
      <
      INITIAL STATE: both USB-Box PS OFF, HV PS OFF
      >
      >
      INITIAL STATE: both USB-Box PS OFF, HV PS OFF
       
      1. Use copy_cfgfiles script to copy board36.cfg and board37.cfg to working folders (QA and test).
      Line: 467 to 484
       Then new run is started automatically. The running can be stopped by clicking stop. Then slick save to save the Summary file.
      Added:
      >
      >
      At the end of all tests switch HV and then LV off.
       

      Data post-processing

      Line: 597 to 615
        </>
      <!--/twistyPlugin-->
      Changed:
      <
      <

      Putting results into the production database

      >
      >

      Putting results into production Db

        Attention: Putting data into database is a SEMI-automated process and needs an active supervision of the operator.
      Depending on the current state of the database and results, some data may remain not uploaded. One of these cases is when some relevant data already exists in the database.
      Line: 611 to 630
       If during access to readout (USB boxes) program crashes (any program) the most likely reason is the LV PS. Check that their are powered on. If yes, disconnect connector and carefully check all voltages, there are fuses inside can be broken.
      Changed:
      <
      <
      Another reason can be problem with software, eg. related libs are broken. Then one can recompile the program, see below
      >
      >
      Another reason can be problem with software, eg. related libs are broken. Then one can recompile the program, see above
       

      Bad SiPM-SPIROC connections and bad channels

      Line: 631 to 650
       

      Bad USB connections and corrupted USB libs.

      Changed:
      <
      <
      This problem manifests as crashing programs or scripts that rely on the USB box. For example modqacern or dacfiles_from_db. After checking that the USB boxes are powered, check the USB connectors on the USB box and PC. If no joy, try to recompile all Libs in scifiusbboard/
      >
      >
      This problem manifests as crashing programs or scripts that rely on the USB box, for example modqacern or dacfiles_from_db. The the most likely reason is the LV PS. Check that their are powered on. If yes, disconnect LV connector and carefully check all voltages, there are fuses inside can be broken.
       
      Added:
      >
      >
      After checking that the USB boxes are powered, check the USB connectors on the USB box and PC. If no joy, try to recompile all Libs in scifiusbboard/ If nothing helps for both USB boxes, the problem might be in PC. One can also check the status of USB drivers lsusb. If only one box is problematic, check the USB cables and connectors carefully, try to replug in the PC side.

      Can't upload DAC values

      See above, most like USB connections or missing LV PS. But it can be that the related BTC files are not available. Can happen for newly produced BTC, check in moduleTests/data/sipm folder. Then contact experts.
       

      Bad LIS connections and replacing LIS driver

      The flex or connector for the LIS driver can be broken. There are a few spare that can be used, but one have to observe the connector orientation. The connectors does'nt have locks, i.e. can be connected either way. Moreover different boards, flexes production version can have different orientations! Check carefully the specifications.

      If LIS driver has to be replaced, the Db entry should be modified and the FAM_FAM folder recreated using the new Db. The new configs will be created.

      Changed:
      <
      <
      The previous folder can be copied with some prefix.
      >
      >
      The previous folder can be copied with some prefix, or deleted.
       

      LIS tune: can't get enough

      Line: 656 to 684
       Increasing Iconst above threshold value doesnt make sense and just increases the SiPM current. However for some LIS drivers it helps, but one have to observe the increase of SiPM constant current (can see rough measurements in Kethley during LIS run), or increase of the LIS peaks in the LIS spectra. This last can be better seen in the summary root file(can produce ot for the incomplete QA run), see himodcb LIS rms, and compare with h1modcb Ped noise without LIS light.
      Added:
      >
      >
      One can also see the actual distribution of LIS LY for all channels in LIS_pe histo.
       The Imod parameter define the laser pulse amplitude that can be up to 12mA, which corresponds to the Imod~60 maximum value.
      Changed:
      <
      <
      If after LIS tune, the target values for 1.1 are not reached even for maximum Imod, one can do follwoing:
      >
      >
      If after LIS tune, the target values for 1.1 are not reached even for maximum Imod, one can do following:
       
      • try to increase/(in case of low light) or decrease (in case of large current) Ibias, checking the width of LIS peaks. To do this, identify which driver it is and rerun using tune_lis_advanced that allows to insert Ibias manually. After that do copy_cfgfiles and modqacern to see results. If helps after a few iterations, use this Ibias for QA. The final LIS settings will be stored in output txt files in the lis/ folder and used for summary files and Db upload.
      Line: 670 to 699
       

      Large SiPM current

      Changed:
      <
      <
      The KETHLEY HV PS for SiPM has a current limitation, usually 0.001A. The typical operation voltage is 58. 0V (then for each SiPM the voltages are adjusted by the SPIROC DAC). If the current is larger, the voltage is limited by this. First check the position of switched on the switch box and SPIROC board. Then check the SiPM flex connectors(clean, reconnect)
      >
      >
      The KETHLEY HV PS for SiPM has a current limitation, usually 0.009A. The typical operation voltage is 58. 0V (then for each SiPM the voltages are adjusted by the SPIROC DAC). During rump up the current can be large and the voltage can rise slowly. If the target voltage is not reached, that is, the current is above the limit. Wait for current evolution a few minutes, if stable: First check the position of switched on the switch box and SPIROC board. Then check the SiPM flex connectors(clean, reconnect)
       If everything is OK, you have a problem. First try to identify which module and SiPM flex is causing the problem (by disconnecting). The reason can be a large light leak, try to cover and fix , or electrical problem. In the latest case BTC has to be exchanged most likely.

      Revision 562019-08-21 - ValeryZhukov

      Line: 1 to 1
       
      META TOPICPARENT name="UpgradeSciFiTracker"

      SciFi Module Assembly and Quality Assurance tests

      Line: 122 to 122
       

      Software

      Changed:
      <
      <
      The software is based on scifiusbboard package used for SPIROC readout via USB,
      >
      >
      The software is based on the scifiusbboard package used for SPIROC readout via USB,
       https://gitlab.cern.ch/lhcb-scifi/scifiusbboard The installation requires a special versions of Linux and root, so cant be run on standard PC.
      Line: 149 to 148
       In this case program will recognise the format. To save summary, should type save as usual. Note that the summary root files contains two types of histogramms; histo filled with current run, and the accumulated histograms with the whole statistics (AllRuns).
      Added:
      >
      >
      The input settings for the modqacern is read out from the usbboard*.cfg files stored locally (contrary to the strosmic). This cfg files contain information about uplinks and, important, the LIS settings, such as Ibias and Imod. Note that after lis_tune the tuned settings are saved not in the local cfg files but in the scfiusbboard/cfgFiles/ and must be copied to the running folder using ./copy_cfgfiles script, or manually.

      The templates for the scripts used for the running and analysis are in scifiusbboard/cern_scripts/. The operation and analysis codes are made as root macros that are called from the scripts created by the start script taking into account the locations and configs. The start script creates the scripts that can be run from the corresponding folder. It also creates the config files containing all relations. The cern_scripts includes:

      • lis_tuning that make the Imod scan trying to reach target Ly for the LIS using tune_lis or tune_lis_advanced Also there is a Imod scan code (optional, not in the templates) that just scan Imod.
      • cosmic that analysing all data called from the sum_QA script. The anadual process the dualtree with the selected hits (one hit per plane) that allows to calculate cluster size for vertical track, and the sumanalqa that includes the results of the anadual, Summary files produced in QA and module tests, as well as lis, LT tests and Vbd files, and analzing for bad channels, etc. * LT just a query to fill a file with light tightness test
      • vdb have a script to extract Vbd from SiPM Db for each BTC and store it as a root histo. This part currently can't run on the lhcbscifi PC, that is, the filesare produced elswhere and copied to /home/lhcb-cern/moduleTest/data/sipm. Then used by dac_from_db script and sum_QA
      • ana example of analysis of sum root files
       
      Deleted:
      <
      <
      The templates for the scripts used for the running and analysis are in scifiusbboard/cern_scripts/
       

      Computing

      Line: 253 to 269
        Created Config files:
      config.txt is a config file with entered module data, including obtained from Db, and .config.root the same, but as root file, this one is used for all scripts, i.e.
      Changed:
      <
      <
      doesnt make sense to modify txt file.
      >
      >
      doesnt make sense to modify the txt file only.
        Scripts:
        Line: 414 to 430
         

        Advanced LIS tuning

        Changed:
        <
        <
        >
        >
        This will ask for the Ibias, allowing to change it from the nominal values read from Db. Note that the Ibias and Imod after lis tune are stored in the /home/lhcb-cern/sw/scifiusbboard/cfgFiles/board*cfg and then can be copied to the QA and test folders using ./copy_cfgfiles script. These Ibias and Imod will appear in the lis/ folder in the results files.
         

        QA cosmic test

        Line: 623 to 642
         The previous folder can be copied with some prefix.
        Changed:
        <
        <

        LIS tune: not enough light

        >
        >

        LIS tune: can't get enough

         LIS tune is used to find the LIS driver setting that deliver light enough to see 5 p.e. with >1% of events (from total 8000). This corresponds to the average 1.5 p.e. for each driver (512 channels, or one mat). Obviously across the mat the light yield from LIS is not uniform, usually rising toward side where the light fiber is connected to the light bar, however the average per driver (mat) is used sofar. This 1.5 p.e. target may not be reached for some mats, especially mat 0 and 2 that have light bar far from the fiber mat, which is covered by the black foil. This black foil
        Line: 650 to 669
         Note that all operation should be registered in the ELOG.
        Added:
        >
        >

        Large SiPM current

        The KETHLEY HV PS for SiPM has a current limitation, usually 0.001A. The typical operation voltage is 58. 0V (then for each SiPM the voltages are adjusted by the SPIROC DAC). If the current is larger, the voltage is limited by this. First check the position of switched on the switch box and SPIROC board. Then check the SiPM flex connectors(clean, reconnect) If everything is OK, you have a problem. First try to identify which module and SiPM flex is causing the problem (by disconnecting). The reason can be a large light leak, try to cover and fix , or electrical problem. In the latest case BTC has to be exchanged most likely.

        Note that the current can increase significantly during the LIS tests, this is also a bad sign, can be related to the large Ibias current. Usually the LISspectra lokks bad in this case, and the Ibias can be reduced and lis tuning repeated.

         

        Cosmic hodoscope trigger rate

        The typical trigger rate of cosmic hodoscope is about 150 Hz ranging in 120-170 Hz. Much lower or much higher rate can be due to:
          Line: 716 to 747
           To perform a LIS scan:
          1. Go to your working directory (FAM_FAM)
          Changed:
          <
          <
        • Go to lis/ and create a sub-directory for output data, e.g. =scan/, cd into it. Alternatively, you can use any directory in any place.
        • Run the scanning scipt: root -l -q '$USBBOARDPATH/cern_scripts/lis_tuning/scan_lis.c("../../config.root")'.
        • >
          >
        • Go to lis/ and create a sub-directory for output data, e.g. scan/, cd into it. Alternatively, you can use any directory in any place.
        • Run the scanning script: root -l -q '$USBBOARDPATH/cern_scripts/lis_tuning/scan_lis.c("../../config.root")'.
        •   If you run from different directory as stated above, please ensure that you have supplied a correct path to your config.root file or leave this parameter empty("") to make the script ask for bias settings..
        • You get a number of files: lis_raw_??.root (with raw histograms) and lisAnalysis_??.root (with calculated pedestals, gains and LYs), where ?? is a decimal number with current modulation setting for all LIS channels. Bias settings are taken from config.root or from manual input if you don't specify the file.
        • Revision 552019-08-19 - ValeryZhukov

          Line: 1 to 1
           
          META TOPICPARENT name="UpgradeSciFiTracker"

          SciFi Module Assembly and Quality Assurance tests

          Line: 611 to 611
           
        • Extra noise in LIS spectra (large width of LIS peaks).
        • Added:
          >
          >

          Bad USB connections and corrupted USB libs.

          This problem manifests as crashing programs or scripts that rely on the USB box. For example modqacern or dacfiles_from_db. After checking that the USB boxes are powered, check the USB connectors on the USB box and PC. If no joy, try to recompile all Libs in scifiusbboard/
           

          Bad LIS connections and replacing LIS driver

          The flex or connector for the LIS driver can be broken. There are a few spare that can be used, but one have to observe the connector orientation. The connectors does'nt have locks, i.e. can be connected either way. Moreover different boards, flexes production version can have different orientations! Check carefully the specifications.

          Revision 542019-08-16 - ValeryZhukov

          Line: 1 to 1
           
          META TOPICPARENT name="UpgradeSciFiTracker"

          SciFi Module Assembly and Quality Assurance tests

          Line: 630 to 630
            should be big enough to be above thresholds for Light-Icurr curve. The optimal Ibias values are measured at RWTH and are extracted from Db. The Ibias=10 corresponds to the Iconst=15.5mA that covers most of LIS driver threshold values. Increasing Iconst above threshold value doesnt make sense and just increases the SiPM current. However for some LIS drivers it helps,
          Changed:
          <
          <
          but one have to observe the increase of SiPM constant current (the present setup doesnt have this possibility), or increase of the LIS peaks in the LIS spectra (possible)
          >
          >
          but one have to observe the increase of SiPM constant current (can see rough measurements in Kethley during LIS run), or increase of the LIS peaks in the LIS spectra.
           This last can be better seen in the summary root file(can produce ot for the incomplete QA run), see himodcb LIS rms, and compare with h1modcb Ped noise without LIS light. The Imod parameter define the laser pulse amplitude that can be up to 12mA, which corresponds to the Imod~60 maximum value. If after LIS tune, the target values for 1.1 are not reached even for maximum Imod, one can do follwoing:
            Changed:
            <
            <
          • try to increase Ibias, checking the width of LIS peaks are not increasing too much. To do this, identify which driver it is and rerun using tune_lis_advanced that allows to insert Ibias manually. After that and copy_cfgfiles and modqacern to see results. If helps after a few iterations, use this Ibias for QA. The final LIS settings will be stored in output files in the lis folder and threfore used for summary files and Db upload. Note that the initial Ibias in the Db remains enchanged.
          • exchange LIS driver with smaller Ibias (as in Db). Usually this means slightly large LIS light output. The exchange means you have to change the Db entry for the corresonding module and rerun start script (or use restart)
          • >
            >
          • try to increase/(in case of low light) or decrease (in case of large current) Ibias, checking the width of LIS peaks. To do this, identify which driver it is and rerun using tune_lis_advanced that allows to insert Ibias manually. After that do copy_cfgfiles and modqacern to see results. If helps after a few iterations, use this Ibias for QA. The final LIS settings will be stored in output txt files in the lis/ folder and used for summary files and Db upload. Note that the initial Ibias in the Db for each LIS driver remains enchanged.
          • exchange LIS driver with smaller Ibias (as in Db). Usually this means slightly large LIS light output. The exchange means you have to change the Db entry for the corresponding module and rerun start script (or use restart).
          •  
          • do nothing, noting in ELOG
          • Changed:
            <
            <
            >
            >
            Note that all operation should be registered in the ELOG.
             

            Cosmic hodoscope trigger rate

            Revision 532019-08-15 - ValeryZhukov

            Line: 1 to 1
             
            META TOPICPARENT name="UpgradeSciFiTracker"

            SciFi Module Assembly and Quality Assurance tests

            Line: 120 to 120
             There HV line is connected to the SPIROC boards via sophisticated switch box. It allows to measure HV current precisely for each module.
            Changed:
            <
            <

            Software and computing

            >
            >

            Software

              The software is based on scifiusbboard package used for SPIROC readout via USB, https://gitlab.cern.ch/lhcb-scifi/scifiusbboard The installation requires a special versions of Linux and root, so cant be run on standard PC.
            Added:
            >
            >
            To compile can try run make all in the scifiusbboard folder using existing Makefile. Note that if some new files are added, need to rerun qmake after modification of pro file.

            One can use strosmic90 with one or two modules, eg: strosmic90 halfmodule or strosmic90 module used fortesing in production centers, for some tests.

             
            Changed:
            <
            <
            One can use strosmic90 with one or two modules, eg: strosmic90 halfmodule or strosmic90 module The modified version is in HD2CERN scifiusbboard/utils/modqacern to run type in the appropriate folder:
            >
            >
            The modified version to be used at CERN for QA is in HD2CERN scifiusbboard/utils/modqacern to run it, type in the appropriate folder:
             modqacern module

            It include several features:

            Line: 137 to 141
             
            • have some extra histos in the summary
            • some modifications in LIS gain calculations, etc...
            Changed:
            <
            <
            In the GUI one can add prefix to all raw files with uplink data, and summary files. Type start to start running. After starting the run, it runs 1000 events for the pedestal and then 8000 events for the LIS (takes ~1min) after that the related histograms are appearing and can be inspected. The raw file (root) is created with the prefix+unix time stamp, and the dualtree+time stamp. When run is finished (30min) another two files are created; summary file+time stamp, and the equivalent Summary_last.root file, the last is always containing the last summary. The created Summary files can be inspected by root during the run. The dualtree can be also seen by root, but should be copied first (to avoid locking when programm is running). If you copy dualtree, dont use dualtree name in the copied files because all files with dualtree names are used further on for analysis. The summary file is saved by taping on save after stop.
            >
            >
            Similar to old code in the GUI one can add prefix to all raw files with uplink data, and summary files. Type start to start running. After starting the run, it runs 1000 events for the pedestal and then 8000 events for the LIS (takes ~1min), after that the related histograms are appearing in GUI and can be inspected. The raw file (prefix_timestamp.root) is created, and the root tree with selected events with two hits in two planes dualtree_time stamp is filled. When run is finished (30min) another two files are created; summary file A_Summary+prefix+time stamp, and the equivalent Summary_last.root file, the last is always containing the last summary. The created Summary files can be inspected by root browser during the run. The dualtree can be also seen by root, but should be copied first (to avoid locking when program is filling data). If you copy dualtree, dont use dualtree name in the copied files because all files with dualtree names are used further on for the analysis. The final summary file with total statistics should be also saved by taping on save after stop
             
            Changed:
            <
            <
            One can reprocess raw data by running modqacern  rawfilenames.root In this case program will recognise the format, to save summary, should type save.
            >
            >
            One can reprocess raw data by running modqacern  rawfilenames.root (in case you miss some summary file) In this case program will recognise the format. To save summary, should type save as usual. Note that the summary root files contains two types of histogramms; histo filled with current run, and the accumulated histograms with the whole statistics (AllRuns).
             
            Added:
            >
            >
            The templates for the scripts used for the running and analysis are in scifiusbboard/cern_scripts/

            Computing

             The lhcbscifi PC is connected to cern network via wifi. To connect externally use lhcb-cern@lhcbscifi.dyndns.cern.ch. Outside CERN one have to connect to lxplus first.
            Line: 172 to 180
              Check the assembly checklists (attached) and prepare a new ModuleQA checklists for each module.
          • Initialize. Create directory structure, by running script ./start
          • Changed:
            <
            <
            This will create folder with FAM[uppermodulId]_FAM[downmoduleId] and put there config.txt,root files and all needed scripts. Ensure that all information is correctly downloaded from Db by checking config.txt
            >
            >
            This will create folder with FAM[uppermodulId]_FAM[downmoduleId] and put there config.txt, config.root files and all needed scripts. Ensure that all information is correctly downloaded from the Db by checking config.txt.
              Go to the created folder.
            Changed:
            <
            <
          • Open ELOG ELOG. Register the modules to be tested in the System->Module. You need to have an account, and the link should be in the browser. Write all related information about the modules(new, retested, BTC modification,etc) setup(if changed) and all problems during the test.
          • >
            >
          • Open ELOG. Register the modules to be tested in the System->Module. You need to have an account, and the link should be in the browser. Write all related information about the modules(new, retested, BTC modification,etc) setup(if changed) and all problems during the test.
          •  
          • Set Spiroc DACs (offsets to SiPM HV). Use Vbreakdown from Db for each SiPM. For this power LV PS for all USB boxes and run ./dac_from_db. Check the error messages if appeared (should not). Check content of vbd/ folder.
          • Perform LighTightness tests (LT). Fill data by running ./check_LT, check content of LT/ folder.
          • Changed:
            <
            <
          • Perform connectivity test using 'old' LIS settings. First copy existing board36/37 cfg by ./copy_cfgfiles then go to test/ folder and run modqacern module. Put meanfull prefix, then start run, check Pedestal, LIS, some cosmics, stop and save summary.
          • >
            >
          • Perform connectivity test. Use 'old' LIS settings, by first coping existing board36/37 cfg ./copy_cfgfiles , then go to test/ folder and run modqacern module. Put meanfull prefix, start run, check Pedestal, LIS, and some cosmics, then stop the run and save summary.
          •  
          • Tune LIS. Use Ibias from Db to get optimised Imod by running ./tune_lis. This takes about 30min and produce cfg file in sw/ folder and txt files in lis/ folder. Copy new cfg files to local folders ./copy_cfgfiles , go to test/ folder and repeat test run to check LIS settings in new cfg files.
          • Changed:
            <
            <
          • Run cosmic QA for >= 6 hours, For this go to QA/ folder and run modqacern module setting QA prefix for files
          • Post-process data . After QA is finished, run ./sum_QA that creates root files in the sum folder.
          • >
            >
          • Run cosmic QA. Usually for >= 6 hours through the night. For this go to QA/ folder and run modqacern module setting QA prefix for files.
          • Post-process data . After QA is finished, run ./sum_QA that creates root and txt files in the sum/ folder, check the files.
          •  
          • Upload to Db. Put data into the database by running ./upload_db
          • Changed:
            <
            <
          • Archive data. Move FAM_FAM folder to the archive in order to save space. Each test usually takes about 40Gb.
          • Disconnect modules and store it either on the bench or in the transportation box. Put the checklists together with assembly ones.
          • >
            >
          • Archive data. Move FAM_FAM folder to the archive in order to save space, each test usually takes about 40Gb.
          • Dismount. Disconnect modules and store it either on the bench or in the transportation box. Put the QA tests checklists together with assembly ones in the folder attached to the modules.
          •  

            All steps has to be registered in the checklist https://twiki.cern.ch/twiki/pub/LHCb/SciFiFibreModulesQA/Modtest_v4.pdf: Modtest_v4.pdf

            Added:
            >
            >
            and some important information in the ELOG, see previous entries for examples.
             

            Installation

            Line: 223 to 232
             
          • Type ./start
          • Answer all questions given by the script
          • If there are problems with accessing database, probably you're not logged in. Break the script and type ./dblogin
          • Changed:
            <
            <
            If this not working, problem with Db access. One can still work offline(i.e answering no on Db access during the scripts), but is not recommended. However it might be needed if entries in Db are not correct (eg. wrong BTC, or Ibias in LIS, etc).
            >
            >
            If this not working, problem with Db access. One can still work offline(i.e answering NO on Db access during the scripts), but is not recommended, because one need to know all relations of objects. However it might be needed if entries in Db are not correct (eg. wrong BTC, or Ibias in LIS, etc), though it is recommended to correct them
             

            Following folders are created:

            Line: 297 to 307
              INITIAL STATE:both USB-Box LV PS OFF, HV PS OFF
            Changed:
            <
            <
            Note that this procedure is needed once at the begining of all tests with new SiPM (re)connected to the SPIROC.
            >
            >
            Note that this procedure is needed once at the beginning of all tests with new SiPM (re)connected to the SPIROC.

            The procedure assumes that all information from needed BTC is already downloaded into the moduleTests/data and correctly formatted. If this particular BTC is not in the Db, the Vbd from Db can not be used! Please contact experts (AG).

             
            Changed:
            <
            <
            Automated procedure:
            >
            >
            Automated procedure for using Db:
             
            1. Ensure that HV is OFF, then set both LV PS ON
            2. Run ./dac_from_db It takes a few minutes, check for errors on the screen.
            Line: 320 to 334
              Fill the check list.
            Added:
            >
            >
            The alternative procedure to have correction for SPIROC DAC is to run gainAnalysis =  from =scifiusbboard/utils using the LIS signals. The procedure will follow.
             
            Added:
            >
            >

            DAC from GainAnalysis

             

            Connectivity test

            Line: 396 to 413
             
          • Config files will be configured for the last tuned setting and stored in the $USBBOARDPATH/cfgFiles.
          • Added:
            >
            >

            Advanced LIS tuning

             

            QA cosmic test

            INITIAL STATE: both USB-Box PS OFF, HV PS OFF

            Line: 522 to 542
             

            Archiving results locally

            After the tests the whole directory has to copied into moduleTests/cern_data/larchive.

            Changed:
            <
            <
            From 17.05.2019 all data are stored in FAM_new folder.
            >
            >
            From 17.05.2019 all data are stored in FAM_new folder assuming the modules are (re)produced with the modified BTC, that is, some modules are retested.
             There are a few scripts:
            • process_sum_all - reprocess all data with sum_QA scripts
            Line: 591 to 611
             
          • Extra noise in LIS spectra (large width of LIS peaks).
          • Added:
            >
            >

            Bad LIS connections and replacing LIS driver

            The flex or connector for the LIS driver can be broken. There are a few spare that can be used, but one have to observe the connector orientation. The connectors does'nt have locks, i.e. can be connected either way. Moreover different boards, flexes production version can have different orientations! Check carefully the specifications.

            If LIS driver has to be replaced, the Db entry should be modified and the FAM_FAM folder recreated using the new Db. The new configs will be created. The previous folder can be copied with some prefix.

             

            LIS tune: not enough light

            LIS tune is used to find the LIS driver setting that deliver light enough to see 5 p.e. with >1% of events (from total 8000). This corresponds to the average 1.5 p.e.
            Changed:
            <
            <
            for each driver (512 channels, or one mat). Obviously across the mat the light yield from LIS is not uniform, usually rising toward side where the light fiber is connected to the light bar, however the average is used sofar. This 1.5 p.e. target may not be reached for some mats, especially mat 0 and 2 that have light bar near the fiber mat, which is covered by the black foil. This black foil can reduce the light input for the light bar. The LIS light can be increased by increasing duration of the LIS pulse. The SPIROC readout can provide only Tw=10ns pulse, while
            >
            >
            for each driver (512 channels, or one mat). Obviously across the mat the light yield from LIS is not uniform, usually rising toward side where the light fiber is connected to the light bar, however the average per driver (mat) is used sofar. This 1.5 p.e. target may not be reached for some mats, especially mat 0 and 2 that have light bar far from the fiber mat, which is covered by the black foil. This black foil can reduce the light input from the light bar. The LIS light can be increased by increasing duration of the LIS pulse. The SPIROC readout can provide only Tw=10ns pulse, while
             the final PACIFIC readout up to 20ns (the relation of LIS LY and Tw is not linear, above 20ns not much gain). Thus during LIS tune two target values are used 1.5 p.e. and 1.1. p.e. that last corresponds to the 15ns pulse, and therefore two LIS settings.
            Line: 613 to 639
             insert Ibias manually. After that and copy_cfgfiles and modqacern to see results. If helps after a few iterations, use this Ibias for QA. The final LIS settings will be stored in output files in the lis folder and threfore used for summary files and Db upload. Note that the initial Ibias in the Db remains enchanged.
            Changed:
            <
            <
          • exchange LIS driver with smaller Ibias (as in Db). Usually this means slightly large LIS light output. The exchange means you have to change the Db entry for the corresonding module and rerun start script. (or use restart)
          • >
            >
          • exchange LIS driver with smaller Ibias (as in Db). Usually this means slightly large LIS light output. The exchange means you have to change the Db entry for the corresonding module and rerun start script (or use restart)
          •  
          • do nothing, noting in ELOG
          • Line: 629 to 658
             The lhcbscifi PC doesn't have internet cable connection, it run via wifi board installed in the PC. If there is o connection, check that the wifi is working (using your laptop/mobil). Then try to restart wifi server in PC
            Changed:
            <
            <

            Recompile software

            >
            >

            Missed Db connection, or no entries

            If the relations between objects is not known, the testing is impossible. If some information is missed in Db, better first to find out what and enter in Db. The testing require some information to be downloaded and preprocessed already, eg: * the Vbd for the BTC that is extracted from SiPM testing, the prerpocessing order things in correct way. This is used for SPIROC DAC prior to any measurements. * Ibias current for LIS driver used during LIS tune * the results from modtest in production centers (HD and NIKHEF), used in final analysis

            Retesting the module

            There are a few reasons to retest module(s); reassembly fixing BTC problem or any other problem without changing components, reassembly with changed components, repetition if previous data are lost/corrupt, some more extensive testing, etc. Important that the previous information is not lost, that is, the existing folder with the same name should be renamed. If only one module is retested, and the latest data should be used for QA, one has to move/rename the old summary files for related module. The upload_db should be repeated for corresponding entries to overwrite the old one. All changes should be written in the ELOG.
             
            Deleted:
            <
            <
            Can try run make all in the scifiusbboard folder using existing Makefile. Note that if some new files are added, need to rerun qmake.
             

            System maintenance (for experts only)

            Revision 522019-08-14 - ValeryZhukov

            Line: 1 to 1
             
            META TOPICPARENT name="UpgradeSciFiTracker"

            SciFi Module Assembly and Quality Assurance tests

            Line: 11 to 11
             Contact persons for operation:

            Valery Zhukov joukov@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 78188 Cell(CERN): +41 76 487 6537
            Deleted:
            <
            <
            Andreas Guth andreas.guth@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 75750 Cell(CERN):
             
            Michal Dziewiecki mdziewie@cernNOSPAMPLEASE.ch Office: Cell(CERN): +48 791 221 186
            Added:
            >
            >
            Andreas Guth andreas.guth@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 75750 Cell(CERN):
             
            Sebastian Bachmann bachmann@uphysiNOSPAMPLEASE.uni-heidelberg.de Office: Cell(CERN): +48 791 221 186
            Changed:
            <
            <
            Assembly:
            >
            >
            Module Assembly:
             
            Antonio Pelligrino antonio@nikhefNOSPAMPLEASE.nl
            Lara Veldt lveldt@nikhefNOSPAMPLEASE.nl
            Line: 70 to 69
             

            Module Assembly

            Changed:
            <
            <
            The procedure steps can be seen in the :
            >
            >
            The procedure steps can be seen in the assembly datasheet :
             
            Changed:
            <
            <
            https://twiki.cern.ch/twiki/pub/LHCb/SciFiFibreModulesQA/Modassembly_v4.pdf: Modassembly_v4.pdf
            >
            >
            https://twiki.cern.ch/twiki/pub/LHCb/SciFiFibreModulesQA/Modassembly_v4.pdf
              For more information contact Antonio, Lara and Robin
            Line: 169 to 168
             The standard procedure is following, more detail will follow:

              Changed:
              <
              <
            1. Install two modules on the upper and down cosmic bench positions, and cosmic hodoscope in between.
            2. Initialize directory structure, by running scripts, ensure that all information is correctlybdownloaded from Db
            3. >
              >
            4. Install. Place two modules on the upper and down cosmic bench positions, and cosmic hodoscope in between. Check the assembly checklists (attached) and prepare a new ModuleQA checklists for each module.
            5. Initialize. Create directory structure, by running script
            6.   ./start This will create folder with FAM[uppermodulId]_FAM[downmoduleId] and put there config.txt,root files and all needed scripts.
              Changed:
              <
              <
              Go there.
            7. Enter ELOG ELOG and register the modules to be tested in the System->Module. You need to have an account, and the link should be in the browser. Write all related information about the modules(new, retested, BTC modification,etc) setup(if changed) and all problems during the QA test.
            8. Set Spiroc DACs (offsets to SiPM HV) using Vbreakdown from Db for each SiPM. Power PS for all USB boxes and run ./dac_from_db
            9. Perform LighTightness tests (LT) and fill data by running ./check_LT.
            10. Perform connectivity test using all LIS settings. First copy old cfg by ./copy_cfgfiles then fo to test folder and run modqacern module. Put meanfull prefix, start run, check all, and save summary.
            11. Tune LIS using Ibias from Db to get optimised Imod by running ./tune_lis. This takes about 30min and produce cfg file in sw/ folder and txt files in lis/ folder. Copy new cfg files to local folders ./copy_cfgfiles , go to test/ folder and repeat test run to check LIS settings.
            12. Run cosmic QA for >= 6 hours. Go to QA/ folder and run modqacern module setting QA prefix
            13. >
              >
              Ensure that all information is correctly downloaded from Db by checking config.txt Go to the created folder.
            14. Open ELOG ELOG. Register the modules to be tested in the System->Module. You need to have an account, and the link should be in the browser. Write all related information about the modules(new, retested, BTC modification,etc) setup(if changed) and all problems during the test.
            15. Set Spiroc DACs (offsets to SiPM HV). Use Vbreakdown from Db for each SiPM. For this power LV PS for all USB boxes and run ./dac_from_db. Check the error messages if appeared (should not). Check content of vbd/ folder.
            16. Perform LighTightness tests (LT). Fill data by running ./check_LT, check content of LT/ folder.
            17. Perform connectivity test using 'old' LIS settings. First copy existing board36/37 cfg by ./copy_cfgfiles then go to test/ folder and run modqacern module. Put meanfull prefix, then start run, check Pedestal, LIS, some cosmics, stop and save summary.
            18. Tune LIS. Use Ibias from Db to get optimised Imod by running ./tune_lis. This takes about 30min and produce cfg file in sw/ folder and txt files in lis/ folder. Copy new cfg files to local folders ./copy_cfgfiles , go to test/ folder and repeat test run to check LIS settings in new cfg files.
            19. Run cosmic QA for >= 6 hours, For this go to QA/ folder and run modqacern module setting QA prefix for files
            20.  
            21. Post-process data . After QA is finished, run ./sum_QA that creates root files in the sum folder.
            22. Changed:
              <
              <
            23. Put data into the database by running ./upload_db
            24. Move FAM_FAM folder to the archive in order to save space. Each test usually takes about 40Gb.
            25. >
              >
            26. Upload to Db. Put data into the database by running ./upload_db
            27. Archive data. Move FAM_FAM folder to the archive in order to save space. Each test usually takes about 40Gb.
            28. Disconnect modules and store it either on the bench or in the transportation box. Put the checklists together with assembly ones.
            29.  

              All steps has to be registered in the checklist https://twiki.cern.ch/twiki/pub/LHCb/SciFiFibreModulesQA/Modtest_v4.pdf: Modtest_v4.pdf

              Changed:
              <
              <

              Initializing directory structure for measurements

              >
              >

              Installation

              INITIAL STATE:both USB-Box LV PS OFF, HV PS OFF

              1. Disconnect tested modules; LIS and SPIROC using a grabbing tool. Position the SPIROC boards on the rack safely.
              2. Remove previous modules from the bench. Move hodoscope beneath the modules on the shell, carefully (with HV on)
              3. if needed move the rack to the side for tests. For this disconnect power (without switching off PC) and ground pin. Keep the trigger cables connected(going to hodoscope) and carefully move the rack, holding the SPIROC boards.
              4. Install a new module on down position, ensure module position and flatness. Put hodoscope in between to the right place (close to the center)
              5. Ground yourself using braclet, touching the metallic parts.
              6. Mount SPIROC readout boards to the module using two M8 screws (for upper and down modules)
              7. Connect SiPM flexes. Handle them with care. Ensure that all connectors are fully pushed in. Recommended to clean up the SPIROC motherboard connectors by isopropanol.
              8. Connect LIS flex cables.
              9. Switch ON both LV PS then HV PS (58.0V) only after LV is ON. Check total current (should be ~0.012A, but higher during ramping)
              10. Switch HV OFF

              Fill the check list for both modules.

              Initialising directory structure for measurements

                There's a script for creating a directory structure (and some further helpful scripts) for each new measurement session (one side of a module pair).
                Line: 213 to 237
                 
              1. .../lis/ - a directory for LIS tuning results
              2. .../QA/ - a directory for cosmic data and results
              3. .../test/ - a directory for connectivity and other test cosmic runs
              4. Changed:
                <
                <
              5. .../sum/ - a directory for cosmic data analysis
              6. >
                >
              7. .../LT/ -for LightT ightness test
              8. .../sum/ - a directory for cosmic data analysis results
              9.  

                Created Config files:

                Changed:
                <
                <
                config.txt is a config file with entered module data, including obtained from Db, and .config.root the same, but as root file used for other scripts.
                >
                >
                config.txt is a config file with entered module data, including obtained from Db, and .config.root the same, but as root file, this one is used for all scripts, i.e. doesnt make sense to modify txt file.
                  Scripts:
                  Line: 267 to 293
                   </>
                  <!--/twistyPlugin-->
                  Deleted:
                  <
                  <

                  Installation

                  INITIAL STATE:both USB-Box LV PS OFF, HV PS OFF

                  1. Disconnect tested modules; LIS and SPIROC using a grabbing tool. Position the SPIROC boards on the rack safely.
                  2. Remove previous modules from the bench. Move hodoscope beneath the modules on the shell, carefully (with HV on)
                  3. if needed move the rack to the side for tests. For this disconnect power (without switching off PC) and ground pin. Keep the trigger cables connected(going to hodoscope) and carefully move the rack, holding the SPIROC boards.
                  4. Install a new module on down position, ensure module position and flatness. Put hodoscope in between to the right place (close to the center)
                  5. Ground yourself using braclet, touching the metallic parts.
                  6. Mount SPIROC readout boards to the module using two M8 screws (for upper and down modules)
                  7. Connect SiPM flexes. Handle them with care. Ensure that all connectors are fully pushed in.
                  8. Connect LIS flex cables.
                  9. Switch ON both LV PS then HV PS (58.0V) only after LV is ON. Check total current (should be ~0.012A, but higher during ramping)
                  10. Switch HV OFF

                  Fill the check list for both modules.

                   

                  Downloading Vdb info and setting Spiroc DACs

                  INITIAL STATE:both USB-Box LV PS OFF, HV PS OFF

                  Line: 594 to 600
                   the final PACIFIC readout up to 20ns (the relation of LIS LY and Tw is not linear, above 20ns not much gain). Thus during LIS tune two target values are used 1.5 p.e. and 1.1. p.e. that last corresponds to the 15ns pulse, and therefore two LIS settings.
                  Changed:
                  <
                  <
                  The LIS driver is steered by two values in the setting Imodulation

                  >
                  >
                  The LIS driver is steered by two values in the settings. The Ibias parameter define a constant current of GBLD(laser driver) Icons= 2 mA + Ibias x 0.16 mA. The 2.5mA is subtracted in LIS mezzanine to keep Icons~0 if no Ibias defined. The max Iconst= 42mA and should be big enough to be above thresholds for Light-Icurr curve. The optimal Ibias values are measured at RWTH and are extracted from Db. The Ibias=10 corresponds to the Iconst=15.5mA that covers most of LIS driver threshold values. Increasing Iconst above threshold value doesnt make sense and just increases the SiPM current. However for some LIS drivers it helps, but one have to observe the increase of SiPM constant current (the present setup doesnt have this possibility), or increase of the LIS peaks in the LIS spectra (possible) This last can be better seen in the summary root file(can produce ot for the incomplete QA run), see himodcb LIS rms, and compare with h1modcb Ped noise without LIS light. The Imod parameter define the laser pulse amplitude that can be up to 12mA, which corresponds to the Imod~60 maximum value. If after LIS tune, the target values for 1.1 are not reached even for maximum Imod, one can do follwoing:
                  • try to increase Ibias, checking the width of LIS peaks are not increasing too much. To do this, identify which driver it is and rerun using tune_lis_advanced that allows to insert Ibias manually. After that and copy_cfgfiles and modqacern to see results. If helps after a few iterations, use this Ibias for QA. The final LIS settings will be stored in output files in the lis folder and threfore used for summary files and Db upload. Note that the initial Ibias in the Db remains enchanged.
                  • exchange LIS driver with smaller Ibias (as in Db). Usually this means slightly large LIS light output. The exchange means you have to change the Db entry for the corresonding module and rerun start script. (or use restart)
                  • do nothing, noting in ELOG
                   

                  Cosmic hodoscope trigger rate

                  Added:
                  >
                  >
                  The typical trigger rate of cosmic hodoscope is about 150 Hz ranging in 120-170 Hz. Much lower or much higher rate can be due to:
                  • No HV. Check it, switch Off and On.
                  • some thresholds in discriminators are off (due to defected trimmers). Try to turn threshold a bit, see results,
                  • some extra RF noise affecting hodoscope readout. Then can try to increase thresholds (loosing efficiency)
                   

                  PC wifi

                  Added:
                  >
                  >
                  The lhcbscifi PC doesn't have internet cable connection, it run via wifi board installed in the PC. If there is o connection, check that the wifi is working (using your laptop/mobil). Then try to restart wifi server in PC
                   

                  Recompile software

                  Added:
                  >
                  >
                  Can try run make all in the scifiusbboard folder using existing Makefile. Note that if some new files are added, need to rerun qmake.
                   
                  Changed:
                  <
                  <

                  System maintenance (experts)

                  For experts only
                  >
                  >

                  System maintenance (for experts only)

                   

                  Replacing USB box

                  Line: 638 to 663
                   
                  Changed:
                  <
                  <

                  Taking LIS scan

                  >
                  >

                  Taking LIS global scan

                    The LIS scan is a procedure to collect data for a specified range of LIS settings. It is not intended to be used for every module, it's just for studying LIS properties.

                  Revision 512019-08-14 - ValeryZhukov

                  Line: 1 to 1
                   
                  META TOPICPARENT name="UpgradeSciFiTracker"

                  SciFi Module Assembly and Quality Assurance tests

                  Line: 25 to 25
                   

                  Info and Links

                  Deleted:
                  <
                  <
                  SciFiModRes Current Status
                    SciFi upgrade twiki
                  Line: 34 to 32
                    SciFi indico
                  Added:
                  >
                  >
                  Summary moduleQA
                   

                  Talks

                  Changed:
                  <
                  <
                  SciFi General:
                  >
                  >
                  SciFi General:
                    03.12.2018 SciFi General M.Dziewiecki
                  Line: 53 to 54
                   25.07.2017 SciFi General Meeting S.Bachmann
                  Changed:
                  <
                  <
                  Working:
                  >
                  >
                  Module Production:
                    * pdf_15052019.zip: Valery15052019
                  Line: 61 to 62
                    * slides_module.pdf: Andreas22072019
                  Added:
                  >
                  >

                  Current Status

                  SciFi Status uptodate

                   

                  Module Assembly

                  The procedure steps can be seen in the :

                  Line: 553 to 560
                   To start, go to FAM directory and type ./update_db. Entering DB credentials might be necessary.
                  Changed:
                  <
                  <

                  System maintenance

                  >
                  >

                  FAQ and Troubleshouting

                  No connection to USB boxes

                  If during access to readout (USB boxes) program crashes (any program) the most likely reason is the LV PS. Check that their are powered on. If yes, disconnect connector and carefully check all voltages, there are fuses inside can be broken.

                  Another reason can be problem with software, eg. related libs are broken. Then one can recompile the program, see below

                  Bad SiPM-SPIROC connections and bad channels

                  These connectors are critical, the used connectors are supposed to sustain ~50 connections. On the SiPM flex side the connectors are used only a few times for BTC testing, while on the SPIROC motherboard side many times, hence can have loose contacts. It is recommended to clean them with isopropanol prior to each connection. Check the alignment of connectors before switching LV ON.

                  There are several problems can be related to bad connections:

                  • One bad, misaligned connector can cause LV problem, or even break PS(fuse). Sometimes one can hear a sound from PS in case of bad load due to bad connection.
                  • Some bad channels seen in the LIS scan with no or little light. Usually these bad channels are spread all other the module in random way. After identification of these bad channels and related connector, try to disconnect, clean and reconnect. If this doesn't help one can use so called connector 'saver' board. In case of persistent problem, one can exchange the SPIROC board. It might happen the problem is on the SiPM flex side, then nothing can be done.
                  • Extra noise in LIS spectra (large width of LIS peaks).

                  LIS tune: not enough light

                  LIS tune is used to find the LIS driver setting that deliver light enough to see 5 p.e. with >1% of events (from total 8000). This corresponds to the average 1.5 p.e. for each driver (512 channels, or one mat). Obviously across the mat the light yield from LIS is not uniform, usually rising toward side where the light fiber is connected to the light bar, however the average is used sofar. This 1.5 p.e. target may not be reached for some mats, especially mat 0 and 2 that have light bar near the fiber mat, which is covered by the black foil. This black foil can reduce the light input for the light bar. The LIS light can be increased by increasing duration of the LIS pulse. The SPIROC readout can provide only Tw=10ns pulse, while the final PACIFIC readout up to 20ns (the relation of LIS LY and Tw is not linear, above 20ns not much gain). Thus during LIS tune two target values are used 1.5 p.e. and 1.1. p.e. that last corresponds to the 15ns pulse, and therefore two LIS settings.

                  The LIS driver is steered by two values in the setting Imodulation

                  Cosmic hodoscope trigger rate

                  PC wifi

                  Recompile software

                  System maintenance (experts)

                    For experts only

                  Replacing USB box

                  Line: 600 to 654
                   Remark: The original modulation values in the config files will be overwritten. Therefore, you should run tune_lis after the scanning procedure or manually recover these settings.
                  Deleted:
                  <
                  <

                  Results

                  SciFi Status uptodate

                    -- ValeryZhukov - 2019-01-28

                  Revision 502019-08-13 - LaraVeldt

                  Line: 1 to 1
                   
                  META TOPICPARENT name="UpgradeSciFiTracker"

                  SciFi Module Assembly and Quality Assurance tests

                  Line: 631 to 631
                   
                  META FILEATTACHMENT attachment="I2C_Address_Translator-Schematics.pdf" attr="" comment="LIS interface documentation (might be outdated)" date="1563275011" name="I2C_Address_Translator-Schematics.pdf" path="I2C_Address_Translator-Schematics.pdf" size="15150" user="mdziewie" version="1"
                  META FILEATTACHMENT attachment="slides_modules.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1563807734" name="slides_modules.pdf" path="slides_modules.pdf" size="18047083" user="ag604848" version="1"
                  META FILEATTACHMENT attachment="Modtest_v4.pdf" attr="" comment="Modtest_v4.pdf" date="1563960982" name="Modtest_v4.pdf" path="Modtest_v4.pdf" size="78057" user="joukov" version="1"
                  Added:
                  >
                  >
                  META FILEATTACHMENT attachment="Overview_Production_Greyroom_13.08.2019.JPG" attr="" comment="Overview Production Greyroom 13.08.2019" date="1565694981" name="Overview_Production_Greyroom_13.08.2019.JPG" path="Overview_Production_Greyroom_13.08.2019.JPG" size="2244802" user="lveldt" version="1"

                  Revision 492019-08-12 - ValeryZhukov

                  Line: 1 to 1
                   
                  META TOPICPARENT name="UpgradeSciFiTracker"

                  SciFi Module Assembly and Quality Assurance tests

                  Line: 72 to 72
                   

                  CERN Cosmic Bench

                  Changed:
                  <
                  <
                  The cosmic bench is used to test SciFi modules in pairs, such that one can select a track and estimate the angle.
                  >
                  >
                  The cosmic bench is used to test SciFi modules in pairs, such that one can select a track and estimate the angle. This data are used for the QA.

                  One can also use only one (usually upper) position, similar to the modtest in the modproduction center for the debugging purpose.

                   

                  Setup

                  Line: 164 to 167
                    ./start This will create folder with FAM[uppermodulId]_FAM[downmoduleId] and put there config.txt,root files and all needed scripts. Go there.
                  Added:
                  >
                  >
                • Enter ELOG ELOG and register the modules to be tested in the System->Module. You need to have an account, and the link should be in the browser. Write all related information about the modules(new, retested, BTC modification,etc) setup(if changed) and all problems during the QA test.
                •  
                • Set Spiroc DACs (offsets to SiPM HV) using Vbreakdown from Db for each SiPM. Power PS for all USB boxes and run ./dac_from_db
                • Perform LighTightness tests (LT) and fill data by running ./check_LT.
                • Line: 598 to 602
                   

                  Results

                  Added:
                  >
                  >
                  SciFi Status uptodate
                   

                  -- ValeryZhukov - 2019-01-28

                  Revision 482019-08-08 - ValeryZhukov

                  Line: 1 to 1
                   
                  META TOPICPARENT name="UpgradeSciFiTracker"

                  SciFi Module Assembly and Quality Assurance tests

                  Line: 118 to 118
                   The installation requires a special versions of Linux and root, so cant be run on standard PC.
                  Changed:
                  <
                  <
                  One can use strosmic90 with one or two modules, eg:

                  strosmic90 halfmodule or strosmic90 module

                  In the GUI one can add prefix to all raw files with uplink data, and summary files. The summary file is saved by taping on save

                  >
                  >
                  One can use strosmic90 with one or two modules, eg: strosmic90 halfmodule or strosmic90 module
                   The modified version is in HD2CERN scifiusbboard/utils/modqacern to run type in the appropriate folder: modqacern module
                  Line: 134 to 128
                   
                  • have some extra histos in the summary
                  • some modifications in LIS gain calculations, etc...
                  Added:
                  >
                  >
                  In the GUI one can add prefix to all raw files with uplink data, and summary files. Type start to start running.
                   After starting the run, it runs 1000 events for the pedestal and then 8000 events for the LIS (takes ~1min) after that the related histograms are appearing and can be inspected. The raw file (root) is created with the prefix+unix time stamp, and the dualtree+time stamp. When run is finished (30min) another two files are created; summary file+time stamp, and the equivalent Summary_last.root file, the last is always containing the last summary. The created Summary files can be inspected by root during the run. The dualtree can be also seen by root, but should be copied first (to avoid locking when programm is running). If you copy dualtree, dont use dualtree name in the copied files because all files with dualtree names are used further on for analysis.
                  Added:
                  >
                  >
                  The summary file is saved by taping on save after stop.
                   
                  One can reprocess raw data by running modqacern  rawfilenames.root In this case program will recognise the format, to save summary, should type save.

                  Revision 472019-08-07 - ValeryZhukov

                  Line: 1 to 1
                   
                  META TOPICPARENT name="UpgradeSciFiTracker"

                  SciFi Module Assembly and Quality Assurance tests

                  Line: 63 to 63
                   

                  Module Assembly

                  Changed:
                  <
                  <
                  The procedure can be seen in the :
                  >
                  >
                  The procedure steps can be seen in the :
                    https://twiki.cern.ch/twiki/pub/LHCb/SciFiFibreModulesQA/Modassembly_v4.pdf: Modassembly_v4.pdf

                  For more information contact Antonio, Lara and Robin

                  Deleted:
                  <
                  <

                  Module Testing in Cosmic Bench

                   
                  Changed:
                  <
                  <
                  The cosmic bench is used to test SciFi modules in pairs, such that one can select a track and estimate the angle.
                  >
                  >

                  CERN Cosmic Bench

                   
                  Added:
                  >
                  >
                  The cosmic bench is used to test SciFi modules in pairs, such that one can select a track and estimate the angle.
                   
                  Changed:
                  <
                  <

                  Setup

                  >
                  >

                  Setup

                    Two main components:
                  Changed:
                  <
                  <
                  1. The movable rack with:
                  >
                  >
                  I. The movable rack with:
                   
                  1. two SPIROC boards got upper and down positions connected to the corresponding boxes by ribbons
                  2. PC(ask for account): lhcbscifi.dyndns.cern.ch
                  Line: 90 to 90
                   
                • HV switch box, with connection to multimeter (for LT test)
                • Changed:
                  <
                  <
                  2. Cosmic bench with holders for two standard (5m) modules
                  >
                  >
                  II. Cosmic bench with holders for two standard (5m) modules
                   and Cosmic hodoscope in between (placed on top of the bottom module):
                    Changed:
                    <
                    <
                  1. plate with 3 scintillators 80x20cm (from AMS01) providing 60x80cm total area, equipped with 2 RS PM each (HVmax=800V) running in coincidence. NIM crate with: HV, amplifiers, discriminators, logics and the counter. The typical cosmic rate is about 140Hz.
                  2. >
                    >
                  3. plate with 3 scintillators 80x20cm (from AMS01) providing 60x80cm total area, equipped with 2 Hamamtsu RS5900 PM each (HVmax=800V) running in coincidence.
                  4. NIM crate with: HV, amplifiers, discriminators, logics and the counter. The typical cosmic rate is about 140Hz.
                  5.  
                    Changed:
                    <
                    <

                    DAQ

                    >
                    >

                    DAQ

                      Based on the USB box and SPIROC motherboard, see attachments for schematics and connections. Be careful with connections, watch the channels and uplink numerations:
                    Line: 108 to 108
                      The ribbon are made such that the 4 cables are connected up and another 4 down (for each box)
                    Changed:
                    <
                    <
                    There HV line is connected to the SPIROC boards via switch box.
                    >
                    >
                    There HV line is connected to the SPIROC boards via sophisticated switch box. It allows to measure HV current precisely for each module.
                     
                    Changed:
                    <
                    <

                    Software and computing

                    >
                    >

                    Software and computing

                      The software is based on scifiusbboard package used for SPIROC readout via USB, https://gitlab.cern.ch/lhcb-scifi/scifiusbboard
                    Added:
                    >
                    >
                    The installation requires a special versions of Linux and root, so cant be run on standard PC.
                     

                    One can use strosmic90 with one or two modules, eg:

                    Line: 133 to 134
                     
                    • have some extra histos in the summary
                    • some modifications in LIS gain calculations, etc...
                    Changed:
                    <
                    <
                    One can reprocess raw data by running modqacern  rawfilenames.root

                    The lhcbscifi PC is connected to cern network via wifi. To connect externally use lhcb-cern@lhcbscifi.dyndns.cern.ch. Outside CERN one have to connect to lxplus first.

                    >
                    >
                    After starting the run, it runs 1000 events for the pedestal and then 8000 events for the LIS (takes ~1min) after that the related histograms are appearing and can be inspected. The raw file (root) is created with the prefix+unix time stamp, and the dualtree+time stamp. When run is finished (30min) another two files are created; summary file+time stamp, and the equivalent Summary_last.root file, the last is always containing the last summary. The created Summary files can be inspected by root during the run. The dualtree can be also seen by root, but should be copied first (to avoid locking when programm is running). If you copy dualtree, dont use dualtree name in the copied files because all files with dualtree names are used further on for analysis.
                    One can reprocess raw data by running modqacern  rawfilenames.root In this case program will recognise the format, to save summary, should type save.
                    The lhcbscifi PC is connected to cern network via wifi. To connect externally use lhcb-cern@lhcbscifi.dyndns.cern.ch. Outside CERN one have to connect to lxplus first.
                     The PC have 3 SSD disks (mounted as raid): main working disk 250 Gb, storage 2Tb and archive disk 14Tb. There software is in the sw and testing in the moduleTest where data contain results from MOD tests i HD and NIKHEF, and SiPM testing used to extarct Vbd, while cern_data is used for the testing in Cosmic Bench.
                    Changed:
                    <
                    <
                    >
                    >

                     The archive data are at larchive (14Tb) and ldata (2Tb).
                    Deleted:
                    <
                    <
                     The larchive has two main folders FAM_old contain modules tested before 17.05.2019 and FAM_new tested after. (Some modules were reassembled and retested with modified ColdBox)
                    Line: 148 to 152
                     The larchive has two main folders FAM_old contain modules tested before 17.05.2019 and FAM_new tested after. (Some modules were reassembled and retested with modified ColdBox)
                    Added:
                    >
                    >
                    The templates for the scripts used for the running and analysis are in scifiusbboard/cern_scripts/
                     
                    Added:
                    >
                    >

                    QA test procedure

                    All operation with hardware:moving modules, connections, etc should be performed only by qualified personals (see contact persons for operations) Most of operations on software are done with the scripts, but operator should know the procedure behind.
                     
                    Changed:
                    <
                    <

                    QA test procedure

                    All operation with hardware:moving modules, connections, etc should be performed only by qualified personal (see contact persons for operations)

                    Most of operations on software are done with the simple scripts, but operator should know the procedure behind. Be careful. Never switch ON SiPM HV WITHOUT LV PS ON!.

                    >
                    >
                    Never switch ON SiPM HV WITHOUT LV PS ON!
                      The standard procedure is following, more detail will follow:
                    Line: 169 to 173
                     
                  6. Perform LighTightness tests (LT) and fill data by running ./check_LT.
                  7. Perform connectivity test using all LIS settings. First copy old cfg by ./copy_cfgfiles then fo to test folder and run modqacern module. Put meanfull prefix, start run, check all, and save summary.
                  8. Changed:
                    <
                    <
                  9. Tune LIS using Ibias from Db to get optimised Imod by running ./tune_lis. This takes about 30min and produce cfg file in sw folder and txt files in lis folder. Copy new cfg files to local folders ./copy_cfgfiles , go to test folder and repeat test run to check LIS settings.
                  10. Run cosmic QA for >= 6 hours. Go to QA folder and run modqacern module setting QA prefix
                  11. >
                    >
                  12. Tune LIS using Ibias from Db to get optimised Imod by running ./tune_lis. This takes about 30min and produce cfg file in sw/ folder and txt files in lis/ folder. Copy new cfg files to local folders ./copy_cfgfiles , go to test/ folder and repeat test run to check LIS settings.
                  13. Run cosmic QA for >= 6 hours. Go to QA/ folder and run modqacern module setting QA prefix
                  14.  
                  15. Post-process data . After QA is finished, run ./sum_QA that creates root files in the sum folder.
                  16. Put data into the database by running ./upload_db
                  17. Changed:
                    <
                    <
                  18. Move FAM*_FAM* folder to archive.
                  19. >
                    >
                  20. Move FAM_FAM folder to the archive in order to save space. Each test usually takes about 40Gb.
                  21.  

                    All steps has to be registered in the checklist https://twiki.cern.ch/twiki/pub/LHCb/SciFiFibreModulesQA/Modtest_v4.pdf: Modtest_v4.pdf

                    Changed:
                    <
                    <

                    Initialising directory structure for measurements

                    >
                    >

                    Initializing directory structure for measurements

                      There's a script for creating a directory structure (and some further helpful scripts) for each new measurement session (one side of a module pair).
                      Line: 188 to 192
                       
                    1. Type ./start
                    2. Answer all questions given by the script
                    3. If there are problems with accessing database, probably you're not logged in. Break the script and type ./dblogin
                    4. Added:
                      >
                      >
                      If this not working, problem with Db access. One can still work offline(i.e answering no on Db access during the scripts), but is not recommended. However it might be needed if entries in Db are not correct (eg. wrong BTC, or Ibias in LIS, etc).
                       
                      Deleted:
                      <
                      <
                      Currently, the following directories/files are created:
                       
                      Changed:
                      <
                      <
                      Directories:
                      >
                      >
                      Following folders are created:
                       
                        Deleted:
                        <
                        <
                      • .../config.txt - a summary file with entered module data
                      • .../config.root - the same as root tree
                      •  
                      • .../vbd/ - a directory for all breakdown-related stuff
                      • Changed:
                        <
                        <
                        • .../vbd/mod_up/
                        • .../vbd/mod_dn/
                        >
                        >
                        .../vbd/mod_up/ for upper module
                        .../vbd/mod_dn/ for down module

                         
                      • .../lis/ - a directory for LIS tuning results
                      • .../QA/ - a directory for cosmic data and results
                      • Changed:
                        <
                        <
                      • .../test/ - a directory for debug cosmic runs
                      • .../sum/ - a directory for cosmic data analysis
                      • >
                        >
                      • .../test/ - a directory for connectivity and other test cosmic runs
                      • .../sum/ - a directory for cosmic data analysis
                      •  
                        Changed:
                        <
                        <
                        Scripts:
                        >
                        >
                        Created Config files:
                        config.txt is a config file with entered module data, including obtained from Db, and .config.root the same, but as root file used for other scripts.

                        Scripts:

                         
                          Changed:
                          <
                          <
                        • .../tune_lis - a convenience script for running LIS tuning procedure
                        • .../tune_lis_advanced - the same, but allowing for modifying of bias currents. Use with care
                        • .../dacfiles_from_db - copy DAC files from local database to working directory
                        • .../dac_from_db - run dacfiles_from_db and then set Spiroc DACs
                        • .../copy_cfgfiles - copy module config files from USBBOARDPATH to QA and test directories
                        • .../run_QA - run modqacern from QA directory (must copy_cfgfiles first!)
                        • .../test_QA - run modqacern from test directory (must copy_cfgfiles first!)
                        • .../sum_QA - post-process QA data
                        • .../check_LT - query light tightness result and write them to a file
                        • .../db_login - a helper for logging into the production database (produces Michal's name on output as a side effect)
                        • .../update_db - upload all possible data into the production database
                        • .../copy_results - copy most important files to the data/FAM directory
                        • .../restart - re-create directory structure, config files and/or local scripts
                        • >
                          >
                        • tune_lis - a script for running LIS tuning procedure
                        • tune_lis_advanced - the same, but allowing for modifying of bias currents. For experts.
                        • dacfiles_from_db - copy DAC files from local database to working directory. For experts.
                        • dac_from_db - run dacfiles_from_db and then set Spiroc DACs
                        • copy_cfgfiles - copy module config files from USBBOARDPATH to QA and test directories
                        • run_QA - run modqacern from QA directory
                        • test_QA - run modqacern from test directory. For experts.
                        • sum_QA - post-process QA data
                        • check_LT - query light tightness result and write them to a file
                        • db_login - a helper for logging into the production database (produces Michal's name on output as a side effect)
                        • update_db - upload all possible data into the production database.
                        • copy_results - copy most important files to the data/FAM directory. For experts.
                        • restart - re-create directory structure, config files and/or local scripts. For experts.
                        •  
                          Changed:
                          <
                          <
                          Attention: backup script
                          Important: In most cases, running some scripts twice would delete old data. To avoid it, a backup script can be used.
                          >
                          >
                          <!--/twistyPlugin twikiMakeVisibleInline-->

                          Attention: backup script is a part of run scripts. In most cases, running some scripts twice would delete old data. To avoid it, a backup script can be used.

                           To backup a dir, simply go into it and type backup_me. This will create a new folder with a general name of BACKUP_yyyymmdd_hhmmss and copy or move all files there. The script is interactive and will ask for a short comment (then saved to a backup_info file) and whether to delete old data. It can be used anywhere (even outside the created directory structure).
                          Deleted:
                          <
                          <
                          Further comments on the script:
                           
                          #The name of this subdirectory is always BACKUP_yyyymmdd_hhmmss.
                          #Additionally, a text file in this directory (backup_info) will be created with a user-given information.
                          
                          
                          Line: 246 to 257
                           

                          <!-- The QA and test directories contain a backup_blind file, which disables making backups if only USBBoard config files are there. -->
                          Added:
                          >
                          >
                          <!--/twistyPlugin-->
                           
                          Changed:
                          <
                          <

                          Downloading Vdb info and setting Spiroc DACs

                          >
                          >

                          Installation

                           
                          Changed:
                          <
                          <
                          Automated procedure: (use it!)
                          >
                          >
                          INITIAL STATE:both USB-Box LV PS OFF, HV PS OFF

                          1. Disconnect tested modules; LIS and SPIROC using a grabbing tool. Position the SPIROC boards on the rack safely.
                          2. Remove previous modules from the bench. Move hodoscope beneath the modules on the shell, carefully (with HV on)
                          3. if needed move the rack to the side for tests. For this disconnect power (without switching off PC) and ground pin. Keep the trigger cables connected(going to hodoscope) and carefully move the rack, holding the SPIROC boards.
                          4. Install a new module on down position, ensure module position and flatness. Put hodoscope in between to the right place (close to the center)
                          5. Ground yourself using braclet, touching the metallic parts.
                          6. Mount SPIROC readout boards to the module using two M8 screws (for upper and down modules)
                          7. Connect SiPM flexes. Handle them with care. Ensure that all connectors are fully pushed in.
                          8. Connect LIS flex cables.
                          9. Switch ON both LV PS then HV PS (58.0V) only after LV is ON. Check total current (should be ~0.012A, but higher during ramping)
                          10. Switch HV OFF

                          Fill the check list for both modules.

                          Downloading Vdb info and setting Spiroc DACs

                          INITIAL STATE:both USB-Box LV PS OFF, HV PS OFF

                          Note that this procedure is needed once at the begining of all tests with new SiPM (re)connected to the SPIROC.

                          Automated procedure:

                           
                            Changed:
                            <
                            <
                          1. Ensure that HV is off, both LV on
                          2. Run ./dac_from_db
                          3. >
                            >
                          4. Ensure that HV is OFF, then set both LV PS ON
                          5. Run ./dac_from_db It takes a few minutes, check for errors on the screen.
                          6.  
                            Changed:
                            <
                            <
                            Manual procedure: (only in troubles)
                            >
                            >
                            Manual procedure: (if needed):
                             
                              Changed:
                              <
                              <
                            1. Copy DAC files: type ./dacfiles_from_db
                              Currently, programing DAC must be done manually:
                            2. Ensure that HV is off, both LV on
                            3. Switch upper PS on, lower PS off
                            4. Type setSpirocDac $USBBOARDPATH/cfgFiles ./vbd/mod_up/dacfile_from_db.txt to program Spiroc chips for upper system
                            5. Switch upper PS off, lower PS on
                            6. Type setSpirocDac $USBBOARDPATH/cfgFiles ./vbd/mod_dn/dacfile_from_db.txt to program Spiroc chips for lower system
                            7. Switch both PS back on
                            8. >
                              >
                            9. Copy DAC files: type ./dacfiles_from_db Currently the files are manually downloaded from Db and stored in moduleTest/data/sipm. If the corresponding BTC doesnt exist, you are in trouble.
                            10. Ensure that HV is OFF
                            11. Switch upper PS ON while , lower PS OFF
                            12. Type setSpirocDac $USBBOARDPATH/cfgFiles ./vbd/mod_up/dacfile_from_db.txt to program SPIROC chips for upper system
                            13. Switch lower PS ON, while upper PS is OFF.
                            14. Type setSpirocDac $USBBOARDPATH/cfgFiles ./vbd/mod_dn/dacfile_from_db.txt to program SPIROC chips for lower system
                            15. Switch both PS OFF
                            16.  
                              Added:
                              >
                              >
                              Fill the check list.
                               
                              Changed:
                              <
                              <

                              Installation and connectivity test

                              >
                              >

                              Connectivity test

                              INITIAL STATE:both USB-Box LV PS OFF, HV PS OFF

                               
                                Changed:
                                <
                                <
                              1. Ensure that both LV and HV power supplies are off!
                              2. Remove previous modules from the bench. Move hodoscope beneath the modules on the shell, carefully (with HV on)
                              3. Install a new module on down position, ensure module position and flatness.
                              4. Ground yourself!
                              5. Mount spiroc readout to the module usng two M8 screws
                              6. Connect SiPM flexes. Handle them with care. Ensure that all connectors are fully pushed in.
                              7. Connect LIS flex cables.
                              8. Install hodoscope on top, close to the centre of the module
                              9. Repeat points 3-6 for upper module
                              10. Switch on both LV PS and HV PS (58.0V)
                              11. run copy_cfgfiles and then test_QA script and collect some data to ensure that the system seems to work properly
                              12. >
                                >
                              13. Check tumbler positions on the switch box (bypass is UP, others are full DOWN). Check positions of tumblers on SPIROC boards (all DOWN, by default)
                              14. Switch LV PS ON.
                              15. Switch HV ON (58V)
                              16. Use ./copy_cfgfiles script to copy board36.cfg and board37.cfg to working folders (QA/ and test/).
                              17. Go to test/ folder and run modqacern module Set the prefix for stored files, eg. firsttest, afterlistune, etc.... and start the run. After LIS run, and first cosmics check the histos and save summary. Check the summary file is stored.
                              18. close the GUI
                              19. HV is OFF
                              20.  
                                Added:
                                >
                                >
                                Fill the check list.

                                Light Tightness Test

                                INITIAL STATE:both USB-Box LV PS ON, HV PS OFF

                                 
                                Deleted:
                                <
                                <

                                Light Tightness Tests

                                INITIAL STATE: both USB-Box PS ON, HV PS OFF
                                Use check_LT script for saving data on the PC!
                                 
                                1. Connect multimeter (uA input) to banana cables from HV distribution box.
                                Changed:
                                <
                                <
                              21. Distribution box: all switches DOWN
                              22. Spiroc cards: all switches DOWN
                              23. Power Spiroc (LV on)
                              24. Start a run with test_QA script to initialize Spiroc chips. Run may be stopped after LIS phase. This step is not needed, if the LV for both modules was not switched off since connectivity test
                                CHECKING TOP MODULE:
                              25. Distribution box: Ch1 DOWN, Ch2 in CENTRAL position
                              26. Switch on HV PS, V=58.0V
                              27. Wait until readout stabilises, then write down current from multimeter
                              28. >
                                >
                              29. Switch box: all switches DOWN, i.e bypass and both channels.
                              30. SPIROC boards: all switches DOWN (should be by default)
                              31. both LV PS are ON
                              32. Start a run with test_QA script to initialise SPIROC chips. Run may be stopped after LIS phase (this step is not needed, if the LV for both modules was not switched off since connectivity test)

                                TOP module:

                                1. Switch box: Ch1 DOWN, Ch2 in CENTRAL position
                                2. LV is ON, Switch on HV PS (58.0V)
                                3. Wait until readout stabilises ~5min, then write currents from multimeter
                              33.  
                              34. Switch multimeter to relative mode
                              35. Changed:
                                <
                                <
                              36. Switch on bright lamp, 'scan' coldbox and connections to the module, write down highest current
                              37. >
                                >
                              38. Switch on bright lamp and illuminate different parts of coldbox and connections to the module, write down highest current
                              39.   < 5 uA: OK
                                5-15 uA: Not critical, but try to locate the leak and leave a comment
                                > 15uA: locate and repair the leak, leave a comment
                                Changed:
                                <
                                <
                              40. Switch off lamp, switch off HV, meter back from relative to normal mode
                                CHECKING BOTTOM MODULE:
                              41. Distribution box: Ch1 in CENTRAL position, Ch2 DOWN
                              42. Repeat 6-11
                                SWITCH BACK:
                              43. ENSURE THAT HV IS OFF!
                              44. Distribution box: all switches UP
                              45. Spiroc cards: all switches UP
                              46. >
                                >
                              47. Switch lamp OFF
                              48. Switch HV OFF
                              49.  
                                Deleted:
                                <
                                <
                                Ready for cosmic tests
                                 
                                Changed:
                                <
                                <

                                LIS tuning

                                >
                                >
                                BOTTOM module:
                                1. Switch box: Ch2 DOWN, Ch1 in CENTRAL position,
                                2. LV is ON, Switch on HV PS (58.0V)
                                3. Wait until readout stabilises ~5min, then write currents from multimeter
                                4. Switch multimeter to relative mode
                                5. Switch on bright lamp and illuminate different parts of coldbox and connections to the module, write down highest current
                                6. Switch lamp OFF
                                7. Switch HV OFF
                                8. Distribution box: set bypass UP, set both channel all DOWN.

                                Use check_LT script for saving data on the PC. Fill the checklist.

                                LIS tuning

                                INITIAL STATE: both USB-Box PS OFF, HV PS OFF

                                 
                                Deleted:
                                <
                                <
                                INITIAL STATE: both USB-Box PS ON, HV PS ON, V=58V. Vbd must be calibrated and deltaV=3.5V.
                                 
                                  Added:
                                  >
                                  >
                                1. Switch both LV ON, then HV ON (V=58V)
                                2.  
                                3. Open terminal, go to right moduleTest/cern_data/FAMxxxxxxX_FAMxxxxxxX directory
                                4. Type =./tune_lis=
                                  The configuration will be fetched from a root file generated by initialisation script. You don't need to enter it again.
                                5. Changed:
                                  <
                                  <
                                  Use tune_lis_advanced if there's a need to modify bias currents. This is really an advanced option, so don't use it without understanding.
                                  >
                                  >
                                  Use tune_lis_advanced if there's a need to modify bias currents. This is an advanced option, so don't use it without understanding.
                                   
                                6. It takes about 30min to calibrate both modules
                                7. Changed:
                                  <
                                  <
                                8. Text files with report will be generated at the end (module_name.lis.txt) and put into lis subdirectory.
                                9. >
                                  >
                                10. Text files with report will be generated at the end (module_name.lis.txt) and put into lis subdirectory. Check the files and fill the check list.
                                11.  
                                12. Config files will be configured for the last tuned setting and stored in the $USBBOARDPATH/cfgFiles.
                                13. Changed:
                                  <
                                  <

                                  HV scan (Vbd optimization) - optional

                                  >
                                  >

                                  QA cosmic test

                                   
                                  Changed:
                                  <
                                  <
                                  Currently, this step can be performed only manually. However, it shouldn't be performed at all;)
                                  >
                                  >
                                  INITIAL STATE: both USB-Box PS OFF, HV PS OFF
                                   
                                  Changed:
                                  <
                                  <

                                  Cosmics

                                  Use copy_cfgfiles script to copy board36.cfg and board37.cfg to working folders (QA and test).

                                  Use run_QA script for starting DAQ software.

                                  setup the prefix for saved root files and click start. Use QA prefix for regular runs.

                                  Each run consists of 3 parts: Pedestal 1000triggers LIS run 8000triggers Cosmic 30min

                                  >
                                  >
                                  1. Use copy_cfgfiles script to copy board36.cfg and board37.cfg to working folders (QA and test).
                                  2. LV is ON, then HV is ON (58V)
                                  3. Use run_QA script for starting DAQ software, it will start modqacern module in the QA/ folder. Set the prefix for saved root files and click start, use QA prefix for final runs used in analysis.
                                  4. run for >6 hours, which corresponds to more than 1000000 selected tracks (in dualtree)

                                    <!--/twistyPlugin twikiMakeVisibleInline-->
                                    Each run consists of 3 parts:
                                    Pedestal 1000triggers
                                    LIS run 8000triggers
                                    Cosmic 30min
                                    During the run 3 trees are filled in the corresponding root file with the name prefix_unixtime_data_time.root
                                    Also the selected dualtree tree for events with only 1 hit in one module is stored in the dualtree_unixtime.root file.
                                    New run is started automatically each 30min, the running can be stopped by clicking stop. Then slick save to save the Summary file.
                                    <!--/twistyPlugin-->
                                   
                                  Changed:
                                  <
                                  <
                                  During the run 3 trees are filled in the corresponding root file with the name prefix_unixtime_data_time.root Also the selected tree for events with only 1 hit in one module is stored in the dualtree_unixtime.root file.
                                  >
                                  >
                                14. stop the run, save, check that output files in the QA/ folders are OK (latest dualtree and Summary)
                                15. close the GUI, switch HV OFF, and then LV OFF. <\ol>
                                16.   Then new run is started automatically. The running can be stopped by clicking stop. Then slick save to save the Summary file.
                                  Changed:
                                  <
                                  <

                                  Data post-processing

                                  >
                                  >

                                  Data post-processing

                                   
                                  Changed:
                                  <
                                  <
                                  To post-process the data collected in the QA run, simply type ./sum_QA from the FAM directory.
                                  >
                                  >
                                  To post-process the data collected in the QA run, simply type ./sum_QA from the FAM_FAM folder.
                                   Attention: post-processing might take a significant amount of time (> few s).
                                  Added:
                                  >
                                  >
                                   The following files will be generated in the .../sum_QA directory:
                                    Added:
                                    >
                                    >
                                  • sum_FAMxxxxx_X.root (x2) - the main output file with data, for each module
                                  • sum_FAM_xxxxx_X.pdf (x2) - a pdf summary of the above
                                  •  
                                  • BTCxxxxx_Vbd.root (x2) - a file with breakdown voltages copied from data/BTC
                                  • mod_FSMxxxxx_X.root (x2) - a file with HD/Nikhef QA data for a module, copied from data/FSM
                                  • dual_FAMxxxxx_X.root (x2) - an intermediate file with Cern cosmic data processed
                                  • modcb_FAMxxxxx_X.root (x2) - another file of this kind
                                  • Deleted:
                                    <
                                    <
                                  • sum_FAMxxxxx_X.root (x2) - the main output file with data
                                  • sum_FAM_xxxxx_X.root (x2) - a pdf summary of the above
                                  •  
                                  • sumbadch_FAM_xxxxx_X.txt - a text file with a summary of bad channels
                                  • sumgaps_FAM_xxxxx_X.txt - a text file with a summary of mat-SiPM gap calculation
                                  • Added:
                                    >
                                    >
                                    The summary root files after processing contains results from the current tests(modcb), as well as from FSM test in module production centers(mod), and SIPM testing.:
                                    <!--/twistyPlugin twikiMakeVisibleInline-->
                                     TH2D   h2mod_LIS;1   
                                     TH1D   h1mod_LIS_gain;1   
                                     TH1D   h1mod_LIS_pe;1   h1mod_LIS_pe
                                     TH1D   h1mod_Cosm_prof;1   12826435 entries / 2048 channels = 6262 entries per channel
                                     TH1D   h1mod_Cosm_sig;1   2048 entries / 2048 channels = 1 entries per channel
                                     TH1D   h1mod_Cosm_sigcl;1   2048 entries / 2048 channels = 1 entries per channel
                                     TH1D   h1mod_LISbad;1   
                                     TH1D   h1mod_Cosmsbad;1   2048 entries / 2048 channels = 1 entries per channel
                                     TH1D   h1mod_Cosmpbad;1   12826435 entries / 2048 channels = 6262 entries per channel
                                     TH1D   h1mod_allbad;1   
                                     TH1D   h1mod_mask;1   
                                     TH2D   h2modcb_LIS;1   
                                     TH2D   h2modcb_LIS_S;1   LIS Scurve
                                     TH1D   h1modcb_LIS_gain;1   
                                     TH1D   h1modcb_LIS_pe;1   h1modcb_LIS_pe
                                     TH1D   h1modcb_LIS_rms;1   LISrms
                                     TH1D   h1modcb_LIS_p0;1   LIS5pe
                                     TH1D   h1modcb_LIS_p5;1   LIS0pe
                                     TH1D   h1modcb_LIS_p0fr;1   hs5pe
                                     TH1D   h1modcb_LIS_p5fr;1   hs0pe
                                     TH1D   h1modcb_Ped_noise;1   proj
                                     TH1D   h1modcb_Cosm_prof;1   11968521 entries / 2048 channels = 5844 entries per channel
                                     TH1D   h1modcb_Cosm_sig;1   2048 entries / 2048 channels = 1 entries per channel
                                     TH1D   h1modcb_Cosm_sigcl;1   2048 entries / 2048 channels = 1 entries per channel
                                     TH1D   h1modcb_Cosm_dnoise;1   Noise Down
                                     TH1D   h1modcb_Cosm_deff;1   Eff Down
                                     TH1D   h1modcbdual_prof;1   h1d_posa
                                     TH1D   h1modcbdual_sig;1   h1d_siga
                                     TH1D   h1modcbdual_sigcl;1   h1d_sigcla
                                     TH1D   h1modcbdual_cls;1   h1d_clsa
                                     TGraphErrors   gmodcbdual_cls0;1   
                                     TGraphErrors   gmodcbdual_sig;1   
                                     TGraphErrors   gmodcbdual_sigcl;1   
                                     TH1D   h1modcb_Pedbad;1   proj
                                     TH1D   h1modcb_Cosmnbad;1   Noise Down
                                     TH1D   h1modcb_Cosmsbad;1   h1d_sigcla
                                     TH1D   h1modcb_Cosmsbadfr;1   h1d_sigcla
                                     TH1D   h1modcb_Cosmpbad;1   h1d_posa
                                     TH1D   h1modcb_LISbad;1   
                                     TH1D   h1modcb_allbad;1   
                                     TH1D   h1modcb_noisebad;1   proj
                                     TH1D   h1modcbdual_rsigcls0;1   hsig
                                     TH2D   h2modcbdual_sig2cls0;1   h2modcb_sig2cls0
                                     TH1D   h1modcb_matbad;1   
                                     TH1D   h1modcb_sipmbad;1   
                                     TH1F   h1modcb_Vbd;1   Vbd_from_DB
                                     TH1D   h1modcb_lt;1   h1modcb_lt
                                     TH1D   h1modcb_pos;1   h1modcb_pos
                                     TH1D   LIS_mat_mapping;1   LIS mat mapping
                                     TH1D   LIS_bias_currents;1   LIS bias currents
                                     TH1D   LIS_mod_currents_ly_15_tp_100;1   LIS mod currents: ly=1.5p.e. tp=10.0ns
                                     TH1F   LIS_measured_LY_ly_15_tp_100;1   LIS measured LY: ly=1.5p.e. tp=10.0ns
                                     TH1D   LIS_mod_currents_ly_11_tp_100;1   LIS mod currents: ly=1.1p.e. tp=10.0ns
                                     TH1F   LIS_measured_LY_ly_11_tp_100;1   LIS measured LY: ly=1.1p.e. tp=10.0ns
                                    
                                    
                                    <!--/twistyPlugin-->

                                    The analysis procedure is following.
                                    * some results from former tests in modproduction centers are copied from moduleTest/data/FSM. as mod_FSMxxx.root. The FSM files are already preprocessed.to get correct channelo rdering The corresponding histos habe mod prefix. * the SiPM Vbd are copied from moduleTest/data/sipm/ taking into account correct ordering ad BTC_XXX.root. * the latest summary files in the QA/ folder is taken as link Summary.root and after processing is stored as modc_FAMxxx.root. * all dualtreexxx.root files are merged to a dualtree.root file and the dualtree.root is analysed for the vertical tracks and results are stored for each module in dual_FAMxxx.root * all stored root files are analysed together and final results are stored into sumFAMxxx.root files for each module, as well as pdf (with some selected plots) and txt files with lists.

                                     

                                    Archiving results locally

                                    Added:
                                    >
                                    >
                                    After the tests the whole directory has to copied into moduleTests/cern_data/larchive. From 17.05.2019 all data are stored in FAM_new folder. There are a few scripts:
                                    • process_sum_all - reprocess all data with sum_QA scripts
                                    • collect_sumroot - collect all sum_FAMxxx.root into sumroot/ folder
                                    • collect_pdf -collect pdf files from sum/ folders into pdf/
                                    • collect_lis - same for lis information, into lis/ folder
                                    • collect_sum -collect all sum/ folders into sum/FAM/
                                    • collect-QAsummary -collect all Summary.root files into fam/FAMxxx/ folders
                                     To make a local copy in data/FAM/, type ./copy_results.
                                    Changed:
                                    <
                                    <
                                    See the example code below to see which files are copied:
                                    >
                                    >
                                    See the example code below to see which files are copied
                                    <!--/twistyPlugin twikiMakeVisibleInline-->
                                     
                                    		mkdir -p $DATAPATH/FAM/FAM00019 
                                     		mkdir $DATAPATH/FAM/FAM00019/sideA 
                                    
                                    
                                    Line: 392 to 543
                                      mkdir $DATAPATH/FAM/FAM00019/sideA/LT cp ./LT/lt.txt $DATAPATH/FAM/FAM00019/sideA/LT/
                                    Added:
                                    >
                                    >
                                    <!--/twistyPlugin-->
                                     
                                    Changed:
                                    <
                                    <

                                    Putting results into production database

                                    >
                                    >

                                    Putting results into the production database

                                     
                                    Changed:
                                    <
                                    <
                                    Remark: Putting data into database is a SEMI-automated process and needs an active supervision of the operator.
                                    >
                                    >
                                    Attention: Putting data into database is a SEMI-automated process and needs an active supervision of the operator.
                                     Depending on the current state of the database and results, some data may remain not uploaded. One of these cases is when some relevant data already exists in the database.

                                    To start, go to FAM directory and type ./update_db. Entering DB credentials might be necessary.

                                    Deleted:
                                    <
                                    <
                                    Please read carefully every line of script's output and follow ALL weblinks. Even if annoying, it's still way better than putting all the data manually!
                                     
                                    Changed:
                                    <
                                    <

                                    System maintenance / Advanced

                                    >
                                    >

                                    System maintenance

                                    For experts only
                                     
                                    Changed:
                                    <
                                    <

                                    Replacing USB box

                                    >
                                    >

                                    Replacing USB box

                                      In order to replace one of existing USB boxes (36 or 37) with a spare one (22), do the following:
                                      Line: 417 to 568
                                        If you have a spare with different USB ID, the procedure is the same; just replace 22 with your USB ID.
                                      Changed:
                                      <
                                      <

                                      Adjusting LV PS voltages

                                      Attention! This is a VERY advanced procedure!
                                      >
                                      >

                                      Adjusting LV PS voltages

                                        The +/-2V outputs of Spiroc setup PSes are adjustable. It has been checked that their adjustment has significant effect on the readout noise.
                                      Line: 434 to 584
                                       
                                      Changed:
                                      <
                                      <

                                      Taking LIS scan

                                      >
                                      >

                                      Taking LIS scan

                                        The LIS scan is a procedure to collect data for a specified range of LIS settings. It is not intended to be used for every module, it's just for studying LIS properties.
                                      Line: 447 to 597
                                       
                                    1. You get a number of files: lis_raw_??.root (with raw histograms) and lisAnalysis_??.root (with calculated pedestals, gains and LYs), where ?? is a decimal number with current modulation setting for all LIS channels. Bias settings are taken from config.root or from manual input if you don't specify the file.
                                    2. Changed:
                                      <
                                      <
                                      Remark: The original modulation values in the config files will be overwritten. Therefore, you should run tune_lis after the scanning procedure or manually recover these settings.
                                      >
                                      >
                                      Remark: The original modulation values in the config files will be overwritten. Therefore, you should run tune_lis after the scanning procedure or manually recover these settings.
                                       
                                      Changed:
                                      <
                                      <

                                      Results

                                      >
                                      >

                                      Results

                                       

                                      Revision 462019-08-07 - ValeryZhukov

                                      Line: 1 to 1
                                       
                                      META TOPICPARENT name="UpgradeSciFiTracker"

                                      SciFi Module Assembly and Quality Assurance tests

                                      Line: 6 to 6
                                       

                                      Access and Contacts

                                      Grey Room in LHCB Hall
                                      Changed:
                                      <
                                      <
                                      ask for key's LHCb secretariat.
                                      >
                                      >
                                      (ask for key's LHCb secretariat)
                                        Contact persons for operation:

                                      Valery Zhukov joukov@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 78188 Cell(CERN): +41 76 487 6537
                                      Andreas Guth andreas.guth@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 75750 Cell(CERN):
                                      Michal Dziewiecki mdziewie@cernNOSPAMPLEASE.ch Office: Cell(CERN): +48 791 221 186
                                      Added:
                                      >
                                      >
                                      Sebastian Bachmann bachmann@uphysiNOSPAMPLEASE.uni-heidelberg.de Office: Cell(CERN): +48 791 221 186

                                      Assembly:

                                      Antonio Pelligrino antonio@nikhefNOSPAMPLEASE.nl
                                      Lara Veldt lveldt@nikhefNOSPAMPLEASE.nl
                                      Robin Schmeitz robins@nikefNOSPAMPLEASE.nl
                                       

                                      Info and Links

                                      Changed:
                                      <
                                      <
                                      SciFiModRes
                                      >
                                      >
                                      SciFiModRes Current Status
                                       
                                      Changed:
                                      <
                                      <
                                      [https://twiki.cern.ch/twiki/bin/viewauth/LHCb/UpgradeSciFiTracker][SciFi upgrade]]
                                      >
                                      >
                                      SciFi upgrade twiki
                                        Elog SciFi:Module
                                      Line: 28 to 36
                                       

                                      Talks

                                      Added:
                                      >
                                      >
                                      SciFiGeneral:
                                        03.12.2018 SciFi General M.Dziewiecki
                                      Line: 44 to 53
                                       25.07.2017 SciFi General Meeting S.Bachmann
                                      Changed:
                                      <
                                      <

                                      Module Assembly

                                      >
                                      >
                                      Working:

                                      * pdf_15052019.zip: Valery15052019

                                      * bads07072019.pdf: Valery08072019

                                      * slides_module.pdf: Andreas22072019

                                      Module Assembly

                                      The procedure can be seen in the :

                                      https://twiki.cern.ch/twiki/pub/LHCb/SciFiFibreModulesQA/Modassembly_v4.pdf: Modassembly_v4.pdf

                                      For more information contact Antonio, Lara and Robin

                                      Module Testing in Cosmic Bench

                                       
                                      Added:
                                      >
                                      >
                                      The cosmic bench is used to test SciFi modules in pairs, such that one can select a track and estimate the angle.
                                       
                                      Changed:
                                      <
                                      <

                                      Module Testing in Cosmic Bench

                                      >
                                      >

                                      Setup

                                       
                                      Changed:
                                      <
                                      <
                                      --+++++ Setup Three main components:
                                      >
                                      >
                                      Two main components:
                                       
                                      Changed:
                                      <
                                      <
                                      The rack with:
                                      >
                                      >
                                      1. The movable rack with:
                                       
                                        Added:
                                        >
                                        >
                                      1. two SPIROC boards got upper and down positions connected to the corresponding boxes by ribbons
                                      2.  
                                      3. PC(ask for account): lhcbscifi.dyndns.cern.ch
                                      4. two USB boxes:
                                      5. Changed:
                                        <
                                        <
                                        Up: board37 uplinks:10,11,12,13,14,15,16,17

                                        Down: board36 uplinks: 20,21,22,23,24,25,26,27

                                      6. two corresponding PC
                                      7. HV Kethley PS
                                      8. >
                                        >
                                        Up: board37 uplinks:10,11,12,13,14,15,16,17 and Down: board36 uplinks: 20,21,22,23,24,25,26,27
                                      9. two corresponding LV power supply (PS)
                                      10. HV Keithley PS
                                      11.  
                                      12. HV switch box, with connection to multimeter (for LT test)
                                      13. Deleted:
                                        <
                                        <
                                      14. two SPIROC boards got upper and down positions connected to the corresponding boxes by ribbons
                                      15.  
                                        Changed:
                                        <
                                        <
                                        Cosmic bench with holders for two standard (5m) modules

                                        Cosmic hodoscope:

                                        >
                                        >
                                        2. Cosmic bench with holders for two standard (5m) modules and Cosmic hodoscope in between (placed on top of the bottom module):
                                         
                                          Changed:
                                          <
                                          <
                                        1. PC PC(ask for pass): lhcb-cern /lhcbscifi.dyndns.cern.ch
                                        2. >
                                          >
                                        3. plate with 3 scintillators 80x20cm (from AMS01) providing 60x80cm total area, equipped with 2 RS PM each (HVmax=800V) running in coincidence. NIM crate with: HV, amplifiers, discriminators, logics and the counter. The typical cosmic rate is about 140Hz.
                                        4.  
                                          Added:
                                          >
                                          >

                                          DAQ

                                          Based on the USB box and SPIROC motherboard, see attachments for schematics and connections. Be careful with connections, watch the channels and uplink numerations:

                                          * the module SiPM channels: 0 from the right (look from readout side) * the LIS channel: 0 is the right, 1 left * uplink ribbon cables, uplink 10(20) is the right (look on the USB box connectors) The ribbon are made such that the 4 cables are connected up and another 4 down (for each box)

                                          There HV line is connected to the SPIROC boards via switch box.

                                          Software and computing

                                          The software is based on scifiusbboard package used for SPIROC readout via USB, https://gitlab.cern.ch/lhcb-scifi/scifiusbboard

                                           
                                          Added:
                                          >
                                          >
                                          One can use strosmic90 with one or two modules, eg:
                                           
                                          Changed:
                                          <
                                          <
                                          SPIROC DAQ
                                          >
                                          >
                                          strosmic90 halfmodule or strosmic90 module
                                           
                                          Changed:
                                          <
                                          <
                                          Software
                                          >
                                          >
                                          In the GUI one can add prefix to all raw files with uplink data, and summary files. The summary file is saved by taping on save
                                           
                                          Changed:
                                          <
                                          <
                                          scifiusbboard/modqacern
                                          >
                                          >
                                          The modified version is in HD2CERN scifiusbboard/utils/modqacern to run type in the appropriate folder: modqacern module
                                           
                                          Added:
                                          >
                                          >
                                          It include several features:
                                          • write a tree with events where we have exactly one hit in the upper and down modules
                                          • write a summary files after each run (30min by default)
                                          • have some extra histos in the summary
                                          • some modifications in LIS gain calculations, etc...
                                           
                                          Changed:
                                          <
                                          <
                                          Cosmic hodoscope
                                          >
                                          >
                                          One can reprocess raw data by running modqacern  rawfilenames.root
                                           
                                          Deleted:
                                          <
                                          <
                                          Based on AMS scintillators runiing with hamamatsu flat PM (HVmax=800V)
                                           
                                          Added:
                                          >
                                          >
                                          The lhcbscifi PC is connected to cern network via wifi. To connect externally use lhcb-cern@lhcbscifi.dyndns.cern.ch. Outside CERN one have to connect to lxplus first.
                                           
                                          Added:
                                          >
                                          >
                                          The PC have 3 SSD disks (mounted as raid): main working disk 250 Gb, storage 2Tb and archive disk 14Tb. There software is in the sw and testing in the moduleTest where data contain results from MOD tests i HD and NIKHEF, and SiPM testing used to extarct Vbd, while cern_data is used for the testing in Cosmic Bench.
                                           
                                          Changed:
                                          <
                                          <

                                          QA testing procedure in the CERN cosmic bench

                                          >
                                          >
                                          The archive data are at larchive (14Tb) and ldata (2Tb).

                                          The larchive has two main folders FAM_old contain modules tested before 17.05.2019 and FAM_new tested after. (Some modules were reassembled and retested with modified ColdBox)

                                          QA test procedure

                                           All operation with hardware:moving modules, connections, etc should be performed only by qualified personal (see contact persons for operations)

                                          Most of operations on software are done with the simple scripts, but operator should know the procedure behind.

                                          Added:
                                          >
                                          >
                                          Be careful. Never switch ON SiPM HV WITHOUT LV PS ON!.
                                           
                                          Changed:
                                          <
                                          <
                                          The standard procedure is following:
                                          >
                                          >
                                          The standard procedure is following, more detail will follow:
                                           
                                            Changed:
                                            <
                                            <
                                          1. Install two modules on the upper and down cosmic bench positions, and cosmic hodoscope in between
                                          2. >
                                            >
                                          3. Install two modules on the upper and down cosmic bench positions, and cosmic hodoscope in between.
                                          4.  
                                          5. Initialize directory structure, by running scripts, ensure that all information is correctlybdownloaded from Db
                                          6. Changed:
                                            <
                                            <
                                          7. Set Spiroc DACs (offsets to SiPM HV) using Vbreakdown from Db for each SiPM, by
                                          8. Perform LighTightness tests (LT)
                                          9. Perform connectivity test using all LIS seetings
                                          10. Tune LIS using Ibias from Db to get optimised Imod
                                          11. Copy config files and run cosmic QA for >= 6 hours
                                          12. Post-process data and put it into archive using relevant scripts
                                          13. Put data into the database
                                          14. >
                                            >
                                            ./start This will create folder with FAM[uppermodulId]_FAM[downmoduleId] and put there config.txt,root files and all needed scripts. Go there.
                                          15. Set Spiroc DACs (offsets to SiPM HV) using Vbreakdown from Db for each SiPM. Power PS for all USB boxes and run ./dac_from_db
                                          16. Perform LighTightness tests (LT) and fill data by running ./check_LT.
                                          17. Perform connectivity test using all LIS settings. First copy old cfg by ./copy_cfgfiles then fo to test folder and run modqacern module. Put meanfull prefix, start run, check all, and save summary.
                                          18. Tune LIS using Ibias from Db to get optimised Imod by running ./tune_lis. This takes about 30min and produce cfg file in sw folder and txt files in lis folder. Copy new cfg files to local folders ./copy_cfgfiles , go to test folder and repeat test run to check LIS settings.
                                          19. Run cosmic QA for >= 6 hours. Go to QA folder and run modqacern module setting QA prefix
                                          20. Post-process data . After QA is finished, run ./sum_QA that creates root files in the sum folder.
                                          21. Put data into the database by running ./upload_db
                                          22. Move FAM*_FAM* folder to archive.
                                          23.  
                                            Added:
                                            >
                                            >
                                            All steps has to be registered in the checklist https://twiki.cern.ch/twiki/pub/LHCb/SciFiFibreModulesQA/Modtest_v4.pdf: Modtest_v4.pdf
                                             

                                            Initialising directory structure for measurements

                                            There's a script for creating a directory structure (and some further helpful scripts) for each new measurement session (one side of a module pair).

                                            Line: 379 to 452
                                             

                                            Results

                                            Changed:
                                            <
                                            <
                                            * pdf_15052019.zip: pdf_15-62019
                                            >
                                            >
                                              -- ValeryZhukov - 2019-01-28

                                            Changed:
                                            <
                                            <
                                            >
                                            >
                                             
                                            META FILEATTACHMENT attachment="Modassembly_v3.pdf" attr="" comment="ModuleAssembly check list" date="1548697366" name="Modassembly_v3.pdf" path="Modassembly_v3.pdf" size="96150" user="joukov" version="1"
                                            META FILEATTACHMENT attachment="Modassembly_v4.pdf" attr="" comment="ModuleAssembly check list v4" date="1548777333" name="Modassembly_v4.pdf" path="Modassembly_v4.pdf" size="99207" user="joukov" version="1"

                                            Revision 442019-08-06 - ValeryZhukov

                                            Line: 1 to 1
                                             
                                            META TOPICPARENT name="UpgradeSciFiTracker"

                                            SciFi Module Assembly and Quality Assurance tests

                                            Line: 9 to 9
                                              ask for key's LHCb secretariat.
                                            Changed:
                                            <
                                            <
                                            >
                                            >
                                            Contact persons for operation:
                                             
                                            Valery Zhukov joukov@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 78188 Cell(CERN): +41 76 487 6537
                                            Andreas Guth andreas.guth@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 75750 Cell(CERN):
                                            Line: 21 to 21
                                              ELOG:SciFi:Module elog
                                            Changed:
                                            <
                                            <
                                            Talks:
                                            >
                                            >
                                            Talks, see SciFi meetings:
                                              03.12.2018 SciFi General M.Dziewiecki
                                            Line: 33 to 33
                                              16.05.2019 SciFi General M.Dziewiecki
                                            Added:
                                            >
                                            >
                                            17.06.2019 SciFi General V.Zhukov

                                            25.07.2017 SciFi General Meeting S.Bachmann

                                             

                                            Module Assembly

                                            Deleted:
                                            <
                                            <

                                            GasTightness Test

                                             

                                            Module Testing in Cosmic Bench

                                            Changed:
                                            <
                                            <
                                            Cosmic bench PC(ask for pass): lhcb-cern / lhcbscifi.dyndns.cern.ch
                                            >
                                            >
                                            --+++++ Setup Three main components:

                                            The rack with:

                                            1. PC(ask for account): lhcbscifi.dyndns.cern.ch
                                            2. two USB boxes: Up: board37 uplinks:10,11,12,13,14,15,16,17

                                              Down: board36 uplinks: 20,21,22,23,24,25,26,27

                                            3. two corresponding PC
                                            4. HV Kethley PS
                                            5. HV switch box, with connection to multimeter (for LT test)
                                            6. two SPIROC boards got upper and down positions connected to the corresponding boxes by ribbons

                                            Cosmic bench with holders for two standard (5m) modules

                                             
                                            Added:
                                            >
                                            >
                                            Cosmic hodoscope:
                                            1. PC PC(ask for pass): lhcb-cern /lhcbscifi.dyndns.cern.ch
                                             
                                            Line: 49 to 73
                                             
                                            Software
                                            Added:
                                            >
                                            >
                                            scifiusbboard/modqacern

                                            Cosmic hodoscope

                                            Based on AMS scintillators runiing with hamamatsu flat PM (HVmax=800V)

                                             
                                            Deleted:
                                            <
                                            <
                                            Hodoscope
                                             
                                            Added:
                                            >
                                            >

                                            QA testing procedure in the CERN cosmic bench

                                            All operation with hardware:moving modules, connections, etc should be performed only by qualified personal (see contact persons for operations)
                                             
                                            Added:
                                            >
                                            >
                                            Most of operations on software are done with the simple scripts, but operator should know the procedure behind.
                                             
                                            Changed:
                                            <
                                            <

                                            General workflow

                                            >
                                            >
                                            The standard procedure is following:
                                             
                                            Deleted:
                                            <
                                            <
                                            One must proceed with all the paragraphs below with their order, so:
                                             
                                              Changed:
                                              <
                                              <
                                            1. Initialize directory structure
                                            2. Set Spiroc DACs
                                            3. Perform connectivity test
                                            4. Tune LIS
                                            5. Copy config files and run QA for >= 6 hours
                                            6. >
                                              >
                                            7. Install two modules on the upper and down cosmic bench positions, and cosmic hodoscope in between
                                            8. Initialize directory structure, by running scripts, ensure that all information is correctlybdownloaded from Db
                                            9. Set Spiroc DACs (offsets to SiPM HV) using Vbreakdown from Db for each SiPM, by
                                            10. Perform LighTightness tests (LT)
                                            11. Perform connectivity test using all LIS seetings
                                            12. Tune LIS using Ibias from Db to get optimised Imod
                                            13. Copy config files and run cosmic QA for >= 6 hours
                                            14.  
                                            15. Post-process data and put it into archive using relevant scripts
                                            16. Put data into the database
                                            17. Revision 432019-07-30 - MichalDziewiecki

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 304 to 304
                                                If you have a spare with different USB ID, the procedure is the same; just replace 22 with your USB ID.
                                              Added:
                                              >
                                              >

                                              Adjusting LV PS voltages

                                              Attention! This is a VERY advanced procedure!

                                              The +/-2V outputs of Spiroc setup PSes are adjustable. It has been checked that their adjustment has significant effect on the readout noise.

                                              In order to adjust the voltages, remove the PS outer cover and locate two miniature pots on the two leftmost channels of the PS (looking from LV output side). To adjust vlotages, use a small screwdriver and a voltmeter to control the voltage. The nominal value now is 2.15V.

                                              Remarks:

                                              • It's recommended to set both outputs to the same voltage.
                                              • Any increase of voltage should be consulted at least with Michal.
                                              • The lowest 'working' setting is 2.1V. For lower values, on-board voltage regulators for Spiroc chips do not work properly.
                                              • Always tune the PS warmed-up. The diagnostics ('third') setup can be used as a load.
                                               

                                              Taking LIS scan

                                              Revision 412019-07-24 - MichalDziewiecki

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 289 to 289
                                                Please read carefully every line of script's output and follow ALL weblinks. Even if annoying, it's still way better than putting all the data manually!
                                              Changed:
                                              <
                                              <

                                              System maintenance

                                              >
                                              >

                                              System maintenance / Advanced

                                               

                                              Replacing USB box

                                              Line: 303 to 303
                                                If you have a spare with different USB ID, the procedure is the same; just replace 22 with your USB ID.
                                              Added:
                                              >
                                              >

                                              Taking LIS scan

                                              The LIS scan is a procedure to collect data for a specified range of LIS settings. It is not intended to be used for every module, it's just for studying LIS properties.

                                              To perform a LIS scan:

                                              1. Go to your working directory (FAM_FAM)
                                              2. Go to lis/ and create a sub-directory for output data, e.g. =scan/, cd into it. Alternatively, you can use any directory in any place.
                                              3. Run the scanning scipt: root -l -q '$USBBOARDPATH/cern_scripts/lis_tuning/scan_lis.c("../../config.root")'.
                                                If you run from different directory as stated above, please ensure that you have supplied a correct path to your config.root file or leave this parameter empty("") to make the script ask for bias settings..
                                              4. You get a number of files: lis_raw_??.root (with raw histograms) and lisAnalysis_??.root (with calculated pedestals, gains and LYs), where ?? is a decimal number with current modulation setting for all LIS channels. Bias settings are taken from config.root or from manual input if you don't specify the file.

                                              Remark: The original modulation values in the config files will be overwritten. Therefore, you should run tune_lis after the scanning procedure or manually recover these settings.

                                               

                                              Results

                                              * pdf_15052019.zip: pdf_15-62019

                                              Revision 402019-07-24 - ValeryZhukov

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 332 to 332
                                               
                                              META FILEATTACHMENT attachment="I2C_Address_Translation.pdf" attr="" comment="LIS interface documentation (might be outdated)" date="1563275011" name="I2C_Address_Translation.pdf" path="I2C_Address_Translation.pdf" size="1190917" user="mdziewie" version="1"
                                              META FILEATTACHMENT attachment="I2C_Address_Translator-Schematics.pdf" attr="" comment="LIS interface documentation (might be outdated)" date="1563275011" name="I2C_Address_Translator-Schematics.pdf" path="I2C_Address_Translator-Schematics.pdf" size="15150" user="mdziewie" version="1"
                                              META FILEATTACHMENT attachment="slides_modules.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1563807734" name="slides_modules.pdf" path="slides_modules.pdf" size="18047083" user="ag604848" version="1"
                                              Added:
                                              >
                                              >
                                              META FILEATTACHMENT attachment="Modtest_v4.pdf" attr="" comment="Modtest_v4.pdf" date="1563960982" name="Modtest_v4.pdf" path="Modtest_v4.pdf" size="78057" user="joukov" version="1"

                                              Revision 392019-07-22 - AndreasGuth

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 320 to 320
                                               
                                              META FILEATTACHMENT attachment="pdf_15052019.zip" attr="" comment="pdf_15-62019" date="1560630495" name="pdf_15052019.zip" path="pdf_15052019.zip" size="21204441" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="scifi17062019.pdf" attr="" comment="" date="1560686046" name="scifi17062019.pdf" path="scifi17062019.pdf" size="7836654" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="slides.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1562164188" name="slides.pdf" path="slides.pdf" size="12061348" user="ag604848" version="4"
                                              Changed:
                                              <
                                              <
                                              META FILEATTACHMENT attachment="comparison_all.pdf" attr="" comment="Info for each assembled and tested module side regarding the cluster size for vertical tracks ('gap analysis') and light yield." date="1561736587" name="comparison_all.pdf" path="comparison_all.pdf" size="5562298" user="ag604848" version="1"
                                              >
                                              >
                                              META FILEATTACHMENT attachment="comparison_all.pdf" attr="" comment="Info for each assembled and tested module side regarding the cluster size for vertical tracks ('gap analysis') and light yield." date="1563808061" name="comparison_all.pdf" path="comparison_all.pdf" size="5567585" user="ag604848" version="2"
                                               
                                              META FILEATTACHMENT attachment="slides_topCover_manipulation.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1562619491" name="slides_topCover_manipulation.pdf" path="slides_topCover_manipulation.pdf" size="13991611" user="ag604848" version="1"
                                              META FILEATTACHMENT attachment="bads07072019.pdf" attr="" comment="Valery08072019" date="1562621519" name="bads07072019.pdf" path="bads07072019.pdf" size="3248504" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="manual.pdf" attr="" comment="Manual for the gas tightness tester" date="1563045543" name="manual.pdf" path="manual.pdf" size="638248" user="mdziewie" version="1"
                                              Line: 331 to 331
                                               
                                              META FILEATTACHMENT attachment="I2C_3M-TO-LIS_Adapter-Schematics.pdf" attr="" comment="LIS interface documentation (might be outdated)" date="1563275011" name="I2C_3M-TO-LIS_Adapter-Schematics.pdf" path="I2C_3M-TO-LIS_Adapter-Schematics.pdf" size="9471" user="mdziewie" version="1"
                                              META FILEATTACHMENT attachment="I2C_Address_Translation.pdf" attr="" comment="LIS interface documentation (might be outdated)" date="1563275011" name="I2C_Address_Translation.pdf" path="I2C_Address_Translation.pdf" size="1190917" user="mdziewie" version="1"
                                              META FILEATTACHMENT attachment="I2C_Address_Translator-Schematics.pdf" attr="" comment="LIS interface documentation (might be outdated)" date="1563275011" name="I2C_Address_Translator-Schematics.pdf" path="I2C_Address_Translator-Schematics.pdf" size="15150" user="mdziewie" version="1"
                                              Added:
                                              >
                                              >
                                              META FILEATTACHMENT attachment="slides_modules.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1563807734" name="slides_modules.pdf" path="slides_modules.pdf" size="18047083" user="ag604848" version="1"

                                              Revision 382019-07-16 - MichalDziewiecki

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 324 to 324
                                               
                                              META FILEATTACHMENT attachment="slides_topCover_manipulation.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1562619491" name="slides_topCover_manipulation.pdf" path="slides_topCover_manipulation.pdf" size="13991611" user="ag604848" version="1"
                                              META FILEATTACHMENT attachment="bads07072019.pdf" attr="" comment="Valery08072019" date="1562621519" name="bads07072019.pdf" path="bads07072019.pdf" size="3248504" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="manual.pdf" attr="" comment="Manual for the gas tightness tester" date="1563045543" name="manual.pdf" path="manual.pdf" size="638248" user="mdziewie" version="1"
                                              Added:
                                              >
                                              >
                                              META FILEATTACHMENT attachment="ADB-PiggybackV2.1.pdf" attr="" comment="Schematics for Piggyback" date="1563274592" name="ADB-PiggybackV2.1.pdf" path="ADB-PiggybackV2.1.pdf" size="887204" user="mdziewie" version="1"
                                              META FILEATTACHMENT attachment="HPE-SPIROCA-256_1_1-Schematics.pdf" attr="" comment="Schematics for the Spiroc mezzanine" date="1563274622" name="HPE-SPIROCA-256_1_1-Schematics.pdf" path="HPE-SPIROCA-256_1_1-Schematics.pdf" size="110354" user="mdziewie" version="1"
                                              META FILEATTACHMENT attachment="LHCB_TestBoard_SchematicNeu_19_03_2015.pdf" attr="" comment="Schematics for Spiroc motherboard" date="1563274646" name="LHCB_TestBoard_SchematicNeu_19_03_2015.pdf" path="LHCB_TestBoard_SchematicNeu_19_03_2015.pdf" size="36344" user="mdziewie" version="1"
                                              META FILEATTACHMENT attachment="ROE_ADB.pdf" attr="" comment="Schematics for the USB-Board" date="1563274674" name="ROE_ADB.pdf" path="ROE_ADB.pdf" size="5369136" user="mdziewie" version="1"
                                              META FILEATTACHMENT attachment="I2C_3M-TO-LIS_Adapter-Schematics.pdf" attr="" comment="LIS interface documentation (might be outdated)" date="1563275011" name="I2C_3M-TO-LIS_Adapter-Schematics.pdf" path="I2C_3M-TO-LIS_Adapter-Schematics.pdf" size="9471" user="mdziewie" version="1"
                                              META FILEATTACHMENT attachment="I2C_Address_Translation.pdf" attr="" comment="LIS interface documentation (might be outdated)" date="1563275011" name="I2C_Address_Translation.pdf" path="I2C_Address_Translation.pdf" size="1190917" user="mdziewie" version="1"
                                              META FILEATTACHMENT attachment="I2C_Address_Translator-Schematics.pdf" attr="" comment="LIS interface documentation (might be outdated)" date="1563275011" name="I2C_Address_Translator-Schematics.pdf" path="I2C_Address_Translator-Schematics.pdf" size="15150" user="mdziewie" version="1"

                                              Revision 372019-07-13 - MichalDziewiecki

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 323 to 323
                                               
                                              META FILEATTACHMENT attachment="comparison_all.pdf" attr="" comment="Info for each assembled and tested module side regarding the cluster size for vertical tracks ('gap analysis') and light yield." date="1561736587" name="comparison_all.pdf" path="comparison_all.pdf" size="5562298" user="ag604848" version="1"
                                              META FILEATTACHMENT attachment="slides_topCover_manipulation.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1562619491" name="slides_topCover_manipulation.pdf" path="slides_topCover_manipulation.pdf" size="13991611" user="ag604848" version="1"
                                              META FILEATTACHMENT attachment="bads07072019.pdf" attr="" comment="Valery08072019" date="1562621519" name="bads07072019.pdf" path="bads07072019.pdf" size="3248504" user="joukov" version="1"
                                              Added:
                                              >
                                              >
                                              META FILEATTACHMENT attachment="manual.pdf" attr="" comment="Manual for the gas tightness tester" date="1563045543" name="manual.pdf" path="manual.pdf" size="638248" user="mdziewie" version="1"

                                              Revision 362019-07-10 - MichalDziewiecki

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 288 to 288
                                                Please read carefully every line of script's output and follow ALL weblinks. Even if annoying, it's still way better than putting all the data manually!
                                              Added:
                                              >
                                              >

                                              System maintenance

                                              Replacing USB box

                                              In order to replace one of existing USB boxes (36 or 37) with a spare one (22), do the following:

                                              1. Locate $USBBOARDPATH/cfgFiles/board22.cfg.bak, edit it and put all contents from the relevant file (board36.cfg.bak or board37.cfg.bak)
                                              2. Go to line 7 of this file and edit it to: usbBoardID || 22 ||, save file and close editor.
                                              3. Locate $USBBOARDPATH/cern_scripts/utils.h, edit it and modify the relevant define at line 4 or 5 (USB_ID_TOP or USB_ID_BOT), save file and close editor.
                                              4. If you already created your working directory ($CERNDATAPATH/FAMxxxxxX_FAMxxxxxxX), go into it, ./restart and ./copy_cfgfiles.
                                              5. Now you are running with new USB Box.
                                              If you have a spare with different USB ID, the procedure is the same; just replace 22 with your USB ID.
                                               

                                              Results

                                              * pdf_15052019.zip: pdf_15-62019

                                              Revision 352019-07-08 - ValeryZhukov

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 296 to 296
                                               

                                              Added:
                                              >
                                              >
                                               
                                              META FILEATTACHMENT attachment="Modassembly_v3.pdf" attr="" comment="ModuleAssembly check list" date="1548697366" name="Modassembly_v3.pdf" path="Modassembly_v3.pdf" size="96150" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="Modassembly_v4.pdf" attr="" comment="ModuleAssembly check list v4" date="1548777333" name="Modassembly_v4.pdf" path="Modassembly_v4.pdf" size="99207" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="Modtest_v2.pdf" attr="" comment="" date="1550063093" name="Modtest_v2.pdf" path="Modtest_v2.pdf" size="74863" user="joukov" version="1"
                                              Line: 305 to 307
                                               
                                              META FILEATTACHMENT attachment="slides.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1562164188" name="slides.pdf" path="slides.pdf" size="12061348" user="ag604848" version="4"
                                              META FILEATTACHMENT attachment="comparison_all.pdf" attr="" comment="Info for each assembled and tested module side regarding the cluster size for vertical tracks ('gap analysis') and light yield." date="1561736587" name="comparison_all.pdf" path="comparison_all.pdf" size="5562298" user="ag604848" version="1"
                                              META FILEATTACHMENT attachment="slides_topCover_manipulation.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1562619491" name="slides_topCover_manipulation.pdf" path="slides_topCover_manipulation.pdf" size="13991611" user="ag604848" version="1"
                                              Added:
                                              >
                                              >
                                              META FILEATTACHMENT attachment="bads07072019.pdf" attr="" comment="Valery08072019" date="1562621519" name="bads07072019.pdf" path="bads07072019.pdf" size="3248504" user="joukov" version="1"

                                              Revision 342019-07-08 - AndreasGuth

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 304 to 304
                                               
                                              META FILEATTACHMENT attachment="scifi17062019.pdf" attr="" comment="" date="1560686046" name="scifi17062019.pdf" path="scifi17062019.pdf" size="7836654" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="slides.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1562164188" name="slides.pdf" path="slides.pdf" size="12061348" user="ag604848" version="4"
                                              META FILEATTACHMENT attachment="comparison_all.pdf" attr="" comment="Info for each assembled and tested module side regarding the cluster size for vertical tracks ('gap analysis') and light yield." date="1561736587" name="comparison_all.pdf" path="comparison_all.pdf" size="5562298" user="ag604848" version="1"
                                              Added:
                                              >
                                              >
                                              META FILEATTACHMENT attachment="slides_topCover_manipulation.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1562619491" name="slides_topCover_manipulation.pdf" path="slides_topCover_manipulation.pdf" size="13991611" user="ag604848" version="1"

                                              Revision 322019-07-03 - AndreasGuth

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 302 to 302
                                               
                                              META FILEATTACHMENT attachment="Modtest_v3.pdf" attr="" comment="" date="1550755225" name="Modtest_v3.pdf" path="Modtest_v3.pdf" size="76464" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="pdf_15052019.zip" attr="" comment="pdf_15-62019" date="1560630495" name="pdf_15052019.zip" path="pdf_15052019.zip" size="21204441" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="scifi17062019.pdf" attr="" comment="" date="1560686046" name="scifi17062019.pdf" path="scifi17062019.pdf" size="7836654" user="joukov" version="1"
                                              Changed:
                                              <
                                              <
                                              META FILEATTACHMENT attachment="slides.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1562059946" name="slides.pdf" path="slides.pdf" size="11616445" user="ag604848" version="2"
                                              >
                                              >
                                              META FILEATTACHMENT attachment="slides.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1562164188" name="slides.pdf" path="slides.pdf" size="12061348" user="ag604848" version="4"
                                               
                                              META FILEATTACHMENT attachment="comparison_all.pdf" attr="" comment="Info for each assembled and tested module side regarding the cluster size for vertical tracks ('gap analysis') and light yield." date="1561736587" name="comparison_all.pdf" path="comparison_all.pdf" size="5562298" user="ag604848" version="1"

                                              Revision 312019-07-02 - AndreasGuth

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 302 to 302
                                               
                                              META FILEATTACHMENT attachment="Modtest_v3.pdf" attr="" comment="" date="1550755225" name="Modtest_v3.pdf" path="Modtest_v3.pdf" size="76464" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="pdf_15052019.zip" attr="" comment="pdf_15-62019" date="1560630495" name="pdf_15052019.zip" path="pdf_15052019.zip" size="21204441" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="scifi17062019.pdf" attr="" comment="" date="1560686046" name="scifi17062019.pdf" path="scifi17062019.pdf" size="7836654" user="joukov" version="1"
                                              Changed:
                                              <
                                              <
                                              META FILEATTACHMENT attachment="slides.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1561729028" name="slides.pdf" path="slides.pdf" size="3559983" user="ag604848" version="1"
                                              >
                                              >
                                              META FILEATTACHMENT attachment="slides.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1562059946" name="slides.pdf" path="slides.pdf" size="11616445" user="ag604848" version="2"
                                               
                                              META FILEATTACHMENT attachment="comparison_all.pdf" attr="" comment="Info for each assembled and tested module side regarding the cluster size for vertical tracks ('gap analysis') and light yield." date="1561736587" name="comparison_all.pdf" path="comparison_all.pdf" size="5562298" user="ag604848" version="1"

                                              Revision 302019-06-28 - AndreasGuth

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 303 to 303
                                               
                                              META FILEATTACHMENT attachment="pdf_15052019.zip" attr="" comment="pdf_15-62019" date="1560630495" name="pdf_15052019.zip" path="pdf_15052019.zip" size="21204441" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="scifi17062019.pdf" attr="" comment="" date="1560686046" name="scifi17062019.pdf" path="scifi17062019.pdf" size="7836654" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="slides.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1561729028" name="slides.pdf" path="slides.pdf" size="3559983" user="ag604848" version="1"
                                              Added:
                                              >
                                              >
                                              META FILEATTACHMENT attachment="comparison_all.pdf" attr="" comment="Info for each assembled and tested module side regarding the cluster size for vertical tracks ('gap analysis') and light yield." date="1561736587" name="comparison_all.pdf" path="comparison_all.pdf" size="5562298" user="ag604848" version="1"

                                              Revision 292019-06-28 - AndreasGuth

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 302 to 302
                                               
                                              META FILEATTACHMENT attachment="Modtest_v3.pdf" attr="" comment="" date="1550755225" name="Modtest_v3.pdf" path="Modtest_v3.pdf" size="76464" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="pdf_15052019.zip" attr="" comment="pdf_15-62019" date="1560630495" name="pdf_15052019.zip" path="pdf_15052019.zip" size="21204441" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="scifi17062019.pdf" attr="" comment="" date="1560686046" name="scifi17062019.pdf" path="scifi17062019.pdf" size="7836654" user="joukov" version="1"
                                              Added:
                                              >
                                              >
                                              META FILEATTACHMENT attachment="slides.pdf" attr="" comment="Status of top-cover manipulation tests for the investigation of the 'edge anomaly'" date="1561729028" name="slides.pdf" path="slides.pdf" size="3559983" user="ag604848" version="1"

                                              Revision 282019-06-16 - ValeryZhukov

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 301 to 301
                                               
                                              META FILEATTACHMENT attachment="Modtest_v2.pdf" attr="" comment="" date="1550063093" name="Modtest_v2.pdf" path="Modtest_v2.pdf" size="74863" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="Modtest_v3.pdf" attr="" comment="" date="1550755225" name="Modtest_v3.pdf" path="Modtest_v3.pdf" size="76464" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="pdf_15052019.zip" attr="" comment="pdf_15-62019" date="1560630495" name="pdf_15052019.zip" path="pdf_15052019.zip" size="21204441" user="joukov" version="1"
                                              Added:
                                              >
                                              >
                                              META FILEATTACHMENT attachment="scifi17062019.pdf" attr="" comment="" date="1560686046" name="scifi17062019.pdf" path="scifi17062019.pdf" size="7836654" user="joukov" version="1"

                                              Revision 272019-06-15 - ValeryZhukov

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 288 to 288
                                                Please read carefully every line of script's output and follow ALL weblinks. Even if annoying, it's still way better than putting all the data manually!
                                              Added:
                                              >
                                              >

                                              Results

                                               
                                              Changed:
                                              <
                                              <
                                              >
                                              >
                                              * pdf_15052019.zip: pdf_15-62019
                                                -- ValeryZhukov - 2019-01-28
                                              Changed:
                                              <
                                              <
                                              >
                                              >
                                               
                                              META FILEATTACHMENT attachment="Modassembly_v3.pdf" attr="" comment="ModuleAssembly check list" date="1548697366" name="Modassembly_v3.pdf" path="Modassembly_v3.pdf" size="96150" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="Modassembly_v4.pdf" attr="" comment="ModuleAssembly check list v4" date="1548777333" name="Modassembly_v4.pdf" path="Modassembly_v4.pdf" size="99207" user="joukov" version="1"

                                              Revision 262019-06-15 - ValeryZhukov

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 293 to 293
                                                -- ValeryZhukov - 2019-01-28
                                              Added:
                                              >
                                              >
                                               
                                              META FILEATTACHMENT attachment="Modassembly_v3.pdf" attr="" comment="ModuleAssembly check list" date="1548697366" name="Modassembly_v3.pdf" path="Modassembly_v3.pdf" size="96150" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="Modassembly_v4.pdf" attr="" comment="ModuleAssembly check list v4" date="1548777333" name="Modassembly_v4.pdf" path="Modassembly_v4.pdf" size="99207" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="Modtest_v2.pdf" attr="" comment="" date="1550063093" name="Modtest_v2.pdf" path="Modtest_v2.pdf" size="74863" user="joukov" version="1"
                                              META FILEATTACHMENT attachment="Modtest_v3.pdf" attr="" comment="" date="1550755225" name="Modtest_v3.pdf" path="Modtest_v3.pdf" size="76464" user="joukov" version="1"
                                              Added:
                                              >
                                              >
                                              META FILEATTACHMENT attachment="pdf_15052019.zip" attr="" comment="pdf_15-62019" date="1560630495" name="pdf_15052019.zip" path="pdf_15052019.zip" size="21204441" user="joukov" version="1"

                                              Revision 232019-04-02 - MichalDziewiecki

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 90 to 90
                                               
                                            18. .../copy_cfgfiles - copy module config files from USBBOARDPATH to QA and test directories
                                            19. .../run_QA - run modqacern from QA directory (must copy_cfgfiles first!)
                                            20. .../test_QA - run modqacern from test directory (must copy_cfgfiles first!)
                                            21. Added:
                                              >
                                              >
                                            22. .../sum_QA - post-process QA data
                                            23.  
                                            24. .../check_LT - query light tightness result and write them to a file
                                            25. .../db_login - a helper for logging into the production database (produces Michal's name on output as a side effect)
                                            26. .../update_db - upload all possible data into the production database
                                            27. Added:
                                              >
                                              >
                                            28. .../copy_results - copy most important files to the data/FAM directory
                                            29.  
                                            30. .../restart - re-create directory structure, config files and/or local scripts
                                            31. Line: 162 to 164
                                               

                                              Light Tightness Tests

                                              INITIAL STATE: both USB-Box PS ON, HV PS OFF
                                              Changed:
                                              <
                                              <
                                              Use check_LT script for saving data on the PC!
                                              >
                                              >
                                              Use check_LT script for saving data on the PC!
                                               
                                              1. Connect multimeter (uA input) to banana cables from HV distribution box.
                                              2. Distribution box: all switches DOWN
                                              Line: 232 to 234
                                               

                                              Data post-processing

                                              Added:
                                              >
                                              >
                                              To post-process the data collected in the QA run, simply type ./sum_QA from the FAM directory.
                                              Attention: post-processing might take a significant amount of time (> few s).
                                              The following files will be generated in the .../sum_QA directory:
                                              • BTCxxxxx_Vbd.root (x2) - a file with breakdown voltages copied from data/BTC
                                              • mod_FSMxxxxx_X.root (x2) - a file with HD/Nikhef QA data for a module, copied from data/FSM
                                              • dual_FAMxxxxx_X.root (x2) - an intermediate file with Cern cosmic data processed
                                              • modcb_FAMxxxxx_X.root (x2) - another file of this kind
                                              • sum_FAMxxxxx_X.root (x2) - the main output file with data
                                              • sum_FAM_xxxxx_X.root (x2) - a pdf summary of the above
                                              • sumbadch_FAM_xxxxx_X.txt - a text file with a summary of bad channels
                                              • sumgaps_FAM_xxxxx_X.txt - a text file with a summary of mat-SiPM gap calculation
                                               
                                              Deleted:
                                              <
                                              <

                                              Archiving results locally

                                               
                                              Added:
                                              >
                                              >

                                              Archiving results locally

                                               
                                              Added:
                                              >
                                              >
                                              To make a local copy in data/FAM/, type ./copy_results.
                                              See the example code below to see which files are copied:
                                              		mkdir -p $DATAPATH/FAM/FAM00019 
                                               		mkdir $DATAPATH/FAM/FAM00019/sideA 
                                               		cp ./config.txt $DATAPATH/FAM/FAM00019/sideA/ 
                                               		cp ./config.root $DATAPATH/FAM/FAM00019/sideA/ 
                                               		mkdir $DATAPATH/FAM/FAM00019/sideA/sum 
                                               		cp ./sum/sum_FAM00019_A.root $DATAPATH/FAM/FAM00019/sideA/sum/ 
                                               		cp ./sum/sumgaps_FAM00019_A.txt $DATAPATH/FAM/FAM00019/sideA/sum/ 
                                               		cp ./sum/sumbadch_FAM00019_A.txt $DATAPATH/FAM/FAM00019/sideA/sum/ 
                                               		cp ./sum/sum_FAM00019_A.pdf $DATAPATH/FAM/FAM00019/sideA/sum/ 
                                               		mkdir $DATAPATH/FAM/FAM00019/sideA/lis 
                                               		cp ./lis/FAM00019A.lis.txt $DATAPATH/FAM/FAM00019/sideA/lis/ 
                                               		mkdir $DATAPATH/FAM/FAM00019/sideA/LT 
                                               		cp ./LT/lt.txt $DATAPATH/FAM/FAM00019/sideA/LT/ 
                                              
                                               

                                              Putting results into production database

                                              Remark: Putting data into database is a SEMI-automated process and needs an active supervision of the operator. Depending on the current state of the database and results, some data may remain not uploaded. One of these cases is when some relevant data already exists in the database.

                                              Changed:
                                              <
                                              <
                                              To start, go to FAM folder and type ./update_db. Entering DB credentials might be necessary.
                                              >
                                              >
                                              To start, go to FAM directory and type ./update_db. Entering DB credentials might be necessary.
                                                Please read carefully every line of script's output and follow ALL weblinks. Even if annoying, it's still way better than putting all the data manually!

                                              Revision 222019-03-28 - MichalDziewiecki

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 90 to 90
                                               
                                            32. .../copy_cfgfiles - copy module config files from USBBOARDPATH to QA and test directories
                                            33. .../run_QA - run modqacern from QA directory (must copy_cfgfiles first!)
                                            34. .../test_QA - run modqacern from test directory (must copy_cfgfiles first!)
                                            35. Added:
                                              >
                                              >
                                            36. .../check_LT - query light tightness result and write them to a file
                                            37.  
                                            38. .../db_login - a helper for logging into the production database (produces Michal's name on output as a side effect)
                                            39. .../update_db - upload all possible data into the production database
                                            40. Added:
                                              >
                                              >
                                            41. .../restart - re-create directory structure, config files and/or local scripts
                                            42.  

                                              Attention: backup script
                                              Line: 117 to 119
                                               
                                            43. run_QA
                                            44. Changed:
                                              <
                                              <
                                              The QA and test directories contain a backup_blind file, which disables making backups if only USBBoard config files are there.
                                              >
                                              >
                                              <!-- The QA and test directories contain a backup_blind file, which disables making backups if only USBBoard config files are there. -->
                                               

                                              Downloading Vdb info and setting Spiroc DACs

                                              Changed:
                                              <
                                              <
                                              Automated procedure:
                                              >
                                              >
                                              Automated procedure: (use it!)
                                               
                                              1. Ensure that HV is off, both LV on
                                              2. Run ./dac_from_db
                                              Changed:
                                              <
                                              <
                                              Manual procedure:
                                              >
                                              >
                                              Manual procedure: (only in troubles)
                                               
                                              1. Copy DAC files: type ./dacfiles_from_db
                                                Currently, programing DAC must be done manually:
                                              Line: 140 to 141
                                               
                                            45. Type setSpirocDac $USBBOARDPATH/cfgFiles ./vbd/mod_dn/dacfile_from_db.txt to program Spiroc chips for lower system
                                            46. Switch both PS back on
                                            47. Deleted:
                                              <
                                              <
                                              This process will be automated in the future...
                                               

                                              Installation and connectivity test

                                              Line: 162 to 161
                                               

                                              Light Tightness Tests

                                              Changed:
                                              <
                                              <
                                              INITIAL STATE: both USB-Box PS ON, HV PS OFF
                                              >
                                              >
                                              INITIAL STATE: both USB-Box PS ON, HV PS OFF
                                              Use check_LT script for saving data on the PC!
                                               
                                              1. Connect multimeter (uA input) to banana cables from HV distribution box.
                                              2. Distribution box: all switches DOWN
                                              Line: 207 to 206
                                               

                                              HV scan (Vbd optimization) - optional

                                              Currently, this step can be performed only manually.

                                              Added:
                                              >
                                              >
                                              However, it shouldn't be performed at all;)
                                               

                                              Cosmics

                                              Line: 216 to 216
                                                setup the prefix for saved root files and click start. Use QA prefix for regular runs.
                                              Added:
                                              >
                                              >
                                               Each run consists of 3 parts: Pedestal 1000triggers LIS run 8000triggers
                                              Line: 223 to 224
                                                During the run 3 trees are filled in the corresponding root file with the name prefix_unixtime_data_time.root Also the selected tree for events with only 1 hit in one module is stored in the dualtree_unixtime.root file.
                                              Added:
                                              >
                                              >
                                                Then new run is started automatically. The running can be stopped by clicking stop. Then slick save to save the Summary file.

                                              Revision 212019-03-28 - MichalDziewiecki

                                              Line: 1 to 1
                                               
                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                              SciFi Module Assembly and Quality Assurance tests

                                              Line: 78 to 78
                                               
                                            48. .../lis/ - a directory for LIS tuning results
                                            49. .../QA/ - a directory for cosmic data and results
                                            50. Changed:
                                              <
                                              <
                                            51. .../test/ - a directory for debug cosmic runs
                                            52. >
                                              >
                                            53. .../test/ - a directory for debug cosmic runs
                                            54. .../sum/ - a directory for cosmic data analysis
                                            55.   Scripts:
                                                Line: 114 to 115
                                                 
                                              • tune_lis
                                              • tune_lis_advanced
                                              • run_QA
                                              • Deleted:
                                                <
                                                <
                                              • test_QA
                                              •  

                                                The QA and test directories contain a backup_blind file, which disables making backups if only USBBoard config files are there.

                                                Revision 192019-03-21 - MichalDziewiecki

                                                Line: 1 to 1
                                                 
                                                META TOPICPARENT name="UpgradeSciFiTracker"

                                                SciFi Module Assembly and Quality Assurance tests

                                                Line: 13 to 13
                                                 
                                                Valery Zhukov joukov@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 78188 Cell(CERN): +41 76 487 6537
                                                Andreas Guth   Office: Cell(CERN):
                                                Added:
                                                >
                                                >
                                                Michal Dziewiecki mdziewie@cernNOSPAMPLEASE.ch Office: Cell(CERN): +48 791 221 186
                                                 

                                                Info and Links

                                                Line: 52 to 53
                                                 
                                              • Tune LIS
                                              • Copy config files and run QA for >= 6 hours
                                              • Post-process data and put it into archive using relevant scripts
                                              • Added:
                                                >
                                                >
                                              • Put data into the database
                                              •  

                                                Initialising directory structure for measurements

                                                Line: 87 to 89
                                                 
                                              • .../copy_cfgfiles - copy module config files from USBBOARDPATH to QA and test directories
                                              • .../run_QA - run modqacern from QA directory (must copy_cfgfiles first!)
                                              • .../test_QA - run modqacern from test directory (must copy_cfgfiles first!)
                                              • Added:
                                                >
                                                >
                                              • .../db_login - a helper for logging into the production database (produces Michal's name on output as a side effect)
                                              • .../update_db - upload all possible data into the production database
                                              •  

                                                Attention: backup script
                                                Line: 227 to 231
                                                 

                                                Data post-processing

                                                Changed:
                                                <
                                                <

                                                Archiving results

                                                >
                                                >

                                                Archiving results locally

                                                 
                                                Added:
                                                >
                                                >

                                                Putting results into production database

                                                Remark: Putting data into database is a SEMI-automated process and needs an active supervision of the operator. Depending on the current state of the database and results, some data may remain not uploaded. One of these cases is when some relevant data already exists in the database.

                                                To start, go to FAM folder and type ./update_db. Entering DB credentials might be necessary.

                                                Please read carefully every line of script's output and follow all weblinks. Even if annoying, it's still way better than putting all the data manually!

                                                 

                                                Revision 182019-03-01 - MichalDziewiecki

                                                Line: 1 to 1
                                                 
                                                META TOPICPARENT name="UpgradeSciFiTracker"

                                                SciFi Module Assembly and Quality Assurance tests

                                                Line: 61 to 61
                                                 
                                              • Open terminal. Go to moduleTest/cern_data
                                              • Type ./start
                                              • Answer all questions given by the script
                                              • Added:
                                                >
                                                >
                                              • If there are problems with accessing database, probably you're not logged in. Break the script and type ./dblogin
                                              •   Currently, the following directories/files are created:
                                                Line: 82 to 83
                                                 
                                              • .../tune_lis - a convenience script for running LIS tuning procedure
                                              • .../tune_lis_advanced - the same, but allowing for modifying of bias currents. Use with care
                                              • .../dacfiles_from_db - copy DAC files from local database to working directory
                                              • Added:
                                                >
                                                >
                                              • .../dac_from_db - run dacfiles_from_db and then set Spiroc DACs
                                              •  
                                              • .../copy_cfgfiles - copy module config files from USBBOARDPATH to QA and test directories
                                              • .../run_QA - run modqacern from QA directory (must copy_cfgfiles first!)
                                              • .../test_QA - run modqacern from test directory (must copy_cfgfiles first!)
                                              • Line: 116 to 118
                                                 

                                                Downloading Vdb info and setting Spiroc DACs

                                                Added:
                                                >
                                                >
                                                Automated procedure:
                                                1. Ensure that HV is off, both LV on
                                                2. Run ./dac_from_db

                                                Manual procedure:

                                                 
                                                1. Copy DAC files: type ./dacfiles_from_db
                                                  Currently, programing DAC must be done manually:
                                                Changed:
                                                <
                                                <
                                              • Ensure that HV is off
                                              • >
                                                >
                                              • Ensure that HV is off, both LV on
                                              •  
                                              • Switch upper PS on, lower PS off
                                              • Type setSpirocDac $USBBOARDPATH/cfgFiles ./vbd/mod_up/dacfile_from_db.txt to program Spiroc chips for upper system
                                              • Switch upper PS off, lower PS on
                                              • Revision 172019-03-01 - MichalDziewiecki

                                                Line: 1 to 1
                                                 
                                                META TOPICPARENT name="UpgradeSciFiTracker"

                                                SciFi Module Assembly and Quality Assurance tests

                                                Line: 63 to 63
                                                 
                                              • Answer all questions given by the script Currently, the following directories/files are created:
                                              • Added:
                                                >
                                                >
                                                Directories:
                                                 
                                                • .../config.txt - a summary file with entered module data
                                                • .../config.root - the same as root tree
                                                • .../vbd/ - a directory for all breakdown-related stuff
                                                Added:
                                                >
                                                >
                                                • .../vbd/mod_up/
                                                • .../vbd/mod_dn/
                                                 
                                              • .../lis/ - a directory for LIS tuning results
                                              • .../QA/ - a directory for cosmic data and results
                                              • Changed:
                                                <
                                                <
                                              • .../test/ - a directory for debug cosmic runs
                                              • >
                                                >
                                              • .../test/ - a directory for debug cosmic runs
                                                Scripts:
                                                •  
                                                • .../tune_lis - a convenience script for running LIS tuning procedure
                                                • .../tune_lis_advanced - the same, but allowing for modifying of bias currents. Use with care
                                                • Changed:
                                                  <
                                                  <
                                                • .../dacfiles_from_db - download Vbd data from database and generate DAC files from them under construction...
                                                • >
                                                  >
                                                • .../dacfiles_from_db - copy DAC files from local database to working directory
                                                •  
                                                • .../copy_cfgfiles - copy module config files from USBBOARDPATH to QA and test directories
                                                • .../run_QA - run modqacern from QA directory (must copy_cfgfiles first!)
                                                • .../test_QA - run modqacern from test directory (must copy_cfgfiles first!)
                                                • Line: 89 to 98
                                                   #The name of this subdirectory is always BACKUP_yyyymmdd_hhmmss. #Additionally, a text file in this directory (backup_info) will be created with a user-given information. #All files specified in .backup_ignore will be SKIPPED when archiving.
                                                  Changed:
                                                  <
                                                  <
                                                  #All files specified in .backup_blind will be archived, by not relevant for the initial decision: do backup or do not.
                                                  >
                                                  >
                                                  #All files specified in .backup_blind will be archived, but not relevant for the initial decision: do backup or do not.
                                                   #Currently, only files from top-level directory can be specified, i.e. any subdirectory is treated as a single file. #Both files use regular expressions.
                                                  Line: 107 to 116
                                                   

                                                  Downloading Vdb info and setting Spiroc DACs

                                                  Added:
                                                  >
                                                  >
                                                  1. Copy DAC files: type ./dacfiles_from_db
                                                    Currently, programing DAC must be done manually:
                                                  2. Ensure that HV is off
                                                  3. Switch upper PS on, lower PS off
                                                  4. Type setSpirocDac $USBBOARDPATH/cfgFiles ./vbd/mod_up/dacfile_from_db.txt to program Spiroc chips for upper system
                                                  5. Switch upper PS off, lower PS on
                                                  6. Type setSpirocDac $USBBOARDPATH/cfgFiles ./vbd/mod_dn/dacfile_from_db.txt to program Spiroc chips for lower system
                                                  7. Switch both PS back on
                                                  This process will be automated in the future...
                                                   

                                                  Installation and connectivity test

                                                  Revision 162019-02-26 - MichalDziewiecki

                                                  Line: 1 to 1
                                                   
                                                  META TOPICPARENT name="UpgradeSciFiTracker"

                                                  SciFi Module Assembly and Quality Assurance tests

                                                  Line: 84 to 84
                                                   The script is interactive and will ask for a short comment (then saved to a backup_info file) and whether to delete old data. It can be used anywhere (even outside the created directory structure).
                                                  Added:
                                                  >
                                                  >
                                                  Further comments on the script:
                                                  #The name of this subdirectory is always BACKUP_yyyymmdd_hhmmss.
                                                  #Additionally, a text file in this directory (backup_info) will be created with a user-given information.
                                                  #All files specified in .backup_ignore will be SKIPPED when archiving.
                                                  #All files specified in .backup_blind will be archived, by not relevant for the initial decision: do backup or do not.
                                                  #Currently, only files from top-level directory can be specified, i.e. any subdirectory is treated as a single file. 
                                                  #Both files use regular expressions.
                                                  
                                                   The following scripts make backups automatically if target directories are not empty:
                                                  • tune_lis
                                                  Line: 92 to 102
                                                   
                                                • test_QA
                                                • Changed:
                                                  <
                                                  <
                                                  The QA and test directories contain a backup_blind file, which disallows making backups if only USBBoard config files are there.
                                                  >
                                                  >
                                                  The QA and test directories contain a backup_blind file, which disables making backups if only USBBoard config files are there.
                                                   

                                                  Downloading Vdb info and setting Spiroc DACs

                                                  Revision 152019-02-25 - MichalDziewiecki

                                                  Line: 1 to 1
                                                   
                                                  META TOPICPARENT name="UpgradeSciFiTracker"

                                                  SciFi Module Assembly and Quality Assurance tests

                                                  Line: 79 to 79
                                                   

                                                  Attention: backup script
                                                  Changed:
                                                  <
                                                  <
                                                  Important: In most cases, running some scripts twice would delete old data. to avoid it, a backup script can be used. Top backup a dir, simply go into it and type backup_me. This will create a new folder with a general name of BACKUP_yyyymmdd_hhmmss and copy or move all files there.
                                                  >
                                                  >
                                                  Important: In most cases, running some scripts twice would delete old data. To avoid it, a backup script can be used. To backup a dir, simply go into it and type backup_me. This will create a new folder with a general name of BACKUP_yyyymmdd_hhmmss and copy or move all files there.
                                                   The script is interactive and will ask for a short comment (then saved to a backup_info file) and whether to delete old data.
                                                  Added:
                                                  >
                                                  >
                                                  It can be used anywhere (even outside the created directory structure).
                                                   
                                                  Changed:
                                                  <
                                                  <
                                                  Additionally, the following scripts make backups automatically if target directories are not empty:
                                                  >
                                                  >
                                                  The following scripts make backups automatically if target directories are not empty:
                                                   
                                                  • tune_lis
                                                  • tune_lis_advanced
                                                  Line: 91 to 92
                                                   
                                                • test_QA
                                                • Added:
                                                  >
                                                  >
                                                  The QA and test directories contain a backup_blind file, which disallows making backups if only USBBoard config files are there.
                                                   

                                                  Downloading Vdb info and setting Spiroc DACs

                                                  Revision 142019-02-25 - MichalDziewiecki

                                                  Line: 1 to 1
                                                   
                                                  META TOPICPARENT name="UpgradeSciFiTracker"

                                                  SciFi Module Assembly and Quality Assurance tests

                                                  Line: 58 to 58
                                                    There's a script for creating a directory structure (and some further helpful scripts) for each new measurement session (one side of a module pair).
                                                    Changed:
                                                    <
                                                    <
                                                  1. Open terminal. Go to moduleTest/cern_data
                                                  2. Type ./start
                                                  3. >
                                                    >
                                                  4. Open terminal. Go to moduleTest/cern_data
                                                  5. Type ./start
                                                  6.  
                                                  7. Answer all questions given by the script Currently, the following directories/files are created:
                                                  8. Line: 76 to 76
                                                     
                                                  9. .../copy_cfgfiles - copy module config files from USBBOARDPATH to QA and test directories
                                                  10. .../run_QA - run modqacern from QA directory (must copy_cfgfiles first!)
                                                  11. .../test_QA - run modqacern from test directory (must copy_cfgfiles first!)
                                                  12. Added:
                                                    >
                                                    >
                                                     
                                                    Added:
                                                    >
                                                    >
                                                    Attention: backup script
                                                    Important: In most cases, running some scripts twice would delete old data. to avoid it, a backup script can be used. Top backup a dir, simply go into it and type backup_me. This will create a new folder with a general name of BACKUP_yyyymmdd_hhmmss and copy or move all files there. The script is interactive and will ask for a short comment (then saved to a backup_info file) and whether to delete old data.
                                                     
                                                    Added:
                                                    >
                                                    >
                                                    Additionally, the following scripts make backups automatically if target directories are not empty:
                                                    • tune_lis
                                                    • tune_lis_advanced
                                                    • run_QA
                                                    • test_QA
                                                     

                                                    Downloading Vdb info and setting Spiroc DACs

                                                    Line: 92 to 103
                                                     
                                                  13. Ground yourself!
                                                  14. Mount spiroc readout to the module usng two M8 screws
                                                  15. Connect SiPM flexes. Handle them with care. Ensure that all connectors are fully pushed in.
                                                  16. Changed:
                                                    <
                                                    <
                                                  17. Connect LIS flex cables.
                                                    <!--The LIS drivers should be connected to USB boards such that ribbon cables are crossing. Actually, they are crossed within the USB box now.-->

                                                    If there's a need to exchange a cable: The flex connectors on the small boards (on white panels) are inverted, i.e., the small flex connector should be connected such that the the flex is bent toward the big connector.
                                                  18. >
                                                    >
                                                  19. Connect LIS flex cables.
                                                  20.  
                                                  21. Install hodoscope on top, close to the centre of the module
                                                  22. Repeat points 3-6 for upper module
                                                  23. Changed:
                                                    <
                                                    <
                                                  24. Switch on both LV PS and HV PS (58.0V), run test_QA script and collect some data to ensure that the system seems to work properly
                                                  25. >
                                                    >
                                                  26. Switch on both LV PS and HV PS (58.0V)
                                                  27. run copy_cfgfiles and then test_QA script and collect some data to ensure that the system seems to work properly
                                                  28.  
                                                    Line: 109 to 118
                                                     
                                                  29. Distribution box: all switches DOWN
                                                  30. Spiroc cards: all switches DOWN
                                                  31. Power Spiroc (LV on)
                                                  32. Changed:
                                                    <
                                                    <
                                                  33. Start a run modqacern module (or any other DAQ program) to initialise Spiroc chips. Run may be stopped after LIS.
                                                  34. >
                                                    >
                                                  35. Start a run with test_QA script to initialize Spiroc chips. Run may be stopped after LIS phase. This step is not needed, if the LV for both modules was not switched off since connectivity test
                                                  36.   CHECKING TOP MODULE:
                                                  37. Distribution box: Ch1 DOWN, Ch2 in CENTRAL position
                                                  38. Switch on HV PS, V=58.0V
                                                  39. Line: 132 to 141
                                                     

                                                    LIS tuning

                                                    Deleted:
                                                    <
                                                    <
                                                    <!-- Option 1: you created directory structure using script (see above)
                                                    -->
                                                     INITIAL STATE: both USB-Box PS ON, HV PS ON, V=58V. Vbd must be calibrated and deltaV=3.5V.
                                                      Changed:
                                                      <
                                                      <
                                                    1. Open terminal, go to right moduleTest/cern_data/FAMxxxxxxX_FAMxxxxxxX directory
                                                    2. Type ./tune_lis
                                                    3. >
                                                      >
                                                    4. Open terminal, go to right moduleTest/cern_data/FAMxxxxxxX_FAMxxxxxxX directory
                                                    5. Type =./tune_lis=
                                                    6.   The configuration will be fetched from a root file generated by initialisation script. You don't need to enter it again.
                                                      Changed:
                                                      <
                                                      <
                                                      Use tune_lis_advanced if there's a need to modify bias currents. This is really an advanced option, so don't use it without understanding.
                                                      >
                                                      >
                                                      Use tune_lis_advanced if there's a need to modify bias currents. This is really an advanced option, so don't use it without understanding.
                                                       
                                                    7. It takes about 30min to calibrate both modules
                                                    8. Changed:
                                                      <
                                                      <
                                                    9. Text files with report will be generated at the end (module_name.lis.txt) and put into lis subdirectory.
                                                    10. Config files will be configured for the last tuned setting and stored in the /cfgFiles
                                                    11. >
                                                      >
                                                    12. Text files with report will be generated at the end (module_name.lis.txt) and put into lis subdirectory.
                                                    13. Config files will be configured for the last tuned setting and stored in the $USBBOARDPATH/cfgFiles.
                                                    14.  
                                                      Deleted:
                                                      <
                                                      <
                                                      <!-- Option 2: independent measurement

                                                      INITIAL STATE: both USB-Box PS ON, HV PS ON. Vbd must be calibrated and deltaV=3.5V.

                                                      1. Go to moduleTest/lis_tuning
                                                      2. Run root tune_lis.c
                                                      3. Answer questions regarding module/LIS numbers and bias currents
                                                      4. Go for coffee
                                                      5. Text files with report will be generated at the end (module_name.lis.txt)
                                                      6. Config files will be configured for the last tuned setting
                                                      If you need to customize the procedure (different settings, using only one module etc.) look at the beginning of tune_lis.c -->
                                                       

                                                      HV scan (Vbd optimization) - optional

                                                      Line: 166 to 160
                                                       

                                                      Cosmics

                                                      Changed:
                                                      <
                                                      <
                                                      Use copy_cfgfiles script to copy board36.cfg and board37.cfg to working folders (QA and TEST).
                                                      >
                                                      >
                                                      Use copy_cfgfiles script to copy board36.cfg and board37.cfg to working folders (QA and test).
                                                        Use run_QA script for starting DAQ software.

                                                      Revision 132019-02-25 - MichalDziewiecki

                                                      Line: 1 to 1
                                                       
                                                      META TOPICPARENT name="UpgradeSciFiTracker"

                                                      SciFi Module Assembly and Quality Assurance tests

                                                      Line: 40 to 40
                                                       
                                                      Hodoscope
                                                      Changed:
                                                      <
                                                      <

                                                      Initialising directory structure for measurements

                                                      >
                                                      >

                                                      General workflow

                                                      One must proceed with all the paragraphs below with their order, so:

                                                      1. Initialize directory structure
                                                      2. Set Spiroc DACs
                                                      3. Perform connectivity test
                                                      4. Tune LIS
                                                      5. Copy config files and run QA for >= 6 hours
                                                      6. Post-process data and put it into archive using relevant scripts

                                                      Initialising directory structure for measurements

                                                        There's a script for creating a directory structure (and some further helpful scripts) for each new measurement session (one side of a module pair).
                                                        Line: 58 to 72
                                                         
                                                      1. .../test/ - a directory for debug cosmic runs
                                                      2. .../tune_lis - a convenience script for running LIS tuning procedure
                                                      3. .../tune_lis_advanced - the same, but allowing for modifying of bias currents. Use with care
                                                      4. Changed:
                                                        <
                                                        <
                                                      5. .../dacfiles_from_db - download Vbd data from database and generate DAC files from them
                                                      6. >
                                                        >
                                                      7. .../dacfiles_from_db - download Vbd data from database and generate DAC files from them under construction...
                                                      8.  
                                                      9. .../copy_cfgfiles - copy module config files from USBBOARDPATH to QA and test directories
                                                      10. Added:
                                                        >
                                                        >
                                                      11. .../run_QA - run modqacern from QA directory (must copy_cfgfiles first!)
                                                      12. .../test_QA - run modqacern from test directory (must copy_cfgfiles first!)
                                                      13.  
                                                        Added:
                                                        >
                                                        >

                                                        Downloading Vdb info and setting Spiroc DACs

                                                         

                                                        Installation and connectivity test

                                                        Line: 76 to 96
                                                          If there's a need to exchange a cable: The flex connectors on the small boards (on white panels) are inverted, i.e., the small flex connector should be connected such that the the flex is bent toward the big connector.
                                                      14. Install hodoscope on top, close to the centre of the module
                                                      15. Repeat points 3-6 for upper module
                                                      16. Added:
                                                        >
                                                        >
                                                      17. Switch on both LV PS and HV PS (58.0V), run test_QA script and collect some data to ensure that the system seems to work properly
                                                      18.  
                                                        Changed:
                                                        <
                                                        <

                                                        Downloading Vdb info and setting Spiroc DACs

                                                        >
                                                        >
                                                         

                                                        Light Tightness Tests

                                                        Line: 139 to 160
                                                         
                                                        
                                                        If you need to customize the procedure (different settings, using only one module etc.) look at the beginning of tune_lis.c -->
                                                        Changed:
                                                        <
                                                        <

                                                        HV scan (Vbd optimization)

                                                        >
                                                        >

                                                        HV scan (Vbd optimization) - optional

                                                         
                                                        Added:
                                                        >
                                                        >
                                                        Currently, this step can be performed only manually.
                                                         

                                                        Cosmics

                                                        Changed:
                                                        <
                                                        <
                                                        Use copy_cfgfiles script to copy board36.cfg and board37.cfg to working folders (QA and TEST). Run in working directory: modqacern module
                                                        >
                                                        >
                                                        Use copy_cfgfiles script to copy board36.cfg and board37.cfg to working folders (QA and TEST).
                                                         
                                                        Added:
                                                        >
                                                        >
                                                        Use run_QA script for starting DAQ software.
                                                         
                                                        Changed:
                                                        <
                                                        <
                                                        setup the prefix for saved root files and click start. Use QA prefic for regular runs.
                                                        >
                                                        >
                                                        setup the prefix for saved root files and click start. Use QA prefix for regular runs.
                                                          Each run consists of 3 parts: Pedestal 1000triggers
                                                        Line: 162 to 184
                                                         Then slick save to save the Summary file.
                                                        Added:
                                                        >
                                                        >

                                                        Data post-processing

                                                         
                                                        Deleted:
                                                        <
                                                        <

                                                        Analysis

                                                         
                                                        Changed:
                                                        <
                                                        <

                                                        Database

                                                        >
                                                        >

                                                        Archiving results

                                                         

                                                        Revision 122019-02-21 - ValeryZhukov

                                                        Line: 1 to 1
                                                         
                                                        META TOPICPARENT name="UpgradeSciFiTracker"

                                                        SciFi Module Assembly and Quality Assurance tests

                                                        Line: 177 to 177
                                                         
                                                        META FILEATTACHMENT attachment="Modassembly_v3.pdf" attr="" comment="ModuleAssembly check list" date="1548697366" name="Modassembly_v3.pdf" path="Modassembly_v3.pdf" size="96150" user="joukov" version="1"
                                                        META FILEATTACHMENT attachment="Modassembly_v4.pdf" attr="" comment="ModuleAssembly check list v4" date="1548777333" name="Modassembly_v4.pdf" path="Modassembly_v4.pdf" size="99207" user="joukov" version="1"
                                                        META FILEATTACHMENT attachment="Modtest_v2.pdf" attr="" comment="" date="1550063093" name="Modtest_v2.pdf" path="Modtest_v2.pdf" size="74863" user="joukov" version="1"
                                                        Added:
                                                        >
                                                        >
                                                        META FILEATTACHMENT attachment="Modtest_v3.pdf" attr="" comment="" date="1550755225" name="Modtest_v3.pdf" path="Modtest_v3.pdf" size="76464" user="joukov" version="1"

                                                        Revision 112019-02-20 - MichalDziewiecki

                                                        Line: 1 to 1
                                                         
                                                        META TOPICPARENT name="UpgradeSciFiTracker"

                                                        SciFi Module Assembly and Quality Assurance tests

                                                        Line: 50 to 50
                                                          Currently, the following directories/files are created:
                                                          Changed:
                                                          <
                                                          <
                                                        • .../config.txt - a summary file with entered module data
                                                        • .../config.root - the same as root tree
                                                        • .../vbd/ - a directory for all breakdown-related stuff
                                                        • .../lis/ - a directory for LIS tuning results
                                                        • .../QA/ - a directory for cosmic data and results
                                                        • .../test/ - a directory for debug cosmic runs
                                                        • .../tune_lis - a convenience script for running LIS tuning procedure
                                                        • .../tune_lis_advanced - the same, but allowing for modifying of bias currents. Use with care
                                                        • .../dacfiles_from_db - download Vbd data from database and generate DAC files from them
                                                        • >
                                                          >
                                                        • .../config.txt - a summary file with entered module data
                                                        • .../config.root - the same as root tree
                                                        • .../vbd/ - a directory for all breakdown-related stuff
                                                        • .../lis/ - a directory for LIS tuning results
                                                        • .../QA/ - a directory for cosmic data and results
                                                        • .../test/ - a directory for debug cosmic runs
                                                        • .../tune_lis - a convenience script for running LIS tuning procedure
                                                        • .../tune_lis_advanced - the same, but allowing for modifying of bias currents. Use with care
                                                        • .../dacfiles_from_db - download Vbd data from database and generate DAC files from them
                                                        • .../copy_cfgfiles - copy module config files from USBBOARDPATH to QA and test directories
                                                        •  

                                                          Installation and connectivity test

                                                            Added:
                                                            >
                                                            >
                                                          1. Ensure that both LV and HV power supplies are off!
                                                          2.  
                                                          3. Remove previous modules from the bench. Move hodoscope beneath the modules on the shell, carefully (with HV on)
                                                          4. Install a new module on down position, ensure module position and flatness.
                                                          5. Ground yourself!
                                                          6. Line: 76 to 78
                                                             
                                                          7. Repeat points 3-6 for upper module
                                                          8. Added:
                                                            >
                                                            >

                                                            Downloading Vdb info and setting Spiroc DACs

                                                             

                                                            Light Tightness Tests

                                                            INITIAL STATE: both USB-Box PS ON, HV PS OFF
                                                              Line: 86 to 91
                                                               
                                                            1. Start a run modqacern module (or any other DAQ program) to initialise Spiroc chips. Run may be stopped after LIS.
                                                              CHECKING TOP MODULE:
                                                            2. Distribution box: Ch1 DOWN, Ch2 in CENTRAL position
                                                            3. Changed:
                                                              <
                                                              <
                                                            4. Switch on HV PS
                                                            5. >
                                                              >
                                                            6. Switch on HV PS, V=58.0V
                                                            7.  
                                                            8. Wait until readout stabilises, then write down current from multimeter
                                                            9. Switch multimeter to relative mode
                                                            10. Switch on bright lamp, 'scan' coldbox and connections to the module, write down highest current
                                                            11. Line: 104 to 109
                                                                Ready for cosmic tests
                                                              Deleted:
                                                              <
                                                              <

                                                              HV scan

                                                               

                                                              LIS tuning

                                                              Deleted:
                                                              <
                                                              <
                                                               
                                                              <!-- Option 1: you created directory structure using script (see above)
                                                              -->
                                                              Changed:
                                                              <
                                                              <
                                                              INITIAL STATE: both USB-Box PS ON, HV PS ON.
                                                              >
                                                              >
                                                              INITIAL STATE: both USB-Box PS ON, HV PS ON, V=58V.
                                                               Vbd must be calibrated and deltaV=3.5V.
                                                              1. Open terminal, go to right moduleTest/cern_data/FAMxxxxxxX_FAMxxxxxxX directory
                                                              Line: 137 to 139
                                                               
                                                              
                                                              If you need to customize the procedure (different settings, using only one module etc.) look at the beginning of tune_lis.c -->
                                                              Added:
                                                              >
                                                              >

                                                              HV scan (Vbd optimization)

                                                               

                                                              Cosmics

                                                              Changed:
                                                              <
                                                              <
                                                              Copy board36.cfg and board37.cfg to working folder. Run in working directory:
                                                              >
                                                              >
                                                              Use copy_cfgfiles script to copy board36.cfg and board37.cfg to working folders (QA and TEST). Run in working directory:
                                                                modqacern module
                                                              Changed:
                                                              <
                                                              <
                                                              setup the prefix for saved root files and click start.
                                                              >
                                                              >
                                                              setup the prefix for saved root files and click start. Use QA prefic for regular runs.
                                                                Each run consists of 3 parts: Pedestal 1000triggers

                                                              Revision 102019-02-19 - MichalDziewiecki

                                                              Line: 1 to 1
                                                               
                                                              META TOPICPARENT name="UpgradeSciFiTracker"

                                                              SciFi Module Assembly and Quality Assurance tests

                                                              Line: 54 to 54
                                                               
                                                            12. .../config.root - the same as root tree
                                                            13. .../vbd/ - a directory for all breakdown-related stuff
                                                            14. .../lis/ - a directory for LIS tuning results
                                                            15. Changed:
                                                              <
                                                              <
                                                            16. .../cosmic/ - a directory for cosmic data and results
                                                            17. >
                                                              >
                                                            18. .../QA/ - a directory for cosmic data and results
                                                            19. .../test/ - a directory for debug cosmic runs
                                                            20.  
                                                            21. .../tune_lis - a convenience script for running LIS tuning procedure
                                                            22. Added:
                                                              >
                                                              >
                                                            23. .../tune_lis_advanced - the same, but allowing for modifying of bias currents. Use with care
                                                            24. .../dacfiles_from_db - download Vbd data from database and generate DAC files from them
                                                            25.  
                                                              Line: 64 to 67
                                                               
                                                              1. Remove previous modules from the bench. Move hodoscope beneath the modules on the shell, carefully (with HV on)
                                                              2. Install a new module on down position, ensure module position and flatness.
                                                              Changed:
                                                              <
                                                              <
                                                            26. install hodoscope on top, close to the centre of the module
                                                            27. >
                                                              >
                                                            28. Ground yourself!
                                                            29. Mount spiroc readout to the module usng two M8 screws
                                                            30. Connect SiPM flexes. Handle them with care. Ensure that all connectors are fully pushed in.
                                                            31. Connect LIS flex cables.
                                                              <!--The LIS drivers should be connected to USB boards such that ribbon cables are crossing. Actually, they are crossed within the USB box now.-->

                                                              If there's a need to exchange a cable: The flex connectors on the small boards (on white panels) are inverted, i.e., the small flex connector should be connected such that the the flex is bent toward the big connector.
                                                            32. Install hodoscope on top, close to the centre of the module
                                                            33. Repeat points 3-6 for upper module
                                                            34.  
                                                              Deleted:
                                                              <
                                                              <
                                                               

                                                              Light Tightness Tests

                                                              INITIAL STATE: both USB-Box PS ON, HV PS OFF
                                                                Line: 98 to 107
                                                                 

                                                                HV scan

                                                                LIS tuning

                                                                Deleted:
                                                                <
                                                                <
                                                                The LIS drivers should be connected to USB boards such that ribbon cables are crossing. The flex connectors on the small boards are inverted, i.e., the small flex connector should be connected such that the the flex is bent toward the big connector
                                                                 
                                                                Changed:
                                                                <
                                                                <
                                                                Option 1: you created directory structure using script (see above)
                                                                >
                                                                >
                                                                <!-- Option 1: you created directory structure using script (see above)
                                                                -->
                                                                  INITIAL STATE: both USB-Box PS ON, HV PS ON. Vbd must be calibrated and deltaV=3.5V.
                                                                1. Open terminal, go to right moduleTest/cern_data/FAMxxxxxxX_FAMxxxxxxX directory
                                                                Changed:
                                                                <
                                                                <
                                                              1. Type ./tune_lis
                                                                The configuration will be fetched from a root file generated by initialisation script. You don't need to enter it again.
                                                              2. >
                                                                >
                                                              3. Type ./tune_lis
                                                                The configuration will be fetched from a root file generated by initialisation script. You don't need to enter it again.
                                                                Use tune_lis_advanced if there's a need to modify bias currents. This is really an advanced option, so don't use it without understanding.
                                                              4.  
                                                              5. It takes about 30min to calibrate both modules
                                                              6. Text files with report will be generated at the end (module_name.lis.txt) and put into lis subdirectory.
                                                              7. Config files will be configured for the last tuned setting and stored in the /cfgFiles
                                                              8. Changed:
                                                                <
                                                                <
                                                                Option 2: independent measurement
                                                                >
                                                                >
                                                                <!-- Option 2: independent measurement
                                                                  INITIAL STATE: both USB-Box PS ON, HV PS ON. Vbd must be calibrated and deltaV=3.5V.
                                                                Line: 125 to 135
                                                                 
                                                              9. Text files with report will be generated at the end (module_name.lis.txt)
                                                              10. Config files will be configured for the last tuned setting
                                                              11. Changed:
                                                                <
                                                                <
                                                                If you need to customize the procedure (different settings, using only one module etc.) look at the beginning of tune_lis.c
                                                                >
                                                                >
                                                                If you need to customize the procedure (different settings, using only one module etc.) look at the beginning of tune_lis.c -->
                                                                 

                                                                Cosmics

                                                                Revision 92019-02-15 - ValeryZhukov

                                                                Line: 1 to 1
                                                                 
                                                                META TOPICPARENT name="UpgradeSciFiTracker"

                                                                SciFi Module Assembly and Quality Assurance tests

                                                                Line: 129 to 129
                                                                 

                                                                Cosmics

                                                                Added:
                                                                >
                                                                >
                                                                Copy board36.cfg and board37.cfg to working folder. Run in working directory: modqacern module

                                                                setup the prefix for saved root files and click start.

                                                                Each run consists of 3 parts: Pedestal 1000triggers LIS run 8000triggers Cosmic 30min

                                                                During the run 3 trees are filled in the corresponding root file with the name prefix_unixtime_data_time.root Also the selected tree for events with only 1 hit in one module is stored in the dualtree_unixtime.root file.

                                                                Then new run is started automatically. The running can be stopped by clicking stop. Then slick save to save the Summary file.

                                                                 

                                                                Analysis

                                                                Revision 82019-02-13 - ValeryZhukov

                                                                Line: 1 to 1
                                                                 
                                                                META TOPICPARENT name="UpgradeSciFiTracker"

                                                                SciFi Module Assembly and Quality Assurance tests

                                                                Line: 143 to 143
                                                                 
                                                                META FILEATTACHMENT attachment="Modassembly_v3.pdf" attr="" comment="ModuleAssembly check list" date="1548697366" name="Modassembly_v3.pdf" path="Modassembly_v3.pdf" size="96150" user="joukov" version="1"
                                                                META FILEATTACHMENT attachment="Modassembly_v4.pdf" attr="" comment="ModuleAssembly check list v4" date="1548777333" name="Modassembly_v4.pdf" path="Modassembly_v4.pdf" size="99207" user="joukov" version="1"
                                                                Added:
                                                                >
                                                                >
                                                                META FILEATTACHMENT attachment="Modtest_v2.pdf" attr="" comment="" date="1550063093" name="Modtest_v2.pdf" path="Modtest_v2.pdf" size="74863" user="joukov" version="1"

                                                                Revision 72019-02-11 - ValeryZhukov

                                                                Line: 1 to 1
                                                                 
                                                                META TOPICPARENT name="UpgradeSciFiTracker"

                                                                SciFi Module Assembly and Quality Assurance tests

                                                                Line: 40 to 40
                                                                 
                                                                Hodoscope
                                                                Changed:
                                                                <
                                                                <

                                                                >>> Initializing directory structure for measurements <<<

                                                                >
                                                                >

                                                                Initialising directory structure for measurements

                                                                  There's a script for creating a directory structure (and some further helpful scripts) for each new measurement session (one side of a module pair).
                                                                  Line: 61 to 61
                                                                   

                                                                  Installation and connectivity test

                                                                  Added:
                                                                  >
                                                                  >
                                                                  1. Remove previous modules from the bench. Move hodoscope beneath the modules on the shell, carefully (with HV on)
                                                                  2. Install a new module on down position, ensure module position and flatness.
                                                                  3. install hodoscope on top, close to the centre of the module

                                                                   

                                                                  Light Tightness Tests

                                                                  INITIAL STATE: both USB-Box PS ON, HV PS OFF
                                                                    Line: 68 to 74
                                                                     
                                                                  1. Distribution box: all switches DOWN
                                                                  2. Spiroc cards: all switches DOWN
                                                                  3. Power Spiroc (LV on)
                                                                  4. Changed:
                                                                    <
                                                                    <
                                                                  5. Start a run modqacern module (or any other DAQ program) to initialize Spiroc chips. Run may be stopped after LIS.
                                                                  6. >
                                                                    >
                                                                  7. Start a run modqacern module (or any other DAQ program) to initialise Spiroc chips. Run may be stopped after LIS.
                                                                  8.   CHECKING TOP MODULE:
                                                                  9. Distribution box: Ch1 DOWN, Ch2 in CENTRAL position
                                                                  10. Switch on HV PS
                                                                  11. Line: 92 to 98
                                                                     

                                                                    HV scan

                                                                    LIS tuning

                                                                    Added:
                                                                    >
                                                                    >
                                                                    The LIS drivers should be connected to USB boards such that ribbon cables are crossing. The flex connectors on the small boards are inverted, i.e., the small flex connector should be connected such that the the flex is bent toward the big connector
                                                                      Option 1: you created directory structure using script (see above)
                                                                    Line: 100 to 107
                                                                     
                                                                    1. Open terminal, go to right moduleTest/cern_data/FAMxxxxxxX_FAMxxxxxxX directory
                                                                    2. Type ./tune_lis
                                                                    Changed:
                                                                    <
                                                                    <
                                                                    The configuration will be fetched from a root file generated by initialization script. Yo don't need to enter it again.
                                                                  12. Go for coffee
                                                                  13. >
                                                                    >
                                                                    The configuration will be fetched from a root file generated by initialisation script. You don't need to enter it again.
                                                                  14. It takes about 30min to calibrate both modules
                                                                  15.  
                                                                  16. Text files with report will be generated at the end (module_name.lis.txt) and put into lis subdirectory.
                                                                  17. Changed:
                                                                    <
                                                                    <
                                                                  18. Config files will be configured for the last tuned setting
                                                                  19. >
                                                                    >
                                                                  20. Config files will be configured for the last tuned setting and stored in the /cfgFiles
                                                                  21.  

                                                                    Option 2: independent measurement

                                                                    Revision 62019-02-11 - MichalDziewiecki

                                                                    Line: 1 to 1
                                                                     
                                                                    META TOPICPARENT name="UpgradeSciFiTracker"

                                                                    SciFi Module Assembly and Quality Assurance tests

                                                                    Line: 40 to 40
                                                                     
                                                                    Hodoscope
                                                                    Added:
                                                                    >
                                                                    >

                                                                    >>> Initializing directory structure for measurements <<<

                                                                    There's a script for creating a directory structure (and some further helpful scripts) for each new measurement session (one side of a module pair).

                                                                    1. Open terminal. Go to moduleTest/cern_data
                                                                    2. Type ./start
                                                                    3. Answer all questions given by the script
                                                                    Currently, the following directories/files are created:
                                                                    • .../config.txt - a summary file with entered module data
                                                                    • .../config.root - the same as root tree
                                                                    • .../vbd/ - a directory for all breakdown-related stuff
                                                                    • .../lis/ - a directory for LIS tuning results
                                                                    • .../cosmic/ - a directory for cosmic data and results
                                                                    • .../tune_lis - a convenience script for running LIS tuning procedure
                                                                     

                                                                    Installation and connectivity test

                                                                    Line: 50 to 68
                                                                     
                                                                  22. Distribution box: all switches DOWN
                                                                  23. Spiroc cards: all switches DOWN
                                                                  24. Power Spiroc (LV on)
                                                                  25. Changed:
                                                                    <
                                                                    <
                                                                  26. Start a run modqacern module (or any other DAQ program) to initialize Spiroc chips. Run may be stopped after LIS.
                                                                  27. CHECKING TOP MODULE: Distribution box: Ch1 DOWN, Ch2 in CENTRAL position
                                                                  28. >
                                                                    >
                                                                  29. Start a run modqacern module (or any other DAQ program) to initialize Spiroc chips. Run may be stopped after LIS.
                                                                    CHECKING TOP MODULE:
                                                                  30. Distribution box: Ch1 DOWN, Ch2 in CENTRAL position
                                                                  31.  
                                                                  32. Switch on HV PS
                                                                  33. Wait until readout stabilises, then write down current from multimeter
                                                                  34. Switch multimeter to relative mode
                                                                  35. Line: 59 to 78
                                                                      < 5 uA: OK
                                                                    5-15 uA: Not critical, but try to locate the leak and leave a comment
                                                                    > 15uA: locate and repair the leak, leave a comment
                                                                    Changed:
                                                                    <
                                                                    <
                                                                  36. Switch off lamp, switch off HV, meter back from relative to normal mode
                                                                  37. CHECKING BOTTOM MODULE: Distribution box: Ch1 in CENTRAL position, Ch2 DOWN
                                                                  38. Repeat 6-10
                                                                  39. SWITCH BACK: ENSURE THAT HV IS OFF!
                                                                  40. >
                                                                    >
                                                                  41. Switch off lamp, switch off HV, meter back from relative to normal mode
                                                                    CHECKING BOTTOM MODULE:
                                                                  42. Distribution box: Ch1 in CENTRAL position, Ch2 DOWN
                                                                  43. Repeat 6-11
                                                                    SWITCH BACK:
                                                                  44. ENSURE THAT HV IS OFF!
                                                                  45.  
                                                                  46. Distribution box: all switches UP
                                                                  47. Spiroc cards: all switches UP
                                                                  48. Line: 71 to 92
                                                                     

                                                                    HV scan

                                                                    LIS tuning

                                                                    Added:
                                                                    >
                                                                    >
                                                                    Option 1: you created directory structure using script (see above)

                                                                    INITIAL STATE: both USB-Box PS ON, HV PS ON. Vbd must be calibrated and deltaV=3.5V.

                                                                    1. Open terminal, go to right moduleTest/cern_data/FAMxxxxxxX_FAMxxxxxxX directory
                                                                    2. Type ./tune_lis
                                                                      The configuration will be fetched from a root file generated by initialization script. Yo don't need to enter it again.
                                                                    3. Go for coffee
                                                                    4. Text files with report will be generated at the end (module_name.lis.txt) and put into lis subdirectory.
                                                                    5. Config files will be configured for the last tuned setting

                                                                    Option 2: independent measurement

                                                                     INITIAL STATE: both USB-Box PS ON, HV PS ON. Vbd must be calibrated and deltaV=3.5V.
                                                                    1. Go to moduleTest/lis_tuning
                                                                    Changed:
                                                                    <
                                                                    <
                                                                  49. run root tune_lis.c
                                                                  50. >
                                                                    >
                                                                  51. Run root tune_lis.c
                                                                  52.  
                                                                  53. Answer questions regarding module/LIS numbers and bias currents
                                                                  54. Go for coffee
                                                                  55. Text files with report will be generated at the end (module_name.lis.txt)
                                                                  56. Revision 52019-02-06 - ValeryZhukov

                                                                    Line: 1 to 1
                                                                     
                                                                    META TOPICPARENT name="UpgradeSciFiTracker"

                                                                    SciFi Module Assembly and Quality Assurance tests

                                                                    Line: 7 to 7
                                                                     

                                                                    Access and Contacts

                                                                    Grey Room in LHCB Hall
                                                                    Added:
                                                                    >
                                                                    >
                                                                    ask for key's LHCb secretariat.
                                                                     

                                                                    Valery Zhukov joukov@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 78188 Cell(CERN): +41 76 487 6537
                                                                    Line: 14 to 16
                                                                     

                                                                    Info and Links

                                                                    Deleted:
                                                                    <
                                                                    <
                                                                    recent talks:
                                                                     
                                                                    Added:
                                                                    >
                                                                    >
                                                                    ELOG:SciFi:Module elog

                                                                    Talks:

                                                                     

                                                                    Module Assembly

                                                                    GasTightness Test

                                                                    Module Testing in Cosmic Bench

                                                                    Changed:
                                                                    <
                                                                    <

                                                                    Installation

                                                                    >
                                                                    >
                                                                    Cosmic bench PC(ask for pass): lhcb-cern@lhcbscifiNOSPAMPLEASE.dyndns.cern.ch

                                                                    SPIROC DAQ

                                                                    Software

                                                                    Hodoscope

                                                                    Installation and connectivity test

                                                                     

                                                                    Light Tightness Tests

                                                                    INITIAL STATE: both USB-Box PS ON, HV PS OFF
                                                                    Line: 31 to 49
                                                                     
                                                                  57. Connect multimeter (uA input) to banana cables from HV distribution box.
                                                                  58. Distribution box: all switches DOWN
                                                                  59. Spiroc cards: all switches DOWN
                                                                  60. Changed:
                                                                    <
                                                                    <
                                                                  61. Start a run in strosmic90 (or any other DAQ program) to initialize Spiroc chips. Run may be stopped then (don't need to run during test).
                                                                  62. >
                                                                    >
                                                                  63. Power Spiroc (LV on)
                                                                  64. Start a run modqacern module (or any other DAQ program) to initialize Spiroc chips. Run may be stopped after LIS.
                                                                  65.  
                                                                  66. CHECKING TOP MODULE: Distribution box: Ch1 DOWN, Ch2 in CENTRAL position
                                                                  67. Switch on HV PS
                                                                  68. Changed:
                                                                    <
                                                                    <
                                                                  69. Wait until readout stabilizes, then write down current from multimeter
                                                                  70. >
                                                                    >
                                                                  71. Wait until readout stabilises, then write down current from multimeter
                                                                  72.  
                                                                  73. Switch multimeter to relative mode
                                                                  74. Changed:
                                                                    <
                                                                    <
                                                                  75. Switch on LED lamp, 'scan' coldbox and connections to the module, write down highest current
                                                                  76. >
                                                                    >
                                                                  77. Switch on bright lamp, 'scan' coldbox and connections to the module, write down highest current
                                                                  78.   < 5 uA: OK
                                                                    5-15 uA: Not critical, but try to locate the leak and leave a comment
                                                                    > 15uA: locate and repair the leak, leave a comment
                                                                    Line: 47 to 66
                                                                     
                                                                  79. Distribution box: all switches UP
                                                                  80. Spiroc cards: all switches UP
                                                                  81. Added:
                                                                    >
                                                                    >
                                                                    Ready for cosmic tests
                                                                     

                                                                    HV scan

                                                                    Revision 42019-02-06 - MichalDziewiecki

                                                                    Line: 1 to 1
                                                                     
                                                                    META TOPICPARENT name="UpgradeSciFiTracker"

                                                                    SciFi Module Assembly and Quality Assurance tests

                                                                    Line: 26 to 26
                                                                     

                                                                    Installation

                                                                    Light Tightness Tests

                                                                    Changed:
                                                                    <
                                                                    <
                                                                    >
                                                                    >
                                                                    INITIAL STATE: both USB-Box PS ON, HV PS OFF
                                                                    1. Connect multimeter (uA input) to banana cables from HV distribution box.
                                                                    2. Distribution box: all switches DOWN
                                                                    3. Spiroc cards: all switches DOWN
                                                                    4. Start a run in strosmic90 (or any other DAQ program) to initialize Spiroc chips. Run may be stopped then (don't need to run during test).
                                                                    5. CHECKING TOP MODULE: Distribution box: Ch1 DOWN, Ch2 in CENTRAL position
                                                                    6. Switch on HV PS
                                                                    7. Wait until readout stabilizes, then write down current from multimeter
                                                                    8. Switch multimeter to relative mode
                                                                    9. Switch on LED lamp, 'scan' coldbox and connections to the module, write down highest current
                                                                      < 5 uA: OK
                                                                      5-15 uA: Not critical, but try to locate the leak and leave a comment
                                                                      > 15uA: locate and repair the leak, leave a comment
                                                                    10. Switch off lamp, switch off HV, meter back from relative to normal mode
                                                                    11. CHECKING BOTTOM MODULE: Distribution box: Ch1 in CENTRAL position, Ch2 DOWN
                                                                    12. Repeat 6-10
                                                                    13. SWITCH BACK: ENSURE THAT HV IS OFF!
                                                                    14. Distribution box: all switches UP
                                                                    15. Spiroc cards: all switches UP
                                                                     

                                                                    HV scan

                                                                    LIS tuning

                                                                    Added:
                                                                    >
                                                                    >
                                                                    INITIAL STATE: both USB-Box PS ON, HV PS ON. Vbd must be calibrated and deltaV=3.5V.
                                                                    1. Go to moduleTest/lis_tuning
                                                                    2. run root tune_lis.c
                                                                    3. Answer questions regarding module/LIS numbers and bias currents
                                                                    4. Go for coffee
                                                                    5. Text files with report will be generated at the end (module_name.lis.txt)
                                                                    6. Config files will be configured for the last tuned setting
                                                                    If you need to customize the procedure (different settings, using only one module etc.) look at the beginning of tune_lis.c
                                                                     

                                                                    Cosmics

                                                                    Revision 32019-02-04 - ValeryZhukov

                                                                    Line: 1 to 1
                                                                     
                                                                    META TOPICPARENT name="UpgradeSciFiTracker"
                                                                    Changed:
                                                                    <
                                                                    <

                                                                    SciFi Module Assembly and Quality Assurance tests

                                                                    >
                                                                    >

                                                                    SciFi Module Assembly and Quality Assurance tests

                                                                    Access and Contacts

                                                                    Grey Room in LHCB Hall

                                                                    Valery Zhukov joukov@cernNOSPAMPLEASE.ch Office: +41 (0)22 76 78188 Cell(CERN): +41 76 487 6537
                                                                    Andreas Guth   Office: Cell(CERN):

                                                                    Info and Links

                                                                    recent talks:

                                                                    Module Assembly

                                                                    GasTightness Test

                                                                    Module Testing in Cosmic Bench

                                                                    Installation

                                                                    Light Tightness Tests

                                                                    HV scan

                                                                    LIS tuning

                                                                    Cosmics

                                                                    Analysis

                                                                    Database

                                                                     

                                                                    -- ValeryZhukov - 2019-01-28

                                                                    Revision 22019-01-29 - ValeryZhukov

                                                                    Line: 1 to 1
                                                                     
                                                                    META TOPICPARENT name="UpgradeSciFiTracker"

                                                                    SciFi Module Assembly and Quality Assurance tests

                                                                    Line: 6 to 6
                                                                     -- ValeryZhukov - 2019-01-28

                                                                    META FILEATTACHMENT attachment="Modassembly_v3.pdf" attr="" comment="ModuleAssembly check list" date="1548697366" name="Modassembly_v3.pdf" path="Modassembly_v3.pdf" size="96150" user="joukov" version="1"
                                                                    Added:
                                                                    >
                                                                    >
                                                                    META FILEATTACHMENT attachment="Modassembly_v4.pdf" attr="" comment="ModuleAssembly check list v4" date="1548777333" name="Modassembly_v4.pdf" path="Modassembly_v4.pdf" size="99207" user="joukov" version="1"

                                                                    Revision 12019-01-28 - ValeryZhukov

                                                                    Line: 1 to 1
                                                                    Added:
                                                                    >
                                                                    >
                                                                    META TOPICPARENT name="UpgradeSciFiTracker"

                                                                    SciFi Module Assembly and Quality Assurance tests

                                                                    -- ValeryZhukov - 2019-01-28

                                                                    META FILEATTACHMENT attachment="Modassembly_v3.pdf" attr="" comment="ModuleAssembly check list" date="1548697366" name="Modassembly_v3.pdf" path="Modassembly_v3.pdf" size="96150" user="joukov" version="1"
                                                                     
                                                                    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