GitLab

We store here the length ratio computed in 34fbcbd5.

This should be directly moved into some KmerRepresentativeComputer() constructor.

build it / update it ...
remove one more global function

The ratio between the length of the representative and the length
of considered reads is a good indicator of the overall quality
of the representative. Many clones have good ratios, above 90%.

Mathieu Giraud authored Mar 16, 2015 and Vidjil Team committed Mar 16, 2015

These reads/segs/ratio/wins informations should be stored in the db.

In case of spaces and parentheses, the path must be protected for mktemp but also
for the --xml-file option. Hence the double double quotes.

The outer double quotes must not be escaped (otherwise double quotes are passed to valgrind
which is not good)

store important element in scatterplot object instead of running through the DOM

We are exiting the program early because of a missing file.
That causes some memory leaks which are not a problem (that's
just because the program ended unexpectedly).

The dir function was considering spaces as separator, which is bad.

Mathieu Giraud authored Mar 16, 2015 and Vidjil Team committed Mar 16, 2015

This adds a 'format' optional argument to db.call('admin/log').

Mathieu Giraud authored Mar 16, 2015 and Vidjil Team committed Mar 16, 2015

We should use regexps here.