Channel Archiver
The Channel Archiver is one of the archiving toolsets for EPICS.There are two mayor versions available:
- 2.x is for EPICS base R3.14.x.
These releases are new with ongoing maintainance. - 1.x is for EPICS base R3.13.x.
These releases have been in use for a while, but there is no more active development nor bug fixes.
Current Affairs
Since about July 2006 the SNS uses version 2.9, which includes a major re-write of the ArchiveEngine. In March 2006 we changed the overall setup to separate "sampling" from "serving" computers as described in the "Example Setup" section of the current manual, but we are still collecting more data than we can handle.Documentation
See manual.pdf included in the 'manual' subdirectory of the sources or check the snapshot given below.Sources
People with access to the SNS CVS repository at ORNL might prefer to look there.For non-SNS collaborators, some snapshots are available here:
- archiver.tgz, a 08/29/2006 snapshot of the Channel Archiver...
- manual.pdf, ... and the manual.
- archive_viewer_15.tgz is a
03/24/2006 snapshots of version "1.2 SNS 2" of the Java archive
viewer which includes some bug fixes, see the release file
that comes in the tgz.
The snapshot was built with Java 1.5. If you have Java 1.5, all you have to do is unpack and then run "java -jar archiveviewer.jar -u Your_Data_Server_URL". It includes the sources, so you can recompile yourself. - The Java Archive Viewer also has its own web page:
http://ics-web1.sns.ornl.gov/archive/viewer/index.html. - channelarchiver-1.10.2.src.zip: The last R3.13 version.
Related Sources
StripTool is primarily a "live" Channel Access client, see http://www.aps.anl.gov/epics/extensions/StripTool."History" modules allow StripTool to access ChannelArchiver samples in addition to Channel Access data.
There used to be a preliminary history plug-in for StripTool 2-4 and 2.5.4.1. It worked somewhat but had the following issues: Striptool has a GUI button for archiver configuration, but the Strip-History API does not allow customization of that dialog (which is specific to the DESY data server). Ideally, the StripHistory API would include a "ShowHistoryConfig" method where the ChannelArchiver data source could be configured (server URL, archive, request method).
The StripHistory API lists support for async operation via FETCH_PENDING, but it's not implemented inside StripTool. All requests for history data will therefore cause delays in the operation of StripTool.
It might not be a good idea to use the current StripTool with history data access.
The following is a copy of a previous StripTool release, including glue code for the R3.13.x ChannelArchiver. It will not work with the new XML-RPC data server.
