Code Monkey home page Code Monkey logo

unicycling-convention-guide's People

Contributors

dependabot-preview[bot] avatar rdunlop avatar

Watchers

 avatar  avatar  avatar

unicycling-convention-guide's Issues

Improved Slow Races Notes

What follows are some notes about possible recommendations for Slow/Stillstand competition improvements. some are logistical, some are rules.


  1. Regarding to registration:

The webmaster should consider the following:

Slow races:
NO option to sign in the best time.
but the following:
Qualification round slow forward ( please note: you need to perform a time equal or grater than 45 sec. to start at the final, otherwise your result will be deleted because no age groups will be ranked. After getting the reminder, you have to confirm your start between 01.06. and 10.06.2017 by sending an e-mail to...........)

The Sign in for finals will become valid by sending your previous result list until 01.06.2017 to .....................

Qualification round slow backward: ( please note: you need to perform a time equal or grater than 40 sec. to start at the final, otherwise your result will be deleted because no age groups will be ranked. After getting the reminder, you have to confirm your start between 01.06. and 10.06.2017 by sending an e-mail to ...........)

The Sign in for finals will become valid by sending your previous result list until 01.06.2017 to.......................
(Why?: So misunderstandings could be avoided, and number of qualification candidates will be reduced to serious starters.)

  1. Regarding to the schedule:

Time window:
4 hours qualification round
4 hours finals

  1. Regarding to the judges:

Judges have to pass judging workshop at EC unicycling or online- instruction.
Volunteers needed: 4 judges and 2 volunteers at the laptops, the same for finals.

  1. Equipment needed:

The main things:
2 laptops
starting posts
boards
5 stop watches
tape
desk

Regarding to Stillstand:

The webmaster should include the following:

After getting the reminder, you have to confirm your start between 01.06. and 10.06.2017 by sending an e-mail to.................
(why? this has been the idea at unicon18 to get to know the number of starters who seriously would have come to perform their "run"

regarding to the schedule :

time window: 4-5 hours

regarding to the judges:
Volunteers: 8 judges and 2 volunteers at the laptops.

Equipment:
2 laptops
1 table
boards
starting posts
stop watches

As slow races and stillstand are very different from track races, in my opinion it has been a good decision to separate them from track races and to get an own director for these disciplines. I am glad that you have got Rosi Bongers as director for track races, she really has great experiences, but as there aren´t any tradition to offer slow races in Duisburg, I would do the job of the slow race and stillstand director.
Here in Bavaria we have tested and evaluated the new rules (rulebook 2015) and the riders and judges feedbag was 100% positiv.

Improve Freestyle Judge notes

Really the only issues that occurred for freestyle were when we did not have enough laptops. I would add something to the convention guide about laptops and who is providing them. Are the hosts providing them or is the chief judge supposed to collect enough.

Also, we often had access to iPads but they only work for technical judging due to the formatting of the screen. Performance has too many categories to enter. So this was a problem. Also, many people were happy to enter scores on their phones in a pinch but this was not possible because of the formatting of the score entering page.

I would also suggest adding something to the freestyle page about judges. When/where is the judging workshop? How are you communicating with the judges when they are assigned to judge? I think that one of the main reasons that freestyle ran so smoothly this time is because judges had an easy way to check when they were supposed to judge (google doc). Crises that arise with freestyle are when you are scrambling to find a judge at the last minute or when you don't have enough laptops/ipads.

The track timing system should discuss start/finish and data recording

When doing track starts, we need to start with a "Beep-beep" or "gun start" which synchronizes with the photo finish system.

We need this to be synchronized. We need this to be tested.

Secondly, the output from the e-timing system should be tested with the UDA (data-recording) system in advance.

Needs:

  • thousands precision (3 decimal places)
  • lane numbers
  • DQ/DNS for those who do not show.

eventbook idea

There is an idea to release an IUF Eventbook (accompanying the rulebook), like ever since (I brought up this idea at the IUF meeting 2008 myself). Also there is no success in doing so. I think you have alread covered a lot of information which can be turned into something official?
Also hit up Jenni, she has a lot to say, too (she's on github but I don't know her handle to ping her).

Improve MUni recommendation areas

We want to hear about what you wish had been organized differently in advance for your specific event(s)?

Volunteer List at the registration (it was written 0 which didn't help to get the volunteers needet).

Completely legal track which is be ready for training with at least a little bit of track marking in advance of the event.

A local co director who speaks spanish and english (i was told there would be one but there wasn't).

Something like the list which responsibilities the director has in advance. For long distance races it also should be clear that it is not possible for a director from abroad to organize ambulance, bathrooms, legalization of the track. I think a director who is not local can help mostly on the rule and sport part of the competition (at least on the competitions which are not in a gym or stadium).

What didn't go well, and why?

To find volunteers in the short period between the race started and the unicyclist arrived at the track. Volunteers should be found at least on the day before.

Marking of the track. (Not enough tape, it was not allowed to put sticks on the ground to have something everywhere to attach the tape and not enough time because the track marking was only allowed to start at 7pm on the evening before the race).

Clear map of the track. I think this was a result of the "half legal" status.

Chip timing...

What should have been done differently in order to make it run better?

More logical track (one 2-4km circle done multiply times instead of the complicated first circle a then b then a again modus).

What did we do well, but isn't in the guides?

Just some general input from me:

2-4km track which the rider do multiply times. For downhill the final track should not be longer than 2-4 minutes for the fastest riders (like in DH Biking or Skiing, it makes the race much more exciting for the audience).

The possibility to train on the track. It should be clear where the track goes before the race either it is already marked or map will be published before.

Some input on volunteers:

There should be something like volunteers meals to keep them motivated and the possibility to take a break from helping every 3-4 hours.

How to deal with overlapping events?

From Rolf:

How should we deal with overlapping events?

I can see 2 possible answers:

  1. Once the schedule is fixed at the beginning of the Unicon, it is
    fixed. If there is an overlap, it's bad luck for the competitor.

  2. We try to solve such problems also during the Unicon. For many events
    (e.g. team sports, track racing, freestyle), the competitors spend
    most of their time waiting until it is their turn. With good
    communication, the overlap can be minimized.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.