1. CODA run-control JLAB DAQ Group V. Gyurjyan C. Timmer A. Smith New Horizons governor school

2. Run-control history Eiffel C++ Java

3. Run-control design requirements Extendable. Network distributed. Platform independent. Software centric. Flexible. Dynamic hierarchical. Synchronization via message passing. Real-time hardware actions and knowledge processing. Maintainable code replicating the old run-control functionality. Integration with the detector control and legacy software systems.

4. Agent properties Autonomy. Proactive intelligence. Adaptive intelligence. Temporal continuity. Mobility. Rationality/benevolence.

5. Multi - Agent approach Distributes computational resource. Accommodates legacy systems. Peer-to-peer model. Global coordination. High performance.

6. FIPA- Foundation for Intelligent Physical Agents FIPA framework (http://www.fipa.org). FIPA is a specification NOT an implementation. Directory Facilitator (DF). Agent Management System (AMS). Agent Communication Channel (ACC). Java Agent DEvelopment framework (JADE) -FIPA specification JAVA implementation (http://sharon.cselt.it/projects/jade).

7. Run-Control Platform Architecture Communication through message passing. JVM1 JVM2 Message can contain any arbitrary objects. NODE3 HV hardware

8. COOL- Control Oriented Ontology Language Based on RDFS (Resource Definition Framework Schema). Control domain knowledge creation and reuse. Knowledge base sharing. Domain knowledge and operational knowledge separation. Domain knowledge analyses. Extensible via XML-namespaces and RDF modularization.

9. XML or RDF? After all both are text constructs. Duplet vs. triplet to transfer human knowledge. Tag Value XMLRDF ResourcePropertyValueSubjectPredicateObject

10. COOL taxonomy Control Component Process Command Data Node Loop Option Subjects/ObjectsPredicates hasOption hasComponent acceptsComponent hasScrupulosity hasComponentName hasComponentType hasPriority hasProcess Differentiate hasSession hasRunType hasCode hasNode hasFirst hasNext hasInput hasOutput resultNotify acceptData acceptStatus hasCommand hasCheckWith isPartOf hasData hasCommandName hasCommandType hasExpectedOk hasTimeOut hasLoop returnData inputdata hasDataContent hasDataType hasDataCardinality hasTimeStamp hasSemantics hasNodename hasIP isLocal hasUser hasPasswd loopRepete loopDelay stopAt hasDataFile hasDataLimit hasEventLimit hasTokenInterval Splitmb

11. Extending run-control state machine Any control process can be defined as a CODA component. Every component can have associated processes. Each process can be attached to the CODA standard state machine transition by means of isPartOf COOL predicate. COOL process is RDF subclass of the COOL component. Every process has associated COOL command. COOl command can have expectedOk predicate. Control A >> hasProcess >> B Process B >> isPartOf >> download Process B >> hasProcess >> B1 Process B >> hasProcess >> Bn B1 >> expectedOk >> Output String

13. <cool:hasCategory rdf:resource="http://ankaa.jlab.org/~gurjyan/COOL/cool#internal"/> 129.57.167.14 clon10.jlab.org jas.server.HistogramServer /usr/local/clas/jar/jas.jar hep.analyses.Histogram /usr/local/clas/jar/hep.jar JAVA JAS data server description in COOL HistogramServer 1 Histogram fill

14. COOL GUI and knowledge auto-transfer from mSQL to COOL db2cool

15. Run-control GUI

16. Conclusion New run-control is ready to be released. Extended graphing and monitoring capabilities. Backwards compatibility between old and new run configuration files. Agent platform administration and fault tolerance. Integration of the foreign processes through DP, vmeServer and Shell interfaces. Process abstraction has been implemented through the newly developed control oriented ontology language. Future plans Integration of the EPICS processes through the channel access interface. Integration of the CAEN HV control systems through the CAEN OPC server interface. Develop agent supporting JXTA peer to peer specification. Run-control web interface.