EPICS Controls Argonne National Laboratory

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  <20142015  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  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Some CSS BOY questions
From: "Kasemir, Kay" <[email protected]>
To: "Arnold, Ned D." <[email protected]>
Cc: John Gordon <[email protected]>, "[email protected]" <[email protected]>
Date: Tue, 18 Feb 2014 09:00:16 -0500
Hi:

Ned is pointing in the right direction.
Your testing is just one case of automation.
CSS/BOY should be the user interface, not the automation.
You should be able to stop the user interface, while the automation continues.
You should be able to open multiple user interfaces, without each new GUI also starting another test run.

Python now has interfaces to both CA clients and servers.
That would allow you do write a python tool which runs the test, with PVs to start/stop/monitor the test.
CSS can then be used to talk to those PVs.

Thanks,
Kay


On Feb 18, 2014, at 8:54 AM, "Arnold, Ned D." <[email protected]<mailto:[email protected]>> wrote:

Hi John -

Your "critical tasks for the product testing application" sound like data analysis ... so I would use a tool/language more amenable for that purpose, such as Matlab (or it's open source cousin octave) or python.  All these options have channel access libraries so you could integrate the analysis part with your CSS BOY screens .e.g. CSS BOY could initiate the analysis and display the results.

HTH -

    Ned


________________________________
From: [email protected]<mailto:[email protected]> [[email protected]<mailto:[email protected]>] on behalf of John Gordon [[email protected]<mailto:[email protected]>]
Sent: Monday, February 17, 2014 5:35 PM
To: [email protected]<mailto:[email protected]>
Subject: Some CSS BOY questions

Hi

We are thinking of using CSS and BOY to develop product test screens for our products.  We have already developed some demo end-user screens with BOY, which work nicely, and were quick to do and get working.  However these just set and read PVs that are handled by Channel Access Server at the typical refresh rates, which are fine for a GUI.  I want to know how easy it is to do some of the critical tasks for the product testing application.  These include:

-          Recover blocks of contiguous data that have been collected at high rate and buffered in the device
-          Do calculations based on those data blocks (eg noise analysis, peak fitting, zero subtraction etc etc)
-          Post the raw data and the computed results to file
-          Compare computed results with acceptance criteria read from files to get pass/fail
-          Put computed results, pass/fail indications and other text onto the GUI

Regards

John Gordon
Pyramid Technical Consultants, Inc.




References:
Some CSS BOY questions John Gordon
RE: Some CSS BOY questions Arnold, Ned D.

Navigate by Date:
Prev: RE: Some CSS BOY questions Arnold, Ned D.
Next: RE: Some CSS BOY questions Dalesio, Leo
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Some CSS BOY questions Arnold, Ned D.
Next: RE: Some CSS BOY questions Dalesio, Leo
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 17 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·