Open bradbell opened 1 year ago
Hi, I've not tested it in a separate build directory - the instructions say to type ./configure and make in the top-level directory.
Hi, I've not tested it in a separate build directory - the instructions say to type ./configure and make in the top-level directory.
OK that works.
Is there a proper way to create a debug / release version of the libraries ?
Most of the Adept library is in headers, so if you want to debug your own code that use the library, you don't need to recompile the Adept library - you just should compile your code with the -DADEPT_BOUNDS_CHECKING -DADEPT_INIT_SNAN -DADEPT_TRACK_NON_FINITE_GRADIENTS flags (although I normally don't bother with the last one).
See the other options at section 5.6.1 at http://www.met.reading.ac.uk/clouds/adept/adept_documentation_2.1.pdf
I was able to implement a general adapet gradient and thereby include adept in my new AD comparison package; see https://cmpad.readthedocs.io/en/latest/adept_gradient.hpp.html
The idea behind this comparison package is that it should be easy to add packages and easy to build and test for just one package; i.e., it is only necessary to get the packages one is interested in.
The result for some small example cases can be seen in src/main.csv: https://cmpad.readthedocs.io/en/latest/xam_main.py.html#src-xam-main-csv
The cases above are small. You can run larger cases (on your system) using the program https://cmpad.readthedocs.io/en/latest/main.html
Thanks.
Steps to reproduce:
Result:
Configure Warning: configure: WARNING: cannot determine how to obtain linking information from f77
System: