-
Notifications
You must be signed in to change notification settings - Fork 271
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #657 from macs3-project/doc/macs3/3.0.2
Doc/macs3/3.0.2 for v3.0.2 release
- Loading branch information
Showing
28 changed files
with
9,421 additions
and
9,012 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
2024-04-27 Tao Liu <[email protected]> | ||
MACS 3.0.2 (pending) | ||
2024-09-06 Tao Liu <[email protected]> | ||
MACS 3.0.2 | ||
|
||
* Features added | ||
|
||
|
@@ -11,16 +11,27 @@ | |
file from previous version, if there is no hmm-type information in | ||
the model file, the hmm-type will be assigned as gaussian. #635 | ||
|
||
2) Add `--cutoff-analysis-steps` and `--cutoff-analysis-max` for | ||
2) `hmmratac` now output narrowPeak format output. The summit | ||
position and the peak score columns reported in the narrowPeak | ||
output represents the position with highest foldchange value | ||
(pileup vs average background). | ||
|
||
3) Add `--cutoff-analysis-steps` and `--cutoff-analysis-max` for | ||
`callpeak`, `bdgpeakcall`, and `hmmratac` so that we can | ||
have finer resolution of the cutoff analysis report. #636 #642 | ||
|
||
3) Reduce memory usage of `hmmratac` during decoding step, by | ||
4) Reduce memory usage of `hmmratac` during decoding step, by | ||
writing decoding results to a temporary file on disk (file | ||
location depends on the environmental TEMP setting), then loading | ||
it back while identifying state pathes. This change will decrease | ||
the memory usage dramatically. #628 #640 | ||
|
||
5) Fix instructions for preparing narrowPeak files for uploading | ||
to UCSC browser, with the `--trackline` option in `callpeak`. #653 | ||
|
||
6) For gappedPeak output, set thickStart and thickEnd columns as | ||
0, according to UCSC definition. | ||
|
||
* Bugs fixed | ||
|
||
1) Use `-O3` instead of `-Ofast` for compatibility. #637 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
MACS_VERSION = "3.0.1" | ||
MACS_VERSION = "3.0.2" | ||
MAX_PAIRNUM = 1000 | ||
MAX_LAMBDA = 100000 | ||
FESTEP = 20 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,10 @@ | ||
# BED format | ||
|
||
The BED format is a widely used format to store the genome | ||
annotation. It's flexible and has many variation depends on how many | ||
fields exists in the file. The official definition of BED format can | ||
be found | ||
[here](https://genome.ucsc.edu/FAQ/FAQformat.html#format1). Formats | ||
like BEDPE, narrowPeak, broadPeak, or gappedPeak can be regarded as | ||
variation of BED format. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,26 @@ | ||
# SAM/BAM/BAMPE format | ||
|
||
SAM and BAM formats are the most common format used to store alignment | ||
information of sequencing reads. The BAM format is in fact the binary | ||
version of SAM which is a text file. Please refer to [SAM format | ||
specification](https://samtools.github.io/hts-specs/SAMv1.pdf) for | ||
detail. As in MACS3, we call the BAM file from paired-end reads | ||
mapping as `BAMPE` -- BAM file for Paired-End data. When you specify | ||
the input format as `BAMPE` such as `-f BAMPE` in `callpeaks`, you | ||
will trigger the PE mode for MACS3 where we will consider the whole | ||
fragment between read pair as the DNA fragment bound by the protein of | ||
interest. On the contrast, even if the BAM storing PE mapping | ||
information, if you specify `-f BAM`, MACS3 will treat the input as | ||
single-end data and use only the 1st mate of read pair to estimate the | ||
fragment length using the cross-correlation model. | ||
|
||
Most of MACS3 modules only take the mapping location of reads from | ||
SAM/BAM/BAMPE file. If necessary, you can use `macs3 filterdup | ||
--keep-dup all` or `macs3 randsample -p 100` to convert the | ||
SAM/BAM/BAMPE into BED or [BEDPE](./BEDPE.md) format, then gzip them | ||
to save storage. | ||
|
||
The only exception is that the `callvar` command in MACS3 will need to | ||
read the actual sequences and mapping information such as the | ||
mismatch, insertion, deletion, etc from BAM. Also, please make sure | ||
that the BAM file for `callvar` has to be sorted and indexed. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,13 @@ | ||
# bedGraph format | ||
|
||
The official definition of bedGraph can be found | ||
[here](https://genome.ucsc.edu/goldenPath/help/bedgraph.html). As for | ||
all other files generated directly from MACS3, you may need to add a | ||
trackline to the beginning of the file when you upload the file to | ||
UCSC genome browser for display. A minimal trackline for bedGraph is | ||
`track type=bedGraph`. Please read the above link to the official | ||
definition page for more instruction. The bedGraph format file can be | ||
further converted into a binary format named 'bigWig' for smaller file | ||
size and for fast and random access. Check this | ||
[gist](https://gist.github.com/taoliu/2469050) for a script to convert | ||
the plain text bedGraph to binary bigWig. |
Oops, something went wrong.