Outils pour utilisateurs

Outils du site



Let us assume that genomic sequences G1 and G2 are associated to antibiotic resistant bacterial strains, while genomic sequences G3 and G4 are derived from bacterial strains sensitives to this antibiotic (genomic sequences G1, G2, G3 and G4 are stored in tests directory).

The objective here is to search for specific sequences than can be involved in antibiotic resistance in genomes G1 and G2.

To do so, we first create a list file with the paths of genomic sequences that belong to antibiotic resistance strains (inGroupTest.txt). And a list file with the paths of genomic sequences that not belong to antibiotic resistance strains (outGroupTest.txt).

SkIf2 search for specific k-mers (in this example length = 24) of genomes G1 and G2 :

cd tests
../build/bin/SkIf2 -inGroupFile inGroupTest.txt -outGroupFile outGroupTest.txt -k 24 -outputFile specificInGroup.csv

Check outputs :

  • 45 specific k-mers detected in G1 and G2. Results are stored in specificInGroup.csv.
  • Specific k-mers are mapped on first genome in inGroupTest.txt paths list (G1).

We can observe that a lot of specific k-mers are located in the same genomic region. We want then to create long mer (concatenation of consecutive k-mers) with the following command line:

../scripts/getLongestKmers.pl -f specificInGroup.csv -o longspecific

Check outputs :

  • 2 specific long-mers in G1 and G2. Results are stored in longspecific.csv and longspecific.fasta

We can also observe that these 2 specific long-mers overlapped. So, we want to concatenate these overlapping regions :

../scripts/getLongestKmersNC.pl -f specificInGroup.csv -k 24 -o longlong

Check outputs :

  • 1 long fragment that include all specific k-mers present in group 1. Results are stored in longlong.csv and longlong.fasta

As G1 and G2 are antibiotic resistant bacterial strain, we can postulate that the CDS involved in this trait is probably located in this long fragment.

example.txt · Dernière modification: 2021/07/06 14:12 par martial.briand@inrae.fr