From: Stefan Andersson <sanders3d@(email surpressed)> Subject: Render Elapsed Date: Thu, 12 Jan 2006 10:52:26 -0500 |
Msg# 1181 View Complete Thread (2 articles) | All Threads Last Next |
Hello, I was wondering about the "Elapsed" column in the iRush menu (regardless of the new or the old). It shows how long it's been in the que, not how long it has actully rendered. I have one job which tells me in the iRush menu that it's been there for 190:31:08 and if I press the "frame info" button I can see a log saying "Render Elapsed: 00:30:36". Is it possible to have the "Render Elapsed" showing in the column instead of the "Elapsed"? best regards stefan andersson -- ________________________________________________________________________ http://stefan.sanders3d.com/ http://os3d.blogspot.com/ |
From: Greg Ercolano <erco@(email surpressed)> Subject: Re: Render Elapsed Date: Thu, 12 Jan 2006 16:33:47 -0500 |
Msg# 1182 View Complete Thread (2 articles) | All Threads Last Next |
Stefan Andersson wrote: I was wondering about the "Elapsed" column in the iRush menu (regardless of the new or the old). It shows how long it's been in the que, not how long it has actully rendered. I have one job which tells me in the iRush menu that it's been there for 190:31:08 and if I press the "frame info" button I can see a log saying "Render Elapsed: 00:30:36". Is it possible to have the "Render Elapsed" showing in the column instead of the "Elapsed"? The "Frame Info" button (rush -lfi) is currently the only way to view the accumulated cpu time for the job.. this operation shows other specifics as well, including average per-frame render times. I've been thinking about making the 'rush -lj' report more flexible from within irush, so that specific fields can be added/removed. But currently that's not available. Currently the only way to add the info you're requesting is to make a wrapper script for 'rush' that checks for the -lj and -laj options, and if found, merges in the desired field(s) from the -lfi report, inserting it as a new column. irush(1) will automatically parse the new field, assuming it has a heading like all the other columns, and is added as one of the columns at the right. I would not remove the elapsed field, as that's needed to determine how old a job is, so that old jobs can be dumped. I'd suggest adding the render time as a new column between the existing BUSY and ELAPSED columns. -- Greg Ercolano, erco@(email surpressed) Rush Render Queue, http://seriss.com/rush/ Tel: (Tel# suppressed) Cel: (Tel# suppressed) Fax: (Tel# suppressed) |