Stefan Paquay

I would like to take a look because I am interested in it myself but I would have to bother @stanmoore1 a lot with Kokkos-related questions, since porting a complicated...

OK, I will take a look at it. Unfortunately, I am more interested in rigid/small but I'll see what I can do for either. I think rigid/small would be more...

OK, since fix propel/self is pretty much done from a programming point of view I have started with this now.

Will do. For a second I couldn't find the lambdas anywhere but I found them. They look nicer than C++11 lambdas so they were hard to spot. :)

The latest changes with minimize seem to cause linking problems with clang on my laptop, but it might be something dumb on my part. I'll look into it more tomorrow.

Yup, that must have been it. I figured it was something like this but didn't know where to find the CMake files. Thanks! On Wed, Sep 11, 2019 at 10:23...

@stanmoore1 In some places the rigid code calls functions in math_extra that expects arrays of (implicit) size three. I am sure Kokkos provides a way to slice an array (subview...

OK, before I can actually test any of that I stumbled upon another thing: Rigid uses a bunch of additional storage for center-of-mass positions, velocities and forces. It looks like...

fix rigid. EDIT: I plan to port both, but started with rigid. If you think rigid/small will be significantly easier I can also try that one first.

Ah, that is brilliant! So, just to make sure I fundamentally understand this; whenever you do a memoryKK->create_array or memoryKK->grow_array, Kokkos wraps that memory in a dualview so that after...