---

1/25/2002 12:29:00 PM

We briefly talked about the messages that will be passed between computers and have come up with the following 3:

1. Command Message




• Turn on/off experiment


• Change attitude


• Run backup kernel functionality


• ...




2. Query Message




• Are you alive?


• What is the current coordinate?


• ...




3. Data Message




• I am alive


• Raw experiment data


• Formatted experiment data


• Coordinate data


• ...

posted by dJsLiM | Link | Edit

---

1/25/2002 11:42:00 AM

We have sandbox directories underneath our project home so that we can use that space for anything we want. (i.e. use it as your working directory instead of using your own AFS space ) The directories are set up under /afs/andrew/scs/cs/CS395-3/sandbox/ with your respective userids.

---

CVS has been setup. To get started on using CVS, do one of the following:

1. Set your environment variable CVSROOT to /afs/andrew/scs/cs/CS395-3/CVS/


2. Use command line argument -d for all your cvs commands ( i.e cvs -d /afs/andrew/scs/cs/CS395-3/CVS/ checkout ass1 )

Once you have decided to do either one of the above two, you're ready to checkout our ass1 module to start on ass1. Type in the following command in the directory where you want to check files out into.
% cvs checkout ass1

If you had decided to go the command line argument route, you'd have had to insert -d /afs/andrew/scs/cs/CS395-3/CVS/ between cvs and checkout

Browse the online CVS manual here. The main CVS commands you should know how to use are: add, remove, update, commit, and checkout.

---

Python 2.1.2 (includes pyUnit) has been built for Solaris. To run it, use the following path:
% /afs/andrew/scs/cs/CS395-3/python/python

When you start python, you should see the following message:

Python 2.1.2 (#1, Jan 25 2002, 11:00:08)
[GCC 2.95.3 20010315 (release)] on sunos5
Type "copyright", "credits" or "license" for more information.

Now, do the following and make sure your path contains the paths listed below:

>>> import sys
>>> sys.path
['', '/afs/andrew.cmu.edu/scs/cs/CS395-3/python/Lib', '/afs/andrew.cmu.edu/scs/c
s/CS395-3/python/Lib/plat-sunos5', '/afs/andrew.cmu.edu/scs/cs/CS395-3/python/Li
b/lib-tk', '/afs/andrew.cmu.edu/scs/cs/CS395-3/python/Modules', '/afs/andrew.cmu
.edu/scs/cs/CS395-3/python/build/lib.solaris-2.8-sun4u-2.1']

To quit, press CTRL-D

Of course you may make your lives easier by making aliases, links, altering your paths, etc...

posted by dJsLiM | Link | Edit

---

1/22/2002 04:34:00 PM

Since Sarah is willing to try out python with me, here are some pointers. :) Python.ORG has some excellent resources on python. I suggest you skim through the tutorial ( I bet you will be up and writing python code in an hour ). Here is a link to pyUnit which is the python unit testing framework. I have been an avid python fan for the past 3 years and personally believe python is an excellent language for eXtrememe programming due to its rapid development nature. Also, here is a sample python style guide that I have put together.

posted by dJsLiM | Link | Edit

---

1/21/2002 04:08:00 PM

Guys, check out one coding standard I follow for all my C programs. ( I know that we've picked Java) I'm not a big fan of keeping __rigourous__ coding standards like the one put forth my Hungarian notations and other GNU stuff, but that one has a very simple guideline that I tend to follow all of the time. A colleague of mine recommended that I read Elements of Java Style. For everyone's sake it might be a good idea to get a copy and to breeze through it or have it by your side when you're coding. It's a very tiny paperback reference book. Here are some main points.


posted by dJsLiM | Link | Edit