jcastro-inf / delfos Goto Github PK

When a GroupCaseStudy xml is re-executed, the replicability is ok. However, when the xml is re-generated, even if the content is the same, it produces different recommendation results. This is a serious issue, because other researchers that use delfos in the future might obtain different results.

This should be possible to avoid that a change in two parameters or more on a recommender systems triggers two or more recommendationModel updates in the "--neighborhood-gui" interface.

For each setParameterValue, a parameterChanged event is triggered. If in one metod a bunch of parameters is set, only one parameterChanged event is triggered at the end of the parameter values changes.

Implement the command line help for the library (Command 'delfos --help'). A possible solution is to gather all the CaseUseMode.this.getModeParameter() and provide a sentence or two about each.

Hi,
Please i downloaded your project in order to modify it to make my own recommendation but the project is not complete there are some missing packages.
So please can u send me the complete version of the project with all the packages?

Not following this standard produces unexpected failures in later computations that use User methods such as compare, equals and hashCode.

Parameter selection for the dataset and the recommender system

The goal with this issue is to improve the time of execution of a case study with many executions in machines that support a high thread count.

It is going to be implemented using a lot of lambda expressions. Enjoy 💃