Changes between Version 29 and Version 30 of DevelopmentIssues


Ignore:
Timestamp:
Oct 17, 2012, 10:19:51 AM (12 years ago)
Author:
Valentin Hirschi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DevelopmentIssues

    v29 v30  
    1515DONE MZ r370 (and 16 for MCatNLO-utilities)
    1616
    17  aMC@NLO ?? && ?? |J.A && O.M | Change the tag before the > for the aMC@NLO run interface. ::
    18 done
     17
     18 aMC@NLO ?? && ?? | O.M | Having all acceptance/parralel test working !! (not the case currently) ::
    1919
    2020
    21  aMC@NLO ?? && ?? | O.M | Having all acceptance/parralel test working !! (not the case currently) ::
    2221== To fix before v2.0 release ==
    2322 
    … …  
    4948== Fixed issues ==
    5049
     50 aMC@NLO ?? && ?? |J.A && O.M | Change the tag before the > for the aMC@NLO run interface. :: So to make it explicit where the user stand and avoid confusion.
     51
     52 '''[ Fixed ] V.H. |''' I changed it to aMC@NLO_run>.
     53
    5154 2 | O.M | Commands help and auto-completion:: Update the auto-completion and help for the loop functionalities.
    5255
    53   '''[ Fixed ] V.H. |''' The auto-completion should now be ok, especially when entering loop processes definitions. The help has gained a color scheme and is now updated with the loop features except for the aMC@NLO launch section which Marco will fill in very soon. So let us know if anything suspicious is left in this department.
     56 '''[ Fixed ] V.H. |''' The auto-completion should now be ok, especially when entering loop processes definitions. The help has gained a color scheme and is now updated with the loop features except for the aMC@NLO launch section which Marco will fill in very soon. So let us know if anything suspicious is left in this department.
    5457
    5558 10 | M.Z. | Fix the STOP: momentum conservation errror from madloop ::
    5659  '''[ Fixed ] M.Z. |''' (r355), it was a stupid bug inside check_poles
    5760 
     61
    5862 1 | R.F | Default coupling orders at NLO:: Change the default chosen coupling order configuration for processes which can have mixed order contributions at LO already. Typically, one wants p p > t t~ [QCD] to return only contributions with QED = 0.
    5963  '''[ Fixed ] V.H. |''' Now in the case proposed above, it will inform the user that the configuration (QED=0,QCD=*) is chosen and warns that additional contributions of configuration (QED=2,QCD=*) are detected but discarded.