On 08/24/2018 08:22 AM, pratik@gmail.com wrote:
Thank you. Is there any particular reason that these raw pointers are
not exposed outside ? It would make it much easier for people who would
like to solve using their own solvers on gpu's and hybrid systems much
easier, right ?
But it
Pratik,
Le ven. 24 août 2018 à 10:22, a écrit :
> Thank you. Is there any particular reason that these raw pointers are not
> exposed outside ? It would make it much easier for people who would like to
> solve using their own solvers on gpu's and hybrid systems much easier,
> right ? without
Bruno,
Thank you. Is there any particular reason that these raw pointers are not
exposed outside ? It would make it much easier for people who would like to
solve using their own solvers on gpu's and hybrid systems much easier,
right ? without depending on Trilinos or Petsc ?
Best,
Pratik.
Thank you Wolgang and Jean Paul.
In these days I made some implementation in the line you propose but I am
not happy with it and thus I am asking advices on a different path of
reasoning.
In brief: I'd like to design an algorithm to solve a problem over two
separate domains connected by an
Dear Zhibo,
I guess that this could be fixed in Candi (? ping Uwe, Timo). As of the El
Capitan release (I think), its not possible to use DYLD_LIBRARY_PATH anymore if
SIP (System Integrity Protection) is enabled. For an immediate solution I would
suggest trying to use install_name_tool to add
