ARSC HPC Users' Newsletter 341, May 26, 2006
ARSC Summer Tours start June 7th
ARSC conducts public tours in our Discovery Lab every summer. This is a great introduction to the center. No reservations required, but if you've got a large group, please contact "firstname.lastname@example.org" first:
ARSC Summer Tours, 2006:
- June 7-August 30: Wednesdays, 1 p.m.
For more info and directions to the D-Lab, see:
Seminar Series: ARSC Postdoctoral Fellows
Please join for seminars conducted by ARSC's Postdoctoral Fellows. These events are scheduled for the 1st and 3rd Wednesdays, May through August, 1 - 2pm in the ARSC Conference Room, WRRB 010. (You can still take your ARSC tour on the 2nd or 4th Wednesday!)
May 17: John Chappelow, "Atmospheres and Impact: Mars" June 7: Jessica Cherry, "Arctic Hydroclimatology" June 21: TBA July 5: Martin King, "Ocean Internal Wave Generation by Tidal Forcings" July 19: Peter Webley, "Ash Dispersion Modeling of North Pacific Volcanoes" August 2: John Bailey, TBA August 16: Daniel Pringle, "Towards Lattice Boltzmann modeling of Fluid Flow in Sea Ice"
Quick-Tip Q & A
A:[[ What development environments do you use to write [[ C/C++/FORTRAN/<other> code, and how do you manage your (possibly [[ many) source code files. What editors and other tools do you [[ use? # # From Kate Hedstrom: # I've described how I use make on all our files in prior issues. We've gone to a multidirectory structure after many years of having all the files in one directory. We use cpp and Perl too. There are two Perl scripts, one to build f90 dependences, one to optionally clean up after cpp, removing blank lines, etc. I use vi - and haven't yet learned the fine points of vim, the vi on Linux. Instead I learned nvi details some years back that don't carry over to vim (though vim's colors are fun). I used to use RCS to manage versions, then migrated to CVS, now I'm learning SVN (Subversion). I'm determined to finally learn to let it help me manage merging versions as I make changes in parallel with other people's changes. # # Lee Higbie # I use SlickEdit, also, or formerly, called "Visual SlickEdit." It provides all the features of a good, language and syntax sensitive editor that you'd expect plus such things as: 1- Color coding & highlighting on screen and on listings 2- Syntax tables for about 60 languages including Fortran. (I have not used it extensively for Fortran, but I've only seen support for Fortran 77.) It would not be difficult to modify the tables for Fortran 95. 3- Multi-file search and replace in a variety of modes, all with syntax sensitivity 4- Side-by-side file comparison/differencing/merging 5- Syntax expansion and user-supplied syntax expansion. This extends to user-created functions/methods where it prompts for such things as types of arguments. 6- Compilation within the editor and jumping directly to the site of the next compiler-detected error. This extends to running and debugging from within SlickEdit. (But what I really need is jumping to the next undetected error.) 7- Jump from the current symbol to its definition and back (one keystroke each). Q: Is there a way I can reference my shell aliases from scripts? Here's a ksh example of the problem: $ cat t2.ksh #!/bin/ksh ls -l *.ksh $ $ ./t2.ksh -rwx------ 1 monty grp 20 May 26 16:08 t.ksh -rwx------ 1 monty grp 23 May 26 16:08 t2.ksh $ $ alias ll ll='ls -l' $ $ cat t.ksh #!/bin/ksh ll *.ksh $ $ ./t.ksh ./t.ksh: ll: not found $
[[ Answers, Questions, and Tips Graciously Accepted ]]
Ed Kornkven ARSC HPC Specialist ph: 907-450-8669 Kate Hedstrom ARSC Oceanographic Specialist ph: 907-450-8678 Arctic Region Supercomputing Center University of Alaska Fairbanks PO Box 756020 Fairbanks AK 99775-6020
Subscribe to (or unsubscribe from) the e-mail edition of the
ARSC HPC Users' Newsletter.
Back issues of the ASCII e-mail edition of the ARSC T3D/T3E/HPC Users' Newsletter are available by request. Please contact the editors.