New output format for bedtools getfasta -name

68 views
Skip to first unread message

sven.sc...@novartis.com

unread,
May 20, 2020, 2:22:52 PM5/20/20
to bedtools-discuss
Hi,

It seems that the output format for bedtools getfasta -name was changed:


chbscl-8-7: [~] $ cat test.fa
>chr1
AAAAAAAACCCCCCCCCCCCCGCTACTGGGGGGGGGGGGGGGGGG
chbscl
-8-7: [~] $ cat test.bed
chr1    
5       10      myseq
chbscl
-8-7: [~] $ tools/CentOS7/bedtools/bedtools-2.29.2/bin/bedtools  getfasta -fi test.fa -bed test.bed -name
>myseq::chr1:5-10
AAACC
chbscl
-8-7: [~] $


 This is very unfortunate for pipelines in which bedtools getfasta -name is used. Why was the format changed?

Best regards,

Sven

Aaron Quinlan

unread,
May 26, 2020, 9:48:42 AM5/26/20
to sven.sc...@novartis.com, bedtools...@googlegroups.com
Hi Sven,

Sorry for the trouble. This change was actually to correct an earlier change that itself modified the behavior from the original. I suspect the -nameOnly option is what will produce your desired behavior.

Best,
Aaron
--
You received this message because you are subscribed to the Google Groups "bedtools-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bedtools-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bedtools-discuss/7ed54c4a-4d58-4b51-8d59-551d6e2dbb3e%40googlegroups.com.

Sven Schuierer

unread,
May 26, 2020, 10:00:29 AM5/26/20
to bedtools-discuss
Hi Aaron,

Thanks a lot for letting me know. Actually, yesterday I accidentally created the help output of getfasta and realized that there is the option -nameOnly.

I would still argue that it would have been the better choice to keep the output of the -name option unchanged and add a new option, say -nameExtended (you had -name+, right?) for the new output format. In this way existing pipelines would not break.

Best regards,

Sven 
Reply all
Reply to author
Forward
0 new messages