EPICS Core Telecon 31-Jan-2017

Earlier                                                                                Later


  1. Progress on AIs
  2. Status
  3. Release Process for 3.16.1
    See also this
    3.16 Release Checklist
  4. F2F Meeting in Feb/Mar
  5. AOB


Chair: AJ

Present: AJ, BD, MD, RL, SH, MK, KK

Minutes: AJ

1. Table of AIs




Target Date



Update your headers to contain the header text.





Monitor changes pull request (move Monitor API from pvData to pvAccess; AI from meeting 15-Mar-2016, http://tinyurl.com/zqa3qyp



Test creating a Launchpad project for the bundleCPP module


Created, not good

2. Status

No substantial progress on the AI items.

AJ: Some test work done, but Git on Launchpad does not seem to be a well-integrated solution.

3. Release Process for 3.16.1

See also this 3.16 Release Checklist.


SH: Fundamental problem is that funding for 3.16 development has not appeared yet.

BD: EPICS 7 needs about 6 months of MD’s time, including the gateway, access security etc.

RL: I think the CA-level security is present in V4 already.

MD: A provider currently can’t find out who is connected with it.

BD: Need to make use of what MS has provided.

MK: ESS has to set up a test environment for this, they are the logical site for this testing.

SH: ESS are claiming to still be pure pvAccess site.

BD: We estimate they need twice the funding they are providing. I’m trying to make pva compelling, but we’re not there yet and only ESS and SLAC are showing funding availability.

SH: Could see a Base release that supports both. What’s the minimum release that we’re comfortable calling EPICS 7. Doesn’t need all the services.

AJ: What else does the link support code need?

MD: Another link type implementation that uses it, doesn’t have to be pvAccess.

BD: Rather have something with a warning that the API may change so other implementations need to be aware if it changes.

MD: Want to avoid any nasty regressions in existing link types.

AJ: Write a new CA link type?

MD: Wanted to for a while, performance improvements possible.

SH: See 3.16 as stepping stone for EPICS 7 release.

BD: Maybe with caveats it would be better to make a 3.16 release than not. Need to name a date and go for a release.

SH: Would be helpful to get an ESS rep on this call.

4. F2F Meeting in Feb/Mar

AJ: March 14-16 at APS, could use this for the final 3.16.1 release work if not done before then, AJ + RL + MD at least will be present.

BD: We should now in a couple weeks if we’ll have the technical stuff done.

KK: Don’t need new link types for EPICS 7; having a single release with CA plus PVA and be able to run AreaDetector and an image server in the default IOC. Currently you need to install lots of pieces to get this to work. Having the gateway is also important.

MK: Gateway and Access Security

SH: Need link support ready for the March meeting, but if not ready we should release the functionality we have.


KK: Important that this is released, not experimental. We just agreed to update beamlines to the latest 3.14 release, not even 3.15. For the last V4 training we had 2 different VMs, this isn’t compelling.

AJ: March meeting to put 3.16 to bed and start planning EPICS 7 structure.

KK: June 5 as tentative week for combined F2F meeting?

AJ: Yes. Then October at ITER.

BD: What about the meeting in Japan?

KK: May 15-19.

BD: Was talking to Japanese about training, having MD and Kunal give them. Would Kay be willing to give CS-Studio training?

KK: Yes.

Satellite workshop at ICALEPCS: Nobody in group is currently organizing this.

5. AOB

AJ: Next meeting - 2 weeks?

KK: That’s Valentines day.

BD: I’l be on a beach, lets say 3 weeks.

AJ: Ok, Feb 21st it is.

Meeting adjourned 10:50am.