About getorf result
1
0
Entering edit mode
6 weeks ago
ZZOYEA ▴ 10
>TCONS_00446964_313 [248 - 216] (REVERSE SENSE) gene=RNU6-813P
KALATLERVEV
>TCONS_00446964_314 [220 - 176] (REVERSE SENSE) gene=RNU6-813P
KSERNFFIRETRSVS
>TCONS_00446964_315 [396 - 157] (REVERSE SENSE) gene=RNU6-813P
SSKGHRVDSDPRIFFSLLWLPLFWFMCQAETGKAKRHNERSQKGNFFGMKSFGHIGKGRS
LRETFSSGRLGRCLSPFRLL
>TCONS_00446964_316 [172 - 128] (REVERSE SENSE) gene=RNU6-813P
SFQAAVTKYHLLGGL
>TCONS_00446964_317 [153 - 124] (REVERSE SENSE) gene=RNU6-813P
QSTIYWVAYK
>TCONS_00446964_318 [185 - 3] (REVERSE SENSE) gene=RNU6-813P
VGVLVLSGCCNKVPSTGWLINNRNLFLTVLEAEKSKIKVSGEHSTASWFRVSPFLLCPHM
V

I used getorf to obtain ORFs from a fasta file, but the results appeared as follows. A single TCON id is fragmented into numerous pieces in the output. Is this normal? Is there a way to prevent the fragments from being so divided and instead have them output as a single piece?

the command I used is:

getorf -sequence 03.selected.fa -maxsize 300
getorf ORF • 271 views
ADD COMMENT
1
Entering edit mode
6 weeks ago
shelkmike ★ 1.2k

This is the expected behavior of getorf, because there can be many ORFs in one nucleotide sequence.

ADD COMMENT

Login before adding your answer.

Traffic: 2130 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