GitLab

Fused files with many samples are large.
By default, we limit the number of samples taken into account.

Previously, the informations coming from the best top were kept.
However we could have a sequence in the top 1, with few reads, in a poorly segmented dataset that
was preferred over a top 2 sequence with lots of reads in a highly segmented dataset.

Now we just take into account the number of reads, by assuming with the higher number
of reads we should have the higher reliability. This should be a better criterion than the previous
one (wishful thinking).

Mikaël Salson authored Sep 12, 2016 and Mathieu Giraud committed Sep 23, 2016

This should keep the error message so that we get more valuable information

Mikaël Salson authored Aug 23, 2016 and Mathieu Giraud committed Sep 23, 2016

With malformed files, Fuse will raise an exception that must be caught here.

Mikaël Salson authored Aug 23, 2016 and Mathieu Giraud committed Sep 23, 2016

Will be useful for the clone DB

Incompatible changes are the numerical values in

Those files could quickly saturate disk space

Those files could quickly saturate disk space

> pear.py > don't produce output file on failure
> don't reschedule run if pre-process has failed

Specific PEAR options should be configured through pre-process configs.

Mathieu Giraud authored Jan 08, 2016 and Vidjil Team committed Jan 20, 2016

Some .vidjil files have 'clones: null' instead of an empty list.

TODO: The path to the .analysis file should not be hard-coded.