Difference: LHCbDetectorAlignmentDatabases (1 vs. 16)

Revision 162010-04-27 - WouterHulsbergen

Line: 1 to 1
 
META TOPICPARENT name="LHCbDetectorAlignment"
Line: 14 to 14
  The latest constants for field on and off are:
Changed:
<
<
  • LATEST FIELD ON: v2.2.db
    • Nickname: v2.2
>
>
  • LATEST FIELD ON: v3.0.db
    • Tag: not yet tagged
    • Description: fixes the velo half alignment, realigns TT, IT and OT * Velo-halves: Tx, Ty, Rx, Ry with millepede * TT-modules, IT ladders, OT modules

  • LATEST FIELD ON: v2.3.db
 
    • Tag: align-20100302
Changed:
<
<
    • Description: like v2.1 but without the realignment of Ty for IT boxes. this solves a problem in the IT overlaps.
>
>
    • Description: like v2.2 but fixing the TT pitch
 
  • LATEST FIELD OFF: v1.3.db
    • Nickname: v1.3
Line: 90 to 95
 
    • Tag: not yet uploaded
    • Description: like above, but adding IT ladder and OT modules (both Tx and Rz). This databases gives a few % improvement in the residuals in IT and OT.
Added:
>
>
* v2.2.db
    • Tag: align-20100302
    • Description: like v2.1 but without the realignment of Ty for IT boxes. this solves a problem in the IT overlaps.
 
  • alignment of IT boxes using TED data
    • input: TED2 data

Revision 152010-03-13 - WouterHulsbergen

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

Alignment constants for first data

Added:
>
>
Note: most of the sets with alignment constants below can be found in /afs/cern.ch/user/w/wouter/public/AlignDB. To load a particular set, use the following:
     from Configurables import ( CondDB, CondDBAccessSvc )
     alignDBLayer = CondDBAccessSvc( 'AlignDBLayer' )
     alignDBLayer.ConnectionString ='sqlite_file:/afs/cern.ch/user/w/wouter/public/AlignDB/v2.2.dbLHCBCOND'
     CondDB().addLayer( alignDBLayer )

The latest constants for field on and off are:

  • LATEST FIELD ON: v2.2.db
    • Nickname: v2.2
    • Tag: align-20100302
    • Description: like v2.1 but without the realignment of Ty for IT boxes. this solves a problem in the IT overlaps.

  • LATEST FIELD OFF: v1.3.db
    • Nickname: v1.3
    • Tag: align-20100302-moff
    • Description: uses the IT ladder / OT module alignment of v2.2, but realigns the boxes and C-frames just as for v1.2. This gives slightly better residuals in IT and OT.

Below are older databases.

 
  • VeloOTTxTyModulesTxITTxTyRzTTTxFieldOff_20100115.db
    • Nickname: v1.0
    • Tag: LHCBCOND align-20100115
Line: 50 to 74
  a bit closer to the ideal geometry. This database isn't really any better than the previous but was the starting point for the magnet-on alignments. it works poorer on magnet-on data.
Deleted:
<
<
  • v1.3.db
    • Nickname: v1.3
    • Description: uses the IT ladder / OT module alignment of v2.2, but realigns the boxes and C-frames just as for v1.2. This gives slightly better residuals in IT and OT.
 
  • VeloOTTxTyTzModulesTxITTxTyTzRxRyRzTTTxTTLaddersFieldOn_20100211.db
    • Nickname: v2.0
    • Tag: not yet uploaded
Line: 70 to 90
 
    • Tag: not yet uploaded
    • Description: like above, but adding IT ladder and OT modules (both Tx and Rz). This databases gives a few % improvement in the residuals in IT and OT.
Deleted:
<
<
  • v2.2.db
    • Nickname: v2.2
    • Tag: not yet uploaded
    • Description: like v2.1 but without the realignment of Ty for IT boxes. this solves a problem in the IT overlaps.
 
  • alignment of IT boxes using TED data
    • input: TED2 data

Revision 142010-02-22 - WouterHulsbergen

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

Alignment constants for first data

  • VeloOTTxTyModulesTxITTxTyRzTTTxFieldOff_20100115.db
Changed:
<
<
    • Nickname: v1.0
>
>
    • Nickname: v1.0
 
    • Tag: LHCBCOND align-20100115
    • Data-set: run 63596
    • IOV: [23/11/2009 - Infty]
Line: 19 to 19
 
      • OT-CFrames Tx, Ty
      • OT-Modules Tx
  • VeloOTTxTyModulesTxITTxTyRzTTTxFieldOffTTLaddersFieldOn_20100122.db
Changed:
<
<
    • Nickname: v1.1
>
>
    • Nickname: v1.1
 
    • Tag: LHCBCOND tt-20100129
    • Data-set: run 63596 and some magnet on data
    • IOV: [23/11/2009 - Infty]
Line: 32 to 32
 
      • take resulting TT module alignment, and fix TT global parameters on field-of run 63596 The resulting database only differes from 20100115 in the TT alignment.
  • VeloOTTxTyTzModulesTxITTxTyTzRyRzTTTxFieldOffTTLaddersFieldOn_20100205.db
Changed:
<
<
    • Nickname: v1.2
>
>
    • Nickname: v1.2
 
    • Tag: not for release
    • Description: same as above, but now adding more degrees of freedom:
      • Velo-global Rx
Line: 50 to 50
  a bit closer to the ideal geometry. This database isn't really any better than the previous but was the starting point for the magnet-on alignments. it works poorer on magnet-on data.
Added:
>
>
  • v1.3.db
    • Nickname: v1.3
    • Description: uses the IT ladder / OT module alignment of v2.2, but realigns the boxes and C-frames just as for v1.2. This gives slightly better residuals in IT and OT.
 
  • VeloOTTxTyTzModulesTxITTxTyTzRxRyRzTTTxTTLaddersFieldOn_20100211.db
Changed:
<
<
    • Nickname: v2.0
>
>
    • Nickname: v2.0
 
    • Tag: not yet uploaded
    • Description: this is the first FIELD-ON alignment. On field-on data this database gives 30% better IT residual distribution, better overlap between IT stacks, and better matching between T and Velo, and T and CALO,
Line: 62 to 66
 
      • TT-halfmodules: Tx
        IT and OT were fixed in T3
  • VeloOTTxTyTzModulesTxRzITTxTyTzRyRzITLaddersTxRzTTTxOffTTLaddersFieldOn_20100212.db
Changed:
<
<
    • Nickname: v2.1
>
>
    • Nickname: v2.1
 
    • Tag: not yet uploaded
    • Description: like above, but adding IT ladder and OT modules (both Tx and Rz). This databases gives a few % improvement in the residuals in IT and OT.
Added:
>
>
  • v2.2.db
    • Nickname: v2.2
    • Tag: not yet uploaded
    • Description: like v2.1 but without the realignment of Ty for IT boxes. this solves a problem in the IT overlaps.
 
  • alignment of IT boxes using TED data
    • input: TED2 data
    • parameters:

Revision 132010-02-13 - WouterHulsbergen

Line: 1 to 1
 
META TOPICPARENT name="LHCbDetectorAlignment"
Line: 61 to 61
 
      • TT: Tx Ty Tz
      • TT-halfmodules: Tx
        IT and OT were fixed in T3
Changed:
<
<
  • VeloOTTxTyTzModulesTxITTxTyTzRyRzITLaddersTxRzTTTxOffTTLaddersFieldOn_20100212.db
>
>
  • VeloOTTxTyTzModulesTxRzITTxTyTzRyRzITLaddersTxRzTTTxOffTTLaddersFieldOn_20100212.db
 
    • Nickname: v2.1
    • Tag: not yet uploaded
Changed:
<
<
    • Description: like above, but adding IT ladder and OT modules.
>
>
    • Description: like above, but adding IT ladder and OT modules (both Tx and Rz). This databases gives a few % improvement in the residuals in IT and OT.
 
  • alignment of IT boxes using TED data
    • input: TED2 data
    • parameters:

Revision 122010-02-12 - WouterHulsbergen

Line: 1 to 1
 
META TOPICPARENT name="LHCbDetectorAlignment"
Line: 33 to 33
  The resulting database only differes from 20100115 in the TT alignment.
  • VeloOTTxTyTzModulesTxITTxTyTzRyRzTTTxFieldOffTTLaddersFieldOn_20100205.db
    • Nickname: v1.2
Changed:
<
<
    • Tag: not yet uploaded
>
>
    • Tag: not for release
 
    • Description: same as above, but now adding more degrees of freedom:
      • Velo-global Rx
      • Velo-right-half Ry
Line: 46 to 46
 
      • TT-halflayers Tx
      • TT-Boxes Tx
        Furthermore, the OT survey was fixed for the bowing of the bridge that was measured
