Changes between Version 137 and Version 138 of todo


Ignore:
Timestamp:
Mar 25, 2018 9:21:54 AM (7 years ago)
Author:
maronga
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • todo

    v137 v138  
    1313||Web docu     ||Update links from manual to Tutorial (new: PALM seminar material) ||tba ||
    1414||Web docu     ||Revise description of timeseries output ||tba ||
    15 ||             ||                                        ||    ||
    1615||Tickets      ||Sort tickets of component "General" into appropriate components (change title and keywords where needed, create new components where necessary) ||tba ||
    17 ||             ||                                        ||    ||
    1816||PALM code    ||Check for double-use of error numbers ||tba ||
    1917||PALM code    ||Clean up / extend location messages ||tba ||
     
    2725||Discussion   ||Parameter file inconsistencies. Settings for data output are not consistent within the parameter file. For example, 3d/2d/pr output variables are explicitly declared, but timeseries are always the same (confusing for users). Also, differentiation between data_output and data_output_pr is confusing. A possible solution would be to use data_output exclusively and include profiles, e.g. for pt this then would read "pt", "pt_xy", "pt_pr", etc. ||group ||
    2826||Discussion   ||Discuss the treatment of package parameters, regarding their appearance in {{{rrd_global}}} and {{{wrd_global}}}. Discuss the general treatment / separation of {{{inipar}}} and {{{d3par}}} parameters. ||group  ||
     27||PALM code    ||Revise variable/dimension names and attributes in the NetCDF data input and PIDS input according to the [UC]² data policy ||tba ||
     28||PALM code    ||Add georeferencing (lat/lon) and global attributes according to [UC]² data policyto NetCDF output ||tba ||
     29
    2930
    3031
     
    9899|| PALM code || discuss using Fortran Intrinsic Function "SUM" instead of loops as done many times in the code || all (KS) ||
    99100||initializing_actions|| discuss use of initializing_actions='user', because its usage requires good code knowledge and the advantage over using 'set_constant_profiles' and later overwriting variables in user_init_3d_model.f90 is not clear || all (KS) ||
     101||PALM code    ||Revise Fortran NAMELIST names (e.g. &inipar --> &initialization_parameters)||Björn ||
    100102\\
    101103== Code performance==