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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: benchtop testbeds for EPICS development and testing? |
From: | Kevin Peterson <[email protected]> |
To: | "Shen, Guobao" <[email protected]>, Gedare Bloom <[email protected]> |
Cc: | Talk EPICS Tech <[email protected]> |
Date: | Fri, 11 May 2018 14:45:04 -0500 |
https://github.com/kmpeters/VirtualMotorControllerThis has a few advantages over the simulated motors included in the motor module:
* the python script can be killed to simulate a controller failure * the code can be easily modified to simulate bad behavior in the future Kevin On 05/11/2018 11:51 AM, Shen, Guobao wrote:
Hi Gedare, The EPICS Core development and application development are different, although they are related of course. It seems that as the first step, you want to focus on the application side, therefore some soft IOC and simulators like areaDetector simulator would be a good start. You can definitely use simDetector to test your network performance, which gives you a reasonable frame per second depending on your server. Another advantage of simDetector is that it supports both CA and PVA, therefore you can test both CA and PVA performance. For the IO testing, unless you want to use some real hardware, you can use simulators which could give you same responses like your hardware. It is fairly easy to develop one if you are using asyn for your hardware IOC. We have some preliminary hardware simulators at APS for our ASYN based IOCs. Of course, virtual accelerator is also one of nice tool for your evaluation. Thanks, Guobao