Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
<== Date ==> <== Thread ==>

Subject: Re: OPIs from command line - Re: Tech-talk Digest, Vol 13, Issue 309
From: Tong Zhang via Tech-talk <tech-talk@aps.anl.gov>
To: Tyler Lemon <tlemon@jlab.org>
Cc: mailingEPICS l <tech-talk@aps.anl.gov>
Date: Wed, 24 Jul 2019 17:34:03 -0400
Hi Tyler,

Thanks for your reply, passing fullpath of opi file does work only for the simplest case, i.e. cs-studio --launcher.openFile /home/tong/.cs-studio/CSS/test1.opi,
but I still got segfault when I tried to add more options, e.g. cs-studio --launcher.openFile "/home/tong/.cs-studio/CSS/test1.opi Position=Detached".

Tong

On Tue, Jul 23, 2019 at 11:21 AM Tyler Lemon <tlemon@jlab.org> wrote:
Hi Tong,

I saw your message regarding how to open OPIs from the command line.

I've found that the --launcher.openFile option needs to have the full system path to the OPI for it to work.

I've also found that it works a little better if you also set the workspace with a command line option.

For example, if your OPI "test1.opi" is in a directory called "screens" in the workspace at "/home/CSS-Workspaces/test/" the command would be:

css -data /home/CSS-Workspace/test --launcher.openFile /home/CSS-Workspace/test/screens/test1.opi

Hope this helps!

Best regards,
Tyler

From: tech-talk-bounces@aps.anl.gov <tech-talk-bounces@aps.anl.gov> on behalf of tech-talk-request@aps.anl.gov <tech-talk-request@aps.anl.gov>
Sent: Tuesday, July 23, 2019 11:09 AM
To: tech-talk@aps.anl.gov
Subject: Tech-talk Digest, Vol 13, Issue 309
 
Send Tech-talk mailing list submissions to
        tech-talk@aps.anl.gov

To subscribe or unsubscribe via the World Wide Web, visit
        https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.aps.anl.gov_mailman_listinfo_tech-2Dtalk&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=us-o9gwDx2Pk0eVrGqn2HwSxYkqOceqAcuatb6EPaeg&e=
or, via email, send a message with subject or body 'help' to
        tech-talk-request@aps.anl.gov

You can reach the person managing the list at
        tech-talk-owner@aps.anl.gov

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tech-talk digest..."


Today's Topics:

   1. RE:Compress Record with input from partial Waveform (GAGET Alexis)
   2. Re: Channel Access and channel name weirdness (Michael Westfall)
   3. Start OPIs from command line interface (Tong Zhang)
   4. EPICS Base labels and series descriptions at epics.anl.gov
      (J. Lewis Muir)
   5. EPICS Base labels at epics-controls.org (J. Lewis Muir)
   6. EPICS vs. EPICS Base (J. Lewis Muir)
   7. Re: EPICS Base labels and series descriptions at
      epics.anl.gov (Johnson, Andrew N.)
   8. EPICS Base bin/<arch>/ca{get,info,monitor,put}.pl scripts
      (J. Lewis Muir)
   9. Starting XY Graph with tools enabled by default? (Tyler Lemon)


----------------------------------------------------------------------

Message: 1
Date: Mon, 22 Jul 2019 17:14:55 +0000
From: GAGET Alexis <alexis.gaget@cea.fr>
To: Bruno Martins <brunoseivam@gmail.com>, tech-talk
        <tech-talk@aps.anl.gov>
Subject: RE:Compress Record with input from partial Waveform
Message-ID:
        <7972A7C4CF81B349B0530B2BAF0FA7D51043E77C@E-EXDAGE-A1.extra.cea.fr" target="_blank">7972A7C4CF81B349B0530B2BAF0FA7D51043E77C@E-EXDAGE-A1.extra.cea.fr>
Content-Type: text/plain; charset="iso-8859-1"

