1. Epics Archiving at DESY Albert Kagarmanov (IHEP Protvino Russia) Matthias Clausen (DESY Hamburg Germany)

2. Contents DESY Epics Archiving overview  History  Using Channel Archiver experience Current Work around Archiving  AAPI as Abstract Archive Data Interface  2D waveform plot in Channel Archiver Web-Interface BESSY 2002, EPICS Workshop, Albert Kagarmanov “Epics Archiving at DESY”

3. DESY Epics Archiving overview History  A lot of different Control Systems at DESY  TINE for Hera, DOOCS for TTF, EPICS for Kryo  From 96 to 99 we are used used home-made Archive Monitor:  Filename Structure- yyyy/mm/recordName –1 file per month per record  Contents– simple binary array of time/value/status  Now this data convert to SDDS-format.  GUI- IDL tool from Research Systems,Inc (http://www.rsinc.com) -see following picture:http://www.rsinc.com BESSY 2002, EPICS Workshop, Albert Kagarmanov “Epics Archiving at DESY”

4. Typical IDL screens: BESSY 2002, EPICS Workshop, Albert Kagarmanov “Epics Archiving at DESY”

5. DESY Epics Archiving overview Using Channel Archiver Experience  We are using Channel Archiver during last 2,5 years.  Currently we are storing about 3000 channels.  It’s working good. We had some troubles with writing data to NFS-disk.  GUI for Archive Data:  Standard CGI-interface from Channel Archiver  IDL  Strip(History)Tool  JoiMint through DIXI-server for XML-data BESSY 2002, EPICS Workshop, Albert Kagarmanov “Epics Archiving at DESY”

6. Current Work around Archiving AAPI as Abstract Archive Data Interface  For extract data from different Archive Source (EPICS,DOOCS,TINE,SDDS) we are using additional program interface layer : Archive API - AAPI  AAPI can answer for few questions about abstract archive data:  getData [and ControlInfo]  getChannelInfo  getChannelList  AAPI is independent TCP/IP server  AAPI_server –port 3999 & BESSY 2002, EPICS Workshop, Albert Kagarmanov “Epics Archiving at DESY”

7. Current Work around Archiving AAPI as Abstract Archive Data Interface  Name convention: by prefix:  EPICS|channelName (Epics is default)  DOOCS|channelName  TINE|channelName  (plan?) OLD_EPICS|channelName ( For old archive data)  AAPI is more convenient for adding new Data Source:  Do not need recompile existing GUI application  Do not need even restart it. (See next picture: ) BESSY 2002, EPICS Workshop, Albert Kagarmanov “Epics Archiving at DESY”

8. AAPI as Abstract Archive Data Interface Blue lines – not implemented yet. BESSY 2002, EPICS Workshop, Albert Kagarmanov “Epics Archiving at DESY” EPICS World Other Control System Perl/OtherCGI-interface StripHistory Tool IDLJoiMintOther GUI DIXI / XML ArchiveAPI -interface HERA TINE TTF DOOCS Epics Data Other/Old Epics Data Channel ArchiverSDDS

9. 2D waveform plot in Channel Archiver Web-Interface 2D waveform plot in Channel Archiver Web-Interface :  Existing 3-D waveform picture is very complicate for understanding.  For improving this situation we are added small modification to existing CGI-Web part of Channel Archiver.  We are added additional button “2D-Plot” and textEntry “wf number”, which allow 2d-plot this waveform as 2D-picture: BESSY 2002, EPICS Workshop, Albert Kagarmanov “Epics Archiving at DESY”

10. 2D waveform plot in Channel Archiver Web-Interface BESSY 2002, EPICS Workshop, Albert Kagarmanov “Epics Archiving at DESY”

11. 2D waveform plot in Channel Archiver Web-Interface 2D picture for time = 05/05/2002 00:38:17, Number =3. Link: http://www-kryo.desy.de/documents/2dPlot.html BESSY 2002, EPICS Workshop, Albert Kagarmanov “Epics Archiving at DESY”