gsl | Go wrappers for CBLAS w/o dependencies

Whatever distribution you are trying to use (Cygwin, Mingw, Linux Debian, Fedora..) some programs are NOT installed by default. As not anyone is a C++ programmer, you need to install/add the dedicated packages that contails the tools, compiler, header, libraries you need for your task.

For example Cygwin has almost 10000 packages:
https://cygwin.com/packages/package_list.html

So you need make, g++ and at least the gsl development package.
Use cygcheck -p to find the package that contains the program:

The type of solveOdeC is almost the same as the type for solveOde. The former type involves CDouble at several points, including inside Vectors and Either. The latter instead uses Double.

The code relies on CDouble and Double having the same representation. Because of that, using coerce one can define a function by simply calling the other one with essentially zero overhead. Without that, one would need to create a new Vector which would be bitwise identical to the first one only to satisfy the type checker, spending O(N) for this overhead.

To be honest, I find the definition in the library unnecessarily verbose. One could have written, instead,

I figured out the solution for the issue. First of all, I do not need to install a separate gsl library to use with R. So, I removed the gsl library I installed earlier into C:\R_soft\R\local323. Then I opened the msys2 shell in rtools and ran pacman -S mingw-w64-x86_64-gsl. This installs gsl library to mingw64 folder in rtools (default folder used by rtools to store C++ libraries). See https://packages.msys2.org/package/mingw-w64-x86_64-gsl for more about the gsl package information.

To manually implement an algorithmic differentiation it helps to include explicit intermediary steps

There is a particular section in the inkskape documentation about your question

The major steps:

There are multiple issues with your code:

• You don't check that the inputs are exactly as expected (real, double, non-sparse, etc.)
• You are attaching memory allocated without MATLAB API functions to an mxArray
• You are freeing the memory behind the pointers right after you attach them to the mxArray
• You don't create the plhs[ ] mxArray variables before using them

Normally, when working with mex routines one would do the following in order:

• Check that inputs are exactly as expected
• Create the output plhs[ ] mxArray variables
• Get the pointers to the data areas of the plhs[ ] mxArray variables
• Pass these pointers to the calculation routines

In your case, maybe there is a reason you want to use the gsl_matrix_alloc( ) routine for your memory allocation instead of the MATLAB API memory allocation functions. Fine, but if you do this then you will have to copy the result into the plhs[ ] mxArray data area. You can't attach the pointer directly because that will screw up the MATLAB Memory Manager and lead to a crash downstream. But in all cases you need to create the plhs[ ] mxArray variables first. E.g., if we just go with your current memory allocation scheme you would need to copy the data:

EDIT for gsl data copy

What you need is to look into this similar issue with good explanation how to make it work error in GSL - root finding. To help, you can use https://www.desmos.com/calculator/zuaqvcvpbz to view the function, and you can set initial values like this: double x_lo = 0.0, x_hi = 1.0; in your implementation to make it run; Adding this code will help to find appropriate values for x_lo and x_hi :

auto is just a placeholder for a compiler-deduced type, depending on the context in which auto is used.

In your example, you can't use auto as the return value of my_f_params::inter_auto(), because the compiler has no way to know what type inter_auto() actually returns, so it can't deduce the type of the auto. You would need to do this instead:

You didn't post your full code as a MWE, so I made a new implementation below. Unfortunately, currently the SVD in GSL requires M >= N, so I compute the SVD of the transpose of the matrix, and then output the correct U and V factors from that.