HTML automatically generated with rman
Table of Contents

Name

cookbook - a quick list of what to do to run treecode on the 205 (outdated)

Description

Sample steps to run N-body programs on CYBER 205, as starting on SUN’s. The boldface is what you type on the keyboard. I will assume that you will do your work in some subdirectory on JVNC
(-)
prepare your input data file, in (binary) snapshot format, on the sun. Call it i001.dat. There are various programs available to make these startup files. See Programs(1)
(-)
convert the snapshot to ascii, using STOA: 
sun>stoa i001.dat i001.data
(-)
prepare a parameter file with input parameters for the hackcode to run, call it i001.par. This is a regular ascii file. See treecode(1) for a description what should be in, although it may deviate somewhat if you change your I/O in CODE.UPD on the JVNC/205.
(-)
copy (FTP) both (ascii) files over to JVNC (currently through IASVAX) 
sun>ftp iasvax
-...Name: scratch
-...Password: <CR> (give a carriage return)
ftp> put i001.data
ftp> put i001.par
ftp> quit
(-)
log in on JVNC (you will never directly talk to the 205); 
sun>telnet iasvax
-...Username: NETWORK
-...Enter node name..: JVNC
-...Username: <your JVNC Username>
-...Password: <your JVNC Password>
JVNC>
(-)
go over to the proper dir and get the input files from IASVAX 
JVNC> CD WORK or SET DEF [.WORK]
JVNC> FTP IASVAX
* USER SCRATCH
Password:<CR> (give a Carriage Return)
* GET I001.DATA
* GET I001.PAR
* QUIT
(-)
put the files on the 205: 
JVNC> PEPPUT I001.DATA TREEBODI 
JVNC> PEPPUT I001.PAR TREEPARS
(-)
make sure that the exectuable code is present on the cyber by e.g. running PEPFILES and see if the controllee file (CODEGO) is on your user area on the 205; otherwise, regenerate it by JVNC> @CODECL and wait for a CODE.LOG to come back on VAX and check if compilation was OK.
(-)
run it (perhaps after modifying the time limit and queue in the RESOURCE statement in the CODEGO.COM file. 
JVNC> @CODEGO
(-)
check status using PEPSTAT or check if a new CODE.LOG file has arrived in your directory
(-)
rename the funny 205 output filenames to more appropriate names: 
JVNC> RENAME TREEBODO R001.DATA
JVNC> RENAME TREELOGS R001.LOG 
JVNC> RENAME CODE.LOG C001.LOG
(-)
copy (FTP) your output files back to IASVAX first 
JVNC> FTP IASVAX
* USER SCRATCH
Password:<CR> (give a Carriage Return)
* PUT R001.DATA
* PUT R001.LOG
* PUT C001.LOG
* QUIT
(-)
go back to your favourite SUN: 
JVNC> logout
Enter Node...:<CR> (give a carriage return)
sun> ls
get the files from IASVAXsun> ftp iasvax-...Name: scratch-...Password: <CR> (give a carriage return)ftp> get r001.dataftp> get r001.logftp> get c001.logftp> quit(-)
convert the output ascii file to snapshot and delete the (huge) .data file(s). 
sun> atos r001.data r001.dat 
sun> rm r001.data i001.data 




(-)start analysing...... (see Programs(1))sun> snapplot r001.datAuthorPeter Teuben
Files
JVNCC::DISK27:[TEUBEN1P.CODE]CODE*.COM    some (edited) PEP command files

Bugs

JVNC went out of business in the spring of 1990. Their 5 year contract with NSF was not extended.... The manual page is kept for historical reasons.

See Also

update(lNEMO) , usage205(8NEMO)

Update History


 6-May-87    document created             PJT
25-Jun-87    extensive example session    PJT
9-oct-90    OLD but Kept for Historical Reasons    PJT