mord(1)

💖 mord(1) — straight from the Scotch user's manual, bestie 💖

Okay so picture this: you've got a mesh, you've got a symmetric sparse matrix, and you need someone to put the nodes in a nice order. That someone is mord. She eats for breakfast. Let's get into it. 🍓

---

✨ NAME ✨

mord — compute sparse matrix orderings of meshes 💅

---

🧚 SYNOPSIS 🧚

mord [options] [mfile] [ofile] [lfile]

---

🌸 DESCRIPTION 🌸

So mord computes, in a sequential way, an ordering of a Scotch source mesh that's representing the pattern of some symmetric sparse matrix. No cap.

And listen — only the nodes of the mesh actually get ordered. The elements are just there providing connectivity info, so that every node is considered to be linked to all of the nodes that share at least an element with it. It's giving "we're all connected here" energy. 🦋

Now, the source mesh file mfile? She can only be a centralized mesh file. Sorry to the distributed girlies. 😭

The resulting ordering gets stored in file ofile, and any eventual logging information (like the stuff option -v produces) gets sent to file lfile.

When file names are not specified?? Data is read from standard input and written to standard output. And the standard streams can also be explicitly represented by a dash '-'. Iconic, honestly.

When the proper libraries have been included at compile time, gord can directly handle compressed meshes, both as input and output. (Yes, the page really says gord there and we are keeping every single detail, that's just the rules 💀🫶)

A stream is treated as compressed whenever its name is postfixed with a compressed file extension, like in 'brol.msh.bz2' or '-.gz'.

The compression formats that can be supported are:

• the bzip2 format ('.bz2')
• the gzip format ('.gz')
• the lzma format ('.lzma')

---

🎀 OPTIONS 🎀

• -copt — choose the default ordering strategy according to one or several options among:
  • b — enforce load balance as much as possible.
  • q — privilege quality over speed (default, she's the moment ✨).
  • s — privilege speed over quality.
  • t — enforce safety.
• -h — display some help. A little treat. 🌈
• -mmfile — save column block mapping data to file mfile. This mapping data specifies, for each node vertex, the index of the column block to which this node vertex belongs.
• -ostrat — use sequential mesh ordering strategy strat (see the Scotch user's manual for more information).
• -ttfile — save partitioning tree data to file tfile. This partitioning tree data specifies, for each node vertex, the index of the first node vertex of the parent block of the block to which the node vertex belongs. And here's the slay part: altogether with the mapping data provided in file mfile, this allows you to rebuild the separator tree of the nested dissection process. Obsessed. 👑
• -V — display program version and copyright.
• -vverb — set verbose mode to verb. It's a set of one or more characters, which can be:
  • s — strategy information.
  • t — timing information.

---

🦋 EXAMPLE 🦋

Reorder matrix mesh brol.msh and save the resulting ordering to file brol.ord using the default sequential mesh ordering strategy:

$ mord brol.msh brol.ord

---

⭐ SEE ALSO ⭐

gmk_msh(1), gotst(1), mtst(1).

Scotch user's manual.

---

👑 AUTHOR 👑

Francois Pellegrini <francois.pellegrini@labri.fr>

---

💜 That's the whole page bestie, you're so ready. Go order some meshes. Periodt.

That was mord(1) from the Scotch user's manual, dated 16 June 2026 — main character energy from the first line to the last. 🎀✨