From: jance <powerjance@(email surpressed)>
Subject: binary render order?
   Date: Thu, 03 Nov 2005 16:58:16 -0800

At a facility I worked at that used Rush, there was an option in the 
submit scripts for the render order, where you could render in order 
(1,2,3,4,5...) or a "binary" order (first, last, middle...).  This was 
really handy because you could kick off your render and wait for three 
frames and you could spot check your shot.  I don't see that in the 
default submit scripts; was that something the facility put in 
themselves or am I missing something?

Thanks for any help!

jance wrote:

[posted to rush.general]

At a facility I worked at that used Rush, there was an option in the submit scripts for the render order, where you could render in order (1,2,3,4,5...) or a "binary" order (first, last, middle...). This was really handy because you could kick off your render and wait for three frames and you could spot check your shot. I don't see that in the default submit scripts; was that something the facility put in themselves or am I missing something?

	Sounds like a customization.

	Either they submitted the job and changed the frame order afterwards
	with 'rush -reorder', or they tweaked the submit logic to break out
	the frame range into individual frames in the order they wanted.

	FWIW, if you just want the first few frames rendered to be first/middle/last,
	you can specify them in the 'Frames:' window manually, ie. instead of:

		Frames: 1-100

	..you can say instead:

		Frames: 1 50 100 2-49 51-99

	..which will get you a frame list where 1, 50 and 100 render first,
	followed by the rest in regular order:

STAT FRAME   TRY HOSTNAME        PID     JOBID            START          ELAPSED  NOTES
Done 0001    1   ontario         29811   ontario.57       11/03,17:21:32 00:00:11
Done 0050    1   ontario         29814   ontario.57       11/03,17:21:44 00:00:11
Done 0100    1   ontario         29817   ontario.57       11/03,17:21:56 00:00:11
Done 0002    1   ontario         29821   ontario.57       11/03,17:22:08 00:00:11
Done 0003    1   ontario         29824   ontario.57       11/03,17:22:20 00:00:11
Done 0004    1   ontario         29827   ontario.57       11/03,17:22:32 00:00:11
Done 0005    1   ontario         29830   ontario.57       11/03,17:22:44 00:00:11
Done 0006    1   ontario         29833   ontario.57       11/03,17:22:56 00:00:11
Done 0007    1   ontario         29836   ontario.57       11/03,17:23:08 00:00:11
Done 0008    1   ontario         29839   ontario.57       11/03,17:23:20 00:00:11
Done 0009    1   ontario         29842   ontario.57       11/03,17:23:32 00:00:11
[..]

--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)

I lost a render machine yesterday and had to rebuild it. During the time I
was doing this the rest of the render farm told me that the host that was
down was holding onto jobs. When I managed to bring the machine back (after
a complete system re-install) I restarted rush but the job didn't continue.
I have tried dumping the job but it stays in a state of Dump and has been
there over night.

I'm guessing it's because the rush installation on the rebuilt machine is
out of sync with the rest of the machines. How can I remove the job from all
the machines?



--
Dylan R. Penhale

Ella Enchanted
Goldcrest Post Production
London
United Kingdom

Email:  Dylan@(email surpressed)