From: Greg W. <gr...@sl...> - 2012-02-14 11:38:24
|
Sounds good, care to draft a resolution Michael? Doesn't have to be long, just basically the combination of what we've said. Then we can use that as a reference. Thanks. Also a little thing about the eget example: > > # positional parameters > eget -s archiveRPC QUAD01 2012-02-14T11:12:30 2012-02-14T11:12:40 I think you'd be required to specify the parameters taken by archiveRPC on the command line of the eget tool: eget -s archiveRPC -t0 2012-02-14T11:12:30 -t2 2012-02-14T11:12:40 QUAD01 Another thing: I would very much suggest that in any institution, the name asked for had an indication that it's archive data in it. I know this is kind of unfamiliar to EPICS people, but it's been really useful at SLAC. That is, assuming the name of the PV is QUAD01, the name that the archive service responds to would be, for example, QUAD01:HIST. Another possibility, dare I say it, QUAD01.HIST. Greg On 14 Feb 2012, at 12:21, <mic...@di...> wrote: > From: Greg White [mailto:gr...@sl...] >> OK, so we're standardizing on this form for EPICS V4? >> >> Given by date format +"%Y-%m-%dT:%H:%m:%S" > > Let me suggest one final detail following the time standard. Either you need to be explicit that this date format is UTC and is UTC only, or you need some way to distinguish the time zone. ISO 8061 says that time is either local time or UTC time, and that a trailing Z on the time format can be used to indicate UTC time. > > So I suggest either > > 1. Specify that all date times are in UTC (probably unfriendly) > > or > > 2. Specify that all date times are in local time unless the string ends with Z, in which case the time is in UTC. > > There is also a mechanism for specifying numerical time offsets, but that may be a bit much for the application... > > -- > This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. > Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. > Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. > Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom > > > > |