Packages

Omegahat
RS-DBI: An interface from R and S to Database Management Systems (DBMS)
RSXML: R and S facilities for reading XML documents and DTDs.
LaTeX, HTML and CSS input files for processing Omegahat (and other) documents.
libProps, a C++ library for reading properties files.
Omegahat include/ directory. Useful for using the source code for Omegahat packages directly without installing (parts of) Omegahat from source.

Omegahat Modules

NumericsSource-0.1.tar.gz Source and compiled classes from the org.omegahat.Numerics module, including the Optimizers, LinearAlgebra, GeneticAlgorithms sub-packages.: Source and compiled classes from the org.omegahat.Numerics module, including the Optimizers, LinearAlgebra, GeneticAlgorithms sub-packages.

Available "Distributions" for Omegahat

This page provides access to much of the current Omegahat code in a variety of different manners. The intent of making it available is to encourage people to get involved and allow people to explore the framework and design philosophy we are developing. It is by no means intended to be a complete or functioning system. The interactive Java interpreter also provides a convenient mode of exploring Java in an R/S-like environment. The CORBA facilities for R, S and Omegahat are reasonably complete and we hope to get feedback about these. The embedded Java within S chapter will be released soon and the version for R shortly after that.

We would appreciate hearing about any problems, successful installations, bugs, comments on the design, etc. There is a bug tracking system which can be used to submit remarks.

Thanks to Tony Rossini for having previously configured the anonymous CVS access server from this machine and for helping to test the installation.

CVS Access

A frequently updated snapshot of the entire (including the interpreter, CORBA material, Models, Graphics, etc.) source tree is available via CVS from the repository

  :pserver:anoncvs@www.omegahat.net:/home/anoncvs/src/omegahat

See CVS Installation for more details.

Non-CVS "Distributions"

OmegaBinary.tar.gz The simplest distribution containing the Environment.jar and Graphics.jar files for the interpreted language and some preliminary primitives for experimenting with static plots. Additionally, the scripts for running Omegahat. You will need to fetch the JHelp distribution for things to run smoothly. (They will run without this, but an error will be produced at startup time.) OmegaSource.tar.gz This contains the java class and source files (in both simple java format and noweb source where available), along with the scripts, etc. In other words, this is a version that one can edit and is not wrapped in jar files, etc.: The simplest distribution containing the Environment.jar and Graphics.jar files for the interpreted language and some preliminary primitives for experimenting with static plots. Additionally, the scripts for running Omegahat.
You will need to fetch the JHelp distribution for things to run smoothly. (They will run without this, but an error will be produced at startup time.)
OmegaSource.tar.gz This contains the java class and source files (in both simple java format and noweb source where available), along with the scripts, etc. In other words, this is a version that one can edit and is not wrapped in jar files, etc.: This contains the java class and source files (in both simple java format and noweb source where available), along with the scripts, etc. In other words, this is a version that one can edit and is not wrapped in jar files, etc.

These two files end with the file extension .tar.gz and have been created with the GNU tar program using the compression flag (z). You can extract them with GNU tar via

     gtar zxvf filename

or with the regular (non-GNU) tar via

  gunzip -c filename | tar xvf -

Installation

Configuration of these should be as simple as

untar the distribution archive
change to the directory org/omegahat/.
run the command ./Config/javaConfigure
If this guessed and displayed an appropriate version for JAVA_HOME, you are set. Otherwise, you need to edit the first two lines of file Config/local.config. Set JAVA_HOME to the appropriate directory and comment out JAVA2 if you are not using Java 2.
Invoke the command ./bin/omegahat

3^rd Party Packages

Antlr The parser and lexer generators from the Antlr distribution by the Magelang Institute, and specifically Terence Parr. Version 2.4.0 works, while higher versions are not yet compatible. Jas The Java byte-code generator from sbktech. JHelp Fetch the JHelp distribution from Sun. Version 1.0 or greater should suffice.: The parser and lexer generators from the Antlr distribution by the Magelang Institute, and specifically Terence Parr. Version 2.4.0 works, while higher versions are not yet compatible.
Jas The Java byte-code generator from sbktech. JHelp Fetch the JHelp distribution from Sun. Version 1.0 or greater should suffice.: The Java byte-code generator from sbktech.
JHelp Fetch the JHelp distribution from Sun. Version 1.0 or greater should suffice.: Fetch the JHelp distribution from Sun. Version 1.0 or greater should suffice.

CORBA Distributions

There are two types of CORBA distributions provided in the Omegahat software. These are

Java based tools and classes, language extensions providing dynamic access to and servers from the interpreted Omega language.
similar dynamic CORBA facilities providing method calls and CORBA servers from both R and S.

Java Classes

Interfaces.jar The classes needed for making the Omegahat session easily CORBA-aware. You will also require the (free for non-commercial use) Orbacus implementation of the CORBA specification from Object Oriented Concepts, Inc. Version 3.x works fine on Linux (RH6.0), Solaris (2.7) and Irix 6.4 for us. To install into the binary distribution above, add this file to the Jars/Omegahat directory. If working from the source code version, you should extract the files using the jar tool in the JDK and do this from the parent of the org/ directory containing omegahat/, i.e. $OMEGA_HOME/../../.. InterfacesSource.tar.gz The source (classes, java and jweb source files) for the Interfaces code in Interfaces.jar. Install by un-tarring the archive from the parent of the org directory. i.e. $OMEGA_HOME/../../..: The classes needed for making the Omegahat session easily CORBA-aware.
You will also require the (free for non-commercial use) Orbacus implementation of the CORBA specification from Object Oriented Concepts, Inc. Version 3.x works fine on Linux (RH6.0), Solaris (2.7) and Irix 6.4 for us.
To install into the binary distribution above, add this file to the Jars/Omegahat directory. If working from the source code version, you should extract the files using the jar tool in the JDK and do this from the parent of the org/ directory containing omegahat/, i.e. $OMEGA_HOME/../../..
InterfacesSource.tar.gz The source (classes, java and jweb source files) for the Interfaces code in Interfaces.jar. Install by un-tarring the archive from the parent of the org directory. i.e. $OMEGA_HOME/../../..: The source (classes, java and jweb source files) for the Interfaces code in Interfaces.jar.
Install by un-tarring the archive from the parent of the org directory. i.e. $OMEGA_HOME/../../..

CORBA in R and S

The following apply to versions of R greater than 0.64 and S4 and Splus5 only. They will not work in versions of Splus based on S, version 3 or earlier versions of R than R-0.65. They also currently require the Orbacus C++ libraries.

R & S CORBA packages/chapters Linux, Solaris (SunOS 5.6), Compiled C++ Libraries, S objects, and R code and documentation providing CORBA access to and from both S and R. These are dynamically linked against the Orbacus 3.1.3 C++ libraries. To install, untar this file from the parent of the directory org/. You will need to set the environment variable ORBACUS_CONFIG to identify the file containing the different Orbacus settings. You can modify the one in org/omegahat/Interfaces/CORBA/CORBAConfig/Orbacus.config and set the environment variable to refer to it. This can be set permanently and applies to all Orbacus applications (yours, the utilities such as idl, irfeed, ...) Then, to install the S chapter, change directory to org/omegahat/S/library/CORBA and issue the commands make chapter To install the R package, change directory to org/omegahat/R/library/CORBA and issue the commands setenv R_HOME wherever the R distribution was installed make To run, you will need to ensure the environment variable LD_LIBRARY_PATH is set. Follow the instructions for treating this as a library in the different systems.: Compiled C++ Libraries, S objects, and R code and documentation providing CORBA access to and from both S and R. These are dynamically linked against the Orbacus 3.1.3 C++ libraries.
To install, untar this file from the parent of the directory org/. You will need to set the environment variable ORBACUS_CONFIG to identify the file containing the different Orbacus settings. You can modify the one in org/omegahat/Interfaces/CORBA/CORBAConfig/Orbacus.config and set the environment variable to refer to it. This can be set permanently and applies to all Orbacus applications (yours, the utilities such as idl, irfeed, ...)
Then, to install the S chapter, change directory to org/omegahat/S/library/CORBA and issue the commands
make chapter

To install the R package, change directory to org/omegahat/R/library/CORBA and issue the commands
setenv R_HOME wherever the R distribution was installed make

To run, you will need to ensure the environment variable LD_LIBRARY_PATH is set.
Follow the instructions for treating this as a library in the different systems.

Daily Updates

Javadoc API A compressed tar file containing the Javadoc output from the latest source files along with some additional documents , built daily. Daily builds. Daily builds of some of the Jar files. At times these won't get built because of errors in the code committed to the CVS repository. Check the dates on the files.: A compressed tar file containing the Javadoc output from the latest source files along with some additional documents , built daily.
Daily builds. Daily builds of some of the Jar files. At times these won't get built because of errors in the code committed to the CVS repository. Check the dates on the files.: Daily builds of some of the Jar files. At times these won't get built because of errors in the code committed to the CVS repository. Check the dates on the files.

Duncan Temple Lang <duncan@research.bell-labs.com>

Last modified: Fri Nov 26 08:33:46 PST 2004