dddomin3 / savingscalc Goto Github PK

This is actually a very important point. When the program is running on G2020, it would be a very expensive operation to expect the entire data set every single time this program runs. Regardless, even now, it would be great if only the current months data, and some sort of continuation file is given so the program only needs that to run.

Therefore, files that save all of the necessary information from the previous run are imperative. Changing previous data should ALWAYS be an expensive operation, and this will prompt an update which will require a run from the beginning. G2020 will have logs to let SavingsCalc who when to rerun all data.

The program should be able to accept data on a line by line basis from any source. Only source so far is the .csv data files.

In the future, when more information is given, Galaxy 2020 may send data in JSON, XML, or some other format, and SavingsCalc should be able to parse this information at will.

line-by-line is a big assumption, but I imagine this enhancement will change multiple times throughout its life-cycle.

If it doesn't reside in the third column with the correct facility, program spits out zero for annualized quantities, but numbers for non-annualized numbers.

re: active code in analytics, CalcActive, etc

If points simply do not exist, they should not impact the active percentage, unless they ALL do not exist, or a sufficient amount do not exist to inhibit calculation.

This is pretty much for OoO...

A user should be able to view a timestamp by timestamp output of every ticket so that he/she may evaluate them on a case-by-case basis.

This should look exactly like the _save files of old, just prettier