Fernando Pereira
Fernando Pereira
We define the following utility functions, which have proven to be live savers :) ```c++ template inline py::array_t as_pyarray(Sequence&& seq) { // Move entire object to heap (Ensure is moveable!)....
> With such fix, the compiler will warn you if you calls with without std::move @arquolo If you call without std::move, it will bind as an L-value reference and then...
The function is called `as_array` and the "docs" say it will move, so I think it's fine, but you choose. It's standard to use `std::forward` in case you want to...
I think I understood the issue with neurodamus-py. Indeed we didn't have a `setup_transfer` before `stdinit` when dumping gid info. However, and this is a bit worrying, if we do...
The run results (reports) are different. I also haven't looked deeply, I am just raising awareness and asking for initial thoughts.
Anyway, that shouldn't hit us in neurodamus since we changed it to have a single set of calls to `setup_transfer -> stdinit`. However, it seems `setup_transfer -> stdinit` -> dump...
I don't really understand why the CI could fail in GPU. @pramodk Ideas?
@ramcdougal @Helveg I tried fixing it by checking the places where we could corrupt memory, but unfortunately the problem is still there. There were a couple of places it seemed...
I wonder if a review from @nrnhines would reveal the hiding bug
@ramcdougal @Helveg We are thinking about reviving this for the next Hackathon. IIRC we were not far from feature complete, except for the CI crash. I can start by rebasing...