Purpose of this page

Is to provide a written logbook of changes affecting muon triggers and reports from validation.

Log-Book

Tracking software integration log.
Muon tracking software integration log.
The comments below are related to a configuration only change [C] or a software change, accompagnied with configuration change [S].

3.11 Cycle

3.11.1.hltpatch1

  • Report on 10 March 2011
    • Trigger validation (hn posting) shows no significant differences from 3.11.0.pre5.

3.11.0.pre2

  • Report on 12 January 2011
    • Trigger validation (hn posting) shows no significant differences from 3.10.0 (no FastSim available).

3.10 Cycle

3.10.0

  • Report on 12 January 2011
    • Trigger validation (hn posting) shows no significant differences from 3.10.0.pre5.

3.10.0.pre9

  • Report on 3 January 2011
    • Trigger validation (hn posting) shows no significant differences from 3.10.0.pre5.

3.10.0.pre7 and 3.10.0.pre5

  • Report on 7 December 2010
    • Trigger validation (hn posting) shows no significant differences from 3.10.0.pre2.

3.10.0.pre4

  • Report on 18 November 2010
    • Trigger validation (hn posting) shows no significant differences from 3.10.0.pre3.
    • Trigger validation also shows no difference between the special CMS.RelVal samples produced with 64-bit architecture vs. the normal 32-bit samples.

3.10.0.pre3

  • Report on 9 November 2010
    • Trigger validation (hn posting) shows no significant differences from 3.10.0.pre2

3.10.0.pre2

  • Report on 4 November 2010
    • Trigger validation (hn posting) shows no significant differences from 3.10.0.pre1

3.10.0.pre1

  • Report on 26 October 2010
    • Trigger validation (hn posting) shows no significant differences from 3.9.0.

3.9 Cycle

3.9.6 and 3.9.7

  • Report on 3 January 2011
    • Trigger validation (hn posting) shows no significant differences from 3.9.5.

3.9.5, 3.9.4, and 3.9.3

  • Report on 7 December 2010
    • Trigger validation (hn posting) shows no significant differences from 3.9.2.

3.9.2

  • Report on 9 November 2010
    • Trigger validation (hn posting) shows no significant differences from 3.9.1

3.9.1

  • Report on 4 November 2010
    • Trigger validation (hn posting) shows no significant differences from 3.9.0.

3.9.0

  • Report on 19 October 2010
    • Trigger validation (hn posting) shows no significant differences from 3.9.0.pre7.

3.9.0.pre7

  • Report on 14 October 2010
    • Trigger validation (hn posting) shows no significant differences from 3.9.0.pre5.

3.9.0.pre5

  • Report on 28 September 2010
    • Trigger validation (hn posting) shows a slight increase in L1 efficiency in the endcaps for the JPsi sample.

3.9.0.pre4

  • Report on 21 September 2010
    • Trigger validation (hn posting) shows no significant differences from 3.9.0.pre3.

3.9.0.pre3

  • Report on 3 September 2010
    • Trigger validation (hn posting) shows significant gains in efficiency at L3 vs. 3.9.0.pre2 due to the introduction of the L3 cascade algorithm.

3.9.0.pre2

  • Report on 26 August 2010
    • Trigger validation (hn posting) shows agreement with 3.9.0.pre1.

3.9.0.pre1

  • Report on 3 August 2010
    • Trigger validation (hn posting) shows agreement with 3.8.0.

3.8 Cycle

3.8.6

  • Report on 9 November 2010
    • Trigger validation (hn posting) shows no significant differences from 3.8.5

3.8.5

  • Report on 14 October 2010
    • Trigger validation (hn posting) shows no significant differences from 3.8.4.

3.8.4

  • Report on 21 September 2010
    • Trigger validation (hn posting) shows significant gains in efficiency at L3 vs. 3.9.0.pre2 due to the introduction of the L3 cascade algorithm.

3.8.3

  • Report on 16 September 2010
    • Trigger validation (hn posting) shows agreement with 3.8.2.

3.8.2

  • Report on 27 August 2010
    • Trigger validation (hn posting) shows agreement with 3.8.1.

3.8.1

  • Report on 12 August 2010
    • Trigger validation (hn posting) shows no significant differences from 3.8.0.

3.8.0

  • Report on 26 July 2010
    • Trigger validation (hn posting) shows the same inefficiencies for JpsiMM seen since 3.8.0.pre1. We received news, however, from Ivan Furic and the L1 team that the inefficiency is real, so this release is considered validated for muon trigger.

3.8.0.pre8

  • Report on 13 July 2010
    • Trigger validation (hn posting) shows the same inefficiencies for JpsiMM seen since 3.8.0.pre1.

3.8.0.pre7

  • Report on 6 July 2010
    • Trigger validation (hn posting) shows the same inefficiencies for JpsiMM seen since 3.8.0.pre1.

3.8.0.pre6

  • Report on 6 July 2010
    • Trigger validation (hn posting) shows the same inefficiencies for JpsiMM seen since 3.8.0.pre1.

3.8.0.pre5

  • Report on 6 July 2010
    • Trigger validation (hn posting) shows the same inefficiencies for JpsiMM seen since 3.8.0.pre1.

3.8.0.pre4

  • Report on 21 June 2010
    • Trigger validation (hn posting) shows the same inefficiencies for JpsiMM seen since 3.8.0.pre1.

3.8.0.pre2

  • Report on 14 June 2010
    • Trigger validation (hn posting) shows the same inefficiencies for JpsiMM seen in 3.8.0.pre1.

3.8.0.pre1

  • Report on 8 June 2010
    • Trigger validation (hn posting) shows an L1 efficiency drop of ~10% in the endcaps for JPsiMM.

3.7 Cycle

3.7.1

  • Report on 12 August 2010
    • Trigger validation (hn posting) shows no significant differences from 3.7.0.

3.7.0

  • Report on 1 June 2010
    • Trigger validation(hn posting) shows agreement with 3.7.0.

3.7.0.pre5

  • Report on 25 May
    • Trigger validation (hn posting) shows agreement with 3.7.0.pre4.

3.7.0.pre4

  • Report on 17 May
    • Trigger validation (hn posting) shows agreement with 3.7.0.pre3.

3.7.0.pre3

  • Report on 7 May
    • Trigger validation (hn posting) shows agreement with 3.7.0.pre2.

3.7.0.pre2

  • Report on 30 April
    • Trigger validation (hn posting) shows agreement with 3.5.7 for all per-muon plots, but the efficiency summary shows an increased rate for some triggers (this may also be present in 3.7.0.pre1).

3.7.0.pre1

  • Report on 26 April
    • Trigger validation (hn posting) shows agreement with 3.5.0.pre1, but with some higher (1%) L1 and L2 efficiencies at low pT.

3.6 Cycle

3.6.3

  • Report on 17 June
    • Trigger validation (hn posting) shows agreement with 3.6.1.

3.6.2

  • Report on 8 June 2010
    • Trigger validation (hn posting) shows agreement with 3.6.1.

3.6.1.patch1

  • Report on 25 May
    • Trigger validation (hn posting) shows agreement with 3.6.1.

3.6.1

  • Report on 14 May
    • Trigger validation (hn posting) shows agreement with 3.6.0.

3.6.0

  • Report on 26 April
    • Trigger validation (hn posting) shows agreement with 3.5.0.pre1, but with some higher (1%) L1 and L2 efficiencies at low pT.

3.6.0.pre5

  • Report on 7 April
    • Trigger validation (hn posting) shows agreement with 3.5.0.pre1.

3.6.0.pre4

  • Report on 26 March
    • Trigger validation (hn posting) shows agreement with 3.5.0.pre1 for the first time since 3.5.0.pre5. L1 reverted back to the previous algorithm which does not produce extra ghosts while L2 works on a solution that will maintain efficiency with the newer algorithm.

3.6.0.pre3

  • Report on 16 March
    • Trigger validation (hn posting) shows the same L1 inefficiency seen since 3.5.0.pre5.

3.6.0.pre2

  • Report on 8 March
    • Trigger validation (hn posting) shows the same L1 inefficiency seen since 3.5.0.pre5 (both architectures).

3.6.0.pre1

  • Report on 1 March
    • Trigger validation (hn posting) shows the same L1 inefficiency seen since 3.5.0.pre5 (both architectures).

3.5 Cycle

3.5.8

  • Report on 30 April
    • Trigger validation (hn posting) shows agreement with 3.5.7.

3.5.7

  • Report on 26 April
    • Trigger validation (hn posting) shows agreement with 3.5.0.pre1, but with some higher (1%) L1 and L2 efficiencies at low pT.

