GitLab

* The options can be overriden usig the option override_imgt_options.
* The results are overwritten in m.clones[].seg.imgt
* We now launch IMGT Post twice: 1. With nt-sequence 2. With summary (% id in V gene)

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

Ensure that field is defined before accessing it.

Test that boundaries provided by IMGT have the priority on what we
could compute by hand (even if the boundaries do not make sense).
Beware IMGT starts numbering at 1.

The field searched for are not the same anymore, so we adapt the tests.

Will be useful for the clone DB

In this case sequences are longer, which is more interesting and IMGT provides
the start and stop positions, which is more robust.
Additionnally we also have access to all CDR and FR regions for the future.

The for-loop was useless. We start by defining the fields to be processed and then
for each of them we compute the start and stop positions.
We also take benefit of the fact that IMGT may define itself the start and stop positions
in which case we just retrieve them.

Proxy is now on rbx and not on dev anymore (for quite a long time actually).

Resolved an issue where the permissions for viewing results logs were
checked on the wrong sample set

Refactored the selection of the owner group when adding a patient and a
run since the process is the same, but there was a duplication in the
code and the two versions had diverged, creating a bug.

It avoids ambiguity and ensures that we redirect to the right page.

We can remove results file from a run that is
not linked in any way to a patient. We just
consider the sample set

improve loop

same as list.js

nodes start with size 0 (=>the scatterplot doesn't freeze anymore during the first frames)

remove some useless code

build everything once, update/hide/display if necessary

improve sortListByXXX functions
-add generic function sortListBy(fct)
-remove obsolete funtion
-use javascript to retrieve attribute instead of jquery

redraw lines only if neccessary

This hotfix resolves an issue with default group selection when creating
a new patient.

This issue affected users that belonged to multiple groups but did not
have creation permissions on all groups.

The default user group is now also only displayed if the user has create
permissions on that group.

Revamped the packaging information with new tools and techniques that
have come to light to my attention and make things easier

database.js / file controller : add a client side form validator for file upload (check the number of file provided/pre_process)

numerical field by 'val' key
textual field by 'info' key.