Sep 25, 2013 (TMVA-v4.2.0) |
Factory:
The default has changed and is now "EqualNumEvents" (with fixed meaning)
While previously NumEvents and EqualNumEvents (by mistake/miscommunication)
took into account training+test events, they are now correctly
normalising only "Training Events" (note the reason for these
normalisations was to have the possibility to easily force the
effective (weighted) number of training events used for Signal (class
0) to equal the number of training events in the Backgr. (sum of all
remaining classes in multiclass mode)
Boosted Decision Trees:
MethodBoost:
July 20, 2011 (TMVA-v4.1.2) |
Variable transformation:
(TMVA::gConfig().GetVariablePlotting()).fNbinsMVAoutput = 50;
Bug fixes:
Dec 20, 2010 (TMVA-v4.1.0) |
The changes with respect to TMVA 4.0.7 are listed below.
Framework:
Nov 3, 2009 (TMVA-v4.0.3) |
TMVA/macros/ TMVAClassificationCategory.C | TMVA/macros/ TMVAClassificationCategoryApplication.C |
TMVA/execs/ TMVAClassificationCategory.cxx | TMVA/execs/ TMVAClassificationCategoryApplication.cxx |
July 25, 2009 (TMVA-v4.0.2) |
June 29, 2009 (TMVA-v4.0.1) |
May 16, 2009 (TMVA-v4.0.0) |
Release of beta version of TMVA 4 | |
Why a beta release ? |
The changes from TMVA 3.9.7 to TMVA 4 are substantial. Some parts
such as documentation − the TMVA Users Guide − are not yet
updated accordingly (this is our next target!). We have done a large
number of tests before releasing this version of TMVA, and are thus
confident that the classifiers work properly. For the regression
algorithms we need to collect more practical experience to know how
best to tune them. Technically however they work. Please provide feedback whenever you encounter a problem or unwanted feature! |
What risk do I take by using TMVA 4 ? | TMVA 4 is not (necessarily) backward compatible. Mainly, because we have moved from text weight files to XML format. It is still possible to create MVA methods via the Reader by giving text weight files, but we cannot guarantee that they will work properly due to the many changes we have done in the data handling framework and MVA methods themselves. If you need to upgrade to TMVA 4, but also require backward compatibility for the reading of the weight files, contact the authors − we will help. |
Known problems / issues |
|
Dec 2, 2008 (TMVA-v3.9.6) |
Aug 9, 2008 (TMVA-v3.9.5) |
May 28, 2008 (TMVA-v3.9.4) |
Apr 16, 2008 (TMVA-v3.9.2) |
Apr 8, 2008 (TMVA-v3.9.1) |
Apr 3, 2008 (TMVA-v3.9.0) |
Jan 23, 2008 (TMVA-v3.8.14) |
Dec 22, 2007 (TMVA-v3.8.13) |
Oct 26, 2007 (TMVA-v3.8.11) |
Oct 13, 2007 (TMVA-v3.8.10) |
Oct 3, 2007 (TMVA-v3.8.9) |
Oct 2, 2007 (TMVA-v3.8.8+) |
Sep 28, 2007 (TMVA-v3.8.8) |
Aug 28, 2007 (TMVA-v3.8.7) |
July 16, 2007 (TMVA-v3.8.6) |
June 26 - July 5, 2007 (TMVA-v3.8.5) |
June 19, 2007 (TMVA-v3.8.4) |
June 5, 2007 (TMVA-v3.8.1 - TMVA-v3.8.3) |
May 18, 2007 (TMVA-v3.7.3) |
There are two possibilities to circumvent the bug:
April 10-18, 2007 (TMVA-v3.7.0 - v3.7.2) |
March 9, 2007 (TMVA-v3.6.1) |
March 5, 2007 (TMVA-v3.6.0) |
December 17, 2006 (TMVA-v3.5.0) |
November 15, 2006 (TMVA-v3.4.0) |
October 24, 2006 (TMVA-v3.3.7) |
October 1, 2006 (TMVA-v3.3.4) |
September 12, 2006 (TMVA-v3.0) |
July 27, 2006 (TMVA-v2.1) |