From dpelleg+ at cs.cmu.edu Fri Dec 6 07:21:21 2002 From: dpelleg+ at cs.cmu.edu (Dan Pelleg) Date: Fri, 6 Dec 2002 07:21:21 -0500 Subject: [auton-users] BigPapa problems Message-ID: <15856.38465.290866.448007@toto.wburn> We're having more trouble with BigPapa. This means you can log in to the lab's servers, but you won't have access to your home or data directories. We'll update you as find out more. Right now it just wouldn't talk to the server at some very low level. We already told it that counts as "being naughty". From dpelleg+ at cs.cmu.edu Fri Dec 6 10:33:38 2002 From: dpelleg+ at cs.cmu.edu (Dan Pelleg) Date: Fri, 6 Dec 2002 10:33:38 -0500 Subject: [auton-users] BigPapa problems In-Reply-To: <15856.38465.290866.448007@toto.wburn> References: <15856.38465.290866.448007@toto.wburn> Message-ID: <15856.50002.588330.568989@gargle.gargle.HOWL> BigPapa is back online now. Apologies for the inconvenience. We're ordering some new SCSI cables for it. From komarek at andrew.cmu.edu Sat Dec 14 15:24:46 2002 From: komarek at andrew.cmu.edu (Paul Komarek) Date: Sat, 14 Dec 2002 15:24:46 -0500 (EST) Subject: [auton-users] lazy belongs to the admins for a while Message-ID: Jacob and I have commandeered lazy for some idl tests. -Paul From komarek at andrew.cmu.edu Tue Dec 17 15:31:16 2002 From: komarek at andrew.cmu.edu (Paul Komarek) Date: Tue, 17 Dec 2002 15:31:16 -0500 (EST) Subject: [auton-users] lazy is available Message-ID: Oops, forgot to tell everyone that lazy is available again. I hope nobody has been waiting for us to make this announcement, as lazy has been availble again for several days. -Paul Komarek From komarek at andrew.cmu.edu Tue Dec 17 15:30:27 2002 From: komarek at andrew.cmu.edu (Paul Komarek) Date: Tue, 17 Dec 2002 15:30:27 -0500 (EST) Subject: [auton-users] IDL on GNU/Linux Alphas Message-ID: Hello, Some of you have complained in the past about the abnormal slowness of IDL on the GNU/Linux Alphas for certain (maybe all) operations. That problem has been fixed, hopefully completely. Bob is happy, so we're happy. Let me know if you are not happy. Please respond to user at autonlab.org. -Paul Komarek From komarek at andrew.cmu.edu Tue Dec 17 16:19:39 2002 From: komarek at andrew.cmu.edu (Paul Komarek) Date: Tue, 17 Dec 2002 16:19:39 -0500 (EST) Subject: [auton-users] [Fwd: Not entirely happy] (fwd) Message-ID: ---------- Forwarded message ---------- Date: Tue, 17 Dec 2002 16:20:16 -0500 From: Chris Miller To: Paul Komarek Subject: [Fwd: Not entirely happy] Paul, I was unable to send to user at autonlab.org from my machine (I guess I need the whole, unaliased group).. Could you forward this to the mailing list? -------- Original Message -------- Subject: Not entirely happy Date: Tue, 17 Dec 2002 16:17:34 -0500 From: Chris Miller Reply-To: chrism at cmu.edu To: user at autonlab.org Dear Paul and others, Something definitely changed on the auton linux-alphas. My code seems to run faster than it use to. But note that it never runs fast (i.e. it is typically as fast as on my 1Ghz Pentium). However, I started a code earlier today and noticed something had changed within the last couple of hours: I went from running pretty fast, to a dead crawl. I have suspended the code (while still in IDL) and when I type: print, sin(whatever), it takes a full second to calculate. That same command runs instantaneously on Crazy. It *wasn't* having the problem a couple of hours ago (i.e. the code got about half-way done before this started happening). Any ideas? Anything in the kernel logs look funny? Chris From komarek at andrew.cmu.edu Tue Dec 17 17:22:45 2002 From: komarek at andrew.cmu.edu (Paul Komarek) Date: Tue, 17 Dec 2002 17:22:45 -0500 (EST) Subject: [auton-users] [Fwd: Not entirely happy] (fwd) In-Reply-To: Message-ID: Hi Chris, The problem we're having with IDL is that the GNU/Linux Alpha version keeps triggering unaligned exceptions. It's not completely clear whether these are the fault of IDL or something in Linux (the kernel). That said, IDL is currently causing (directly or indirectoy) many hundreds of these exceptions right now, which explains your slow-down. I'm not sure what to do or say. Here are some options: 1) Changing Linux kernels has helped in the past (making it look like the kerenls are guilty). We're already current with the kernels, but could try an older kernel (while hopefully avoiding the weekly-scsi-error-fest we had with many of the older kernels). 2) We could reinstall Tru64 on Limey. However, nobody seemed to like Tru64 -- limey/Tru64 was only used for occasional IDL and scp tasks over the last several months and never registered any significant or continued load (except for some of my doing). 3) We could complain to the IDL folks. They have a new version of IDL out for every platform they support (it seems), except for GNU/Linux on Alpha. I'd appreciate suggestions. For the record, #2 is my least favorite because a) I'd like to standardize on GNU/Linux for the Alphas and hence avoid the hours of extra work I've put in adapting admin stuff to Tru64, not to mention changing my personal stuff from time to time as well as the AUTON lab's build scripts, b) It seems a big waste to use limey only for IDL and scp, as it has been used for the last several months with Tru64 (even when the GNU/Linux Alphas have been slammed). We bought for over $40,000 and currently sells for over $10,000. Limey has a nice big 64 bit address space, 4GB of ram, and a 4MB cache. Sustaining an average load of 0.00 is a bit silly. -Paul On Tue, 17 Dec 2002, Paul Komarek wrote: > > > ---------- Forwarded message ---------- > Date: Tue, 17 Dec 2002 16:20:16 -0500 > From: Chris Miller > To: Paul Komarek > Subject: [Fwd: Not entirely happy] > > Paul, I was unable to send to user at autonlab.org from my machine > (I guess I need the whole, unaliased group).. > > Could you forward this to the mailing list? > > > -------- Original Message -------- > Subject: Not entirely happy > Date: Tue, 17 Dec 2002 16:17:34 -0500 > From: Chris Miller > Reply-To: chrism at cmu.edu > To: user at autonlab.org > > > > Dear Paul and others, > Something definitely changed on the auton linux-alphas. > My code seems to run faster than it use to. But note that it > never runs fast (i.e. it is typically as fast as on my 1Ghz Pentium). > > However, I started a code earlier today and noticed something > had changed within the last couple of hours: I went from running > pretty fast, to a dead crawl. I have suspended the code (while > still in IDL) and when I type: print, sin(whatever), it takes a full second > to calculate. That same command runs instantaneously on Crazy. > > It *wasn't* having the problem a couple of hours ago (i.e. the > code got about half-way done before this started happening). > > Any ideas? Anything in the kernel logs look funny? > > Chris > > > > > > > From nichol at cmu.edu Tue Dec 17 17:42:36 2002 From: nichol at cmu.edu (nichol) Date: Tue, 17 Dec 2002 17:42:36 -0500 (EST) Subject: [auton-users] fds conversion Message-ID: Hi All, Someone help me before with ascii to fds conversion (thanks). I need to do it again but dont want to bug someone everytime I need this. Is there a script (c or f77 program) to do this? I have "fdsconvert.pl" in one of my directories (/mnt/BigPapa/home/nichol/npt/GIFparticles) but it doesnt seem to produce a .fds file?? Cheers Bob -- Bob Nichol 5000 Forbes Ave. Carnegie Mellon 412-268-8068 nichol at cmu.edu From komarek at andrew.cmu.edu Tue Dec 17 18:14:18 2002 From: komarek at andrew.cmu.edu (Paul Komarek) Date: Tue, 17 Dec 2002 18:14:18 -0500 (EST) Subject: [auton-users] fds conversion In-Reply-To: Message-ID: Hi Bob, 1) get dset If you have access to AUTON source, you should check out the dset project and build it (it depends on the utils probject). I can help you with that to some extent. In case you don't have or want the source, I copied the dset executable to your home directory. It is called (surprise) dset. 2) run dset if your input (text) file is foo.txt, do ./dset edit in foo.txt 3) save as fds from the dset prompt, do save foo.fds 4) quit type 'quit' to quit from dset If the input filename ends in .txt or .csv, it will be read in some sensible way for an ascii file. When you save, if you save to a filename with .fds as the extension, then you'll get an fds file. Of course, you can to the opposite, too: ./dset edit in foo.fds save foo.txt quit -Paul On Tue, 17 Dec 2002, nichol wrote: > > Hi All, > > Someone help me before with ascii to fds conversion (thanks). > I need to do it again but dont want to bug someone everytime > I need this. Is there a script (c or f77 program) to do this? > > I have "fdsconvert.pl" in one of my directories > (/mnt/BigPapa/home/nichol/npt/GIFparticles) but it doesnt seem > to produce a .fds file?? > > Cheers > > Bob > > > -- > Bob Nichol > 5000 Forbes Ave. > Carnegie Mellon > 412-268-8068 > nichol at cmu.edu > > > From nichol at cmu.edu Tue Dec 17 21:03:17 2002 From: nichol at cmu.edu (nichol) Date: Tue, 17 Dec 2002 21:03:17 -0500 (EST) Subject: [auton-users] fds conversion In-Reply-To: Message-ID: Thanks Paul, Actually, I was wondering if there was a simplier alternative like the "fdsconvert.pl" code some put in my dir. It seems to work apart from it just prints the screen. Is the fds format hard to understand. Actually, another option is for me to use someone elses dset; can someone point me to theirs? Cheers Bob * *Hi Bob, * *1) get dset * *If you have access to AUTON source, you should check out the dset project *and build it (it depends on the utils probject). I can help you with *that to some extent. * *In case you don't have or want the source, I copied the dset executable to *your home directory. It is called (surprise) dset. * *2) run dset * *if your input (text) file is foo.txt, do * * ./dset edit in foo.txt * *3) save as fds * *from the dset prompt, do * * save foo.fds * *4) quit * * type 'quit' to quit from dset * *If the input filename ends in .txt or .csv, it will be read in some *sensible way for an ascii file. When you save, if you save to a filename *with .fds as the extension, then you'll get an fds file. Of course, you *can to the opposite, too: * * ./dset edit in foo.fds * save foo.txt * quit * *-Paul * *On Tue, 17 Dec 2002, nichol wrote: * *> *> Hi All, *> *> Someone help me before with ascii to fds conversion (thanks). *> I need to do it again but dont want to bug someone everytime *> I need this. Is there a script (c or f77 program) to do this? *> *> I have "fdsconvert.pl" in one of my directories *> (/mnt/BigPapa/home/nichol/npt/GIFparticles) but it doesnt seem *> to produce a .fds file?? *> *> Cheers *> *> Bob *> *> *> -- *> Bob Nichol *> 5000 Forbes Ave. *> Carnegie Mellon *> 412-268-8068 *> nichol at cmu.edu *> *> *> * -- Bob Nichol 5000 Forbes Ave. Carnegie Mellon 412-268-8068 nichol at cmu.edu From komarek at andrew.cmu.edu Tue Dec 17 21:53:34 2002 From: komarek at andrew.cmu.edu (Paul Komarek) Date: Tue, 17 Dec 2002 21:53:34 -0500 (EST) Subject: [auton-users] fds conversion In-Reply-To: Message-ID: Hi Bob, If the perl script is writing to screen, maybe you just need to redirect it into a file: fdcconvert.pl foo.txt > foo.fds As far as "someone else's dset", they're all going to be the same as the one I put in your home directory. dset isn't my software, and I haven't customized it at all. So here's what I did for you, Bob. There's a new executable in your home directory called dsetconvert. It only does one thing: convert between text and fds. ./dsetconvert foo.txt foo.fds or ./dsetconvert foo.fds foo.txt Furthermore, it's written in C and compiled with optimizations, so it will be fast on large datasets. The only way it's going to get any simpler is if you hire an undergrad. ;-) -Paul On Tue, 17 Dec 2002, nichol wrote: > > Thanks Paul, > > Actually, I was wondering if there was a simplier alternative > like the "fdsconvert.pl" code some put in my dir. It seems to > work apart from it just prints the screen. Is the fds format > hard to understand. > > Actually, another option is for me to use someone elses dset; > can someone point me to theirs? > > Cheers > > Bob > > > * > *Hi Bob, > * > *1) get dset > * > *If you have access to AUTON source, you should check out the dset project > *and build it (it depends on the utils probject). I can help you with > *that to some extent. > * > *In case you don't have or want the source, I copied the dset executable to > *your home directory. It is called (surprise) dset. > * > *2) run dset > * > *if your input (text) file is foo.txt, do > * > * ./dset edit in foo.txt > * > *3) save as fds > * > *from the dset prompt, do > * > * save foo.fds > * > *4) quit > * > * type 'quit' to quit from dset > * > *If the input filename ends in .txt or .csv, it will be read in some > *sensible way for an ascii file. When you save, if you save to a filename > *with .fds as the extension, then you'll get an fds file. Of course, you > *can to the opposite, too: > * > * ./dset edit in foo.fds > * save foo.txt > * quit > * > *-Paul > * > *On Tue, 17 Dec 2002, nichol wrote: > * > *> > *> Hi All, > *> > *> Someone help me before with ascii to fds conversion (thanks). > *> I need to do it again but dont want to bug someone everytime > *> I need this. Is there a script (c or f77 program) to do this? > *> > *> I have "fdsconvert.pl" in one of my directories > *> (/mnt/BigPapa/home/nichol/npt/GIFparticles) but it doesnt seem > *> to produce a .fds file?? > *> > *> Cheers > *> > *> Bob > *> > *> > *> -- > *> Bob Nichol > *> 5000 Forbes Ave. > *> Carnegie Mellon > *> 412-268-8068 > *> nichol at cmu.edu > *> > *> > *> > * > > -- > Bob Nichol > 5000 Forbes Ave. > Carnegie Mellon > 412-268-8068 > nichol at cmu.edu > > >