scientific-computing

Describe your issue.

I have enclosed a minimum reproducible example with data and I am trying to use two methods in the scipy optimize package - https://docs.scipy.org/doc/scipy/reference/optimize.html

One is minimize_scalar and the other is Brent's method. But both the outputs have large differences. Can anybody explain why ?

Also I get a runtime error while running Brent-

test.p

See:
gonum/gonum#845 (comment)

What is the desired addition or change?

provide a cmake c++17 switch

What is the motivation for this feature?

to not depend on the std_backport

If applicable, describe how this feature would be implemented.

change those lines from 11 to 17 conditional to a global define

https://github.com/mlpack/mlpack/blob/de94eee6881e33f1145d9d4a8b5380a5be8af36a/CMakeLists.txt#L

Current implementation of join can be improved by performing the operation in a single call to the backend kernel instead of multiple calls.

This is a fairly easy kernel and may be a good issue for someone getting to know CUDA/ArrayFire internals. Ping me if you want additional info.

Currently spack does not support the following packages, all of these packages are installed outside of Spack at Cori, we would like to get support for these packages if possible.

• cpmd https://www.lcrc.anl.gov/for-users/software/available-software/cpmd/
• ComputeCPP https://github.com/codeplaysoftware/computecpp-sdk need to confirm link
• ds9 https://sites.google.com/cfa.harvard.

Add #[track_caller] to some panicking methods. Slicing methods seem the most prudent (Index/Mut does not apply, sorry).

Needs benchmarks to investigate impact, preferably holistic benchmarks.

In terms of functionality, the mid-term end goal is to achieve an offering of ML algorithms and pre-processing routines comparable to what is currently available in Python's scikit-learn.

These algorithms can either be:

• re-implemented in Rust;
• re-exported from an existing Rust crate, if available on crates.io with a compatible interface.

CDash has builds with C++17 enabled, but they are not triggered when github builds opened PR's.

It would be great to have at least one build (gcc or clang) in github wih C++17.

https://llvm.org/docs/NewPassManager.html

The tricky part is to keep our custom command line options working.

using the approach laid out in:
dswah/pyGAM#154