What is "Possible polymerase run-on fragment"?
1
0
Entering edit mode
5.9 years ago
I0110 ▴ 140

I used gffcompare recently to compare a newly assembled transcriptome and a published transcriptome. The class code p transcripts are "possible polymerase run on". What does that mean? I tried very hard but still cannot find the answer. Thanks!!

class_code

transcriptome • 1.5k views
ADD COMMENT
1
Entering edit mode
5.9 years ago

Answered by Devon Ryan on Bioinfo SE here: https://bioinformatics.stackexchange.com/a/4462/650

Original comment by Devon Ryan that was moved to an answer on 9/4/2020:


Hello I0110!

It appears that your post has been cross-posted to another site: https://bioinformatics.stackexchange.com/questions/4458/what-is-possible-polymerase-run-on-fragment

This is typically not recommended as it runs the risk of annoying people in both communities.

ADD COMMENT
0
Entering edit mode

Hi Devon, Thanks so much for your help on the bioinformatics stackexchange site. Sorry, I posted on the stackexchange bioinformatics site and waited for a day. Is there a general rule? For example, how long should I wait before I cross-posted? Or I should delete one before I posted in another? Please enlighten me since I am fairly new to this business. I only did that because: besides my extensive googling, a similar question was asked in Biostar awhile ago and never answered so I was afraid this might be an undocumented term that not many people knows. Thanks again.

ADD REPLY
1
Entering edit mode

In general as long as you post a link to the other posts you're OK. I would suggest giving people one business day to reply. You posted on a Sunday or Saturday, so it's unreasonable to expect anyone to read it until Monday.

ADD REPLY
0
Entering edit mode

I will certainly add a link and wait for at least one business day next time. Thanks so much for your help, Devon!

ADD REPLY

Login before adding your answer.

Traffic: 1860 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

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

Powered by the version 2.3.6