Skip to content

njspix/scwgbs_biscuit_nf

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

scWGBS processing with Biscuit and Nextflow

This is a work-in-progress meant to record my current thoughts/process for analyzing (sc)WGBS data with Biscuit and related tools.

Quick start:

You'll need the following to get started:

  • Files:
    • Paired-end fastq files from scWGBS sequencing
    • Biscuit-indexed reference genome
    • Biscuit QC assets for your reference genome
    • A copy of the Biscuit QC script (at least for now...)
    • A 'target' bed file (regions covered in this file will be represented in the output R object)
  • Tools:
    • Singularity or similar container engine (Nextflow Docs)
    • Nextflow

Reference genome and Biscuit QC config:

Open conf/resource_files.config in your favorite editor. Add the following paths:

  • bqc_path : path to the Biscuit QC script
  • ref : path to a FASTA file containing the specified reference genome. Note that Biscuit index files must be present in the same directory. Run biscuit index <your_reference_genome>.fa to generate these files (only needs to be done once per genome).
  • bqc_assets : path to directory containing Biscuit QC assets for the specified genome.

If you plan to use the hg38 genome, fill in paths to the reference and Biscuit QC assets for hg38. Likewise, if you plan to use to use the mouse genome, fill in the paths for mm39. You can also add your own genomes by adding another key, e.g.

	params.bqc_assets = [
		hg38: '',
		mm39: '',
		yourNewGenome: '/path/to/bqc/assets'
	]

This file can be re-used across many runs of the pipeline; you only need to update it when you want to analyze your reads against a new reference genome.

Cluster configuration

Depending on the resources available at your site, you may need to specify a different execution engine, job queue, or other variables. Place these in the cluster.config file (see Nextflow docs for details).

Run-specific configuration

Create a copy of the config file example_run.config. Open it in your favorite text editor and update the following fields:

  • in_dir : path to directory containing input fastq files
  • out_dir : path where you want your output files (will be created if it doesn't exist)
  • target_bed : BED file containing regions of the genome you want to analyze (only these regions will be reported in the final R dataframes/files)
  • genome : Genome to align reads to. Must match one of the keys in the ref map mentioned above. E.g. hg38, mm39, or even yourNewGenome if you added a custom genome.
  • bsconv_filter : reads with more than this fraction of unconverted CpH bases will be discarded. The suggested default (0.1) is probably sensible.

Save your new config file, e.g. as 2022_09_23-scwgbs-run.config.

Run it!

nextflow run analysis.nf -c ./conf/2022_09_23-scwgbs-run.config

Note: on at least some systems, the login or head node limits memory allocation to individual users, preventing the Nextflow JVM from starting. I get around this with the following alias:

alias nfr='NXF_OPTS="-Xmx500m" MALLOC_ARENA_MAX=4 nextflow run'

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published