Hi Bruno
I would have tried to play on the Input instead, trying to replace the waveform by a subArray or adding it between the compress and the waveform. The subArray NELM can be modified online so you can maybe defined it with the "fix amount per run" (if you know it)

Something like that :
record(waveform, "WVF") {
    field(FTVL, "DOUBLE")
    field(NELM, "50")
}
record (calcout, "plouf"){
    field(INPA, "MyFixAmout CPP")
    field(VAL, "A")
    field(OUT, "SubA.NELM PP")
}

record(subArray, "SubA") {
    field(INP, "WVF CPP")
    field(FTVL, "DOUBLE")
    field(NELM, "5")
    field(MALM, "100")
}

record(compress, "CMP") {
    field(ALG,  "Circular Buffer")
    field(INP,  "SubA CP")
    field(NSAM, "100")
}

Not sure that's work, it's by memory, so consider it as a lead

Cheers
Alexis

________________________________
De : tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] de la part de Bruno Martins via Tech-talk [tech-talk@aps.anl.gov]
Envoy? : vendredi 19 juillet 2019 23:43
? : tech-talk
Objet : Compress Record with input from partial Waveform

Hi folks,

Is there a way to force compress to take only NORD elements from its INP waveform? I have a big waveform that only has some of its data initialized (a fixed amount per "run"), and I want to accumulate this initialized data in a circular buffer. Has anyone made something similar work? Do I need to interpose an acalcout between the two (which I tried but didn't seem to work)?

Please see example below.

Thanks!

Bruno

$ cat test.db
record(waveform, "WVF") {
    field(FTVL, "DOUBLE")
    field(NELM, "50")
}

record(compress, "CMP") {
    field(ALG,  "Circular Buffer")
    field(INP,  "WVF CP")
    field(NSAM, "100")
}

$ softIoc -d test.db
...

$ caget CMP.NUSE  # returns 50, I expected 0 (no PINI set)...
CMP.NUSE                       50

$ caput CMP.RES 1  # let's reset compress
Old : CMP.RES                        0
New : CMP.RES                        0

$ caget CMP.NUSE
CMP.NUSE                       0

$ caput -a WVF 5 1 2 3 4 5
Old : WVF 50 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
New : WVF 50 1 2 3 4 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

$ caget WVF.NORD
WVF.NORD                       5

$ caget CMP.NUSE   # I expected 5
CMP.NUSE                       50

$ caget CMP
CMP 100 1 2 3 4 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

$ caput -a WVF 5 6 7 8 9 10
Old : WVF 50 1 2 3 4 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
New : WVF 50 6 7 8 9 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

$ caget WVF.NORD
WVF.NORD                       5

$ caget CMP.NUSE  # I expected 10
CMP.NUSE                       100

$ caget CMP # I expected 1,2,3,4,5,6,7,8,9.10
CMP 100 1 2 3 4 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 7 8 9 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman.aps.anl.gov_pipermail_tech-2Dtalk_attachments_20190722_45a86348_attachment.html&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=L3r5yNBXkGP35Qyms6jJWElyBxrziLwd8zRCZyfvWkA&e= >

------------------------------

Message: 2
Date: Mon, 22 Jul 2019 14:27:03 -0400
From: Michael Westfall <mwestfal@gemini.edu>
To: "Johnson, Andrew N." <anj@anl.gov>
Cc: "tech-talk@aps.anl.gov Talk" <tech-talk@aps.anl.gov>
Subject: Re: Channel Access and channel name weirdness
Message-ID:
        <CAJMnkYrX73MAPPRX1+ydNpk+_-QFy2md7Gx4MnS_a1530hou7Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi Andrew,

I've filtered for packets coming from a specific IP address, so I know
which IOC is sending it.

I hadn't considered the possibility that the problem is in a sequencer
program. A quick check of the relevant  sequencer programs shows that these
channels are referenced there as well as in the main database file. So... I
will do some further investigation...

On Fri, Jul 19, 2019 at 5:38 PM Johnson, Andrew N. <anj@anl.gov> wrote:

> Hi Mike,  How do you know what client is requesting those names? My guess
> is it may be a sequence program (or maybe a PV named in an access security
> file) running on the same IOC which hasn't been given the right prefix.
>
> The 'dbcar' command lists the IOC's dbCa links, and can confirm or deny
> that it's a database link (use dbcar "*", 0/1/2 to see increasing amounts
> of info). You'll need to use the sequencer commands seqShow and seqChanShow
> to check for unconnected channels for your sequence programs, I forget what
> the arguments are to seqChanShow but I think you give it a program name and
> "-" to see only disconnected channels. There is also a similar 'ascar
> <level>' command for reporting CA connections if you're using access
> security.
>
> HTH,
>
> - Andrew
>
> --
> Complexity comes for free, Simplicity you have to work for.
>
>

--
Mike Westfall
Control Systems Software Engineer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman.aps.anl.gov_pipermail_tech-2Dtalk_attachments_20190722_a6ba6cca_attachment.html&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=8W2qPx8FdEH2EoIn50EUwvxnFFmiei8_rQYT1qYxoYA&e= >

------------------------------

Message: 3
Date: Mon, 22 Jul 2019 15:37:48 -0400
From: Tong Zhang <warriorlance@gmail.com>
To: "'tech-talk@aps.anl.gov'" <tech-talk@aps.anl.gov>
Subject: Start OPIs from command line interface
Message-ID: <6a86967c-a79a-2287-aa09-815f0ba2b3a3@gmail.com" target="_blank">6a86967c-a79a-2287-aa09-815f0ba2b3a3@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed

Hello,

I'm trying to start up CS-Studio BOY opi from CLI, this is what I did:

cs-studio --launcher.openFile test1.opi

But ended up with 'Segmentation fault', I'm following the links:
https://urldefense.proofpoint.com/v2/url?u=http-3A__cs-2Dstudio.sourceforge.net_docbook_ch29.html&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=FWN9zO0kfzIp3nJTcmv_LAl8u8bye767j89EeuwI8xw&e=  and
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ControlSystemStudio_cs-2Dstudio_issues_2204&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=o_D72BItjMnEv58iR5GFWkTy3Eph-A50vXS4ZM1Xze4&e=

without --launcher.openFile option it works. Thanks for any help.

Tong


------------------------------

Message: 4
Date: Mon, 22 Jul 2019 14:40:31 -0500
From: "J. Lewis Muir" <jlmuir@imca-cat.org>
To: EPICS Tech-Talk <tech-talk@aps.anl.gov>
Subject: EPICS Base labels and series descriptions at epics.anl.gov
Message-ID: <20190722194031.qdkui4spfmfiocc5@mink.imca.aps.anl.gov" target="_blank">20190722194031.qdkui4spfmfiocc5@mink.imca.aps.anl.gov>
Content-Type: text/plain; charset=utf-8

Hello!

At the EPICS Base page

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=CZ0RfXytPxxpoA9TULC6glckqTkHqBYZw66rXLB8Hr0&e=

there's an EPICS Base series list:

  * EPICS 7.0 (2017-present) ? current release series
  * Release 3.16 (2016-2018) ? closed
  * Release 3.15 (2014-present) ? stable release series
  * Release 3.14 (2002-2018) ? closed
  * Release 3.13 (1996-2003) ? closed, deep-frozen
  * Release 3.12 (1995) ? closed, historic
  * Release 3.11 (1991-1994) ? closed, fossilized

Why is the EPICS Base 7.0 series labeled "EPICS 7.0" when the others
are labeled "Release 3.x"?  It seems to me that it should be labeled
"Release 7.0".

Similarly, on the 7.0 page

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R7-2D0_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=ZbkLxxrCFTlbWvWLkwqpQgD9HxpKZ3WgYlY8W7cfqdU&e=

it lists point releases:

  * EPICS 7.0.1 (Initial release)
  * EPICS 7.0.2 (Bug fixes and new features)

Those should be labeled "Release 7.0.x", not "EPICS 7.0.x".

Also, they're in chronological order, but reverse chronological order
would be better because most people will be interested in the latest
point release and because reverse chronological order is what's used on
all the other series pages:

* https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D16_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=n7jslgqKXdmBSyGKGpSvXDhpdreMCYR5n7jOaHG1WA4&e=
* https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D15_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=r_2xk2ZGeLHivkpouvEA3Uu0-71SPDC6ax-qNGr0jjQ&e=
* https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D14_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=QKW4o6T2uvYQ91P6ENTIt2vqEbzt4OZnYZpYn7fTw7E&e=
* https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D13.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=9s_vujnhbZaMNiqeTiJGKTHhuZgjGztvrs3iCPhdREg&e=
* https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D12.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=31CA1G7ZpFSk60-LsOn2dYR_qNYAzEDn2VRV6Vmix_w&e=
* https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D11.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=2DJWw_JTDKfK-OuAsxz8n_cCAXYhX1lwTM1P1gaalKo&e=

Back to the series labeling at the EPICS Base page

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=CZ0RfXytPxxpoA9TULC6glckqTkHqBYZw66rXLB8Hr0&e=

in the EPICS Base series list

  * EPICS 7.0 (2017-present) ? current release series
  * Release 3.16 (2016-2018) ? closed
  * Release 3.15 (2014-present) ? stable release series
  * Release 3.14 (2002-2018) ? closed
  * Release 3.13 (1996-2003) ? closed, deep-frozen
  * Release 3.12 (1995) ? closed, historic
  * Release 3.11 (1991-1994) ? closed, fossilized

it says the 3.16 series is closed, but if I follow the "Release 3.16"
link to

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D16_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=n7jslgqKXdmBSyGKGpSvXDhpdreMCYR5n7jOaHG1WA4&e=

it says:

  This is the "Current" release series.

I think that needs to be updated to say that it's closed.

And lastly, again at the EPICS Base page

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=CZ0RfXytPxxpoA9TULC6glckqTkHqBYZw66rXLB8Hr0&e=

in the EPICS Base series list

  * EPICS 7.0 (2017-present) ? current release series
  * Release 3.16 (2016-2018) ? closed
  * Release 3.15 (2014-present) ? stable release series
  * Release 3.14 (2002-2018) ? closed
  * Release 3.13 (1996-2003) ? closed, deep-frozen
  * Release 3.12 (1995) ? closed, historic
  * Release 3.11 (1991-1994) ? closed, fossilized

it describes "EPICS 7.0" as the "current release series", but if I
follow the "EPICS 7.0" link to

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R7-2D0_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=ZbkLxxrCFTlbWvWLkwqpQgD9HxpKZ3WgYlY8W7cfqdU&e=

it says:

  This is the development release series of EPICS.

I think it's confusing to call it the "current release series" on the
EPICS Base page, but the "development release series" on the 7.0 release
series page.  It seems to me that they should match: call it either the
"current release series" or the "development release series", but not
both.

Thanks!

Lewis


------------------------------

Message: 5
Date: Mon, 22 Jul 2019 15:18:37 -0500
From: "J. Lewis Muir" <jlmuir@imca-cat.org>
To: EPICS Tech-Talk <tech-talk@aps.anl.gov>
Subject: EPICS Base labels at epics-controls.org
Message-ID: <20190722201837.vkmsztqal22bpdpf@mink.imca.aps.anl.gov" target="_blank">20190722201837.vkmsztqal22bpdpf@mink.imca.aps.anl.gov>
Content-Type: text/plain; charset=us-ascii

Hello!

(
  I just reported similar things for epics.anl.gov in

    https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_tech-2Dtalk_2019_msg01219.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=_fPW79HzUpZR_WviIh1MH-m6vljAESrB3Z2vKaQ08CQ&e=
)

At the EPICS Base page

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics-2Dcontrols.org_resources-2Dand-2Dsupport_base_&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=rV0gcIMo7FFjFHvyTiuUHltFSaJsjAySGvXEJ4xZzTw&e=

I don't understand the naming.  It seems inconsistent to me.

In the Download section, why is the EPICS Base 7.0.2 release labeled
"EPICS 7.0.2" when the EPICS Base 3.15.6 release is labeled "Base
3.15.6"?  They should be consistent: e.g., "Base 7.0.2" and "Base
3.15.6" (or "Release 7.0.2" and "Release 3.15.6").

In the Versions section, I see "EPICS Release x": the versions are
labeled "EPICS", but in other places they're labeled "EPICS Base".
Which one is it?

And in the Development Statistics section, there's:

  * EPICS 7
  * Base-3.16
  * Base-3.15
  * Base-3.14
  * Base-3.13

I think consistent naming would help improve clarity.

Thanks!

Lewis


------------------------------

Message: 6
Date: Mon, 22 Jul 2019 16:01:50 -0500
From: "J. Lewis Muir" <jlmuir@imca-cat.org>
To: EPICS Tech-Talk <tech-talk@aps.anl.gov>
Subject: EPICS vs. EPICS Base
Message-ID: <20190722210150.5qlnhm6lw4e4kf53@mink.imca.aps.anl.gov" target="_blank">20190722210150.5qlnhm6lw4e4kf53@mink.imca.aps.anl.gov>
Content-Type: text/plain; charset=us-ascii

Hello!

It seems to me that the terms "EPICS" and "EPICS Base" are often used
interchangeably, yet they're not the same thing.  Are the following
definitions correct?

  EPICS: A specification of control system definitions and protocols.

  EPICS Base: A C/C++ implementation of the EPICS specification.

If correct, then I'm OK with keeping the name EPICS Base, but I wonder
if a better name might be EPICS-C++?  Then, if desired, you could
have other implementations of the EPICS specification: EPICS-Java,
EPICS-Perl, EPICS-Python, EPICS-Ruby, etc.

Thoughts?

Lewis


------------------------------

Message: 7
Date: Mon, 22 Jul 2019 22:23:14 +0000
From: "Johnson, Andrew N." <anj@anl.gov>
To: "J. Lewis Muir" <jlmuir@imca-cat.org>, EPICS Tech-Talk
        <tech-talk@aps.anl.gov>
Subject: Re: EPICS Base labels and series descriptions at
        epics.anl.gov
Message-ID: <26c5c2d1-c410-e152-10b9-4f1cb1f5a55c@anl.gov" target="_blank">26c5c2d1-c410-e152-10b9-4f1cb1f5a55c@anl.gov>
Content-Type: text/plain; charset="utf-8"

Hi Lewis,

Some of these differences are deliberate, some may be because I missed something when updating the site...

On 7/22/19 2:40 PM, J. Lewis Muir via Tech-talk wrote:

At the EPICS Base page

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=CZ0RfXytPxxpoA9TULC6glckqTkHqBYZw66rXLB8Hr0&e=

there's an EPICS Base series list:

  * EPICS 7.0 (2017-present) ? current release series
  * Release 3.16 (2016-2018) ? closed
  * Release 3.15 (2014-present) ? stable release series
  * Release 3.14 (2002-2018) ? closed
  * Release 3.13 (1996-2003) ? closed, deep-frozen
  * Release 3.12 (1995) ? closed, historic
  * Release 3.11 (1991-1994) ? closed, fossilized

Why is the EPICS Base 7.0 series labeled "EPICS 7.0" when the others
are labeled "Release 3.x"?  It seems to me that it should be labeled
"Release 7.0".


Because the community decided (at the SNS collaboration meeting IIRC) they wanted to call the result of merging Base 3.x with the V4 (now PVA) modules "EPICS 7" [and if you insert an R or V in there you lose the ability to pronounce it "epics heaven"]. Those of us with OCD tendencies (or CDO to be alphabetically pedantic) just have to get used to the change.


Similarly, on the 7.0 page

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R7-2D0_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=ZbkLxxrCFTlbWvWLkwqpQgD9HxpKZ3WgYlY8W7cfqdU&e=

it lists point releases:

  * EPICS 7.0.1 (Initial release)
  * EPICS 7.0.2 (Bug fixes and new features)

Those should be labeled "Release 7.0.x", not "EPICS 7.0.x".


The header on that page says "EPICS 7.0 Release Series", just to mix things up even further...


Also, they're in chronological order, but reverse chronological order
would be better because most people will be interested in the latest
point release and because reverse chronological order is what's used on
all the other series pages:

* https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D16_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=n7jslgqKXdmBSyGKGpSvXDhpdreMCYR5n7jOaHG1WA4&e=
* https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D15_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=r_2xk2ZGeLHivkpouvEA3Uu0-71SPDC6ax-qNGr0jjQ&e=
* https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D14_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=QKW4o6T2uvYQ91P6ENTIt2vqEbzt4OZnYZpYn7fTw7E&e=
* https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D13.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=9s_vujnhbZaMNiqeTiJGKTHhuZgjGztvrs3iCPhdREg&e=
* https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D12.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=31CA1G7ZpFSk60-LsOn2dYR_qNYAzEDn2VRV6Vmix_w&e=
* https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D11.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=2DJWw_JTDKfK-OuAsxz8n_cCAXYhX1lwTM1P1gaalKo&e=


Ack, I have swapped the list items for the 7.0.1 and 7.0.2 point release pages.


Back to the series labeling at the EPICS Base page

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=CZ0RfXytPxxpoA9TULC6glckqTkHqBYZw66rXLB8Hr0&e=

in the EPICS Base series list

  * EPICS 7.0 (2017-present) ? current release series
  * Release 3.16 (2016-2018) ? closed
  * Release 3.15 (2014-present) ? stable release series
  * Release 3.14 (2002-2018) ? closed
  * Release 3.13 (1996-2003) ? closed, deep-frozen
  * Release 3.12 (1995) ? closed, historic
  * Release 3.11 (1991-1994) ? closed, fossilized

it says the 3.16 series is closed, but if I follow the "Release 3.16"
link to

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R3-2D16_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=n7jslgqKXdmBSyGKGpSvXDhpdreMCYR5n7jOaHG1WA4&e=

it says:

  This is the "Current" release series.

I think that needs to be updated to say that it's closed.


Thanks, done.


And lastly, again at the EPICS Base page

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=CZ0RfXytPxxpoA9TULC6glckqTkHqBYZw66rXLB8Hr0&e=

in the EPICS Base series list

  * EPICS 7.0 (2017-present) ? current release series
  * Release 3.16 (2016-2018) ? closed
  * Release 3.15 (2014-present) ? stable release series
  * Release 3.14 (2002-2018) ? closed
  * Release 3.13 (1996-2003) ? closed, deep-frozen
  * Release 3.12 (1995) ? closed, historic
  * Release 3.11 (1991-1994) ? closed, fossilized

it describes "EPICS 7.0" as the "current release series", but if I
follow the "EPICS 7.0" link to

  https://urldefense.proofpoint.com/v2/url?u=https-3A__epics.anl.gov_base_R7-2D0_index.php&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=ZbkLxxrCFTlbWvWLkwqpQgD9HxpKZ3WgYlY8W7cfqdU&e=

it says:

  This is the development release series of EPICS.

I think it's confusing to call it the "current release series" on the
EPICS Base page, but the "development release series" on the 7.0 release
series page.  It seems to me that they should match: call it either the
"current release series" or the "development release series", but not
both.


Agreed. 7.0 started out as a developer branch, but when we closed the 3.16 branch and 7.0 became the current branch I missed updating that term on the 7.0 series page. Now fixed.

Some don't like the term "developer" release, and to be honest "current" doesn't have an obviously clear meaning. We currently use "stable" for the 3.15 series, and I think that's reasonable since we limit the changes on that branch to mostly bug-fixes and build system changes. I'm wondering whether "active" might be a better term for the 7.0 series, but I would be happy to hear other people's opinions on that.

