2013:groups:tools:dlha
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
2013:groups:tools:dlha [2013/06/18 17:00] balazs.csaba |
2013:groups:tools:dlha [2013/06/20 17:07] balazs.csaba |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ==== People involved ==== | ==== People involved ==== | ||
| - | Alexandre, Andreas, Ben, Benj, Björn, Csaba, Fawzi, Geneviève, Nazila, Sasha, Sezen, Pietro, ... | + | * Present at Les Houches: Alexandre, Andreas, Ben, Benj, Björn, Csaba, Fawzi, Geneviève, Nazila, Sasha, Sezen, Pietro |
| + | * Outside of Les Houches: Ben Allanach, David Cerdeno, Peter Skands, & 50+ other people representing various dark matter calculators. | ||
| ==== Useful links ==== | ==== Useful links ==== | ||
| Line 20: | Line 21: | ||
| * As long as we agree about the blocks defined in the LH11 proceedings, we could try to implement those as a first (and simplest) step to see how things go. | * As long as we agree about the blocks defined in the LH11 proceedings, we could try to implement those as a first (and simplest) step to see how things go. | ||
| * We should clarify the role and aim of the functions. Functions were introduced to mediate information that is more complex than just a set of independent numerical values. However as it is there are various roles for functions. They | * We should clarify the role and aim of the functions. Functions were introduced to mediate information that is more complex than just a set of independent numerical values. However as it is there are various roles for functions. They | ||
| - | * define complex inputs (such as a dark matter spatial distribution) in an abstract, pre-agreed way: | + | * define function inputs (such as a dark matter spatial distribution) in an abstract, pre-agreed way: |
| * ''FUNCTION rho_g type=P args=2 | DLHA rho_g 5 | END_FUNCTION'' | * ''FUNCTION rho_g type=P args=2 | DLHA rho_g 5 | END_FUNCTION'' | ||
| * allow the user direct access to existing methods within the codes: | * allow the user direct access to existing methods within the codes: | ||
| Line 32: | Line 33: | ||
| ==== 2nd discussion ==== | ==== 2nd discussion ==== | ||
| - | |||
| * Blocks should only contain numerical info where the entries are independent from each other. (This is how SLHA works.) | * Blocks should only contain numerical info where the entries are independent from each other. (This is how SLHA works.) | ||
| * A separate TABLE object should be defined as a specific I/O format for functions. | * A separate TABLE object should be defined as a specific I/O format for functions. | ||
| * In the function definitions we have to fix the content of the tables. | * In the function definitions we have to fix the content of the tables. | ||
| - | * The table header will look like this: | + | * The table header should look like this: |
| * TABLE <name> <column> <row> | * TABLE <name> <column> <row> | ||
| * The name will probably be inherited from the function | * The name will probably be inherited from the function | ||
| Line 43: | Line 43: | ||
| * Parameters should be moved out of functions. | * Parameters should be moved out of functions. | ||
| - | ==== Things to do ==== | + | ==== 3rd discussion ==== |
| + | * micrOmegas includes an SLHA reader/writer which could be generalized for DLHA. | ||
| + | * A stand-alone version is published in [[http://arxiv.org/abs/arXiv:1008.0181|arXiv:1008.0181]]. | ||
| + | * There's a problem with trying to agree upon the I/O of existing functions in existing codes, because this would restrict coding. This problem arises when directly accessing existing methods within existing codes, such as: | ||
| + | * ''FUNCTION <name> type=<type> args=<# of args> | libName=<name of compiled library> | funcName=<name of function in library> | END_FUNCTION'' | ||
| + | * Agreement about the I/O of these directly accessed functions could tie the hands of the author(s) of the original code. | ||
| + | ==== 4th discussion ==== | ||
| + | * A DLHA reader/writer prototype can be created based on SLHA+. | ||
| + | * FUNCTION I/O should happen via arrays. | ||
| + | * We should consider agreeing about the I/O of existing methods in existing calculators. (For abundance, direct or indirect detection calculations, for example.) Then the authors of the codes could distribute a pre-compiled Linux library from which these methods could be called directly based on DLHA. | ||
| + | * We should specify the number of significant figures (16 was suggested) for numerical values. | ||
| + | |||
| + | ==== Things to do ==== | ||
| * The write-up has to be updated to reflect the changes we decide to make at LH13. | * The write-up has to be updated to reflect the changes we decide to make at LH13. | ||
| * ... | * ... | ||
2013/groups/tools/dlha.txt · Last modified: 2013/06/20 17:24 by balazs.csaba
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
