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
Giving the single clade timeseries workflow a community with multiple clades causes the number of clades to become the analysis' number of samples.
This error can be reproduced by using a 3 clade community and 4 time points. (num_samples != number of clades) The workflow progresses up to deconvolution, where the numbers get mixed up (so to speak). Downstream at measure_accuracy.py the incorrect number of strains is used and you can get indexing errors.
Either an assertion is overlooked at a Process level or in munging channels.
The text was updated successfully, but these errors were encountered:
cerebis
changed the title
Weird results when single clade timeseries is given a multiple clade community
Unintended continuation when single clade timeseries is given a multiple clade community
Dec 1, 2016
Giving the single clade timeseries workflow a community with multiple clades causes the number of clades to become the analysis' number of samples.
This error can be reproduced by using a 3 clade community and 4 time points. (num_samples != number of clades) The workflow progresses up to deconvolution, where the numbers get mixed up (so to speak). Downstream at measure_accuracy.py the incorrect number of strains is used and you can get indexing errors.
Either an assertion is overlooked at a Process level or in munging channels.
The text was updated successfully, but these errors were encountered: