Changes between Version 122 and Version 123 of todo

Timestamp:

Sep 20, 2017 9:14:45 AM (7 years ago)

Author:

kanani

Comment:

--

todo

@@ -38 +38 @@
 
 ||='''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.  ||  ||
 ||palmplot || Make palmplot compatible with latest NCL versions ||  ||
 ||... ||  ||  ||
@@ -78 +70 @@
 || data_output || When calculating vertical cross sections averaged along x or y, leave out topography || ||
 || data_output || Do not output ghost points || ||
+||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? ||  ||
 || 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) || ||