WizAnn Books App Manual

WizAnn Books App Manual
The basic structure of the application is a call-over system, in conjunction with the WizAnn
books, blue books, missing pieces, cross sections, football runs, livery halls, bankers, strike
runs and other run books, this will allow for the application to import purchased books from
WizAnn and then for them to remain updated via a single update file. There is always a
balance to be struck with flexibility and security, e.g. copyright protection of the runs is
important, but also the need to export and import custom runs to/from other people, so to get
the balance right, all the imported WizAnn books are not exportable, but your custom runs are,
so they can be shared.
Calling runs falls into two distinct categories for me, learning the runs, and calling them over,
in my previous testing of myself over a couple of years of calling over the following pattern
was noted, that when runs had only been called a few times, I needed to repeat them more
frequently, once I had called a run in excess of 20 times, I could widen the calling frequency to
about once every 10 days and still keep the same level of fluency, once I had called a run more
than 50 times I could call it without thinking, of course these parameters are different for
everyone. I have build a calling frequency algorithm that goes something like this,
Correct calls.
1 = 1 Minute
2 = 4 Hours
3 = 8 Hours
4 = 1 Day
5 = 2 Days
6 = 4 Days
7 = 5 Days
8 = 7 Days
9 = 10 Days
10 = 20 Days
11 = 50 Days
If you call the same run correct without mistakes 8 times you will be calling the run every 7
days, any mistake and you go back to the start of the frequencies. There is a max calling
frequency this can be set per run, which ever figure is the lower is honoured. This is how timed
out runs occur.
You can if you wish call the runs in the books/lists in strict order if you wish, the choice is
yours (strict or random order is a global setting in the settings page), I find with the time out
system I am focusing more on the runs Im having trouble with, rather than the runs that I
have no problem with, meaning that my time is better spent focusing on issues rather than
over repeating well known stuff.
Setup right, you can just use the time out screen to call over from, adding tricky stuff each day
to memorise those.
The application is basically the same for the iPhone/iPod/iPad, the screen layouts change
depending on the device but the overall function is the same. For the purposes of this manual
all the screenshots will be from the iPad, but the same features are available on the iPhone.
This is the main screen.
This is a listing of all the books, you can create your own books, a word of warning, if you
create a blue book yourself this will not be updatable via the automatic update mechanism and
you will have to manually update all the runs yourself, whilst it is possible it is a lot of work to
keep these things in sync.
Clicking on the blue arrow on the right takes you to the list screen, here is a list of all the lists
in that book, it is possible to add runs that that level.
Options on this page, the action button top right, you can get to the App settings, shuffle the
runs, import/update runs, export runs.
Add book takes you to a screen to allow you to manually create a book.
(1) View timed out runs [number of runs that have timed out at this level], this takes
you to a screen where you can see all the timed out runs. The numbers are what has
timed out already, what is timing out in the next 1 hour, in the next 4 hours, in the next
12 hours and in the next day (24 hours).
(2) View virtual lists, this allows you to link to runs that you have already in the app, so
you could create virtual lists of runs you are having trouble with for example.
(3) View sticky runs, in the settings there is auto-sticky and auto-un-sticky settings when
both are set any run that is called in error is automatically marked as sticky (this can be
set manually as well), if you call a run enough times that the max timeout for the run is
reached e.g. 7 days then a run will automatically be un-sticky.
(4) View runs to be run, there is a flag on each run setting if you want to run the run,
this way you can build a list of runs that you are going to actually run.
(5) View pen and call runs, there is a setting that sets a run for pen and call on error,
you can also set this manually.
There is another button that can be displayed this is if the update file as updated any runs, this
button will be displayed so you can see which runs have been updated.
Clicking on a book the following menu appears.
1. Call book all, this will load up all the runs in the selected book, it will take the ordering
from the settings screen (strict or random order).
2. Call book completed, this will load up all the runs that have been marked as run in
the selected book, like above it will take the ordering from the settings screen.
3. View book, shows you the content of the book this is the same as clicking on the blue
arrow to the right of the list.
4. Edit book, this allows you to edit the details of the book.
5. Delete book, this deletes the book, all the lists and runs in the book, this cannot be
undone.
6. Ran all, this allows you to mark all the runs in the book as being run.
Settings
Setting options
Author, set this to your name (optional), any runs you create will then be embedded with
your name when you export your books.
Max days, this is a global max figure, no run timer can exceed this figure, so for instance you
could set this figure to 50 days, and then set individual books/runs to a lower figure, so blue
book must be called every 7 days, turnarounds every 20 for instance.
Auto sticky, setting this to on means when you call a run wrong it is automatically marked as
a sticky run.
Auto un-sticky, setting this to on means if a run is sticky and you call it enough times for it
to hit the max timeout for the run then it will automatically be un-stickyed.
Random Calling, any book, list or collections of runs the order will be randomised before
calling commences.
Bottom up, this means the calling over screen displays the roads from the bottom (bottom
up) of the screen rather than from the top (top down).
Alert no, this highlights counters that exceed this figure (this will in a future version alert you
when the runs exceed this amount).
Alert minutes, (not implemented yet) this will warn you when the current calling session
exceeds this amount of minutes.
Auto refresh timer, this is the auto refresh of the books screen set to default of 4 minutes.
Auto pen and call, when you call a run wrong then the run is automatically flagged for
penning and calling.
Pen and call freq, when you pen and call and set the next pen and call for the run, this is
how many days into the future the next pen and call will be.
IPad text size, set your own size of text on the calling over screen, iPad only.
Reset Scores, this removes all previous calling histories and sets the runs back to their
default status.
From both the list and run listings the action button has the following options:Shuffle, this allows you to shuffle the order of the runs.
Import text, this is how you import one off runs.
On the list and run listing pages how many runs have timed out, sticky,
Calling over screens.
The above image is the iPad calling over screen, at the top is the title of the run, the edit
button takes you to the run edit screen, the pause button pauses the timer, at the bottom TC=
total calls today, GC = total good calls today, BC = bad calls today, TR= total individual runs
calls, so does not count the repeated calls. The timer on the left is the time for this run, the
timer on the right is the total time spent today calling, the progress bar indicates how far
through the set of runs you are. Swiping left to right takes you to the previous call, swiping
right to left takes you to the next call.
The tick progresses the call the cross restarts the call, touching the screen progresses the call
on a device with IOS6+ pulling down the screen restarts the call like the image below.
The app will automatically progress to the next run when you have finished calling the run.
Importing and exporting individual runs,
This process is very simple, go into the run, click on the Action button top right,
click on Email run, the next screen appears,
just fill in the email address of the person you want to send the run to and click send.
On the importation side of the process, open the email or go onto the message board with the
post of the run and select the run like the following.
You select the run like above, then click copy, then in either the lists or runs screen, click on
the Action button, then click on Import text
The next screen appears,
press on the box and the paste option appears, click on paste, the following will happen,
now click on Import (top left) and the run will be imported.
Importing/Adding new books
All books are received via email, open this email on the device,
click on the attachment then select Open in WizBooks, the app will open, then from the books
main page, click on the action button top right the following menu will appear.
Click on Import/Update, the following screen will appear.
Click on the relevant book and then click on “Import Book”
WizAnn Points Revision Version 2.4
Basic Manual
Index
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
Introduction.
Concept/Basic flow of information.
Installation.
Creating a database.
Installing the beginner’s points.
Starting from scratch, have not started pointing yet.
Been pointing for a while, want to move over to this system.
Pinning.
Creating bike lists.
Revising bike lists/schedules.
Importing the daily/weekly sheet.
Revising the daily/weekly sheet.
Point’s management/Editing point details.
1. Introduction
This document will give step by step instructions on the main features of the WizAnn point’s revision
program.
I have broken the document into 2 parts, this part is the beginners guide that will walk through the basic
features of the program (all you actually need to do the knowledge) and an advanced guide that will
describe how to accomplish more advanced tasks.
Hopefully this program will provide a constant process for you to be able to keep on top of your points
and pointing.
I do not recommend that you attempt to import any data that you may have entered into spreadsheet’s
into the program, there are a number of issues with trying to do this, firstly all matching in the database is
based on point name, road name and postcode these have to exactly match otherwise duplication of
points occurs, if you do have points data in other formats, keep it in that format for future reference, I do
believe in most cases notes are a waste of time, actual position on the map e.g. pinned on memory map is
more useful, the time you take to write up notes could be better spent on p2p to and from those points,
the system will help in generating p2p questions for you in this case.
2. Concept/Basic flow of information.
When the program is first installed you start with nothing, no points just like when you start pointing, you
have two main ways to get points into the program, via a pointing pack e.g. beginners points or
daily/weekly sheets. When points are added to the program they are always added as un-pinned, un-
pointed points, it is using the program that changes the status of the points. Below is a simple flow chart
of the process.
3. Installation
There is always the latest version of the program available on the wizann website under features and
downloads, it is important to know that when upgrading from one version to the next sometimes there are
changes to the database structure these will happen on first use and your data will be preserved and available
after the upgrade.
Installation is very straightforward, download the pointsrevision.msi file from the WizAnn website and double
click the file, once downloaded, just select the default options and install, this will put a WizAnn Points
Revision shortcut on your desktop and install another shortcut into your start menu. Currently the program
only runs on Microsoft Windows, we are considering other platforms but we need to understand all the
ramifications before embarking on other routes.
4. Creating a database
When the program is run for the first time, you will be prompted to either create a new database or open an
existing one, for a first time user you will need to create a database, this can be any name you choose, it is
possible to have more than one database but for most people a single database will do everything they need.
It is worth noting that a database can reside on a removable key e.g. a USB stick, it is important to make
regular backups of your database, there is a backup procedure in the program and all your data is contained in
a single file that can be just copied from computer to computer e.g. from a home computer to a work
computer. If you are going to copy the database make sure the program is not running at that time, data
corruption can occur if the database is in use when being copied. The backups can be opened with programs
like 7-zip http://www.7-zip.org .
Here is a screen shot of the status bar at the bottom of the screen with a newly created database the figures
will be zero.
5. Installing the beginners points
The beginner’s points are available from WizAnn this is the same set of points in the paper version of the
beginner’s points so it is advisable that if you are going to use the revision program you should buy the
electronic version of the points and not the paper version of the points. The process of installing the beginners
points is simple just download the file to the desktop and with the program closed double click on the file, this
will automatically import the points, you must have run the program at least once before and have created or
opened a database file so that the beginners points know where to install into. It is worth noting that you
don’t need the beginner’s points as the database will grow just off daily/weekly sheets, but the beginner’s
points are highly recommended for anyone just about to start pointing.
6. Starting from scratch not started pointing yet.
As above I highly recommend you install the Beginner’s points as this is the base set of points that you will be
working with. It is important to use a consistent process throughout the pointing process as this will be
something you will be doing right up till the day you get your req. I recommend getting some coloured paper
e.g. yellow to print out the pinning sheets for the beginner’s points as this will differentiate them from points
that you will pin from the daily sheets. To pin the beginner’s points you will need approx. 100 sheets of paper,
the number of sheets depends on how much you pin at any one time. The more you pin at any one time the
less paper that is wasted.
7. Been pointing a while and want to move over to this system.
The program has been designed to allow for people part way through pointing to move over to this system, by
this I mean that you may have a lot of points pinned up on your map and want to use the system to create bike
lists and revise those points. In the case of pinned point’s un-pin as normal but in the program create a bike list
and type the names of the points into the bike list to create a bike list with the correct order of points. To
create a bike list, click on point’s icon on the toolbar or the point’s menu item, on the pointer screen, click on
bike list.
This will produce an ordered list of points, in the bike list section (bottom list) you can double click a point to
edit the details like putting in notes for the bike list. Once you are happy that you have all the points you want
to go and find click on “Create Sheet”.
In the above example the colours have meaning a point that is in green means it has already been pointed, a
point in blue means you have the Google street view link for that point.
The next screen is the bike list screen.
If you have already been pointing and you are wanting to move over to using this program, then I suggest that
you install the pointing pack then revise each postcode to work out what you know and what you don’t this is
the quickest way to bring the database up to date with your pointing. To revise by postcode, click on “Revise
By…” at the top of the program window, then click on “Revise by Postcode/Area” just work your way through
the postcodes, you can work out which ones you have done by clicking on the “Last Ran” column to order the
list.
8. Pinning.
All the points come into the system unpinned, all points should be pinned at least once, in the case of a
dropped point then it should be re-pinned.
Pinning should be done in order of times asked, when you first start out try to pin everything that has been
asked more than 250 times, this should produce an 8 page list of points to pin.
To produce pinning sheets, click on the Pinning button
Sheets/Pinning Sheet.
on the toolbar or click on File/Print
9. Creating bike lists
This is a fundamental part of the process, if you pin your points then you want to add these points as you unpin from the map, to do this you click on the Point’s button
on the toolbar on the menu option
above. On the Point’s screen there is a Bike list button
following screen.
on the menu click it, you will see the
From the Actions menu you have the following options.
You can change the order of the points on the list by dragging and dropping points, also F5 will move the
selected point up the list and F6 will move the selected point down the list, I have found a few versions of
windows where the drag and drop ordering does not work this is a limitation of that version of windows
not the program, on computers where drag and drop does not work use F5 and F6 to change the order.
Once you are happy that you have all the points you want to point on the bike list, click on “produce bike
list” from the menu on the button on the form, you will then see the following screen.
This is the same screen that as above, I have duplicated it because different people may want to read
different parts of the document.
If you click on the “Create Bike List Revision Set” button you are presented with the following screen.
Clicking on the “Revision Schedule” button shows the following screen.
On the “Build Revision Set and Schedule” screen clicking on the ADV button shows 3 more buttons, these
allow for exporting of the bike list to different revision systems, the Tab separated format is compatible
with Excel, Mnemosyne, CueCards and Anki.
10. Revising Bike lists and schedules.
All revisions are basically the same, so daily/weekly sheets and bike lists all perform the same functions,
the only difference is that bike lists are scheduled and you will be prompted to revise them multiple times,
the daily and weekly sheets are to be revised once (if you want to you can revise them multiple times but
there is no point).
Below is a screenshot of the revision screen. I will describe each part of the screen.
Sheet Imports, this is a listing of all the daily/weekly sheets and pointing packs that have been installed
into the database, on the right hand side is the statistics of your revisions, this will only list revisions of
daily/weekly and pointing packs. It is possible to edit point information from clicking the edit menu at the
top of the screen, it is worth noting that if you change the name, road, postcode of a point then
duplication may occur as these fields are used to match information when it is imported, so please refrain
from editing these fields.
It is possible to export a revision set to other systems, this is accomplished by clicking the export menu
option.
I have grouped all the basic function buttons into the middle of the screen, with more advanced features
over the right hand side.
This allows for importing of daily/weekly sheets and pointing packs, in most cases you
will double click and open a daily.wzp file in your email to import points.
This allows you to go back to your previously revised point if you feel you answered it
incorrectly. You can scroll back many questions if you wish.
When you revise a point you are shown just the point name you think of the answer
then click Show Answer to see if you got it right. It is worth noting that you can display/hide the postcode
in the question the same applies to AKA (Also Known As) names for the point.
Click this button when you got the answer wrong, it is important to know that this
button will change a pointed point to un-pointed, use the sticky button if you don’t want to change the
status of the point. Clicking this button moves you onto the next question.
Click this button if you feel that you should know the answer and that with a bit of
revision you should be able to recall that information correctly, Stickys can be revised on their own and
they are always displayed most asked to least asked. Clicking this button moves you onto the next
question.
This indicated that you are happy with the answer you have given, it is important to
note that an un-pointed point changes to a pointed point by clicking this button. Clicking this button
moves you onto the next question.
Other basic functions:This button takes you to the pinning list, it is worth noting that a point is only asked to
be pinned once, and unless it has been pinned, pointed then dropped in that case it will be flagged to be
re-pinned.
This takes you to the pointer screen (listing of all the points) it does a search on unpointed points ordered by times asked.
This button saves the current revision set (if one is running) and loads up the list of
sticky points ordered by largest times asked down to least asked.
Advanced functions:This allows you to test all the points that you have flagged as being complex, by
complex I mean complex ins/outs or complex set downs/leaves.
Will show all the scheduled revisions for bike lists, normally this screen will open on its
own, but if you have closed it then this is how you re-open the list.
This is how you flag/un-flag a point for random point to point to learn the ins/outs of a
point by doing point to point. If the background is green then the point is p2p flagged.
This is how you flag/un-flag a point as complex in/out. What I tend to do is mark
everything that is at least two roads away from a road I know, I try to revise the extra roads to see if I can
remember them, if I can’t I make a small run that goes from/to the complex point and call it like a normal
run until the roads have stuck, but this is just my way of doing it that works for me. If the background is
green then the point is complex point flagged.
If the point has a [Google] Street View link for the point then this button will be green,
clicking the button will take you to the [Google] Street View location for the point, you can add these links
by clicking on edit at the top of this screen and then clicking the [Google] Street View button at the
bottom of the edit screen, this will attempt to locate the point on [Google] Street View, there is a small
link button on the [Google] Street View page (it looks like 2 links of a chain) that will give you the current
URL for the page, this is then copy and pasted into the [Google] Street View link box on the edit screen.
At the top of the screen allows you to edit details of a point, the point edit screen can be
accessed from the revision screen or by double clicking on a point in the pointer screen, there is a number
of others way to access this screen, right mouse clicking on some of the lists will allow for editing of
points. Below is a screenshot of the point edit screen.
Boxes 1-5 any information typed into these boxes will appear in the answer to the questions, displaying of
this information can be turned off in settings. Box 7 is where you paste a [Google] Street View URL/link,
clicking on the Streetview button will attempt to find a point on [Google] Street View. Box 6 is where you
type notes that you want to appear on a bike list when out pointing.
The listing down the left hand side of the screen is all the daily/weekly sheets and pointing packs that have
been imported, the daily sheets always take their dates from the time that you do the import, the weekly
sheets will date stamp from the last Friday.
The listing down the right hand side is your progress of revision
Other information on this screen is the statistics on the bottom left of the screen and status of the revision
in the status bar at the bottom, in both cases this applies to the points that have been revised since the
revision started and not the complete revision set. So if you restart a revision the figures only apply to
what has been revised since restarting.
11. Importing from the daily/weekly sheet.
The process of importing is very straight forward, the best way to import the daily/weekly sheet is to
[without the program running] double click the attachment in your email that comes as part of your daily
sheet subscription, it is only the final email of the day that has the daily.wzp file in it, if you encounter
problems save the daily.wzp file to the desktop and double clikc it from there.
12. Revising from the daily sheets/weekly sheets
To get the maximum use from the program you have to subscribe to the WizAnn daily sheets, you will
receive two emails per day, the second email will contain a sheet.wzp file this file is used by the program
to import all the points asked in that day, it will also update the database with new points and update the
times asked for existing points.
The process of revising from the daily sheet is very simple, if your email system will allow just opening the
sheet.wzp from the email should open the program, import the points and take you straight into the
revision process, some email systems don’t allow for this so just save the sheet.wzp from the email on
your desktop and then double-click it from there, it is important that the program is NOT running when
you double click the file.
If you get the sheet.wzp for a Friday this file contains both a daily and weekly file, if you normally revise
each days daily sheet then just import the daily file, if on the other hand you like to revise your points
weekly then just choose to import the weekly sheet below is the dialog box you will be presented with
Then the process is exactly the same as it is for revising bike lists except you don’t have a schedule for
revising into the future for daily/weekly sheets, you are expected to revise these only once.
13. Point’s management/Editing point details.
Below is a screenshot of the pointer screen, this can be accessed from the Points menu option on the
main screen.
From this screen you can do all the points management that you need to, you can type partial matches for
names of points the wildcard character is % so using search clues like this are valid re%hotel on the right
hand side is status this is a drop down list and if you are creating a bike list then select not pointed points,
max is how many points you want to display, if you put 0 in the box it will display everything. Times Asked
> 20 will only display points that have been asked more than 20 times.
The bottom listing is points close to the point selected at the top, these points will always been not points
and if you choose sticky points as well so you can add these to a bike list.
WizAnn Points Revision for the iPhone
Manual
I have written two manuals for the application but under the hood the
application is a single application, the application works out what device it is
running on and displays the correct screens for the device, for iPod's the
screens are the same as the iPhone screens.
When referring to the iPhone/iPad/iPod application I will use the term device
throughout this document, when referring to the application running on the
device I will use the term WizPR (WizAnn Points Revision program/application).
This application can run without any windows version, but has been designed
to work in conjunction with a windows version if you have one, the databases
that contain all your data are 100% compatible between windows and the
device so can be copied using iTunes on and off the devices.
It is worth noting a couple of things, when WizPR is first run it will create a
default database, if you are going to use WizPR in conjunction with windows
just delete this file and copy your database from the windows version. WizPR
looks for a database on first run, it will pick the first database it finds, so if
there is more than one you may open the wrong database. If you copy a
database onto the device whilst WizPR is running you may have to close WizPR
and re-open it (should should only have to do that if the name of the database
changes).
Before we talk about WizPR I need to discuss a few points about databases,
firstly all your data is in a single file, points, notes, revisions, bike lists, this
version of WizPR is only compatible with the very latest versions of the
windows application, specially the last two versions that mention the Olympics
in the title bar (or newer).
The database files can be any name but the extension (letters after the .) must
be wza, so a valid name would be pointsrevision.wza, whilst the windows
version is designed to run multiple databases if you want, WizPR is designed to
run a single database.
All database moving/copying is done through iTunes, so it is expected that you
have your device setup in iTunes, without this setup you will not be able to
move database around.
Backups of the WizPR databases is the same process as copying from the
device to windows, so it is basic copying and not synchronisation that happens
with the data.
A concept that needs to be understood so that you don't get into situations of
databases on windows and the device being both updated at the same time is
this, consider your database like a book, you only have one book, when you
run the database on windows, you cannot update the same database on the
device, the book/database must be lent from the windows version to the
device version, and whilst it is being lent to the device version of the
application it must not be updated on the windows version.
This program was designed to work in the following way, work on the windows
version e.g. do some revision, import sheets, create bike lists, then when you
are ready, you copy the database to the device, you can then continue where
you left off e.g. carry on revising, view the bike list that you created on the
windows version etc, when you get in from a bike session, you copy the
database back onto windows and it can then be run from there. The above idea
works between windows and iPhone/iPad or iPhone to iPad.
Important: WizPR databases are only compatible with the windows version of
the program 3.x.x and above.
Below is a screenshot of iTunes.
There is 4 main steps to understand to use the database on multiple devices.
1. Make sure your device is setup in iTunes.
2. Click on Apps when the device is selected.
3. Go down to File Sharing, click on the WizPR image.
4. In WizPR documents this is where the database is located it can be saved
to windows, copied from windows etc with the two buttons below (Add...
and Save To...).
Important note, if you are upgrading WizPR to a newer version this
includes beta's you must save the database from the WizPR
Documents folder to the desktop (or other location) before you delete
the existing version as removal of WizPR deletes the database.
When you first run the application on an iPhone you get the following screen.
The toolbar options at the bottom are:Revise, which is all the main revision functions.
Pinning, which is how you produce pinning lists for pinning points.
Bike Lists, which is how you produce bike lists for pointing.
P2P, which allows you to produce questions for points that you are having
problems with.
More... takes you to the following screen
Points of Interest, this is the main points searching screen.
Revision Scores, this your history of scores for daily and weekly revision sets.
Message Board, this is the WizAnn message board.
Maintenance, is database maintenance functions.
Info, this is the details of the database and where it has been run from.
Revise
Revise, this is the main revision functions, once you have selected a revision
set type like daily sheet you will see a screen like the one below.
When clicking on the WZP file in the emails from WizAnn the program opens,
even if it is already opened, just click on pinning, then back to revise, you
should then see a new button on the top right of the screen 'load sheet' click
on this, then click on the first sheet this will import the sheet and take you to
the revision screen.
When clicking on a revision set the following screen is shown.
These options are similar to the windows version, “Reset scores” starts the
revision at the first point, “Start at current position”, if you were part way
through a revision set and closed the screen this option will start you on the
point where you left off. “Details” gives you a summary of the revision set and
“View points” will list all the points in the revision set.
The next screen is accessible from anywhere that says “Edit point”
This allows you to edit the point, remember if you change the point name, road
name, or postcode the next import of a WZP file may create a duplicate point
as it is these 3 fields used for matching the points.
The next screen is accessed from anywhere that says “Streetview”, this does
not honour the links in the database as apple have blocked this from working,
so each time there is a proper lookup on google maps, there is no ability to
save these in WizPR, you can use the text box at the top to enter search clues
if no match is found.
This final screen in the revision system is the main revision screen. The screen
is double width so by dragging your finger from right to left will display the
other options. This works the same as the windows version.
The way this screen works is this, you will be displayed a point, you guess the
road it is on, then press show answer, this displays the answer, based on how
well you feel you answered the question you click “Don't Know”, “Sticky” or
“Correct”, “Don't Know” will change a pointed point to unpointed, “Correct” will
change an unpointed point to pointed, “Sticky” will add the point to the list of
sticky points.
Pinning
Pinning is the process of finding points that have not been pinned and printing
out a list of these points and pinning them physically to the map, it is
important to note that all points added to the database are un-pinned by
default, by changing a point from pointed to un-pointed changes the pinned
status back to un-pinned. Below is the default screen, the “Times ask” box is
for displaying only points asked over a certain amount of times, the “Just
pinned” switch is for backward compatibility and should not be needed in most
cases, it is important to note the flow of this screen, you ask to display points
asked more than say 200 times.
Clicking on “Actions” button top right displays the following action sheet,
“Refresh Normal” refreshes the report, “Refresh Tight” produces a report that
is left aligned, “Set Pinned Flag” this updates the database saying that all the
points on the current report have been pinned, you do this once you have
printed out the list.
Once you have pinned all your points above 200 times asked, you can drop the
number down to say 180 times asked, you repeat this process until you have
enough points to start pointing.
Below is the tight report.
Bike Lists
This set of screens is to manage bike lists, by manage I mean, create, modify,
delete and schedule revisions of the bike lists. I have designed these screens
so that it is feasible to work on these lists live, e.g. out on the bike, removing
the need for paper printouts, but the ability to print out is built it if you want to
work in the traditional way.
If you click on an bike list, the following action sheet is displayed, “View bike
list” edits the bike list, so you can add/edit/delete points from the list,
“Schedule revision” moves the bike list from open bike lists to scheduled.
“Revise no schedule” this allows you to revise the list whilst out on the road
without it affecting the scheduling of the list. “Details” displays a summary of
the bike list, “Delete list” this will irreversibly remove the bike list, use with
caution, it does not delete the points but just the bike list.
View Bike List, this screen displays all the points on the bike list
By clicking on a point you are presented with the following menu, the top
option toggles the point from pointed to unpointed, “Edit point” this takes you
to a point edit screen, “Move up” moves the point up the bike list, “Move
down” moves a point down the bike list, “View streetview” takes you to a
streetview of the point. “Delete from list” this deletes the selected point from
the bike list.
If you click on the Actions button on the top right of the screen the following
menu is displayed.
“Add points” takes you to a screen to search for points to add to the bike list,
“Settings” allows you to change certain settings, “details” will display summary
information about the bike list. “Bike List” takes you to the bike list report.
If you click on “Add points” the following screen is displayed, this allows you to
search for points to add to the bike list, you can mix and match the search
criteria e.g. postcode and times asked, the only thing that is exclusive is the
Id, when an Id other than 0 is used then matching is done on just the Id.
When you click on a point, the following menu is displayed. “Add to bottom of
bike list”, this will add the selected point to the bottom of the bike list, “Add to
the top of bike list”, this will add the selected point to the top of the bike list.
“Edit point” will take you to an edit point screen. “View streetview” will take
you to the view streetview screen.
The following screen is the bike list viewer.
Clicking on the “Actions” button, shows the following menu., the first 4 options
are different styles for the report.
Point to Point
This part of the application produces random questions based on points,
postcodes that you maybe having difficulty with. “Weak stuff”, this is where
you enter point to point that you may have struggled with or postcode to
postcode you may have struggled with, just to give you the opportunity to try
those lines again. “View P2P questions”, this is a list of the P2P questions, the
next four buttons are similar, “Generate P2P”, this will generate inter-postcode
P2P questions from points that you have pointed, you have flagged for P2P and
are in the same postcode. “Generate Sticky”, this will generate inter-postcode
P2P questions from points that you have marked as sticky and are in the same
postcode. “Generate Complex”, this will generate inter-postcode P2P questions
from points that you have marked as complex, “Generate Weak Stuff” will
generate P2P questions from items you have put in the weak stuff screen.
Clear list, this will clear the list when you generate any questions, Create qty is
the quantity of questions to generate on any button click, basic usage is, on
the clear list switch select On, then click the generate buttons a number of
times, this will generate a number of P2P questions, then click on “View P2P
Questions” to view the questions. The numbers down the righthand side are
the numbers of points with those flags set.
It is worth noting that there is a p2p weighting system that each time a point
is selected for P2P a counter for that point is incremented, this makes sure that
different points are used for the questions, this can be reset in the
maintenance part of the application.
Weak Stuff
The following screen is the entries for weak stuff, as a basic idea as you are
working your way through the daily sheet doing P2P, if there are lines that you
thought you should try again, it is from this screen that you could enter either
the point to the point or the postcode to the postcode.
In the example below the first entry is postcode to postcode SW1-N16, the
second entry is Paddington Station to Waterloo Station.
P2P Questions
The following screen is a list of the current P2P questions, the way this screen
works is it starts by just displaying the point names (start and end), you try
and guess the start and end road.
By clicking on the point you see this menu, “Show answer” this reveals the
start and end roads and postcodes for the question, “Completed question” this
marks the question as done, “Remove question” this deletes the question, the
next menu options are dynamic depending on the status of the points.
View P2P Questions
The following screen is the P2P questions in report format, this is displayed a
bit like the daily sheet.
Points screen
The following screen is the points screen for searching for points, this is a
double-width screen so dragging your finger from right to left will display more
options.
The searching works the same way as the add points to bike list screen,
Menu options when you click on a point, “Edit point” takes you to the point edit
screen, all the toggle options reverse the current status of that field, e.g.
pinned goes from pinned to un-pinned and vice verser.
Revision Scores
This is history of revisions of the daily and weekly sheets.
This just shows totals from each revision, the scores are not added until you
have revised all the points in a daily or weekly sheet. What you are looking for
is green arrows pointing downwards as this is your dropped count reducing.
Message Board
The following screen is the WizAnn Message Board it works in the same way
that it does in a normal browser, so when setting it up set it to stay logged in
forever.
To refresh the screen or go back to the main message board screen from a
post just click on the “Refresh” button top right.
Maintenance
These are database management functions, “Reset Point Weight”, this resets
the p2p question weights for the points, this should only be used if you are
happy that you are going to be asked the same questions again. “Rebuild
Postcodes”, “Rebuild Categories”, “Rebuild Radius Maps” these should not be
needed as the database should up to date all of the time, so these should only
be used if there is an issue. “Clear Inbox and Extract” this removes all the
temporary files that get created from importing sheets. “Tidy Revision Set
Totals” this fixes any issues with the scoring, for example if a revision set is
removed this will re-align the scores.
Info
This is basic information about the database
Clicking on the “Login Log” button shows the next screen
This shows you when and which device the database was used on, so that you
can confirm the correct database is used.