2010-11-11 : new examples into Makefile for Python
2010-11-11 : added a flag that says need to cal cmor_grid on some axis (site and location)

2010-11-05 : removed option, for now, to create non-standard calendars because the dates in filenames would be wrong.

2010-11-05 : reverted ext_cell_measures to cell_measures

2010-10-27 : edited the test for permission on output directory, used to fail if you had group write privileges but that wasnt your main group

2010-10-22 : exposed cmor_set/get/has_variable in Fortran interface, just like Python works only on "string" variables
2010-10-22 : add optional "parent_experiment_rip" to cmor_dataset (C,Fortran,Python)
2010-10-22 : fixed bug with variables using "grids" and singleton dimensions
2010-10-22 : upgraded to 2.4 in devel branch
2010-10-22 : exposed cmor_set_variable_attribute to users in Python
2010-10-22 : cell_measures var attribute is now called ext_cell_measures

2010-10-22 : upgraded to 2.4 in devel branch
2010-10-22 : exposed cmor_set_variable_attribute to users in Python
2010-10-22 : cell_measures var attribute is now called ext_cell_measures

Merge branch 'master' into devel

Conflicts:
	include/cmor.h

2010-09-29 : Cleaned up error messages, now tries to output var/axis it was working on as well as table used.
2010-09-29 : When value that exceeds valid_min/max is found, now returns location of extreme point instead of first point encountered, as well as actuall coordinates values (not just indices)
2010-09-22 : Joerg found a bug that was due to checking only the refvar.dimension w/o checking the actual tables as well
2010-09-01 : fixed a bug on mac 32bit when reading in net3 version string
2010-09-01 : some vars with grid and singleton dims were wrongly analyzed by cmor_variable has not being defined with the right number of dimmensions.
2010-09-01 : updated doc. Was saying you can pass "none" for units when it really is: ""
2010-09-01 : updated doc. Was wrongly stating you can pass "none" if no missing_value
2010-08-24 : when writing time only variables, the time_bnds would fail to write if passed at cmor_write time.

2010-09-29 : Cleaned up error messages, now tries to output var/axis it was working on as well as table used.
2010-09-29 : When value that exceeds valid_min/max is found, now returns location of extreme point instead of first point encountered, as well as actuall coordinates values (not just indices)

Fixed Joerg's bug, had to do with checking only for the refvar dimension w/o also checking it's coming from the right table

2010-08-24 : when writing time only variables, the time_bnds would fail to write if passed at cmor_write time.

2010-09-01 : some vars with grid and singleton dims were wrongly analyzed by cmor_variable has not being defined with the right number of dimmensions.
2010-09-01 : updated doc. Was saying you can pass "none" for units when it really is: ""
2010-09-01 : updated doc. Was wrongly stating you can pass "none" if no missing_value

2010-08-24 : when writing time only variables, the time_bnds would fail to write if passed at cmor_write time.

2010-08-23 : create_output_path doesn't need to be called b4 cmor_write any more.

not creating directory when caling this and CMOR_CREATE_SUBDIRECTORIES is set off, now with the correct value for the flag...

2010-08-19 : go thru cmor_create_path to figure out isfixed and set frequency, even if directory layout is not required.
2010-08-19 : checker: works with version number of format major.minor.patch
2010-08-19 : checker: update git url from wich to fetch md5s tables
2010-08-19 : forcings attribute can now end with notes in between parenthesis

2010-08-18 : downgraded abs min/max CRITICAL error to NORMAL
2010-08-18 : dowgraded invalid min/max from NORMAL error to WARNING
2010-08-10 : cmor_setup, was initalizing strings beyhond the max number fo elts, cause seg fault with python (loop was to CMOR_MAX_ELEMENTS when it should have been CMOR_MAX_ATTRIBUTES)