Ticket #362 (closed: fixed)
Allow for parameters in instrument definition file
Reported by: | Anders Markvardsen | Owned by: | Anders Markvardsen |
---|---|---|---|
Priority: | major | Milestone: | Iteration 15 |
Component: | Keywords: | ||
Cc: | nick.draper@… | Blocked By: | |
Blocking: | Tester: |
Description
Allow, for example, the 'x','y' or 'z' position of a component defined in an instrument definition file (IDF) to be determined by values in the logfiles of ISIS measurements.
The user should be done allowing to specify <parameter> elements in the IDP that have the attributes:
parameter-name (e.g. 'x') type (default = double) logfile-id (equal to logfile filename minus run number and file extension) eq (short for equation: value from logfile may need to be converted) extract-single-value-as (how to extract value from logfile)
Change History
comment:2 Changed 12 years ago by Anders Markvardsen
(In [1833]) Add methods to: TimeSeriesProperty, PropertyMap, LoadRaw2, Instrument, LoadInstrument and added class: XMLfilename to handle the info about parameter/logfiles defined in instrument definition files.
Got to the stage where parameter map of workspace is populated, for now using the first value in a logfile. Refs #362.
comment:10 Changed 12 years ago by Anders Markvardsen
comment:11 Changed 12 years ago by Anders Markvardsen
- Status changed from assigned to closed
- Resolution set to fixed
comment:12 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 1210