Author Topic: blocking work  (Read 2975 times)

nine020ho

  • Full Member
  • ***
  • Posts: 10
blocking work
« on: January 11, 2005, 07:29:23 PM »
i am trying to setup an mi render scenario where i create jobA to render the miFiles and jobB to generate the miFiles.

I create jobA  and set all of its work to be blocked.
When jobB creates an MI file, I unblock the work in jobA for that file.

The problem i find is that because all of the work in jobA is set to blocked, it sets the entire job to be blocked. 

Do I have to set all of jobA to unblocked each time I want a piece of its work that is now unblocked to run?


eric

  • Hero Member
  • *****
  • Posts: 229
Re: blocking work
« Reply #1 on: January 12, 2005, 01:02:21 AM »
I create jobA? and set all of its work to be blocked.
When jobB creates an MI file, I unblock the work in jobA for that file.

I'll assume that when you submitted jobA, it went in blocked.

Quote
The problem i find is that because all of the work in jobA is set to blocked, it sets the entire job to be blocked.?

That's right.

Quote
Do I have to set all of jobA to unblocked each time I want a piece of its work that is now unblocked to run?

What you need to do is unblock both the job and the work item. On your backend, when you finish the frame, and make the request to the supervisor for another frame, you should check the error status. If there are no unblocked frames, the supe will send you a blocked status in the work item. Just set the subjob status to blocked, and exit.

I think if you check in our examples directory, we have some code for setting up the frontend. The types/frame directory should contain code with the correct behavior for a backend.