Difference between revisions of "User:AperfectBot"

From Geohashing
imported>Aperfectring
(→‎Tasks Remaining)
(under new management)
 
(113 intermediate revisions by 8 users not shown)
Line 1: Line 1:
−
This bot is owned by [[User:Aperfectring|aperfectring]].  Its job is to maintain the future and recent past [[Geo Hashing:Current events|planning pages lists]], and to create new planning pages upon request.
+
{{quote||The AI does not hate you, nor does it love you, but you are made out of atoms which it can use for something else.|Eliezer Yudkowsky}}
  
−
==What should the Bot be named?==
+
This bot was created by [[User:Aperfectring|aperfectring]], who also maintained and hosted it until 2023. Since then, it is hosted by [[User:Fippe|Fippe]]. It is implemented on top of pywikipediabot, and its job is to maintain the daily expeditions lists, as well as the expedition lists on [[Geohashing:Current events]]. It also is able to create both per-user and per-graticule expedition lists.  See [[Help:AperfectBot]] for more information.
−
The most pressing issue right now is what to call my bot.  Voice your opinion or add new name suggestions below! --[[User:Aperfectring|aperfectring]] 18:55, 12 June 2009 (UTC)
 
−
*ApeRobot - Vaguely similar to my nick, and my favorite option.
 
−
*APRBot - Much more representative of who owns it.
 
−
*RingBot
 
−
*[[User:AperfectBot|AperfectBot]] - '''Robyn's''' favorite. relet's too. <---Winner
 
  
−
:Considering that I didn't realize who "APR" was in the chatroom for quite a while, and that the first line on the bot's page will be something like "This is a bot owned by Aperfectring," you might as well go with your first choice. Also: Ringbot, Aperfectbot. (The last is my favourite). -[[User:Robyn|Robyn]] 19:01, 12 June 2009 (UTC)
+
== Much Thanks ==
−
 
+
* The uses some code <s>stolen from</s> graciously donated by [[User:ReletBot|relet]], and he also provided source control before the move to github.  We have started to merge some code which we were sharing, to create a common library of useful geohashing wiki functions. We hope these functions will help facilitate easier development of new bots, and also improve the overall quality of all bots which use it.
−
*BotheRing
+
* [[User:Robyn|Robyn]] came up with the original idea, and provided some great input early in its development.
−
*SpideRing - '''Xore''''s vote. In my opinion, the name has a certain ring to it that I like. --[[User:Xore|Xore]] 21:29, 12 June 2009 (UTC)
+
* [[User:Jiml|Jiml]] hosted and ran the bot while I moved across the country and scrambled for internet access.
−
 
+
* All others who helped with the planning and suggestions for improvement.
−
: My contributions --[[User:Xore|Xore]] 20:40, 12 June 2009 (UTC)
+
The bot wouldn't have been completed nearly so quickly, or gotten to be the dumb ape it is without all of you. Thanks.
−
::That's the other thing I like about wiki. Everyone pitches in to solve important issues. -[[User:Robyn|Robyn]] 22:56, 12 June 2009 (UTC)
 
−
*johnny
 
  
 
== How it works at the moment I edited this ==
 
== How it works at the moment I edited this ==
−
It looks at Category:Expedition_planning, and finds all pages in it which have a title that matches: YYYY-MM-DD lat lon
+
It looks at Category:Meetup on YYYY-MM-DD for the most recent days, and all days where coords are available, and finds all pages in it which have a title that matches: YYYY-MM-DD lat lon
  
−
It looks at each of those pages for users, and a location, it also looks up the graticule name from the All_Graticules page.
+
It also looks at Category:Expedition_planning for all pages matching YYYY-MM-DD lat lon where the date is further in the future than the latest available coordinates.
−
===Users===
 
−
It looks for a "people" or "participants" header
 
  
−
If found, it assumes one user per line, and lists the users as one of the two things:
+
[[User:AperfectBot/Changing_the_output|Go here]] for information about how it constructs the summary.
  
−
*The User:* tag found at the beginning of the line
+
The bot takes somewhere around 10-15 minutes to complete one iteration.  Most of this time is actually fetching and writing the pages, the actual processing time is rather minimal.
  
−
*The first word of the line
+
== Updates to functionality ==
 +
I'll try to keep this up to date with what changes I make on the Ape, but the best place to look is the github repo, as that will be maintained much more often.
  
−
If no header is found, it looks for all User:* tags, and lists all unique occurrences
+
=== 2010-04-28 ===
 +
I added dynamic support for holidays, instead of the previous static one, which I never added holidays to.  Holidays included are:
 +
* Geohashing Day
 +
* Mouseover Day
 +
* DJIA holidays (for the day they actually fall on, not when DJIA observes them)
 +
