-
Notifications
You must be signed in to change notification settings - Fork 5
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
i dont understand the output. Why there are NN in left and right sequence? #7
Comments
Hello, Sequence right and left are a consensus of the reads covering this region. N means that left than 80% of reads give the same nucleotide at this position. |
Thank you for the reply. However, how can I tell which nucleotide is present there instead of N? My other question is that all the output are showing No IR what does it mean? They are not IS elements? How can I see the insertion of those IS elements in the context of the genome in relation to the reference genome? |
N is just an indication that this part of the sequence is not good enough (3' tail of reads). |
python ISFinder_search.py panisa. Most of the time it is showing error. During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Strange, I do some analysis today and it works. |
My version is panISa.py 0.1.6. I dont know may be my internet problem. Some times rarely it's working but maximum time not working. When i am trying to do with my real data it's showing error. I forgot but most probably installed using conda. |
Hello, is it possible that i will send my panisa result to you. You just run this step and give me the output?? |
ok |
Can i get your email id? or should i upload here? |
My email is [email protected] |
May I ask which species you are using this software to analyze? I would like to analyze aquatic organisms and I am not sure if it will be applicable. @Subhajeet1997 |
This is mainly design for insertion sequence in bacteria, I have no idea if it works on other cases. |
Okay, thank you very much for your reply. I want to use it for oyster. So I would like to ask, if my genetic data sequencing depth is 10X, do I use the default values or do I need to set these values based on the sequencing depth?
usage: panISa.py [options] bam
Search integrative element (IS) insertion on a genome using BAM alignment
positional arguments:
bam Alignment on BAM/SAM format
optional arguments:
-h, --help show this help message and exit
-o [OUTPUT], --output [OUTPUT]
Return list of IS insertion by alignment,
default=stdout
-q [QUALITY], --quality [QUALITY]
Min alignment quality value to conserve a clipped
read, default=20
-m [MINIMUN], --minimun [MINIMUN]
Min number of clipped reads to look at IS on a
position, default=10
-s [SIZE], --size [SIZE]
Maximun size of direct repeat region, default=20pb
-p [PERCENTAGE], --percentage [PERCENTAGE]
Minimum percentage of same base to create consensus,
default=0.8
-v, --version show program's version number and exit
…---- Replied Message ----
| From | ***@***.***> |
| Date | 10/14/2024 14:53 |
| To | ***@***.***> |
| Cc | ***@***.***>,
***@***.***> |
| Subject | Re: [bvalot/panISa] i dont understand the output. Why there are NN in left and right sequence? (Issue #7) |
This is mainly design for insertion sequence in bacteria, I have no idea if it works on other cases.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
10X seems low for this research, beacause only a small portion of read that covers the insertion was efficient. |
Ok, thanks for the reply. Do the rest of the values use the default values?
…---- Replied Message ----
| From | ***@***.***> |
| Date | 10/14/2024 18:00 |
| To | ***@***.***> |
| Cc | ***@***.***>,
***@***.***> |
| Subject | Re: [bvalot/panISa] i dont understand the output. Why there are NN in left and right sequence? (Issue #7) |
10X seems low for this research, beacause only a small portion of read that covers the insertion was efficient.
you can decrease the -m option to 5 may be.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Yes, I think |
ok thank u~
…---- Replied Message ----
| From | ***@***.***> |
| Date | 10/14/2024 19:16 |
| To | ***@***.***> |
| Cc | ***@***.***>,
***@***.***> |
| Subject | Re: [bvalot/panISa] i dont understand the output. Why there are NN in left and right sequence? (Issue #7) |
Yes, I think
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Sorry to bother you again. I used the command you told me to process the test.bam file provided on this github website, and luckily got the result file without any errors! But when I use the same command to process my BAM file, some records appear in the nohup file. Can I ignore them? Even though these records exist, the .TE result file is still generated! If I cannot ignore it, why did this error occur? Hope to receive your reply, thank you! @bvalot |
You seems to have not install emboss package as indicated: |
Hello, thank you very much for your previous answer. According to your suggestion, I have successfully run this software and got the .TE result file. I would like to ask if I can annotate ERV, LINE, and SINE based on this .TE result file? @bvalot |
I have no idea how to do that.? You probably need to use reconstruct sequence to search on specific web site for these elements. |
Chromosome End position End clipped reads Direct repeats Start position Start clipped reads Inverted repeats Left sequence Right sequence
contig-2000003 334451 59 GTCCTGGAGC 334442 40 No IR CAATGTCATCAACTTTGGAAATTATCCATAAATATCATATAATTAGCGCTCAAATCAGTGCATGGGAGNNGNC NNNNNGGCCATGGCGGCTGGCTGCTTCGGGGGGCTTGCCTTGGGCAGGGCTGCAGCTTAGGTTGATGACATTG
The text was updated successfully, but these errors were encountered: