Return-Path: Received: from mx2.fz-rossendorf.de ([149.220.142.12] verified) by hzdr.de (CommuniGate Pro SMTP 6.1.10) with ESMTP id 13493161 for picongpu-users@cg.hzdr.de; Tue, 14 Jun 2016 11:31:21 +0200 Received: from localhost (localhost [127.0.0.1]) by mx2.fz-rossendorf.de (Postfix) with ESMTP id DD63F4574A for ; Tue, 14 Jun 2016 11:31:21 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mx2.fz-rossendorf.de 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 7OkeLY7x84od for ; Tue, 14 Jun 2016 11:31:17 +0200 (CEST) Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=147.231.234.10; helo=mailgw.eli-beams.eu; envelope-from=prvs=19734be673=danila.khikhlukha@eli-beams.eu; receiver=picongpu-users@hzdr.de Received: from mailgw.eli-beams.eu (mailgw.eli-beams.eu [147.231.234.10]) by mx2.fz-rossendorf.de (Postfix) with ESMTPS id 3CD0A45742 for ; Tue, 14 Jun 2016 11:31:15 +0200 (CEST) Received: from braun.eli-beams.eu ([10.1.5.17]) by mailgw.eli-beams.eu with ESMTP id u5E9VEEP007799-u5E9VEER007799 (version=TLSv1.0 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 14 Jun 2016 11:31:14 +0200 Received: from BRAUN.eli-beams.eu ([::1]) by braun.eli-beams.eu ([::1]) with mapi id 14.03.0279.002; Tue, 14 Jun 2016 11:31:14 +0200 From: Khikhlukha Danila To: "picongpu-users@hzdr.de" Subject: Field initializers Thread-Topic: Field initializers Thread-Index: AdHGGtxe7IG32dM1RnmNuM3hHPFKfQ== Date: Tue, 14 Jun 2016 09:31:14 +0000 Message-ID: Accept-Language: en-US, cs-CZ Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.36.30.5] Content-Type: multipart/alternative; boundary="_000_BA7C853FEE430847B9C35FFCC6E5B2A52675E4C8braunelibeamseu_" MIME-Version: 1.0 --_000_BA7C853FEE430847B9C35FFCC6E5B2A52675E4C8braunelibeamseu_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear all, I'm trying to tweak the gasProfile structure a bit. In fact I want to speci= fy a custom 1D gas distribution. So currently I'm trying to initialize an array inside a gasProfile declarat= ion code: struct GasProfile { .... const float_64 test[10] =3D {0,1,2,3,4,5,6,7,8,9}; DINLINE float_64 operator()( floatD_64 pos ) {.... The code above gives an error during the compilation .../simulation_defines/param/gasConfig.param(213): warning: field initializ= ers are a C++11 feature .../simulation_defines/param/gasConfig.param(213): warning: field initializ= ers are a C++11 feature .../simulation_defines/param/gasConfig.param(200) (col. 37): error: Interna= l Compiler Error (codegen): "function-scope static variables cannot be init= ialized!" So my questions are: 1. If there is a way how to switch on the c++11 support for a compilation? = (w.r.t. https://github.com/ComputationalRadiationPhysics/picongpu/issues/11= 47) 2. If there is a less dirty way how to plug in a custom gas profile? The cu= stom HDF5 file is mentioned in the code, however I didn't find the way how = to use... BTW, is it thread safe to read a gas profile from the file? Thank you in advance, Danila. --_000_BA7C853FEE430847B9C35FFCC6E5B2A52675E4C8braunelibeamseu_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Dear all,
I'm trying to tweak the gasProfile structure a bit. In fact I want to speci= fy a custom 1D gas distribution.
So currently I'm trying to initialize an array inside a gasProfile declarat= ion code:
            struct G= asProfile           =             &nb= sp;            =             &nb= sp;            =             &nb= sp;            =
            { &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;

            &nb= sp;   ....          =             &nb= sp;            =             &nb= sp;            =             &nb= sp;            =             &nb= sp;
            &nb= sp;   const float_64 test[10] =3D {0,1,2,3,4,5,6,7,8,9}; &nb= sp;            =             &nb= sp;            =             &nb= sp;
            &nb= sp;   DINLINE float_64 operator()( floatD_64 pos )
               = {....

The code above gives an error during the compilation
.../simulation_defines/param/gasConfig.param(213): warning: field initializ= ers are a C++11 feature
.../simulation_defines/param/gasConfig.param(213): warning: field initializ= ers are a C++11 feature
.../simulation_defines/param/gasConfig.param(200) (col. 37): error: Interna= l Compiler Error (codegen): "function-scope static variables cannot be= initialized!"

So my questions are:
1. If there is a way how to switch on the c++11 support for a compi= lation? (w.r.t. https://github.com/ComputationalRadiationPhysics/picongpu/i= ssues/1147)

2. If there is a less dirty way how to plug in a custom gas profile? The cu= stom HDF5 file is mentioned in the code, however I didn't find the way how = to use... BTW, is it thread safe to read a gas profile from the file?

Thank you in advance,
Danila.

--_000_BA7C853FEE430847B9C35FFCC6E5B2A52675E4C8braunelibeamseu_--