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)

In article <1091-rush decimal general at seriss decimal com>,
 Greg Ercolano <erco@(email surpressed)> wrote:

> 	by www.3dsite.com (8.12.8/8.12.8) with SMTP id jA41NkFH019694
> 
> 	for <rush decimal general at seriss decimal com>; Thu, 3 Nov 2005 17:23:46 -0800
> Received: (qmail 48305 invoked from network); 4 Nov 2005 01:24:41 -0000
> Received: from unknown (HELO ?192.168.0.9?) (unknown)
> 
>   by unknown with SMTP; 4 Nov 2005 01:24:41 -0000
> X-pair-Authenticated: 24.205.66.40
> Organization: Seriss Inc.
> User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
> X-Accept-Language: en-us, en
> MIME-Version: 1.0
> To: rush decimal general at seriss decimal com
> In-Reply-To: <1090-rush decimal general at seriss decimal com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
> Path: 3dsite.com
> Xref: 3dsite.com rush.general:1091
> NNTP-Posting-Host: localhost
> 
> 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
> [..]

Cool.  I might have eventually thought of that!  I'll also see if I 
might be able to get my hands on the script I used before, if it's not 
too proprietary.

Thanks.

- Jance