You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have not done thorough testing with anything beyond trios to date. Also, the local assembly graph is not allowed to exceed a configurable maximum number of nodes for any given region. If this number is exceeded, the local assembly is aborted and processing continues without assembled contigs for that region. If the input data are noisy and there are many singleton kmers arising as a result of base errors across multiple samples, you may run into this limit more frequently than with a smaller number of samples.
To see if this limit is reached frequently, run with log level set to TRACE or DEBUG and grep for the following message: Graph too complex for region:. To increase the max number of vertices per assembly graph, use param: --maxn which defaults to 9000.
Additionally, contigs are weighted based upon read support and in cases where a maximum number of contigs is exceeded, those with less read support are not considered. These limits may be more likely to be reached as the number of samples processed is increased. This can apply to assembled contigs (128), contigs arising from high quality soft clipping (16) and contigs arising from indels observed in the initial mappings (8). Not all of these limits are parameterized at the moment.
The text was updated successfully, but these errors were encountered:
Per author suggestions at - mozack/abra2#21 (comment) - of relevance:
We have not done thorough testing with anything beyond trios to date. Also, the local assembly graph is not allowed to exceed a configurable maximum number of nodes for any given region. If this number is exceeded, the local assembly is aborted and processing continues without assembled contigs for that region. If the input data are noisy and there are many singleton kmers arising as a result of base errors across multiple samples, you may run into this limit more frequently than with a smaller number of samples.
To see if this limit is reached frequently, run with log level set to TRACE or DEBUG and grep for the following message:
Graph too complex for region:
. To increase the max number of vertices per assembly graph, use param:--maxn
which defaults to 9000.Additionally, contigs are weighted based upon read support and in cases where a maximum number of contigs is exceeded, those with less read support are not considered. These limits may be more likely to be reached as the number of samples processed is increased. This can apply to assembled contigs (128), contigs arising from high quality soft clipping (16) and contigs arising from indels observed in the initial mappings (8). Not all of these limits are parameterized at the moment.
The text was updated successfully, but these errors were encountered: