Difference between revisions of "Challenge difficulty"

From Project-GC
Jump to: navigation, search
(Initial edit)
 
(Added info about the module in profile stats. Also changed every->most (as not all checkers have a difficulty).)
 
(19 intermediate revisions by 4 users not shown)
Line 1: Line 1:
For every [[Challenge checker]] in the system there is a *Challenge difficulty* calculated. The difficulty is based on on how many [[Geocacher]]s fulfill the challenge or not. Project-GC is running [[Challenge checker]]s in the background for tenths of thousands of [[Geocacher]]s in the background, this process is a part of the [[Auto-Challenge-Checker System]]. The result of these runs is used to calculate the *Challenge difficulty*.
+
==What is it?==
 +
For most [[Challenge checker]]s in the system there is a ''Challenge difficulty'' calculated. The difficulty is based on on how many [[Geocacher]]s fulfill the challenge or not. Project-GC is running [[Challenge checker]]s in the background for tens of thousands of [[Geocacher]]s, this process is a part of the [[Auto-challenge-checkers|Auto-Challenge-Checker System]]. The result of these runs is used to calculate the ''Challenge difficulty''.
  
Basically the *Challenge difficulty* tells us how big share of the [[Geocacher]]s fulfill a challenge or not. The rating is an integer between 0 and 100, but should not be confused with percent. First off it's important to understand that the automatic challenge checker runs aren't automatically executed on the average [[Geocacher]], but more likely on the more hardcore [[Geocacher]]s. It's primarily executed on [[Geocacher]]s with more finds, regular users of [[Project-GC]] and also [[Paid membership|paid members]] of the site.
+
==How is it calculated?==
 +
Basically the ''Challenge difficulty'' tells us what proportion of [[Geocacher]]s fulfill a challenge or not. The rating is an integer between 0 and 100, but should not be confused with percent. First off it's important to understand that the automatic challenge checker runs aren't automatically executed on the average [[Geocacher]], but more likely on the more hardcore [[Geocacher]]s. It's primarily executed on [[Geocacher]]s with more finds, regular users of [[Project-GC]] and also [[Paid membership|paid members]] of the site. With this in mind we know that the result isn't representing the average geocacher, on the other hand, challenges generally aren't targeting the average geocacher either.
  
Then the [[Geoacher]]s the checker has been run on is divided into three categories:
+
The [[Challenge checker]] results are dividing into three categories:
* Region - [[Geocacher]]s that are determined to live in the same **region** as the [[Challenge]] itself.
+
* Region - [[Geocacher]]s that are determined to live in the same '''region''' as the [[Challenge]] itself.
* Country - [[Geocacher]]s that are determined to live in the same **country** as the [[Challenge]] itself, but not in the same region.
+
* Country - [[Geocacher]]s that are determined to live in the same '''country''' as the [[Challenge]] itself, but not in the same region.
 
* World - All others
 
* World - All others
  
For each category a percent of how many fulfills the [[Challenge]] is calculated. Then the results for each group is weighted different in the calculations, basically a list is created and the percentages are added into that list. The percentage of *world geocachers* are added into the list 3 times, country 5 times, and region 10 times.
+
For each category a percentage of how many fulfill the [[Challenge]] is calculated. Then the results for each group is weighted different in the calculations, basically a list is created and the percentages are added into that list. A fourth factor is also added into the mix, the number of finds per day.
  
It should also be noted that there usually are more cached checker runs in the system from more local [[Geocacher]]s than from those living far away.
+
The number of finds per day isn't used as the raw number itself, but rather as '(1-($numFinds/$daysOld))*100'.
  
An example:
+
Then the difficulty is calculated as '$difficulty = (3*$worldPercent + 5*$countryPercent + 10*$regionPercent + $findsPerDay) / (3+5+10+1)'.
 +
 
 +
It should also be noted that there usually are more calculated [[challenge checker]] results in the system from more local [[Geocacher]]s than from those living far away.
 +
 
 +
===Example===
 
* The Challenge is placed in Texas, United States.
 