Changed:
<
<
in the IT survey. This database gives better IT residuals in field-off data than the previous alignment. However,
>
>
in the IT survey. Also the errors on the OT module survey were tightened in order to stay a bit closer to the ideal geometry. This database isn't really any better than the previous but was the starting point for the magnet-on alignments.
  it works poorer on magnet-on data.
  • VeloOTTxTyTzModulesTxITTxTyTzRxRyRzTTTxTTLaddersFieldOn_20100211.db
    • Nickname: v2.0

Revision 112010-02-12 - WouterHulsbergen

Line: 1 to 1
 
META TOPICPARENT name="LHCbDetectorAlignment"
Line: 46 to 46
 
      • TT-halflayers Tx
      • TT-Boxes Tx
        Furthermore, the OT survey was fixed for the bowing of the bridge that was measured
Changed:
<
<
in the IT survey. This database gives better IT residuals in field-off data than the previous alignment.
>
>
in the IT survey. This database gives better IT residuals in field-off data than the previous alignment. However, it works poorer on magnet-on data.
 
  • VeloOTTxTyTzModulesTxITTxTyTzRxRyRzTTTxTTLaddersFieldOn_20100211.db
    • Nickname: v2.0
    • Tag: not yet uploaded

Revision 102010-02-12 - WouterHulsbergen

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

Alignment constants for first data

  • VeloOTTxTyModulesTxITTxTyRzTTTxFieldOff_20100115.db
Added:
>
>
    • Nickname: v1.0
 
    • Tag: LHCBCOND align-20100115
    • Data-set: run 63596
    • IOV: [23/11/2009 - Infty]
Line: 18 to 19
 
      • OT-CFrames Tx, Ty
      • OT-Modules Tx
  • VeloOTTxTyModulesTxITTxTyRzTTTxFieldOffTTLaddersFieldOn_20100122.db
Added:
>
>
    • Nickname: v1.1
 
    • Tag: LHCBCOND tt-20100129
    • Data-set: run 63596 and some magnet on data
    • IOV: [23/11/2009 - Infty]
Line: 30 to 32
 
      • take resulting TT module alignment, and fix TT global parameters on field-of run 63596 The resulting database only differes from 20100115 in the TT alignment.
  • VeloOTTxTyTzModulesTxITTxTyTzRyRzTTTxFieldOffTTLaddersFieldOn_20100205.db
Added:
>
>
    • Nickname: v1.2
 
    • Tag: not yet uploaded
    • Description: same as above, but now adding more degrees of freedom:
      • Velo-global Rx
Line: 45 to 48
  Furthermore, the OT survey was fixed for the bowing of the bridge that was measured in the IT survey. This database gives better IT residuals in field-off data than the previous alignment.
  • VeloOTTxTyTzModulesTxITTxTyTzRxRyRzTTTxTTLaddersFieldOn_20100211.db
Added:
>
>
    • Nickname: v2.0
 
    • Tag: not yet uploaded
    • Description: this is the first FIELD-ON alignment. On field-on data this database gives 30% better IT residual distribution, better overlap between IT stacks, and better matching between T and Velo, and T and CALO,
Line: 55 to 59
 
      • TT-halfmodules: Tx
        IT and OT were fixed in T3
  • VeloOTTxTyTzModulesTxITTxTyTzRyRzITLaddersTxRzTTTxOffTTLaddersFieldOn_20100212.db
Added:
>
>
    • Nickname: v2.1
 
    • Tag: not yet uploaded
    • Description: like above, but adding IT ladder and OT modules.
  • alignment of IT boxes using TED data

Revision 92010-02-12 - WouterHulsbergen

Line: 1 to 1
 
META TOPICPARENT name="LHCbDetectorAlignment"
Line: 54 to 54
 
      • TT: Tx Ty Tz
      • TT-halfmodules: Tx
        IT and OT were fixed in T3
Added:
>
>
  • VeloOTTxTyTzModulesTxITTxTyTzRyRzITLaddersTxRzTTTxOffTTLaddersFieldOn_20100212.db
    • Tag: not yet uploaded
    • Description: like above, but adding IT ladder and OT modules.
 
  • alignment of IT boxes using TED data
    • input: TED2 data
    • parameters:

Revision 82010-02-11 - WouterHulsbergen

Line: 1 to 1
 
