Jed Brown

`make info` will tell you what it found. I just tried with cuda-11.7 and they (Cray?) moved cuda libraries into a different directory. Maybe @jrwrigh has interacted with this recently....

Ah, yeah. `/global/common/software/m1489/cuda/11.5.0/` is a "normal" CUDA installation that hasn't been broken into undocumented nonstandard bits as part of Cray's "value-add". But the above seems to work with the supported...

@tangqi Does the above work for you or is there something we need to fix?

Adding @camierjs, who did most of the initial development. Realistically, this is way off the critical path of @jeremylt's other deliverables (using libCEED, but no longer funded by CEED) so...

I merged from main and kicked off a pipeline. Assuming it's good, I think we can squash-merge.

Thanks, @ArashMehraban. I think my question is a bit different. Compatibility of `examples/solids/` with PETSc versions, and really anything in examples is an entirely separate matter. Feature requests for the...

Yeah, as described here with `maint` and `master` replaced by `release` and `main`. Bug fixes are created from `release` and merged to `release`. Feature branches are created from `main` and...

After a new feature release, `release` fast-forwards to the new release. One can leave an old `release-1.x` branch if someone (like RedHat) needs long-term support for older releases, though it...

PC should be SPD. Are you doing the lumped variant or the "Dirichlet" version (harmonic extension in the balancing)? You can use `PCComputeExplicitOperator` to see if it's symmetric and positive...

You could make the elements macro-elements containing Q1 sub-elements, then compare with our BDDC LFA paper and the corresponding results in PETSc. I don't know if that would take longer...