Ticket #777 (closed: fixed)
Group detectors extension for the excitations group
Reported by: | Steve Williams | Owned by: | Steve Williams |
---|---|---|---|
Priority: | major | Milestone: | Iteration 20 |
Component: | Keywords: | ||
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
The spectra in the output workspace are sums of spectra in the input workspace. Which spectra are added to create which spectra depends a map file. As an example, a map file containing the information below will create an ouput workspace where the first spectrum is the sum of 1,2,4 and the second spectrum is the sum of 5,10,11,12,13,14,15.
1 1,2,4 2 5,10-15
Steve has asked for an example file from the excitiations group
Attachments
Change History
Changed 11 years ago by Steve Williams
- Attachment mid_tubes.map added
map file that creates 14 spectra from ~700
comment:2 Changed 11 years ago by Steve Williams
CORRECTION to the file format, I've attached an example map files and the format appears to be (with each name representing a single ASCII integer):
total_number_of_output_spectra output_spectra_number1 number_of_input_spectra1 input_spec1 input_spec2 input_spec3 input_spec4 input_spec5 input_spec6 output_spectra_number2 number_of_input_spectra2 input_spec1 input_spec2 input_spec3 input_spec4 input_spec5 input_spec6 input_spec7 input_spec8 output_spectra_number3 number_of_input_spectra3 input_spec1 input_spec2 ...
Specifing input spectra ranges with "-" is also supposed to be supported
comment:3 Changed 11 years ago by Steve Williams
That format again with line breaks
total_number_of_output_spectra
output_spectra_number1
number_of_input_spectra1
input_spec1 input_spec2 input_spec3 input_spec4
input_spec5 input_spec6
output_spectra_number2
number_of_input_spectra2
input_spec1 input_spec2 input_spec3 input_spec4
input_spec5 input_spec6 input_spec7 input_spec8
output_spectra_number3
number_of_input_spectra3
input_spec1 input_spec2
...
comment:5 Changed 11 years ago by Steve Williams
- Status changed from new to assigned
This could take 2 days to implement including tests because it is complicated in these ways
- the user specification has two variants, using comas or dashes
- the user data will require some checking
- some syntax errors should be fed back to the users so they can see to correct the problem
It should be finished on Wednesday 26 August
comment:10 Changed 11 years ago by Steve Williams
comment:11 Changed 11 years ago by Steve Williams
comment:12 Changed 11 years ago by Steve Williams
- Status changed from assigned to testing
- Resolution set to fixed
comment:13 Changed 11 years ago by Russell Taylor
- Status changed from testing to closed
Tested OK by Martyn.
comment:14 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 1625