How to add Unique Peak ID to a bed file created from MACS for HOMER analysis
1
1
Entering edit mode
3.6 years ago
Bella_p ▴ 60

Hi all,

I'm new with using MACS and HOMER.
I have created a bed file using MACS, and got 5 columns, for example:

chr1    770811  771252  MACS_peak_1 93.92
chr1    851512  851790  MACS_peak_2 57.31
chr1    920907  921486  MACS_peak_3 207.37
chr1    946784  946982  MACS_peak_4 73.24

Does anyone knows how can I create a column that contains the Unique Peak ID for HOMER analysis? Also, What is the difference between using findMotifs.pl and findMotifsGenome.pl ? besides the fact that the first uses Unique Peak ID and the second uses genomic positions?

Appreciate your help!

ChIP-Seq HOMER MACS • 1.4k views
ADD COMMENT
2
Entering edit mode
3.6 years ago
Benn 8.2k

The difference between findMotifs.pl and findMotifsGenome.pl is that the first works with gene names (or IDs) as input, and the second with genome coordinates. You have coordinates so you can use findMotifsGenome.pl.

For this you need a bed file, I think only the first 4 columns are needed (I am not sure though if the 5th is ignored automatically, or that you have to remove it yourself first). The unique peak ID is already in the 4th column.

Something like this will find the motifs of your peaks.

findMotifsGenome.pl File_peaks.txt ~/Reference/hg38/ensembl/Homo_sapiens.GRCh38.dna.primary_assembly.fa File_peaks -p 20
ADD COMMENT
0
Entering edit mode

Thanks! I thought so, and needed clarification. Can I ask you about the -size argument? I'm doing ChipSeq analysis, what is the common size to use?

ADD REPLY
1
Entering edit mode

I think best is to try the default size of 200 first. There is also an option to put size given, which means the exact size in your bed file will be used.

Check the manual by only typing in the function name:

findMotifsGenome.pl
ADD REPLY

Login before adding your answer.

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