Deadline at school

Deadline - Online monitoring

Our Deadline render farm can be monitored online through our monitor website! This is ideal for when you're on the move and unable to VPN into your school computer. It also has ChatGPT error parsing and image previews.

Scherm­afbeelding 2025-03-12 om 17.32.41.png

Deadline Web App by Mervin van Brakel

Deadline - Render managers

From the second year on, every class has 2 render managers. The render managers from all years work together to make sure the farm runs smoothly, and its resources are divided fairly among all the years. Render managers also have admin level access in the deadline monitor, so they can adjust running jobs and worker settings if need be. Sometimes a job needs to be rushed out the door, render managers makes sure that can be done in a way that won't cause any conflicts! Here's a list of the current render managers:

2nd year:

3rd year:

4th year:

Deadline - Temporarily disabling your worker

Sometimes you might not want your computer to be used for farm rendering, for example when you're caching a heavy sim or need to use it for realtime rendering engines like Unreal. In this case you can temporarily take your machine off the farm. Here's how:

First you need to open the Deadline monitor, select your worker and click on Modify Worker Properties.

deadlinemonitor_nB915219wZ.png

There you can go to Extra Info and fill in a reason in one of these two fields, for example your name and what you're doing:

deadlinemonitor_lTzvwWS1XU.png

Once you've filled in a reason, your computer stops picking up new jobs within about a minute. Your worker still shows as enabled in the Monitor; that's normal.

Want your computer to render along again? Simply clear the field.

This is handled by the LocalActivityOptOut event plugin, see Deadline - Event Plugins.

Deadline - Event Plugins

We have a number of custom Event Plugins on our render farm. They are mostly quality of life improvements that keep the farm running smoothly, and most of them work in the background without you having to do anything. Here's a quick overview:

ErrorTriage and FrameValidator explain what they did at the start of the job comment. So if your job behaves unexpectedly, check the comment first!

EnergyCostCalculator

After a job finishes, this plugin calculates its estimated energy cost: the render time of all tasks of the job × the cost per render hour.

It's not a problem if a job is expensive, the render farm is there to be used; but as an artist it's good to be aware that renders aren't free.

Originally written by Mervin van Brakel

ErrorTriage

This plugin looks at every error of a job to figure out what's going on, so you can quickly see what's wrong with your job, and a broken job doesn't keep rendering forever.

You can see what it did at the start of the job comment, prefixed with [ErrorTriage].

Originally written by Robbert Scholten

FrameValidator

After a job finishes, this plugin checks whether all your frames are really there.

A frame is bad when the file is missing, or when it's much smaller than the frames around it (for example a half-written EXR). Gradual changes like fades are not flagged.

The bad frames are listed at the start of the job comment, prefixed with [FrameValidator].

Originally written by Robbert Scholten

HealthCheck

Every render PC checks itself 4× a day (8:00, 12:00, 16:00 and 20:00) for things that can break renders:

If everything is fine, you won't hear from it. If something is wrong, it goes at the start of the Worker comment, prefixed with [HealthCheck date time], and it disappears again once it's fixed. To check right away, select Workers and right-click > Scripts > HealthCheckNow.

This is mainly useful for the render managers; as an artist you don't need to do anything with it, but if you see a [HealthCheck] comment on a PC, you know why it's acting up.

Originally written by Robbert Scholten

LicenseLimiter

Some of our nodes (for example ReduceNoise from NeatVideo) only have a limited number of floating licenses. If every machine on the farm renders frames with that node at the same time, you get license errors.

Some submitters, like our Nuke submitter, send along how many licenses a job may use. On submission, this plugin sets the job's Machine Limit to that number, so no more machines render the job than we have licenses. If you had already set a stricter Machine Limit yourself, that one stays. Jobs without this number are left unchanged.

Originally written by Mervin van Brakel

LocalActivityOptOut

This lets you temporarily take your PC off the render farm, for example when you're running caches on it. See Deadline - Temporarily disabling your worker for a step-by-step guide with screenshots.

Fill in something in your Worker's Extra Info, for example your name or a reason:

As long as something is in there, that PC won't pick up any jobs. Clear the field and the PC renders along again.

Use this fairly; we want as many machines as possible to keep rendering.

Originally written by Mervin van Brakel

NightlyWorkerRestart

Every evening from 21:00, every Worker gets restarted, so the PCs pick up pipeline updates and the farm renders at full power at night.

Only PCs that are switched on and running the Deadline Launcher can be reached.

Originally written by Robbert Scholten

NukeCleanup

Nuke first writes each frame to a temporary .tmp file (something like -935512534559029538.tmp) and renames it when the frame is done. If a render is interrupted, those files are left behind in your render folder.

This plugin cleans them up after a Nuke job. It only removes files with Nuke's own naming, and only if they haven't been touched for 30 minutes, so files from a render that's still running are left alone.

This is our modified, safer version of Deadline's standard NukeCleanup plugin.

Originally written by Robbert Scholten