Anonymous
12/01/2024 14:12
Subject: Meet Mobile Results Swim and Rock Oak Marr
Anonymous wrote:Anonymous wrote:They’re in swim cloud. Not sure why they aren’t on USA swimming.
Exactly !!
I think anyone can send an official results file to SwimCloud. (ie one of us could download from the pvs results site and send it to them) That’s not the case for USA Swimming.
Anonymous
12/01/2024 13:57
Subject: Meet Mobile Results Swim and Rock Oak Marr
Anonymous wrote:They’re in swim cloud. Not sure why they aren’t on USA swimming.
Exactly !!
Anonymous
12/01/2024 13:44
Subject: Meet Mobile Results Swim and Rock Oak Marr
They’re in swim cloud. Not sure why they aren’t on USA swimming.
Anonymous
11/30/2024 15:20
Subject: Meet Mobile Results Swim and Rock Oak Marr
Anonymous wrote:Anonymous wrote:Looks like Meet Mobile data was reloaded today for the meet.
Thanks 🙏 any updates on eta for these results to post to USA Swimming?
This usually depends on when your LSC uploads it to the swims database. It might not be their first priority over the thanksgiving holiday.
Anonymous
11/30/2024 12:26
Subject: Meet Mobile Results Swim and Rock Oak Marr
Anonymous wrote:Looks like Meet Mobile data was reloaded today for the meet.
Thanks 🙏 any updates on eta for these results to post to USA Swimming?
Anonymous
11/25/2024 17:16
Subject: Meet Mobile Results Swim and Rock Oak Marr
Anonymous wrote:Anonymous wrote:Hey everyone,
Is it just me, or does Meet Mobile act a little weird sometimes? I’ve noticed at meets like Swim and Rock (this weekend at Oak Marr, hosted by the Sea Devils) that results will pop up and then disappear. It’s especially frustrating when you’re trying to keep track of times and roster decisions for big meets like championships.
Does this happen at other meets too, or is it just a glitch with this one? Curious if anyone else has noticed this or knows why it happens.
Thanks!
Are you a coach or admin for a team? If you are, you should already know not to use meet mobile for “roster decisions”. Use the swims database like everyone else. All entry times for selective have to be confirmed by swims. Using meet mobile to keep track of times is like using Wikipedia for research projects. It’s a fallible source.
Oh I’m sure this was a parent trying to game out how likely their child was to make the winter classic roster.
Anonymous
11/25/2024 16:56
Subject: Meet Mobile Results Swim and Rock Oak Marr
Anonymous wrote:Hey everyone,
Is it just me, or does Meet Mobile act a little weird sometimes? I’ve noticed at meets like Swim and Rock (this weekend at Oak Marr, hosted by the Sea Devils) that results will pop up and then disappear. It’s especially frustrating when you’re trying to keep track of times and roster decisions for big meets like championships.
Does this happen at other meets too, or is it just a glitch with this one? Curious if anyone else has noticed this or knows why it happens.
Thanks!
Are you a coach or admin for a team? If you are, you should already know not to use meet mobile for “roster decisions”. Use the swims database like everyone else. All entry times for selective have to be confirmed by swims. Using meet mobile to keep track of times is like using Wikipedia for research projects. It’s a fallible source.
Anonymous
11/25/2024 16:20
Subject: Meet Mobile Results Swim and Rock Oak Marr
You’ve gotten good explanations of the myriad of things that can go on behind the scenes to delay or change results.
WRT DQ protests, coaches have to file them within 30 mins and the referee will consider the protest and either let it stand or overturn the DQ. In very rare circumstances there could be a DQ protest that has to rise to higher levels for a rules interpretation. While the Rulebook is comprehensive there are always issues that come up and there is sometimes room for discussion regarding did X constitute a rules violation or not. Usually those are handled as fast as possible on deck but it could take some time and back and forth between referees and senior level folks to get a ruling. Examples would be things like did a swimmer’s celebration that included a body part going crossing a lane line constitute interference with another swimmer…
WRT DQ protests, coaches have to file them within 30 mins and the referee will consider the protest and either let it stand or overturn the DQ. In very rare circumstances there could be a DQ protest that has to rise to higher levels for a rules interpretation. While the Rulebook is comprehensive there are always issues that come up and there is sometimes room for discussion regarding did X constitute a rules violation or not. Usually those are handled as fast as possible on deck but it could take some time and back and forth between referees and senior level folks to get a ruling. Examples would be things like did a swimmer’s celebration that included a body part going crossing a lane line constitute interference with another swimmer…
Anonymous
11/25/2024 13:16
Subject: Meet Mobile Results Swim and Rock Oak Marr
Looks like Meet Mobile data was reloaded today for the meet.
Anonymous
11/25/2024 13:16
Subject: Meet Mobile Results Swim and Rock Oak Marr
TThank you for the detailed explanation. It's fascinating to learn about the behind-the-scenes process of determining official times and results at swim meets.Anonymous wrote:
The default on the hytec computer system (this is what runs the swim meet results) is that anything that enters the computer system goes directly to meet mobile. This means it is uploading the pad times. If it is a 200, and the swimmer doesn't hit the pad at the finish, hytec initially takes the 150 pad time as the 'pad time.' It also flags it so that the operator corrects it and uses the button time. Slightly different scenario, but if the swimmer doesn't hit the pad, the buttons stop, then while waiting for other swimmers to come in, like 2 seconds later, does hit the pad, the computer will take that late pad time as the 'pad time' and also flag it for the operator for correction. As previously mentioned, this also doesn't include DQs.
If you are seeing results on meet mobile before a race is finished (e.g. heat results) then this default hasn't been turned off and they are meaningless.
The only scenario where I ever really see changes is if kid swam in a wrong lane/ wrong heat. Ideally this is caught by a coach and the timers, and the table reseeds the swimmers to reflect what they actually swum. But occasionally no one notices, and it takes a parent saying "my kid is showing as a no show, but he swam I watched him." That is the only scenario that a parent should say something to a coach based on what they are seeing in meet mobile. A variation of this would be "I noticed my kid was supposed to swim in Heat 3 lane 4, but I saw him swim in heat 2 lane 4, and his time is showing as different from what I saw on the score board when he finished."
Also- in terms of protests about a time- they are really uncommon. The rules of how you determine a time are set forth by USA swimming- I'm not looking at my rule book, but here you go as a summary- The meet announcement lists the timing system- automatic timing (touchpads primary) is the most common. The AO looks at the touchpad time and the button times- as long as one button is within .3 seconds of the touchpad time the touchpad is the time. If the buttons are within .3 seconds of each other, but not of the touchpad- then the average of the two button times will be the time. If the 2 buttons and the pad time are more than .3 seconds apart- or if one of those pieces of data is missing, and the two pieces of data you have are more than .3 apart- then the AO needs to gather more data. The watch time comes in here- if the watch time supports the pad the pad will be taken. The starter records order of finish- if the order of finish supports the pad, the pad will govern. Sometimes they will go get a coaches time- if the coach used a watch vs just writing down what the scoreboard shows- the coaches time wouldn't be the 'official' time- but it might validate the pad time, etc.
The much more common 'time' protest really comes down to someone not swimming the right heat/lane so they were given the wrong time- b/c they were given the time of whoever did swim in their assigned heat/lane...
There seems to be a lot of data and factors involved in validating a time or result. From watch times to order of finish, and even coaches' times, the process can be quite complex. Ultimately, it ensures fairness and accuracy in recording each swimmer's performance.
I imagine time protests are rare, as errors can easily occur when assigning times based on heat and lane numbers. It's understandable that everyone wants their performance recorded accurately, and I'm glad there are measures in place to address these issues.
This was so cool. Thank you.
Anonymous
11/25/2024 10:31
Subject: Re:Meet Mobile Results Swim and Rock Oak Marr
Thank you for the detailed explanation. It's fascinating to learn about the behind-the-scenes process of determining official times and results at swim meets.
There seems to be a lot of data and factors involved in validating a time or result. From watch times to order of finish, and even coaches' times, the process can be quite complex. Ultimately, it ensures fairness and accuracy in recording each swimmer's performance.
I imagine time protests are rare, as errors can easily occur when assigning times based on heat and lane numbers. It's understandable that everyone wants their performance recorded accurately, and I'm glad there are measures in place to address these issues.
There seems to be a lot of data and factors involved in validating a time or result. From watch times to order of finish, and even coaches' times, the process can be quite complex. Ultimately, it ensures fairness and accuracy in recording each swimmer's performance.
I imagine time protests are rare, as errors can easily occur when assigning times based on heat and lane numbers. It's understandable that everyone wants their performance recorded accurately, and I'm glad there are measures in place to address these issues.
Anonymous
11/25/2024 10:29
Subject: Meet Mobile Results Swim and Rock Oak Marr
The default on the hytec computer system (this is what runs the swim meet results) is that anything that enters the computer system goes directly to meet mobile. This means it is uploading the pad times. If it is a 200, and the swimmer doesn't hit the pad at the finish, hytec initially takes the 150 pad time as the 'pad time.' It also flags it so that the operator corrects it and uses the button time. Slightly different scenario, but if the swimmer doesn't hit the pad, the buttons stop, then while waiting for other swimmers to come in, like 2 seconds later, does hit the pad, the computer will take that late pad time as the 'pad time' and also flag it for the operator for correction. As previously mentioned, this also doesn't include DQs.
If you are seeing results on meet mobile before a race is finished (e.g. heat results) then this default hasn't been turned off and they are meaningless.
The only scenario where I ever really see changes is if kid swam in a wrong lane/ wrong heat. Ideally this is caught by a coach and the timers, and the table reseeds the swimmers to reflect what they actually swum. But occasionally no one notices, and it takes a parent saying "my kid is showing as a no show, but he swam I watched him." That is the only scenario that a parent should say something to a coach based on what they are seeing in meet mobile. A variation of this would be "I noticed my kid was supposed to swim in Heat 3 lane 4, but I saw him swim in heat 2 lane 4, and his time is showing as different from what I saw on the score board when he finished."
Also- in terms of protests about a time- they are really uncommon. The rules of how you determine a time are set forth by USA swimming- I'm not looking at my rule book, but here you go as a summary- The meet announcement lists the timing system- automatic timing (touchpads primary) is the most common. The AO looks at the touchpad time and the button times- as long as one button is within .3 seconds of the touchpad time the touchpad is the time. If the buttons are within .3 seconds of each other, but not of the touchpad- then the average of the two button times will be the time. If the 2 buttons and the pad time are more than .3 seconds apart- or if one of those pieces of data is missing, and the two pieces of data you have are more than .3 apart- then the AO needs to gather more data. The watch time comes in here- if the watch time supports the pad the pad will be taken. The starter records order of finish- if the order of finish supports the pad, the pad will govern. Sometimes they will go get a coaches time- if the coach used a watch vs just writing down what the scoreboard shows- the coaches time wouldn't be the 'official' time- but it might validate the pad time, etc.
The much more common 'time' protest really comes down to someone not swimming the right heat/lane so they were given the wrong time- b/c they were given the time of whoever did swim in their assigned heat/lane...
There seems to be a lot of data and factors involved in validating a time or result. From watch times to order of finish, and even coaches' times, the process can be quite complex. Ultimately, it ensures fairness and accuracy in recording each swimmer's performance.
I imagine time protests are rare, as errors can easily occur when assigning times based on heat and lane numbers. It's understandable that everyone wants their performance recorded accurately, and I'm glad there are measures in place to address these issues.