- Andrew


--
Complexity comes for free, Simplicity you have to work for.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman.aps.anl.gov_pipermail_tech-2Dtalk_attachments_20190722_33255fd6_attachment.html&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=FELr3MaqJ3Z3JBaZpF0bxSWjNXLXcOHwH85kYasc0dA&e= >

------------------------------

Message: 8
Date: Mon, 22 Jul 2019 20:57:40 -0500
From: "J. Lewis Muir" <jlmuir@imca-cat.org>
To: EPICS Tech-Talk <tech-talk@aps.anl.gov>
Subject: EPICS Base bin/<arch>/ca{get,info,monitor,put}.pl scripts
Message-ID: <20190723015740.ijj3356bz5dy2gaj@mink.imca.aps.anl.gov" target="_blank">20190723015740.ijj3356bz5dy2gaj@mink.imca.aps.anl.gov>
Content-Type: text/plain; charset=us-ascii

Hello!

Why are there the following Perl scripts with the same names as
binaries, but with a .pl extension, in the EPICS Base 3.15.6 installed
bin/<arch> directory?

  caget.pl
  cainfo.pl
  camonitor.pl
  caput.pl

Are the .pl scripts workalikes to the binaries?  If so, what benefit
do they provide?  If no benefit, then I think they should be removed
in a future release series (e.g., EPICS Base 7.0, assuming it's still
OK to introduce breaking changes in that release series since it's a
development series without a production release).

Thanks!

Lewis


------------------------------

Message: 9
Date: Tue, 23 Jul 2019 15:09:23 +0000
From: Tyler Lemon <tlemon@jlab.org>
To: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Subject: Starting XY Graph with tools enabled by default?
Message-ID:
        <BY5PR09MB3972ECC8630759CE051CBB16BAC70@BY5PR09MB3972.namprd09.prod.outlook.com" target="_blank">BY5PR09MB3972ECC8630759CE051CBB16BAC70@BY5PR09MB3972.namprd09.prod.outlook.com>
       
Content-Type: text/plain; charset="iso-8859-1"

Hello,

We are trying to configure an OPI with an XY Graph to by default, have the tools "show axis trace" and "show value label" from the toolbar enabled. Currently, our users have to manually enable these options on the toolbar whenever the OPI is opened.

Is there a way the XY Chart can be configured to make it so the "show axis trace" and "show value label" tools are enabled by default?

Any help or advise would be appreciated.

Best regards,
Tyler Lemon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman.aps.anl.gov_pipermail_tech-2Dtalk_attachments_20190723_78aa3c7f_attachment.html&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=uUMvytRbVq5LKueEdb-q3pY58tcYwRXp0bF4WxtWtRI&e= >

------------------------------

_______________________________________________
Tech-talk mailing list Tech-talk@aps.anl.gov
https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.aps.anl.gov_mailman_listinfo_tech-2Dtalk&d=DwICAg&c=CJqEzB1piLOyyvZjb8YUQw&r=xJvfz8d-IPB1CokOM-U5MA&m=i0fFyY7r0kqZyK9iyKEWKdr9VG12aJgA6sfsT0kqm2c&s=us-o9gwDx2Pk0eVrGqn2HwSxYkqOceqAcuatb6EPaeg&e=


End of Tech-talk Digest, Vol 13, Issue 309
******************************************

Navigate by Date:
Prev: Re: EPICS 3.15 mlockall()/dbThreadRealtimeLock high memory usage Michael Davidsaver via Tech-talk
Next: epics base compilation for ARM Cotex-A53 (ARM64bit) Ha, Kiman via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
Navigate by Thread:
Prev: Re: EPICS 3.15 mlockall()/dbThreadRealtimeLock high memory usage Michael Davidsaver via Tech-talk
Next: epics base compilation for ARM Cotex-A53 (ARM64bit) Ha, Kiman via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
ANJ, 25 Jul 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·