We were made aware of a problem with our most recent curated rapid reporting packet, number 30. It turns out that there were 11 cases in that packet that were also in packet 29. This occurred because of a bug in the code we use to generate our balanced packets. Essentially, the code was incorrectly identifying which cases were not in use (and therefore chose cases already in packet 29). I’ve fixed this bug, removed the old packet 30 and regenerated a new packet 30 with new unique cases. Most of you won’t notice any difference but those of you who have sat packet 30 will have had your score for that packet reset.
Thanks to Zeid for pointing this out.