fair scoring for cody -凯发k8网页登录

created by nicholas howe

{"relationships":[{"relationshiptype":"http://schemas.mathworks.com/matlab/code/2013/relationships/document","targetmode":"","relationshipid":"rid1","target":"/matlab/document.xml"},{"relationshiptype":"http://schemas.mathworks.com/matlab/code/2013/relationships/output","targetmode":"","relationshipid":"rid2","target":"/matlab/output.xml"}],"parts":[{"parturi":"/matlab/document.xml","relationship":[],"contenttype":"application/vnd.mathworks.matlab.code.document xml","content":"<?xml version=\"1.0\" encoding=\"utf-8\"?>\n<w:document xmlns:w=\"http://schemas.openxmlformats.org/wordprocessingml/2006/main\"><w:body><w:p><w:ppr><w:pstyle w:val=\"text\"/></w:ppr><w:r><w:t>the length-based scoring system for cody has a few well-known loopholes that allow clever programmers to hide complex code inside certain functions so that it doesn't register in the score. this problem represents an attempt to generate a fairer cody scoring function. it doesn't try to replace the length-based criterion with something more elegant; merely to eliminate places where longer code can be hidden and remain undetected by the scoring function.</w:t></w:r></w:p><w:p><w:ppr><w:pstyle w:val=\"text\"/></w:ppr><w:r><w:t>i have included a few examples that i consider abusive to start with. these are just my own opinions. please feel free to add your suggestions for others in the comments section for this problem, and i will add good ideas to the test suite when i have the time. thanks for playing!</w:t></w:r></w:p><w:p><w:ppr><w:pstyle w:val=\"listparagraph\"/><w:numpr><w:numid w:val=\"1\"/></w:numpr></w:ppr><w:r><w:t>regexp: count number of nodes inside (?@cmd) and add to total</w:t></w:r></w:p><w:p><w:ppr><w:pstyle w:val=\"listparagraph\"/><w:numpr><w:numid w:val=\"1\"/></w:numpr></w:ppr><w:r><w:t>regexprep: count number of nodes inside {$cmd} and add to total</w:t></w:r></w:p><w:p><w:ppr><w:pstyle w:val=\"text\"/></w:ppr><w:r><w:t>using this scoring function, it might even be possible to allow use of eval.</w:t></w:r></w:p><w:p><w:ppr><w:pstyle w:val=\"listparagraph\"/><w:numpr><w:numid w:val=\"1\"/></w:numpr></w:ppr><w:r><w:t>eval: count number of nodes inside argument to be evaluated and add to total</w:t></w:r></w:p><w:p><w:ppr><w:pstyle w:val=\"text\"/></w:ppr><w:r><w:t>other possibilities -- should str2num count the numbers inside its argument? suggestions welcome! and if you support the idea of changing the scoring function along these lines, please 'like' this problem. thanks!</w:t></w:r></w:p><w:p><w:ppr><w:pstyle w:val=\"text\"/></w:ppr><w:r><w:t>see also</w:t></w:r><w:r><w:t> </w:t></w:r><w:hyperlink w:doclocation=\"http://www.mathworks.com/matlabcentral/cody/problems/2033-poll-would-you-like-the-regexp-cmd-functionality-to-be-banned-in-cody\"><w:r><w:t>http://www.mathworks.com/matlabcentral/cody/problems/2033-poll-would-you-like-the-regexp-cmd-functionality-to-be-banned-in-cody</w:t></w:r></w:hyperlink></w:p></w:body></w:document>"},{"parturi":"/matlab/output.xml","contenttype":"text/xml","content":"<?xml version=\"1.0\" encoding=\"utf-8\" standalone=\"no\" ?><embeddedoutputs><metadata><evaluationstate>manual</evaluationstate><layoutstate>code</layoutstate><outputstatus>ready</outputstatus></metadata><outputarray type=\"array\"/><regionarray type=\"array\"/></embeddedoutputs>"}]}

the length-based scoring system for cody has a few well-known loopholes that allow clever programmers to hide complex code inside certain functions so that it doesn't register in the score. this problem represents an attempt to generate a fairer cody scoring function. it doesn't try to replace the length-based criterion with something more elegant; merely to eliminate places where longer code can be hidden and remain undetected by the scoring function.i have included a few examples that i consider abusive to start with. these are just my own opinions. please feel free to add your suggestions for others in the comments section for this problem, and i will add good ideas to the test suite when i have the time. thanks for playing!<ul><li>regexp: count number of nodes inside (?@cmd) and add to total</li><li>regexprep: count number of nodes inside {$cmd} and add to total</li></ul>using this scoring function, it might even be possible to allow use of eval.<ul><li>eval: count number of nodes inside argument to be evaluated and add to total</li></ul>other possibilities -- should str2num count the numbers inside its argument? suggestions welcome! and if you support the idea of changing the scoring function along these lines, please 'like' this problem. thanks!see also <a href = "http://www.mathworks.com/matlabcentral/cody/problems/2033-poll-would-you-like-the-regexp-cmd-functionality-to-be-banned-in-cody">http://www.mathworks.com/matlabcentral/cody/problems/2033-poll-would-you-like-the-regexp-cmd-functionality-to-be-banned-in-cody</a>

the length-based scoring system for cody has a few well-known loopholes that allow clever programmers to hide complex code inside certain functions so that it doesn't register in the score.  this problem represents an attempt to generate a fairer cody scoring function.  it doesn't try to replace the length-based criterion with something more elegant; merely to eliminate places where longer code can be hidden and remain undetected by the scoring function.
i have included a few examples that i consider abusive to start with.  these are just my own opinions.  please feel free to add your suggestions for others in the comments section for this problem, and i will add good ideas to the test suite when i have the time.  thanks for playing!
* regexp:  count number of nodes inside (?@cmd) and add to total
* regexprep:  count number of nodes inside {$cmd} and add to total
using this scoring function, it might even be possible to allow use of eval.
* eval:  count number of nodes inside argument to be evaluated and add to total
other possibilities -- should str2num count the numbers inside its argument?  suggestions welcome!  and if you support the idea of changing the scoring function along these lines, please 'like' this problem.  thanks!
see also http://www.mathworks.com/matlabcentral/cody/problems/2033-poll-would-you-like-the-regexp-cmd-functionality-to-be-banned-in-cody

solution stats

last submitted on jun 07, 2023

last 200 solutions

problem comments

9 comments

9 comments

show 6 older comments

on 25 jun 2014

i think this is a very interesting proposal.
so this kind of tricks still allowed in cody, but they will be counted in a fair way.
i used this a couple of times, and i think it is useful to learn this kind of coding methods, but it is not the real meaning of cody.

the most trick i used is the "str2num" one. to count all the numbers inside is a little bit hard, but i will accept this method also. it's fair! ;-)

on 26 jun 2014

i believe you need to redefine the 'newline' variable in all of your testsuite cases?

on 26 jun 2014

this is a very hard problem to solve in general. for example consider the following cases (the score in the first three cases should be penalized with additional 4 points, while in the latter three cases it should not): 1) regexp('',strcat('(?','@a=1)')); 2) str='(?@a=1)';regexp('',str); 3) regexp(' ',char(')@ab>2*'-1)); 4) regexp('',strcat('(?','a=1)')); 5) str='(?@a=1)';regexp(str,''); 6) regexp(' ',char(')@ab>2*' 1));

nicholas howe on 26 jun 2014

alfonso, thank you for your excellent thinking on this subject. you're quite right that an approach based only on parsing the program text would be hard to perfect. one could at least make people work harder to get around the scoring system! but what do you think of a different approach: modifying the definitions of regexp and its ilk on the cody machines so that they dynamically alter the score when called with eval-like arguments?

on 26 jun 2014

hi nicholas, that is a very good idea, the main problem would be to solve the correspondence between the different times regexp is called and the different times it might appear in the code, but perhaps using dbstack we could resolve this? (of course we could just penalize for each time it is called even if that might produce very high penalties for loops, etc.) thoughts?

nicholas howe on 26 jun 2014

the same regexp expression could potentially be called more than once with different dynamic code each time. it might be best to count the score of each unique code string from each separate invocation point -- that seems most in keeping with the spirit of the current rules. you're right that it would be quite complex to keep track.

thanks for pointing out the problem with newline, by the way. i think it is fixed now.

on 1 nov 2020

the easiest way would be to add a fixed size length penalty whenever using the regexp function, for instance, a 1000 points. when a problem requires the regexp function, every player would have the same penalty so it would be meaningless. and when the problem doesn't require it, the cody player would be disencouraged to use it.

ps: instead of banning functions, as cody currently does, a fixed point penalty for certain functions would disencourage their misuse while allowing players to fully explore matlab features.

on 1 nov 2020

and as a bonus, hacks would all have a high score, making them all the worst possible solutions. never the leading ones.

goc3 on 3 nov 2020

i like your ideas in this regard, rafael.

solution comments

problem recent solvers

problem tags

community treasure hunt

find the treasures in matlab central and discover how the community can help you!

start hunting!

fair scoring for cody -凯发k8网页登录

solution stats

last 200 solutions

problem comments

solution comments

problem recent solvers

suggested problems

more from this author

problem tags

community treasure hunt

fair scoring for cody -凯发k8网页登录

solution stats

last 200 solutions

problem comments

solution comments

problem recent solvers

suggested problems

more from this author

problem tags

community treasure hunt

players

wechat