Addition of Memory Protection at code start, Major Changes to Documentation, & Changes to Code Organisation - Preparation for BETA release:
1) Memory Protection: Addition of checks for whether code will be able to run on the available free system memory using the provided parameters. If not, it attempts to enable running by lowering the number of threads. If this fails, then stop & suggest change to 'crop' options.
2) Checking for Binary Write Limitations: The writeBin() function is limited to writing arrays of 2^23-1 bits. As such, if the image is greater than this (~4Gb), attampting to write images will cause code to break. To stop this, the program checks the size of the largest image, and if it is greater than 2^32-1 then the program warns the user and forces no image output.
3) Documentation has been updated
4) Code has been reorganised, commented more extensively, and generally cleaned up.

Note: groupings of 3 commented braces, #{{{ /  #}}}, are fold markers used in vim. The code can be opened in vim and folded/unfolded for ease of viewing psuedocode only, individual section of code & psuedocode, or just for determining which comments are relevant to which sections.
Merging with changes made on GitHub - addition of Minimium Aperture Radius

Merge branch 'master' of https://github.com/AngusWright/LAMBDAR

Conflicts:
	R/MeasureFluxes.R
	R/readparfile.R
	man/MeasureFluxes.Rd