heuristicus / final-year-project Goto Github PK

Everything is really messy now - have a clean top directory with things in directories that make sense.

Specifying start before end, or having a very short interval will likely result in some odd behaviour.

• Write unit tests for each function which deals with interval times to ensure that it behaves predictably.

When a parameter file is passed in that does not exist, ask whether to create a default parameter file with that name.

File should be created using default parameters specified in estimator and generator headers, or just randomly chosen values so that the program can be run with minimal effort.

The generator currently uses 'time units' to generate data. This is fine for general use, but it might be useful to be able to specify the time scale used to generate data. For example, if you want to generate an hour's worth of data, you must manually calculate how many seconds the data has, and then break it down into manageable chunks of time.

• Allow specification of the time scale
• Allow specification of subdivisions to use (some proportion of the time scale). e.g. You want data for one hour, and you can make observations of data every 2 minutes.

Need tests to confirm correct functioning of functions which are testable (stuff in utility files, mathematical stuff)

Need a way to run multiple runs of the generator and estimators in a controlled way, with specified parameters.

This usually happens in the piecewise estimator, in the last time interval. Intervals of < 5 seconds or so often result in extremely steep lines which do not reflect the function at all.

• Impose a limit on the minimum interval length.
• If the interval does not exceed the limit, re-estimate the previous line, including the short interval.

Should be able to ask for a parameter to be converted to an integer before it is passed to the caller.

Candidates: double, int, array of ints or doubles

Having to call separate functions all the time to call specific estimators with given parameters is annoying. There should be a central launcher which takes in the parameter file and deals with everything.

Need to be able to:

• Choose whether to estimate or generate function
• Choose which estimator to use
• Set parameters (from file)

Some of the arrays are still in basic form, which makes things less readable. Replace them with the structs we have now.

Structs for holding estimates for individual intervals would make code more readable.

Structure:

• a estimate
• b estimate
• interval start
• interval end