Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overhaul DEM Scoring Section #877

Open
johaq opened this issue May 14, 2024 · 2 comments
Open

Overhaul DEM Scoring Section #877

johaq opened this issue May 14, 2024 · 2 comments

Comments

@johaq
Copy link
Member

johaq commented May 14, 2024

DEM scoring section is kinda outdated by now. Most tests just contain applicable DEM penalties on their own scoresheet. The percentages mentioned are not really applied there either.

@LeroyR
Copy link
Member

LeroyR commented May 15, 2024

Discussion:
A) Remove DEM section general penalties and focus on penalty section of tasks.

  • allows "better control" over penalties.
  • easier scoring during competition
  • more scoring teams

B) Improve general DEM section penalties, remove most penalty items in Scoresheets

  • less rulebook work
    • we could just add X different dem penanlty levels with some examples and be done.
  • harder scoring. much harder if penalties apply for single score items, less so if they apply to total (scored or max) score. Also may need to cross reference DEM section

I assume that task specific penalty sections encourage teams to actually use DEM: this may increase teams ability to show 'something' but in reality it causes Robots to sometimes "do nothing" but drive around and instruct the refree.
Defining task penalties also may reduce innovation as it gives a more (statemachines-like) fixed task procedure.

Need some data to know if my assumptions hold 😅

@johaq
Copy link
Member Author

johaq commented Nov 25, 2024

I think the general examples in the DEM section should be removed entirely (maybe just a couple examples but without percentages attached). Have all the applicable DEM penalties test specific. Additional ones can be proposed and discussed in the Team Leader Meeting. The robot is not allowed to request something not discussed in the TLM. Easier for referees to be prepared and way less complicated discussions afterwards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants