Taskjuggler scenario bug(?)

[vijay]

I have a task defined as follows
task anhcd "PCS Rate" {
      effort 1d depends mtip.inputs.ml0p5
      allocate gene
      initial:allocate basvaraj
    }
Post scheduling I am seeing the task for both the scenarios allocated to gene

Hydra PCS Rate	Initial	not started	1.0	Gene (gene)	2013-02-13
	Plan	not started	1.0	Gene (gene)	2013-02-15

Similarly for the very next sibling task (Same parent tasks) defined as

    task regif "MTIP Slave generic" { effort 9d
      allocate jaydip
      initial:allocate basvaraj }

MTIP Slave generic	Initial	not started	9.0	r2 (jaydip), Basvaraj (basvaraj)	2013-02-20
	Plan	not started	9.0	r2 (jaydip)	2013-02-21

The most frustrating part is that I am editing some other totally unrelated section (Different hierarchy, same root task) of the plan and for some compiles the above two tasks are scheduled Ok and for some others it again goes for a toss.
Regards
Vijay

[Chris Schlaeger]

On Thu, Feb 7, 2013 at 3:39 AM, vijay <jahagi...@gmail.com> wrote:

task anhcd "PCS Rate" {
      effort 1d depends mtip.inputs.ml0p5
      allocate gene
      initial:allocate basvaraj
    }
Post scheduling I am seeing the task for both the scenarios allocated to gene

That's how it's supposed to work.

allocate gene

will create an allocation attribute for your top-level scenarios and all derived scenarios. Since it's a list attribute

initial:allocate basvaraj

will only append basvaraj to the list for the 'initial' scenario. Looks like basvaraj is assigned to other tasks, so you will not see the allocation for this task.

Try

allocate gene

initial:purge allocate

initial:allocate basvaraj

Chris