[Hola-hackers] defedge added, reports changed

[Philip F. K. <fl...@mr...>]

Hey,

[Mike -- Matt & I have agreed to start emailing each other upon cvs 
checkins with a summary of changes; would you like to be cc'd so that you 
can see what is changing in the msspd code base?]

I've added a routine called defedge_z that displaces an area near the top z
edge (right now chosen to be equal to freeze_dz). This is, I know, similar
to squ_str; but it can shear in x and y as well as strain.  I also didn't
want to mess with something that is in use; at some later point I'd like to
reduce the number of routines that do this or something similar (defedge,
squ_str, strain, dynm_squ_str do not share any code yet all do "strain &
other stuff").  I'm also still not entirely clear on what the 'right thing'
to do with the system/crystal/node boundaries is (that is, when and which
ones should be grown; and how to handle shear).

I also added code to reports.c that will dump the crystal state to a
mathematica file so I could do some analysis on it.

In both cases scripts without the new parameters work fine (that is, the 
new stuff isn't called unless its parameters are present).  tin_white, 
silicon_sw, and drag all seem to run same as before.

There are, in addition, copious changes to the py and observer stuff, which
are both in the "too useful to be pretty" state.  If you're interested in
using these let me know and I can fix them up.

flip