lis_esolver_get_evalues(3)

πŸ“¦ version 2.1.11, in fedora 43, fedora 44, nixos 26.05, nixpkgs unstable

✨ NAME ✨

lis_esolver_get_evalues β€” bestie, this is the one that pulls all the eigenvalues out of the eigensolver πŸ’– (it's a lis library function, from the lis manual, section 3, iykyk)


🌸 SYNOPSIS 🌸

#include "lis.h"

LIS_INT lis_esolver_get_evalues(LIS_ESOLVER esolver, LIS_VECTOR v);

Like. That's the whole vibe. Two args, one dream 🫢


πŸ’… DESCRIPTION πŸ’…

Okay so, what this does: it gets all the eigenvalues from the eigensolver. That's it. That's the function. No cap, that's genuinely the whole job β€” the eigensolver has been doing its little eigenvalue thing in the background and this is how you're like "hand them over bestie" πŸŽ€


🌈 INPUT 🌈

  • esolver β€” the eigensolver. The main character. The one holding all the eigenvalues you're about to steal 🧚

πŸ¦‹ OUTPUT πŸ¦‹

  • v β€” the vector which stores the eigenvalues. She's the container, she's doing the heavy lifting, she's holding every single eigenvalue for you πŸ’œ

πŸ”₯ EXIT STATUS πŸ”₯

The following exit values are returned:

  • 0 β€” the process is normally terminated. Slay. Everything worked, we love to see it ✨
  • unspecified β€” an error occurred 😭 no further details given, it's giving mystery, it's giving undefined

πŸ’€ NOTE πŸ’€

Real talk, do not skip this one: the vector v must be created in advance with the function lis_vector_create. You can't just roll up with an uncreated vector and expect results. She needs to exist first, periodt πŸ™ˆ

πŸ“ SEE ALSO πŸ“


Okay that's the whole page bestie, you ate that πŸ’– This was the lis_esolver_get_evalues(3) man page from the Lis Library Functions, dated 28 Aug 2014 β€” go forth and collect your eigenvalues, you've got this πŸ‘‘πŸŒΈπŸ’…

πŸ“¦ where this page comes from