We should somehow allow specifying different profiling parameters depending on whether a database is for short-read or long-read use.
e.g. for bracken, a database of 400bp of short read read length doesn't make sense to run with nanopore data.
Could have a column in the database sheet specifying whether a database is for short- or long-read (or both?), and then only samples for e.g. illumina goes is combined with the short-reads, and samples for e.g. annopore goes with long-read databases
Description of feature
We should somehow allow specifying different profiling parameters depending on whether a database is for short-read or long-read use.
e.g. for bracken, a database of 400bp of short read read length doesn't make sense to run with nanopore data.
Could have a column in the database sheet specifying whether a database is for short- or long-read (or both?), and then only samples for e.g. illumina goes is combined with the short-reads, and samples for e.g. annopore goes with long-read databases