Jan de Boer wrote:Giovanni you sound like my management and that is not a compliment. (...) I am also living in the Netherlands by the way.
Claude Moore wrote:Interesting question. My humble opinion is that no ANN or other deep learning algorithms are really needed to try to predict the outcome of a football match. What do you need, generally speaking, is a way to measure how much a football team is strong in a given moment of the championship, and, because I don't think that the ability to play football can be measured in absolute terms, you need a way to measure a team strength with respect to competitors. Somehow similar to ELO points used in chess. ELO points are based upon the concept that the more the difference of ELO points between two players is, the more likely is that the player with higher ELO score will win the match. ELO score is adjusted after each match: you get an increment or a decrement of your score proportionally to the difference of your ELO and your opponent's, so that you won't get many points if you are strong and defeat a weak opponent, while you will loose more points if you are defeated by a weaker opponent.
Building an ELO-like score may be enough, and you may try to create such rating by a) assigning to each team an initial score b) update for each team its score using the recent historical series of match outcomes.
Bear Bibeault wrote:
Peter Rooke wrote:I suspect the best work gets done, when people are working remotely from home away from the "managers".
I know this works for me. Last time I worked in a Google-esque "collaboration" room it was impossible to even think straight.
Jeanne Boyarsky wrote:Giovanni: Nice on the Google autocomplete! Yes, those would be reasonable reasons. Except that my resume is not online in the first place. This and this are the closest things that are. So it is clearly boilerplate and not that he was looking at my resume.
Campbell Ritchie wrote:Requiring a laundry list is sexist, so that is discriminatory too.
And I was using Java® long before half past seven.
Piet Souris wrote:There's a lot more to say about what distributions you prefer. First of all, it is a little unfair to compare distributions if the means are different. But if means are different, then it is likely that the price you pay for this higher mean is also higher. Then what about your 'risk appetite': how much risk are you prepared to take? For companies having their shares at the stock exchange, they prefer stable results, so with little variance.
And if you could choose between two lotteries: one that pays out twice the price with 50% change, or pays nothing when you loose, or one that pays 6 in case of a win, or 4 in case of a loss, 50 % again, what would you do if in the first case loosing means having to walk home? And maybe that right one armed bandit is much more expensive? Et cetera. One just gotta love statistics
Giovanni Montano wrote:
Stephan van Hulst wrote:
The only problem with your architecture is that you are bringing <Modeldata> generic type in the repository
Why is that a problem? It's the solution to your problem. Your repository classes are responsible for transforming all the different formats of your backing services to one format that contains the information that your views require. No need for your views to perform one kind of logic for a BezinningModel and another kind of logic for a BezinningDb. They only have to take data from one class that YOU control.
With some regret I do not get what is the solution, naturally I agree with you that my view just getPosts but maybe i did not explain good, I want separation of the business logic from the view of course, my problem logically formulated is this
I changed the name of the methods with more clean code procedures, please if possible remain the post in the Java forum, because is really a Java thing, no need any Android help.
thank you again