Roland Axel Richter

I'm using MKL, but I'm not sure if #3042 will help, after all involved CPUs are Intel CPUs, and therefore the necessary parameters should have been set automatically.

@9prady9 Sorry for not answering, but my project focus has shifted a bit, and I was not able to check results, unfortunately. But will update as soon as I get...

Hei, I addressed the other points, but have some comments regarding the main implementation (dvs. your last comment): - The "low" and "high"-part of my return string intend to inform...

Hei, thanks for the feedback! Based on that, would it be a solution to add an additional input parameter to this extraction function, to either return the bin value (default)...

Work on this feature is on hold for the next weeks, but I'll take it up again after my break, if that's ok? Thanks!

Hei, I reverted the feature calculator to being a "simple" calculator as an initial proof of concept. I have not adjusted the testing-functions yet, but will do that as soon...

I solved it by recasting the vector into thrust::device_vector before transferring it to the odeint-function. In my RHS-function I casted it back into thrust::device_vector. I know that that is not...

Yes, more or less like that. Before entering the boost::odeint-function I recasted it into a -vector, and within my right hand side function it was casted back into a thrust::complex-vector....

In the last example (`once`), the following line is missing: `import typing as t`

In the example code in the same example (`once`), given as ```python import time @once(15) def hello(name): return f"Hello, {name}!" for i in range(30): print(i) try: time.sleep(3) print(hello(f"attempt #{i}")) except...