8:00 – 4:30

• Sent out an announcement on new VISIBILITY capabilities
• Found some bugs in scripting. Fixed
• Loading scripting onto Laureldemo for integration with Dong’s code – done. Updated Data Navigator too. Need to have Tom put up the documentation
• Need to write a SOLR generator to show bridging capability to VISIBILITY
• Need to handle JVM error for things like infinite loops. Not sure how to handle that yet
• Autoindent is still buggy – fixed

8:00 – 4:00

• Still need to allow alert creation and deletion on the AlertServlet.
• Delete in
• Add in – had to make it more restrictive about accepting uids
• List in
• Show single alert in

7:30 – 4:00

• Rolled in Mikes changes – everything seems to be working fine – until we have a user touch things, of course.
• Worked on the properties a bit for scripting – databases are now actually listed in the properties files. It’s good enough to bring in at this point to see how it behaves running on onsite servers.
• Need to write up “This visibility Story” – done
• Still need to allow alert creation and deletion on the AlertServlet.

• Was able to get Glut running by making it the main executive
• Transposed whetstone bridges to a circuit board.  Had to start over cause the soldering was too messy on first attempt.  Glad I waited for Phil to bring in the other solder because it actually melts at the right temperature.
• Set up everything to attach to the new board both bridges work great.
• Somehow the strain gauge is touching the bar again despite many tests to make sure this wasn’t happening before.  Might be do to the rust or whatever the yellow stuff is factor.
• The other stick I made is still testing properly but needs a shim.
• I think I fixed a problem when the input stick was still sending go commands to the other one when it was in a stopped state due to a collision.  Can’t know for sure with only one stick though.

7:30 – 2:30

• Clean up and test alert adding in jython – done
• Start on the AlertServlet – particularly how to add, clear, and delete(?) an alert RESTfully. Started. Servlet runs and posts the alert list xml, but doesn’t perform any operations
• 1:00 meeting at Anne’s – nope, postponed

Tuesday:

• Shortened signal wires to strain gauges so more of the wire is shielded
• Strain Gauge came loose on second sensor stick had to redo it.  Did not use enough silicone to hold the connections in place
• Found out glut is event based.  Need to either use standard GL libraries or freeglut.

Wednesday:

• Finished repairing second sensor stick
• Started putting the whetstone bridges on a board so I wouldn’t have to worry about the wires coming loose all the time
• Had trouble finding GL Headers and libraries.  Found out that they are in the Windows SDK.
• Cold solder doesn’t conduct well.  Connections need to be well seated on the board.
• Saw that freeglut is still supported and was updated as of November 2009.  Going to give it a try since I am having trouble with the standard GL libraries and from the description freeglut is designed to replace glut because glut is no longer supported and outdated.  Freeglut supposedly can be used in a non event based way.

7:30 – 3:30

• Logged into LDAT(2) successfully. Asked for a tutorial/walkthough, and who to talk to for direct JDBC access. I may use the scripting service to publish that data
• More alerting. Need to do the following
• Add an alert in the Alert Manager
• Clean up and test alert adding in jython
• Start on the AlertServlet – particularly how to add, clear, and delete(?) an alert RESTfully

7:30 – 3:30

• Have you done your taxes yet?
• Meeting with Jim Murphy & Trish(?) Went through Don’s system pretty thoroughly.
• Added links to help in vis2
• Add Alert panel to webbapp – started
• Add code hints to scriptFacades
• Start on Alert Servlet

7:30 -3:30

• There is some new data in the employees tables on site. With some poor picking, there could be some real combinatorial problems. Not sure what to do about that right now. Maybe a warning (“Warning, this may result in a very slow return, do you wish to…?) Dunno.
• Working on adding alerts. Can create an alert and add it into the db trough ScriptObject. Tomorrow, I need to be able to pull out the list of alerts for ScriptObject, and start on the REST component. Last thing will be to add interaction with Python.
• Speaking of which, I really need syntax coloring and code completion in the “IDE”. Found some syntax coloring that might be usable on sorceforge. Nothing on code completion.

• OpenGL works in a similar fashion to our RCS system so I decided that I’ll make a controller for the graphics simulation.
• Finally got a second sensor stick assembled waiting for silicone to dry.
• Amp was running extremely hot.  Lowered input voltage to 5 volts. This helped with the heat but there is less range of voltage change then before.  After shielding the wires and lowering the voltage the idle readings are much more stable.

8:00 – 4:00

• Meeting with Anne at 9:30. Then I need to chase down what the issues are with my certs.
• Add alerting capability to JavaFacades.java. I’m thinking another db that can be accessed restfully that has a list of all current alerts. This does mean that I’ll need some level of CRUD to deal with handling alerts (acknowledge, etc, from outside the system)
• BLACKPANTHER meeting/demo

• Did a couple tutorials for OpenGL.  Going to continue this over the weekend if I have time.
• Tried to use  the new sensor rod.  The hole for the motor axis is too big.  Tried to use tape and heat shrink but it would still not get tight enough.
• Started fixing the other sensor rod.

7:30 -3:00

• Got a note from Michelle G (LDAT). They want to move ahead. I need to get FGM’s NDA
• Adding better keyboard control to scripting window. Trapped tabs, going for autoindent. Basics of autoindent are done.
• Some permissions problem at the fort. Going back in. Fixed
• 9:30 Meeting with Anne on Monday. Come here first, I guess.

• Finished attaching strain gauges.  Currently waiting for silicone to dry.  For future reference make sure the first layer of resin is fully dry before attaching strain gauges.  If not you might end up with the strain gauge touching the metal rod.
• Added a stop_CW(clockwise) and stopCCW(counter-clockwise) so that it wouldn’t get move commands when its collision reaches the maximum force.  Its hard to test how successful the changes I made were until I get the other sensor stick working because the current one acts too erratic.
• Read OpenGL book

• Strain gauge sensors were changing in unison.  Found out this is because on strain guage was touching the metal rod and through that connecting to the motor ground.
• Still works with ground detached but there is signal interference this way.
• Started attempting to make a strain gauge rod.   Failed first attempt.
• Started reworking the way the output motor reacts to input so that I can stop it when it collides before it stalls out.