Kurt's Weblog

bp04-6gw-s1-094.0   0.0 0.3  3.468E-6   139.6  35.3 3/17/05;9:04 PM;G34;1 afdemag schwehr
...
bp04-6gw-s1-094.0  40.0 0.4  1.083E-6   125.4  21.7 3/17/05;9:14 PM;G34;1 afdemag schwehr
bp04-6gw-s1-094.0  50.0 0.5  6.843E-7   110.4   6.0 3/17/05;9:15 PM;G34;1 afdemag schwehr



bp04-6gw-s1-094.0  10.0 0.4  2.210E-3   357.0  -2.1 3/21/05;3:13 PM;G34;1 irm schwehr x-in coil2



bp04-6gw-s1-094.0   5.0 0.4  1.983E-3   357.3  -1.6 3/21/05;3:18 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0   7.5 0.4  1.866E-3   357.5  -1.7 3/21/05;3:20 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0  10.0 0.4  1.763E-3   357.4  -1.7 3/21/05;3:21 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0  15.0 0.4  1.588E-3   357.5  -1.6 3/21/05;3:23 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0  20.0 0.4  1.437E-3   357.5  -1.8 3/21/05;3:24 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0  30.0 0.4  1.195E-3   357.6  -1.8 3/21/05;3:26 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0  40.0 0.4  1.006E-3   357.8  -1.9 3/21/05;3:27 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0  50.0 0.4  8.581E-4   357.6  -1.9 3/21/05;3:29 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0  60.0 0.4  7.409E-4   357.5  -2.1 3/21/05;3:30 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0  80.0 0.4  5.720E-4   357.5  -2.0 3/21/05;3:32 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0 100.0 0.4  4.577E-4   357.5  -2.3 3/21/05;3:33 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0 120.0 0.4  3.763E-4   357.6  -2.1 3/21/05;3:35 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0 150.0 0.4  2.915E-4   357.3  -2.3 3/21/05;3:36 PM;G34;1 afdemag-irm schwehr
bp04-6gw-s1-094.0 180.0 0.4  2.320E-4   357.5  -2.2 3/21/05;3:38 PM;G34;1 afdemag-irm schwehr

This is simple but handy command to add LoginItems (items that are
executed after the user logs in) via the command line using the
default tool. To add a normal startup item, use this syntax: 



  defaults write loginwindow AutoLaunchedApplicationDictionary \
  -array-add 'HidePath\
  /path/to/item'



Of course, replace /path/to/item with the absolute path to whatever it
is you want to open. Also, if you want the opened thing to hide itself
when it opens, just change the word false, after the Hide key, to
true. That's all there is to it.



Caution: If you form this command incorrectly, it's
possible you could overwrite all of your login items -- backup the
loginwindow.plist file before starting -- it's in your user's
Library/Preferences folder 

I thought I'd add some comments on this thread. First off we haven't
made an official port of Isis 3 to MacOS X and the post by Kris is in
regards to Isis 2. We are planning to have a fully native port for
Isis 3 completed before October 2005. In terms of dependencies, we
use:



qt 
image magick 
xerces 
xalan 
doxygen 
tnt/jama 
camgraph 
naif toolkit (cspice only) 
gmake 
g++/gcc 
rsync 



Isis 3 does not have any proprietary software so that shouldn't be a
concern and we hope to eliminate camgraph and xerces by using
equivalent functions in qt (although I can't say when this will
happen).



Since I'm Mac-illiterate I can't really weigh in on fink, although I
suspect we will not use it in the port. However, to me it sounds like
all you wanted was a network accessable tarball of our source
tree. This is something that might be easily done on our part. I'm a
little leary because we do have a required data area and it is quite
large. I think to house both rsync'able and tarballs of the same data
might be questionable.



This could be addressed in the make system for Isis 3. I'm hoping that
in the future, we can integrate the selection and installation of the
data (base system and mission specific) through make. This, along with
the tarball of the source, which includes the make files, might be
just what you need to build your fink files.



In your case, fink would grab the source tarball and execute the make
command to build Isis 3 binaries and download the base data area. Then
allow the user to choose which mission-specific data areas to make.



If this scenario might work for you please let us know. 