META TOPICPARENT name="LHCbDetectorAlignment"
Line: 29 to 29
 
      • use magnet-on data to align all global structures plus TT internally
      • take resulting TT module alignment, and fix TT global parameters on field-of run 63596 The resulting database only differes from 20100115 in the TT alignment.
Changed:
<
<
  • FieldOff20100208.db
>
>
  • VeloOTTxTyTzModulesTxITTxTyTzRyRzTTTxFieldOffTTLaddersFieldOn_20100205.db
 
    • Tag: not yet uploaded
Changed:
<
<
    • Description: same as above, but now added Ry rotation for IT boxes
>
>
    • Description: same as above, but now adding more degrees of freedom:
      • Velo-global Rx
      • Velo-right-half Ry
      • IT boxes: Tx, Ty, Tz, Ry, Rz
      • OT C frames: Tx ; OT C-frame A/C-pairs: Ty Tz
      • OT-Modules Tx
      • Velo-global Rx
      • Velo-right-half Ry
      • TT: Tx Ty Tz
      • TT-halflayers Tx
      • TT-Boxes Tx
        Furthermore, the OT survey was fixed for the bowing of the bridge that was measured in the IT survey. This database gives better IT residuals in field-off data than the previous alignment.
  • VeloOTTxTyTzModulesTxITTxTyTzRxRyRzTTTxTTLaddersFieldOn_20100211.db
    • Tag: not yet uploaded
    • Description: this is the first FIELD-ON alignment. On field-on data this database gives 30% better IT residual distribution, better overlap between IT stacks, and better matching between T and Velo, and T and CALO, Starting from the alignment of 20100205, the following dofs were aligned:
      • IT boxes: Tx, Ty, Tz, Rx, Ry, Rz
      • OT C frames: Tx ; OT C-frame A/C-pairs: Ty Tz
      • TT: Tx Ty Tz
      • TT-halfmodules: Tx
        IT and OT were fixed in T3
 
  • alignment of IT boxes using TED data
    • input: TED2 data
    • parameters:

Revision 72010-02-09 - WouterHulsbergen

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

Alignment constants for first data

