Author Archives: pgfeldman

Dong Shin 06.27.2012

  • continue working on Project Totals display
    • insert/update queries..
    • save / update / retrieve working
  • added filtering for Sub Project selection window
    • filter on Project ID and Project Name
    • adjusted sub project selection queries to find the start and end year that falls within the parent
      • SELECT uid, project_number as projectID, title as projectName, begin_year as startFY,
        end_year as endFY, total_budget as totalBudget, 0 as isSelected
        FROM projects
        WHERE uid NOT IN (SELECT project_id FROM _project_sub_projects)
        AND uid NOT IN (SELECT sub_project_id FROM _project_sub_projects)
        AND begin_year >= (SELECT begin_year FROM projects WHERE uid = 102)
        AND end_year <= (SELECT end_year FROM projects WHERE uid = 102)
        AND uid <> 102
  • helped Phil building PPM
    • need to change Flex Project settings…

Mike 6.26.2012

  • Investigating issue tracking software which could be useful for the visibility project or future projects: reasonable free options are trac and bugzilla
    • Bugzilla is apparently a pain to install but works well for very large projects with lots of user feedback
    • Trac is easier to install and maintain and has great svn integration
    • Jira is the best option but costs $1,400-$4,800 per server
  • Gave a demo to Robert A. over the whole vis suite
  • Meeting this afternoon about the SSP was cancelled
  • There seems to be a bug with the vis scripting publish feature, weird characters are being appended to the beginning of the xml.  Appears to only be occurring at site.

Dong Shin 06.26.2012

  • working on Project Totals display
    • need new table – yearly_totals
      • # create new table yearly_totals
        CREATE TABLE `yearly_totals` (
        `uid` INT NOT NULL AUTO_INCREMENT PRIMARY KEY ,
        `project_id` INT NOT NULL ,
        `fiscal_year` INT NOT NULL ,
        `allocated_amount` DOUBLE NOT NULL ,
        INDEX ( `project_id` )
        ) ENGINE = InnoDB;ALTER TABLE `yearly_totals` ADD FOREIGN KEY ( `project_id` ) REFERENCES `project_portfolio`.`projects` (
        `uid`) ON DELETE CASCADE ON UPDATE CASCADE ;
    • created DataGrid to display the yearly totals

Phil 6.26.12

8:00 – 4:00 ESSO

  • Neat jQuery countdown timer here. Also cool is how the examples are embedded in the description.
  • The problem with the excel files and image snapshots was that there was a 
    <vis:download>https://127.0.0.1/Visibility3/downloads</vis:download>

    rather than

    <vis:downloads>https://127.0.0.1/Visibility3/downloads</vis:downloads>

    SingletonDataDictionary stored ‘download’ just fine and when widgetBase asked for ‘downloads’ SDD didn’t know what to return and returned an empty object. Added a warning logger message whenever getItem returns an unset item.

  • Got VisibilityScripting up and running. Oddly, there were no server settings, which had to be added. Checked in now.
  • ….and then I spent the rest of the day dealing with software updates. Sigh.

Mike 6.25.2012

  • Server backups at site
  • Helping Phil get up and running and slowly transferring files, info, etc.
  • Helped introduce Pedro to the tool, met another data entry person
  • Scheduled a demo for tomorrow
  • Working on query for a full year summary report, it’s long but it work in phpMyAdmin, going to try and put it in visibility scripting tomorrow
  • Working on cleaning up my FGM computer, putting important things in svn, saving code I think is useful, etc.

Phil 6.25.12

8:00 – 4:00 ESSO

  • Well, I can log into the integration machine, but not the test. Submitted a ticket
  • Web-based IDE! http://c9.io/
  • PPM issues:
    • Turn off (column) sorting on Project Data entry
    • Gray out non-editable fields in PPM.
  • Icons work in the Network Widget. I can’t save out excel files or screenshots. Next thing on the list…

Tom DeVito 6.24.2012

Start: 12:00

  • Added a spot for the LEDs which I forgot about
  • Continued running traces.
  • Added connectors for LEDs and Sensors
  • Started writing documentation not quite complete at the moment.

End: 8:00

Tom DeVito 6.22.2012

Start: 10:00

  • Cleaned up equipment that was on my desk.  It was placed by the other equipment in.
  • I put all hardware related to the wooden case inside it.  Be careful when moving as there is a cup of screws in there which may or may not be needed.
  • Double checked wirring to speakers and sensors.  There was no good way to easily figure out which one went to which.  The ends are labeled and can be spliced into a new connector.  The connector on the board will have the first row with three fingers two on the ends one in the middle, the second smaller row will have the remaining two on the ends.  The ordering will be left to right up and down.  This applies to both speakers and sensors.
  • Started routing the traces for the midi and reset pins of the midi controllers

End: 6:00

Mike 6.22.2012

  • Server backups at site
  • Gave a one-on-one demo to Marty of the Vis Tool Suite
  • Talked to Denise P. about the SSP checklist, she is trying to track it down
  • Ingested a spreadsheet of all current FY11 data and will try to generate some vis tool reports against it
  • Tested some queries against the Fy11 spreadsheet
  • Need to get Jim and Jim talking to one another about $
  • Resolved an issue with the map server not working
  • Added an abbreviated label function to flexichart within Visibility:
    • 1200000000 > 1.20B
    • 1234567 > 1.23M
    • 1234 > 1.23K
    • 123 > 123

Phil 6.22.12

8:00 – 4:00 ESSO

  • More effort expended on getting my admin password
  • Meeting with Denise P
  • Checked fixed version of MavenAssist back into Sourceforge
  • Testing icons in VISIBILITY
  • Still need to download and install the following:
    • ManagementUtils – FB is having a hard time understanding this one. Fixed by deleting and reloading from SVN, then updating the Flex compiler
    • Visibility Scripting Server
    • PPM
    • PA
  • I’m pulling out the dependencies on the VISIBILITY SWCs and adding in dependencies on projects. It makes rebuilding the application much cleaner, ensures that there will be no mismatch between library code in the editor and what’s being linked in. I think a dummy project that pulls in the appropriate swcs and puts them in the repository may still be a good idea.

Dong Shin 06.22.2012

  • fixed SQL error when apostrophe(‘) is present in Funding Request fields
  • fixed disappearing Labels for the horizontal navigator (Data and Chart) in Financial Data (Monthly Data) panel
  • track last login – added server code to update users, last_login column to user table
  • working on sub/parent projects navigation…
    • removed ProjectBudgetWindow for sub projects, replaced it with Project Editor when double-clicking
    • added yearly budget details for sub projects
    • query to retrieve all funding summary
      • SELECT p1.project_number AS projectID, p1.title AS projectName, p1.begin_year AS startFY, p1.end_year AS endFY, p1.total_budget AS totalBudget, p2 . *, c.*,
        SUM(IF(a.year=1, a.amount, NULL)) as year1Amount,
        SUM(IF(a.year=2, a.amount, NULL)) as year2Amount,
        SUM(IF(a.year=3, a.amount, NULL)) as year3Amount,
        SUM(IF(a.year=4, a.amount, NULL)) as year4Amount,
        SUM(IF(a.year=5, a.amount, NULL)) as year5Amount,
        SUM(IF(a.year=6, a.amount, NULL)) as year6Amount,
        SUM(IF(a.year=7, a.amount, NULL)) as year7Amount,
        SUM(IF(a.year=8, a.amount, NULL)) as year8Amount,
        SUM(IF(a.year=9, a.amount, NULL)) as year9Amount,
        SUM(IF(a.year=10, a.amount, NULL)) as year10Amount
        FROM projects p1, _project_sub_projects p2, budget_centers c,
        budget_amounts a
        WHERE p2.project_id =99
        AND p2.sub_project_id = p1.uid
        AND c.project_id = p2.sub_project_id
        AND c.uid = budget_center_id
        GROUP BY c.project_id

Tom 6.21.2012

Start: 10:00

  • Realized my connectors for the midi controller were missing a pin.  Swapped them out.
  • Fixed some routing problems
  • Started looking through my red box of miscellaneous electronics to see what needs to be labeled.
  • Started writing a readme for both versions of the board to hopefully clear any confusion in my absence.
  • Checklist of important things to add to readme:
  1. rating of sensor resistors
  2. mapping of sensor/speaker connectors
  3. general parts list
  4. add numbering which corresponds to the board locations
  • Although the new boards will be more practical, the old boards do have the advantage of the extra volume control if ever needed in the future.

End 6:00

Mike 6.21.2012

  • Server backups at site
  • Weekly status meeting
  • Sent copies of the documentation to Bill and Jessica
  • Deployed the new visibility to the test server
  • Updated the reports in visibility with the new charting stuff
  • Investigated a bug in PPM when submitting a funding request it would not save.  Appears to be a problem with string being too long to fit in the database
  • Improved some aspects of the charting library
  • Helped Phil build the java projects