8:00 – 5:00 SR

• Figured out Bayes Theorem and got some spreadsheet examples working over the weekend. It’s effective and appropriate.
• Started modifying DBTypedTable to handle tables that are created by sequential calls to the DB. Basically a way of making mode sophisticated joins.
• Adding items into the 2Dchart test.
• All full area charts work.
• Need to get area charts that only cover part of the chart working. Done
• Need to add DataPoints to the bottom of area charts that are not zero. Done
• Need to add clustered bars, based on the number of where the bar is in the order of the dataFormat object.
• Need to throw an event (or do something similar) when an items is clicked.

8:00 – 4:00 SR

• Possibly a good book to get? https://www.ng-book.com/
• Working on getting regression to predict upper and lower bounds
• Working out the structure of the dataFormat and dataProvider Objects
• dataFormat example

  this.dataFormat = { // might add 2D/3d, dynamic/static, etc.
     goals: "area",
     obligations:"area",
     pm_actuals:"bar",
     facts:"bar",
     pm_future:"area",
     facts_future:"area"
  };

• Matching dataProvider example. Note the _mappings array and the fact that all items have a min/max value as well as a chart-wide minmax (no Z in this case)

  this.dataProvider = {
     _type:'XY', // RAH (Radius Angle Height) RAE (Radius Azimuth Elevation), XYZ, etc.
     _min_max:{xmin:0.00, xmax:11.00, ymin:0.00, ymax:3135.30},
     _mappings:[{Jan:0, Feb:1, Mar:2, Apr:3, May:4, Jun:5, Jul:6, Aug:7, Sep:8, Oct:9, Nov:10, Dec:11}],
     goals:{Jan:{min:0, max:1000.00}, Feb:{min:0, max:1100.00}, Mar:{min:0, max:1210.00}, Apr:{min:0, max:1331.00}, May:{min:0, max:1464.10}, Jun:{min:0, max:1610.51}, Jul:{min:0, max:1771.56}, Aug:{min:0, max:1948.72}, Sep:{min:0, max:2143.59}, Oct:{min:0, max:2357.95}, Nov:{min:0, max:2593.74}, Dec:{min:0, max:2853.12}},
     obligations:{Jan:{min:0, max:500.00}, Feb:{min:0, max:600.00}, Mar:{min:0, max:720.00}, Apr:{min:0, max:864.00}, May:{min:0, max:1036.80}, Jun:{min:0, max:1244.16}, Jul:{min:0, max:1492.99}, Aug:{min:0, max:1791.59}, Sep:{min:0, max:2149.91}, Oct:{min:0, max:2579.89}, Nov:{min:0, max:3095.87}, Dec:{min:0, max:3715.04}},
     pm_actuals:{Jan:{min:0, max:250.00}, Feb:{min:0, max:341.39}, Mar:{min:0, max:495.27}, Apr:{min:0, max:618.30}, May:{min:0, max:923.08}, Jun:{min:0, max:1318.68}},
     facts:{Jan:{min:0, max:125.00}, Feb:{min:0, max:134.17}, Mar:{min:0, max:134.31}, Apr:{min:0, max:163.00}, May:{min:0, max:164.36}, Jun:{min:0, max:202.29}},
     future_pm_actuals:{Jun:{min:1318.68, max:1318.68}, Jul:{min:1257.91, max:1499.96}, Aug:{min:1342.92, max:1827.03}, Sep:{min:1427.94, max:2154.10}, Oct:{min:1512.96, max:2481.16}, Nov:{min:1597.97, max:2808.23}, Dec:{min:1682.99, max:3135.30}},
     future_facts:{Jun:{min:202.29, max:202.29}, Jul:{min:193.38, max:215.48}, Aug:{min:196.77, max:240.99}, Sep:{min:200.17, max:266.49}, Oct:{min:203.57, max:291.99}, Nov:{min:206.96, max:317.50}, Dec:{min:210.36, max:343.00}}
  };

• In excel, the results look like the following. Now working on incorporating into the graphing system 
• Setting up a method to calculate the screen positions of the data points based on the dataProvider. Got margins, datagrids and areaCharts working. BarCharts are next. I need to think about how to cluster the bars. I’ll also need to add additional DataPoints when the botom axis is not (zero? horizontal?)

8:00 – 4:30 SR

• Showed Lenny the new charts. He’ll be out tomorrow, so I’ll probably deploy the test version on Monday. We then had a long talk about the best way to statistically model the data in the first chart. It really sounds like Bayes might be the way to do this. Which is awesomely cool, because my schoolwork and jobwork are perfectly aligned for the weekend. Gonna charge me some hours figuring out Bayes.
• Building the dataFormat and dataProvider Objects. Since Lenny wants future performance, I’m pulling in the Apache commons math jar for linear regression. I think I want OLSMultipleLinearRegression
• Added SimpleLinearRegression to JavaUtils that wraps OLSMultipleLinearRegression and hides some complexity.that is not intuitively obvious documentation. Glad I found this example. Added to Subversion. I’ll probably need to add a method that gets the error so that I can add that to the future error.
• More JSON tomorrow, then on to Bayes. Did get this book…

7:00 – 3:30 SR

