GuoXiong

error like this: xtensor/xexpression.hpp:172:9: internal compiler error: Segmentation fault The same issue "2289" can be solved by upgrading gcc and g++ to 8.4. I wonder if it is possible to...

Because my hardware does not support xsimd acceleration, and xtensor does not support gcc-7, while other programs rely on gcc-7, so I want to know whether the performance will be...

For a 2000*60 array, run following code, it outputs: dot_product_xt: 240000 xtensor dot product took 0.00535805 seconds. dot_product_eigen: 240000 Eigen dot product took 0.000759429 seconds. Code: #include #include #include #include...

The xtensor should be analyzed. I just want to try to replace the xtensor in MPPI with eigen, and I do not know whether the original control frequency can be...

Thanks for your advice and help, I will try to migrate MPPI to Eigen.

Hi~, I have initially migrated MPPI to Eigen in Nav1 and conducted a rough comparison experiment. Specifically, Eigen::Array is used instead of xt::xtensor. Params: model_dt = 0.1, time_step = 32,...

source: https://github.com/guoxxiong/mppi_local_planner Because the tensor used by MPPI is at most two-dimensional, I used Array. Eigen : : Tensor may be faster for high-dimensional tensor calculation, but it is more...

Yes, when I increased the array to 2000 * 56, `Eigen::Array` was much slower than xtensor, xtensor(15 ms) vs Eigen::Array(30 ms).

I wonder if `Eigen::Ref` works, `Eigen::Array` allows the use of references (`Eigen::Ref`) to modify elements in an array without data copying, which is similar to `xt::view` in xtensor.

@SteveMacenski ，I used `Eigen::replicate`, `Eigen::Map`, `Eigen::TensorMap` to improve performance, it can indeed achieve better results in CPU occupancy and speed.