Added:
>
>
  • VeloOTTxTyModulesTxITTxTyRzTTTxFieldOff_20100115.db
    • Tag: LHCBCOND align-20100115
    • Data-set: run 63596
    • IOV: [23/11/2009 - Infty]
    • Description (https://savannah.cern.ch/patch/index.php?3673):
      This is the first alignment database obtained with collision tracks. It uses the data from the field-off run 63596. Alignment degrees of freedom were:
      • Velo-global Rx
      • Velo-right-half Ry
      • TT-halflayers Tx
      • TT-Boxes Tx, Ty, Rz
      • OT-CFrames Tx, Ty
      • OT-Modules Tx
  • VeloOTTxTyModulesTxITTxTyRzTTTxFieldOffTTLaddersFieldOn_20100122.db
    • Tag: LHCBCOND tt-20100129
    • Data-set: run 63596 and some magnet on data
    • IOV: [23/11/2009 - Infty]
    • Description (https://savannah.cern.ch/patch/index.php?3729):
      Update of TT half module alignment: The alignment DOFs are identical to 20100115, except that TT half modules are added to resolve a large rotations of some TT modules around the beam pipe. This improves V0 efficiency and resolution. The procedure was:
      • start from previous alignment
      • use magnet-on data to align all global structures plus TT internally
      • take resulting TT module alignment, and fix TT global parameters on field-of run 63596 The resulting database only differes from 20100115 in the TT alignment.
  • FieldOff20100208.db
    • Tag: not yet uploaded
    • Description: same as above, but now added Ry rotation for IT boxes
 
  • alignment of IT boxes using TED data
    • input: TED2 data
    • parameters:

Revision 62009-01-19 - MarcDeissenroth

Line: 1 to 1
 
META TOPICPARENT name="LHCbDetectorAlignment"
Line: 16 to 16
 
    • parameters: Tx of all layers
    • xml
    • note: granularity (full layers) does not necessarily makes sense.
Changed:
<
<
  • alignment of OT half-layers using cosmics
    • input: runs XXXX, ~YYY events, ~ZZZ tracks
>
>
  • alignment of OT half-layers using cosmics (millepede)
    • input: runs 34120,31225,31557,34083,34117, ~31k events (stripped DSTs from Wouter), ~19k tracks
 
    • parameters: Tx of all half layers. first and last two layers fixed.
Changed:
<
<
    • xml:
>
>
 

Alignment constants for MC studies

Revision 52008-09-25 - WouterHulsbergen

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

Alignment constants for first data

  • alignment of IT boxes using TED data
    • input: TED2 data
Added:
>
>
    • parameters:
    • xml
 
  • alignment of VELO using TED data
    • input: TED2 data: runs 32474-32586, ~1900 events, about ~800 tracks
    • parameters: Tx and Ty of all modules; constraints: average position and shearing for both halves
Line: 62 to 64
 
  • now go to the directory that contains MyDBLayer and create the sqlite database with
      shell> SetupProject LHCb
Changed:
<
<
shell> copy_files_to_db.py -c sqlite_file:!MyDBLayer.db/LHCBCOND -s MyDBLayer
>
>
shell> copy_files_to_db.py -c sqlite_file:MyDBLayer.db/LHCBCOND -s MyDBLayer
 

Revision 42008-09-24 - WouterHulsbergen

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

Alignment databases

>
>

Alignment constants for first data

  • alignment of IT boxes using TED data
    • input: TED2 data
  • alignment of VELO using TED data
    • input: TED2 data: runs 32474-32586, ~1900 events, about ~800 tracks
    • parameters: Tx and Ty of all modules; constraints: average position and shearing for both halves
    • xml:
  • alignment of TT using VELO-TT tracks in TED2 data
    • input: TED2 data: runs 32474-32586, ~1900 events, about ~800 tracks
    • parameters: Tx of all layers
    • xml
    • note: granularity (full layers) does not necessarily makes sense.
  • alignment of OT half-layers using cosmics
    • input: runs XXXX, ~YYY events, ~ZZZ tracks
    • parameters: Tx of all half layers. first and last two layers fixed.
    • xml:

Alignment constants for MC studies

  • For the velo misalignment challenge, you can find a sqlite layer here
         /castor/cern.ch/user/s/sblusk/7TeV_Boff_Beam12_H/MisAlCh1/Brunel/VeloSliceMisalignedLHCBCOND.db
       
    and the result after running the alignment software here (under the tag
    VeloAliCh_mille_15b
    )
         /castor/cern.ch/user/g/gersabec/VeloAliCh/VeloAliChResult.db
       
  • A slice for MisAlCh1 you can find here
        /castor/cern.ch/user/w/wouter/lhcb/AlignmentDB/MisAlCh1.db
       
    Marco Clemencic has kindly extracted thisd layer from the original xml database at
        /castor/cern.ch/user/s/sblusk/Brunel/7TeV_FieldOff_MinBias/MisAlCh1/LHCBCOND.db (DON'T USE)
       
  • For the IT/OT alignment with the alignment framework, Matt's page has many xml files, both for the input and ouput of the alignment challenge
  • There is an sqlte layer for "Tx,Rx,Rz" aligned IT ladders and OT modules here
         /castor/cern.ch/user/w/wouter/lhcb/AlignmentDB/ITOTLadderModule_NoTxConstraint_MagnetOn.db
        
    (It would be nice to describe what went into this.) The interesting thing about this one is that the system after the magnet was not constraint in Tx. Therefore, it has an rather large (~1mm) global displacement in x leading to a significant q/p bias.

Tips and tricks for creating alignment databases

  On this page we collect xml files and sqlite layers for various (mis)alignments.
Line: 48 to 90
 

How to load xml files directly

Deleted:
<
<

Sets of aligned databases

  • For the velo misalignment challenge, you can find a sqlite layer here
         /castor/cern.ch/user/s/sblusk/7TeV_Boff_Beam12_H/MisAlCh1/Brunel/VeloSliceMisalignedLHCBCOND.db
       
    and the result after running the alignment software here (under the tag
    VeloAliCh_mille_15b
    )
         /castor/cern.ch/user/g/gersabec/VeloAliCh/VeloAliChResult.db
       
  • A slice for MisAlCh1 you can find here
        /castor/cern.ch/user/w/wouter/lhcb/AlignmentDB/MisAlCh1.db
       
    Marco Clemencic has kindly extracted thisd layer from the original xml database at
        /castor/cern.ch/user/s/sblusk/Brunel/7TeV_FieldOff_MinBias/MisAlCh1/LHCBCOND.db (DON'T USE)
       
  • For the IT/OT alignment with the alignment framework, Matt's page has many xml files, both for the input and ouput of the alignment challenge
  • There is an sqlte layer for "Tx,Rx,Rz" aligned IT ladders and OT modules here
         /castor/cern.ch/user/w/wouter/lhcb/AlignmentDB/ITOTLadderModule_NoTxConstraint_MagnetOn.db
        
    (It would be nice to describe what went into this.) The interesting thing about this one is that the system after the magnet was not constraint in Tx. Therefore, it has an rather large (~1mm) global displacement in x leading to a significant q/p bias.
 

-- WouterHulsbergen - 30 May 2008

Revision 32008-06-09 - MarcoGersabeck

Line: 1 to 1
 
META TOPICPARENT name="LHCbDetectorAlignment"
Line: 54 to 54
 
     /castor/cern.ch/user/s/sblusk/7TeV_Boff_Beam12_H/MisAlCh1/Brunel/VeloSliceMisalignedLHCBCOND.db
   
Added:
>
>
and the result after running the alignment software here (under the tag
VeloAliCh_mille_15b
)
     /castor/cern.ch/user/g/gersabec/VeloAliCh/VeloAliChResult.db
   
 
  • A slice for MisAlCh1 you can find here
        /castor/cern.ch/user/w/wouter/lhcb/AlignmentDB/MisAlCh1.db

Revision 12008-05-30 - WouterHulsbergen

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

Alignment databases

On this page we collect xml files and sqlite layers for various (mis)alignments.

How to create sqlite from the xml

To create an sqlite data base from a set of xml files, you can follow this recipee.

  • first creat an directory that will hold the data files, e.g. MyDBLayer
  • now copy the xml files to the right place, depending on subdetector:
    • for OT: MyDBLayer/Conditions/OT/Alignment/Elements.xml
    • for IT: MyDBLayer/Conditions/IT/Alignment/Detector.xml
    • for VELO constants are split over 3 files
      • global and halves: MyDBLayer/Conditions/Velo/Alignment/Global.xml
      • modules: MyDBLayer/Conditions/Velo/Alignment/Modules.xml
      • sensors: MyDBLayer/Conditions/Velo/Alignment/Detectors.xml
  • now go to the directory that contains MyDBLayer and create the sqlite database with
      shell> SetupProject LHCb
      shell> copy_files_to_db.py -c sqlite_file:!MyDBLayer.db/LHCBCOND -s MyDBLayer

How to load an sqlite 'layer'

This is how you can load it in python

MisAlCh1COND = CondDBAccessSvc("MisAlCh1COND")
MisAlCh1COND.ConnectionString = "sqlite_file:VeloSliceMisaligned.db/LHCBCOND"
addCondDBLayer(MisAlCh1COND)

The recipee for doing this in job options is something like this

CondDBDispatcherSvc.Alternatives = {'/Conditions=CondDBLayeringSvc/CONDLayers'};
CONDLayers.Layers = {'CondDBAccessSvc/CONDLocal', 'CondDBAccessSvc/LHCBCOND'};
CONDLocal.ConnectionString = "sqlite_file:$HOME/VeloSliceMisaligned.db/LHCBCOND";

(See this twiki topic.)

How to extract the xml from an sqlite database

See here

How to load xml files directly

Sets of aligned databases

  • For the velo misalignment challenge, you can find a sqlite layer here
         /castor/cern.ch/user/s/sblusk/7TeV_Boff_Beam12_H/MisAlCh1/Brunel/VeloSliceMisalignedLHCBCOND.db
       
  • A slice for MisAlCh1 you can find here
        /castor/cern.ch/user/w/wouter/lhcb/AlignmentDB/MisAlCh1.db
       
    Marco Clemencic has kindly extracted thisd layer from the original xml database at
        /castor/cern.ch/user/s/sblusk/Brunel/7TeV_FieldOff_MinBias/MisAlCh1/LHCBCOND.db (DON'T USE)
       
  • For the IT/OT alignment with the alignment framework, Matt's page has many xml files, both for the input and ouput of the alignment challenge
  • There is an sqlte layer for "Tx,Rx,Rz" aligned IT ladders and OT modules here
         /castor/cern.ch/user/w/wouter/lhcb/AlignmentDB/ITOTLadderModule_NoTxConstraint_MagnetOn.db
        
    (It would be nice to describe what went into this.) The interesting thing about this one is that the system after the magnet was not constraint in Tx. Therefore, it has an rather large (~1mm) global displacement in x leading to a significant q/p bias.

-- WouterHulsbergen - 30 May 2008

 
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