Cheers, Jeff Anderson

  Agile Testing with Python Test Frameworks
  matplotlib - from brain surgery to rocket science
  Scripting the Mac with Python
  pyblosxom: A microkernel approach to blogging
  A Python Preprocessing Framework for Hydrologic Modeling

   bp04-5gw-s2-024
   bp04-5gw-s2-028
   bp04-5gw-s2-034
   bp04-5gw-s2-124



   bp04-5gw-s1-001
   bp04-5gw-s1-022
   bp04-5gw-s1-039



   bp04-1gw-s2-035
   bp04-1gw-s2-042
   bp04-1gw-s2-081
   bp04-1gw-s2-121



   bp04-1gw-s1-002
   bp04-1gw-s1-020
   bp04-1gw-s1-035

  12077 21 Mar 12:09 1W1-002.RAW
  12080 21 Mar 12:09 1W1-081A.RAW
  12077 21 Mar 12:09 1W1-121.RAW
  12087 21 Mar 12:09 1W1-121B.RAW
   5129 21 Mar 12:09 1W1-121C.RAW
  12074 21 Mar 12:09 NI-2-1.RAW

  2005-Mar-21-NI-2-1.raw
  bp04-1gw-s1-002.raw
  bp04-1gw-s2-081.raw
  bp04-1gw-s2-121-a.raw
  bp04-1gw-s2-121-b.raw
  bp04-1gw-s2-121-c.raw

  "Model 2900 ASCII Data File",7,-1,+2.000000E-01,+5.400327E+02, 2,
   +0.000000E+00, +1.000000E+02, +1.000000E+04, +1.000000E+04 ,
   +0.000000E+00, 0, 202, 404, +2.000000E-03, 16, +8.952734E+01,
   +5.400000E+02, -8.497925E+01, +2.475232E-01, +5.563772E+01, 3,
   "ni-2 -1", +0.000000E+00, +0.000000E+00, +0.000000E+00,
   -1.000000E+03, "03/21/2005  11:00", 0, 0, 0, 0

  +9.992000E+03,+1.756200E-03
  +9.975000E+03,+1.755900E-03
  +9.887500E+03,+1.756500E-03
  +9.788000E+03,+1.756800E-03
  +9.688000E+03,+1.757600E-03

   P3210028.JPG

  Tauxe, L., Pick, T., and Kok, Y.S., Relative paleointensity in
  sediments: a pseudo-Thellier approach, Geophys. Res. Lett., 22,
  2885-2888, 1995.

  21-Mar-2005 Sampling

This works with lambdas as well, for inline calculations. Here's a
switch statement that assigns to a variable in PHP:



switch ($value) {
    case 'a':
        $result = $x * 5;
        break;
    case 'b':
        $result = $x + 7;
        break;
    case 'c':
        $result = $x - 2;
        break;
}



And here's the equivalent code in Python:



result = {
  'a': lambda x: x * 5,
  'b': lambda x: x + 7,
  'c': lambda x: x - 2
}[value](x)

  cc -I/Users/schwehr/Desktop/su/src/../include
  -I/Users/schwehr/Desktop/su/src/../include/MGL -I/usr/X11R6/include
  -I/usr/X11R6/include -O3 -Wall -ansi -pedantic -D_POSIX_SOURCE
  -DCWP_BIG_ENDIAN trip.c -L/Users/schwehr/Desktop/su/src/../lib
  -L/usr/X11R6/lib -L/usr/X11R6/lib -lglut -lXmu -lXt -lSM -lICE
  -lXext -lXi -lX11 -lm -lGL -lGLU -lglut -ltrack -lpar -lcwp -lm -o
  /Users/schwehr/Desktop/su/src/../bin/trip -I/sw/include -L/sw/lib
  ld: multiple definitions of symbol _err /usr/lib/libm.dylib(err.So)
  definition of _err
  /Users/schwehr/Desktop/su/src/../lib/libpar.a(errpkge.o) definition
  of _err in section (__TEXT,__text) ld: multiple definitions of
  symbol _warn /usr/lib/libm.dylib(err.So) definition of _warn
  /Users/schwehr/Desktop/su/src/../lib/libpar.a(errpkge.o) definition
  of _warn in section (__TEXT,__text)

  cc -I/Users/schwehr/Desktop/su/src/../include
  -I/Users/schwehr/Desktop/su/src/../include/MGL -I/usr/X11R6/include
  -O3 -Wall -ansi -pedantic -D_POSIX_SOURCE -DCWP_BIG_ENDIAN trip.c
  -L/Users/schwehr/Desktop/su/src/../lib -L/usr/X11R6/lib
  -L/usr/X11R6/lib -lglut -lXmu -lXt -lSM -lICE -lXext -lXi -lX11 -lGL
  -lGLU -lglut -ltrack -lpar -lcwp -o
  /Users/schwehr/Desktop/su/src/../bin/trip -I/sw/include -L/sw/lib
  ld: warning multiple definitions of symbol _err
  /Users/schwehr/Desktop/su/src/../lib/libpar.a(errpkge.o) definition
  of _err in section (__TEXT,__text) /usr/lib/libSystem.dylib(err.So)
  definition of _err ld: warning multiple definitions of symbol _warn
  /Users/schwehr/Desktop/su/src/../lib/libpar.a(errpkge.o) definition
  of _warn in section (__TEXT,__text) /usr/lib/libSystem.dylib(err.So)
  definition of _warn

I am looking into adding ISIS to fink (Mac OSX packaging tool) before
the next Mars lander mission. The fink policy is to only allow systems
that can be built from source. Unfortunetely, the rsync distribution
mechanism makes in nearly impossible for fink to grab a snapshot of
ISIS. I would have to rsync the source myself and create my own
snapshot (which I would prefer not to do). Is there anyway to make
available on the web a gzip or bzip2 compressed tar archive of
upcoming releases in addition to rsync? Then fink could then do 