* Easter Sunday (Came for free with DJIA Good Friday holiday)
 +
* Pi Day
 +
* Talk Like A Pirate Day
  
−
If at this point, still no user is found, it assumes there is none, and uses the following text: "Unknown, maybe you?"
+
The ape should be able to identify these holiday on its own forever!
  
−
===Location===
+
==Tasks Remaining==
−
It looks for a "location" or "where" header
+
These are in rough order of importance
 +
* Review and possibly improve the fuzzy logic to the library user list function. (ongoing, for continuous improvement)
 +
* Improve transport detection.
 +
* Look into either signing up for access to a server, or convince one of our friendly neighborhood geohashers with a server to let me have access to update and run this, as well as the Notification program, from it.
 +
* Sort the results for each day using an undetermined key to sort on
 +
* Let AperfectBot eat bananas
  
−
If found, it takes up to the first 50 characters of the section, and appends ... to the result if the string is more than 50 characters long.
+
=== Task scheduling ===
 +
I will use this section to plan out my time in the evening on tasks.  I will probably put in an hour or two of work on most weekdays. Anything from before 2009-06-17 is included for historical purposes. The bot is live!  Anything I will be doing from now on is new features, bug fixes, or improvements to output.
  
−
If not found, it starts at the beginning of the page, and tries that same 50 char thing.
+
==== 2010-01-27 ====
 +
* The window is now about 10 seconds each run, which is currently lasting about 6 minutes.
  
−
If still not found, it jumps into the first section and tries again.
+
==== 2010-01-26 ====
 +
* Fixed user texts so that there is a much better chance they will be preserved.  The window is still measurable, but much smaller than it used to be.
  
−
Finally, if there is still no text, it will use this: "Unknown, why not have a spontaneous adventure?"
+
==== 2010-01-14 ====
 +
[[User:Aperfectring/Expeditions]] is updating with a new format: <pre>
 +
|-
 +
|DATE||GRATADD||GRATNAME||PEOPLE||REACHED:[[EXPED|Succeeded]]:[[EXPED|Failed]]:REACHED||LOCATION
 +
</pre>
 +
With the text before and after the update area, this results in a sortable table of expeditions!
  
−
*It looks to me like 50 characters isn't quite enough for a lot of the location descriptions, so I will up it to 75, or maybe 100 today.  Also, I will explicitly strip out any section headers which mysteriously weren't trimmed out before. --[[User:Aperfectring|aperfectring]] 11:51, 17 June 2009 (UTC)
+
Added some new options:
 +
PEOPLE:x - where x is any number - Will display at most x people in the list.  Otherwise operates exactly like PEOPLE
 +
TRANSICON - Will display icons for all transport options detected.
 +
REACHICON - Will display either a green (SUCCESS) or red (FAILURE) arrow icon
  
−
===Name===
+
USERTEXT is now preserved across runs.
−
If the name isn't found in All_Graticules, it calls the graticule "Unknown (lat, lon)"
 
−
 
 
−
===Summary===
 
−
This seems to be able to produce something meaningful for just about every old planning page where something meaningful can be made. --[[User:Aperfectring|aperfectring]] 02:27, 16 June 2009 (UTC)
 
−
 
 
−
==Tasks Remaining==
 
−
* Put the code into source control somewhere
 
−
* Sectionalize the results by date
 
−
* Limit the list to 3 days past, the present day, and as many future days are available
 
−
* Parse Meetup on *DATE* pages to look for uncategorized expeditions, and categorize them as Expedition planning.
 
−
** I will include a comment that this category was added by a bot, and if it does not apply, to add at least one of any other appropriate categories for an expedition page
 
−
** In the bot, this should be done before parsing the Expedition planning page, so that any new expeditions it finds will be added to the list ASAP.
 
−
* Create a list of graticule and graticule talk pages on which planning occurs
 
−
** Create a parsing engine for these pages, to be able to include their plans in the list
 
−
* Sort the results for each day using an undetermined key to sort on
 
−
 
 
−
=== Task scheduling ===
 
−
I will use this section to plan out my time in the evening on tasks.  I will probably put in an hour or two of work on most weekdays.  Anything from before 2009-06-17 is included for historical purposes.
 
−
==== 2009-06-17 ====
 
−
* Tweak the length of location descriptions
 
−
* Trim out the extra instances of header boundaries in the location descriptions
 
−
* Begin work on sectionalizing the results by date
 
−
* Possibly start the bot in a continuous loop, which means that it will provide updates about every 30 minutes, if needed.  I will leave this going overnight and while I am at work the next day, if I do it.
 
  
−
==== 2009-06-16 ====
+
Added ability for multiple users/formats to be specified. See [[User:Relet/Expeditions]] for proof.  Users, expedition list pages, and formats need to be specified here: [[User:AperfectBot/User_expedition_lists]]
−
* Fix up some location parsing.
 
−
* Status: Did some work on it, but not a whole lot
 
  
−
==== 2009-06-15 ====
+
==== 2009-12-02 ====
−
* Look for more options as far as people going
+
* I have started work on creating per-user expedition lists.  Currently it is making a list for [[User:Aperfectring|Aperfectring]] [[User:Aperfectring/Expeditions|here]].  The entries of this list are currently generated using the following format, but it is likely to change in the future:
−
* Look for more options as far as the location the hashpoint is in
+
date DATE - gratadd GRATADD - gratname GRATNAME - people PEOPLE - location LOCATION - transport TRANSPORT - reached REACHED:Succeeded:Failed:REACHED - reason REASON - link LINK - exped EXPED - usertext USERTEXT
−
* Status: The user list may get a little better with time, but its quite close at this point.  There is still work to be done on the location.
+
* Features:
 +
** The reached section is replaced first, so it is able to contain other substitutions seamlessly.  It is used as follows: REACHED:1:2:REACHED  The text in '1' is used on reached coordinates, '2' otherwise.
 +
** USERTEXT will be preserved across updates of the bot, allowing people to make their own comments about their expeditions.
 +
** PEOPLE will contain all of the rest of the people who attended the expedition.
 +
** The use of a format string allows for great flexibility in how the final output is displayed.
 +
** Expeditions are sorted lexicographically by the expedition page name (YYYY-MM-DD LAT LON).  This has the affect of being chronological by date, then pseudo geographical in the following order: Southern hemisphere first, Northern second.  Then roughly equator to poles, though there will be some mixing.  After that, it will do Western hemisphere first, Eastern second.  Then roughly prime meridian to "date line".
 +
* Caveats and current implementation holes:
 +
** Hardcoded to only update for Aperfectring.
 +
** Hardcoded to one specific page to update.
 +
** Hardcoded to the format noted above.
 +
** USERTEXT is currently not preserved across updates.
 +
** The page is completely rewritten each time, which prevents people from having non user list text before or after the user list.
  
−
==== 2009-06-14 ====
+
==== 2009-11-03 ====
−
* Status: 100% less shouting on the page
+
* Put the bot into source control
 +
* Added a getSectionRegex function
 +
* Updated the getSection* functions to be able to operate on just the top level sections or all subsections with an option
 +
* Updated the ape to use the common GraticuleDatabase library
 +
* Updated the ape to use the getSection* functions from the library
  
−
==== 2009-06-13 ====
+
==== Older stuff ====
−
* More thorough planning
+
Go [[User:AperfectBot/Change_history|here]] to see older change history.
−
* Begin coding in earnest
 
−
* Status: By the end of the day, I had a very basic parser, which wrote the full contents of '''Category:Expedition planning''' to [[User:AperfectBot/Test_Page| a page on the wiki]].
 
  
−
==== 2009-06-12 ====
+
= EMERGENCY STOP SECTION =  
−
* Begin preliminary planning
+
Putting any text beneath the following header will cause the bot to stop running.  Please only do so if the bot is REALLY misbehaving.
  
−
--[[User:Aperfectring|aperfectring]] 12:05, 17 June 2009 (UTC)
+
==Distraction Banana==
−
===Other people's thoughts===
 
−
If anyone else has ideas for things to be included in the bot, please put them here. Thanks. --[[User:Aperfectring|aperfectring]] 12:05, 17 June 2009 (UTC)
 

Latest revision as of 19:03, 19 March 2023

“
The AI does not hate you, nor does it love you, but you are made out of atoms which it can use for something else.
 ”
—Eliezer Yudkowsky

This bot was created by aperfectring, who also maintained and hosted it until 2023. Since then, it is hosted by Fippe. It is implemented on top of pywikipediabot, and its job is to maintain the daily expeditions lists, as well as the expedition lists on Geohashing:Current events. It also is able to create both per-user and per-graticule expedition lists. See Help:AperfectBot for more information.

Much Thanks

  • The uses some code stolen from graciously donated by relet, and he also provided source control before the move to github. We have started to merge some code which we were sharing, to create a common library of useful geohashing wiki functions. We hope these functions will help facilitate easier development of new bots, and also improve the overall quality of all bots which use it.
  • Robyn came up with the original idea, and provided some great input early in its development.
  • Jiml hosted and ran the bot while I moved across the country and scrambled for internet access.
  • All others who helped with the planning and suggestions for improvement.

The bot wouldn't have been completed nearly so quickly, or gotten to be the dumb ape it is without all of you. Thanks.

How it works at the moment I edited this

It looks at Category:Meetup on YYYY-MM-DD for the most recent days, and all days where coords are available, and finds all pages in it which have a title that matches: YYYY-MM-DD lat lon

