Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nt-debug (failed pairwise alignment) #7

Open
thierryjanssens opened this issue Sep 10, 2018 · 2 comments
Open

nt-debug (failed pairwise alignment) #7

thierryjanssens opened this issue Sep 10, 2018 · 2 comments
Assignees

Comments

@thierryjanssens
Copy link

thierryjanssens commented Sep 10, 2018

Hello,

it seems that some sequences that are successfully aligned to the reference end up in the nt-debug folder.
While some that failed to do so are not present in the nt-debug folder.

Kind regards,

Thierry

@thierryjanssens
Copy link
Author

Hi,

I think I can see a pattern.
The headers in the fasta file I use consist of
TAXON(with underscores in between)_SAMPLENAME_ORFNAME(with underscores in between).
The Failed folder (i.e. nt-debug output) contains the paired alignment for the unique taxon - sample conbination.

e.g.:

Rhinovirus_A_sample_1_NODE_1-1
Rhinovirus_B_sample_1_NODE_1-1

but

Rhinovirus_B_sample_1_NODE_1-2 does not show up.

kind regards,

Thierry

@plibin plibin self-assigned this Sep 11, 2018
@ktheyss
Copy link
Collaborator

ktheyss commented Sep 20, 2018

In order to replicate this problem, a test fasta file is created, containing Dengue Serotype 1 sequences, Dengue Serotype 3 and HIV-1.

Headers are

virus_A_sample_1_NODE_1-1
virus_A_sample_1_NODE_1-2
virus_A_sample_2_NODE_1-1
virus_A_sample_3_NODE_1-1
virus_B_sample_1_NODE_1-1
virus_B_sample_1_NODE_1-2
virus_B_sample_1_NODE_1-3
denv1_A_sample_1_NODE_1-1
denv1_B_sample_1_NODE_1-1
denv1_B_sample_1_NODE_1-2
denv1_B_sample_2_NODE_2-2
denv1_B_sample_2_NODE_2-2
denv1_B_sample_1_NODE_2-3
denv1_B_sample_2_NODE_1-2

The command used was the following : virulign DENV1-NC001477.xml test.txt --nt-debug debugfolder/

Two remarks to be considered:

  • I could not replicate the error of truncated headers.
  • However, not all (unique header) failed sequences are indeed present in the debug folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants