Difference: DpHipeTools (64 vs. 65)

Revision 652011-03-22 - DavidSharpe

Line: 1 to 1
META TOPICPARENT name="WritingTasks"

Adding Tools to HIPE

Line: 82 to 82
 Warning, important For naming tasks follow the Java conventions, that is, use camelCase and avoid underscores: reduceLight is valid, reduce_light is not. HIPE displays info log messages for invalid task names. Note that task names are used as variable names (of type Task) automatically created when starting HIPE.

Validating prime input

In most cases, the type of the prime input is not enough to determine whether a task is applicable to a variable. Your task may only run on a SpecificProduct if it contains certain contents: a typical example is a SPIRE task operating on an ObservationContext: clearly, such task should not be listed when a HIFI observation is selected.
This site is powered by the TWiki collaboration platform Powered by Perl