[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Meeting Friday



As "usual" (?) we'll be having a meeting on Friday at 1pm.

Emily and I have been working on understanding where the missing link
is between the rest of the pipeline (which ends in walls) and the
BaseGen code.  We've managed to discover where most of the inputs to
BaseGen come from, but it appears to utilize a directory full of files
(mit/src/BaseGen/Input/Bldg) which we cannot discover the source of. 
These contain transformed portal data such as almost output by walls
(it's not transformed coming out of walls).  How are these files
produced?  Is this the missing link that needs to be added to include
the BaseGen code into the overall pipeline?

So Emily has been thinking about how apply Vitaly's fixes to the
building transforms to the "spreadsheet".  From looking through the
code, we think that this means adding some code around the line in
pipeline.py that reads "# FIXME insert vitaly's transforms".  In order
to do so, Emily needs to write some Python code that reads
run/input/mit_building_corrections.xml and applies these deltas to the
"buildings" list produced by strip_spreadsheet.  The plan is for Emily
to work on understanding XML parsing in Python for Friday, and then
work on applying it to solve the given problem.

Ben's hacking on getting the Java SDK installed on Glint.  Michael, is
it already installed?  If so, I can't find it.  I, however, need root
in order to complete the install.  If you have root and want to do it
yourself, there are a pair of tarballs in /scratch/benmv/ which should
do the trick.  If not, let me know the root password in some secure
manner and I'll take care of it.

-Ben