Closed alansaid closed 9 years ago
Parts of this could be covered by the runner classes in rival-splt. @abellogin: any comments?
I can create examples for the example module.
I wanted to come back to my suggestion about migrating runners from the modules to the example module (see #27).
Another option would be to create a runners- module (as you suggest in a comment to #27), I do however think that this could be accomplished by having a single runnable entrypoint (i.e. one main method for all of RiVal) which would be either configurable with property files or via command line arguments (e.g. like myedialite's executable)
I see your suggestion here. However, maybe it is too much to do everything at the same time. We can extract all the runners from the modules for release N, then for release N+1 we create the "single runnable entrypoint". What do you think?
Seems reasonable
Also: #57
A general split example is provided in 81a2b29 (related to issue #54). I can still prepare one dummy example for every splitting strategy, it should be easy once we already have one example working.
@abellogin is this finished now?
I'd say so. The examples are only done for movielens, tho, but they should be clear enough for anyone to replicate them with any other dataset or recommender.
:+1:
Create several split examples