Difference between revisions of "Category:Pragmatic Programming"

From SourceWiki
Jump to navigation Jump to search
Line 35: Line 35:
 
==Topics==
 
==Topics==
  
 
+
* [http://source.ggy.bris.ac.uk/wiki/Parallel Parallel programming using OpenMP]
<!--
 
* [[Linux1|Linux1]]
 
* [[Fortran1|Fortran1]]
 
* [[StartingC|StartingC]]
 
* [[CtoC++|CtoC++]]
 
* [[Linux2|Linux2]]
 
* [[Fortran2|Fortran2]]
 
* [[Fortran3|Fortran3]]
 
* [[Condor|Condor]]
 
* [[Make|Make]]
 
* [[Debugging|Debugging]]
 
* [[Subversion|Subversion]]
 
* [[Profiling|Profiling]]
 
* [[Numerics|Numerics]]
 
* [[Parallel|Parallel]]
 
* [[Polyglot|Polyglot]]
 
* [[UsingNetCDF|Using NetCDF]]
 
* [[UsingSSH|Using SSH]]
 
-->
 

Revision as of 14:56, 20 September 2013

Rationale

"Pragmatic Programming" is a course which was designed for new postgraduate students postdocs and members of staff alike.

It is designed to address two key issues:

  • The first pertains to the word 'science' and the key tenet of reproducibility. A well engineered model will be robust to a change of hardware or compiler. Too often, however, we find that running a model developed by one research group on the systems of another yields different results. How much are we to trust results which we cannot replicate? Not to mention the time wasted trying to track down the cause of the discrepancy. This considerations carry particular weight when model results are used to inform environmental policy in the face of climate change.
  • The second reason is that we simply cannot bear the cost of an ill-considered approach to model development. Time is money and grappling with poorly engineered, or simply un-designed models wastes huge amounts of time. One science experiment is often a slight variant upon another. Well engineered code can be quickly adapted for a following experiment. However, a change to Heath Robinson style creations which we often witness can present an impasse which requires huge efforts to overcome. Imagine this situation repeated hundreds of times over and a sobering waste of resources comes to mind. And this is before we contemplate the cost of tracking down bugs.

Course content

Foundations

  1. Linux1: Linux for beginners.
  2. Linux1: More advanced Linux.
  3. Linux1: Starting administration.

languages

Tools

  1. Performance Analysis and Debugging provide tips to help you find and improve any slow running regions of your program; and hints and tips for avoiding, finding and correcting any bugs that find their way into your code.
  2. The Subversion version control system is fantastic tool for collaborating, debugging, disaster recovery and, well, general sanity preservation!. This tutorial gives you hands on practice for all the essential features.
  3. Project building using Make guides you step-by-step through the otherwise opaque magic of Makefiles and highlights how they can be brought into service not only for code compilation, but also for automatic documentation creation and program testing. The combination of Subversion and Make opens the door to a nightly build for your project--a proven way to catch and correct bugs.

Topics