You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/quick-start.md
+28-1Lines changed: 28 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,20 @@
6
6
7
7
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.
8
8
9
+
9
10
### Predict m6A and infer nucleosomes
10
11
12
+
#### Your PacBio data uses the SPQR chemistry or latter
13
+
14
+
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.
16
+
17
+
```bash
18
+
ft add-nucleosomes -t 16 input.pacbio.bam output.fiberseq.bam
19
+
```
20
+
21
+
#### Your PacBio data predates the SPQR chemistry
22
+
11
23
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.
12
24
13
25
```bash
@@ -26,9 +38,24 @@ Alternatively, we have written a [snakemake pipeline](https://github.com/mrvollg
26
38
27
39
After this point, you will have a Fiber-seq BAM file that is compatible with all the [extraction](fibertools/extracting/extracting.md) commands in `fibertools`.
28
40
41
+
### Validate your Fiber-seq BAM file
42
+
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.
44
+
45
+
```bash
46
+
ft validate output.fiberseq.bam
47
+
Total reads tested: 1879
48
+
Fraction with m6A: 100.00%
49
+
Fraction with nucleosomes: 100.00%
50
+
Numer of FIRE calls: 0
51
+
Fraction aligned: 100.00%
52
+
Fraction phased: 85.10%
53
+
Fraction with kinetics: 0.00%
54
+
```
55
+
29
56
### Fiber-seq peaks and UCSC browser tracks (FIRE)
30
57
31
-
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 repository](https://github.com/fiberseq/FIRE) for more details.
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).
32
59
33
60
# Fiber-seq starting with Oxford Nanopore Technologies (ONT)
0 commit comments