Skip to content

running with a merged fastq file #354

@yeroslaviz

Description

@yeroslaviz

Thank you @rrwick for a great tool.

I was wondering what the reason behind the --kmers parameter.

I have samples which were sequenced twice, the second time was done to increase the sequencing depth. Unfortunately the second run was done with a different machine and a different read length.

When I try to run unicycler on the merged fastq files i it fails when it tries to calculate kmers of length 61. the older fastq file is only 60nt long.

Does it make more sense to give the too a specific list of parameters e.g. --kmers 13,25,33,39,45,49,53,57 or is it better to work with the files separately

thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions