Experimental Physics and
Industrial Control System
| 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: | Re: PyEpics speed |
| From: | Daron Chabot <[email protected]> |
| To: | Jeremy Iken <[email protected]> |
| Cc: | EPICS <[email protected]> |
| Date: | Mon, 24 Jun 2013 12:57:13 -0400 |
On Mon, Jun 24, 2013 at 11:29 AM, Jeremy Iken <[email protected]> wrote:
Hi,
I am using the Python PyEpics3 tool (UChicago), and it seems to take about 0.2 seconds to caget() my PV.
For safety, my system will need the fastest control system.
Why does EPICS take so long? Do all tools take this long? Is this just a Python problem?
As suggested by others, try the command-line tool "caget" first.
FYI, I don't think pyepics has a speed problem.
From an ipython sesson:
In [16]: %timeit -n10 caget('XF:23ID-ES:1{ZP-Ax:TopX}Mtr')
10 loops, best of 3: 339 us per loop
This is fetching a motor record value.
-- dc
- References:
- PyEpics speed Jeremy Iken
- Navigate by Date:
- Prev: Re: PyEpics speed Matt Newville
- Next: Re: Problem in errlogRemoveListener Andrew Johnson
- 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
- Navigate by Thread:
- Prev: Re: PyEpics speed Matt Newville
- Next: cannot start test application Costello, Charles C.
- 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
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·