Broken facility usage constraint removed

groupSizeHard1_6 constraint doesn't work - it aimed to make sure that each of the facilities is used at least once.
However when tested in separation from other constraints it ended up putting all the allocation on one beamline. It did not make any change whatsoever in the final solution.
I don't think we really need to add a constraint for this given the problems we solve tend to have smaller capacity than needed - lots of students and few sessions. We already have a constrain that reduces the variability of the group sizes - which have similar effect.

Number of choices in output summary

The release includes a fix of issue 19 reported by Steve this morning.

Writer class fix

0.6

new version - pom

Full

The first/second preference constraint can be switched on or off (input.xlsx weights).
The default reproductive mode can be now switched on and off (input.xlsx key value).
The results are now stored in a separate copy of input.xlsx called soluition_input.xlsx.

First full

The first/second preference constraint can be switched on or off (input.xlsx weights).
The default reproductive mode can be now switched on and off (input.xlsx key value).
The results are now stored in a separate copy of input.xlsx called soluition_input.xlsx.

Termination

The termination is not an input specified in KeyValues tab of the input file.

Each student will get at least one first or second preference (new constraint)

Long experiments

Long experiment constraint is now correct, there is a new set of constraints which guarantee that each beamline is used at least once.

Functionality

Includes all the required features.