def test_build(self):
chron = ChronoRender()
job = chron.createJob(self.infile)
for robj in job._rndrdoc.renderables:
print robj
for rpass in job._rndrdoc.rndrpasses:
print rpass
def renderSimulations(self):
md = self.verifyMetaData()
frame = int(self.args['framenumber'])
chron = ChronoRender()
job = chron.createJob(md)
job.typefilter = [Simulation]
job.frames = [frame, frame]
job.bOptions = False
chron.runJob(job)
def startDistributedJob(self):
md = self.verifyMetaData()
stream = self.args['renderer']
frames = self.args['framerange']
cr = ChronoRender()
job = cr.createJob(md)
job.frames = frames
# prog = CRLocal()
prog = CRenderLocal()
cr.submitJob(job, prog)
def startLocalRenderJob(self):
md = self.verifyMetaData()
stream = self.args["renderer"]
frange = self.args["framerange"]
# why does cr get what acts like a ChronoRenderBase object
# instead of a ChronoRender object???? (from cr_base not cr.py)
# ANSWER: it calles /light/cr.py's CHronRender which extends
# ChronoRenderBase
cr = ChronoRender()
job = cr.createJob(md, frange, stream)
# job.frames = frange
# print "startLocalRenderJob job.stream = " + job.stream
cr.runRenderJob(job)
def initNewRenderJob(self):
cr = ChronoRender()
job = cr.createJob()
cr.writeJobToDisk(job, self.args['outpath'])
def updateJobAssets(self):
md = self.verifyMetaData()
cr = ChronoRender()
job = cr.createJob(md)
cr.updateJobAssets(job)
