Since it seems we still have some ambiguity and confusion regarding how to time stamp an IR, I am going to make an effort, 1 last time, to clear up how and why we want the time stamps done in the manner described in
this post.
We'll take last weekend's batch of incidents as one of the prime reasons SNAILIRR was built in the first place.
It took our most prolific steward, and probably one of the most efficient reviewers, 7 hours to pull down all the replays necessary, get them transferred to his PS3, imported to GT6 and view, multiple times in some cases, 47 incidents, post a penalty score, to include comments in a discussion document, to validate that score. Let me say that again. 7 hours. He did it all at one go, on a day where he could spare that big a chunk of time, because he knew the rest of the week wasn't going to allow him to do much more. To my knowledge, all the other stewards had to slot in an hour here and an hour there, over 5 days, to get their reviews completed.
In an attempt to collect the necessary data and streamline the process of identifying which incidents are in the same replays, so we, as stewards, don't have to bounce around to different replays, nor bounce around in any one particular replay, and, the only real reason SNAILIRR was born at all, SNAILIRR generates a list of all incidents. This list is where all stewards begin the review process. It groups every IR by Division, then sorts each division group by which round it occurred, then by the race within that round, and finally, by the time stamp. The race lap number is used as a check and validation on the time stamp. This list's sole purpose is to help organize the IRs in a fashion the stewards can smoothly follow from incident to incident without having to jump back and forth between replays or even within a race that sourced multiple IRs. With the accurate data in place, we can roll through each incident in a linear and timely fashion, with as little wasted time as possible.
In the past, the stewards have made an earnest effort to discover, from the seemingly endless variety of time stamping practices some people seem to be able to pull off their races and replays, when any particular incident actually occurred. We have given allowances for folks who might have an accurate time stamp they got from the individual lap elapsed time, total replay time, best lap time, etc. Then there are the folks that don't seem to get, SNAIL Sunday races will never have an hour value greater than 0, ever. Why is that field included in the form you ask? Because google docs requires that hour field when a time value is chosen for an entry, and the brooms that sweep the data around in SNAILIRR require that time data value, to work properly.
Once again, so that everyone sees it, here are the requirements for entering time stamps in the IR form;
***********************************************
Instructions on how to accurately report time stamps in an IR.
The Form asks for time in Hours, Minutes and Seconds. No tenths, hundredths or thousandths are required.
From a replay, at the top right corner of the screen is the race time. Enter this value from as close to the beginning of the incident as possible.
SNAIL Sunday races will never exceed an hour. That field should always be 0. The race time shown above would be entered as shown in the next picture.
Having posted all the above, all SNAILs can expect some changes to policy regarding IR submissions soon.