Changes between Version 143 and Version 144 of todo
- Timestamp:
- Apr 6, 2018 11:56:16 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
todo
v143 v144 18 18 ||PALM code ||Clean up / extend location messages ||tba || 19 19 ||PALM code ||Comment variables/parameters in declaration sections ||tba || 20 || || || ||21 20 ||PALM code ||Known bug: W* and Z_I in the first line of the run control file don't correspond to the values in the last run control output line of the previous run. ||tba || 22 ||PALM code ||Known bug: Restart crashes in sum_up_3d_data if an {{{_av}}} quantity is given in the restart run NAMELIST file (_p3dr) but not in the initial run NAMELIST file (_p3d) --> Implement check?! || tba||21 ||PALM code ||Known bug: Restart crashes in sum_up_3d_data if an {{{_av}}} quantity is given in the restart run NAMELIST file (_p3dr) but not in the initial run NAMELIST file (_p3d) --> Implement check?! || || 23 22 || || || || 24 23 ||Scripts ||Finalize first version of new palmplot script (python) ||Helge || 25 24 ||Scripts ||Remove deprecated vapor scripts ||Tobias || 26 || || || 27 ||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 ||28 ||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||25 || || || || 26 ||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. \\ [[span(style=color: #FF0000, I would leave this as it is. Several quantities only exist as profiles, so it don't make sense to add a _pr to all of them. It should be enough to add (better) hints in the docu. Siggi)]] ||group || 27 ||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. || [[span(style=color: #FF0000, Sebastian / work in progress)]] || 29 28 ||PALM code ||Revise variable/dimension names and attributes in the NetCDF data input and PIDS input according to the [UC]² data policy ||tba || 30 29 ||PALM code ||Add georeferencing (lat/lon) and global attributes according to [UC]² data policyto NetCDF output ||tba || … … 36 35 ||='''Page (e. g. wiki/doc/app/userint)''' =||='''What to do?''' =||='''Name''' =|| 37 36 ||wiki/doc/tec/1d_model ||Description of 1d model || || 38 ||wiki/doc/tec/cloud_physics ||Description of cloud physics module || ||37 ||wiki/doc/tec/cloud_physics ||Description of cloud physics module || [[span(style=color: #FF0000, Johannes)]] || 39 38 ||<page> ||Write descriptions for exercises 6-14 (divide all exercises into Tutorial exercises and Advanced exercises), Advanced examples->Research project examples || || 40 39 ||wiki/doc/ ||Description of statistical methods (computation of fluxes and variances, horizontal averaging, etc.) || || … … 61 60 || ||develop new GUI for parameter file generation || || 62 61 ||PALM code ||code clearing and restructuring following programmer guidelines of DWD/DMI ||[[span(style=color: #FF0000, all, Siggi )]] || 63 ||<page> ||Avoid collecting of 2D data on PE0 (topography data, surface coupling layer) || ||64 ||<page> ||Subgrid-scale saturation fluctuation for Lagrangian cloud model || Fabian||62 ||<page> ||Avoid collecting of 2D data on PE0 (topography data, surface coupling layer) || [[span(style=color: #FF0000, Matthias)]] || 63 ||<page> ||Subgrid-scale saturation fluctuation for Lagrangian cloud model ||[[span(style=color: #FF0000, Johannes)]] || 65 64 ||data_output ||implement output of scalar and momentum fluxes calculated by temporal EC || || 66 65 ||PALM code ||Create temporary job sub-directories via mrun (does not work properly with the FORTRAN system call function) || || 67 ||Example runs ||Modify the "building" example run (example_building_p3d), since topography is allowed with WS-scheme || ||68 ||PALM code ||For reference_state='horizontal_average' round the averaged profile (e.g. 3.3 digits) to make runs repeatable || ||66 ||Example runs ||Modify the "building" example run (example_building_p3d), since topography is allowed with WS-scheme || [[span(style=color: #FF0000, Tobias)]] || 67 ||PALM code ||For reference_state='horizontal_average' round the averaged profile (e.g. 3.3 digits) to make runs repeatable || [[span(style=color: #FF0000, Siggi)]] || 69 68 ||PALM code ||Avoid repeating code blocks in {{{data_output}}} routines and use subroutines instead || || 70 69 ||PALM code ||Avoid unnecessary grid checks when using multi grid solver ||?? || 71 70 ||PALM code ||Implement Johannes' splitting and merging algorithm for Lagrangian particles ||[[span(style=color: #FF0000, Johannes)]] || 72 ||PALM code ||make simple random number generator available for general usage || [[span(style=color: #FF0000, Fabian)]] ||73 || PALM code || Implement and homogenize output of cloud-physical variables derived from bulk and Lagrangian cloud physics (e.g., qc, ql, qr, lpt, pt) || [[span(style=color: #FF0000, Fabian)]] ||74 ||PALM code/ documentation ||Change the name specific humidity to mixing ratio! We don't compute specific humidities. || [[span(style=color: #FF0000, Fabian)]] ||71 ||PALM code ||make simple random number generator available for general usage || [[span(style=color: #FF0000, Johannes )]] || 72 || PALM code || Implement and homogenize output of cloud-physical variables derived from bulk and Lagrangian cloud physics (e.g., qc, ql, qr, lpt, pt) || [[span(style=color: #FF0000, Johannes )]] || 73 ||PALM code/ documentation ||Change the name specific humidity to mixing ratio! We don't compute specific humidities. || [[span(style=color: #FF0000, Johannes )]] || 75 74 || data_output || In profile output define zu and zw only once instead of define a vertical dimension for each individual variable (e.g. zpt, zw"u, zw"v, ...) || || 76 75 || data_output || When calculating vertical cross sections averaged along x or y, leave out topography || || 77 || data_output || Do not output ghost points (still done in masked output) ||||78 || PALM code || Separate option "cyclic_fill" from restart run to avoid unwanted effects (e.g. surface heat flux value in namelist of a run using "cyclic_fill" will always be overwritten by the value used in the precursor run). || ||76 || data_output || Do not output ghost points in masked output ||[[span(style=color: #FF0000, Siggi)]] || 77 || PALM code || Separate option "cyclic_fill" from restart run to avoid unwanted effects (e.g. surface heat flux value in namelist of a run using "cyclic_fill" will always be overwritten by the value used in the precursor run). ||[[span(style=color: #FF0000, Björn / Tobias)]] || 79 78 || PALM code || define dimensions of data_output, data_output_pr, etc. as variables (avoid fixed numbers in code) || || 80 || PALM code || Implement a more flexible y-shift method for non-cyclic but also for cyclic runs || Simon||81 || PALM code || Particle code: unify allocation of particle arrays within lpm_droplet_collision, lpm_droplet_condensation, ... (REAL(wp), DIMENSION(:), ALLOCATABLE or REAL(wp), DIMENSION(prt_count(k,j,i))) ||[[span(style=color: #FF0000, Fabian)]] ||82 || PALM code || Use only one Magnus formula within the code (not several as in microphysics.f90, lpm_droplet_condensation.f90, calc_liquid_water.f90, land_surface_model.f90) ||[[span(style=color: #FF0000, Fabian)]] ||79 || PALM code || Implement a more flexible y-shift method for non-cyclic but also for cyclic runs || [[span(style=color: #FF0000, Simon)]] || 80 || PALM code || Particle code: unify allocation of particle arrays within lpm_droplet_collision, lpm_droplet_condensation, ... (REAL(wp), DIMENSION(:), ALLOCATABLE or REAL(wp), DIMENSION(prt_count(k,j,i))) ||[[span(style=color: #FF0000, Johannes)]] || 81 || PALM code || Use only one Magnus formula within the code (not several as in microphysics.f90, lpm_droplet_condensation.f90, calc_liquid_water.f90, land_surface_model.f90) ||[[span(style=color: #FF0000, Johannes)]] || 83 82 || PALM code || Implement PALM error messages in parallel random number generator module ||[[span(style=color: #008000, Helge)]] || 84 || PALM code || Review summation of "1E-5_wp" in lines 164/167 in diffusivities.f90 (r2119), see ticket:393 || ||83 || PALM code || Review summation of "1E-5_wp" in lines 164/167 in diffusivities.f90 (r2119), see ticket:393 ||[[span(style=color: #FF0000, Tobias)]] || 85 84 || data_output || Make use of already implemented 'long_name' attribute of variables, i.e. give possibility to assign a long_name for user defined variables || || 86 || data_output || Set missing values/fill values inside topography and define these missing values as attributes in NetCDF file. || ||85 || data_output || Set missing values/fill values inside topography and define these missing values as attributes in NetCDF file. ||[[span(style=color: #FF0000, Matthias)]] || 87 86 || data_output || Make proper use of global attributes; especially do not write time average interval in title if there exists a specific attribute ({{{time_avg}}}) for this. || || 88 || PALM code || for consistency reasons, implement "initial gradient" top boundary conditions for the mixing ratio too ||[[span(style=color: #FF0000, Fabian)]] ||87 || PALM code || for consistency reasons, implement "initial gradient" top boundary conditions for the mixing ratio too ||[[span(style=color: #FF0000, Johannes)]] || 89 88 || RRTMG coupling || allow for dry runs with RRTMG (might lead to unrealistic results if the atmosphere is considered totally dry!) ||[[span(style=color: #FF0000, Björn)]] || 90 || 1d-model || fix 1d model to work without Coriolis force || ||91 || PALM code || allow more flexible vertical grid stretching, e.g. for having near-surface stretching, constant grid spacing above and again stretching in the free atmosphere || ||92 || check parameters || with psolver=multigrid, check that the subdomains can be divived by 2 at least once (see documentation of the multigrid). Is this still a problem? Needs to be checked. || ||93 ||Spectra output || Check and possibly revise spectra normalization with wavenumber || ||94 ||Initialization || It needs to be clarified that the initial wind profile constructed by ug_surface, ug_vertical_gradient etc. describes the forcing by the geostrophic wind (pressure gradient), and at the same time depicts the initial actual-wind profile. ||||95 ||PALM scripts || Not all SCRIPTS bash based yet. || ||89 || 1d-model || fix 1d model to work without Coriolis force [[span(style=color: #FF0000, why is this required? Siggi)]] || || 90 || PALM code || allow more flexible vertical grid stretching, e.g. for having near-surface stretching, constant grid spacing above and again stretching in the free atmosphere ||[[span(style=color: #FF0000, Sebastian)]] || 91 || check parameters || with psolver=multigrid, check that the subdomains can be divived by 2 at least once (see documentation of the multigrid). Is this still a problem? Needs to be checked. ||[[span(style=color: #FF0000, Siggi)]] || 92 ||Spectra output || Check and possibly revise spectra normalization with wavenumber ||[[span(style=color: #FF0000, Matthias)]] || 93 ||Initialization || It needs to be clarified that the initial wind profile constructed by ug_surface, ug_vertical_gradient etc. describes the forcing by the geostrophic wind (pressure gradient), and at the same time depicts the initial actual-wind profile. [[span(style=color: #FF0000, just add better hints in docu)]]||[[span(style=color: #FF0000, Siggi)]] || 94 ||PALM scripts || Not all SCRIPTS bash based yet. ||[[span(style=color: #FF0000, Helge)]] || 96 95 ||palmrun || make working directory independent from installation directory || Siggi || 97 ||NAMELISTs || it should be possible to give output levels in real coordinates (m) instead of grid level, output should then be done for the nearest grid point || ||96 ||NAMELISTs || it should be possible to give output levels in real coordinates (m) instead of grid level, output should then be done for the nearest grid point ||[[span(style=color: #FF0000, Sebastian)]] || 98 97 || data_output || all output checks should be done BEFORE the first time step, and not when the first output is done || || 99 98 ||Nesting output || additional output of nesting information is required (e.g. in header): for root domain: number of nested domains, name of nested domains, number of nesting levels; for each domain: position of the nest domains given in grid index number range, e.g. (20..40,10:15), also position of lower left corners in physical coordinates? || || 100 99 || PALM code || routine {{{global_min_max}}} does not work for mode 'min', 'max', and 'minmax'. || Tobias || 101 100 || PALM code || discuss using Fortran Intrinsic Function "SUM" instead of loops as done many times in the code || all (KS) || 102 ||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 ||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 [[span(style=color: #FF0000, just give better explanations in the docu. Siggi)]]|| all (KS) || 103 102 ||PALM code ||Revise Fortran NAMELIST names (e.g. &inipar --> &initialization_parameters)||Björn || 104 103 ||PALM code ||Revise vertical loops in plant-canopy model in order to get rid-off 2D-index array pch_index ||Matthias || … … 110 109 \\ 111 110 == Tools== 112 ||- ||new plotting tool to replace palmplot ||Christoph + Hiwi||111 ||- ||new plotting tool based on python to replace palmplot ||[[span(style=color: #FF0000, Helge)]] || 113 112 ||- ||extend PALM grid finder for nesting configurations ||Hiwi || 114 113 ||- ||tool for finding vertical grid configuration with grid stretching (maybe as part of palm_gf) || Katrin+HiWi ||
