Timothy Smith

> This builds on crusher for a CPU only build. I'm ready to merge. Any objections? I still would not like to add bulk unnecessarily (see my review comments above),...

Seems like #15 is effectively equivalent to the second and third boxes above (unit tests and testing scripts over a range of hardware/compilers)? We have been cleaning up our unit...

@jeffmiles63 I was going to point you to Trilinos but I see we haven't gotten the latest updates there yet. I will submit another snapshot PR by tonight unless @alanw0...

@jeffmiles63 check out `packages/stk/stk_unit_tests/stk_simd` in Trilinos/develop. There's a couple things that might need to be tweaked or extended to test the whole range of functionality (our new unit tests are...

I think we do need everything on this list in order to replace stk_simd. In addition to the math functions you listed above, stk_simd also provides `atan2`, `asinh`, `acosh`, `atanh`,...

@wyphan I'm actually not on the project anymore, so I don't have the latest info on exactly how that patch should apply. @psakievich can you take a look?

I would vote against the FHS. I have struggled a lot with both spack and exawind-builder precisely because they use this layout, and it requires some mental mapping to know...

We had a discussion on the STK team about the best path forward and we think it's best for STK to shift from using GTest as a package to using...

@alanw0 off the top of my head, I think if we and nalu-wind both use `find_package(gtest)`, and if the exawind stack includes gtest built as a TPL available to both,...

Hi @Chengyue810, we recommend using the master branch of nalu-wind (it looks like your spack may have picked up an old version). Also, make sure you are using `[email protected]`, if...