• Timesheets
• Wow – upgraded to Windows 7! Of course, that means that I don’t have PuTTY and can’t get to the servers. Put in a ticket…
• Need to see how super() works in JavaScript. I’m thinking it should be possible to write a Utils.FatSuper(this.myFnPtr) static method that will do the same.
• TypeScript parent class (Parts stripped out for clarity):

  export class TestController implements ITestController {
     // standard TypeScript constructor
     constructor() {
     }
  
     public extendableFunction():void{
        alert("It's extendableFunction()");
     }
  
     public fatArrowFunction = ():void => {
        alert("It's fatArrowFunction()");
     }
  }

• Compiled JavaScript of above:

  var TestController = (function () {
      // standard TypeScript constructor
      function TestController() {
          var _this = this;
          
          this.fatArrowFunction = function () {
              alert("It's fatArrowFunction()");
          };
      }
      TestController.prototype.extendableFunction = function () {
          alert("It's extendableFunction()");
      };
      return TestController;
  })();
  InheritApp.TestController = TestController;

• TypeScript child class:

  export class TestController2 extends TestController implements ITestController2 {
     myInheritedString:string;
  
     // standard inheriting constructor pattern. Note that 'super' must be on the first line and
     // that the arguments from angular get passed through
     constructor(){
        super();
     }
  
     public extendableFunction():void{
        super.extendableFunction();
     }
  }

• Compiled JavaScript of above:

  var TestController2 = (function (_super) {
      __extends(TestController2, _super);
      
      function TestController2() {
          _super.call(this);
      }
      TestController2.prototype.extendableFunction = function () {
          _super.prototype.extendableFunction.call(this);
      };
      return TestController2;
  })(TestController);
  InheritApp.TestController2 = TestController2;

• JavaScript of above with all the contents commented out:

  var TestController2 = (function (_super) {
      __extends(TestController2, _super);
      function TestController2() {
          _super.apply(this, arguments);
      }
      return TestController2;
  })(TestController);
  InheritApp.TestController2 = TestController2;

• As an aside, __extends is just parasitic inheritance:

  var __extends = this.__extends || function (d, b) {
      for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p];
      function __() { this.constructor = d; }
      __.prototype = b.prototype;
      d.prototype = new __();
  };

• So we know a few things now:
  • extending in TypeScript means that the child class is called with the parent class passed in as an argument called ‘_super’
  • Fat arrow functions are defined in the constructor as variables pointing to functions and are attached to ‘this’, not ‘_this’
• I tried looking for the properties in the debugger, but couldn’t really see what was going on in the JavaScript. So I added a loop over the properties in the TestController2 constructor. FatArrowFunction is listed and extendableFunction is not. To me this makes sense, as extendableFunction is on the prototype:

  this[fatArrowFunction] = function () {
          alert("It's fatArrowFunction()");
      }

• Building on the above, we can make what boils down to our own prototype for fat functions. The other option is to turn everything into fat functions as per this nifty piece of work, discussed on this page. I have a concern about adding all this wrapping to functions, so until I run some tests and see what’s faster, here’s a way of doing it semi-manually. Here’s the parent code:

  export class TestController implements ITestController {
     public functionMap:Function[];
  
     // standard TypeScript constructor
     constructor() {
        this.functionMap = [];
        this.setFatPrototype(this.fatArrowFunction, "fatArrowFunction");
     }
  
     public fatArrowFunction = (arg:string):void => {
        alert("It's fatArrowFunction("+arg+")");
     };
  
     public extendableFunction():void{
        alert("It's extendableFunction()");
     }
     public setFatPrototype(fn:Function, n:string){
        // TODO: look for earlier prototypes that we might need to call
        fn["name"] = n;
        this.functionMap[n] = fn;
     }
     public fatSuper(fnName:string, childArgs:IArguments){
        // TODO: look for earlier prototypes that we might need to call
        var fn;Function;
        if(this.functionMap.hasOwnProperty(fnName)){
           fn = this.functionMap[fnName];
           fn.apply(fn, childArgs);
        }else{
           console.log("fatSuper(): function '"+fnName+"'does not exist on the prototype chain");
        }
     }
  }

• And here’s the child class:

  export class TestController2 extends TestController implements ITestController2 {
  
     public extendableFunction():void{
        super.extendableFunction();
     }
  
     public fatArrowFunction = (arg:string):void => {
        this.fatSuper("fatArrowFunction", arguments);
        alert("It's fatArrowFunction2("+arg+")");
     };
  }

• As the comments say, I do not recurse up the ‘prototyp’ tree yet, though that wouldn’t be hard. Before I do that, I need to implement both versions and see if the version that converts all functions to function pointers works with Angular and if it does, to run some tests to see which is faster. Stuff for Monday.

8:00 – 5:00 SR

• Set up Mark’s accounts
• Set up an admin account for our tester. Not sure if that’s actually needed?
• Brought over the latest and greatest for Bill to scan. Should be ready for testing tomorrow.
• Finish integrating Chartinfo class into testbed. Done, but more of an adventure than I was expecting. First, my development box began acting weird (fan noises, flickering graphics, slow performance). Then it BSOD’d. When I finally got it back up, the debugger kept on getting confused about comments. Once that was sorted, I couldn’t get picking to work on area charts, even though it worked fine for everything else. That traced back to a null value for the component name, which is an explicit test I run to manage tooltips. So once the name from the ChartInfo item was loaded into the glComponent, everything began working correctly. Sheesh.
• Tried to get my laptop again and also a replacement workstation, since this one is now suspect.
• Running CC