From Geo Hashing
- I did some refactoring on the parsing engine. It is now a bit more flexible in how it is looking at the expedition page sections, but lost the ability to look into the first section for location descriptions. None of the pages currently on the current events page encountered any change because of that change. I am much more happy about the quality of the new code, and since it is more generic, it should facilitate easier development of new bots or extensions to this bot. The new code is a generic section/subsection parser. It is actually two functions, one which will return the body of a section with the name provided, and one which will return all sections and their bodies as a hash where SectionTitle->Body. What initially prompted me to do this is a request/offer of the user list generator part of the bot for a new bot relet is creating, and I am quite happy with how it turned out.
- Move the help text to Help:AperfectBot and don't have the bot create the section.
- The summaries have been added to the Main Page and if more than 4 would appear on that page, then a "More summaries..." link is put in their place.
- An "Update this list" link has been added to date pages.
- All old expedition summaries have been created. Date pages have been updated to include the summaries as well. The next step is to move the update request to someplace more permanent, and provide an edit link. That will be done after this weekend.
- There appears to be some issue with writing to the old date pages. Until I can figure out what is causing it, the updates on old date pages will be on hold. Anything on the current events page should be updated as normal, or with minimal delay.
- I fixed another bug in the list with user lists.
- And another where the bot was stripping links from location descriptions.
- I also added the ability to specify old dates to update. I am running a test here which should update all date pages this year with the appropriate summaries.
- Date pages should now be automatically created for all dates from $TODAY into the future. They will be overwritten for all dates the current day US ET forward that are on the list. They will only be written between the hours of 9AM and 10AM US ET.
- I fixed some cases where users' names would show up in the user list multiple times. Let me know if you still see cases where the same user shows up twice.
- Create date pages (YYYY-MM-DD) if they don't already exist.
- Move the output from its current location, to a template: Template:Recent_expeditions
- Change the old output page into a transclusion tag, to preview what the final results on the current events page will look like.
- Add includeonly tags around a "provide your own update" link, which goes to an edit page.
- Add a "How to change the text of my planning/expedition summary" link, which should be to a simple, user-friendly description of how it chooses the text, and how someone would go about changing it.
- Add a "Report a problem" link to the list.
- Code fix on writing pages to make them a bit faster.
- Status: The content for point 4 is here. Point 1&2 now complete. Point 5 done, time is now about 8 minutes between updates instead of 12.
- Status2: Everything in the list should be done now. Please look the output page over. Thanks.
- Start using templates and transclusion.
- This should (at least in my deranged mind) make dealing with user edits to the daily lists easier to cope with.
- Add at least some user modification of the list
- Status: The first part seems to be mostly in place, the only part of that which is left is to write the output which is now here to a template page. I also think I have something ready for test on the second point. I also added a hook which will allow us to enhance the date links with holidays.
- Switching to a new set of categories as follows:
- Category:Meetup on YYYY-MM-DD for anything from the latest available back to the first in the list
- Category:Expedition planning for anything further in the future than the latest available
- Still looking for the best way to figure out the last the coords are available for.
- My current thought is to use the python implementation posted here.
- Status: The above is complete. The bot also will create empty date stubs now. I am now looking for input on my update below.
- More planning on picking the dates to report.
- My current thought is to report everything from Expedition planning from three weekdays ago, until the latest available coordinates. This gives people a bit more time to report on a potentially geohash-busy weekend, but means that the number of days in the recent past list is not constant. This table assumes no DOW holidays.
Today (US Eastern Time) First day reported Last day reported Sunday Wednesday Monday Monday Wednesday Tuesday Tuesday Thursday Wednesday Wednesday Friday Thursday Thursday Monday Friday Friday Tuesday Monday Saturday Wednesday Monday
- Another option is to have a fixed number of past days in the list (let's say 3), and all days where coordinates are available. This keeps the recent past list a constant size, but if people are busy geohashing on weekends, their expedition planning could drop off the page before it is reported on. This table assumes no DOW holidays.
Today (US Eastern Time) First day reported Last day reported Sunday Thursday Monday Monday Friday Tuesday Tuesday Saturday Wednesday Wednesday Sunday Thursday Thursday Monday Friday Friday Tuesday Monday Saturday Wednesday Monday
- If I get some decent feedback on which of the above is best, I will begin coding on it.
- Figure out how to determine what days there are coordinates available for.
- Status: I am now using the first option, and parsing both Category:Expedition planning and Category:Expeditions. It now updates about every 7 minutes with the truncated date list.
- Reverse the sort of the dates
- Plan out how to pick the dates to report
- Status: first point done, second still in progress.
- 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.
- Status: All of the above complete. Let me know if the bot misbehaves. If it starts misbehaving really badly, use the Distraction Banana section below.
- Fix up some location parsing.
- Status: Did some work on it, but not a whole lot
- Look for more options as far as people going
- Look for more options as far as the location the hashpoint is in
- 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.
- Status: 100% less shouting on the page
- More thorough planning
- 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 a page on the wiki.
- Begin preliminary planning
--aperfectring 12:05, 17 June 2009 (UTC)