% Missing parts:

% - point to users' guide
% - more on thorn documentation (doc subdirectory, latex)
% % - explain information on web site: download, configure

% - hyperslabbing, reduction, interpolation
% % - I/O system, analysis, triggers
% - syntax of parameter files
% - how to start a simulation

% - test suites
% - nightly build tests, portal.cactuscode.org

% - 3D I/O, HDF5
% - more visualisation

% - CCTK_REAL, CCTK_INT (choose exact type at configuration time)
% - brief introduction to AMR, multi-block
% - show eternal wavetoy
% - have images from simulations
% - Twitter, Flickr

% Other comments:

% - Section names on slides take up much space

% Comments taken while giving the tutorial:
% 
% explain ccl files starting from a motivating physics example?
% 
% add more graphs and figures to the slides
% 
% parallelism: add more introductory material, suitable for people who
% don't know; state that the thorns are not involved in parallelism
% 
% explain the driver earlier
% 
% Cactus: explain its target audience earlier (at least for the purpose
% of this tutorial): 3D PDE time evolution
% 
% explain grid functions
% 
% what is a ``simulation''?
% explain these basic concepts early in the slides
% 
% for the list of frameworks: don't just list them, say what they are
% used for: who knows all of them?
% 
% in the examples: explain CCTK_Info, CCTK_Warn; explain cctkGH
% 
% thorn architecture: add examples as well for src, doc, par, test,
% 
% add transition slides between the sections, giving the presentor a way
% to pause, get feedback
% maybe have introduction and wrapup slides for each section
% 
% provide example tarballs and instructions as html on the cactus web
% site
% 
% define the target audience for this tutorial:
% - HPC beginners?
% - physicists?
% - computer scientists?
% - in the ICCS tutorial, it was about 50/50 physicists and computer
%   scientists, no beginners
% 
% show more screen output overall:
% - schedule at startup
% - example info output
% - ``typical'' parameter file
% 
% in the examples: don't show the schedule of the real wavetoy, it is
% too complicated
% -> create simple wavetoy
% 
% leave out certain (deprecated) details:
% - global parameters
% - friends, protected groups
% 
% the beginning of the tutorial is too abstract.
% - explain the abstract frameworks concepts later
% - begin with practical considerations about HPC, simulations
% - in general, speak more about HPC, physics etc. as motivation in the
%   beginning
% 
% thorn writing:
% - explain CCTK_ARGUMENTS, DECLARE_CCTK_..., CCTK_GFINDEX, etc.
% 
% give the hands-on demostration running in parallel to make things more
% interesting
% 
% IDEA:
% - always have an interactive part of the tutorial
% - keep 10 ``cactus'' logins with pre-prepared accounts around, e.g. on
%   Queen Bee, or on another system (numrel workstation?)
% 
% explain the layout of the Cactus source tree
% explain existing arrangements, basic thorns in more detail
% 
% % add examples for a CFD toolkit?
% 
% when giving examples: begin with the physics, explain it also for
% non-physisits and non-PDE people, have a figure, don't start with just
% equations
% 
% in the hands-on demonstration: have more structure, have a specific
% list of items to show
% 
% have purely local (notebook) configurations for VisIt, Cactus, HTTPD,
% MPI (for parallel runs), etc.
% 
% give brief introduction to VisIt, gnuplot (for people who don't know
% visualisation tools)
% 
% Other things to show during a tutorial:
% - show Scale 2009 movie
% - show Cactus web site
% - show eternal WaveToy (and interact with simulation; login/password
%   is guest/guest)
% - show portal.cactuscode.org (nightly build tests)
% - Twitter?  Flickr?
% - show AMR movie?