lis_vector_set_size(3)

💖 lis_vector_set_size(3) — from the Lis Library Functions, bestie 💖

okay so you're in the lis man pages, section 3, and this one is literally called lis_vector_set_size. it's giving "tell the vector how big it is" energy. let's go 🦋

---

✨ NAME ✨

lis_vector_set_size — assign the size of the vector 💅

---

✨ SYNOPSIS ✨

#include "lis.h"

LIS_INT lis_vector_set_size(LIS_VECTOR v, LIS_INT local_n, LIS_INT global_n);

---

✨ DESCRIPTION ✨

so basically you call this to assign the size of vector v. that's it, that's the whole job. lowkey iconic for how simple it is 🎀

---

✨ INPUT ✨

• v — the vector 👑
• local_n — the size of the partial vector 🌸
• global_n — the size of the global vector 🌈

---

✨ EXIT STATUS ✨

here's what comes back at ya:

• 0 — the process is normally terminated, slay ✨
• unspecified — an error occurred 😭

---

✨ NOTE ✨

okay bestie listen up, this part MATTERS 🫶

either local_n or global_n must be provided. like, at least one of them. not neither, okay?

in the case of the serial and multithreaded environments, local_n is equal to global_n. so therefore, both of these:

lis_vector_set_size(v,n,0)
lis_vector_set_size(v,0,n)

create a vector of size n. same result, no cap 💜

but for the multiprocessing environment it's different, and this is where it gets spicy:

• lis_vector_set_size(v,n,0) creates a partial vector of size n on each processing element.
• lis_vector_set_size(v,0,n) creates a partial vector of size m_p on the processing element p.

and the values of m_p? those are determined by the library. not you. the library. periodt 💅

---

✨ SEE ALSO ✨

• lis(3)
• http://www.ssisc.org/lis/ 🌐

---

okay that's the whole page, you ate that 🍓 go forth and size your vectors, main character. this was the lis_vector_set_size(3) page from the Lis Library Functions, dated 6 Sep 2012 — yes it's vintage but it still hits. mwah 💖🧚‍♀️