=========================== LUNAR ROVER / SOFTWARE NEWS as of April 25, 1995 =========================== ============================================================================== From terry@cmu.edu Wed Nov 16 12:12:05 1994 Newsgroups: frc.general Path: gate.frc.ri.cmu.edu!ingres From: terry@cmu.edu Subject: AFS installed on tahiti & bermuda AFS is now installed on tahiti & bermuda. The installed cell is cs.cmu.edu (what a surprise, eh?). You should be able to use /usr/local/bin/klog to authenticate & get a token for your CS AFS directories. One thing to keep in mind is that tokens are not destroyed on logout unless you do it explicitly (this is true on the FRC suns as well). If you are running csh or tcsh, you should be able to do it in a .logout script as: #!/bin/csh -f # try and destroy AFS tickets if (-x /usr/vice/bin/unlog) then /usr/vice/bin/unlog else if (-x /usr/local/bin/unlog) then /usr/local/bin/unlog else echo warning: AFS tickets not destroyed... sleep 5 endif The AFS cache on both tahiti & bermuda is set at 25 MB and the performance is pretty peppy. Please let me know if you want the cache increased (both machines have enough disk that even 100 MB is possible). -terry ============================================================================== From lri-general-Request@N3.SP.CS.CMU.EDU Tue Jan 17 22:46:03 1995 Sender: Terry Fong Date: Tue, 17 Jan 95 22:44:58 EST From: terry@cmu.edu Reply-To: Terry Fong If you are planning to use the LRI SGI machines (defiant, reliant, voyager) you will need to fix your login files. In particular, if you have a ".xsession" file, you probably will be unable to login at the console. Also, make sure you have "/usr/sbin and /sbin" in your path. The directory ~terry/templates/new-user (accessible from any FRC machine) contains a set of login files which can be used on any FRC machine (Sun or SGI). Let me know if you have any questions! -terry ============================================================================== From lri-general-Request@N3.SP.CS.CMU.EDU Wed Jan 25 15:51:57 1995 Sender: Terry Fong Date: Wed, 25 Jan 95 15:49:47 EST From: terry@cmu.edu Reply-To: Terry Fong There are currently (5) ways to send mail on the SGI's: /bin/mail /usr/sbin/Mail /usr/local/bin/mh/... /usr/bin/X11/zmail /usr/local/bin/emacs (using RMAIL) Please be aware that if you are used to using "mail" under SunOS, the comparable one under IRIX is "Mail". The "Mail" program is the BSD mail program (don't ask me why it is sitting in /usr/sbin). -terry P.S. Murph... nudge, nudge. You should try typing "Mail" instead of "mail". ============================================================================== From lri-general-Request@N3.SP.CS.CMU.EDU Sun Feb 26 21:05:59 1995 Sender: Terry Fong Date: Sun, 26 Feb 95 21:04:23 EST From: terry@cmu.edu Reply-To: Terry Fong The Pele team has agreed to let us drive the Marsokhod while it is still in Hawaii. The arrangement is for us to use the simple user interface developed for JASON, which provides some basic steering functions and frame grabbed images. To do this, I will need to setup some software on a PC ('486 or Pentium preferred) which is connected to the net. So, if anyone has suggestions for a PC that can be borrowed for a day or so, please send me email. Thanks. -terry ============================================================================== From lri-general-Request@N3.SP.CS.CMU.EDU Wed Mar 15 22:28:42 1995 From: "Lalitesh K. Katragadda" To: lri-general@ri.cmu.edu Subject: WWW pages Date: Wed, 15 Mar 95 22:27:14 EST the following directories have been created in /afs/cs/project/lri-3 www : To contain all html (www) files public : To contain public software, demos, etc ftp : Documents, etc for ftp access Access: The group has read-write access to it The world has read access to it All the directories can be accessed through anonymous ftp The lri master/homepage is http://www.cs.cmu.edu:8001/afs/cs/project/lri-3/www/moon-bug.html This is the only page to be publicized as lri; all the other home pages including ones for configuration, autonomous tech, LunaCorp will be linked to it. This page will contain info for files in ftp & other public locations. This file will also have all sorts of contact info, Warning: Right now, a very rough version exists as a place holder, please bear with me for a week before clobbering me, If you create a relevant web page let me know; If you have relevant web pages (eg personal homepages), let me know, they will all be linked cheers, lalit ============================================================================== From lri-general-Request@N3.SP.CS.CMU.EDU Thu Mar 16 02:51:40 1995 Sender: Terry Fong Date: Thu, 16 Mar 95 2:49:20 EST From: terry@cmu.edu Reply-To: Terry Fong As a follow-up to Lalit's last message, the directories: /afs/cs/project/lri-3/ftp /afs/cs/project/lri-3/public are open to people in LRI. To create/delete files in these areas, you will have to be authenticated to the CS AFS cell (if you are on a FRC machine, use klog to get a valid token). You do not need to authenticate just to read files in these areas (in fact, anyone in the entire world with AFS can read files in these directories). Files in the directory: /afs/cs/project/lri-3/www can only be modified by the following people: Sven, Andy, Lalit, Eric K., and Reid If you want to create WWW pages, please talk to one of the above people. -terry ============================================================================== From lri-general-Request@N3.SP.CS.CMU.EDU Tue Mar 28 17:47:52 1995 Sender: Terry Fong Date: Tue, 28 Mar 95 17:45:52 EST From: terry@cmu.edu Reply-To: Terry Fong I have setup an area for anonymous ftp for the project to use. The directories are: /afs/cs/project/lri-3/ftp/incoming /afs/cs/project/lri-3/ftp/outgoing The "incoming" directory is configured as a "drop-box". People who use anonymous ftp to FTP.CS.CMU.EDU can upload files into this directory, but will be unable to modify or delete the files once written. The "outgoing" directory is configured for *private* outgoing files. Anonymous ftp users must know the *full* pathname to files in this area since they will be unable to do a "ls" on the directory. All LRI project members have been given permission to place files into this directory. If you have any questions, let me know! -terry P.S. At the current time, FTP.CS.CMU.EDU appears to be having some problems. I've sent Paul Klarer mail about an alternative method for ftp'ing files to the nav group. ============================================================================== From terry@N3.SP.CS.CMU.EDU Wed Mar 29 18:55:49 1995 Sender: Terry Fong Date: Wed, 29 Mar 95 18:55:05 EST From: terry@cmu.edu Reply-To: Terry Fong To: Dimitrios Apostolopoulos Subject: Re: FTP access Hi Dimi, It's pretty easy, just look at the SCS help page: http://www.cs.cmu.edu:8001/afs/cs.cmu.edu/help/www/01-Documentation/01-SCS_Intro_Doc/32-FTP.html -terry ============================================================================== From lri-general-Request@N3.SP.CS.CMU.EDU Fri Mar 31 10:59:10 1995 Sender: Terry Fong Date: Fri, 31 Mar 95 10:57:02 EST From: terry@cmu.edu Reply-To: Terry Fong To: lri-general@N3.SP.CS.CMU.EDU Subject: now open for business (aka use the /AFS space) Please feel free to use our AFS project space: /afs/cs/project/lri/ doc/ documents (link to ../lri-1/doc) ftp/ ftp area (link to ../lri-3/ftp) members/ personal files (please create your own directories) public/ public demos (link to ../lri-3/public) www/ WWW files (link to ../lri-3/www) I've moved the documents formerly in /usr/apex/doc to /afs/cs/project/lri/doc (/usr/apex/doc will be made read-only as you should use the /afs doc area). Please let me know if there are other directories that should be moved too. Enjoy! -terry ============================================================================== From lri-general-Request@N3.SP.CS.CMU.EDU Mon Apr 10 19:15:30 1995 Date: Mon, 10 Apr 1995 23:09:31 GMT From: Kenneth Courtney Meeting Minutes Meeting Name: LRI Software group weekly meeting Meeting called by: Mary Courtney Location: FRI Small conference room Date: April 6, 1995 Start Time: 4:00PM End Time: 6:00PM Work Breakdown Structure Number: 1.1 Attendees: Mary Courtney, John Murphey, Terry Fong, Conrad Maher, Ken Courtney. Topics: 1. Status of ROSE project The ROSE software is being incrementally developed using Cadre Teamwork OOA models and Recursive Design, C++ programming language, TCA to accomplish intertask communication and TK/TCL to handle the user interface. A refined scenario has been modeled in the OOA CASE tool and the finite state machines for this model are complete. The model is baselined in the CADRE directories stored on gs202.sp. The software architecture and program design use the Shlaer-Mellor recursive design method to produce Rover software objects that rely on active object components driven by an event queue to handle message passing between object state machines. Work on templates that will systemize the creation and refinement of such components is in progress and should be completed over the next week. The user interface under TK/TCL will support the input of scenario 'commands' which are translated internally into 'events' for pushing onto the event queue of the system. This work is about 50% complete and will contain the controlling routines for the entire software package. In addition, TK/TCL is being used to construct user initiated object 'views' which will display the state tables for each software object for information and event injection. This effort is about 80% complete. Focus at this time is on using TCA to interface the state machines and command processor to the software objects developed for the Rover physical simulation, Rover onboard software simulation and the Lunar Environment simulation. This interface will rely on TCA as the mechanism for supplying events and data across the boundary of each independent task. Work in this area is progressing well but lack of familiarity with TCA and TK/TCL has caused problems. 2. Status of the LRI software effort in general Terry Fong spoke of his concern that the overall hardware architecture for the mission software needed attention. He volunteered to research various options and correct some errors in the Rover Technical Report. He discussed the fact that the LRI project has an objective to put out a design release in early August that will narrow technology options down to 3-4 options at most on major components. Terry's objective over the summer will be to identify the best candidate platforms and to report on their capabilities with respect to speed, memory, reliability and environmental tolerances. This suggests that the software group should focus on characterizing the major design configurations with respect to their requirements for memory and speed as well as the reliability concerns associated with the software capabilities that these designs require. Thus the ROSE tool is being specifically developed to quickly investigate high level performance of software and hardware components under a variety of software control strategies and hardware configurations. 3. Work planned for the remainder of the semester The goal of the MSE members is to complete a good demonstration prototype of the ROSE tool. To this end, they are working on the completion of the underlying mechanisms and have been soliciting input from other LRI project members to insure that the tool is being refined to the needs of the LRI community. Members of the LRI-Soft team will meet each Thursday from 4:00-6:00 pm at the SGI machines to review progress and provide input on the direction to take the next week's work. All members of the LRI project are welcome to attend and provide input. 4. Input to the ROSE develop effort - The tool should simulate various software modules and enable the user to understand the data flow requirements that specific software strategies and hardware configurations impose upon the system. - The tool should help identify where things must reside on the selected hardware platform. - The tool should enable users to investigate various design options and learn enough about their performance to make design decisions. - Final product should provide as default the current top choice with respect to various Rover software and hardware components. A pull down menu could provide additional options which the user should be able to select at will. System should be smart enough to constrain incompatible options. - Final product should allow users to view the event trace and easily see how the system responded to a scenario. This means that event states and labels should be descriptive and easy to understand. - System for developing and incorporating new components should be easy to follow from an example and accompanying documentation. That's all for now. Until this Thursday, Mary ==============================================================================