In the latest set of data I build, which includes the new MG505 data, there appears to be an issue with the timepoint mappings.
These data were built with the --separate-timepoints setting, which should mean that only one timepoint is present in the data. However, we see weird things like this in the trees:
It looks like we're having name clashes in the lookup method we use for aggregating over the duplicity information. I think all that's necessary is to ensure that in the separate timepoints version, where we use the original sequence names, we make sure we're looking at the right timepoint.
In the latest set of data I build, which includes the new MG505 data, there appears to be an issue with the timepoint mappings.
These data were built with the
--separate-timepointssetting, which should mean that only one timepoint is present in the data. However, we see weird things like this in the trees:It looks like we're having name clashes in the lookup method we use for aggregating over the duplicity information. I think all that's necessary is to ensure that in the separate timepoints version, where we use the original sequence names, we make sure we're looking at the right timepoint.