1. CODA Users Workshop (Data Acquisition at Jefferson Lab) By David Abbott

2. Welcome - Goals for the Workshop Who are the DAQ Group History What is CODA Introduce CODA 2.5 - new features, tools, and requirements Share what others have done Discuss where we are and where we need to go - in the short term and the long term.

3. Introduction About Us: Six member physics support group - Responsible for providing software and hardware to meet the continually changing data acquisition needs of Jefferson Lab physics… We’re up here

4. Who we are… Me - Team Lead Front-end, Real-time systems, Ed - Custom hardware design Carl - Event Transport, EB, GUI’s Vardan - Java, Intelligent control systems Elliott - Databases, Event I/O, EB Hall B Liaison Dave - Newest member, Hall D Liaison

5. History of CODA Circa 1980s - DAQ systems were closed and custom-built based on the detectors. -------> JLAB has 3 different experimental halls. We didn’t need 3 different DAQ systems. Chip Watson had a better idea… CAMAC MBD VAX

6. CODA History cont… Modular software components use the network for inter-process communication and event transport. Use open standards and minimize the use of commercial software while maximizing use of commercial hardware. DAQ systems for each experimental hall can be “built-up” from common components to fit their needs.

7. CODA Timeline Developed on DEC Ultrix - ported to HP_UX VxWorks front-end, 68K CPUs. RPC-based components Eiffel - RunControl Configure - Flat files Production use in Halls A and C Developed on Solaris - ported to Linux (Red Hat) VxWorks front-end, both 68K and PowerPC CPUs Tcl with Extensions, thread-based components. X/Motif/C++ RunControl Configure - Mini-sql database Used in all three experimental halls Version 1.x (1990-2000)Version 2.x (1996-present)

8. What is CODA?

9. DAQ Components ROCEREB

10. Push Architecture Send big buffers Most efficient use of TCP/IP protocol

11. DAQ Systems EBERROC Simplest System (1 CPU): ADC/TDC BUS file Or get more creative: ROC EB ET file

12. The Database - mSQL msqld Comp Host Port ROC1 tom 1234 EB1 harry 5678 ER1 harry 910 ROC1 Process Table ER1EB1 tom harry Components register in the database Retrieve run configuration information Editing tools: cedit, dbedit Config Table ROC1 myexp.o EB1 ROC1 ER1 myfile.dat

13. Run Control rcServer cdev ROCEREB User Interface State Machine Transition and Monitor multiple components dptcl

14. CODA - Current status Last working release tagged in late 2000 as 2.2.1 Many small changes, additions, and upgrades since then Experimental Halls are working with “different” implementations CODA 3 is under development, but meanwhile we need a stable supportable branch to work with - CODA 2.5

15. CODA 2.5 Two years in the making - incorporate bug fixes, new features, new hardware. Close to a million lines of code to maintain Support updated operating systems and compilers (e.g. Solaris 8, Red Hat 9, Enterprise, vxWorks 5.5) Drop old support (e.g. 68K CPUs, Red Hat 6, Solaris 2.6, DD System etc…) A launching point for introducing CODA version 3 software

16. CODA 2.5 -New Stuff OS Support Solaris 8 Sun 6.2 compiler RedHat 7.x, 9.x, Enterprisegcc 2.96, 3.2 VxWorks 5.4, 5.5gcc 2.96+ (ppc) Redhat 7, 9 will be phased out 68K CPUs (MV162,MV167) will be dropped Dependencies on external packages CMLOG 2.1xpm 4.10 cdev 1.7.5expat.195 Java 1.4+openmotif 2.1

17. CODA 2.5 - New cont… DAQ: bug fixes, ROC-->ET support ET: java, vxWorks, tcl_et ROL: GEN lists, new headers to support new hardware RunControl: New Java-based system Utilities: XML evio, vxServer, codamaster, fbdiag, Database proxy server, etc… Hardware: New libraries for support of VME modules (ADCs, TDCs, scalers, etc…) New TS, interface cards VME, SFI DMA libraries F1 TDC

18. Front-End Support VxWorks - real-time OS With 5.5 - new compiler, more UNIX APIs (e.g. pthreads) Most efficient, convenient hardware access Larger CPU memorys (512MB) supported FASTBUS is headed out Repair costs prohibitive No commercial support VME and PCI are in VME64X - Necessary for F1 TDC PCI interface to CAMAC for small systems

19. Aging Technologies RunControl (runcontrol, rcServer) Poor maintainability Difficult to extend to other control apps Other X11/Motif Apps - xcefdmp, cedit Tcl 7.4 /Tk 4.0 and extensions itcl/itk, tclStruct, dp, blt, tclcdev, tcl_cmlog, tcl_msql, Tix4.0.4, debug, svipc Mini-SQL Database Component nameservice Config and Status

20. Summary CODA has evolved into a successful and stable DAQ toolkit used both at the Lab and in other institutions (e.g. MIT-Bates, TUNL, RHIC). Today’s workshop is an opportunity to learn and share what can be done. CD-0 for the 12 GeV upgrade brings new DAQ challenges - high rates, fully dead-timeless systems. Goals: Keep everything we like. Adapt to new technologies. Introduce what you need and want.