GitLab

min_cover_representative should be seen as a strict minimum on the number of reads
that can support a representative sequence.
The purpose is to avoid a too low ABSOLUTE number of reads to define a representative.
For the relative number, it is ratio_representative's role.

Before, if we specified -r 100 we needed to have 100 corresponding
k-mers which is very strict when a clone has just slightly more than
100 reads

Better logs

See merge request !444

The parameter can be a dictionary when the dictionary has a success and message key.

We can have a debug output but being in this function is not an error.
Moreover we can't pass a dictionary to the log.

Put pointer cursor on icons

Closes #3808

See merge request !441

Fix #3808

js/export.js: report, bikeshed some fields

See merge request !440

Get reads (simple UI)

Closes #1469 and #3733

See merge request !439

Prevent double clicking.

The code is now accessible from elsewhere and can
be used to retrieve an event far away on the stack.

It is useful for the checkProcess function in database.js
Related to #1469

When a process is finished we need to access its result. Thus we provide the result ID.
Related to #1469

Fix #3733

However we pay attention that no one is trying to access a file in a parent directory

In this way it can be used by any controller not just results_file.py

It is required in the remaining of the function

This method now uses the callProcess function which regularly checks for the end of the process

Fix #1469

As discussed in #3718

See #3598