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

different results #47

Closed
illusion-a opened this issue Sep 3, 2022 · 2 comments
Closed

different results #47

illusion-a opened this issue Sep 3, 2022 · 2 comments

Comments

@illusion-a
Copy link

Hello, I uploaded on ISFinder the genome of a not fully assembled Klebsiella pneumoniae with an evalue value of 1e-5 and I got a result. However, when I used ISEScan to predict the same genome, I got a very different result, and I didn't understand what was wrong. My attempts to change the code to get the default or only fully inserted sequences predicted by ISEScan did not solve this problem. The same problem occurred when predicting fully assembled genomes downloaded from NCBI. Can you give me some advice? In addition, I would like to ask if the insertion sequence predicted by ISFinder is the complete insertion sequence? Forgive me if my question is stupid.

Below is the command I used

isescan.py --seqfile KP1.fasta --output results --nthread 8

isescan.py --seqfile KP1.fasta --output results --nthread 8 --removeShortIS
Some of the results are shown in the attachment.
Best wishes!

KP1.txt
20220904013621
KP1.fasta-ISEScan.xlsx

@xiezhq
Copy link
Owner

xiezhq commented Sep 3, 2022

Hello,

Did you use ISsaga supported by ISfinder team when you sadi 'the insertion sequence predicted by ISFinder'? I didn't have idea about ISsaga but I would assume its prediction was the complete inerstion sequence if it didn't say something like that.

I quickly checked the first three IS copies listed in 'KP1.fasta-ISEScan.xlsx'. The genes/proteins predicted by FragGeneScan used by ISEScan for the first two might not be good. You might get different/better (probably 'correct') the predictions different from those two listed in KP1.fasta-ISEScan.xlsx if you try to use the gene/protein annotations from NCBI for the genome sequence regions coverred by the first two IS copies in KP1.fasta-ISEScan.xlsx. Please refer to my sugguestion on May 26 on the page at #45.

Best,
Xie

@illusion-a
Copy link
Author

Hello,

Did you use ISsaga supported by ISfinder team when you sadi 'the insertion sequence predicted by ISFinder'? I didn't have idea about ISsaga but I would assume its prediction was the complete inerstion sequence if it didn't say something like that.

I quickly checked the first three IS copies listed in 'KP1.fasta-ISEScan.xlsx'. The genes/proteins predicted by FragGeneScan used by ISEScan for the first two might not be good. You might get different/better (probably 'correct') the predictions different from those two listed in KP1.fasta-ISEScan.xlsx if you try to use the gene/protein annotations from NCBI for the genome sequence regions coverred by the first two IS copies in KP1.fasta-ISEScan.xlsx. Please refer to my sugguestion on May 26 on the page at #45.

Best, Xie

Thank you very much for your advice

@xiezhq xiezhq closed this as completed Sep 10, 2022
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

2 participants