Category Archives: Phil

Phil 10.16.13

8:00 – 4:00 SR

  • Obligation and Commitments from FACTS are cumulative. Actuals are non-cumulative. Remove all the calculations summing up obligations and commitments by monthly and store monthly values from Cognos.
  • IE7 works with YUI!
  • Need to add search to “View Financial Data”. Rather than showing all the subelements, clicking on a row in Requisition Information (top grid) will show the associated detailed financial view. We should also add a search to Req Info.   The summary always shows.
  • Create historical record Cognos data table. We can use scripts later to integrate data into our reports…
  • Finished chapter 2, starting on chapter 3. Also got timers working from the gallery. One search, one bug, one additional search.

Phil 10.15.13

Phil 8:00 – 3:30  SR

  • The dialog for versions has a broken “dismiss” button.
  • Unlock project is unlocking multiple projects locked by the same user(?)
  • Trying out YUI on the integration server…. Success! Take that, IE7! Ok, maybe not. Just realized that I only ran the testes using the browser that’s on the server, which is FF. Need to try running on a client box with IE tomorrow. The most important example to run will probably be add_capability.html.
  • Working my way through the YUI cookbook. In the element_classes example (Recipe 2.2), there is a call to Y.log(). It turns out that there is support for a logger window. I found this by Googling “yui Y.log” The top result was http://yuilibrary.com/yui/docs/console/.  Which was pretty much what I needed. Using the documentation as a guide, I was able to integrate it, including giving it a global scope.  And then, after a few more minutes, I was able to add draggable behavior by adding “dd-plugin” to the YUI().use() arguments and them to the Y.Console.plug() arguments. For future reference, here’s the total code required for the console, with three lines of test code (bracket the code with <body class = “yui3-skin-sam”>):
YUI().use('console', 'overlay', "console-filters", "dd-plugin", function (Y) {
    // Console has no required configuration
    // In fact, you often don't even need to store the instance
    var cons = new Y.Console({ logSource: Y.Global })
            .plug(Y.Plugin.Drag, { handles: ['.yui3-console-hd'] })
            .plug(Y.Plugin.ConsoleFilters);
    cons.render();
    Y.log("Console info message", "info", "element_classes");
    Y.log("Console warn message", "warn", "element_classes");
    Y.log("Console error message", "error", "element_classes");
});
  • Skedaddled a bit early to get in some good weather

Phil 10.11.13

8:00 – 4:00 SR

  • Backups
  • Meeting with Lenny
  • Deployed a new version of FA that fixed the comboboxes but broke other things. Also, it looks like the QuieryBuilder config isn’t up to date.
  • Installing JetBrains 7.0
  • Back to Javascript. I think a good goal is to produce a suite of tests to run on IE7 and see how that goes.
  • It should actually go pretty well, assuming this compatibility chart is correct:
  • Also, there seems to be a conference coming up.
  • Getting back into the hang of YUI. Still cool. And about a third caught up.

Phil 10.9.13

8:30 – 1:30 SR

  • Ungodly traffic this morning.
  • Backups
  • Deployed new FA and RA, plus some new scripts.
  • Cognos data is wrong in that amounts in excess of the budget are being calculated from expenditures. The >100% rule might fix this, but I’m worried that in may need to be more sophisticated.
  • Did a Cognos upload of 1300 records with logging turned on that really slowed down Tomcat, including things like logging in. Accessing the published data REST servlet on the server worked fine though. Not sure what the deal is. I turned off logging to the DB and restarted the server, which sped things up. We need to try another Cognos ingest to see what happens. Lenny did one this morning that took a fraction of the time of the later one.
  • At the very least, we’re going to need to deal with user reactions to an apparently hung system with a dialog or something.
  • Burning September status to disk.

1:30 – 4:30 FP

  • Done with table. Back to writing.

Phil 10.4.13

8:00 – 4:00 FP

  • Basically banging away on the paper. Abstract, Introduction, Previous Work, Experiment are done. About halfway through results. Might finish first draft on Monday?

Phil 10.3.13

8:00 – 9:00 SR

  • Checking to see if Lenny can come over and help, since he’s stuck at home.
  • Doing some research into the new Flash applications

9:00 – 4:00 FP

Phil 10.2.13

8:30 – 10:30 SR

  • Working out a plan with Dong about what to do with our time. I’m guessing that the shutdown will last until at least Oct 17. The following is for the rest of this week:
    • Fix Script to add EA Cognos data plus autofill  (Obligations_outlays)
    • enter Contract Number in Invoice Entry (RA)
    • allow commas, periods in data entry (RA)
    • add Invoice Viewer in RA for the selected Req
    • Get all code up and running on FGMDEV
    • Drop maven and go to eclipse-based projects
    • Default combobox capability.
    • Create an “table_errors” table that has the application, user, date, time, query and error message, and take out the “Mail to Admin note”
  • For next week, add #include for python module storage and assembly.

10:30 – 4:30 FP

  • Finished Annotated Bibliography. Experimental design is next.

Phil 10.1.13

8:00 – 4:00 FP

  • I’m guessing this is what I charge to for a while
  • In meeting with Dr. Kuber, I brought up something that I’ve been thinking about since the weekend. The interface works, provably so. The pilot study shows that it can be used for (a) training and (b) “useful” work. If the goal is to produce “blue collar telecommuting”, then the question becomes, how do we actually achieve that? A dumb master-slave system makes very little sense for a few reasons:
    • Time lag. It may not be possible to always get a fast enough response loop to make haptics work well
    • Machine intelligence. With robots coming online like Baxter, there is certainly some level of autonomy that the on-site robot can perform. So, what’s a good human-robot synergy?
  • I’m thinking that a hybrid virtual/physical interface might be interesting.
    • The robotic workcell is constantly scanned and digitized by cameras. The data is then turned into models of the items that the robot is to work with.
    • These items are rendered locally to the operator, who manipulates the virtual objects using tight-loop haptics, 3D graphics, etc. Since (often?) the space is well known, the objects can be rendered from a library of CAD-correct parts.
    • The operator manipulates the virtual objects. The robot follows the “path” laid down by the operator. The position and behavior of the actual robot is represented in some way (ghost image, warning bar, etc). This is known as Mediated Teleoperation, and described nicely in this paper.
    • The novel part, at least as far as I can determine at this point is using mediated telepresence to train a robot in a task:
      • The operator can instruct the robot to learn some or all of a particular procedure. This probably entails setting entry, exit, and error conditions for tasks, which the operator is able to create on the local workstation.
      • It is reasonable to expect that in many cases, this sort of work will be a mix of manual control and automated behavior. For example, placing of a part may be manual, but screwing a bolt into place to a particular torque could be entirely automatic. If a robot’s behavior is made  fully autonomous, the operator needs simply to monitor the system for errors or non-optimal behavior. At that point, the operator could engage another robot and repeat the above process.
      • User interfaces that inform the operator when the robot is coming out of autonomous modes in a seamless way need to be explored.

Phil 9.27.13

8:00 – 11:30 SR

  • Parent projects can only be created if there are no REQ’s. If there are, pop up a dialog that says REQ’s must be eliminated. A parent project has no visible REQ tab.
  • Add table_combobox_defaults with 3 columns 1) Editable, 2) Default value, 3) Table name
  • Unresolved discussion about REQ tracking discussion with Lenny.
  • Timesheets.

11:30 – FP

  • More paper