curl http://someusgsurl.usgs.gov/src/isis-3.1.0.tar.bz2 



This tar would just be all the sources and support files excluding the
very large mission datasets.



My goal with fink is to help create a complete planetary science
workstation. Any person on the science team can get a Mac laptop and
have as many of the mission tools as possible. This greatly reduces
the load on the flightops support staff and puts more power in the
hands of the science team members. I have also been trying to
accomplish the same for marine geology/shipboard operations.



See this page for some of the software I have been packaging: 



Maintainer=Kurt Schwehr



Thanks for you consideration, 
-Kurt Schwehr 

Hi Kurt... 



Adding ISIS to Fink is not feasible at the moment for the following reasons: 



ISIS is built entirely independant of the Fink environment. This is a
concious decision we made because we felt the Fink overhead was
significant and unnecessary (and we still feel that way).



There is some proprietary code used in ISIS, albeit a very small
number of routines, but proprietary none-the-less.



The effort required to make ISIS Finkable would be in addition to our
already preferred distribution method (rsync) and probably substantial
in comparison to our current development environment (you do realize
you are asking us to migrate development, or at least support, of Mac
ISIS to the Fink environment).



We have 3rd party software dependancies for the Mac that exist only in
binary form. We would like to take advantage of the availability of
binary versions of software where ever possible to minimize
support. These are, but not limited to:



  OpenMotif 
  A package called PGPLOT 
  GNU Fortran Compiler (g77) 



We have limited support staff and resources to support ISIS, let alone
support the Mac OS X platform.



Fink is a great tool to migrate Unix/Linux software to the Mac
platform, but the downside is that Fink software cannot run
independant of that environment. Our goal is to provide ISIS to the
widest community possible and minimize maintainence and installation
difficulties.



In my opinion, DarwinPorts (http://darwinports.opendarwin.org/)
provides more flexible (runs natively in the Mac environment) and
appealing (does not require the enduser to install anything) ISIS
software development support. With this approach, our ISIS developers
can install the necessary 3rd party software ISIS depends on and only
those software tools. We can then provide these dependancies (i.e.,
shared libraries) with the ISIS distribution. This scenario is
obviously directly in conflict with the Fink policy as you state.



At this time, we do have a consistant development and distribution
configuration for all operating systems we support (Linux, Solaris and
Mac OS X). In my opinion, adding Fink to this mix creates additional
overhead we cannot at this time support.
_________________
Kris Becker 
Computer Scientist 
Astrogeology Team 
U.S. Geological Survey

Hi Kris, 



Thanks for your reply. 



Here are some added some clarifications to what I meant in that last 
post. 



* First: The last thing I want to do is add more work to your load. 
I am offering to do the leg work for an info file. 



* 2nd: I am thinking long term here. I personally can not start 
working on this until I finish my PhD later this year. I ask that you 
consider allowing me to work on a fink info file sometime over the 
next two years before the 2007 mission. 



* This does not have to impact your current development and release 
mechanism. Fink packages generally use what ever a project releases. 
Changing the development methods for such a large project would be 
not a good idea. 



* I would be the one creating an info file to fink. That info file 
would take your source base as is. It is then up to me to create any 
patches and run any commands against that source base necessary to 
compile the program. 



* I was thinking that you could add a tar cfj isis-3.0.3.tar.bz 
ISIS_ROOT to your release process and maybe add an exclude list of the 
proprietary files so that tar skips them. Then, maybe we could get 
community support to create replacements for those missing functions 
and APIs if they are as few as you suggest. This could be done 
without involving the USGS. 



* Alternatively, I could create a fink info file that lives outside of 
the normal fink process that users place in their 
/sw/fink/10.3/local/main/sci directory. Then issues of licenses and 
proprietary code could be reduced. 



* As for dependencies, that should not be a problem. Fink has info 
files for all of what you mentioned (g77, openmotif, and pgplot). The 
fink community can work on getting them into the stable tree where the 
servers build binaries for them. 



* During MER operations, I noticed that there was a huge proportion 
Mac Laptops and many of those had fink. There were a few G5 Macs in 
flight ops this time and I think there will be many more Mac 
workstation setups for the 2007 mission. 



* Fink and darwinports do have some collaboration between projects. 
They definitely have a different style, but in the science teams I am 
around, the science end users seem to really prefer fink with the 
FinkCommander program to provide functionality over the base Mac OSX 
system. 



* Here is the complete list of current packages in fink: 



http://fink.sourceforge.net/pdb/list.php



And links to the ones you mentioned. 



http://fink.sourceforge.net/pdb/package.php/g77
http://fink.sourceforge.net/pdb/package.php/openmotif3
http://fink.sourceforge.net/pdb/package.php/pgplot



Please take your time thinking about this. I am not in any rush. 
Just wanted to plant the idea in your head. Feel free to ask me or 
anyone on the fink lists if you have any questions or thoughts. 



Sincerely, 
Kurt Schwehr 

  sudo defaults write \
  /Library/Preferences/SystemConfiguration/autodiskmount \
  AutomountDisksWithoutUserLogin -bool true

  sleep 5; ioreg -c IOHIDSystem | \
    perl -ane 'if (/Idle/) \
    {$idle=int((pop @F)/1e9); print $idle,"\n"; last}'

  I'm pretty sure these are Painted Lady butterflies (Vanessa
  cardui). They are very widespread around the world (not found in
  Antarctica or Australia). They can form large populations in Mexico
  that then migrate north in the spring. We had a big migration some
  years back (probably 8 or so) - lots of guts on car windshields,
  etc. Seems to me it was the same year we had really spectacular
  bioluminescent red tides...

  We looked up Guide to Butterflies of California and think that they
  are probably Vanassa annnabella, a race of Californian Painted Lady.
  They are not Monarchs.

  lrosenstein on Tue, Mar 15 '05 at 01:54PM



  RAW format captures all the information the camera has without any
  processing. Most cameras only capture one color channel per
  pixel. Producing even a 16-bit TIFF from that would require some
  processing in the camera. 



  You are right about the flexibility of TIFF, and in fact Adobe's new
  digital negative format is based on the TIFF standard.

   Jason's
   Becca's
   Kurt's

    depth = tau1 = tau2 = tau3 = []

