GitLab

The purpose of these tests is to check whether the reads with labeled windows
are kept, and not to test the VDJ segmentation on these difficult reads.

Don't remove anything: the sequences used in segmentation.fasta
are quite specific to test tricky case to see how behaves the
affectanalyser in strange cases. Such tricky cases will be hard to find
only with the last 100nt of V genes

Obviously the number of kmers is lower. But the number of ambiguous k-mer is also lower.

This is a hand-made test with the *start* of a V gene. Therefore it cannot be found
with default parameter where we only keep the last 100bp

It will be default in a next release.

This option is passed to the germline which is passed to the kmerstore (in the insert method).
It is used to only consider one end of a V/J gene

Used to be pass through to the insert() method in KmerStore (to avoid indexing all the Vs or all the Js)

With keep_only parameter we can index either the start or the end of a sequence.
Useful since we may not need to index all the V genes (but only the end).

Discussions in British pubs are valuable!

(merged by magiraud, 2015-05-07, light conflict with 07adde3c)

Fix 9aa52e68.
Thanks to the functional Watir tests.

Partially revert 59f3e19d
Tests should work even without a server on localhost (especially for unit tests run by Jenkins or Travis).

We changed several times this line to see if the clone is the same.
The purpose of the test is to check if we have the same clone in both datasets.
The purpose of the test is not to check the segmentation.

To check that, we remove the part of the lines that differ among both datasets
and only keep the segmentation information. Hence both lines should be equal and
should not appear in the diff.

Do what the test says. We don't care if we have 143 affectations (it is lower now with -t
about 100). We want to see if we have the same affectations. Just do a sort -u:
if we have twice the same line the duplicate will be removed with the -u, hence we will have
only one occurrence of the XXX

Thanks to landscape.io.

Thanks to landscape.io.

The result with '>=' should be more portable.
This may be related to the actual precision of 'double' and rounding issues that may depend on the platform.

Bug detected thanks to unit tests on several slaves. Thank you Jenkins !

Additionnally that function falls back to stderr if there is a problem opening the output file

relaunch-fuse.py: Script that provide commands for relaunching fuse.py for any sequence file containing a given substring

Since auth is initialised at the beginning it doesn't benefit from the change of the DB.
Therefore it was modifying the original DB rather than working on the test DB.

Since we don't modify them at export, there's no reason to modify them at import

If the seed is not symmetrical (as with TRA and VdJa), we can't just reverse the seed.
We need to take back the original substring, reverse it and then take the seed.