Update on IS performance issues Classes for storing and retrieving scan data from IS GUI updates –Scripting support –Histogramming Overview

All data is sent as XML (!). This involves converting all data to text. E.g.: My test sent 4k chunks of data. But the sent data was ~20k. Using the array format improved performance to nearly 1Mb/s. It isn’t clear how useful this array format is. I’ve suggested to Kolos that they compress the data stream first. This should improve performance significantly – perhaps even faster than IPC. But no word yet on whether this will be implemented. IS Performance

SCTData A package to send and retrieve scan data using IS Not sure yet what SCTAPI will produce, so just invented something reasonable. Extremely preliminary, all code subject to change and overhaul!

GUI Updates - Scripting Scripting provided by IBM’s Bean Scripting Framework –Provides general interface to many scripting engines. Scripting engines are robust – two currently tested –BeanShell – Java syntax –JavaScript – same engine as in Mozilla –Many others possible – Python, Perl, etc –No dictionary generation required – direct access to all Java objects –Access can be controlled. Console requires some work to get to same functionality as CINT. –E.g. Tab completion – easy (ish) for Java objects, harder for local vars. –Robust handling of all keyboard input.

GUI Updates – Histogramming GUI now has an internal plotter. Provided by JAIDA (an AIDA interface to JAS). Can plot 1D and 2D histograms –2D histograms only as contour or box plots – not 3D. Will probably suffice for our needs. Removes problems with ROOT event loop and threading issues.