[GenABEL-dev] ACML and make check
Frank, Alvaro Jesus
alvaro.frank at rwth-aachen.de
Fri Jul 25 13:00:17 CEST 2014
Hi Lennart,
I committed an ugly/nice hack to allow the usage of AMD's ACML library with omicabelnomm. This was required due to the program having VERY bad performance issues making it unusable on old Opteron systems prior to the 6200 versions. This are all that have non AVX instructions. I might have broken a few Jenkins warnings due to this, but those will be fixed later.
Normal OMICABEL should be tested against ACML this too. Using MKL on the Opteron System, with 10 traits and 400000 snps. the runtime takes over 10 hours. This does not seem like a normal behavior.
AMD ACMl also allows to use GPU without ANY change, the system just needs to support OpenCL, which NVIDIA and AMD do. I have no access to an Opteron/AMD system that has GPU so I cant test it yet.
The changes also allow for static linking now. So no need to have root access. The howtocompile file reflects this now.
I also have a very improtant request. Your change of make check will not display the output of the testing program as it runs. I previosly compiled the test file and manually called it, giving me a very quick workflow to test the system. But now my 1 cmd do it all workflow is broken, having to use make check to compile test.cpp and then having to abort it manually to later re-call it manually to be able to see the output in real time. Is there a way to change make check to allow for real time output? I tried gooooogoling this, but failed with the most common solutions.
A rewrite of Algorithm.cpp is coming next. it will break the validity/give wrong results perhaps at first.
Thank You.
Alvaro Frank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/genabel-devel/attachments/20140725/2476f099/attachment.html>
More information about the genabel-devel
mailing list