Remember to leave at 3:00 today!

8:00 – 11:30 SR

• Backups
• More training.
• No response from the patch folks. Still waiting.
• Walked through the mapping behavior of column names in Query Builder with Dong.

11:30 – 3:00 FP

• Adding state transitions to app
• Got the entire test suite running.
• Added alerts so that the transition between the speed and accuracy tests is more apparant
• Need to add Exit under the file menu.
• Subversioned everything!
• Tomorrow I need to be able to write out the results.

8:00 – 5:00 SR

• Backups
• Meeting with Chris at 2:00?
• Decided that rather than do updateVizTable and mess with the canonical cars database, I’d start by creating databases and then modifying them. Looks like I might be able to use NOW() for the timestamp column?
• Creating the appropriate table. Did you know that MySQL doesn’t have a way to determine if a table exists? Here’s how I’m doing it:

  	public boolean tableExists(String tableName){
  		try {
  			DatabaseMetaData metadata = dBconnection.getMetaData();
  			ResultSet resultSet = metadata.getTables(null, null, tableName, null);
  			if(resultSet.next())
  				return true;
  		} catch (SQLException e) {
  			return false;
  		}
  		return false;
  	}

• So to add a table, you have to create the table with a UID and timestamp, add a line table_data, get the id for that line, then place that id and the roleId into the table_data_role.
• And here is a script generated test table in VISIBILITY:

• prep for Col. Duke’s presentation
• deployed ProjectManager, looks good
• working on VSS
  • changed variables_values from TEXT to BLOB
    • ALTER TABLE `table_queries` CHANGE `variables_values` `variables_values` BLOB NULL DEFAULT NULL
  • changed variables_values to macros
    • ALTER TABLE `table_queries` CHANGE `variables_values` `macros` BLOB NULL DEFAULT NULL
  • changed all references to variable/variables to macro/macros
  • modified ScriptFacades to use BLOB – convert String to BLOB to store, BLOB to String to retrieve
  • Using Matcher.quoteReplacement(variableValue) to avoid illegal group errors caused by reserved RegEx characters

• cleaned up menus in the main panel and ProjectMgmtPanel
• saving database modifications to ProjectManager/src/main/resources/database/DBUpdateEnhancements.sql
• created a copy of ProjPortfolioMgr webapp – ProjectManager – to use test database, project_portfolio_enh
• created budget_center_contracts – store unique contracts from contracts_cognos table
  • additional column, budget_center_id, to map budget_centers to contracts
  • query to add contracts
    • INSERT INTO budget_center_contracts(
      budget_center,
      appropriation_year,
      requisition_id,
      po_reference,
      acr,
      committed_date,
      committed_amount,
      obligation_date,
      obligated_amount,
      expensed_date,
      expensed_amount,
      po_start_date,
      po_end_date,
      contract_type,
      po_type_code,
      contract_no,
      vendor_id

      )
SELECT budget_center, appropriation_year, requisition_id, po_reference, acr, committed_date, committed_amount, obligation_date, obligated_amount, expensed_date, expensed_amount, po_start_date, po_end_date, contract_type, po_type_code, contract_no, vendor_id
FROM contracts_cognos
GROUP BY requisition_id, po_reference
• add columns to projects table
  • ALTER TABLE `projects` ADD `center_name` VARCHAR( 50 ) NULL ,
ADD `center_number` VARCHAR( 50 ) NULL ,
ADD `appropriation` VARCHAR( 30 ) NULL ,
ADD `type` VARCHAR( 50 ) NULL ,
ADD `capability` VARCHAR( 50 ) NULL ,
ADD `expenditure_center` VARCHAR( 50 ) NULL ,
ADD `investment_portfolio` VARCHAR( 50 ) NULL ,
ADD `program_element` VARCHAR( 50 ) NULL ,
ADD `facts_pe` VARCHAR( 50 ) NULL

• continue re-factoring Project Editor
  • moved Budget Center columns to the main panel from the Budget Center Datagrid
  • removed unnecessary columns
• prepping for move!

• met with Pit-crew, walked through Visibility
• Not all Budget Centers are shown in the Financial Data Entry in PPM causing confusion of the  total budget

