As it stands, this combination triggers an error. After PR #873 gets merged, this can be triggered in release/1.0.x as of August 9, 2019 by making the following modifications to staggered_eigensolve_test below line 600 or so while running a staggered or asqtaddslash_type test:
These correspond to --test 1 and --test 2 in staggered_invert_test. While I haven't tested it, I imagine this could be triggered in the Wilson-type eigensolve_test as well.
The error is related to expecting a single parity field where a full-parity field is provided.
As it stands, this combination triggers an error. After PR #873 gets merged, this can be triggered in
release/1.0.x
as of August 9, 2019 by making the following modifications tostaggered_eigensolve_test
below line 600 or so while running astaggered
orasqtad
dslash_type
test:matpc_type = QUDA_MATPC_EVEN_EVEN;
(orODD_ODD
)solution_type = QUDA_MAT_SOLUTION;
These correspond to
--test 1
and--test 2
instaggered_invert_test
. While I haven't tested it, I imagine this could be triggered in the Wilson-typeeigensolve_test
as well.The error is related to expecting a single parity field where a full-parity field is provided.