GitLab

A @rchikhi set with ~150M reads tested with all locus gave an e-value multiplier >2^31,
leading to integer overflow and many spurious clones.

Moreover, the previous multiplier was only an 'int', depending on the actual implementation.
The multiplier is now a float (double) value.

Thanks for @rchikhi for pointing this out.

The other files are generated through a 'make' in tools/tests

Mathieu Giraud authored Jul 13, 2016 and Vidjil Team committed Jul 13, 2016

We want to be able to retrieve the last fuses on every sample set

Follows 7b955792

Vidjil Team authored Jul 13, 2016 and Mikaël Salson committed Jul 13, 2016

English and French versions

This will help testing the effect of some parameter on all the functional tests.

Incompatible changes are the numerical values in

Because of code duplication, also apply fix of b035dd95

This commit resolves an issue where running a sequence file would not
trigger the fuse on other sample sets.
To achieve this fix, schedule run no longer depends on sample sets and
database calls to fuse are done on each run_fuse

Removed a permission check on patient logging which was not only
redundant but also introduced a bug

When the seg[key] is not an object, we convert it to an object such as seg[key] = {'val': value}.
e-values were stored that way (without object).

As Clone can be built independently it is important that convertSeg
is called directly in the Clone constructor and not afterwards in the model.

As code is duplicated between the edit form and the add form, this
is the same code as efc4589

Who said watir tests are useless? Two unexpected bugs have been caught by making this test
(see the two previous commits).

There definitely should be a watir test on the monitor report.