ToDo-List

Documentation

Responsibilities for PALM-internal workshop 2017 are marked in red color

Page (e. g. wiki/doc/app/userint)	What to do?	Name
wiki/doc/app/jobcontrol	Restructure mrun documentation
wiki/doc/tec/mbuild	Description of mbuild
wiki/doc/tec/subjob	Description of subjob
wiki/doc	more clear structure for wiki/doc
wiki/doc/tec/1d_model	Description of 1d model
wiki/doc/tec/cloud_physics	Description of cloud physics module
wiki/doc/app/errmsg	complete explanations for PALM error messages, check all existing explanations (are they correct?, are they obsolete?)	Simon and Sebastian with help from others
<page>	Links from manual to tutorial
<page>	Write descriptions for exercises 6-14 (divide all exercises into Tutorial exercises and Advanced exercises), Advanced examples->Research project examples
wiki/doc/	Description of statistical methods (computation of fluxes and variances, horizontal averaging, etc.)
wiki/doc/tec/wtm	Write documentation for wind turbine parametrization code	Björn Witha
	Add additions/correction page for the Maronga et al. 2015 paper so that we can incorporate them in the next model description paper

PALM seminar improvements (for 2017) mainly Farah

Item	What to do?	Name
Lecture handouts	Separate binding for lectures and exercises
Name tags	Name tags for participants. Provide PALM T-Shirts and/or name tags for lecturers / exercise advisors
Exercise solutions	After some time into the exercise sessions, participants should receive solutions for the input files in order to be able to produce and analyse some results
Group photo
Exercises	Reduce the runtime of the exercises and test the computational time with gfortran as participants often use this compiler on their noteboeoks.
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 exlusively and include profiles, e.g. for pt this then would read "pt", "pt_xy", "pt_pr", etc.
Default FFT solver	The default is currently "system-specific", but on some notebooks of the user there was no FFT library available. The default should thus be changed to the Temperton FFT
dt_dots	Description in the documentation should be revised (default value)
data output steering	User find it confusing that they have to specify the data output in the parameter file (e.g. for xy and 3d output) and then switch data output on AGAIN in the mrun call. Maybe we can find a more convenient solution?
mrungui	So far we have not used the mrungui within the seminar, although it might be quite convenient tool for users.
...

Source Code

Program parts	What to do?	Name
	develop new GUI for parameter file generation
mrun, subjob	allow batch-job-directives (e.g. PBS) and execution commands (mpiexec, aprun, etc.) to be configured using entries in .mrun.config	Siggi
mrun, subjob, mbuild	cleaning	Siggi
PALM code	code clearing and restructuring following programmer guidelines of DWD/DMI	all, Siggi
PALM code	Add description for all variables/quantities used in PALM according to doxygen syntax, most important is file modules.f90	Farah
	- move initialization from init_3d_model to the respective modules
<page>	Avoid collecting of 2D data on PE0 (topography data, surface coupling layer)
<page>	Subgrid-scale saturation fluctuation for Lagrangian cloud model	Fabian
	implementation of a tracbot, which automatically runs and checks examples in case of any code changes
data_output	implement output of hydrostatic pressure (already done?)	Helge
data_output	implement output of scalar and momentum fluxes calculated by temporal EC
PALM code	Create temporary job sub-directories via mrun (does not work properly with the FORTRAN system call function)
PALM code	Discuss the treatment of package parameters, regarding their appearance in read_var_list and write_var_list. Discuss the general treatment / separation of inipar and d3par parameters.	all
Example runs	Modify the "building" example run (example_building_p3d), since topography is allowed with WS-scheme
PALM code	For reference_state='horizontal_average' round the averaged profile (e.g. 3.3 digits) to make runs repeatable
PALM code	Avoid repeating code blocks in data_output routines and use subroutines instead
PALM code	Avoid unnecessary grid checks when using multi grid solver	??
PALM code	Implement Johannes' splitting and merging algorithm for Lagrangian particles	Johannes
PALM code	make simple random number generator available for general usage	Fabian
PALM code	Implement and homogenize output of cloud-physical variables derived from bulk and Lagrangian cloud physics (e.g., qc, ql, qr, lpt, pt)	Fabian
PALM code/ documentation	Change the name specific humidity to mixing ratio! We don't compute specific humidities.	Fabian
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, ...)
data_output	When calculating vertical cross sections averaged along x or y, leave out topography
data_output	Do not output ghost points
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).
PALM code	define dimensions of data_output, data_output_pr, etc. as variables (avoid fixed numbers in code)
PALM code	Implement synthetic turbulence generation method	Tobias
PALM code	Implement a more flexible y-shift method for non-cyclic but also for cyclic runs	Tobias
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)))	Fabian
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)	Fabian
PALM code	Implement PALM error messages in parallel random number generator module	Helge
mrun / data output	Use same cycle number for all output files	Siggi
PALM code	Review summation of "1E-5_wp" in lines 164/167 in diffusivities.f90 (r2119), see ticket:393
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
data_output	Set missing values/fill values inside topography and define these missing values as attributes in NetCDF file.
mrun, .mrun.config	allow for a different name and directory for the "job_queue" folder	Siggi
PALM code	for consistency reasons, implement "initial gradient" top boundary conditions for the mixing ratio too	Fabian
RRTMG coupling	allow for dry runs with RRTMG (might lead to unrealistic results if the atmosphere is considered totally dry!)	Björn
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
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.
LSM	adjustments	Björn

Code performance

	define setups for scaling / benchmark runs	Björn, Siggi, Fabian
	carry out runs to determine PALM's weak/strong scaling behaviour + parallel efficiency, this might be good to be carried out during the test phase of the HLRNIV	?
<page>	<what>	<name>

Ticket system

Revision number

Add possibility to enter revision number in ticket header, currently only PALM version is available

Farah

Tools

-	new plotting tool to replace palmplot	Christoph + Hiwi
-	revision of document_changes to be called only once	Björn
-	extend PALM grid finder for nesting configurations	Hiwi
-	development and implementation of an automatic mechanism to test source code modifications	Helge