Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • tw7649116
    Junior Member
    • Mar 2014
    • 8

    Hello,everybody! Chloroplast genome assembly Q!!

    I'.m doing the chloroplast genome assembly these days, but I haven't learnt any bioinformatics.
    How to do the genome assembly. Now I'm doing the mapping using some software like Bwa, GATK,picard, sickle,and I have got the .bam file.
    Can I using bam to do the assembly?
  • mastal
    Senior Member
    • Mar 2009
    • 666

    #2
    Which assembler to use depends partly on what type of data you have, Illumina, IonTorrent, 454, etc., and whether there is a reference genome for the species you are working on.

    Popular assemblers include velvet, Abyss, Soapdenovo, Mira, 454's Newbler, but there are many others.

    Comment

    • tw7649116
      Junior Member
      • Mar 2014
      • 8

      #3
      Originally posted by mastal View Post
      Which assembler to use depends partly on what type of data you have, Illumina, IonTorrent, 454, etc., and whether there is a reference genome for the species you are working on.

      Popular assemblers include velvet, Abyss, Soapdenovo, Mira, 454's Newbler, but there are many others.
      Thank you for your Re. Im using the illumina pair-end fastq data! It's about rice, so, I have the reference!

      Comment

      • gringer
        David Eccles (gringer)
        • May 2011
        • 845

        #4
        You can use samtools / bcftools to do this. I have modified the vcftools vcf2fq script (link here) to work on VCF files that only contain variant information, as well as properly dealing with INDELs (i.e. changing the sequence, rather than just masking out INDEL regions in lower case). You can use it with a small modification to that specified in the SAMtools man page:

        Code:
        $ samtools mpileup -L ${maxdepth} -uf \
             chloroplast_ref.fasta results/sample1.bam | \
             bcftools view -v -g - > sample1.vcf
        $ ./vcf2fq.pl -Q 20 -L 20 -f chloroplast_ref.fasta output.vcf \
             > con_sample1.fastq
        Basic help for the vcf2fq script:

        Code:
        Usage:   vcf2fq.pl [options] <variant-sites.vcf>
        
        Options: -d INT    minimum depth                   [3]
                 -D INT    maximum depth                   [100000]
                 -Q INT    min RMS mapQ                    [10]
                 -L INT    min INDEL Qual                  [100]
                 -f FASTA  file with reference sequence(s) []
        
        Note: without a reference sequence, sites that are not specified
              in the VCF file will be filled with Ns
        Last edited by gringer; 03-17-2014, 12:26 PM.

        Comment

        • tw7649116
          Junior Member
          • Mar 2014
          • 8

          #5
          Thank you very much!
          I will try first.

          Comment

          • concitacantarella
            Junior Member
            • Oct 2011
            • 7

            #6
            Velvet inquiry about assembling from multiple libraries

            Hi,
            I' m trying to assembly a plastidial genome (about 160000 bp) from a whole genome NGS experiment.

            I installed Velvet using these configuration parameters:

            make 'CATEGORIES=20' 'MAXKMERLENGTH=77' 'LONGSEQUENCES=1' 'OPENMP=1'

            I have 4 paired-end libraries, with different insert-lengths.

            First I aligned reads to reference and extracted mapping reads.
            Second I tried to do de-novo assembling by Velvet:

            velveth velvet/ 43,69,2 -fastq -separate
            -shortPaired
            mappedReads/paired/lib_400_paired_forward.fastq mappedReads/paired/lib_400_paired_reverse.fastq
            -shortPaired2
            mappedReads/paired/lib_500_paired_forward.fastq mappedReads/paired/lib_500_paired_reverse.fastq
            -shortPaired3
            mappedReads/paired/lib_700_paired_forward.fastq mappedReads/paired/lib_700_paired_reverse.fastq
            -shortPaired4
            mappedReads/paired/lib_700_BP_paired_forward.fastq mappedReads/paired/lib_700_BP_paired_reverse.fastq
            -fastq -short
            mappedReads/unpaired/lib_400_unpaired.fastq
            mappedReads/unpaired/lib_500_unpaired.fastq
            mappedReads/unpaired/lib_700_unpaired.fastq
            mappedReads/unpaired/lib_700_BP_unpaired.fastq
            mappedReads/unpaired/lib_single.fastq


            and for each kmer:

            velvetg velvet/_43/ -exp_cov auto -cov_cutoff auto -min_contig_lgth 200 -ins_length 250 -ins_length2 400 -ins_length3 600 -ins_length4 600

            Unfortunately N50 value for each kmer is identical to kmer value.
            (e.g. kmer 59 Result: Final graph has 24686 nodes and n50 of 59, max 897, total 781924, using 2297000/54940402 reads )

            Could anyone help me to understand what am I doing wrong?

            Comment

            • mastal
              Senior Member
              • Mar 2009
              • 666

              #7
              How long are your reads? Maybe the range of kmer values you tried aren't the best ones for velvet.

              What kind of coverage do you have?
              You could try using velvetk to calculate what kind of coverage you would get for different kmers.

              How closely related is the reference genome that you are aligning your reads to?

              Maybe you could try a reference-assisted assembly with velvet instead of de novo.

              Comment

              • concitacantarella
                Junior Member
                • Oct 2011
                • 7

                #8
                > How long are your reads? Maybe the range of kmer values you tried aren't the best ones for velvet.

                Reads are 100 bp. The range is 43 - 69, I think it is large enough

                > What kind of coverage do you have?
                About 57 millions of reads mapping the reference, this is a very large coverage for plastidial genome (about 160000 bp)

                Comment

                • mastal
                  Senior Member
                  • Mar 2009
                  • 666

                  #9
                  In that case the problem could be that you have very high coverage, velvet doesn't do so well with high coverage.

                  Comment

                  • concitacantarella
                    Junior Member
                    • Oct 2011
                    • 7

                    #10
                    Thanks for suggestion.
                    It has been very useful.
                    Setting the right coverage cutoff, I obtained a good result.


                    Originally posted by mastal View Post
                    In that case the problem could be that you have very high coverage, velvet doesn't do so well with high coverage.

                    Comment

                    • laisuliang
                      Junior Member
                      • Jul 2014
                      • 5

                      #11
                      Originally posted by concitacantarella View Post
                      Thanks for suggestion.
                      It has been very useful.
                      Setting the right coverage cutoff, I obtained a good result.
                      Hi concitacantarella!
                      Can you post the velvet parameters what you used, cause I have the same problem like yours. Thanks!

                      Comment

                      • concitacantarella
                        Junior Member
                        • Oct 2011
                        • 7

                        #12
                        hi,
                        I used velvet-estimate-exp_cov.pl to evaluate the coverage-cutoff.

                        this was the runned command line:

                        velvetg _73/ -exp_cov auto -cov_cutoff 500 -min_contig_lgth 200 -ins_length 280

                        Comment

                        • laisuliang
                          Junior Member
                          • Jul 2014
                          • 5

                          #13
                          Originally posted by concitacantarella View Post
                          hi,
                          I used velvet-estimate-exp_cov.pl to evaluate the coverage-cutoff.

                          this was the runned command line:

                          velvetg _73/ -exp_cov auto -cov_cutoff 500 -min_contig_lgth 200 -ins_length 280
                          Thanks! I am using these parameters and it work great.

                          Comment

                          Latest Articles

                          Collapse

                          • SEQadmin2
                            Proteomic Platforms: How to Choose the Right Analytical Strategy to Improve Detection and Clinical Applications
                            by SEQadmin2


                            Proteomics platforms are evolving rapidly, with advances in mass spectrometry and affinity-based approaches expanding what researchers can detect and at what scale. As the field moves toward deeper proteome coverage and clinical applications, scientists face an increasingly complex landscape of tools. This article will explore how researchers are navigating these choices to find the right platform for their work.

                            The systematic characterization of the human proteome has
                            ...
                            07-20-2026, 11:48 AM
                          • SEQadmin2
                            Advanced Sequencing Platforms Tackle Neuroscience’s Toughest Genomics Problems
                            by SEQadmin2



                            Genomics studies in neuroscience face a special challenge due to the brain’s complexity and scarcity of samples. Mapping changes in cell type and state using conventional next-generation sequencing methods remains challenging. Advances in technologies like single-cell sequencing, spatial transcriptomics, and long-read sequencing have opened the door to deeper studies of the brain and diseases like Alzheimer’s, amyotrophic lateral sclerosis (ALS), and schizophrenia.
                            ...
                            07-09-2026, 11:10 AM
                          • SEQadmin2
                            Cancer Drug Resistance: The Lingering Barrier to Rising Survival
                            by SEQadmin2



                            Cancer survival rates have significantly increased in the last few decades in the United States, reaching a combined 70% 5-year survival rate by 2021. Behind this number, there are years of research to find new therapies, drug targets, and early detection methods. But there is one core challenge that keeps slowing down these advances, and it’s about drug resistance.

                            There is no single reason why many patients don’t respond to treatment as expected. Cancer is...
                            07-08-2026, 05:17 AM

                          ad_right_rmr

                          Collapse

                          News

                          Collapse

                          Topics Statistics Last Post
                          Started by SEQadmin2, 07-24-2026, 12:17 PM
                          0 responses
                          25 views
                          0 reactions
                          Last Post SEQadmin2  
                          Started by SEQadmin2, 07-23-2026, 11:41 AM
                          0 responses
                          20 views
                          0 reactions
                          Last Post SEQadmin2  
                          Started by SEQadmin2, 07-20-2026, 11:10 AM
                          0 responses
                          27 views
                          0 reactions
                          Last Post SEQadmin2  
                          Started by SEQadmin2, 07-13-2026, 10:26 AM
                          0 responses
                          38 views
                          0 reactions
                          Last Post SEQadmin2  
                          Working...