ADRT_SLAVE(1)

πŸ“¦ version 7.44.0, in nixpkgs unstable

✨ ADRT_SLAVE(1) ✨ β€” the BRL-CAD glow-up edition πŸŽ€

okay so picture this: you open the manual for adrt_slave(1), right? and it's giving distributed ray-tracing rendering worker energy. that's the whole vibe. it's part of the BRL-CAD fam, and yes bestie, it's lowkey iconic πŸ’…


🌸 NAME 🌸

adrt_slave β€” the ADRT distributed ray-tracing rendering worker. that's it, that's the girl 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

adrt_slave [-v] [-h] [-p port] [-t threads] [host]

like, that's the whole summoning ritual. so clean ✨


πŸ’– DESCRIPTION πŸ’–

okay so adrt_slave is a rendering worker for the Advanced Distributed Ray Tracer (ADRT). ngl that's a whole mouthful but basically: it receives geometry and per-tile work units over a network socket, ray-traces them with the librender TIE engine, and then sends the rendered pixels back to the dispatcher β€” or, if you're doing a different kind of run, the shotline, component, and bounding-box results. yes, all three. she does it all 😭πŸ”₯

and here's the slay part: multiple slaves cooperating with a single dispatcher let a single image be rendered in parallel across many machines. it's literally main character energy for your cluster. one image, so many machines, no cap πŸ‘‘

so, the fork in the road:

  • if you give a host argument β€” adrt_slave connects to the ADRT dispatcher running on that host (default port 1980). she's the one reaching out πŸ’Œ
  • if you give no host β€” the slave runs as a daemon and listens for an incoming connection (default port 1981). now she's waiting by the phone πŸ™ˆ

either way, the geometry to render is supplied by the dispatcher, adrt_master(1), and the network rendering session is driven by isst(1). those two are the ones running the show, we're just here to render bestie 🧚


⭐ OPTIONS ⭐

  • -p port β€” use the given TCP port instead of the protocol default. and the default is context-dependent, so pay attention: 1980 when connecting to a host, 1981 when running as a daemon. two different defaults, one flag, we love a versatile queen 🌈
  • -t threads β€” launch threads rendering threads per slave. yes the manpage really says "threads rendering threads," we're keeping it exactly as it is πŸ’€. the value is clamped to the range 0-32, and 0 lets the engine choose based on the available cores. so don't try to be cute with 64, she will clamp you.
  • -v β€” print the ADRT version and exit. quick little vibe check, then she's gone ✌️
  • -h β€” print a usage summary and exit. the classic "help me help you" move 🫢

πŸ”₯ EXAMPLES πŸ”₯

Example 1. Run a slave as a daemon awaiting work 🌸

adrt_slave -t 8 -p 1981

start a worker that listens on port 1981 using eight rendering threads. then a dispatcher (for example, one launched from isst(1)) can connect to this host and hand it tiles to render. she's just sitting there, ready, waiting for the work to arrive. patient icon behavior tbh πŸŽ€

Example 2. Connect a slave to a running dispatcher πŸ¦‹

adrt_slave -t 16 dispatcher.example.com

connect to the ADRT dispatcher on the host dispatcher.example.com (port 1980) and contribute sixteen rendering threads to the rendering pool. and here's the move: launching this command on several machines pointed at the same dispatcher spreads the work of a single frame across the cluster. that's the group chat coming together to get one thing done. teamwork fr fr πŸ’œ


πŸ‘‘ SEE ALSO πŸ‘‘

brlcad(1), adrt_master(1), isst(1), rt(1)

go read those too, bestie, they're literally the supporting cast 🫢


πŸ’… AUTHOR πŸ’…

BRL-CAD Team β€” the collective. the whole squad. respect ✨


This software is Copyright (c) 1989-2026 by the United States Government as represented by U.S. Army Research Laboratory.

(that's a lot of years of copyright and honestly? iconic longevity πŸ’€πŸ‘‘)


🧚 BUG REPORTS 🧚

Reports of bugs or problems should be submitted via electronic mail to devs@brlcad.org

ngl if you find a bug, tell them!! they literally want to know!! don't just sit there suffering in silence, that's not the vibe πŸ˜­πŸ“§

and that's the page!! mwah πŸ’– stay rendering, stay parallel, and remember β€” this beauty came to you from BRL-CAD, so go forth and distribute that ray tracing bestie πŸŒˆβ­πŸŽ€

πŸ“¦ where this page comes from