#!/usr/bin/env python
import os	# os.remove()
import sys	# sys.exit()
import string
import sqlite	# pysqlite
import bpsio
import Gnuplot



def plot_susc(db_cx, filename, table, corenum, maxdepth):
    cu = db_cx.cursor()
    searchStr =  "SELECT depth,tau1,tau2,tau3 FROM " + table
    searchStr += " WHERE corenum=" + str(corenum) + " ORDER BY depth;"
    cu.execute(searchStr)



    depth = [];    tau1 = [];    tau2 = [];    tau3 = []
    for row in cu.fetchall():
        depth.append(row['depth'])
        tau1.append(row['tau1'])
        tau2.append(row['tau2'])
        tau3.append(row['tau3'])
    t1 = Gnuplot.Data(tau1,depth,with='lp')
    t2 = Gnuplot.Data(tau2,depth,with='lp')
    t3 = Gnuplot.Data(tau3,depth,with='lp')
    g = Gnuplot.Gnuplot()



    title = table + " core " + str(corenum) + " AMS tau123"
    g.title(title)
    g.xlabel("Tau (Sums to 1)")
    g.ylabel("Depth(cm)")
    g("set yrange [0:"+str(maxdepth)+"] reverse")
    g("set size ratio 2")
    g("set output '"+filename+"'")
    g("set terminal png size 320,480")
    g("set xtics 0.01")
    g.plot(t1,t2,t3)



if __name__ == '__main__':
    cx = sqlite.connect (bpsio.dbFileName);
    plot_susc(cx,"foo.png","ams_geo",1,200)

Distinctive Image Features from Scale-Invariant Keypoints



Lowe, International Journal of Computer Vision, 60, 2 (2004),
pp. 91-110.



Abstract
This paper presents a method for extracting distinctive invariant
features from images, which can be used to perform reliable matching
between different images of an object or scene. The features are
invariant to image scale and rotation, and are shown to provide robust
matching across a a substantial range of affine distortion, addition
of noise, change in 3D viewpoint, and change in illumination. The
features are highly distinctive, in the sense that a single feature
can be correctly matched with high probability against a large
database of features from many images. This paper also describes an
approach to using these features for object recognition. The
recognition proceeds by matching individual features to a database of
features from known objects using a fast nearest-neighbor algorithm,
followed by a Hough transform to identify clusters belonging to a
single object, and finally performing verification through
least-squares solution for consistent pose parameters. This approach
to recognition can robustly identify objects among clutter and
occlusion while achieving near real-time performance.

How to use your PowerBook G4 with the display closed

University of Washington



The most intense swarms of earthquakes detected in the last 10 to 12
years on the far edge of the Juan de Fuca plate could indicate the
eruption of magma from the seafloor or an underwater volcano. Between
50 and 70 earthquakes an hour, most of them small, were occurring  at
the end of February at a spot some 200 miles off the Canadian coast. 
...

  IVCON - 3D Graphics File Conversion

SRCS:=asc.cpp
SRCS+=ase.cpp
SRCS+=byu.cpp
SRCS+=dxf.cpp
SRCS+=gmod.cpp
SRCS+=hrc.cpp
SRCS+=iv.cpp
SRCS+=ivconv.cpp
SRCS+=main.cpp
SRCS+=obj.cpp
SRCS+=pov.cpp
SRCS+=smf.cpp
SRCS+=stl.cpp
SRCS+=tds.cpp
SRCS+=tec.cpp
SRCS+=tmat.cpp
SRCS+=tri.cpp
SRCS+=txt.cpp
SRCS+=ucd.cpp
SRCS+=utils.cpp
SRCS+=vla.cpp
SRCS+=wrl.cpp
SRCS+=xgl.cpp

