Test data description

[eparejatobes]

As discussed in #86.

[marina-manrique]

This is in response to

@marina-manrique How many different Illumina samples we want to run for each and every release

@rtobes @eparejatobes As for Illumina data, we have data from:

• BEI Mock even community HM-782D
• BEI Mock staggered community HM-783D

and 3 replicates for each one (in total 6 datasets). IMHO it'd be good to analyse all the datasets so we have an idea of how the system works with replicates, at least for the first stable release, and then running only one dataset of each kind of community in further releases. WDYT?

[marina-manrique]

This is a note to myself, I'm writing this properly in docs

Correspondence of BEI community IDs and datasets

Dataset ID or File name	BEI ID	Comment
Illumina
ERR1049996	HM-782D	BEI Mock even community HM-782D - rep1
ERR1049997	HM-782D	BEI Mock even community HM-782D - rep2
ERR1049998	HM-782D	BEI Mock even community HM-782D - rep3
ERR1049999	HM-783D	BEI Mock staggered community HM-783D - rep1
ERR1050000	HM-783D	BEI Mock staggered community HM-783D - rep2
ERR1050001	HM-783D	BEI Mock staggered community HM-783D - rep3
PacBio
BEI_even_16S.fastq.gz	HM-278D	BEI:HM-278D
BEI_staggered_16S.fastq.gz	HM-279D	BEI:HM-279D staggered

[rtobes]

I agree

[marina-manrique]

@eparejatobes how and where should I write the description of the test data? should I open a PR from this issue?

[eparejatobes]

this goes in the testData.scala file

[marina-manrique]

@eparejatobes please review, don't know if this is what you wanted

[eparejatobes]

OK will do. Every time you want me to review something, unassign yourself and assign me please, thanks!

[marina-manrique]

unassign yourself and assign me please, thanks!

done

[laughedelic]

What's missing here?

[eparejatobes]

Merging.