Sliding-window splitting about coronet HOT 2 CLOSED

I am working on the sliding-window approach for splitting data and networks. You can find the current process on my branch sliding-window.

Unfortunately, I have a problem with the revisions and ranges that are stored in the ProjectConf object: Right now, to update the revisions and ranges, I use the method ProjectConf$set.revisions (see here), but this does not work properly for the sliding-window approach.

When using the method, I give the list of revisions as follows:

[0/2 tw, 1/2 tw, 2/2 tw,. 3/2 tw, ...]

The list of ranges is computed as follows (which is wrong in this case):

[0/2 -- 1/2 tw, 1/2 tw -- 2/2 tw, 2/2 tw -- 3/2 tw, ...]

The list of revisions should be, as shown in the opening message:

[0/2 -- 2/2 tw, 1/2 tw -- 3/2 tw, 2/2 tw -- 4/2 tw, ...]

The question is now: How do we fix that?
There are two possibilities:

1. Implement a method ProjectConf$set.ranges to set the correct ranges.
2. Add a parameter sliding.window to the method ProjectConf$set.revisions which can be used to adjust the range-construction code (by passing it to ProjectConf$construct.ranges).

There is a follow-up question, especially for option 2: Shall we add a field ranges.sliding.window (or similar) to ProjectConf which indicates, whether a sliding window approach is used for the ranges?

@hechtlC, @Roger1995, @bockthom, any ideas on that?
I am in favor of option 2, by the way.

from coronet.

I have implemented the second option in the referenced commit e4270ae. Thoughts?

from coronet.