3.5.5

  • Report on 29 March
    • Trigger validation (hn posting) shows the same L1 inefficiency seen since 3.5.0.pre5.

3.5.3

  • Report on 8 March
    • Trigger validation (hn posting) shows the same L1 inefficiency seen since 3.5.0.pre5 (both architectures).

3.5.2

  • Report on 23 February
    • Trigger validation (hn posting) shows a loss of efficiency at L1 similar to 3.5.1 and 3.5.0.

3.5.1

  • Report on 22 February
    • Trigger validation (hn posting) shows a loss of efficiency at L1 similar to 3.5.0.

3.5.0

  • Report on 9 February
    • Trigger validation (hn posting) shows a loss of efficiency similar to 3.5.0.pre5, but less severe (5% rather than 10%).

3.5.0.pre5g493

  • Report on 4 February
    • Trigger validation (hn posting) shows consistency with the 3.5.0.pre5 samples; the drop in L1 is still apparent.

3.5.0.pre5

  • Report on 1 February
    • Trigger validation (hn posting) shows a drop in L1 efficiency of ~10% for all paths using an L1 quality cut of 5 or above.
  • Report on 4 February
    • Trigger validation (hn posting shows comparable results between the two architectures slc5_ia32_gcc434 and slc5_amd64_gcc434, with the L1 issues present in both.

3.5.0.pre3

  • Report on 21 January
    • Trigger validation (hn posting) for slc5_amd64_gcc434 environment shows agreement with 3.5.0.pre1.
  • Report on 18 January
    • Trigger validation (hn posting) shows agreement with 3.5.0.pre1.

3.5.0.pre2

  • Report on 4 January
    • Trigger validation (hn posting) shows agreement with 3.5.0.pre1.

3.5.0.pre1

  • Report on 14 December
    • Trigger validation (hn posting) shows agreement with 3.4.0.pre6.

3.4 Cycle

3.4.2

  • Report on 9 February
    • Trigger validation (hn posting) shows agreement with 3.4.1.

3.4.1

  • Report on 22 December
    • Trigger validation (hn posting) shows agreement with 3.4.0.

3.4.0

  • Report on 16 December
    • Trigger validation (hn posting) shows agreement with 3.4.0.pre6.

3.4.0.pre7

  • Report on 7 December
    • Trigger validation ([[https://hypernews.cern.ch/HyperNews/CMS/get/muon-hlt/219.html][hn posting]) shows agreement with 3.4.0.pre6.

3.4.0.pre6

  • Report on 24 November
    • Trigger validation (hn posting) shows agreement with the 3.3 series again. The L1 issue first reported in 3.4.0.pre2 has been resolved.

3.4.0.pre5

  • Report on 9 November
    • Trigger validation (hn posting) shows the same decrease at L1 as seen in pre4, but the L2 efficiency is back in agreement with pre1.

3.4.0.pre4

  • Report on 9 November
    • Trigger validation (hn posting) shows a lower L1 efficiency in the endcaps (~1%) and efficiency at L2 drops to zero for |eta| > 1.8.

3.4.0.pre2

  • Changes
    • The tracker reconstructed hits in the barrel are now purely 1D rechits, while there were techincaly 2D.
  • Report on 22 October
    • Both Muon Trigger validation (hn posting) and RecoMuon validation (hn posting) show a lower L2 muon efficiency in the endcaps, 1.5<|eta|<2

3.4.0.pre1

  • Report on 11 October
    • Trigger validation (hn posting) shows agreement with 3.3.0.pre6.

3.3 Cycle

3.3.6

  • Report on 10 December
    • Trigger validation ([[https://hypernews.cern.ch/HyperNews/CMS/get/hlt/1221.html][hn posting]) shows agreement with 3.3.5.

3.3.5

  • Report on 30 November
    • Trigger validation ([[https://hypernews.cern.ch/HyperNews/CMS/get/hlt/1194.html][hn posting]) shows agreement between 3.3.5 and 3.3.4 with gcc345.

3.3.4

  • Report on 20 November
    • Trigger validation (hn posting) shows agreement between 3.3.4 and 3.3.3 with gcc345.

3.3.3

  • Report on 16 November
    • Trigger validation (hn posting) shows agreement with 3.3.2 for gcc345. We continue to see the significant reduction in efficiency at L1 for gcc434 first reported in 3.3.1.

3.3.2

  • Report on 3 November
    • Trigger validation (hn posting) shows agreement with 3.3.1.
    • Trigger validation using slc5_ia32_gcc434 (hn posting) still shows a significant reduction in efficiency at L1.

3.3.1

  • Report on October 27
    • Trigger validation (hn posting) shows agreement with 3.3.0. Separate samples were produced, however, with different combinations of SLC and gcc versions. The setups using gcc4xx showed a reduced (~5%) efficiency in the endcaps with respect to the gcc3xx compiler used in previous productions.

3.3.0

  • Report on October 14
    • Trigger validation (hn posting) shows agreement with 3.3.0.pre6, including the increase in efficiency. This has been deemed acceptable.
  • Report on October 23
    • Trigger validation (hn posting) of special samples produced with slc4_ia32_gcc432 show a drop in efficiency in the endcaps at L1 (IDEAL conditions only). The problem is most apparent for TeV muons, with a drop of ~10% globally.

3.3.0.pre6

  • Changes
    • The L2 refit is removed.
  • Report on 5 October
    • Trigger validation (hn posting) shows an increase in global efficiency of ~3% over 3.3.0.0pre5, starting at L2.

3.3.0.pre5

  • Report on 29 September
    • Trigger validation (hn posting (check replies)) shows general agreement with 3.3.0.pre3, although there is a gain of ~1% in global efficiency for 100 and 1000 GeV muons.

3.3.0.pre4

  • Changes
    • The code for the global refit of the L3 changed location [S].
    • There is an Hcal problem in this release (hn post) and isolation calculation is biased. Resulting in higher TeV efficiency.
  • Report on 22 September
    • Trigger validation (hn posting): general increase in efficiency (~1%), though dependent on pT; TeV muons gained ~5% in isolated paths, while 10 GeV muons lost ~1%.

3.3.0.pre3

  • Report on 14 September
    • Trigger validation (hn posting): no significant differences observed from 3.3.0.pre2.

3.3.0.pre2

  • Changes
    • To recover failure of pattern recognition, a "safety cone" of 0.1 is added to search for hits when none are compatible with the regular chi squared criteria (same as in 3.2.6)[S].
    • The CSC 2D rechits reconstruction is taking bad channels into account [C].
  • Report on 10 September
    • Trigger validation (hn posting): The new L3TrackFinder tag has been picked up, bringing the 3.3 cycle into agreement with 3.1.2.

3.3.0.pre1

  • Report on 1 September
    • Trigger validation (hn posting): a loss of L3 efficiency in the transition region (around |eta| = 1.1) is still observed, of order 10% for several bins. This is seen in all samples with STARTUP conditions, as well as for low pT in MC conditions.

3.2 Cycle

3.2.8

  • Report on 21 October
    • Trigger validation (hn posting) shows full agreement with 3.2.7.

3.2.7

  • Report on 24 September
    • Trigger validation (hn posting) shows full agreement with 3.2.6.

3.2.6

  • Changes
    • To recover failure of pattern recognition, a "safety cone" of 0.1 is added to search for hits when none are compatible with the regular chi squared criteria [S].
  • Report on 8 September
    • Trigger validation (hn posting) shows agreement with 3.1.2 for the first time in the 3.2 release cycle.

3.2.5

  • Report on 24 August
    • Trigger validation (hn posting) shows drops that are less severe than in previous 3.2.X releases, but still noticable. Overall efficiency at L3 is down ~1.5%, much of which is concentrated in the transition region (eta=1.2). By looking at the SingleMu samples, the loss also seems correlated with low pt; for the 1000 GeV sample, results are nearly identical to 3.1.2, while the 10 GeV sample shows noticeable loss.

3.2.4

  • Report on 10 August
    • Trigger validation (hn posting) shows a reduced (~2%) drop in overall efficiency when compared to 3.1.1 STARTUP. Results look good for IDEAL conditions, except for an eta dependence at low pt.

3.2.3

  • Changes
    • Track candidate maker package was fixed for cosmics and hlt problems [S].
  • Report on 4 August
    • Trigger validation (hn posting) shows the same issues as in 3.2.0 for STARTUP conditions, but is in agreement with 3.1.1 for IDEAL conditions.

3.2.2

  • Report on 30 July
    • Trigger validation (hn posting) shows the same issues as in 3.2.0.
    • Reco validation (hn posting) shows the same issues as in 3.2.0, plus the evidence of a lower number of hits used to reconstruct L2 muons, when those muons are at low pT. Checked afterward that this was not yet present in 3_2_1.

3.2.1

  • Report on 24 July
    • Trigger validation (hn posting) shows the same issues as in 3.2.0.

3.2.0

  • Changes
    • The L3 seeding configuration was changed to OI-state algorithm [C].
    • The standard tracking candidate maker uses the 4 first hits to determine the track candidate parameters (same a before, but some code change occurred) [S].
  • Report on 21 July
    • Trigger validation (hn posting) shows ~20% drop in efficiency for several bins near |eta| = 1.1.

3.1 Cycle

3.1.6

  • Report on 24 November
    • Trigger validation (hn posting) shows complete agreement with 3.1.5.

3.1.5

  • Report on 16 November
    • Trigger validation (hn posting) shows complete agreement with 3.1.4 for FullSim. The L1 in FastSim now shows a dip near eta=1.2 which better emulates FullSim performance, although the overall efficiency estimate has risen.

3.1.4

  • Report on 5 October
    • Trigger validation (hn posting) shows complete agreement with 3.1.3.

3.1.3

  • Report on 29 September
    • Trigger validation (hn posting) shows complete agreement with 3.1.2.

3.1.0

  • Changes
  • Report on July 2
    • Identical to 3_1_0_pre11

3.1.0 pre11

  • Changes
    • none to be reported.
  • Report on July 1
    • Trigger validation for pre11 does not show differences to pre10.
    • Reconstruction validation reports no major issues:
      • Apparent better efficiencies when using the muonAssociatorByHits are due in fact to a fix in that associator
      • Fake rates in L2/L3 went back to (low) value that was there before pre7

3.1.0 pre10

  • Changes
    • none to be reported from the configuration side.
    • DT calibration constants from pre7 are used as fall back.
  • Report on June 15
    • Trigger validation for pre10 does not show differences to pre9.
    • Reconstruction validation reports no major issues:
      • Fit quality has improved from previous validation. Startup samples are not affected.

3.1.0 pre8/9

  • Changes
    • Introduction of "invalid hits" in the L2 pattern recognition (essentially the backward filtering) [S].
    • Uniformization of the configuration of L2 with the stand-alone offline muon reconstruction [C].
    • Momentum cut in level3 seeding is made configurable (2.5 GeV by default) [S].
    • CSC digis parameters are made tracked [S].
    • CSC hits reconstruction uses "FilePoleFit" [S].
    • new DT calibration constants are used. Turns out they are wrong.
  • Report on June 5
    • Trigger validation for pre9 does not show differences to pre8 (almost identical to pre9 anyways).
  • Report on June 1
    • Trigger validation for pre8 does not show differences to pre7.
    • Reco validation for pre8 exhibits several issues.
      • Fake rate in L2 and L3 still at the (high) pre7 level.
      • L2 muons with zero hits due to outliers rejection in pattern reco (to be fixed)
      • Larger track normalized chi squared in the barrel at L2 and L3, probably due to outliers rejection in pattern reco (to be fixed)

3.1.0 pre7

  • Changes
    • level3 global matching configuration is such that pre5 behavior is recovered [C].
  • Report on May 19
    • offline DT rechits are ok.
    • HLT inefficiencies in the endcaps are fully recovered.
    • larger fake rate in pre7 wrt previous pre-releases in L2 and L3

3.1.0 pre6

  • Changes
    • DT 4D segments reconstruction is using the linear drift algorithm (as for offline reconstruction) [C].
  • Report on May 05 (pre4 to pre6)
    • Drop of efficiency of L2 in the endcap (and L3 efficiency): this is due to the CSC track finder emulator FIXED
    • Worse L2 pT resolution in the very central region. L2 pulls are getting worse at 10 GeV. INVESTIGATING .
    • L2 pulls on eta are getting better at 100 GeV.

3.1.0 pre5

  • Changes
    • DT 1D hits reconstruction is using the linear drift algorithm (as for offline reconstruction) [C].
    • CSC local reconstruction parameters are made tracked [S].
    • CSC segments reconstruction configuration is simplified [C].
    • level2 seeding configuration is simplified [C].
    • level2 reconstruction is using 3 successive final fit, and using the stepping helix propagator with level2 optimisation [C].
    • level2 isolation software is modified to be able to either cut in the producer or in the filter [S].
import copy
process.hltSingleMuIsoL3IsoFiltered9.IsolatorPSet = copy.copy(process.hltL2MuonIsolations.IsolatorPSet)
process.hltL2MuonIsolations.IsolatorPSet = cms.PSet()
    • pixel digis parameters are made tracked [S].
    • strip unpacking configuration is adapted for central maintenance of offline and online unpacking [S].
    • level3 seeding configuration cleaned [C].
    • level3 global matching software and configuration are according to proposed changes, but those changes are not supposed to persist (removed in pre7) [S].
  • Report on reconstruction
    • Missing L2 in endcaps (and L3), see above in pre6.
    • Worse L2 pT resolution in the very central region. Pulls are getting worse.

3.1.0 pre4

  • Changes
    • level3 muon candidate software is rolling back to previous behavior. not making the level2<->level3 strictness check [S].
  • Report on March 23 (Jeff)
    • Everything is consistent with pre2.
  • Report on March 28 (Zoltan)
    • Low efficiency in the backward region: associator issue due to geometry issue UNDERSTOOD .

3.1.0 pre3

  • Changes
    • Calorimeter unpacking at level2 modified from level1-centered 1x1-window to level2-centered 0.3x0.3-window [C].
  • Report on March 9
    • Lower efficiency at the isolation step: not related to the changes above, but to a change of top decay generator UNDERSTOOD .

3.1.0 pre2

  • Changes
    • Configuration of optional and un-used level3 seeding removed [C].
    • CSC 2D hits reconstruction uses the pruning of bad hits [S].

3.0 Cycle

3.0 pre9/10

3.0 pre4/5/6/7/8

  • Changes
    • Calorimeter local reconstruction adapted to software modularisation [C].
    • level3 global matching software modifed to allow for more than one matching criteria [S].

3.0 pre3

  • Changes
    • level3 global fit can rescale the errors on the first TEC hit in the backward fit [S].
    • level3 candidates can be made with level2<->level3 strictness (removed in 3.1 pre4) [S].

3.0 pre2

  • Changes
    • DT digis configuration cleaned [C].
    • DT 4D segments reconstruction software change for T0 correction: not applied at HLT [S].
    • CSC segments reconstruction can use showering in ST algorithm (hit pruning????) [S].
    • level2 fitter is changed from the offline configuration to online specific configuration [C].

3.0 pre1 3.0 was branched from 2.1.10

  • Changes
    • level2 seeding refit possible but not switched on [C].
    • level3 global fit selects some of the tracker hits [S].

2.2 Cycle

2.2.4/5/6/7/8/9/10/11/12/13

  • Changes
    • DT 4D segments reconstruction may apply the T0 correction: not applied at HLT [S].

2.2.2/3

  • Changes
    • Pixel track minimum pT raised from 0 to 100 MeV [C].

2.2.0/1 was branched after 2.1.10

  • Changes
    • level2 seeding refit possible but not switched on [C].
    • level3 global fit selects some of the tracker hits [S].
    • DT digis configuration cleaned [C].
    • CSC segments reconstruction can use showering in ST algorithm (hit pruning????) [S].

2.1 Cycle

2.1.1/2/3/4/5/6/7/8/9/10/11/12

  • Changes
    • Modification of configuration of un-used level3 seeding option [C].

2.1.0

  • Changes
    • level3 pixel track deposit extractor configuration actually change [C].

2.1 pre9/10

  • Changes
    • level3 pixel track deposit extractor configuration for startup mis-alignment robustness [S].

2.1 pre7/8

  • Changes
    • level3 seeding region length change from 22.7 to 15.9 cm [C].
    • level3 pixel track deposit extractor is able to cut on number of tracks rather than sum pT [S].

2.1 pre6

  • Changes
    • CSC 2D hits reconstruction handles bad wires and bad strips [S].
    • level2 reconstruction may perform a final refit: not on by default [S].

2.1 pre5 is not taken into account because one cannot track what was the confDB version for it.

anything before 2.1.0.pre4 is not in confDB, and therefore tracking it back is more difficult.

2.0 Cycle

-- JeanrochVlimant - 12 Jun 2009

Edit | Attach | Watch | Print version | History: r91 < r90 < r89 < r88 < r87 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r91 - 2011-03-10 - JeffKlukasExCern
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

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