-
Notifications
You must be signed in to change notification settings - Fork 579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors compiling Trilinos with TriKota #4771
Comments
I'm just guessing, but could it be that some option enabling complex arithmetic was turned off? I'm a bit surprised since I had thought that Dakota used |
Dakota 6.9 has a dependency on Teuchos complex blas. (Which actually we realized isn't needed and we need to turn off in our next release, as it's only used in some experimental code for now.) I'd guess that you can get around this by something like this (or corresponding -D) in your configure:
|
CORRECTION: It should be possible to set Users are supposed to set |
@briadam wrote:
It looks like Dakota is using some kind of internal Teuchos BLAS macros, instead of using |
Thanks @mhoemmen, I had discovered and then forgotten that. We're doing it wrong in our Dakota configure and I meant to fix it; this is a helpful reminder! |
Sorry I failed to answer that question. Between Dakota and our TPLs, I believe we have a mix of calls to *_F77 macros and use of Teuchos::BLAS<int, Real>. I suspect this is either for historical reasons and/or lack of awareness or completeness of the templated interface at the time. |
@briadam That's OK, I just didn't realize that people were using the macros in Teuchos. I'll keep that in mind if we need to change them. |
@briadam : thanks for the replies. If I turn on complex using
The fix is very easy - just add Unfortunately there is another compilation error later on:
It's interesting that the error only happens when TriKota is on. I guess resolving this is a question for @trilinos/stokhos developers. |
My apologies Irina, I forgot about that JEGA patch; it was added to Dakota's devel and master branches a few months ago and will be in a planned patch release coming in May. In case a helpful data point, for Dakota we often maintain patch files for inbound TPLs and apply them after extracting the last released version of the code. When the inbound TPL integrates the patch we delete them from the process. And yeah, no clue about the Stokhos error... |
I don't think Albany cares about Stokhos, so they should be able to turn that off. Regardless, LinearSolver.hpp used to be where the compressive sensing tools were in Pecos, so I needed them for this code in that file:
I take it Pecos::CompressedSensingTool has moved somewhere else? |
John Jakeman worked on refactoring out the Pecos solvers from the core Pecos orthogonal polynomial capabilities. However, we left the legacy tools around for now in pecos/src/LinearSolverPecosSrc.hpp (to distinguish from the newer, but not necessarily backward compatible pecos/util/src/ solvers). I suspect that just changing that include to LinearSolverPecosSrc.hpp will be easiest for now, but will break for Dakota <6.9, so let me know if we need to finesse this more... |
@etphipp : you're right, I can just turn off Stokhos. We don't use it explicitly in Albany anymore as you say, but I was somehow thinking we need it enabled for AD to work under the hood. Anyway, I was able to compile by turning off Stokhos. @briadam , last question hopefully: did the file TriKota_MPDirectApplicInterface.hpp get renamed? I get a compilation error now when building Albany due to that file not being found:
|
You should be able to remove the include of that file, since that was for the multi-point ensemble propagation, which was also removed from Albany. |
Thanks @etphipp , that fixes the compilation error. I'll go ahead and close the issue. Thanks everyone for your help! |
I am trying to revive our Albany tests that use TriKota, which we have not run for awhile (on the order of a year or two). I am getting the following compilation error when I try to compile it:
I am using dakota 6.9 public release, and this is on a Fedora 29, with gcc-8.3.1. Could someone please help me resolve the issue? It's possible I am not using the right Dakota version, or there is some option I'm missing in my configure script (as I said, I haven't tried to build with Dakota in awhile).
@trilinos/trikota
The text was updated successfully, but these errors were encountered: