Skip to content

Commit 6094c5b

Browse files
author
Mitchell R. Vollger
committed
.
1 parent f46d806 commit 6094c5b

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

src/quick-start.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,19 +6,18 @@
66

77
HiFi kinetics are required for predicting [m6A](glossary.md#m6a) with `fibertools`. **Check with your sequencing provider prior to sequencing** to ensure that the output file will have kinetics. Additionally, many of `fibertools` commands are compatible with CpG methylation which can be completed on instrument (if requested) or later with [Jasmine](https://github.com/PacificBiosciences/jasmine), e.g. `jasmine --keep-kinetics input.ccs.bam output.ccs.bam`. This command should be run prior to `fibertools` if CpG methylation information is desired as Jasmine will overwrite the m6A predictions in the MM and ML tags.
88

9-
109
### Predict m6A and infer nucleosomes
1110

1211
#### Your PacBio data uses the SPQR chemistry or latter
1312

1413
As of the SPQR chemistry with PacBio their base modification caller `jasmine` can make m6A predictions on instrument in addition to 5mC.
15-
This removes the need for `ft predict` and PacBio BAMs that have the kinetics information. However, after you must still run `ft add-nucleosomes` which is required for downstream analysis.
14+
This removes the need for `ft predict` and PacBio BAMs that have the kinetics information. However, after you must still run `ft add-nucleosomes` which is required for downstream analysis.
1615

1716
```bash
1817
ft add-nucleosomes -t 16 input.pacbio.bam output.fiberseq.bam
1918
```
2019

21-
#### Your PacBio data predates the SPQR chemistry
20+
#### Your PacBio data predates the SPQR chemistry
2221

2322
To create useable Fiber-seq data you must first call m6A base-mods on the PacBio CCS bam using `fibertools`. First [install fibertools](fibertools/install.md) and then process your bam file using the prediction command.
2423

@@ -40,7 +39,8 @@ After this point, you will have a Fiber-seq BAM file that is compatible with all
4039

4140
### Validate your Fiber-seq BAM file
4241

43-
We have a quick validation tool which can test your BAM file for the desigered Fiber-seq features. At this point you should have m6A and nucleosome calls.
42+
We have a quick validation tool which can test your BAM file for the desired Fiber-seq features.
43+
At this point you should have m6A and nucleosome calls.
4444

4545
```bash
4646
ft validate output.fiberseq.bam
@@ -55,7 +55,10 @@ Fraction with kinetics: 0.00%
5555

5656
### Fiber-seq peaks and UCSC browser tracks (FIRE)
5757

58-
Once you have a phased bam file, you can identify [Fiber-seq inferred regulatory elements (FIREs)](glossary.md#fires) to call Fiber-seq peaks and make a UCSC trackHub. Please see the FIRE page for more details [FIRE](fire/fire.md).
58+
Once you have a phased bam file, you can identify [Fiber-seq inferred regulatory elements (FIREs)](glossary.md#fires) to call Fiber-seq peaks and make a UCSC trackHub.
59+
60+
You can find more details in on installing and running FIRE here:
61+
[Running the FIRE pipeline](/fire/run.md).
5962

6063
# Fiber-seq starting with Oxford Nanopore Technologies (ONT)
6164

0 commit comments

Comments
 (0)