[stamp] Re: to do list
- From: "Joshua Hecht" <goldeye.ichiban@xxxxxxxxx>
- To: stamp@xxxxxxxxxxxxx
- Date: Sun, 26 Feb 2006 00:26:16 -0500
From experience with other tournament systems: schedule difficulty (often
used as a tiebreaker in non-team tournaments), is usually displayed in the
form of opponents' average win percentage. For the alliance based system,
I'd calculate opponents' average win percentage and allies average win
percentage, and display them seperately. You could also average (opponents
average win%) and (1-allies average win%) and use that as a percent
difficulty indicator.
An interesting way to display this would be to color team numbers based on
their win percentage. Opponents with a low winning percentage and allies
with a high winning percentage are displayed in green. A "greener" green
for the more extreme records, and white for 50%. Likewise, opponents with
high winning percentages and allies with low percentages are colored red (or
perhaps black or some other color, since the alliance color is red.
Using green and red in statistics as an indicator compared to the average is
a good idea, in general.
A quick glance at their schedule noticing an aura of green or red can easily
gauge their record.
On 2/25/06, Steven Buss <steven.buss@xxxxxxxxx> wrote:
>
> I'm looking for some input on the strength of schedule function. How do
> you think strength should be represented? A number, a word
> "hard/moderate/easy"? I'm trying to write the function but I don't know how
> to present the information.
>
> Also, i'm going to do the match prediction tonight. I am also setting up
> a server and if I get everything working i'll write a howto (thought
> actually getting everything working is unlikely :P)
>
>
> On 2/24/06, Ryan McElroy <ryan@xxxxxxxxxxxxxxxxx> wrote:
> >
> > I'm willing to give a go at making database_setup more intilligent
> > making/modifying tables.
> >
> > ~Ryan
> >
> > On 2/23/06, Brandon Ripley <Brandon.Ripley@xxxxxxxxxx> wrote:
> > >
> > > This is a list of things to do for the stamp software. We will be
> > tackling
> > > these at team 93 over the next two weeks. If anyone else wants to own
> > any of
> > > these, by all means, take it.
> > >
> > > TO DO:
> > > database_setup.php:
> > > Do not display team passwords with database_setup.php after it has
> > been run
> > > once
> > > Change database_setup.php so is verifies all the tables have all the
> > > required columns and adds columns if necessary
> > >
> > > scouting_input.php:
> > > Add functionality to insert "disqualified" checkbox from
> > scouting_input into
> > > database
> > >
> > > admin.php :
> > > Get team password lookup working on the admin page
> > >
> > > Add functionality to change user privileges for your team on the admin
> > page
> > >
> > > stamp_includes.php:
> > > Add version number to the footer.
> > >
> > > robot_summary.php:
> > > Load the team images from images/teams/teamXXXX.jpg
> > > Make it look pretty and print on an 8.5x11
> > >
> > > self_entry.php:
> > > Make it look pretty
> > > Add functionality to allow team A to enter data for all the teams
> > >
> > > match_predictor.php:
> > > Make match prediction page
> > >
> > > all pages:
> > > Add restrictions to pages so adminLevel 0 can only view "safe" data
> > and
> > > can't change anything
> > >
> > >
> > > Brandon Ripley
> > > Design Engineer
> > > Plexus
> > > 920-969-6267
> > >
> >
> >
>
>
> --
> Steven Buss
> steven.buss@xxxxxxxxx
> PHP/MySQL programmer
>
Other related posts:
