OpenForecast

If you choose to forecast on a hourly basis, and you
DataSet runs over a "daylight saving time switch"
(dst), there will be two DataPoints in the set that are
not aequidistant, if you use Hour.class. At least this
happens if you live in a TZ hat has dst ....

My solutuion was -let's call it a workaround- to create
a timezone without dst and added setters on several
parts of openforcecast (May you could switch the
default TZ too, but this might break other things in
your software).

The TZ looks like this:
SimpleTimeZone utcTz = new SimpleTimeZone(0, "nodst");

I am not able to provide a clean patch because I
modified openforecast heaily and don't want you to
confront woth a monster-patch ar the time .....

rgds,
Andreas

P.S. Stay tuned, I added arbitraty lags to the model
and I am working on ln()-ized vars, as well as I have
R^2 value patched in already .....