OBJS:=${SRCS:.cpp=.o}

TARGETS:=ivconv mesh
CXXFLAGS:= -O3 -funroll-loops -fexpensive-optimizations -DNDEBUG -ffast-math -mpowerpc

targets: ${TARGETS}

ivconv: ${OBJS}
	g++ $^ -o $@ ${CXXFLAGS}

mesh: mesh.o
	g++ $^ -o $@ ${CXXFLAGS}

clean:
	rm ${OBJS} ${TARGETS}

     ivconv foo.wrl foo.obj



initializing...Bad data VertexProperty
  Bad data texCoord
  Bad data normalIndex
  Bad data textureCoordIndex
  Bad data -1
  
  DATA_REPORT - The input file contains:
  
    Bad data items             5
    Text lines                 142514
    Text bytes (binary data)   0
    Colors                     0
    Comments                   1
    Duplicate points           0
    Faces                      0
    Groups                     0
    Vertices per face, maximum 0
    Line items                 0
    Points                     19748
    Objects                    0
  
  DATA_CHECK - Data checked.
  
  EDGE_NULL_DELETE:
    There are a total of 0 edges.
    Of these, 0 were of zero length, and deleted.
  
  FACE_AREA_SET:
    Minimum face area is 0.000000
    Maximum face area is 0.000000
  
  FACE_NULL_DELETE
    There are a total of 0 faces.
    Of these, 0 passed the order test.
  
  COR3_RANGE - Data range:
  
     Minimum   Average   Maximum  Range
  
  X  -15.038561 -6.743375 -2.956082 12.082479
  Y  1.490623 3.606597 8.242425 6.751802
  Z  -0.457958 1.089934 2.803719 3.261677
  
  OBJ_WRITE - Wrote 19754 text lines.

#Inventor V2.1 ascii






Separator {



  Texture2 { filename "foo.png"  }
  ShapeHints {
    vertexOrdering COUNTERCLOCKWISE
    shapeType UNKNOWN_SHAPE_TYPE
    creaseAngle 1.5
  }
  Material {
    ambientColor 1 1 1
    diffuseColor 1 1 1
    specularColor 0 0 0
    emissiveColor 0 0 0
    shininess 0
    transparency 0
  }
  IndexedTriangleStripSet {
    vertexProperty 
    VertexProperty {
      vertex [ -9.5078192 4.1908059 0.080789998,
          -9.5088491 4.2086911 0.096816003,
          -9.515564 4.1935291 0.096675001,
...
          -3.3741801 1.669412 0.46248901,
          -3.377382 1.663372 0.46251801,
          -3.3802321 1.657196 0.462392,
          -3.3816769 1.650483 0.46164301,
          -3.383647 1.643977 0.461128 ]
      normal [ 0.84313971 -0.27994934 0.45906833,
          0.76509589 -0.38959566 0.51268256,
          0.78889918 -0.27429348 0.54991013,
          0.78889918 -0.27429342 0.54991019,
          0.83235496 -0.18904907 0.52100438,
...
          0.31228593 0.19732746 -0.92926818,
          0.53384936 -0.030668387 -0.84502321,
          0.26931736 -0.21443249 -0.93887532,
          0.53384936 -0.030668389 -0.84502321,
          0.57270825 -0.1091051 -0.8124662 ]
      texCoord [ 0.78613299 0.97070301,
          0.78125 0.96582001,
          0.78613299 0.96582001,
          0.79101598 0.96582001,
          0.38085899 0.96582001,
...
          0.81054699 0.013672,
          0.81542999 0.013672,
          0.82031202 0.013672 ]
      orderedRGBA [  ]
      normalBinding PER_VERTEX_INDEXED
      materialBinding OVERALL



    }
    coordIndex [ 19747, 19691, 19746, -1, 19691, 19690, 19746, -1,
        19745, 19689, 19744, -1, 19689, 19688, 19744, -1,
        19744, 19687, 19743, -1, 19743, 19687, 19686, -1,
        19743, 19686, 19742, -1, 19741, 19685, 19684, -1,
        19741, 19684, 19740, -1, 19740, 19684, 19683, -1,
        19740, 19683, 19739, -1, 19739, 19683, 19682, -1,
        19737, 19681, 19736, -1, 19681, 19680, 19736, -1,
        19736, 19680, 19679, -1, 19736, 19679, 19735, -1,
...
        40, 39, -1, 39, 38, 36, 37, -1,
        28, 27, 26, 25, -1, 19, 17, 18,
        16, -1, 16, 17, 15, -1, 14, 13,
        12, 11, -1, 12, 11, 10, 9, -1,
        9, 7, 8, 6, -1 ]
    normalIndex [ 68580, 68578, 68579, -1, 68394, 68576, 68577, -1,
        68572, 68388, 68571, -1, 68387, 68570, 68569, -1,
        68568, 68378, 68567, -1, 68566, 68376, 68565, -1,
        68564, 68372, 68563, -1, 68558, 68559, 68560, -1,
        68558, 68556, 68557, -1, 68553, 68554, 68555, -1,
        68553, 68552, 68551, -1, 68551, 68550, 68357, -1,
        68546, 68353, 68545, -1, 68353, 68543, 68544, -1,
...
        45, 43, 44, 41, -1, 28, 25, 27,
        26, -1, 26, 25, 21, -1, 20, 18,
        19, 15, -1, 17, 15, 16, 13, -1,
        12, 9, 11, 10, -1 ]
    textureCoordIndex -1



  }
}

 ivconv foo.wrl foo.obj
