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

Certain judgment types should not cause a penalty in terms of standings (JE/CS) #952

Open
johnbrvc opened this issue Apr 1, 2024 · 0 comments
Labels
Comments/Analysis Requested Soliciting comments and feedback from the Team about how to implement issue Primary CCS Required for PC2 to act as primary CCS

Comments

@johnbrvc
Copy link
Collaborator

johnbrvc commented Apr 1, 2024

If a judgment is of type JE (judge error) or CS (contact staff), the team should not be assessed a penalty during standings calculation. Currently, if a judgment is JE or CS, and the team subsequently solves the problem, a penalty is assessed equal to a "NO" response (typically 20 minutes).
...

Feature Description:
Provide a list of judgment types that do not assess a penalty, similar to the way CE (compile error) works. eg. ContestInformation property (POINTS_PER_NO_COMPILATION_ERROR)
...

**Have you considered other ways to accomplish the same thing?
There is currently no way to work around this, other than to override (edit) the judgment) after the fact, and change it to CE
...

Do you have any specific suggestions for how your feature would be implemented in PC^2?
Perhaps add a property for EACH judgment type that indicates the number of penalty points? Currently, you can only specify the number of points for NO, YES, CE and SE. (No, Accepted, Compile Error and Security Violation). Every other judgment uses the penalty for "NO".
...

Additional context:
DSA (calcProblemScoreData) and NSA (createProblemScoreRecord) would have to be fixed, in addition to ContestInformationPane.
...

@johnbrvc johnbrvc added Comments/Analysis Requested Soliciting comments and feedback from the Team about how to implement issue Primary CCS Required for PC2 to act as primary CCS labels Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Comments/Analysis Requested Soliciting comments and feedback from the Team about how to implement issue Primary CCS Required for PC2 to act as primary CCS
Projects
None yet
Development

No branches or pull requests

1 participant