EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: [Bug 1935037] Re: Invalid charactor in field name
From: mdavidsaver via Core-talk <core-talk at aps.anl.gov>
To: core-talk at aps.anl.gov
Date: Fri, 27 Aug 2021 19:58:49 -0000
Personally, no.  I've tested with ~10, not hundreds, of group fields.

I don't know of any reason why it won't "work" in the strictest sense of
not crashing, and eventually yielding consistent data.  My curiosity is
about performance.  There is a strong application specific component
here as groups tie in with locking is done with database records (aka.
dbScanLock() ).

When a group is read out, on GET or when a monitor update is triggered,
QSRV will lock *all* of the individual records in *sequence*.  This
means waiting for any record processing to complete, and preventing
subsequent processing.  So inclusion in a group couples scan times of
the constituent records with each other, and with QSRV.

The worst case time to read out a group is the sum of the worst case
processing times of the constituent records in isolation.  Further,
because the constituents are no longer in isolation, this also becomes
the worst case scan time of each record.  Each might have to wait for
all the others, and QSRV.

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1935037

Title:
  Invalid charactor in field name

Status in EPICS Base:
  New

Bug description:
  When creating a group in QSRV, the allowed characters are too
  restrictive

  error:
  Error Group not created: Invalid charactor '-' (45) in field name "BI02-TimeRise" must be A-Z, a-z, 0-9, or '_'

  expected behaviour:
  pva structures should allow for a more liberal set of characters that just what is covered by \w regex metacharacter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1935037/+subscriptions


References:
[Bug 1935037] [NEW] Invalid charactor in field name Niko Kivel via Core-talk

Navigate by Date:
Prev: Re: [Bug 1935037] Re: Invalid charactor in field name Niko Kivel via Core-talk
Next: [Bug 1941875] Re: Buggy warning message "Record/Alias name '...' should not contain non-printable ... mdavidsaver via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
Navigate by Thread:
Prev: [Bug 1935037] Re: Invalid charactor in field name Dirk Zimoch via Core-talk
Next: [Bug 1777768] Re: NPP Put to a pp(TRUE) VAL field doesn't trigger monitors Andrew Johnson via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
ANJ, 29 Aug 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·