PCTRTRI(l)
PCTRTRI π β the LAPACK baddie that inverts your triangular distributed matrix
okay bestie, gather round, because we're talking about a real one from LAPACK routine (version 1.5) β the PCTRTRI era. this is the parallel-girlie cousin of the classic triangular inverse, and she is serving linear algebra on a process grid. π«Ά
β¨ NAME β¨
PCTRTRI β compute the inverse of a upper or lower triangular distributed matrix sub( A ) = A(IA:IA+N-1,JA:JA+N-1)
like yes, that's the whole job. she inverts. she distributes. she slays. π
π¦ SYNOPSIS π¦
SUBROUTINE PCTRTRI( UPLO, DIAG, N, A, IA, JA, DESCA, INFO )
CHARACTER DIAG, UPLO
INTEGER IA, INFO, JA, N
INTEGER DESCA( * )
COMPLEX A( * )
look at her. seven-ish little inputs, one big job. iconic behaviour, no notes. π
πΈ PURPOSE πΈ
PCTRTRI computes the inverse of a upper or lower triangular distributed matrix sub( A ) = A(IA:IA+N-1,JA:JA+N-1).
that's it, that's the mission statement. inverse. triangular. distributed. periodt. π
Notes
bestie, before you touch anything here, you need to understand the descriptor vector situation, because this is the part where people get humbled. π
Each global data object is described by an associated description vector. This vector stores the information required to establish the mapping between an object element and its corresponding process and memory location.
Let A be a generic term for any 2D block cyclicly distributed array. Such a global array has an associated description vector DESCA. In the following comments, the character _ should be read as "of the global array".
so like, the cheat sheet of what lives where:
DTYPE_A(global) β stored inDESCA( DTYPE_ )β the descriptor type. In this case,DTYPE_A = 1.CTXT_A(global) β stored inDESCA( CTXT_ )β the BLACS context handle, indicating the BLACS process gridAis distributed over. The context itself is global, but the handle (the integer value) may vary.M_A(global) β stored inDESCA( M_ )β the number of rows in the global arrayA.N_A(global) β stored inDESCA( N_ )β the number of columns in the global arrayA.MB_A(global) β stored inDESCA( MB_ )β the blocking factor used to distribute the rows of the array.NB_A(global) β stored inDESCA( NB_ )β the blocking factor used to distribute the columns of the array.RSRC_A(global) β stored inDESCA( RSRC_ )β the process row over which the first row of the arrayAis distributed.CSRC_A(global) β stored inDESCA( CSRC_ )β the process column over which the first column of the arrayAis distributed.LLD_A(local) β stored inDESCA( LLD_ )β the leading dimension of the local array.LLD_A >= MAX(1,LOCr(M_A)).
okay and now the grid math, because this is the part that's giving main character energy but also giving pop quiz. π§
Let K be the number of rows or columns of a distributed matrix, and assume that its process grid has dimension p x q.
LOCr( K ) denotes the number of elements of K that a process would receive if K were distributed over the p processes of its process column.
Similarly, LOCc( K ) denotes the number of elements of K that a process would receive if K were distributed over the q processes of its process row.
The values of LOCr() and LOCc() may be determined via a call to the ScaLAPACK tool function, NUMROC:
LOCr( M ) = NUMROC( M, MB_A, MYROW, RSRC_A, NPROW ),
LOCc( N ) = NUMROC( N, NB_A, MYCOL, CSRC_A, NPCOL ).
An upper bound for these quantities may be computed by:
LOCr( M ) <= ceil( ceil(M/MB_A)/NPROW )*MB_A
LOCc( N ) <= ceil( ceil(N/NB_A)/NPCOL )*NB_A
memorise it or cry about it, those are the options. π
π ARGUMENTS π
UPLOβ (global input)CHARACTER. Specifies whether the distributed matrixsub( A )is upper or lower triangular:= 'U': Upper triangular,= 'L': Lower triangular.
DIAGβ (global input)CHARACTER. Specifies whether or not the distributed matrixsub( A )is unit triangular:= 'N': Non-unit triangular,= 'U': Unit triangular.
Nβ (global input)INTEGER. The number of rows and columns to be operated on, i.e. the order of the distributed submatrixsub( A ).N >= 0.Aβ (local input/local output)COMPLEXpointer into the local memory to an array of dimension(LLD_A,LOCc(JA+N-1)). On entry, this array contains the local pieces of the triangular matrixsub( A ). IfUPLO = 'U', the leading N-by-N upper triangular part of the matrixsub( A )contains the upper triangular matrix to be inverted, and the strictly lower triangular part ofsub( A )is not referenced. IfUPLO = 'L', the leading N-by-N lower triangular part of the matrixsub( A )contains the lower triangular matrix, and the strictly upper triangular part ofsub( A )is not referenced. On exit, the (triangular) inverse of the original matrix.IAβ (global input)INTEGER. The row index in the global arrayAindicating the first row ofsub( A ).JAβ (global input)INTEGER. The column index in the global arrayAindicating the first column ofsub( A ).DESCAβ (global and local input)INTEGERarray of dimensionDLEN_. The array descriptor for the distributed matrixA.INFOβ (global output)INTEGER.= 0: successful exit< 0: If the i-th argument is an array and the j-entry had an illegal value, thenINFO = -(i*100+j), if the i-th argument is a scalar and had an illegal value, thenINFO = -i.> 0: IfINFO = K,A(IA+K-1,JA+K-1)is exactly zero. The triangular matrixsub( A )is singular and its inverse can not be computed.
π¨ ok so real talk: that last one is the villain arc. ifINFOcomes back> 0, your triangular matrixsub( A )is singular and its inverse can not be computed. there is no clever workaround hiding in this manpage. she said no. π
that's the whole page, bestie. go forth, invert responsibly, and may your process grid always be p x q in your favour. π
sign-off: this was brought to you by LAPACK version 1.5, dated 12 May 1997 β vintage, but the drip is timeless. βπΈπ
π¦ where this page comes from
- ubuntu jammy: scalapack-doc 1.5-11
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms