Using multiple devices

Quick tip: Sometimes you work on a computer in the tab room, and during the tournament want to walk around using your tablet or phone to scare up a missing judge or whatever. Problem is, if you log in on a different device, you lose the log-in on the last device. Simple fix: Give yourself two different accesses to the tournament. Give admin rights to the tournament to a second email (create one if you need to). I generally log in with my gmail account but if I want a second access, I use my Yahoo account.

It's a small detail, but it can make things just that much more convenient.

MJP deadlines

This is probably worth passing along.

If you use MJP at your tournament, you will want to set it up so that teams can’t pref unless their judges are all in place. That’s easy enough. You’ll also want everyone’s teams to stay in place. That's not so easy, especially if you have, shall we say, inevitably disorganized loosey-goosey teams attending your tournament (and you probably do). There is only one thing more annoying than getting judge changes once MJP opens and having to tell everyone to go back and redo their prefs, and that's actually being the everyone constantly going in and redoing their prefs. That vague "everyone" isn't blaming the loose geese (leese geese? loose gooses) for the extra work: they're blaming you.

So, a piece of advice. Open prefs late. If the tournament starts on Friday afternoon, open them Thursday night. This reduces the likelihood of last minute changes. Of course, you don’t want that list of judges to be a surprise 24 hours before the tournament, so make sure that you have the list of judges public at least a week before the tournament starts.

Handling mandated judge preferences

We had a handful of “Blue Ribbon” judges at Newark. To wit, these were judges that the tournament had gone out of its way to bring in (with the exception of one judge who was accompanying a registered team). The idea was that, for whatever reason, these judges represented something that the tournament stood for, and that all the entrants ought to be prepared to debate in front of them.

I hedge on explaining the precise nature of these judges because, for one thing, they weren’t all the same. For another thing, a similar situation was discussed by the NDCA. In their case, the tournament had gone out of its way to bring in hired judges adding good diversity to the pool, and the problem was, after all that, should entrants be allowed to strike those judges? If I recollect correctly, it was determined that in the future they must be ranked either a 1 or a 2, but I could be wrong about whether this was actually agreed to.

The problem of forcing a ranking, i.e., forcing people to rank certain judges, is that if you have, say, 60 judges, with 10 for each category, and five of those judges are Blue Ribbon enforced 1s, that leaves you with only five 1s of your own choosing. I guess I could have set the percentages to reflect the five mandated 1s—it’s only one less of all the other categories—but I thought about it differently. I just marked the BRs as inactive during the ranking period. People got to rank all the judges except these.

The next thing was that I didn’t want to burn these folks out. Newark was single-flighted, and did we really want our Blue Ribbon judges in every single round (especially the ones who had just come off two back-to-back final rounds, one for the Round Robin and the other for the postponed Ridge tournament)? Kaz was also one of the BRs, and she still hasn’t stopped mumbling about judging every round at Apple Valley. I can sympathize with the desire for a round off, and if I have the luxury of enough judges to do so, I try to insure at least one for everybody in normal double-flighted tournaments (which was, admittedly, a lot easier in TRPC where you just click a judge on or off for a given round). Our BR judges deserved the same treatment.

My solution was to keep the Blue Ribbons as inactive when I paired the rounds and made the initial judge assignments. Then I went in and turned them on (if I wasn’t giving them the round off). Then I went back to the pairing and looked for bad assignments, starting at the bubble. The logic (which Alston agreed with) of putting BR judges on the bubble seemed intuitive: if these are the mandated judges, it presumes that the tournament respects their decisions without qualification, and who best should be handling your toughest rounds? If a pairing already had a good mutuality, I left it alone. I wasn't there to make a statement, just to use the BRs most wisely.

Doing it this way had a side benefit for tab. Instead of each person having ten 1s, they had fifteen, and five of those were guaranteed mutual. I mean, there are plenty of times when there isn’t a single mutual agreement on a judge between two debaters in the entire pool (and usually this happens to the same schools over and over, who have unique opinions on the pool from the norm as well as unique opinions from a handful of others, whom they always seem to hit). Having a mandated-1 wild card to pop into a down-two round to replace a 1-3 pairing (!!!) was a godsend.

Granted, this sort of Blue Ribbon or mandated ranking of any sort is a rarity, and I’m not offering an opinion on whether it’s a good thing or a bad thing (I haven’t given it much thought), but it is interesting, and it’s something to think about as a general practice, and certainly something that you might have to hack out if you’re the one in the tabroom.

Bracketing issues

At the Newark tournament this weekend we had various issues with this and that. We were running a totally e-ballot tournament, with NLD, VLD, NPF and VPF (plus they were running a couple of policy divisions in another building, and we had preceded the invitational with a round robin, but that’s all beside the point). There were two of us in tab, me and Cruz, until we pulled Sheryl in. Which means pretty serious firepower behind the machines.

For not the first time, we had issues with the debaters advancing in the break rounds. Things did not work the way they were supposed to work. I have no idea why, but this has happened before. You have, say, an octos round that goes perfectly normally, you enter all the results correctly (or in the case of an e-tournament, the judges do it, so by definition the results are correct), and then you go to pair the quarters, and a wrong team has advanced, totally misbracketed. There’s ways of surviving this (which we’re still learning, unfortunately). What we do is pair the round by hand, which is easy enough except for one thing. If the bracketing has gone haywire, the system may not spit out the correct teams in order or resulting bracket anymore. In other words, you can’t rely on any part of the system to know who’s debating whom, if any other part breaks down. It’s all connected.

So this is imperative. I don’t print too many things in tab these days, but one thing I always print is the bracket. When you move to elims, the bracket will magically appear under Results/Web Publish. It won’t be visible to the assembled masses, but you’ll have access to it in tab. PRINT THIS UP BEFORE YOU DO ANYTHING!!! It’s your safety net. The North Koreans can take over tabroom completely as far as you’re concerned as long as you have this printout. For one thing, you’ll know who should advance over whom in closeouts when a coach pops by to advance someone. Of course, I believe that you should make the bracket public from the beginning. If a tab room is transparent, that’s one of the things people ought to be able to see. Regardless, when the problems hit us at Newark, they hit the brackets, which stopped updating (which they normally do with each progressive break round). At the point where we were hand-pairing both the PF division break rounds, having this first bracket printed and in hand was a godsend.

If everything is working well—and everything does usually work well—you can pull and print an updated bracket after each round, and I recommend that too. You can’t be too careful, and it’s nice to watch the tournament work its way along. By the way, be careful with those brackets. As of this writing, if you delete it, you can't get it back. (I've put in a request to fix that.)