Update config example and docs to use SpeedScan default and full names

RocketMap · Feb 20, 2018 · fcf8e59 · fcf8e59
1 parent e074970
commit fcf8e59
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 10 deletions.
diff --git a/config/config.ini.example b/config/config.ini.example
@@ -46,7 +46,7 @@
 #db-threads:                    # Number of db threads; increase if the db queue falls behind. (default=1)
 
 
-# Scan method (speed preferable, (default is hex)
+# Scan method (speed preferable, (default is SpeedScan)
 #############
 #scheduler: SpeedScan            # Use speed-scan as the search scheduler.
                                 # This is the recommended Scheduler for most uses.

diff --git a/docs/first-run/commandline.md b/docs/first-run/commandline.md
@@ -247,20 +247,20 @@ environment variables which override config file values which override defaults.
       -nk, --no-pokestops   Disables PokeStops from the map (including parsing
                             them into local db). [env var: POGOMAP_NO_POKESTOPS]
       -sch, --scheduler
-                            Sets the method of scanning (default: hex)
-                            ''speed''
+                            Sets the method of scanning (default: SpeedScan)
+                            ''SpeedScan''
                             Recommended value for normal scanning of pokémon.
                             Identify spawn points and then scan closest spawns.
-                            ''hex''
+                            ''HexSearch''
                             Default scan method, scans all cells around 
                             location based on step size 
-                            ''skip-empty''
+                            ''HexSearchSpawnpoint''
                             Requires previously populated database. Scans only
                             hex cells that aren't empty.
-                            ''spawnpoint''
+                            ''SpawnScan''
                             Use spawnpoint scanning (instead of hex grid). Scans
                             in a circle based on step_limit when on DB.
-                            ''fort''
+                            ''FortSearch''
                             Requires previously populated database. 
                             Cluster and scan only gyms and/or pokestops. 
                             [env var: POGOMAP_SCHEDULER]

diff --git a/docs/scanning-method/fort-scheduler.md b/docs/scanning-method/fort-scheduler.md
@@ -20,7 +20,7 @@ Fort Scheduler is only meant to be run after a database has been populated with
 
 What command line args should I use for scanning gyms only?
 
-> Here's an example: `runserver.py -fs -np -nk -sd 60 -w 10 -ac accounts.csv`
+> Here's an example: `runserver.py -sch FortSearch -np -nk -sd 60 -w 10 -ac accounts.csv`
 
 How big should I make my -st?
 
@@ -46,8 +46,8 @@ We have 200 gyms we want to scan:
 
  ` 126 gyms / 6 gyms per minute per worker = ` 21 workers  
 
-arguments: `runserver.py -fs -np -nk -sd 10 -w 21`
+arguments: `runserver.py -sch FortSearch -np -nk -sd 10 -w 21`
 
 If we allow each gym to only be scanned every 2nd minute, was can reduce the workers to 10
 
-arguments: `runserver.py -fs -np -nk -sd 10 -w 10`
+arguments: `runserver.py -sch FortSearch -np -nk -sd 10 -w 10`