Return-Path: Received: from mx2.fz-rossendorf.de ([149.220.142.12] verified) by hzdr.de (CommuniGate Pro SMTP 6.1.16) with ESMTP id 17386374 for picongpu-users@cg.hzdr.de; Wed, 24 May 2017 10:19:46 +0200 Received: from localhost (localhost [127.0.0.1]) by mx2.fz-rossendorf.de (Postfix) with ESMTP id 1DF6D40092 for ; Wed, 24 May 2017 10:19:46 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mx2.fz-rossendorf.de Authentication-Results: mx2.fz-rossendorf.de (amavisd-new); dkim=pass (2048-bit key) header.d=runbox.com Received: from mx2.fz-rossendorf.de ([127.0.0.1]) by localhost (mx2.fz-rossendorf.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZfknTOLYAD8 for ; Wed, 24 May 2017 10:19:42 +0200 (CEST) Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=91.220.196.211; helo=aibo.runbox.com; envelope-from=berceanu@runbox.com; receiver=picongpu-users@hzdr.de Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) by mx2.fz-rossendorf.de (Postfix) with ESMTPS id 6E76040083 for ; Wed, 24 May 2017 10:19:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=runbox.com; s=rbselector1; h=Message-Id:In-Reply-To:Date:Subject:To:From:MIME-Version: Content-Transfer-Encoding:Content-Type; bh=IzXCdiMizBDPgO77WvP9n0iS9gQ3dboYmt76QT+D3DI=; b=CBPGpRWv6KDjC68DR4dpYJo3MA MDF9Sp2HqFsxOA+GSfgt6nee7IYC/pq4bJOkPl6RTpwXojx7L1EFoTWAZDI59lglCE0sXGl7/Opt2 NWq1UpSsVJAhJ6Od00nYXV6a6CjmypnONX0JBjyCvf9rpJmoLVhLcZchXSwcyoA+eRhcCsOXrk2JI naQJH64OX3NES17SOCquAnQXq35o2c7cAIcOWhUSN1jLmJV+BOLOd0XjNhsd6gvIn2e58v9u7V54n 3e7FqjqM2L94E1wdveYbL84ANp5hY0Zo6FsYAdq/5SZTN0e3TrCGvZS5xrvbcsGY7UsiWRaLylSEM 5rcEp7xg==; Received: from [10.9.9.127] (helo=rmmprod05.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1dDRW9-0006Wy-Dv for picongpu-users@hzdr.de; Wed, 24 May 2017 10:19:41 +0200 Received: from mail by rmmprod05.runbox with local (Exim 4.86_2) (envelope-from ) id 1dDRW9-00010t-Ce for picongpu-users@hzdr.de; Wed, 24 May 2017 10:19:41 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (811097)] by runbox.com with http (RMM6); for ; Wed, 24 May 2017 08:19:41 GMT From: "Andrei Berceanu" To: "picongpu-users" Subject: Re: [PIConGPU-Users] recommended OS for development Date: Wed, 24 May 2017 10:19:41 +0200 (CEST) X-Mailer: RMM6 In-Reply-To: Message-Id: Dear Axel, Thank you for the warm welcome and your detailed reply! While I am quite ne= w to PIC codes, I have done scientific computing in the past and I now work= on laser-matter interaction at ELI-NP [1], where we are currently evaluati= ng the possibility of using PIConGPU instead of EPOCH. In fact, my previous= question about OS/software stack was because I want to install a developme= nt version of PIConGPU on my personal laptop [2] for some benchmarks agains= t EPOCH and for playing around with the code. On a separate note, one of my colleagues managed to install PIConGPU on a c= luster, but he told me all the examples he could find in the docs refer to = the PBS batch system, while the batch system on this particular cluster is = Slurm. Are you aware of any examples of using PIConGPU with Slurm? Thanks, Andrei [1] http://www.eli-np.ro [2] https://www.asus.com/ROG-Republic-Of-Gamers/ROG-GL552JX/specifications/ On Sat, 20 May 2017 17:10:34 +0200, Axel Huebl wrote: > Hi Andrei,=20 >=20 > Welcome to our list! Most of us devel on a Debian derivative, e.g. Debian= testing, latest release of Ubuntu or Mint. Most of our runtime testing we = do in interactive queues on various clusters.=20 >=20 > We don't have a vagrant setup yet but in case you like docker, we have a = nvidia-docker file under: > https://github.com/ComputationalRadiationPhysics/picongpu/issues/829 >=20 > If you are an expert in vagrant, please don't hesitate to share you setup= . I just did not find the time to check how well GPU support works with vag= rant and if people are using it regularly. I know it exists but have not se= en other scientists working with it yet. >=20 > Package wise we usually need a rather recent version of cuda, cmake and b= oost with a working mpi installation, see our install requirements for exac= t versions : > https://picongpu.readthedocs.io/en/dev/install/dependencies.html >=20 > An attractive and brand new alternative is also spack, which has working = build receipts for all our dependencies : > https://github.com/LLNL/spack > https://spack.io >=20 > Are you just generally interested or developing with a specific lab/unive= rsity? If you need any help to get started or have a specific development y= ou are aiming for, feel free to open threads here or issues on github. >=20 > Again, welcome! :)=20 >=20 > Cheers,=20 > Axel