Difference: DpHipeTools (37 vs. 38)
Revision 382009-04-22 - JaimeSaiz
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
Adding Tools to HIPE | ||||||||
| Line: 82 to 82 | ||||||||
The mechanism above makes you task to become a tool within the system and it appears whenever a variable of type | ||||||||
| Changed: | ||||||||
| < < | Sometimes this may not be enough, e.g. is certain situations your task will only run on a SpecificProduct if it contains certain contents. A typical situation would be when a SPIRE reduction operates on a ObservationContext: such a task should not be listed whenever a HIFI observation is selected... | |||||||
| > > | Sometimes this may not be enough, e.g. in certain situations your task will only run on a SpecificProduct if it contains certain contents. A typical situation would be when a SPIRE reduction operates on a ObservationContext: such a task should not be listed whenever a HIFI observation is selected... | |||||||
You can write a ParameterValidator to do just that:
| ||||||||
