Summing up our Zoom discussion: The ts post filter should be able to
allocate a new db_field_log and convert the timestamp from the
pLog->time field into a new value of whatever type/format was requested
by the filter args.
My preference would be that ts:{fmt="%Y-%m-%d %H:%M:%S.%09f"} would
return a DBF_STRING (although Michael isn't keen on accepting format
strings from the network for security reasons; we can discuss that),
while say ts:{epoch:1970} would return a double giving the number of
seconds since 1970-01-01 00:00:00 UTC (that being the Posix epoch, while
for 1990 it would use the EPICS epoch).
--
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/1182091
Title:
Make TIME field directly accessible
Status in EPICS Base:
Triaged
Bug description:
Users often request the ability to access the TIME field directly.
It could be provided as an array of 2 32-bit values, possibly with a specific string in ISO-8601 form say.
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1182091/+subscriptions
- Navigate by Date:
- Prev:
[Bug 1905159] Re: Fix warnings from recent compiler versions Andrew Johnson via Core-talk
- Next:
Re: ANN: RTEMS libnetworking relocation Vijay Kumar Banerjee via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
- Navigate by Thread:
- Prev:
[Bug 1182091] Re: Make TIME field directly accessible Jure Varlec via Core-talk
- Next:
[Bug 1182091] Re: Make TIME field directly accessible Ben Franksen via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
|