Changes between Version 20 and Version 21 of DevelopmentIssues


Ignore:
Timestamp:
Oct 15, 2012, 8:33:28 PM (12 years ago)
Author:
Olivier Mattelaer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DevelopmentIssues

    v20 v21  
    55 When editing the above, please try to stick to the self-explanatory conventions (Syntax, fixed numbering and placement in the right section when fixed).
    66
     7== To fix before v2.0 beta release ==
     8
     9 aMC@NLO 5 | J.A. | When launching aMC@NLO some 'set' commands are not recognized and output their help.:: This is because aMCatNLOLauncher uses exec_cmd from ExtendedCmd which in turn will call the do_set() of common_run_interface.py for which 'check_set()' does not recognize some options like complex_mass_scheme and loop_optimized_output. I am not sure how Marco wants this fixed, so please Marco do it.
     10
     11 aMC@NLO 71| O.M. | aMCatNLO-Utilities should auto-detect the compiler/ the fact that we are in 64 bit/...::
     12and also having a file make_opts used by all sub makefile present in this utilities.
     13
    714== To fix before v2.0 release ==
    815
    916 4 | O.M. | Generate some html output for checking the generation of the fortran code and of the output. ::
    1017
    11 
    12  15FKS | O.M. | Generalize the function get_interaction_q_power:: so that it uses aloha to retrieve this information (comment copied from FKS5 branch review)
    13   '''R.F. |''' Is this necessary before the release? We support only virtual corrections within the Standard Model.
    1418
    1519 22FKS | All | We need to discuss what functionality we want to release,:: in particular the complex mass scheme. It is not correct as such right now but people could easily correct it and scoop us. Same for QED in principle. What feature do we want to lock and how? Please make your proposal below.
    … …  
    1923
    2024
    21  aMC@NLO 5 | J.A. | When launching aMC@NLO some 'set' commands are not recognized and output their help.:: This is because aMCatNLOLauncher uses exec_cmd from ExtendedCmd which in turn will call the do_set() of common_run_interface.py for which 'check_set()' does not recognize some options like complex_mass_scheme and loop_optimized_output. I am not sure how Marco wants this fixed, so please Marco do it.
     25== To be adressed (the fatest the better) ==
    2226
    23 
    24 == To be adressed after v2.0 release ==
     27 15FKS | O.M. | Generalize the function get_interaction_q_power:: so that it uses aloha to retrieve this information (comment copied from FKS5 branch review)
     28  '''R.F. |''' Is this necessary before the release? We support only virtual corrections within the Standard Model.
    2529
    2630 28FKS | O.M. | Refactor helas_call_writers.py:: by creating a loop version of this file to be put in the 'loop' directory and creating a LoopHelasCallWriter daughter class to build more elegant structures for the loop helas output. (comment copied from FKS5 branch review)