A Step-By-Step Tour of Java Analysis Studio

A job is the most fundamental construct in Java Analysis Studio.   There are two basic job types:

• A local job is the simplest type, where all event processing takes place on the user's machine.  All data sources are on the user's machine, or accessible on its network.
• A remote job is more complicated.  In a remote job, Java Analysis Studio works in client/server mode.  The data sources used are on a server that is running Java Data Server code.  All event processing takes place there.  While histogram bin values or other results of event processing are sent to the client, the data themselves remain on the server.  The user can use the client code to visualize and analyze the data summaries without having to send it all over from the server.

Java Analysis Studio accesses data using pluggable Data Interface Modules (DIMs).   The Java AnalysisStudio developers have created a number of DIMs for commonly used data formats, but users are free to define their own by following our documentation.

A Java Data Server must be configured for which DIMs it will use.  Local data are accessed using Local Data Interface Modules, which are stored in a Local DIM Registry.   Users can add and remove classes from this registry to customize the application to their specific needs.

Opening a job

To open a job, use the new job wizard. Its first page is shown below:

The wizard asks the user to open eiter a job for generating events or for analyzing events.  The only difference is that if you select a job for analyzing events, the wizard will take you to the pages for opening data sets.  How this works depends on whether the job is remote or local.  See the examples of opening data sets.

If you have selected a remote job, the wizard will ask for a server name.  Give the name of a server that is running the Java Data Server code.  There is currently no documentation on how to set up your own data server, so contact Tony Johnson or Jonas Gifford for information on how to do this.

Our example branches into now, to give separate examples for how event analyzers and event generators.  For event analyzers, see creating an event analyzer.   For event generators, see creating an event generator.

Some other pages that may be of interest:

• The Java Analysis Studio Environment
• Help Contents (requires browser with JDK 1.1 and may take a while to load)

Click here to submit a bug, comment, or suggestion.

You are visitor number .

Page maintained by Jonas Gifford.   Last updated 01/14/04.