How to use BBmap (mutate.sh) to simulate the human genome?
0
0
Entering edit mode
4.6 years ago
kamanovae ▴ 100

Hi! I want to simulate the human genome. I found a suitable BBMap mutate.sh) program. The mutate.sh only outputs reads that contain mutations. But I need to get a fast output file that would contain reads with mutation and without mutations. I want to try to maintain the coverage of the reference genome. How can i do this?

Now I use the command to run:

1.bbmap/mutate.sh in=reference/gh19.fasta out = reference/hg19_with_mut.fasta id = 0.99 prefix = bbmap

I can use the program BBMap randomreads.sh) , but it looks much more difficult to run and I'm afraid to unconsciously get an undesirable result

simulation human genome bbmap • 1.2k views
ADD COMMENT
1
Entering edit mode

One does not really simulate a genome but you simulate reads using the reference for that genome. randomreads.sh is not difficult to run.

Do you need to simulate a genome at this point? There are plenty available in databases. You can run mutate.sh on one of them to introduce the mutations, if you don't want to simulate a new dataset.

ADD REPLY
0
Entering edit mode

At this stage, I need to introduce mutations in the reference genome, and then I plan to use the NanoSim program to simulate nanopore reads. My final goal is nanopore reads with introduced mutations. Which program is better for the first step?

ADD REPLY
0
Entering edit mode

Then use mutate.sh.

Written by Brian Bushnell
Last modified August 6, 2019

Description:  Creates a mutant version of a genome.

Usage:  mutate.sh in=<input file> out=<output file> id=<identity>

I/O parameters:
in=<file>       Input genome.
out=<file>      Output mutant genome.
vcf=<file>      Output VCF file showing variations added.

Take a look at processing parameters to control the mutations.

ADD REPLY

Login before adding your answer.

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