Luke Shulenburger
Luke Shulenburger
If we pursue either of these, we need to be very careful of the trade-offs associated with moving to this model of programming. New programmers coming to the code are...
Ray has some notes in https://github.com/rcclay/miniqmc/wiki . The C style structs do cause a problem for kokkos (although one that can be solved very easily). I would be in favor...
Something that I would be interested in exploring is the role / scope of refactoring in the miniapp. A lot of the challenges we face concern what happens when our...
I've got no problem with that. What would you think about creating something like a population class to hold walkers?
I like the second one. It may also make sense to eventually move some of the generic methods to here rather than having to rely on generic_walker->waveFunction.method(blah....)
In response to your question, I like having this sort of object because by passing it to a method to work on the population you can defer how it should...
Not opposed to that idea. It could be a good point of convergence.
Are you building Kokkos inline? You should change the KOKKOS_ARCH to HSW in your cmake.
Problem looks to be that you are using nvcc_wrapper to build the code with KOKKOS_ENABLE_CUDA=false. Try building again with gcc directly.
Perfect. I need to update the CMakeLists.txt, The only executable you can build at the moment is miniqmc_sync_move_noref .