How are Highlighted Scenes Decided?

[Nxdt]

So thats my question...
Here is why i'm asking it. I have just uploaded a scene and i'm refreshing that page to see how many downloads/comments are going on, when at only 4 downloads, no comments and no (Additional) ratings it appears in the First slot of the Highlighted scenes. This kind of led me to question how these scenes are chosen, are they chosen by a mod, or are they selected with script?

[Chronos]

I'm pretty certain it's a (completely biased) script.

[TC42]

I think the script is based off # ratings, #comments, # downloads, regardless of whether the comments are good or not..

[Dare]

It looks like it is simply based on rating and downloads. Probably not comments.

[Gear97]

Well, my guess is that if the scene receives a large amount of downloads in a relative short period of time the script selects this scene to be highlighted. When I upload my scenes it seems that this is what happens
I already saw various scenes with downloads below 100, but that appeared in the highlighted and they were pretty recent to time I was seeing them.
Well this just a GUESS.

[Nxdt]

I think that gear probably has the right explaination, This would stop any older scenes appearing and seems a flawless way to get the most popular scenes of the moment.

[Someone Else]

Perhaps it's something like this: For all the scenes uploaded in the past month, an index is calculated based on all or part of what TC42 said, with the possible addition of what Gear97, which deals with the concentration of ratings, comments, or downloads in time.

Or perhaps the index is calculated based on an uber-complicated-machine-learning-program that objectively calculates the quality of the scene based on the PHN file.

In any case, the index, minus (or divided by? Some nonsensical math based on logs, quartic terms, and trig?) the age of the scene, equals the probability of the scene being highlighted.

[Emanuel]

Highlighted scenes are scenes from seven days back in time that are first sorted by ratings and then by

Code: Select all

The number of ratings + the number of downloads/40 + the number of views/20

/ Emanuel

[Nxdt]

Thanks for clearing that up. But i still don't understand how a scene with only 4 downloads, the default rating and 3 views was in there, is there a random element???

[Dare]

Probably because on that day, there were not any good scenes to be highlighted? Maybe...

[electronicboy]

or maybe even a bad week for uploads...
(lots of low rated scenes, yet small number of uploads)

[Someone Else]

Again, thanks for clarifying.

What's the threshold for ratings that are close enough together for the above script to take place? That is,

Code: Select all

scene.my.decision = (scene1, scene2, threshold)=>{{rating1 > rating2} ? {
    {scene1(0) - scene2(0) < threshold} ? {scene.my.finalDecision(scene1, scene2)} : {1}
} : {
    {scene2(0) - scene1(0) < threshold} ? {scene.my.finalDecision(scene1, scene2)} : {2}}
};

scene.my.finalDecision = (scene1, scene2)=>{scene.my.decision([
    scene1(1) + (scene1(2) / 40) + (scene1(3) / 20)
], [
    scene2(1) + (scene2(2) / 40) + (scene2(3) / 20)
], 0)};

//The scene arrays follow this syntax: [rating_float, ratings_int, downloads_int, views_int]


What exactly are scene views? Can't be how many times someone looks at the scene description page- one of my recent scenes actually had more downloads...

[Emanuel]

What exactly are scene views? Can't be how many times someone looks at the scene description page- one of my recent scenes actually had more downloads...

It is the number of times someone (except the creator) looks at the scene page, but a scene can be downloaded directly from the start or search page.

/ Emanuel

[electronicboy]

scene view's, are when a user actually visits the page for the scene
(the page where it shows scene description and comments).

The reason why you had more downloads than scene views, is because of people using the download button on the main algodoo page.

Edit: damn! Emanuel beat me by a minute!

[Someone Else]

I see. Well... So a scene view is exactly what I thought it wasn't.

But that doesn't answer my other question. The above codes will output 1 or 2, depending on which scene specs are higher-ranked. 1 is the first scene, 2 is the second.

So what is the appropriate value for the third argument in scene.my.decision? Assuming my codes are correct...

*checking*

Oh wow. Toward the right end of the first line of scene.my.decision, you'll see {rating1 > rating2}.
This should be {scene1(0) > scene2(0)}.