Add support for tracking the multiplex index sequence. 0.5.4
authorDiane Trout <diane@caltech.edu>
Sat, 17 Sep 2011 00:26:58 +0000 (17:26 -0700)
committerDiane Trout <diane@caltech.edu>
Sat, 17 Sep 2011 00:26:58 +0000 (17:26 -0700)
commitbc27b813d0cdd3513323434405ee2ec5126490e5
tree7553625b883381bb96b73581d58e372fab34ee3d
parent0123277f86af843d47170d56d217f45e7d7cb4a6
Add support for tracking the multiplex index sequence.

I had to add a new table to store the sequence Samples.MultiplexIndex
its manually searched by library type and ID.

There's also some extra complexity in that the multiplex id field
allows entering a comma seperated list to handle the cases where there are
samples that are pooled before being given to us. (As our library actually
represents a single physical tube).

This also adds a --sample-sheet option to attempt to create a sample sheet
for demultiplexing samples.
docs/v0.5.3_to_v0.5.4.sql [new file with mode: 0644]
htsworkflow/frontend/experiments/experiments.py
htsworkflow/frontend/experiments/fixtures/test_flowcells.json
htsworkflow/frontend/experiments/tests.py
htsworkflow/frontend/samples/admin.py
htsworkflow/frontend/samples/fixtures/initial_data.json
htsworkflow/frontend/samples/models.py
htsworkflow/frontend/templates/sample_header.html
htsworkflow/pipelines/retrieve_config.py
htsworkflow/pipelines/test/test_retrive_config.py
scripts/htsw-get-config