It also looks at Category:Expedition_planning for all pages matching YYYY-MM-DD lat lon where the date is further in the future than the latest available coordinates.

Go here for information about how it constructs the summary.

The bot takes somewhere around 10-15 minutes to complete one iteration. Most of this time is actually fetching and writing the pages, the actual processing time is rather minimal.

Updates to functionality

I'll try to keep this up to date with what changes I make on the Ape, but the best place to look is the github repo, as that will be maintained much more often.

2010-04-28

I added dynamic support for holidays, instead of the previous static one, which I never added holidays to. Holidays included are:

  • Geohashing Day
  • Mouseover Day
  • DJIA holidays (for the day they actually fall on, not when DJIA observes them)
  • Easter Sunday (Came for free with DJIA Good Friday holiday)
  • Pi Day
  • Talk Like A Pirate Day

The ape should be able to identify these holiday on its own forever!

Tasks Remaining

These are in rough order of importance

  • Review and possibly improve the fuzzy logic to the library user list function. (ongoing, for continuous improvement)
  • Improve transport detection.
  • Look into either signing up for access to a server, or convince one of our friendly neighborhood geohashers with a server to let me have access to update and run this, as well as the Notification program, from it.
  • Sort the results for each day using an undetermined key to sort on
  • Let AperfectBot eat bananas

Task scheduling

I will use this section to plan out my time in the evening on tasks. I will probably put in an hour or two of work on most weekdays. Anything from before 2009-06-17 is included for historical purposes. The bot is live! Anything I will be doing from now on is new features, bug fixes, or improvements to output.

2010-01-27

  • The window is now about 10 seconds each run, which is currently lasting about 6 minutes.

2010-01-26

  • Fixed user texts so that there is a much better chance they will be preserved. The window is still measurable, but much smaller than it used to be.

2010-01-14

User:Aperfectring/Expeditions is updating with a new format: 

|-
|DATE||GRATADD||GRATNAME||PEOPLE||REACHED:[[EXPED|Succeeded]]:[[EXPED|Failed]]:REACHED||LOCATION

With the text before and after the update area, this results in a sortable table of expeditions!

Added some new options: PEOPLE:x - where x is any number - Will display at most x people in the list. Otherwise operates exactly like PEOPLE TRANSICON - Will display icons for all transport options detected. REACHICON - Will display either a green (SUCCESS) or red (FAILURE) arrow icon

USERTEXT is now preserved across runs.

Added ability for multiple users/formats to be specified. See User:Relet/Expeditions for proof. Users, expedition list pages, and formats need to be specified here: User:AperfectBot/User_expedition_lists

2009-12-02

  • I have started work on creating per-user expedition lists. Currently it is making a list for Aperfectring here. The entries of this list are currently generated using the following format, but it is likely to change in the future:
date DATE - gratadd GRATADD - gratname GRATNAME - people PEOPLE - location LOCATION - transport TRANSPORT - reached REACHED:Succeeded:Failed:REACHED - reason REASON - link LINK - exped EXPED - usertext USERTEXT
  • Features:
    • The reached section is replaced first, so it is able to contain other substitutions seamlessly. It is used as follows: REACHED:1:2:REACHED The text in '1' is used on reached coordinates, '2' otherwise.
    • USERTEXT will be preserved across updates of the bot, allowing people to make their own comments about their expeditions.
    • PEOPLE will contain all of the rest of the people who attended the expedition.
    • The use of a format string allows for great flexibility in how the final output is displayed.
    • Expeditions are sorted lexicographically by the expedition page name (YYYY-MM-DD LAT LON). This has the affect of being chronological by date, then pseudo geographical in the following order: Southern hemisphere first, Northern second. Then roughly equator to poles, though there will be some mixing. After that, it will do Western hemisphere first, Eastern second. Then roughly prime meridian to "date line".
  • Caveats and current implementation holes:
    • Hardcoded to only update for Aperfectring.
    • Hardcoded to one specific page to update.
    • Hardcoded to the format noted above.
    • USERTEXT is currently not preserved across updates.
    • The page is completely rewritten each time, which prevents people from having non user list text before or after the user list.

2009-11-03

  • Put the bot into source control
  • Added a getSectionRegex function
  • Updated the getSection* functions to be able to operate on just the top level sections or all subsections with an option
  • Updated the ape to use the common GraticuleDatabase library
  • Updated the ape to use the getSection* functions from the library

Older stuff

Go here to see older change history.

EMERGENCY STOP SECTION

Putting any text beneath the following header will cause the bot to stop running. Please only do so if the bot is REALLY misbehaving.

Distraction Banana

Retrieved from "https://geohashing.site/index.php?title=User:AperfectBot&oldid=864337"
Powered by MediaWiki