COOT(1)

💖 COOT(1) 💖

okay bestie so this is a page from the General Commands Manual — the COOT(1) one, obviously — and we're gonna talk about a lil tool that saves you from naming collisions. sit down, hydrate, let's go 🫶

---

✨ NAME ✨

coot-available-comp-id — no cap, that's the whole name, that's the whole vibe 🌸

---

🌈 SYNOPSIS 🌈

coot-available-comp-id [comp-id|comp-id-prefix]

like… that's it. that's the whole thing. she's lowkey minimal 💅

---

🎀 DESCRIPTION 🎀

so here's the tea: coot-available-comp-id is the girl you call when you're making a new ligand and you need to find a comp-id that nobody's already using. it's giving "is this seat taken" but for ligand names, and honestly? iconic.

a comp-id prefix can be either one or two characters. one or two. not three. we'll get to three. hold on.

if you hand her a 3-character comp-id — like XYZ for example — then coot-available-comp-id will say one of these two things, and only these two things:

INFO:: comp-id XYZ is available

or, the sad one 😭:

INFO:: comp-id XYZ is not available

and if instead you give her a comp-id-prefix? then she'll hit you back with a list of all the available comp-ids that start with that prefix. a whole lil menu. a buffet. we love a list ✨

---

👑 AUTHOR 👑

Paul Emsley — the main character who wrote this, fr fr 💜

---

💀 NOTES 💀

okay important, don't skip this one:

the Coot package needs to be compiled with the CCP4 SRS for this to give useful output.

so if you're out here getting weird or useless results, that's probably why. it's not you, it's the build 🙈

---

and that's the whole page, bestie!! this one comes from the COOT(1) manual — and ngl the footer's just the manual name, no version and no date in sight, so that's all the sign-off we get 💖 stay naming your ligands safely, ily, bye 🦋🎀💅