The summary parsing code now seems to handle paired end runs
authorDiane Trout <diane@caltech.edu>
Wed, 10 Dec 2008 01:00:25 +0000 (01:00 +0000)
committerDiane Trout <diane@caltech.edu>
Wed, 10 Dec 2008 01:00:25 +0000 (01:00 +0000)
commitb374e7c2d15aca12d5928e7335cbf609c9d7e3a7
treeb77165461886472a82b7c9128d8a85c746b8d5e0
parenta644279b03e32ecea147badd8def47a7b0b16f32
The summary parsing code now seems to handle paired end runs
this required changing how the lane_results were being stored,
previously it was a dictionary indexed by lane, now it is a list
of dictionaries, where the list index indicates which "end" of
a paired end run it is. (0 is the first, 1 is the second)

Also I got tired of being forced to use strings for the lane index
by element tree and modified the code so it converts the strings
required by element tree to integers for our internal dictionaries.
htsworkflow/pipelines/eland.py
htsworkflow/pipelines/gerald.py
htsworkflow/pipelines/summary.py
htsworkflow/pipelines/test/simulate_runfolder.py
htsworkflow/pipelines/test/test_runfolder026.py
htsworkflow/pipelines/test/test_runfolder030.py
htsworkflow/pipelines/test/test_runfolder110.py
htsworkflow/pipelines/test/test_runfolder_ipar100.py
htsworkflow/pipelines/test/test_runfolder_pair.py