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 2019 2020 2021 2022 2023 2024 | 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 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | pyEpics time stamps |
From: | Eric Norum <[email protected]> |
To: | EPICS mailing list <[email protected]> |
Date: | Mon, 12 May 2014 13:48:21 -0700 |
I’m seeing something odd with time stamps in my pyEpics application. Am I doing something wrong or is there a problem with how pyEpics handles time stamps? Step 1 — check local time
Step 2 — confirm that the record time stamps are as expected: enorum@b04lxioc02 214> camonitor SR1:BCM:ADC_WF | sed '/10496.*/s///'
Step 3 — check what pyEpics reports:
Times are two hours off, both UTC and local (we are now 7 hours behind UTC). Here’s the pyEpics script that printed the above — it’s stripped out of a somewhat larger application just to show the problem
|