Hi all,
First a happy new year to all!
Thijs, Jan, and I talked about doing a DOMjudge hackathon day. We propose the weekend of 23/24 January. Who else is interested in joning and do you have a preference for Saturday 23rd or Sunday 24th?
Jaap
I’m always in favor of hackathons :).
For me the 23th is not ideal as I’m helping a friend move that day. So the 24th is better.
Regards,
Nicky
On 3 jan. 2016, at 10:31, Jaap Eldering jaap@jaapeldering.nl wrote:
Hi all,
First a happy new year to all!
Thijs, Jan, and I talked about doing a DOMjudge hackathon day. We propose the weekend of 23/24 January. Who else is interested in joning and do you have a preference for Saturday 23rd or Sunday 24th?
Jaap _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
Hi Jaap,
At what time do you plan to start the hackathon on either of the day ?
Umair
On Sun, Jan 3, 2016 at 3:04 PM, Nicky Gerritsen nickygerritsen@me.com wrote:
I’m always in favor of hackathons :).
For me the 23th is not ideal as I’m helping a friend move that day. So the 24th is better.
Regards,
Nicky
On 3 jan. 2016, at 10:31, Jaap Eldering jaap@jaapeldering.nl wrote:
Hi all,
First a happy new year to all!
Thijs, Jan, and I talked about doing a DOMjudge hackathon day. We propose the weekend of 23/24 January. Who else is interested in joning and do you have a preference for Saturday 23rd or Sunday 24th?
Jaap _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
There is no concrete plan yet, but we probably start around 10-11am CET (UTC+1).
Jaap
On 03-01-16 17:01, Umair Khan wrote:
Hi Jaap,
At what time do you plan to start the hackathon on either of the day ?
Umair
On Sun, Jan 3, 2016 at 3:04 PM, Nicky Gerritsen <nickygerritsen@me.com mailto:nickygerritsen@me.com> wrote:
I’m always in favor of hackathons :). For me the 23th is not ideal as I’m helping a friend move that day. So the 24th is better. Regards, Nicky > On 3 jan. 2016, at 10:31, Jaap Eldering <jaap@jaapeldering.nl <mailto:jaap@jaapeldering.nl>> wrote: > > Hi all, > > First a happy new year to all! > > Thijs, Jan, and I talked about doing a DOMjudge hackathon day. We > propose the weekend of 23/24 January. Who else is interested in joning > and do you have a preference for Saturday 23rd or Sunday 24th? > > Jaap > _______________________________________________ > DOMjudge-devel mailing list > DOMjudge-devel@domjudge.org <mailto:DOMjudge-devel@domjudge.org> > https://www.domjudge.org/mailman/listinfo/domjudge-devel _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org <mailto:DOMjudge-devel@domjudge.org> https://www.domjudge.org/mailman/listinfo/domjudge-devel
Hi,
*Jaap Eldering jaap@jaapeldering.nl [16/01/03]:
Thijs, Jan, and I talked about doing a DOMjudge hackathon day. We propose the weekend of 23/24 January. Who else is interested in joning and do you have a preference for Saturday 23rd or Sunday 24th?
In general, a hackathon sounds like a great idea. But I am not sure now what my schedule looks like on these days. So make plans without me and I'll join if I can.
Tobi
Hi all,
Great idea, and I was thinking about joining this hackathon for a change, but unfortunately (or maybe fortunately) I have decided to go on a skiing holiday that weekend so neither of the days work out for me.
Regards, Jeroen
Hi all,
First a happy new year to all!
Thijs, Jan, and I talked about doing a DOMjudge hackathon day. We propose the weekend of 23/24 January. Who else is interested in joning and do you have a preference for Saturday 23rd or Sunday 24th?
Jaap
Hi all,
Since I've only heard Nicky with a specific preference for Sunday, let's do the hackaton on Sunday 24 January. We'll probably organize a real-life gettogether in Utrecht starting around 10-11 am CET. Anyone interested to join either in real life or online, do let us know.
Best, Jaap
On 12-01-16 10:32, Jeroen Bransen wrote:
Hi all,
Great idea, and I was thinking about joining this hackathon for a change, but unfortunately (or maybe fortunately) I have decided to go on a skiing holiday that weekend so neither of the days work out for me.
Regards, Jeroen
Hi all,
First a happy new year to all!
Thijs, Jan, and I talked about doing a DOMjudge hackathon day. We propose the weekend of 23/24 January. Who else is interested in joning and do you have a preference for Saturday 23rd or Sunday 24th?
Jaap
DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
Ah real-life, I like it :). I guess I can train to Utrecht.
Regards,
Nicky
On 12 jan. 2016, at 22:08, Jaap Eldering jaap@jaapeldering.nl wrote:
Hi all,
Since I've only heard Nicky with a specific preference for Sunday, let's do the hackaton on Sunday 24 January. We'll probably organize a real-life gettogether in Utrecht starting around 10-11 am CET. Anyone interested to join either in real life or online, do let us know.
Best, Jaap
On 12-01-16 10:32, Jeroen Bransen wrote:
Hi all,
Great idea, and I was thinking about joining this hackathon for a change, but unfortunately (or maybe fortunately) I have decided to go on a skiing holiday that weekend so neither of the days work out for me.
Regards, Jeroen
Hi all,
First a happy new year to all!
Thijs, Jan, and I talked about doing a DOMjudge hackathon day. We propose the weekend of 23/24 January. Who else is interested in joning and do you have a preference for Saturday 23rd or Sunday 24th?
Jaap
DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
Hi all,
This is to confirm that we will do the hackathon tomorrow. At least Thijs, Nicky, Jan and I will organize ourselves at Thijs' place tomorrow, starting around 11am CET (UTC+1). We will certainly be available via the IRC channel and if people are interested we could have a skype call to discuss things to work on.
Some issues that could be worked on: - Improve the UI for adding a combined user+team, both manually in the webinterface and via import. - Allow filtering the submissions list on teams,problems,languages,etc.
A bug/feature list from previous contests (not sure if these are fixed): - Import clarifications in the XML/REST import script? - The XML event feed import removes contest freezetime. - testcase -> judging_run delete does not cascade - Merge executable overview,code pages pages into a single one, also for editing. - Add a 'delete all' button for testcases on problem page? - Cleanup testcase page? Add easier reordering of testcases? - Uploading an archive to a problem that is part of a selected contest should default to adding to that contestproblem data as well. - Do not assume that passing output limit results in wrong-answer (it could be time-limit, run-error)
And finally, anything from https://github.com/DOMjudge/domjudge/issues
Some issues for discussion: - (How to) run the compilation phase in a chroot? This requires more dependencies in the chroot environment, conflict of /bin mountpoint, /tmp, ... - Integrate any features from online-judge branch?
Suggestions for other features welcome (also from people who are not going to join tomorrow)!
Best, Jaap
On 12-01-16 22:35, Nicky Gerritsen wrote:
Ah real-life, I like it :). I guess I can train to Utrecht.
Regards,
Nicky
On 12 jan. 2016, at 22:08, Jaap Eldering jaap@jaapeldering.nl wrote:
Hi all,
Since I've only heard Nicky with a specific preference for Sunday, let's do the hackaton on Sunday 24 January. We'll probably organize a real-life gettogether in Utrecht starting around 10-11 am CET. Anyone interested to join either in real life or online, do let us know.
Best, Jaap
On 12-01-16 10:32, Jeroen Bransen wrote:
Hi all,
Great idea, and I was thinking about joining this hackathon for a change, but unfortunately (or maybe fortunately) I have decided to go on a skiing holiday that weekend so neither of the days work out for me.
Regards, Jeroen
Hi all,
First a happy new year to all!
Thijs, Jan, and I talked about doing a DOMjudge hackathon day. We propose the weekend of 23/24 January. Who else is interested in joning and do you have a preference for Saturday 23rd or Sunday 24th?
Jaap
DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
Jaap Eldering wrote:
This is to confirm that we will do the hackathon tomorrow. At least Thijs, Nicky, Jan and I will organize ourselves at Thijs' place tomorrow, starting around 11am CET (UTC+1). We will certainly be available via the IRC channel and if people are interested we could have a skype call to discuss things to work on.
Unfortunately, this is at 2 AM in the greater Los Angeles area. There once was a time when I would have been programming at that hour, but no longer. :-)
Some issues that could be worked on:
- Improve the UI for adding a combined user+team, both manually in the
webinterface and via import.
- Allow filtering the submissions list on teams,problems,languages,etc.
I would really like to see the ability to import users and teams (with passwords), so if you are taking priority requests, that is one of mine.
[...]
Some issues for discussion:
- (How to) run the compilation phase in a chroot? This requires more
dependencies in the chroot environment, conflict of /bin mountpoint, /tmp, ...
- Integrate any features from online-judge branch?
I would also like to see the ability for teams to download any test cases (input and output) that are marked as "sample". I believe that is offered in the online-judge branch, although I have not looked at it.
Suggestions for other features welcome (also from people who are not going to join tomorrow)!
One thing we would like to be able to do is to include a message with an execution result as part of the review process. We normally do this to comply with the (perhaps older) rule that a run-time error result should include the nature of the error, but not any information that would disclose information about the judges' secret data. For example, a contestant can be told "Segmentation Fault", or even "Index out of range", but not a line number or call trace. This would be done as part of the verification process.
Marc
On 23-01-16 18:21, Marc Furon wrote:
Jaap Eldering wrote:
This is to confirm that we will do the hackathon tomorrow. At least Thijs, Nicky, Jan and I will organize ourselves at Thijs' place tomorrow, starting around 11am CET (UTC+1). We will certainly be available via the IRC channel and if people are interested we could have a skype call to discuss things to work on.
Unfortunately, this is at 2 AM in the greater Los Angeles area. There once was a time when I would have been programming at that hour, but no longer. :-)
We'll work throughout the day so you're welcome to join at a more reasonable local time ;-) but don't feel any obligation.
Some issues that could be worked on:
- Improve the UI for adding a combined user+team, both manually in the
webinterface and via import.
- Allow filtering the submissions list on teams,problems,languages,etc.
I would really like to see the ability to import users and teams (with passwords), so if you are taking priority requests, that is one of mine.
Ok, we'll take it into account.
Some issues for discussion:
- (How to) run the compilation phase in a chroot? This requires more
dependencies in the chroot environment, conflict of /bin mountpoint, /tmp, ...
- Integrate any features from online-judge branch?
I would also like to see the ability for teams to download any test cases (input and output) that are marked as "sample". I believe that is offered in the online-judge branch, although I have not looked at it.
That sounds like a reasonable feature to port.
Suggestions for other features welcome (also from people who are not going to join tomorrow)!
One thing we would like to be able to do is to include a message with an execution result as part of the review process. We normally do this to comply with the (perhaps older) rule that a run-time error result should include the nature of the error, but not any information that would disclose information about the judges' secret data. For example, a contestant can be told "Segmentation Fault", or even "Index out of range", but not a line number or call trace. This would be done as part of the verification process.
Ok, so this would essentially be a message manually entered by the judges at verification, but shown to the team, right?
Jaap
Jaap Eldering wrote:
One thing we would like to be able to do is to include a message with an execution result as part of the review process. We normally do this to comply with the (perhaps older) rule that a run-time error result should include the nature of the error, but not any information that would disclose information about the judges' secret data. For example, a contestant can be told "Segmentation Fault", or even "Index out of range", but not a line number or call trace. This would be done as part of the verification process.
Ok, so this would essentially be a message manually entered by the judges at verification, but shown to the team, right?
Yes, that is correct. It would be fine if this was available for any result, although we would normally only expect to use it in the case of a run-time error. The old Southern California contest software would prompt for such a message for any attempt that resulted in a run-time error.
Marc
On Sat, January 23, 2016 18:21, Marc Furon wrote:
I would also like to see the ability for teams to download any test cases (input and output) that are marked as "sample". I believe that is offered in the online-judge branch, although I have not looked at it.
Done.
Cheers, Thijs
This is my tiny contribution for this hackathon :-)
By coincidence, tomorrow we will have a local contests in my University in Madrid and we will use DOMjudge. We have three different problems categories with different level of difficulty, because our contestants have different programming background. We want those categories to be visible in the scoreboard.
I've changed libwww/scoreboard.php so each column belongs to a CSS class specific for the problem Id. After that, style.css can be changed with something like:
.probId-5 { background-color: blue; }
so the column for that problem is shadowed. A better solution would have been to integrate the color into the problem DB, but that would have been too much for me, I'm afraid.
Please find attach a .patch file (I hope it will be correct). Note that I'm using DOMjudge 5.0; I hope it will be valid also for the last version and it is considered useful enough to be added :-)
Congratulation for your software! Pedro Pablo
On Sun, Jan 24, 2016 at 4:51 PM, Thijs Kinkhorst thijs@kinkhorst.com wrote:
On Sat, January 23, 2016 18:21, Marc Furon wrote:
I would also like to see the ability for teams to download any test cases (input and output) that are marked as "sample". I believe that is offered in the online-judge branch, although I have not looked at it.
Done.
Cheers, Thijs _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
I my... I've sent the old (and wrong) version. Sorry for that.
On Sun, Jan 24, 2016 at 5:16 PM, PEDRO PABLO GOMEZ MARTIN <pedrop@fdi.ucm.es
wrote:
This is my tiny contribution for this hackathon :-)
By coincidence, tomorrow we will have a local contests in my University in Madrid and we will use DOMjudge. We have three different problems categories with different level of difficulty, because our contestants have different programming background. We want those categories to be visible in the scoreboard.
I've changed libwww/scoreboard.php so each column belongs to a CSS class specific for the problem Id. After that, style.css can be changed with something like:
.probId-5 { background-color: blue; }
so the column for that problem is shadowed. A better solution would have been to integrate the color into the problem DB, but that would have been too much for me, I'm afraid.
Please find attach a .patch file (I hope it will be correct). Note that I'm using DOMjudge 5.0; I hope it will be valid also for the last version and it is considered useful enough to be added :-)
Congratulation for your software! Pedro Pablo
On Sun, Jan 24, 2016 at 4:51 PM, Thijs Kinkhorst thijs@kinkhorst.com wrote:
On Sat, January 23, 2016 18:21, Marc Furon wrote:
I would also like to see the ability for teams to download any test cases (input and output) that are marked as "sample". I believe that is offered in the online-judge branch, although I have not looked at it.
Done.
Cheers, Thijs _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
Hi Pedro Pablo,
Thanks for your contribution! I'll see what the best way to merge it be. One thing that I'm considering is that if you fix the HTML, one would still be needing to edit CSS. So would it add much value in the main branch on its own I'm wondering?
Cheers, Thijs
On Sun, January 24, 2016 17:28, PEDRO PABLO GOMEZ MARTIN wrote:
I my... I've sent the old (and wrong) version. Sorry for that.
On Sun, Jan 24, 2016 at 5:16 PM, PEDRO PABLO GOMEZ MARTIN <pedrop@fdi.ucm.es
wrote:
This is my tiny contribution for this hackathon :-)
By coincidence, tomorrow we will have a local contests in my University in Madrid and we will use DOMjudge. We have three different problems categories with different level of difficulty, because our contestants have different programming background. We want those categories to be visible in the scoreboard.
I've changed libwww/scoreboard.php so each column belongs to a CSS class specific for the problem Id. After that, style.css can be changed with something like:
.probId-5 { background-color: blue; }
so the column for that problem is shadowed. A better solution would have been to integrate the color into the problem DB, but that would have been too much for me, I'm afraid.
Please find attach a .patch file (I hope it will be correct). Note that I'm using DOMjudge 5.0; I hope it will be valid also for the last version and it is considered useful enough to be added :-)
Congratulation for your software! Pedro Pablo
On Sun, Jan 24, 2016 at 4:51 PM, Thijs Kinkhorst thijs@kinkhorst.com wrote:
On Sat, January 23, 2016 18:21, Marc Furon wrote:
I would also like to see the ability for teams to download any test cases (input and output) that are marked as "sample". I believe that is offered in the online-judge branch, although I have not looked at
it.
Done.
Cheers, Thijs _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
Hello Thijs,
Sorry for the delay, but I'm sure you know how stressful a contest day can be :-)
Thanks for your contribution!
I'll see what the best way to merge it be. One thing that I'm considering is that if you fix the HTML, one would still be needing to edit CSS. So would it add much value in the main branch on its own I'm wondering?
Well, I think that could be useful for others, but it's just an opinion. In fact, I've done this same change in previous versions of DOMjudge, although I've never submitted as a patch. I'm aware that changing the CSS is still a bit boring because server access is needed. But that is also true for other things, such as using create_accounts to avoid too manual work registering teams/users. No so many versions ago, access was also needed for changing the compilation and executions tools, configuring team logos (that now has been in fact dropped, AFAI, at least in 4.x), and so on. Your developer tendency today is to avoid the necesity for that local access, and that is really great. So I'm sure it would have been a better contribution adding something as "problem categories" so the column color could be configured in the frontend instead of patching the CSS. But in the meantime (and because I'm not so competent with DOMjudge source code :( ) I feel using CSS could be good enough. After all, I've being using DOMjudge since 2010 and I've always had access to the server so I don't think this is a hard restrinction :-)
Anyway, this is obviously an opinion :-) and you have a better vision of the DOMjudge future development, so I will understand any decision about this unimportant change :-) Nevertheless, for claryfing myself, what we have done is a small contest with students from three different level courses, but just a problem set. There were problems adapted for each student level, and we have used different points for each problem. What we wanted was to be able to shade each problem column depending on the problem category (and points). Teams categories had the same color as a hint showing what problems were created with what students in mind. Nevertheless, any student could submit a solution for any problem. This is the first rows of our final scoreboard where colors are quite meanful.
[image: Inline image 1]
The first four teams were in the fifth semeter, and the last two problems were specifically created for them. The other two problem/students categories were beginners and intermediate.
Anyway, thank you for your work. You've made possible many local programming contests around the world that would have not existed without DOMjudge. Pedro Pablo
Cheers, Thijs
On Sun, January 24, 2016 17:28, PEDRO PABLO GOMEZ MARTIN wrote:
I my... I've sent the old (and wrong) version. Sorry for that.
On Sun, Jan 24, 2016 at 5:16 PM, PEDRO PABLO GOMEZ MARTIN <pedrop@fdi.ucm.es
wrote:
This is my tiny contribution for this hackathon :-)
By coincidence, tomorrow we will have a local contests in my University in Madrid and we will use DOMjudge. We have three different problems categories with different level of difficulty, because our contestants have different programming background. We want those categories to be visible in the scoreboard.
I've changed libwww/scoreboard.php so each column belongs to a CSS class specific for the problem Id. After that, style.css can be changed with something like:
.probId-5 { background-color: blue; }
so the column for that problem is shadowed. A better solution would have been to integrate the color into the problem DB, but that would have been too much for me, I'm afraid.
Please find attach a .patch file (I hope it will be correct). Note that I'm using DOMjudge 5.0; I hope it will be valid also for the last version and it is considered useful enough to be added :-)
Congratulation for your software! Pedro Pablo
On Sun, Jan 24, 2016 at 4:51 PM, Thijs Kinkhorst thijs@kinkhorst.com wrote:
On Sat, January 23, 2016 18:21, Marc Furon wrote:
I would also like to see the ability for teams to download any test cases (input and output) that are marked as "sample". I believe that is offered in the online-judge branch, although I have not looked at
it.
Done.
Cheers, Thijs _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
Thijs Kinkhorst wrote:
On Sat, January 23, 2016 18:21, Marc Furon wrote:
I would also like to see the ability for teams to download any test cases (input and output) that are marked as "sample". I believe that is offered in the online-judge branch, although I have not looked at it.
Done.
That is good news--thank you! This will be a big help for our regional contest.
Marc
Thijs Kinkhorst wrote:
On Sat, January 23, 2016 18:21, Marc Furon wrote:
I would also like to see the ability for teams to download any test cases (input and output) that are marked as "sample". I believe that is offered in the online-judge branch, although I have not looked at it.
Done.
Did this feature make it into the 5.1.2 release? I looked for the capability but did not see it. Perhaps I was just not looking in the proper place...
Marc
On 13-09-16 01:27, Marc Furon wrote:
Thijs Kinkhorst wrote:
On Sat, January 23, 2016 18:21, Marc Furon wrote:
I would also like to see the ability for teams to download any test cases (input and output) that are marked as "sample". I believe that is offered in the online-judge branch, although I have not looked at it.
Done.
Did this feature make it into the 5.1.2 release? I looked for the capability but did not see it. Perhaps I was just not looking in the proper place...
No, that only landed in the master branch, see
https://github.com/DOMjudge/domjudge/commit/14fe242a539173e3fae2f9b18d5bdfe3...
Jaap
-
Jaap Eldering -
Jeroen Bransen -
Marc Furon -
Nicky Gerritsen -
PEDRO PABLO GOMEZ MARTIN -
Thijs Kinkhorst -
Tobias Werth -
Umair Khan