* The Challenge is placed in Texas, United States.
* 80% of the [[Geocacher]]s in Texas fulfills it.
+
* 80% of the [[Geocacher]]s in Texas fulfill it.
* 40% of the [[Geocacher]]s in the other states of the United States fulfills it.
+
* 40% of the [[Geocacher]]s in the other states of the United States fulfill it.
* 30% of the [[Geocacher]]s in the rest of the world fulfills it.
+
* 30% of the [[Geocacher]]s in the rest of the world fulfill it.
* A list containing these values are created: 30,30,30,30,30,30,30,30,30,30, 40,40,40,40,40, 80,80,80
+
* The challenge is one year old (365 days) and have had 10 finds during this period.
* The *Challenge difficulty* ends up being 740/18 = 41.11, which is rounded down to 41. The values are always rounded down to the closest integer.
+
* Then to weigh these differently using coefficients a sum is created like this: 3*80+5*40+10*30+((1-(10/365))*100).
 +
* This sum is then divided by 19 (3+5+10+1, the last being related to findsPerDay).
 +
* The ''Challenge difficulty'' ends up being 837.26/19 = 44.066, which is rounded down to 44. The values are always rounded down to the closest integer.
 +
 
 +
==Related statistics==
 +
[[Challenge difficulty per rating interval]] shows the correlation between the [[D/T|difficulty rating]] of the geocache and the challenge difficulty.
 +
 
 +
The [[Challenges_tab#Challenge_difficulties|challenge tab]] in the profile stats has a module for challenge difficulties.
 +
 
 +
[[Category:Site Info]]

Latest revision as of 22:40, 26 April 2024

What is it?

For most Challenge checkers in the system there is a Challenge difficulty calculated. The difficulty is based on on how many Geocachers fulfill the challenge or not. Project-GC is running Challenge checkers in the background for tens of thousands of Geocachers, this process is a part of the Auto-Challenge-Checker System. The result of these runs is used to calculate the Challenge difficulty.

How is it calculated?

Basically the Challenge difficulty tells us what proportion of Geocachers fulfill a challenge or not. The rating is an integer between 0 and 100, but should not be confused with percent. First off it's important to understand that the automatic challenge checker runs aren't automatically executed on the average Geocacher, but more likely on the more hardcore Geocachers. It's primarily executed on Geocachers with more finds, regular users of Project-GC and also paid members of the site. With this in mind we know that the result isn't representing the average geocacher, on the other hand, challenges generally aren't targeting the average geocacher either.

The Challenge checker results are dividing into three categories:

  • Region - Geocachers that are determined to live in the same region as the Challenge itself.
  • Country - Geocachers that are determined to live in the same country as the Challenge itself, but not in the same region.
  • World - All others

For each category a percentage of how many fulfill the Challenge is calculated. Then the results for each group is weighted different in the calculations, basically a list is created and the percentages are added into that list. A fourth factor is also added into the mix, the number of finds per day.

The number of finds per day isn't used as the raw number itself, but rather as '(1-($numFinds/$daysOld))*100'.

Then the difficulty is calculated as '$difficulty = (3*$worldPercent + 5*$countryPercent + 10*$regionPercent + $findsPerDay) / (3+5+10+1)'.

It should also be noted that there usually are more calculated challenge checker results in the system from more local Geocachers than from those living far away.

Example

  • The Challenge is placed in Texas, United States.
  • 80% of the Geocachers in Texas fulfill it.
  • 40% of the Geocachers in the other states of the United States fulfill it.
  • 30% of the Geocachers in the rest of the world fulfill it.
  • The challenge is one year old (365 days) and have had 10 finds during this period.
  • Then to weigh these differently using coefficients a sum is created like this: 3*80+5*40+10*30+((1-(10/365))*100).
  • This sum is then divided by 19 (3+5+10+1, the last being related to findsPerDay).
  • The Challenge difficulty ends up being 837.26/19 = 44.066, which is rounded down to 44. The values are always rounded down to the closest integer.

Related statistics

Challenge difficulty per rating interval shows the correlation between the difficulty rating of the geocache and the challenge difficulty.

The challenge tab in the profile stats has a module for challenge difficulties.