On Mon, May 13, 2019 at 4:45 PM Alexander Lindsay
wrote:
> I could maybe think of a libmesh-only case, but if you're willing to run
> MOOSE, you can run the
> moose/test/tests/geomsearch/nearest_node_locator/nearest_node_locator.i
> input file. It appears to reproduce the error every time (with
>
I could maybe think of a libmesh-only case, but if you're willing to run
MOOSE, you can run the
moose/test/tests/geomsearch/nearest_node_locator/nearest_node_locator.i
input file. It appears to reproduce the error every time (with
--n-threads=2).
You're probably already aware of this, but for helg
Certainly that is a small mesh and shouldn't be a bottleneck compared to
anything else going on. However, we'd need many more details about your
setup to help diagnose the problem. I'll mention that for questions
regarding performance, you'll want to make sure you're using METHOD=opt
(and linking a
