route-rnd(1)

👑 route-rnd(1) — the route-rnd manual, but make it cute

okay bestie, sit down, hydrate, because we're about to talk about route-rnd — the external PCB autorouter from the route-rnd manual pages (section 1, obviously, she's a command, she's a main character). 🦋

✨ NAME ✨

route-rnd — external PCB autorouter 💅

✨ SYNPOSIS ✨

(not me spelling it SYNPOSIS, it's literally what the page says, we respect the source 🫶)

route-rnd [-v] -m method [-o out_fn] inp_fn
route-rnd -m method -l
route-rnd -M

✨ DECSRIPTION ✨

(yes, DECSRIPTION. iconic. we don't fix her, we love her. 💖)

So here's the vibe: route-rnd takes a route request in tEDAx form, routes zero or more nets (zero!! she can route nothing and still be valid, queen of boundaries), and hands you back a route result also in tEDAx form.

She also has options to list methods (the algorithms, the little geniuses) and their settings in a computer-readable format. fr fr, machine-readable slay. 🤖✨

✨ OPTIONS ✨

• -M — List available methods (in TSV format) on stdout. That's your menu of algorithms, bestie. 👑
• -m method — Select which method (algorithm) to use. Wanna know the names? They're literally the first column of the -M output. Go look, iykyk. 🎀
• -l — List config options of a method in tEDAx route res format on stdout. ⚠️ Use it together with -m, like a duo, a package deal, a buddy system. Don't show up solo.
• -v — increase verbosity. And the way that you can specify it multiple times?? more vs, more chatting. -vvv is her yapping era. 😭🔥
• -o out_fn — Output file name (for tEDAx route result). Where the finished artwork goes. 🖼️
• inp_fn — Input file name (tEDAx route request). Where the chaos starts. 🌸

✨ SEE ALSO ✨

• pcb-rnd(1) — her sister, her collaborator, the whole family tree. go say hi. 🫶

and that's the whole page, no notes. this was the route-rnd manual, page route-rnd(1), dated 2021-10-10 — so yes she's a little vintage but she still ate, no crumbs. mwah. 💋 💜 🧚 💀 ⭐ 🌈