• Viz Tool status meeting – notes at PPM/PA req’s and bugs and stuff
• clean up!
• Financial Assistant Specification with Phil

8:00 – 4:30 ESSO

• Presentation prep
  • Need to add the ability to sum across rows in the value views. This might be doable in advanced queries. Need to check further.
• Fixed the color mapping functions to have more variation so that colorblind users can see the pie charts.

8:00 – 12:00 ESSO

• Updated database so alert queries are running correctly.
• Had a bunch of really odd problems – The date calculation seems not to be running correctly, and the headers are not showing up in AdvancedQueryWidgets for new users, but only for a while. It seems to go away and work properly after adding explicit themes, but not immediately. Need more info.

12:00 – 4:00 FP

• Finishing paper.

8:30 – 5:00 ESSO

• Gave Jim Griffie the writeup on why we need at least 2.5 FTE on VISIBILITY
• Jessica found a bug (or at least, something bug-ish). If an invoice has a zero value, it still saves.
• Redid the VISIBILITY website to behave more in line with the way that people use it, and to add Account Manager.
• Reworked VSS so that there are fewer requests of the server at login. Also fixed a bunch of formatting problems. It turns out that a ResizeEvent won’t cause the vertical resize to occur on a Spark form. I had to go back to mx:Form to make resize work properly.
• sent a note about my SSBI

8:30 – 4:30 ESSO

• Looks like a hot summer solstice this year.
• Worked on getting my accounts restarted
• Sent Jim a note on getting the funds adjusted on the ESSO contract.
• Checking into the status of Hudson, etc for fgmdev.
• Getting all the code for VISIBILITY and verifying that it builds.
  • Got the flex side working. Oddities include
    • MvnAssist is no longer working? No – it looks like the part that pulls the POM path from the Eclipse integration is not working correctly. Everything else seems to be behaving.
    • Changing to a new version of Flexbuilder (i.e. 3.2, 3.4 -> 3.6) caused odd include arguments to be added to the Flex Library Compiler option dialog. The additional arguments were removed and then the “Include all classes from all source paths” option had to be selected from the Flex Library Build Path dialog.
    • mvn dependency:tree is a nice way of seeing what a project depends on in a 1980’s graphics format

DataDictionary:

• Check serialize Method
• Flush loops enough times completes data transfer.  Need to integrate all the communications stuff into this method.  (Implemented but Dependent on ComUtil Progress)
• Add get data to data dictionary level.
• Add error checking to importData.  ??? possibly done needs testing
• Add a define for name length.

ComUtil:

Get Large Data Transfer Working Reliably
• Make sure message is sent before data.
• Fix Constructor on Arduino side
• Determine if FinishedProcessing should send a message (No it should not, I need to make it so only one part of the program sends messages for better reliability)
• clearRBuffer() on PC side missing rbufindex reset
• Change CTS case in handshake switch to receive message then data.  Remove receiveMessage() from the ReceiveDataMethod.
• Fix Pointer intialization in both version of the receiveData method
• Figure out if the state commented out is necessary in changeState() both sides
• Adjust methods to evaluate the number of bytes read/written to determine true/false return ???  For some reason the counters in the windows api don’t seem to return properly
• Optimize logic for less passes and better reliabilty

ComMgr:

• Change return of Send and Receive methods on both sides to return number of bytes read/written  This doesn’t work very well.  For some reason the variable that is supposed to return the data sent does not seem to work at all.
• Figure out why the Arduino is not receiving properly

FingerController:

• Need to add variables with names and sizes mirroring the PC side
• adjust logic for new variables
• add some commands for various feature(ex. Material)

Many times I find it hard to find the information I want in to blog among the other entries.  These tags will help to flag important information, to filter some of the more trivial stuff out(if you want more added to the list I will edit this post):

#NOTE:  Something interesting that was found
#IMPROVE:  Something that needs optimization
#FUTURE: Something that you want to remember to look into

#ATTENTION:  Something that you want the other people on the project to read

#LIMITATION:  For noting limiting factors such as memory constraints and what not