4 ms·
Yes, exactly: Piz Kesch and Escha. The code is currently also run on Piz Daint on Pascal. Piz Kesch/Escha is pretty special because the system has 16 GPUs per n
by __mp 10y ago
Yes, exactly: Piz Kesch and Escha. The code is currently also run on Piz Daint on Pascal. Piz Kesch/Escha is pretty special because the system has 16 GPUs per node which makes the MPI configuration pretty hairy compared to one GPU systems like daint.
I meant it as a general trend. There's interest from the community to run the GPU model on their system but unfortunately the official COSMO code is not fully GPU ready yet.
- gbrown_ 10y agoCool, thanks for replying. Didn't know you guys were actually running anything on Daint (I'd heard tests were planned). Your earlier comment was the first time I'd heard of the ICON model too. Quite an informative day on HN.
- __mp 10y agoYou're welcome. This is what they presented last year: ftp://ftp-anon.dwd.de/pub/DWD/Forschung_und_Entwicklung/CUS2016_presentations_PDF/06_Dynamics_and_Numerics/01_Invited_Z%E4ngl/ICON_CUS_2016.pdf very nice stuff! (there's a seminar at DWD next week where they probably will give an update). The ICON model is also interesting because they are able to interleave a local area model over Europe with their global model. Well, actually it's actually mostly Jenkins that runs the code for us on Daint. ETH, which I'm also affiliated with, is starting to use the model in GPU mode for climate runs on Daint. What are you working on at Cray?
- gbrown_ 10y ago> What are you working on at Cray? I'm a sysadmin so I get called when things so bump in the night and maintain the running of the systems. I also get to help out with other systems in the EMEA region.
- __mp 10y agoCool, then you are probably the a person who is able to answer this question: What is a good way to mix C++ and Fortran build environments? Is there a way to mix the PrgEnv-{Cray/PGI} so that I can compile C++/CUDA code with GCC 5.x/6.x and the Fortran code in OpenACC mode with PGI/Cray? Right now, we have quite a elaborate build environment where we first load the GCC build environment to compile the C++ code base. Then we load a Fortran build environment to compile the Fortran code base. I would rather have to use one environment to work in. In the most recent Cray and PGI environments (6.0.3) I have to also add the linker path to GCC version I used for C++. This is to avoid linker issues with the C++11 abi in the newer GCC compilers (somehow, the Cray/PGI environment always wants to link with old GCC libraries). Its not a big problem with our build scripts but annoying nevertheless.
- gbrown_ 10y agoNot sure on that sadly, our users don't really mix compilers within a build. With regards to the Cray modules they do go out of their way to avoid you mixing compilers (in terms of setting conflicts in the module files). I'll ask one of our application guys tomorrow to see if there's something I may not be aware of.