SEQanswers

Go Back   SEQanswers > Bioinformatics > Bioinformatics



Similar Threads
Thread Thread Starter Forum Replies Last Post
How to convert .txt file to .bed or .gff, How can we use chip seq data in R software forevermark4 Bioinformatics 57 06-30-2014 05:01 AM
seq.txt, qseq.txt and fastq NicoBxl Bioinformatics 5 01-03-2014 08:35 AM
s_*_export.txt VS s_*_sequence.txt zhuj Illumina/Solexa 5 06-08-2010 01:35 PM
solexa output files | s_*_seq.txt vs. s_*_sequencece.txt lajoieb Illumina/Solexa 3 04-08-2009 05:52 PM
Difference between eland_multi.txt and eland_extended.txt seq_GA Illumina/Solexa 1 02-13-2009 03:50 AM

Reply
 
Thread Tools
Old 01-26-2009, 10:29 PM   #1
hannat
Member
 
Location: Germany

Join Date: Jan 2009
Posts: 16
Default problems concerning seq.txt and prb.txt

I try to convert seq.txt and prb.txt to standard fastq output, using maq tool,

fq_all2std.pl seqprb2fastq seq.txt prb.txt

here comes the problems, the perl scripts returns lots of warning messages, so i checked seq.txt and prb.txt, find some strange lines, which looks like this in "seq.txt"
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@s_6_0003_seq.txt^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@0000644^@0001367^@0001035^@00000751113^@10553464424^@013222^@ 0^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ustar ^@mhirst^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@solexa^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

in "prb.txt"
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@s_6_0002_prb.txt^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@0000644^@0001367^@0001035^@00014532430^@10553464427^@013223^@ 0^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ustar ^@mhirst^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@solexa^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

so does anyone have similar problem before, what should i do about these lines, please give me some suggestions.
hannat is offline   Reply With Quote
Old 01-26-2009, 10:31 PM   #2
hannat
Member
 
Location: Germany

Join Date: Jan 2009
Posts: 16
Default

forget to mention how the rest of the files looks like
"seq.txt"
6 3 298 121 GGTGTTCTGGCTAGATTCATGAATTCA
6 3 395 116 TATTTGTTCTTTACTAAAGAAATTTAA
6 3 849 368 ACTAGCAAAAGTAATACCTATTCATTA
6 3 259 119 GTGATGGAGCCCTACAGGTCCTCACTG

"prb.txt"
30 -30 -30 -30 -30 -30 -30 30 -30 30 -30 -30 -30 30 -30 -30 -30 30 -30 -30 30 -30 -30 -30 -30 -30 -30 30 -30 30 -30 -30 -30 30 -30 -30 -30 30 -30 -30 30 -30 -30 -30 -30 -30 -30 30 -30 -30 -30 30 -30 -30 30 -30 -30 30 -30 -30 -30 -30 -30 30 -30 30 -30 -30 -30 -30 30 -30 -30 -30 -30 30 30 -30 -30 -30 -30 30 -30 -30 -30 -30 30 -30 -30 -30 30 -30 -30 -30 30 -30 -30 30 -30 -30 -30 -30 -30 30 -30 -30 -30 30
hannat is offline   Reply With Quote
Old 01-27-2009, 04:09 AM   #3
regyre
Member
 
Location: Umeň, Sweden

Join Date: Jan 2009
Posts: 11
Default can you post some more details?

Just need some more details here.

Where is the file content that you posted coming from?

Does it come from some example s_*_prb.txt and s_*_seq.txt files (i.e. for you from what I see in your first post, something like s_6_0002_prb.txt)?

Or were these files already concatenated into your "seq.txt" and "prb.txt" file? If yes, how did you do the concatenation? And could something has gone wrong there, because to me it looks like the file got corrupted.

Cheers
regyre is offline   Reply With Quote
Old 01-27-2009, 04:49 AM   #4
new300
Member
 
Location: northern hemisphere

Join Date: Mar 2008
Posts: 50
Default

Looks like a corrupt filing system or memory leak to me (I've not seen prb/seq files like this before). Are you able to check the original files?
new300 is offline   Reply With Quote
Old 01-27-2009, 10:35 PM   #5
hannat
Member
 
Location: Germany

Join Date: Jan 2009
Posts: 16
Default

i got the data from this site, http://www.bcgsc.ca/data/chipseq. I am using STAT1_stimulated, i checked every file, all most all of them have this problem, i guess they didn't notice it when they were concatenating the files.

I wrote a perl script to take away those lines, so now, fq_all2std.pl doesnt complain anymore.
hannat is offline   Reply With Quote
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off




All times are GMT -8. The time now is 10:58 PM.


Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.