The parallel version of the radiation fields was not working properly (wrong geolocalization for the domain band). The documentation has also been updated.

Finally, this is the implementation of issue 340: distributed cloudiness (through atmospheric loss factor and splitting coefficient). This mostly follows the lines of what has been recently implemented in MeteoIO with a few tricks to perform domain decomposition when running in parallel (either MPI or OpenMP).  as well as benefit from Snowpack's albedo feedback. In the first tests, when commenting out this albedo feedback and forcing horizontal components, it performs exactly the same as MeteoIO's implementation.

Since there is no meteo1d object anymore, Snowdrift had to be modified so it can extract what it needs from a vector of MeteoData. An hopefully better implementation of Snowdrift without slatation is also included.

Much more flexible view.sh script, it can now be called from anywhere and should properly find its associated jar file. The glacier.cc calibration tool has been expanded with a few extra possible outputs.

The criterias used in checkKatabaticFlows have been changed in order to now count the number of snowfree cells outside the glacier and the number of glacier cells experiencing proper conditions for katabatic flows. The code has been modified to better handle nodata cells in the domain: now glaciated cells are marked with 1, non-glaciated with 0 and nodata remain nodata.

Code cleanup in Glaciers. In SnowpackInterface, a warning is printed out if a requested grid can not be found. Moreover, a logic bug was found when handling dynamic glacier masks: the mask was only refreshed when doing the outputs. Now it is refreshed at each time step and properly provided to Glaciers (otherwise it was providing a default, no glacier mask and therefore the katabatic flow correction was never activated). A new grid has been defined: GLACIER_EXPOSED for future usage. In RadiationField, the horizon is now computed by calling the matching MeteoIO method from DEMObject (that is exactly the same as the previous method).

Updating the syntax of the io.ini; using the atmospheric correction logic from mio::Sun() instead of the local one (ie making the code simpler) and relying or nodata checks done in meteoio instead of redoing them in RadiationField.

Fixed some documentation issues, lowered the thresholds to turn on the katabatic flows correction, swapped the linking order of Snowpack and MeteoIO in order to easily allow to use a system-wide MeteoIO with a locally installed Snowpack

Added a define to run snowdrift without computing the saltation (it is then highly recommended to also turn off the sublimation!). Created a small piece of code to test/calibrate the glacier katabatic flows correction.

Small code cleanup, better comments and added the ability to scale the flow reach in the katabatic flow modeling

The latest changes in Snowpack have been reflected in SnowpackInterface. The new way of setting the compiler options has been imported and tweaked from meteoIO. In order to mave closer to the "efficient c++" recommendations, several changes have been made in the rest of the classes (mostly defining a few copy constructors and "=" operators).

The "--no-compute" option has been extended in order to help calibrating the glacier katabatic flows correction. This is far from perfect, but it is a start... A minor bug has been fixed in pt_extract.cc

The improvements to the katabatic flows corrections by (Ayala et al., 2015) have been implemented. A more flexible "debug" output has been implemented in Snowdrift.

Since the SMET files now contain the creation date, this line had to be deleted before comparing the reference and test files

reverting the previous fix for the meteoPixel being modified by Snowpack: now this is fixed in Snowpack itself (passing currentMeteo by copy)

The tests uncovered a bug that got fixed by sheer luck in one of the lasts commits: when using Snowpack with Canopy, the forcing meteo data will be changed for below canopy values. If Snowpack is called multiple times within an Alpine3D time step, these changes will be performed at every sub-time step (ie correcting data that had already been corrected) leading to an underestimation of the radiative fluxes. The same will also happen with precip (but this has NOT yet been fixed).

An easier fix (than reseting the variables to proper values) would be to pass currentMeteo to runSnowpack() by copy.

The getSynop script should belong to MeteoIO instead of Alpine3D, therefore it has been moved and the documentation updated

More documentation fixes, improvements to the getSynop script, small bug fix in EnergyBalance (more useful error message to help debug simulations)

Some documentation has been added, the POI outputs have been improved, the reference .smet file for the test has been updated and a new script to download and convert synop data has been created (it is still quite experimental).

Fixed a (tricky) bug that prevented running mixed OpenMP/MPI simulations. Imrproved the POI SMET outputs to contain more helpful information. Added some documentation (specially about how MPI could end up being misconfigured and running very slowly). And very minor code cleanup at some places.

Updated the pt_extract "rescue" tool to fit the more recent MeteoIO (this was quite old). It is far from being user friendly but at least it is now usable after reading the explanations given at the begining of the file.

Two bugs have been found: when using "LOCAL" coordinates on a large domain, the projection error compared to usually provided cartesian systems can grow a little too large. Therefore, now by default the cartesian coordinate system that is chosen is the one from the DEM and "LOCAL" can only be enabled with a key.

The MPI version had a problem when gathering gridded data that lead to a stalled simulation. This has been fixed by having all workers gather the requested data on only the master writing it out.

Fixing a small issue when using the runoff module: the default value of the THRESH_RAIN key was not properly handled.

When running with "--nocompute", it now checks the forcing parameters and output various benchmarks to help find out potential problems: monthly sums for various parameters, out of range data, lapse rates, etc

It seems that the test running on the server do not produce the same results as when running on my computer (as for Snowpack)... These reference files are coming from the server.

Updated the reference runs to take into account the very small changes that appeared a few days ago. Despite not understanding why (and after trying for days to re-run with older versions and always producing these "new" results).