DGET38(3)

💅 dget38.f(3) — Library Functions Manual

Okay bestie, so this one lives at /home/abui...IG/dget38.f(3) in the manual — it's a LAPACK testing file, and yes, the header is a whole journey. Buckle up 🎀

---

✨ NAME ✨

/home/abuild/rpmbuild/BUILD/lapack-static-3.12.0-build/lapack-3.12.0/TESTING/EIG/dget38.f

Like... that's the whole name. That's the path. She's giving "I was compiled once and never emotionally recovered" 😭 but it's literally the test source file for DGET38, so slay.

---

🌸 SYNOPSIS 🌸

Functions/Subroutines

• subroutine DGET38 (rmax, lmax, ninfo, knt, nin) — the one and only DGET38, here to do her little testing thing 💖

subroutine DGET38 (rmax, lmax, ninfo, knt, nin)

---

🦋 Function/Subroutine Documentation 🦋

subroutine DGET38 (double precision, dimension( 3 ) rmax, integer, dimension( 3 ) lmax, integer, dimension( 3 ) ninfo, integer knt, integer nin)

subroutine DGET38 (double precision, dimension( 3 ) rmax, integer, &
                   dimension( 3 ) lmax, integer, dimension( 3 ) ninfo, &
                   integer knt, integer nin)

DGET38 — that's her name, that's her whole brand 👑

🧚 Purpose:

!> !> DGET38 tests DTRSEN, a routine for estimating condition numbers of a !> cluster of eigenvalues and/or its associated right invariant subspace !> !> The test matrices are read from a file with logical unit number NIN. !>

So basically: DTRSEN estimates condition numbers for a cluster of eigenvalues and/or its associated right invariant subspace, and DGET38 is the girl whose entire job is testing whether that's actually working. Iconic behavior, no notes. 💅 And the test matrices? They get read from a file — logical unit number NIN, iykyk.

---

🎀 Parameters 🎀

RMAX

!> RMAX is DOUBLE PRECISION array, dimension (3) !> Values of the largest test ratios. !> RMAX(1) = largest residuals from DHST01 or comparing !> different calls to DTRSEN !> RMAX(2) = largest error in reciprocal condition !> numbers taking their conditioning into account !> RMAX(3) = largest error in reciprocal condition !> numbers not taking their conditioning into !> account (may be larger than RMAX(2)) !>

So RMAX is a DOUBLE PRECISION array, dimension (3), holding the biggest test ratios, broken down like:

• RMAX(1) — the largest residuals from DHST01 or from comparing different calls to DTRSEN 🌈
• RMAX(2) — the largest error in reciprocal condition numbers, taking their conditioning into account ✨
• RMAX(3) — the largest error in reciprocal condition numbers, not taking their conditioning into account — and yes, this one may be larger than RMAX(2), that's literally fine, don't @ me 💀

LMAX

!> LMAX is INTEGER array, dimension (3) !> LMAX(i) is example number where largest test ratio !> RMAX(i) is achieved. Also: !> If DGEHRD returns INFO nonzero on example i, LMAX(1)=i !> If DHSEQR returns INFO nonzero on example i, LMAX(2)=i !> If DTRSEN returns INFO nonzero on example i, LMAX(3)=i !>

INTEGER array, dimension (3). LMAX(i) is the example number where the largest test ratio RMAX(i) got achieved — like a little receipts trail 🧾 Also, plot twist:

• If DGEHRD returns INFO nonzero on example i, then LMAX(1)=i
• If DHSEQR returns INFO nonzero on example i, then LMAX(2)=i
• If DTRSEN returns INFO nonzero on example i, then LMAX(3)=i

Not me keeping track of every single one of these 😭

NINFO

!> NINFO is INTEGER array, dimension (3) !> NINFO(1) = No. of times DGEHRD returned INFO nonzero !> NINFO(2) = No. of times DHSEQR returned INFO nonzero !> NINFO(3) = No. of times DTRSEN returned INFO nonzero !>

INTEGER array, dimension (3) — the group chat of "how many times did this go off the rails" 💀

• NINFO(1) = No. of times DGEHRD returned INFO nonzero
• NINFO(2) = No. of times DHSEQR returned INFO nonzero
• NINFO(3) = No. of times DTRSEN returned INFO nonzero

KNT

!> KNT is INTEGER !> Total number of examples tested. !>

INTEGER. Total number of examples tested — the headcount, the attendance sheet, the whole roster 🫶

NIN

!> NIN is INTEGER !> Input logical unit number. !>

INTEGER. Input logical unit number — that's the file hookup from the Purpose section, she's the main character of "where do the test matrices come from" 🔥

---

👑 Author 👑

• Univ. of Tennessee
• Univ. of California Berkeley
• Univ. of Colorado Denver
• NAG Ltd.

The whole squad fr fr 💜

---

⭐ Definition at line 90 of file dget38.f. ⭐

That's it, that's where she lives. Line 90. Periodt.

---

🌈 Author 🌈

Generated automatically by Doxygen for LAPACK from the source code.

Like, nobody hand-wrote this — Doxygen did it automatically for LAPACK, straight from the source code 🧚 No cap.

---

Heads up bestie: this page is auto-generated documentation, so treat it as a description of the test routine's interface, not as extra promises about behavior beyond what's written here 🙈

---

Okay that's the whole page!! 💖 And for the cute little sign-off: this is LAPACK, Version 3.12.0, dated /home/abui...IG/dget38.f(3) — go off, queen, you ate 🍓✨