I tried to replicate the analysis, but the diamond.fasta file is no longer consistent with the XML: some of the sequences have new identifiers. The identifiers have changed because they contain the time stamp of the sequence and removing one of the sequences has changed the distribution of the sequences across the day. It's good to see that the changes have propagated through the files but means that you need to tweak the XML for it to run.
I'm closing this because I think it is out of scope if we have verified that the pipeline all works and we have the correct hash for the diamond.fasta now.
Description
I tried to replicate the analysis, but the
diamond.fasta
file is no longer consistent with the XML: some of the sequences have new identifiers. The identifiers have changed because they contain the time stamp of the sequence and removing one of the sequences has changed the distribution of the sequences across the day. It's good to see that the changes have propagated through the files but means that you need to tweak the XML for it to run.Files involved
./data/readme.org
./data/diamond.fasta
./xml/timtam-timeseries-stage-2-with-removal-prevalence-HKY-weekly-histories.xml
To reproduce
diamond.fasta
todata/
and usesha256sum diamond.fasta
to see it is goodant setuplib
ant mcmc
for error messagecat data/diamond.fasta | grep ">"
tocat data/readme.org | grep "^DP"
to see these are differentTasks
Here are some loose suggestions, there are probably cleaner solutions.
diamond.fasta
and store this mapping somewhere else so labels do not include analysis results.readme.org
.