Open cdmmoeller opened 3 years ago
Hi @cdmmoeller,
From the log file, it seems that the molecule length of your OM data is short. You may try to decrease the settings of the minimum molecule length to ensure there is sufficient data coverage. If you have a draft assembly, you can also try to use it to adjust the parameters by running 'runBNG MQR'.
Cheers, Andy
Hi Andy,
Thanks for your reply.
I tried decreasing the minimum molecule length (-l) to 40kb and minimum number of labels per molecule (-m) to 6, as well as using the parameters output by runBNG MQR. This is my command:
$BNG_DIR/runBNG denovo \
-P saphyr \
-H no \
-e yes \
-t /BiO/Access/cdmm92/resource/bionano/tools/pipeline/Solve3.6.1_11162020/RefAligner/11442.11643rel \
-s /BiO/Access/cdmm92/resource/bionano/tools/pipeline/Solve3.6.1_11162020 \
-b $ASCABER_DIR/Resources/Raw/Bionano/20200616_A_scaber_chamchui__RawMolecules.bnx \
-T 80 \
-l 40 \
-m 6 \
-j 60 \
-z 6000 \
-r $ASCABER_DIR/Analysis/bionano/smartdenovo.nextpolish.curated.0_37_175/fa2cmap/smartdenovo.nextpolish.curated.0_37_175_DLE1_20kb_5labels.cmap \
-a 17 \
-p 1.88 \
-n 0.15 \
-d -0.05 \
-f 0.12 \
-R 0.03 \
-L 640 \
-S 8 \
-o $ASCABER_DIR/Analysis/bionano/smartdenovo.nextpolish.curated.0_37_175/denovo
However, the same error appears. I've attached the stdout. bionano_denovo.o238892.txt
MQR stdout: bionano_MQR.o238775.txt
Do you have any other potential solutions to this issue?
Thanks again, Christian
Hi @cdmmoeller,
From the MQR, the mapping rate is pretty low, do you know the reason? Or can you please decrease the molecule length in the MQR test and see if the parameter changes?
Cheers, Andy
Hi @yuxuanyuan ,
Thanks for taking the time to help.
In MQR, I've tried changing the molecule length from the default 150 to: 50, 90 and 200. It seems that the shorter the molecule lengths, the lower the mapping rate (from 4.32% at -s 50 to 12.3% for -s 90). The other parameters are practically unchanged. MQR_s90.stdout.txt MQR_s150.stdout.txt MQR_s200.stdout.txt MQR_s50.stdout.txt
Could the low mapping rate be caused by the quality of the reference?
Following long-read assembly it's been polished and haplotig-purged. Some basic stats: G: 4.59Gb, Contigs: 34,571, N50: 206.8kb. The BUSCO score is C:86.4%[S:75.5%,D:10.9%],F:2.2%,M:11.4%,n:1614.
The haploid genome size has previously been estimated to be ~6G by flow cytometry and k-mer analysis.
Thanks, Christian
Thanks @cdmmoeller for the info.
I guess one of the reasons is that the assembly is fragmented and the contigs are short. Another reason might be that the quality of the OM data is not good. We recently had an OM experiment and due to some elements binding on DNA, which were not fully removed, the nanochannel was partially blocked when producing the data. Few DNA could pass the channel, which led to the quality of data be bad. In our case, the mapping rate is as low as yours.
Hi @yyx8671
Hope your work goes well. We are suffering from similar problems in this issue. I guess our problems are originated from some elements which blocked the nanochannel as in your comments. If it is possible, could you recommend some methods (or related papers) for removing such elements binding on DNA?
Best,
Hi,
When trying to run the following command with version 2.0.1
I get the following error at the assembly stage:
I am attaching the full stdout.
Could you please help me solve this issue?
Many thanks, Christian bionano_denovo.o238785.txt