8:00 – 10:00 SR

• Backups
• Sent a note to the system security folks asking to clarify what I was responsible for installing on my virtual server.
• Need to do a status report for Tangie
• Got tooltips for RA/FA
• Meeting with Chris and Lenny. Mostly we discussed the issue of bad data in Cognos.

10:00 – 4:00

• Integrating Phantom
• Code is in and compiling, but there are mysterious errors:
• 
• 
• I think I need a more robust startup. Looking at more examples….
• Hmm. After looking at other examples, the HD_TIMER_ERROR  problem appears to crop up for anything more than trivially complex. Since both programs seem to run just fine by themselves, I’m going to make two separate executables that communicate using Named Shared Memory. Uglier than I wanted, but not terrible.
• Created a new project, KF_Phantom to hold the Phantom code
• Stripped out all the Phantom (OpenHaptics) references from the KF_Virtual_Hand_3 project;
• Added shared memory to KF_Phantom and tested it by creating a publisher and subscriber class within the program. It all works inside the program. Next will be to add the class to the KF_VirtualHand project (same code, I’m guessing? Not sure if MSVC is smart enough to share). Then we can see if it works there. If it does, then it’ll be time to start getting the full interaction running. And since the data transfer is essentially memcpy, I can pass communication objects around.

8:00 – 10:00 SR

• Backups
• Need to write up monthly status reports for Tangie

10:00 – 4:30 FP

• Continue integrating Phantom into testbed
• Need to bring headphones back for microphone
• Spent most of the day trying to figure out how to deal with geometry that has to be available to both the haptic and graphics subsystems. The haptics subsystem has to run fast – about 1000hz and gets its own callback-based loop from the HD haptic libraries. The graphics run as fast as they can, but they get bogged down. So the idea for the day was to structure the code so that a stable geometry patch can be downloaded from the main system to the haptics subsystem. I’m thinking that they could be really simple, maybe just a plane and a concave/convex surface. I started by creating a BaseGeometryPatch class that takes care of all the basic setup and implements a sphere patch model. Other inheriting classes simple override the patchCalc() method and everything should work just fine. I also built a really simple test main loop that runs at various rates using Sleep(). The sphere is nice and stable regardless of the main loop update rate, though the transitions as the positionis updated can be a little sudden. It may make sense to add some interpolation rather than just jumping to the next position. But it works. The next thing will be to make the sphere work as a convex shape by providing either a flag or using a negative length. Once that’s done (with a possible detour into interpolation), I’ll try adding it to the graphics code. In the meanwhile, here’s a video of a dancing Phantom for your viewing pleasure:

8:00 – 10:00 SR

• Backups
• Got the development environment including Mike’s old workspace set up on the integration machine
• Was able to run the PKI test code and get good results. Next is to attach to the server and step through the filter to see what’s going on.

10:00 – FP

• Finish getting the Phidgets code working in KF_Hand_3 – done
• Start to add sound classes – done inasmuch as sounds are loaded and played using the library I wrote. More detail will come later.
• Start to integrate Phantom. Got HelloHapticDevice2 up and running again, as well as quite a few demos

8:00 – 10:00 SR

• Backups
• Tried to do some training, but the servers were undergoing maintenance.

10:00 – FP

• Brought in my fine collection of jumpers and connectors. Next time I won’t have to build a jumper cable…
• Built the framework for the new hand test. The basic graphics are running
• Added cube code to the FltkShaderSupport library
• Next, I’m going to integrate the Phidget sensor code into the framework, then hook that up to sound code.
• Had Dong register for Google’s Ingress, just to see what’s going on.
• Loaded in the Phidgets example code and the library that works is the x86 library. Using the 64bit library results in unresolved externals errors.
• There are a lot of straight C examples. Just found the C++ class examples simple.h and simple.cpp.

SR 8:30 – 10:30

• Backups
• Found the source of the doubleing and tripling bug. New lines for the same values are being ingested. There needs to be a conflict resolution screen that is part of the ingest process.
• Need to escape reserverd characters from query builder
• Need to ensure that reserved words aren’t used in export to viztool.

FP 10:30 –

• Prepping for demo
• Fixing cable that broke on Friday
• Got a lot of new parts in over the weekend including probes, cable, and sensors
• Nice meeting with Dave Coleman. No concrete results (more meeting[s] required), but I think it went well.

SR 8:00 – 10:00

• Found some query builder bugs
  • “GROUP BY” is getting stripped out
  • Two requisition ID’s is confiusing
  • If you select new items after an modifier, incorrect SQL is generated
  • Need to be able to group similar rows (i.e. roll up all rows with the same req id)
• There seems to be a math error on the “Budget Information” panel. Lenny found that on project 236, there are three EA lines (and nothing else). One line is correct, one line is doubled, and one line is tripled.
• Backups
• Installed Eclipse 4.2 and Mikes old workspace on the server.

FP 10:00- 4:00

• Today, the goal is to build a circuit with three channels that connects to the Phidgets voltage sensor. The only thing I’m wondering is if I’ll get the resolution with the voltage range I’m getting – Zero to about 2.5 volts. I’m estimating that I should get about 1500 – 3000 steps out of that, assuming -30v to +30v is resolved to a (unsigned?) 16-bit int.
• Done!