Results

How are these 2 Kids appear in the result list within the Lynx-Softwware?

Also tied - or one on 2nd and the other on 3rd?

Ciao

dirk

We have had this where at 1/100 second resolution, you can identify one racer ahead of the other, but does not separate on time. If it's in the same heat like in this case, we will JD it in Meet Manager and then wait for the coach to come talk to us and insist on seeing the picture. We'll also review it with the head official so that he is aware of what happened so that when the coach comes and asks, he or she will be prepared to address the outcome.

I was asking for the placements in Lynx, because such a case will happen often.
At this Example, you see, that the runners in lane 1 and lane 5 do have the same time - but you can easiely decide, who is in front.
And the software also decides this.



The .lif file (for data-exchange) also shows this ranking:

205000032,205000045,1,60m Finale M14,,,,,,,14:14:39.8005
1,77,3,Adjagi,Peter Shina,LG Baunatal/Fuldabr¸ck,7.49,,7.49,,,,,,
2,94,4,Kanacher,Scott,LG VfL/SSG Bensheim,7.68,,0.19,,,,,,
3,268,8,Shuminov,Daniel,LG Eintracht Frankfurt,7.74,,0.06,,,,,,
4,425,6,Morat,Luis Andrey,TSV Kirch-Brombach,7.86,,0.12,,,,,,
5,394,5,W¸stenhˆfer,Daniel,TV Herborn,7.89,,0.03,,,,,,
6,98,1,Petersmann,Niclas,LG VfL/SSG Bensheim,7.89,,0.00,,,,,,
7,393,7,Domes,Daniel,TV Herborn,7.92,,0.03,,,,,,
8,626,2,Flasshoff,Christian,TSG Wehrheim,8.00,,0.08,,,,,,
 

So, if Meetmanager gets these infos, it should be able to display them.

Since we are working with "Seltec Track and Field" - and this software is able to do so, this might be an error at Meetmanager...

Ciao

dirk

With the Hy-tek software the Finishlynx needs to have the .lif report to the .000 for the MEETMANAGER to show the proper placing of the athletes within a heat and between heats.

Ah...
so Meetmanager doesn't care about the placing (1st column) in the .lif.

So this leaves the question, if this is a bug or a feature ;-)

ciao

dirk

A response from Hy-Tek indicated that Meet manager brings in times and not places but should look to thousandths if it is set to do so. We will have to check our settings closer to make sure they are set to 1000ths. I was pretty sure we did have it set that way but will double check the next time we are set up.

Yes we almost always have level of precision set to thousandths and that breaks ties. Many operators will then right click on the time and add the time to the thousandth as a comment right of the time.

In lynx, go to the kids line in the results, right click and set precision to 1000th on both, or click on the heading and set the whole heat to 1000th. It is still in there. That will show you the times and they will import in the proper order in Hytek at that point. Then in hytek as I mentioned, right click on the kids name and type in their time to the thousandth as a comment so that the coach knows you looked at it.

I would also suggest that you check your frame rate as it will spread out a picture like this in many cases. But as timing goes that isn't even a tight race. :-)

This is real close. I think the photo finish here ought to cover the problems with the misjudgement. We had a similar problem in my university meet and it was cleared by a similar photo finish. I don’t remember the equipment but this equipment shown here looks good!

I didn,t had time to read all post.

In here, We always set our lynx precision in 1000th but in case we forgot to set in 1000th and remain in 100th, you can break tie manually with the option Judges in the run Hy-tek windows. You will manually tell which one is ahead the other.

You can leave FinishLynx to 1/100, and then manually break the tie by using the JD function (JD stands for judges decision) in Hytek. That button in found in the functions that run through the center of the run menu. You can add a comment by right clicking on the time, and adding the times to the 1/1000, delta time,whatever you wish.

in Lynx:
File, Options, Database, Time Precision, Thousandths.

To Captureguy:

1) Set your Lynx to minimum 1,000 frame rate. Preferably set it to more than that. For track meets I use a frame rate of 1,500 and higher. If you can't set your frame rate that high and still cover the width of the finish line set the rate as high as you can but make sure you can see all the lanes.

2) If you are using your Lynx in a FAT setting, set your File - Options - Database - Time Precision value to Thousandths. FAT means you are using a RadioLynx or some sort of electronic start system.

3) If you ARE NOT using your Lynx in a FAT setting, set your File - Options - Database - Time Prevision value to Tenths. When you are not FAT you are the same as a stopwatch or Automatic Timing as they call it. Non FAT means you are not using the RadioLynx or you are using the manual start feature on the Lynx software to initiate a start. In the U.S. for High School Track & Field, if non-FAT timing is being used ties stay as a tie.

Make sure to leave your File - Options - Results - Default Precision to Ten Thousandths or as high as you can. The Results window in the Lynx software default rounding procedure is set to Round Up per Track & Field requirements. You can also set the Results Window precision by placing the arrow on the Time Column, right clicking, and selecting what precision you want to see. However, this will not change the File - Options - Database - Time Precision setting.

If your Lynx frame rate is set as high as you can you will visibly see the separation in runners especially if there is a tie. The "recorded time" in HyTek may say the same time but on the Lynx results window which will be set to thousandths you will be able to see the difference in thousandths for the runners.

As Doug DeAngelis from Lynx notes, "It is a simple fact that the more data you have to make a decision, the better chance you have of making the right decision. That means a higher frame rate is better, period (so long as you have the light to expose it)."

The ONLY downside with a super high frame rate is your runners will look fat because they will be traveling slower than what the camera is set at. This can make it hard to identify the torso of the runner and differentiate between runners because all of them will look fat. So I usually stick around 1600 to 1800 for sprints and 1500 to 1600 for distance races.

Frame rate should be a ratio to pixel height, with sprints at about 2 to 1 and distance around 1.4 to 1. Different angles of view will also effect image so that the ratio should be adjusted for high angles of view or views from a "standard" tripod. In Track bodies that are too fat or too thin make accurate positioning of the timing line difficult. Colour fringing from 3 bar systems (all but the "Pro" camera) gets worse as the bodies get fatter from too high of a capture rate. So in my opinion, Hi rates are great with a "Pro" camera but with most situations sticking to a ratio based on speed of athlete and Pixel height available for exposure is a better way to go for most operators.
The time precision for reporting needs to be set in the meet management program, even if the Lynx .LIF is reporting to 1/10's the meet program will show times to the 1/100th unless set correctly. When the meet program is set correctly it will do the rounding up itself correctly even when the .lif is reporting to the 1/1000th.
A small comment the I.A.A.F. says that times should only be reported to 1/100th for F.A.T so that is your max time precision in athletics (results window), reading can taken to the 1/1000th to determine placement so making making the .lif report higher than that is not necessary(data base window)

I have completed a crash course in Linux and now I am with a project with Linux. I am thinking to do some higher level course related to Linux. Can you suggest about any course which does have high job importance. That would be really helpful.


Thanks
windowssupportnumber.com