SEPJava files follow the general form of SEPLIB files. Each dataset contains an ASCII file (.J by convention) and a binary data file. The ASCII file follows the standard SEPLIB conventions (in, esize, n1 n2, d1, d2, o1, o2, etc.) The only additional requirement is this cube description is given in a specific form (seen below) at the beginning of the ASCII file. The .J file for the data seen in Figure 3 is seen below:
in=circle.T@ esize=1 n1=250 n2=90 n3=5 d1=0.000002000 d2=50.000000 d3=1.000000 o1=0.002000 o2=50.000000 o3=0.000000 title=Phase Shift Circle label1=time label2=position label3=phase
In addition to the .J file and the binary data file, an html file is required. The html file requires the applet, in this case the Animator, you wish to call; the location of the code for that applet; the path of the data; and the location of the header file.
<html>
<head>
<title> circle.J </title>
</head>
<APP CLASS="Animator"
src="http://sepwww.stanford.edu/sep/krl/Animator/"
PATH="http://sepwww.stanford.edu/pub/sep/bob/"
HEADER="http://sepwww.stanford.edu/pub/sep/bob/circle.J">
</html>
At SEP, a SEPLIB history file can be created by using Bytecube2www:
Byte2java <input.H parsRequired: applet=a Animator c Cube Viewer Optional: in_J=Name of the binary header file htmlout=name of html file [input.html] fileout=Java file name anipath=http path of the applet [http://sepwww.stanford.edu/sep/krl/[applet]/]
data_http=http address of the java file data_out=unix directory htmlpath=html directory all defaulted to (/sepwww/pub/sep/username/ and http://sepwww.stanford.edu/sep/username/ username can be over written by using user variable to put files in subdirectories
Purpose: Converts a standard SEPLIB header file to our accepted form for a SEPJava header file and puts the header file, the data file, and a created html file into the user's sepwww directory.