Level 3 Online Status Reports

Back to index Next

Issue 1
Monday, March 29, 1999

Event Flow

Reports

• Data has been transported from the test wedge, through the ADMEM crate, links, VRB, event builder, and Level 3, all the way to the output node. No trigger was used, and the event rate was limited by the readout to 5.5 events/s. The system stopped after about 200K events.
• Tests using the Level 3 system by itself (converters, processors, and output nodes) stop after several million events.

Actions

• Jeff will work on sending data from the output node to the consumer server.
• Ilya and Christoph will continue with system tests to find out when and why the system stops.

Executable Interface

Reports

• Event reformatting was successful in the above tests, but the test only included one VRB and one SCPU.
• Raw data files can be found in b0l3c04:/cdf/dat, which can be read by the l3_converter program.
• Andreas has written a Java program which generates more complicated fake events for more stringent tests.
• There exists a statically linked Level 3 executable for tests.

Actions

• More complicated tests with the reformatter.
• Christoph will test the executable with the control framework.

Test Control

Reports

• Steve is investigating the use of different CORBA packages. This is because Steve and Sasha have discovered that the ROBIN IDL compiler is somewhat delicate and doesn't implement certain standard features.

Actions

• Steve, Sasha, and Ilya will continue to investigate CORBA packages in order to find one with a good IDL compiler, open source (both libraries and compiler, preferably), and lean libraries.
• We need a Level 3 control IDL.
• Identify where database accesses may be necessary for configuration information.

Monitoring

Reports

• Ivan has investigated the use of SmartSockets. Nice, but the license fee is several hundred dollars per node.
• Christoph and Jim suggest the DIM package, which originated at DELPHI and is being used also at BaBar.

Actions

• Ivan will work on evaluating the DIM package.
• Jeff will make status information accessible in l3_converter.
• Define different sets of monitoring information for Level 3.

Back to index Next