If users realize part way through a render job that they no longer want the render what is the best way to keep the metrics valid without losing the data for the partially rendered job?
My current work flow doesn’t keep all the data accurate. I would appreciate any tips on how to accomplish this.
thanks
Are you referring to the individual task stats that we keep for completed tasks? Those should be maintained even if the render job is suspended. Note that we don’t keep stats for tasks that are currently rendering, so if you suspend those tasks, it’s not like any data is being lost.
I think I might be misunderstanding your problem, so if I am, could you perhaps describe it in more detail?
Cheers,
I think he means if the job is deleted. He still wants to keep track of the stats for the frames that rendered. I wanted the same thing…so I created a mysql database to keep the data, and entered the data in a post task script.
I have the users suspend the jobs when they dont want them to continue
unless i am missing something the stats from suspended jobs aren’t stored in the repository statistics.
If they are then I have overlooked this.
so do you recommend that when a job is not needed and its partially rendered that I just suspend them and then the stats will end up in the appropriate place?
i just need a process to save the data from jobs that dont finish.
i can instruct the users to either delete, suspend or whatever as long as i have a process to stop them mid job and keep the data.
Ah, I understand. Only completed jobs stats are stored in the repository stats at the moment. It is possible to write your own stats system though (as Lehm metioned), and use post-task/job scripts or have a separate application that uses DeadlineCommand (franticfilms.com/software/su … ommand.php) to query repository information and store it.
Cheers,