Features

Directory: /nethome/users/{user-name}/{pipeline-dir}/pipeline/pipeline/
Filename: groups.xml

Format

<Groups>
<Group name="your-groupname" parent="your-parentgroupname" priority="yourpriority" numProcessors="your-numberOfProcessorsAllowedForGroup"/>
<Group name="neuro" parent="0" priority="10" numProcessors="20">
<Group name=...    .../>
<Group name=...    .../>
...
...
<Group name=...    .../>
</Groups>

Variable Definitions

groupname: : Name of the group
parentgroupname: : The name of the parent group that this group belongs to
priority: : The priority at which the processes executing in the context of this group should run
numProcessors: : The number of processors that this group is allowed

Rules

1. The root group is identified when the group definition provides a string "0" (the numeral Zero as a string) under parentgroupname
2. Each group A's definition should preceed its usage as a parent for any other group B. For eg., if B is A's child,
   the definition of A should preceed that of B
3. The words "grid", "modulemonitor", "systemhelperprocess" etc should not be used for group names as they are keywords
4. The higher the numeric value of priority, the lower its semantic priority! Just like Unix, 0, 1, 2 have higher
   priority than 3 than 4 than 5 etc.
5. On any given branch of the group tree (that results from this file), the numProcessors should monotonically increase from the child to the root. That is, if A is the root Group, and B is a child of A and C is a child of B, then,

         {numProcessors(C)  <= numProcessors(B) <= numProcessors(C)} 
   
   should be ensured for all branches of the tree!
   

-- JagadeeswaranRajendiran - 22 Mar 2005