Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.6
-
Fix Version/s: 2.6.1
-
Component/s: None
-
Labels:None
Description
not entirely sure when this bug was introduced, but for 2.6, trying to import a PIR file - with or without modeller lines, results in the db info line (between the tag and the sequence record) being imported as sequence. Not good:
This pir line :
>P1;FER_CAPAA/1-97
FER_CAPAA 97 residues
..........................................................ASYKVKLITPDGPI
EFDCPDDVYILDQAEEAGHDLPYSCRAGSCSSCAGKIAGGAVDQTDGNFLDDDQLEEGWVLTCVAYPQSDVT
IETHKEAELVG.*
becomes the fasta file:
>P1;FER_CAPAA/1-117
FER_CAPAA.97.residues...................................................
.......ASYKVKLITPDGPIEFDCPDDVYILDQAEEAGHDLPYSCRAGSCSSCAGKIAGGAVDQTDGNFLD
DDQLEEGWVLTCVAYPQSDVTIETHKEAELVG.*
This pir line :
>P1;FER_CAPAA/1-97
FER_CAPAA 97 residues
..........................................................ASYKVKLITPDGPI
EFDCPDDVYILDQAEEAGHDLPYSCRAGSCSSCAGKIAGGAVDQTDGNFLDDDQLEEGWVLTCVAYPQSDVT
IETHKEAELVG.*
becomes the fasta file:
>P1;FER_CAPAA/1-117
FER_CAPAA.97.residues...................................................
.......ASYKVKLITPDGPIEFDCPDDVYILDQAEEAGHDLPYSCRAGSCSSCAGKIAGGAVDQTDGNFLD
DDQLEEGWVLTCVAYPQSDVTIETHKEAELVG.*
Attachments
Issue Links
- related with
-
JAL-678 test PIR/FASTA/BLC file type recognition and IO of metadata associated with sequences (viz. the Modeler description lines)
-
- Open
-