opal AT lists.psi.ch
Subject: The OPAL Discussion Forum
List archive
- From: Christof Metzger-Kraus <christof.j.kraus AT gmail.com>
- To: Anastasia Ierides <aaierides AT gmail.com>
- Cc: opal <opal AT lists.psi.ch>
- Subject: Re: [Opal] Issues with calling string variable in element definition
- Date: Fri, 5 Jun 2020 06:08:25 +0200
- Authentication-results: localhost; iprev=pass (mail-io1-f46.google.com) smtp.remote-ip=209.85.166.46; spf=pass smtp.mailfrom=gmail.com; dkim=pass header.d=gmail.com header.s=20161025 header.a=rsa-sha256; dmarc=pass header.from=gmail.com
Hi Anastasia,
thank you for reporting this issue. Currently only variables containing numbers can be replaced like this but not strings. I don't remember why I chose it to be like this. I'll fix it.
Christof
On Fri, Jun 5, 2020 at 1:03 AM Anastasia Ierides <aaierides AT gmail.com> wrote:
Hi OPAL team,I am trying to assign a file name to a variable that will be called later into the FMAPFN attribute of an RFCAVITY definition. I have something likeSTRING tempFMAPFN = "filename";Then I all on it asI have also tried using other variations of this format, but the different error messages keep popping up, the most common being that the file with the filename doesn't exist. Is there a correct or different way to do this "file calling"?CAV: RFCAVITY, .... FMAPFN = '${tempFMAPFN}$;Thanks and hope you are all staying safe,Anastasia
- [Opal] Issues with calling string variable in element definition, Anastasia Ierides, 06/05/2020
- Re: [Opal] Issues with calling string variable in element definition, Christof Metzger-Kraus, 06/05/2020
Archive powered by MHonArc 2.6.19.