initializing...
DATA_REPORT - The input file contains:



  Bad data items             0
  Text lines                 163654
  Text bytes (binary data)   0
  Colors                     0
  Comments                   1
  Duplicate points           0
  Faces                      37019
  Groups                     0
  Vertices per face, maximum 3
  Line items                 0
  Points                     19748
  Objects                    0

   Becca's pic

Visualization tools facilitate geological investigations of Mars
Exploration Rover landing sites



Kurt D. Schwehr, Carrie Nishimura, Catherine L. Johnson, Debi L. Kilb,
Atul Nayak



Publication:



Proc. SPIE Vol. 5669, p. 135-145,  Visualization and Data Analysis
2005; Robert F. Erbacher, Jonathan C. Roberts, Matti T. Gröhn, Katy
Börner; Eds.



Publication Date: Mar 2005

Designing visualization software for ships and robotic vehicles



Kurt D. Schwehr, Alexander Derbes, Laurence Edwards, Laurent Nguyen,
Eric Zbinden



Publication:



Proc. SPIE Vol. 5669, p. 226-237, Visualization and Data Analysis
2005; Robert F. Erbacher, Jonathan C. Roberts, Matti T. Gröhn, Katy
Börner; Eds.



Publication Date: Mar 2005

  http://www.seismology.harvard.edu/~becker/igmt/igmt_v1.2-20040303.tar.gz

1. Put out two i bolts on the deck far enough apart to fit the whole box core frame.
2. Transfer to under the A-Frame
3. Strap it down with ratchet strap.
4. Set the top door with pins
5. Tie the ropes from bottom doors to the loops with light string
6. Pull surgical tubing over trigger
7. Attach a frame winch to red O link using a shackle
8. Attach tag lines through the two rope loops attached to handles and clip one end to the aft cleets of the A-Frame
9. Remove rachet strap.
10. (Leave the life lines in place -- back railing)
11. Lift box core up so that the weights are up and the core is off the deck
12. Pull the two flagged safety pines
13. A-frame out
14. lower winch
15. When box corer is in the water, remove tag lines.
16. Record GPS time and location
17. lower box core to 50 meters above the sea floor at 25 m/sec
18. then 20 m/sec to the bottom
19. let out 3 extra meters of line to let the core get into the mud.
20. record GPS time and location
21. life to 50 m/sec below the surface
22. up to the top at 15 m/s
23. Use two recovery poles to grab the two garden hose covered loops.
24. Pull the lines into the ship and ditch the recovery poles.
25. Raise the box core up and over the life lines using the crane and the a-frame at the same time.
26. Place the box core just above the deck.
27. Put the two safety pins in the sides.
28. Then lower the frame onto the deck.
29. Secure it with a rachet strap and remove the winch wire.
30. Secure the winch wire.
31. Lift up the top door and secure it with the pin.
32. Siphon the water off with some flexible tubing. Need 6 feet of tubing to do this easily.
33. (FIX: insert tube prep info above.)
34. Push core liner tubes in the mud, down to the bottom.

Officials with the San Diego Fire Department told NBC 7/39 that
lifeguards and a city geologist had been called to the scene after the
hillside gave way about ½ mile north of Scripps Pier.

  My gmtplus web page

  Runnin X11

  sudo emacs /sw/etc/fink.conf
  # Add unstable/main and unstable/crypto to Trees
  fink index
  fink selfupdate
  sudo apt-get install emacs21  gnuplot gv wget-ssl doxygen gsl gengetopt imagemagick
  sudo apt-get install qt3
  fink install postgresql73-ssl  python24 python24-socket-ssl scietificpython-py24 sqlite
  fink install density # This is a couple hours
  fink install postgresql73-ssl
  fink install sqlite
  fink install python24
  fink install python
  fink install pysqlite-py24  
  fink install sqlite3
  fink install biggles-py24 f2py-py24 gnuplot-py24 numarray-py24
  fink install proj
  fink install gsl
  fink install gdal
  fink install mbsystem
  fink install pmag
  fink install tksu  # you will have to answer some questions for it to build.
  #fink install weka  # Errr... this is currently broken.  Sorry.
  fink install xtermcontrol g3data
  fink install pdflib-py24 
  fink install density soxt3
  fink install scipy-py24 scientificpython-py24
  fink install pygsl-py24
  fink install tksu # brings cwp-su (seismic unix)
  fink install twisted-py24
  fink install wxpython-py24
  fink install pyxml-py24
  fink install rpy-py24
  fink install octave # Very much link matlab
  fink install gdl # Very much like IDL
  fink install matplotlib-py24
  fink install ipython-py24
  fink install povray graphviz



  # finish up...
  fink clean
  fink scanpackages

  The bright patch of disturbed soil, dubbed "Paso Robles," has the
  highest salt concentration of any rock or soil ever examined on
  Mars. Combined information gained from inspecting it with Spirit's
  three spectrometers and panoramic camera suggests its main ingredient
  is an iron sulfate salt with water molecules bound into the
  mineral. The soil patch is also rich in phosphorus, but not otherwise
  like a high-phosphorus rock, called "Wishstone," that Spirit examined
  in December. "We're still trying to work out what this means, but
  clearly, with this much salt around, water had a hand here," Squyres
  said.

#!/usr/bin/env python
import Gnuplot
g = Gnuplot.Gnuplot()



x = [1,2,3,4,5]
y = [1,2,2,3,2.5]
gData = Gnuplot.Data(x,y,with='lp')
g('set terminal pdf')
g("set output 'foo.pdf'")
  
g.plot(gData)

#!/usr/bin/env python
import Gnuplot



g = Gnuplot.Gnuplot()
g.title('Plot 1')
g("set xlabel 'yo x label'")



x = [1,2,3,4,5]
y = [1,2,2,3,2.5]
gData = Gnuplot.Data(x,y,with='lp')
g.plot(gData)

   .ddi     ---  depth dec inc
   .di	    ---  dec inc
   .dt      ---  depth and a text string
   t123     ---  for AMS Tau 1,2, and 3
   f12-f23  ---  F test
   susc     ---  Bulk susceptibility
   etc.

  locate .ttf  | grep '\.ttf$' | less

#!/usr/bin/env python
import Image, ImageDraw, ImageFont
im = Image.new("RGB",(400,400),"white")
draw = ImageDraw.Draw(im)



font = ImageFont.truetype("/usr/X11R6/lib/X11/fonts/TTF/luxirb.ttf",30)



draw.text((10,100),"hello", font=font, fill="red")
im.show()

  s = start, Indx = index, Trmt = treatment level



  samplename type1 s1Indx s1Trmt e1Indx e1Trmt type2 s2Indx s2Trmt e2Indx e2Trmt



  1gws2-030  line  1      5.0    4      15.0   plane 5      20     9      60
  1gws2-033  both  0      0.0    5      20.0   line  3      10     10     80

  samplename trmtIdNum type startIndx startTrmt endIndx endTrmt
  1gws2-030  0         line   1          5.0       4      15.0
  1gws2-030  1         plane  5         20.0       9      60.0
  1gws2-030  2         line   0          0.0      -1      -1.0

  tKeys=('er_specimen_name','trmtIdNum','type','startIndx','startTrmt','endIndx','endTrmt');
  t=[]
  t.append(('1gws2-030', 0, 'line',  1,   5.0,  4,  15.0))
  t.append(('1gws2-030', 1, 'plane', 5,  20.0,  9,  60.0))
  t.append(('1gws2-030', 2, 'line',  0,   0.0, -1,  -1.0))

    bp04-1gw-s2-030

  measurement_step_min
  measurement_step_max
  specimen_calculation_type = l or p (but I will make them line or plane)
  er_specimen_name
  specimen_comp_name

def testSqlInsertStrFromDictTwo(self):
    """Try two values"""
    aDict = {'one':1,'two':2.}
    expectedResult="insert into myTable (one,two) values (1,2.0);"
    got=sqlInsertStrFromDict("myTable",aDict)
    print got
    self.failUnless(expectedResult==got)

  insert into myTable (two,one) values (2.0,1);

#!/usr/bin/env python
"""LIST VERSION"""



import unittest



def sqlInsertStrFromList (table,aList):
    """ Take a list and make an insert string"""
    ins = "insert into " + table + " ("
    first=True
    for pair in aList:
        key = pair[0]
        if first: first=False
        else:     ins+=","
        ins+=str(key)
    ins += ") values ("
    first=True
    for pair in aList:
        value = pair[1]
        if first: first=False
        else:     ins+=","
        ins+=str(value)
    ins += ");"
    return ins



class SqlTests(unittest.TestCase):
    def testSqlInsertStrFromListOne(self):
        """The simplest case I can come up with.  Table field called 'one' with value of the number 1"""
        aList = [('one',1)]
        expectedResult="insert into myTable (one) values (1);"
        got=sqlInsertStrFromList("myTable",aList)
        #print got
        self.failUnless(expectedResult==got)



    def testSqlInsertStrFromListFloat(self):
        """Try a float"""
        aList = [('two',2.)]
        expectedResult="insert into myTable (two) values (2.0);"
        got=sqlInsertStrFromList("myTable",aList)
        #print got
        self.failUnless(expectedResult==got)



    def testSqlInsertStrFromListTwo(self):
        """Try two values"""
        aList = [('one',1),('two',2.)]
        expectedResult="insert into myTable (one,two) values (1,2.0);"
        got=sqlInsertStrFromList("myTable",aList)
        #print got
        self.failUnless(expectedResult==got)



    def testSqlInsertStrFromDictOne(self):
        """Will a dict work too?  It seems to!"""
        aDict = [('one',1)]
        expectedResult="insert into myTable (one) values (1);"
        got=sqlInsertStrFromList("myTable",aDict)
        #print "dict one: ", got
        self.failUnless(expectedResult==got)






def main():
    unittest.main()



if __name__ == '__main__':
    main()

   # The simplest example... localhost is the same as your current machine
   ssh localhost ls



   # now make it a remote machine
   ssh pixie ls



   # if you are having name resolution troubles where it says
   # "who the heck is pixie"
   ssh pixie.ucsd.edu ls



   # You need quotes if the command had any spaces
   ssh pixie "ls -l"



   # What if you need to switch users?
   ssh smith@pixie "ls -la"



   # What if you are not sure that you are getting to the right host?
   ssh pixie hostname
   ssh pixie "uname -a"
   ssh pixie pwd



   # So you want to backup the etc directory on a remote machine to a
   # tar file and copy it to your current computer?
   ssh smith@pixie "tar cf etc.tar /etc"
   ssh smith@pixie "bzip2 -9 etc.tar"
   scp smith@pixie:etc.tar.bz2 .
   tar tfjv etc.tar.bz2

#!/usr/bin/env python



def sqlInsertStrFromDict (table,aDict):
    """ Take a dict and make an insert string"""



    ins = "insert into " + table + " ("
    first=True
    for key in aDict.keys():
        if first: first=False
        else:     ins+=","
        ins+=str(key)
    ins += ") values ("
    first=True
    for value in aDict.values():
        if first: first=False
        else:     ins+=","
        ins+=str(value)
    ins += ");"
    return ins



import unittest
class SqlTests(unittest.TestCase):
    def testSqlInsertStrFromDictOne(self):
        aDict = {'one':1}
        expectedResult="insert into myTable (one) values (1);"
        got=sqlInsertStrFromDict("myTable",aDict)
        print got
        self.failUnless(expectedResult==got)



def main():
    unittest.main()



if __name__ == '__main__':
    main()

import rmag_ams
file = rmag_ams.K15file()
file.open("antarctica.k15","r")
# Write out all the sample entries
file.writeMagIC("antartica.samples.magic")



# get one sample
sample = file.getNextK15()



new = rmag_ams.K15()
new.sampleholder = 4.75
new.K[0] = 1.077E+2
new.K[1] = 1.057E+2
....
new.K[13] = 1.076E+2
new.K[14] = 1.071E+2



new.write("measurements.k15")

file = rmag_ams.KnFile(numPos=9)

  "Now the reason for this is obvious," Gellert told (New Scientist. "We
  found proof that we unintentionally swapped both instruments." Spirit
  is carrying the spectrometer destined for Opportunity, while
  Opportunity is in possession of Spirit's.

Small problems lead to medium sized problems which lead to big
problems. Example: In the 1970's the NRC was similar to the Department
of Transportation or FAA (pre 9/11) in that their job was to help
facilitate the nuclear economy, not to beat down offenders. In the
early 70's plant managers at a nuclear power plant in Alabamba, Browns
Ferry Nuclear Power Plant, received reports that their insulation
connecting to a cable room was not in accordance with fire
specifications (small problem). Since this was not a significant
problem, managers ignored it. Later workers testing the air-tightness
of the room failed to follow the correct procedures by using candles
to check the air tightness (if the flame is deflected, air is moving
in that direction--small problem). Managers were aware but dismissed
the problem. During testing for air leaks the flame of a candle was
sucked into insulation and a fire erupted. The cable run that caught
on fire was non-redundant and carried all of the control features for
two nuclear reactors. Control of the reactors was lost and reactor
safety was severly compromised. Problems that occurred included that
the operators of the reactors did not know how to properly respond to
this causality (including attempts to put out a large class A fire
with portable CO2 extinguishers). Over $100 million in damages
occurred, but the reactors narrowly escaped tragedy (medium sized
problem). This occurred in 1975 and the NRC mostly covered up the
problem. No congressional hearing were held. No significant corrective
actions were issued and review of the ability of the operators to
fight a causality at a nuclear power plant was not reviewed. Fast
forward four years and we arrive at Three Mile Island (big problem),
where many of the shortcomings of the Brown's Ferry Plant and of the
NRC being able to regulate and control the nuclear industry were
exposed. 

La Jolla

  http://a9.com/schwehr.org
  http://www.alexa.com/data/details/?url=schwehr.org