icetBoundingVertices(3)

✨ NAME ✨

icetBoundingVertices — set bounds of geometry. periodt. 💅

okay so you're reading icetBoundingVertices(3), bestie, straight outta the IceT Reference manual, and it's giving “tell IceT where your geometry lives” energy. 🦋

---

🦋 Synopsis 🦋

#include <IceT.h>

void icetBoundingVertices(   IceTInt            size,
                             IceTEnum           type,
                             IceTSizeType       stride,
                             IceTSizeType       count,
                             const IceTVoid *   pointer  );

---

🌸 Description 🌸

okay so icetBoundingVertices is literally how you tell IceT what the bounds are for the geometry drawn by the callback you registered with icetDrawCallback or icetGLDrawCallback. The bounds are assumed to be the convex hull of the vertices you give it. And bestie, you gotta make sure the drawn geometry actually fits inside that convex hull, because if it doesn't, the data may be culled in unexpected ways 😭. IceT runs most efficiently when the bounds you give are tight (like, they match the actual volume of the data well) and when the number of vertices you give is minimal. lowkey iconic efficiency behavior. ✨

Here's the parameter tea, fr fr:

• size — specifies the number of coordinates given for each vertex. Coordinates are given in X-Y-Z-W order. Any Y or Z coordinate not given (because size is less than 3) is assumed to be 0.0, and any W coordinate not given (because size is less than 4) is assumed to be 1.0.
• type — specifies in what data type the coordinates are given. Valid types are ICET_SHORT, ICET_INT, ICET_FLOAT, and ICET_DOUBLE, which correspond to types IceTShort, IceTInt, IceTFloat, and IceTDouble, respectively.
• stride — specifies the offset between consecutive vertices in bytes. If stride is 0, the array is assumed to be tightly packed.
• count — specifies the number of vertices to set.
• pointer — is an array of vertices with the first vertex starting at the first byte.

If data replication is being used, each process in a data replication group should register the same bounding vertices that encompass the entire geometry. By default there is no data replication, so unless you call icetDataReplicationGroup, all process can have their own bounds. no cap. 💖

---

💀 Errors 💀

• ICET_INVALID_ENUM — raised if type is not one of ICET_SHORT, ICET_INT, ICET_FLOAT, or ICET_DOUBLE. so don't do that, bestie. 💅

---

🙈 Warnings 🙈

None. like, zero. nada. 🫶

---

🐛 Bugs 🐛

None known. we love a bug-free era. 👑

---

👑 Copyright 👑

Copyright (C)2003 Sandia Corporation

Under the terms of Contract DE-AC04-94AL85000 with Sandia Corporation, the U.S. Government retains certain rights in this software.

This source code is released under the New BSD License.

---

🔥 See Also 🔥

• icetBoundingBox(3)
• icetDataReplicationGroup(3)
• icetDrawCallback(3)
• icetGLDrawCallback(3)

---

that's the whole page, bestie. source/version: IceT Reference · date: September 20, 2010 · page: icetBoundingVertices(3) 💖✨ stay slay. 💅