scalapack: query lwork from ppocon #5915
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
i was trying to fix
scalapack_05
on some testers https://cdash.kyomu.43-1.org/testSummary.php?project=1&name=scalapack%2Fscalapack_05.mpirun%3D4.debug&date=2018-02-15and was digging into the code.
Looks like
lwork
is wrong, IBM states this as:and netlib-scalapack as
in our case
IA=JA=1
so things are simpler, but still there were nomax
and alike inTo be on the safe side we can query the right number from
ppocon
.p.s. this does not fix the
float
test for me, it still hangs on MPI=4 run with a32x32
matrix with block-size32
(process grid will consist of one core only here).double
works just fine, so doesfloat
with 1 MPI core...