Sponsored Content
Special Forums News, Links, Events and Announcements DARPA contestants make robotic history Post 85965 by vino on Sunday 9th of October 2005 11:36:02 AM
Old 10-09-2005
The Red Team

To add to this. The first DARPA Grand Challenge was held a little more than 18 months ago. At that time no one completed the race. CMU's Sandstorm went about 7 miles and then crashed out of the challenge. None of the others even came up to 7 miles.

I was working under one of the CMU Prof's who also happened to be one of the external technical advisor for Sandstorm. The reason he gave for the crash was the technical people behind Sandstorm did not forsee the following situation: Encounter a curved uphill slope.

So apparently Sandstorm did not reduce its speed when it encountered the curved uphill slope. Hence it jumped the tracks, which lead it to crash and eventually one of the wheels caught fire.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ksh: how to make [up arrow] recall command history

I want to get my up arrow key to recall my previous commands in Korn shell. Anyone help please? thanks a bunch! BG (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

2. UNIX for Dummies Questions & Answers

How to review the history and the commands that has been done in this history?

Hello every body, Kindly inform me How Do i find out the time I executed a command previously on UNIX Solaris?? To be more specific and more clear about what i want to know is that I want a command the enables me to know the history and which command i run at this history/time. FYI I used... (5 Replies)
Discussion started by: ahmedamer12
5 Replies

3. UNIX for Advanced & Expert Users

History to Another file [local user history , but root access]

Hi all, My need is : 1. To know who , when , which command used. 2. Local user should not delete this information. I mean , with an example , i can say i have a user user1 i need to give all the following permissions to user1, : a. A specific directory other than his home... (3 Replies)
Discussion started by: linuxadmin
3 Replies

4. UNIX for Dummies Questions & Answers

History to Another file [local user history , but root access]

Hi all, My need is : 1. To know who , when , which command used. 2. Local user should not delete this information. I mean , with an example , i can say i have a user user1 i need to give all the following permissions to user1, : a. A specific directory other than his home... (1 Reply)
Discussion started by: sriky86
1 Replies

5. UNIX for Dummies Questions & Answers

How to make each login shell history independent for same account?

Hello All, Many developers in our company use same application account to log in Linux Box for code development, how can i redirect my log in shell history to a different file to avoid history being shown to others or accidentally execute the same command which i or others executed? Thank you. (4 Replies)
Discussion started by: Ariean
4 Replies

6. What is on Your Mind?

The Great History of UNIX (1969-1999) | 30 Years of UNIX History | YouTube Video

I am pleased to announce this new video in 1080 HD for UNIX lovers honoring thirty years of UNIX history spanning from 1969 to 1999 presented in 150 seconds (two and a half minutes) in 1080 HD, celebrating the 50th anniversary of UNIX. The Great History of UNIX (1969-1999) | 30 Years of UNIX... (8 Replies)
Discussion started by: Neo
8 Replies
cr_open(3)						     Library Functions Manual							cr_open(3)

NAME
cr_open() - open crash dump for reading SYNOPSIS
DESCRIPTION
The library call opens a crash dump and passes back a crash dump descriptor. The path argument points to a path name naming a crash dump directory or file, and must not exceed bytes in length. The CRASH * to which crash_cb points is set to a crash dump descriptor, which can then be passed to the other functions to access the crash dump. flags is a bitmask of zero or more of the following flag values, which affect the operation of future calls to libcrash routines for this crash dump, except for cr_verify(3), which has its own flags parameter. The library will not attempt to verify checksums of files in the crash dump if this flag is set. The library will write messages to stderr during time-consuming operations (decompressions and checksums) if this flag is set. RETURN VALUE
Returns zero for success. Other possible return values are described in libcrash(5). EXAMPLES
The following call to opens crash dump contained in the directory and returns the crash dump descriptor For an example of reading the crash dump see the cr_read(3) manual entry. AUTHOR
was developed by HP. SEE ALSO
cr_close(3), cr_perror(3), libcrash(5). cr_open(3)
All times are GMT -4. The time now is 03:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy