Guillaume Fraux
Guillaume Fraux
What's the exact command you used to install librascal?
8405cbdc0b5c72a5f0b0c93593100dde348bb95f fixed some of the errors when cross-compiling on CI. You should be able to git pull and install again, but make sure to wipe your `build` and `_skbuild` folders...
The error comes from `-Werror=array-bounds`, so I would guess it is a question of the compiler which got better at this warning. The simplest fix would be to remove `-Werror`...
The mirror solution would be to have a copy of the deps at `github.com/librascal/` and download from there.
`fy.chalmers.se` is down again, #412 fixes the build by mirroring wigxjpf to github (https://github.com/lab-cosmo/wigxjpf) & downloading from there.
`lrascal` is not easy to pronounce, but I'll be fine with the other two. Although we have been using `librascal` in the group to refer to this code, it feels...
I also think we should change the python module name to match the name on pypi, i.e. `from librascal import XXX` instead of `from rascal import XXX`. While this is...
Before making a release, I think we should re-license to LGPL-v2 or later (https://github.com/cosmo-epfl/librascal/issues/303). I can take care of this if everyone is fine with it.
The API could look like this ```cpp #include #include namespace rascal { /// Possible logging levels enum class LogLevel { Debug, Info, Warn, Error }; /// Send a single log...
Can we automatically do `ostream_redirect` for all calls to C++ functions, or does the user need to manually specify it for every function call?