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

The change of semantics of score.txt is a bit subtle #328

Closed
niemela opened this issue Aug 20, 2024 · 3 comments
Closed

The change of semantics of score.txt is a bit subtle #328

niemela opened this issue Aug 20, 2024 · 3 comments

Comments

@niemela
Copy link
Member

niemela commented Aug 20, 2024

Comment from @gkreitz:

The complete change of semantics for score.txt is gonna be a complete pain to deal with (it's either a float in [0,1] if the test group score is bounded, or the actual score). It would have been much better IMHO to separate those two modes of operations into two files (score.txt vs scaledscore.txt ?) to not break every legacy problem

Thoughts on this?

@Tagl
Copy link
Collaborator

Tagl commented Aug 20, 2024

I think separating is fine. Might make auto-updating packages easier too.

@eldering
Copy link
Collaborator

I have no strong opinions on the matter, but I have to say that when I was reading the specification it was not very clear due to the complex inter-dependence of "unbounded" and scores in subgroups, etc. So I think that indeed separating this will also make it clearer.

@evouga evouga mentioned this issue Sep 18, 2024
@niemela
Copy link
Member Author

niemela commented Feb 21, 2025

We did this. Closing.

@niemela niemela closed this as completed Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants