MUMmer show-tiling is out of date?
Entering edit mode
9.5 years ago
marcelelaux ▴ 20

Hello guys

I am doing a recruitment analysis looking for metagenomic islands. The inputs are a fasta file of my target species, extracted from the original metagenomic reads file, and the complete reference genome of my target species.

I am using MUMmer Promer utility for the alignment and show-coords utility for data exploration. The only utility that give me the length of the gap between a contig and the next, respecting the synteny of the reference genome is show-tiling, and I have used it to look for gaps larger than 10000 bp. It seems to work weel, when exploring this areas in show-coords output, but I read in a post that show-tiling would be out of dated. This is too bad for me, because I dont know how to look for this low/no alignment regions in the show-coords output.

Can anyone tell me something about show-tiling and, if it really is out of date, how can I get this gap between recruited reads (reads that aligned about 98 identity, similarity and coverage)?

Here is a example of the show-tiling output:

[S1] [S2] [gap between this contig and the next] [length/contig] [align.cov.] [average identity] [orientation] [contig id]
2813632 2813778 15787   147     94.56   85.87   +       HD4RJIW01BV3T7
3618731 3618964 10484   234     96.15   90.67   -       HD4RJIW02GX7DC
3813833 3814001 12862   169     100.00  85.19   -       HD4RJIW02HFIBU

The third field is what I need, and what I am using.

Here is a example of the show-coords output:

[S1] [E1] [S2] [E2] [L1] [L2] [%id] [%sim] [%stp] [cov R] [cov Q] [FRM] [TAGS]

where S=subject, E=query, L=length, stp=stop codon, FRM=orientation/frame

775     903     7       135     129     129     93.02   95.35   1.16    0.00    94.16   1       1       gi|166362741|ref|NC_010296.1|   HD4RJIW01EHAFJ
811     963     169     17      153     153     96.08   100.00  0.00    0.00    90.00   1       -2      gi|166362741|ref|NC_010296.1|   HD4RJIW02IJPAZ
823     1008    200     15      186     186     96.77   100.00  1.61    0.00    92.08   1       -3      gi|166362741|ref|NC_010296.1|   HD4RJIW01DF547

I tried to write a perl script that read a line, split, read the orientation[FRM], then choose between S1 or S2 field, then jump to the next line, split again, read the orientation again, choose the right field and do the subtraction. If larger than 10000, send the two lines to a new file, and so on, but it doesn't worked at all, I couldn't jump to the next line.

If you like, I can show you my frustrated script.... But if is all ok with show-tiling, so I don't need to worry.


The input file:

[marlaux@n4-202-14 recruit_2015]$ cat -A RL5_promer.tiling | head
>gi|166362741|ref|NC_010296.1| 5842795 bases$

This script I tried to wrote to use the show-coords, instead of show-tiling, because I am not sure if show-tiling is the right utility for this. I hope it is. The script is:

use diagnostics;
use warnings;

print "arquivo 1:\t";
$arq1 = <STDIN>;
open (MYFILE, $arq1);
open (NEW_FILE, '>>');
@file = <MYFILE>;
close (MYFILE);
    foreach $line (@file) {
        @aligns = split (/\t/, $line);    
        #print "@aligns $p1 $p2\n";
        if ($aligns[11] > 0)    {
            print "$aligns[11] $a\n";
            @aligns2 = split (/\t/, $line);
                if ($aligns2[11]>0)    {
                else    {
        else    {
            @aligns2 = split (/\t/, $line);
                if ($aligns2[11]<0)     {
                else    {
        print "$a $b $gap\n";
        if ($gap>9000)    {
        push (@new_file, ("@aligns\n@aligns2\n"));
        print NEW_FILE @new_file;

Thank you

recruitment MUMmer Show-coords • 3.2k views
Entering edit mode

Please paste your script here. It looks like the problem is either with the delimiter you're using or the EOL character, so could you also give us the output of:

cat -A show_tiling_file | head

where show_tiling_file is the file your perl script is trying to parse please?

EDIT: Thanks for adding information, I've moved all the pertinent info to the question.


Login before adding your answer.

Traffic: 3848 users visited in the last hour
Help About
Access RSS

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6