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

Allow marking "model solutions" #317

Open
niemela opened this issue Aug 19, 2024 · 6 comments
Open

Allow marking "model solutions" #317

niemela opened this issue Aug 19, 2024 · 6 comments

Comments

@niemela
Copy link
Member

niemela commented Aug 19, 2024

This is a bit of a fringe feature. Most systems would ignore it, but it would not be much work to support.

A model solution is a solution that the authors would be happy to publish as a "good correct solution." It's probably a bit polished, possibly even commented.

I would suggest adding model_solution: true in submissions.yaml.

@eldering
Copy link
Collaborator

I have a feeling it would barely or not all be used to select submissions for publication (also because typically the package would get published as a whole), so even though I agree it's very cheap to add, I'd lean to not do so. No objections though if others indeed feel it's useful.

@Tagl
Copy link
Contributor

Tagl commented Aug 19, 2024

I guess this is more of an educational feature that allows systems to identify these solutions with ease.

@evouga
Copy link
Collaborator

evouga commented Sep 18, 2024

I agree with eldering; this feature would have been useful when contest directors needed to manually extract test data and judge solutions to post on contest web sites. It’s less useful if full packages are now on a centralized archive.

@niemela
Copy link
Member Author

niemela commented Sep 19, 2024

It is still useful in an educational setting. The difference between a "model solution" and any other "accepted" solution is that the former is intended to be polished, commented, and idiomatic , whereas the latter is just expected to work.

When publishing solutions after a contest we don't really care about polished, commented, and idiomatic, and contest code is seldom those things, but in an educational setting we do.

In any case, I'm not hearing any strong opposition to this?

@eldering
Copy link
Collaborator

I feel a bit that this is feature creep. If this is not used to publish a selected set of model submissions, will this then first of all be used by authors to mark these model solutions, and secondly by students to see which ones are? I doubt that.

@niemela
Copy link
Member Author

niemela commented Sep 21, 2024

I feel a bit that this is feature creep. If this is not used to publish a selected set of model submissions, will this then first of all be used by authors to mark these model solutions, and secondly by students to see which ones are? I doubt that.

We already use something similar for education, so I would argue that I know that it would be used. Again, I don't think it will be used at contests much or at all.

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

4 participants