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.
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.
Got the sensor resistance converted to voltage. A 1k ohm resistor seems to work best, since I want most of the sensitivity to be light pressure. Next, 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.
Uploaded new VSS jars to the server to see if I can track down the problem with large(?) files.
Backups
Added more logging, but it turns out that the problem was in the creation of the table with reserved column names (“index”, etc);
Checked in scriptengine and JavaUtils. Also created an “Eclipse Server Projects” and checked the Vis3Testbed and VSSTestbed projects into it.
2:00 – 4:30 FP
Brian came over last night and we were able to load up his laptop with the drivers and software and run examples. At this point, we’re looking at three things to study with the rig:
What is/are the best frequencies for spatial orientation (position and distance) using these actuators?
What happens with speed and accuracy when there are more than one signal?
Do 7 actuators work better than 4?
We’re in the process now of writing up the test plan. In the meantime, I’m now going to try to adapt the Audio2X software to replace the synthesizers and use a Phidgets 1019 to replace the Ardino of the previous telepresence test rig. Once that’s done, then I’ll add in the Phantom. For reference, here’s a video of the first version running:
And here’s a picture of the latest interface that will be attached to the Phantom:
To move this along, I’ve brought a small pile of electronics in from home. Tomorrow’s goal is to make sure that I can connect to the interface board. Once that’s working I need to hook up the sensors from the old prototype (note! Bring in crimping pins for female DB15 connector!).
Deployed new FA and RA. Next week we’ll change the links on the VizTool webpage so that the primary links are to the new tools
Discussed how to handle the column width issue with Dong. It’ll be a method like ‘width = getColumnWidth(minWidth, numColumns, parentWidth);’ that’s called on resize().
Looking into the issue where large tables appear not to be inserted into the vis2 database. And of course, everything is working fine here. Need to add some more logging, I guess.
You must be logged in to post a comment.