Difference: DpHipeTools (21 vs. 22)

Revision 222008-07-08 - NicolaDeCandussio

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

Adding Tools to HIPE

Line: 23 to 23
 

Task Registry

Line: 41 to 42
  For PCSS (PACS' builds) users, this __init__.py file is located at $install_dir/data/toolbox/your_sub_system.
Changed:
<
<
You can also specify that your task belongs to one or more categories ###http://www.rssd.esa.int/SD-general/Projects/Herschel/hscdt/releases/doc/api/herschel/ia/gui/kernel/Tool.Category.html:
>
>
You can also specify that your task belongs to one or more Category :
 
    from herschel.ia.gui.kernel.Tool import Category
    TaskToolFactory.register(compute, [Category.IMAGE, Category.PACS]))

Line: 50 to 51
  Within your task, you can control which parameter signs-up to be the prime parameter (the one which reacts on a selected data variable) by the Task API:

Changed:
<
<
class MyTask extends Task { MyTask() {
>
>
class ComputeTask extends Task { ComputeTask() { super(compute);
  prime=new TaskParameter("spectrum",SpecificProduct.class) : getSignature().setPrimeInput(prime)
Line: 59 to 61
  }
Changed:
<
<
One more thing. If you call super("My Task") within the constructor of class "MyTask", do not have any spaces between the string because this string is the name of the task in HIPE. Thus you should use super("MyTask") instead.
>
>
Naming conventions for task when to be registered in Hipe should follow this example assuming that the task will perform the functionality named "reduce" :
     Name of the Class             : ReduceTask
     Name of the Task (getName())  : reduce
     Name of the variablein Jython : reduce
 
 

Prime input validation

 
This site is powered by the TWiki collaboration platform Powered by Perl