This might actually generate soft file with raw & supplemental data.
authorDiane Trout <diane@caltech.edu>
Tue, 25 Sep 2012 23:18:42 +0000 (16:18 -0700)
committerDiane Trout <diane@caltech.edu>
Tue, 25 Sep 2012 23:18:42 +0000 (16:18 -0700)
commit93f0db5c7e4b67e2fb5dd82a9ce7749343ef81a4
tree456f36f2fd34a9c577a58aa347f37f06b5a5cc0f
parent28242245c13a034387a0e0a000c45e814ee12945
This might actually generate soft file with raw & supplemental data.

To make working with the development server easier, I changed
the submission class to take a host which it will use to generate
the base library url.

When constructing URLs for files, I'm now using the actual path names
instead of synthesizing something based on the submission name.
This is to limit the amount of knowledge that needs to be passed
between the fastq generation code.

For fastq files it looks at the source file to find the flowcell
information. For supplemental files it looks at the submission
class for that analysis directory and grabs the library id
from there.
encode_submission/geo_gather.py
htsworkflow/submission/condorfastq.py
htsworkflow/submission/geo.py
htsworkflow/submission/submission.py
htsworkflow/templates/geo_fastqs.sparql
htsworkflow/templates/geo_files.sparql