Experimental Physics and Industrial Control System
We have funding and are interested in collaborating with EPICs developers
to build a web services interface to EPICS and use web services workflow
(e.g Keppler) to enable a "labview" like flexibility for interconnecting
devices.
Similar work is underway at UoIndianna. Please see following for more
detail
http://www.canarie.ca/conferences/advnet2004/ppt/mcmullen.ppt
For a general overview of our work on web services for process control
please see
http://www.canarie.ca/conferences/advnet2004/program.html
Bill
---------
[email protected]
+1.613.944.5603
> -----Original Message-----
> From: Ned Arnold [mailto:[email protected]]
> Sent: Tuesday, January 04, 2005 5:48 PM
> To: '[email protected]'
> Cc: John Carwardine
> Subject: A New Year, A New Start
>
> Happy New Year -
>
> At December's EPICS Collaboration Meeting in Tokai, Japan (co-organized
> by JAERI-Tokai and KEK), there was extensive discussion on how to build
> some momentum into the the on-going evolution, development and support
> of EPICS. Although all such development will continue to be a
> collaborative effort, it was concluded that to best make use of widely
> distributed resources from different institutions, some coordination,
> planning, and tracking of efforts is desperately needed.
>
> Here is "a plan" that was proposed:
>
> - Group the activities into the following categories:
> > EPICS Core (iocCore, Channel Access, SNL)
> > Core Tools/Extensions (fundamental tools and popular extensions)
> > Collaboration Support (training, documentation, information, etc)
> > R&D for EPICS 5.0++ and beyond (EPICS 2010 follow through)
>
> - For each category, identify a "category lead" - i.e. the
> person(s) responsible for making something happen in that
> category. [it was acknowledged that no one knows what
> authoritative body exists to approve these "leads", so we just made
> them up :) ]
>
> - These category leads have not been given much direction (other
> than this e-mail), so it will be up to them to initiate whatever
> activity they deem appropriate. Some reasonable expectations
> would include ...
>
> > Identify interested people who are committed to contributing
> both ideas and effort in this category
>
> > Identify immediate needs, work being done, future plans
> and ideas for that category by soliciting input from
> the EPICS community (i.e. develop a plan)
>
> > Maintain web page(s) that clearly identify current efforts,
> planned efforts, and needed resources (i.e. publicize the plan)
>
> > Match available resources to needed tasks and track progress
>
> > Ensure that plans, implementations, etc are sufficiently
> distributed/exposed for comments and all effort is done
> in a "collaborative" mode (i.e. beta releases, appropriate
> reviews, etc)
>
> > Report at every EPICS Collaboration Meeting on the activities
> in this category and receive honest feedback from the
> community
>
> This plan in no way inhibits one's opportunity to contribute to the
> collaboration. In fact, it provides the benefit of identifying a
> contact
> person with whom to discuss your ideas/efforts!
>
> The discussions at Tokai identified the following "Category Leads":
>
> > EPICS Core - Bob Dalesio
> > Core Tools/Extensions - Matthias Clausen
> > Collaboration Support - Ned Arnold/John Maclean
> > R&D for EPICS 5.0++ and beyond - Steve Hunt
>
> The EPICS Core category has already gained some momentum. Bob presented
> a new Road Map that includes plans for EPICS Release 3.15, Channel
> Access 4.0 Definition/Development, and EPICS Release 4.0. See the last
> lecture listed at http://www-linac.kek.jp/epicsasia2004 (The second to
> last presentation conveys similar information as this e-mail).
>
> As web-sites for each category are made available, a link will be
> provided from the EPICS Home Page.
>
> We welcome your <helpful> comments. General comments may be submitted
> to
> tech-talk. Specific comments and/or suggestions for a particular
> category should go to the "category lead".
>
>
> Ned
>
- References:
- A New Year, A New Start Ned Arnold
- Navigate by Date:
- Prev:
RE: Problem building 3.14.7 on win32-x86 Jeff Hill
- Next:
Re: sysAtReboot 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:
A New Year, A New Start Ned Arnold
- Next:
Problem building 3.14.7 on win32-x86 Mark Rivers
- 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