Category Archives: Phil

Phil 12.13.13

8:00 – 12:00 SR

  • Backups
  • Meeting with Tim next week, probably Wednesday afternoon
  • Deployed new FA, RA and RQ
  • Installed a new truststore. We’ll see if it fixes the new login problems

Phil 12.11.13

8:00 – 4:00 SR

  • Backups
  • Deployed new Reqonciler and updated the queries
  • Created a new adminUtils.html page. This now has links to all the admin tools, and I took them off the index.html page.

Phil 12.9.13

8:30 – 2:30 SR

  • Two words without redeeming value: “Wintery mix”.
  • Backups
  • Verified that RA was recording user info in the query logs. It does not seem to be recording info about FMPs though.
  • Deploying new RA, but not the RQ updates, since Dong was stuck at home.

Phil 12/6/13

8:00 – 4:00 SR

  • Backups
  • Deployed new RA and DB updates
  • Need to do status report!
  • Don’t refresh RA display unless an update is made.
  • Lenny will provide a whitelist of Cognos columns to use for row compare on ingest.
  • RQ is double-counting on pre-process
  • Obligation not showing up for FY14
  • Finished adding en errors to fake data as per customer spec
    • Multiple obligation dates
    • Disappearing commitment and/or obligation dates
    • Committed Amount greater than Req Allocation
    • Obligated Amount greater than Committed Amount
    • Obligated Amount greater than Req Allocation
    • Outlay Amount greater than Committed Amount
    • Outlay Amount greater than Obligated Amount
    • Outlay Amount greater than Req Allocation

Phil 12.5.13

8:00 – 4:00 SR

  • Two years ago I broke my femur, so it’s as good as it’s going to get. Which is actually pretty good. Just some low-level aches.
  • Backups
  • Meeting with the full financial and project team
  • The user object in RA is not working correctly. Wrong user id’s are being written into the query log. FA is ok.
  • Meeting with Tim E. at 1:30?

Phil 12.4.13

8:00 – 4:00

  • Backups
  • Server paperwork
  • Fixing bugs in the generation program
    • Filling in data only until “today”
    • Allowing varying numbers of lines up to the requested amount, based on if the project is at its end year.
    • All bugs appear fixed. Now we need to break things. Burning a copy of the spreadsheet for Lenny to look at.
  • Next step is to create a Swing(?) app that will let the user determine what errors to inject.

Phil 12.3.13

8:00 – 4:00 SR

  • Backups
  • SQL changes
  • Changes made to queries in query builder are not updating correctly
  • Obligations may only be appearing in the month that they occurred. They need to carry forward, then overwrite as the next obligation comes in.
  • Still a problem with EAs. Req assistent shows correct outlays through September of the first year, but is blank in October of the second year, then roughly four times the amount that it should be. Queries are wrong, with no discernible pattern. MIPRs are ok.
  • Change “Committed Amount” to REQ Funded Amount”
  • Got spreadsheets ingesting
  • Found a date bug that may have had something to do with ints vs. longs. Adding more lines fixed the problem.

Phil 11.29.13

8:00 – 10:30 SR

  • Backups
  • Paperwork – finally worked out the receipts from the YUIconf trip.
  • Timesheets!

10:00 – 4:00 FP

  • Checked to see if learning time made was significant. Nope.
  • Make any changes to Ravi’s paper
  • Change all references to “normalized” reaction times to “percentage”. Hopefully that will be more clear.
  • Cut down paper to 6 (CHI WIP format) and 2 page (Haptics or 3DUI?)  versions.
  • If the office is open, run ANOVA on the time-to-learn (session 2 – session 1)

Phil 11.27.13

8:00 – 4:00 SR

  • One day the sky will be blue again…
  • Backups
  • Deployed new FA
  • Got completely flummoxed about why the year-summing query is misbehaving. Numerous attempts to fix, with no joy. Dong’s going to mull this one over the holiday
  • Working on iterating over sub-budget centers to write out correct data. Once that’s working, I start on screwing it up.
    • Committed date(s)
    • Committed amount(s)
    • Obligation date(s)
    • Obligation amount(s)
    • Expensed date(s)
    • Expensed amount(s)
    • Iterate over all SBCs and add lines from SBCs that have their project set.
    • A random number of rows >= 1 gets returned.  Data is synthesized from the ObligationOutlays class.
  • Done and running. Need to make a little more general. Right now there are only two rows per type – an entry from halfway from today to the beginning of teh project and an entry from last week.

Phil 11.25.13

8:00 – 3:00 SR

Phil 11.22.13

8:00 – 5:00 SR

  • Backups
  • Move back into the office
  • Add date handling based on project start and whether current ObligationOutlay.value(type) is at total budget. Done.
  • Project SQL output testing – done
  • Start cognos spreadsheet outputs
  • The portfolio managers on the project information tab should see all the requisitions (in RA) that are behind that project (High Priority)
  • Need to list what users are active, and what roles they have (Can just be a query)
  • Purge users that are not assigned to a project or requisition.
  • Because of the Cognos line matching algorithm, should we be only pulling the minimum columns?
  • There can be multiple projects per sub-budget center.

Phil 11.21.13

8:00 – 4:00 SR

  • One month to go until the days start getting longer
  • Backups
  • New furniture
  • Need to change column names in vis export so that there are no spaces (special characters) in the column names. Underscores should be used to match ingestor.

Phil 11.20.13

8:00 – 5:00 SR

  • Backups
  • Deployed new FA
  • Verified that we could connect to Visibility, but the default table name is in there.
  • Discussed path forward with Chris and Lenny. Next discussion will be next Tuesday
  • Duplicate project listing in “Project Management” in FA
  • Fake data
    • Need to add start date
    • Need to stop PM Actuals, Outlays from being written in the future
    • Change OO from being nxn arrays to arrays of n OO classes each with 12 months?
    • Only one sub budget center per project. BC can be shared, but SBCs are not
    • Future values are null, not zero
    • Started writing out Project sql. Need to know what a few things are before finishing.