Problem 42396. the proud tradition of zero scores in Cody

Created by Alfonso Nieto-Castanon

Solve Later

{"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 short version is:</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:b/></w:rPr><w:t></w:t></w:r><w:r><w:rPr><w:b/><w:i/></w:rPr><w:t>your function should return a zero and also have a zero score/size</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>The long version comes with a little history:</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>There is a long tradition of attempting to modify the scoring function in Cody to be able to create problems that score solutions, for example, based on the solution running-time instead of the solution code-complexity. There is, of course, a parallel tradition of Cody players trying to \"game\" the system into getting the lowest possible score for their solutions.</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>Cody players are a very resourceful crowd, and very early into the game they found that overwriting the solution file (after it was evaluated) did the trick: Cody would then evaluate your solution size/code-complexity from the contents of the overwritten file so problem creators could overwrite the solutions with specially-crafted files that would return the desired solution score. Also solvers could overwrite their own files to get a 0 score if they so wished, simply adding</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"code\"/></w:pPr><w:r><w:t><![CDATA[!echo \"%\" > my_fcn_name.m]]></w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>to their solutions.</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>That state of affairs, naturally, perhaps sadly, did not last long, and Cody machinery was modified to score the solutions</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>before</w:t></w:r><w:r><w:t> the testsuite was run.</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>Of course this fix lasted even shorter, and Cody players found that the variable where that score was being stored could be accessed from the testsuite code using evalin('caller',...) or assignin('caller',...) syntax (yes, that variable was very amicably named</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>score</w:t></w:r><w:r><w:t>). So cody creators could now add the line</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"code\"/></w:pPr><w:r><w:t><![CDATA[assignin('caller','score',0);]]></w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>to their testsuite to give players a 0 (or any arbitrary) score.</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>This new scenario lasted for quite some time, probably because while problem creators could still modify the scoring function as they wish and create all forms of problems that departed from the size/complexity-based scoring, problem solvers could not do the same to get any arbitrary score. From the solution function perspective the variable</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>score</w:t></w:r><w:r><w:t> was two(!) steps up in the stack, and there is simply no way to use evalin('caller',...) syntax recursively along the lines of</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"code\"/></w:pPr><w:r><w:t><![CDATA[evalin('caller','assignin(''caller'',''score'',0)');]]></w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>Somewhat recently this situation changed again and Cody started using the Unit Testing framework to run solutions. That put</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>a lot</w:t></w:r><w:r><w:t> of layers between the testsuite and the coveted workspace where the</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>score</w:t></w:r><w:r><w:t> variable lived, making the assignin trick obsolete. In addition key Cody functionality was hidden into .p files, which added a small burden to exploring the inner workings of Cody, and the old</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>score</w:t></w:r><w:r><w:t> variable was nowhere to be found in those new functions.</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>Your job in this problem, following this proud tradition, is to get a zero score. Also your solution function should return a 0 as well, just to make it</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>do</w:t></w:r><w:r><w:t> something.</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>A few pointers to get you started would be:</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>the now somewhat obsolete</w:t></w:r><w:r><w:t> </w:t></w:r><w:hyperlink w:docLocation=\"http://www.mathworks.com/matlabcentral/cody/problems/1769-singularity-2-0-easier\"><w:r><w:t>singularity</w:t></w:r></w:hyperlink><w:r><w:t> series</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>the folder ~/+cody</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:hyperlink w:docLocation=\"http://www.mathworks.com/help/matlab/ref/dbstack.html\"><w:r><w:t>dbstack</w:t></w:r></w:hyperlink></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>Good luck and please hack responsibly!</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>ps1. if you are thinking of submitting an empty solution, no, that does not count (that is not a function and that is not returning any number).</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>ps2. if you are thinking of copy/pasting my own</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>SetSolutionScore</w:t></w:r><w:r><w:t> trick, that will not work here, sorry! (it is protected so that it only works when the testsuite code uses it; if you manage to disable this protection and make it work from within your solution file I will accept that as well as a valid solution)</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>ps3. if you want to use</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>SetSolutionScore</w:t></w:r><w:r><w:t> to be able to assign not-size-based scores in your own problems, simply copy/paste the relevant code in</w:t></w:r><w:r><w:t> </w:t></w:r><w:hyperlink w:docLocation=\"http://www.mathworks.com/matlabcentral/cody/problems/1192-say-something-funny/solutions/new#test_suite_body\"><w:r><w:t>this problem testsuite</w:t></w:r></w:hyperlink><w:r><w:t>.</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>SetSolutionScore</w:t></w:r><w:r><w:t>, like the old</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>assignin</w:t></w:r><w:r><w:t> trick, will not interfere with other problems (solvers cannot copy/paste your testsuite code to get zero-scores in other problems)</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:rPr><w:b/></w:rPr><w:t>note: please refrain from using this sort of Cody tricks to get leading scores in general non-hacking problems. That is just discorteous to other players</w:t></w:r><w:r><w:t> (add here rant about the regexp trick and how leading scores used to be worth pursuing).</w:t></w:r></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 short version is: your function should return a zero and also have a zero score/sizeThe long version comes with a little history:There is a long tradition of attempting to modify the scoring function in Cody to be able to create problems that score solutions, for example, based on the solution running-time instead of the solution code-complexity. There is, of course, a parallel tradition of Cody players trying to "game" the system into getting the lowest possible score for their solutions.Cody players are a very resourceful crowd, and very early into the game they found that overwriting the solution file (after it was evaluated) did the trick: Cody would then evaluate your solution size/code-complexity from the contents of the overwritten file so problem creators could overwrite the solutions with specially-crafted files that would return the desired solution score. Also solvers could overwrite their own files to get a 0 score if they so wished, simply adding<pre class="language-matlab">!echo "%" &gt; my_fcn_name.m
</pre>to their solutions.That state of affairs, naturally, perhaps sadly, did not last long, and Cody machinery was modified to score the solutions before the testsuite was run.Of course this fix lasted even shorter, and Cody players found that the variable where that score was being stored could be accessed from the testsuite code using evalin('caller',...) or assignin('caller',...) syntax (yes, that variable was very amicably named score). So cody creators could now add the line<pre class="language-matlab">assignin('caller','score',0);
</pre>to their testsuite to give players a 0 (or any arbitrary) score.This new scenario lasted for quite some time, probably because while problem creators could still modify the scoring function as they wish and create all forms of problems that departed from the size/complexity-based scoring, problem solvers could not do the same to get any arbitrary score. From the solution function perspective the variable score was two(!) steps up in the stack, and there is simply no way to use evalin('caller',...) syntax recursively along the lines of<pre class="language-matlab">evalin('caller','assignin(''caller'',''score'',0)');
</pre>Somewhat recently this situation changed again and Cody started using the Unit Testing framework to run solutions. That put a lot of layers between the testsuite and the coveted workspace where the score variable lived, making the assignin trick obsolete. In addition key Cody functionality was hidden into .p files, which added a small burden to exploring the inner workings of Cody, and the old score variable was nowhere to be found in those new functions.Your job in this problem, following this proud tradition, is to get a zero score. Also your solution function should return a 0 as well, just to make it do something.A few pointers to get you started would be:<ul><li>the now somewhat obsolete <a href = "http://www.mathworks.com/matlabcentral/cody/problems/1769-singularity-2-0-easier">singularity</a> series</li><li>the folder ~/+cody</li><li><a href = "http://www.mathworks.com/help/matlab/ref/dbstack.html">dbstack</a></li></ul>Good luck and please hack responsibly!ps1. if you are thinking of submitting an empty solution, no, that does not count (that is not a function and that is not returning any number).ps2. if you are thinking of copy/pasting my own SetSolutionScore trick, that will not work here, sorry! (it is protected so that it only works when the testsuite code uses it; if you manage to disable this protection and make it work from within your solution file I will accept that as well as a valid solution)ps3. if you want to use SetSolutionScore to be able to assign not-size-based scores in your own problems, simply copy/paste the relevant code in <a href = "http://www.mathworks.com/matlabcentral/cody/problems/1192-say-something-funny/solutions/new#test_suite_body">this problem testsuite</a>. SetSolutionScore, like the old assignin trick, will not interfere with other problems (solvers cannot copy/paste your testsuite code to get zero-scores in other problems)note: please refrain from using this sort of Cody tricks to get leading scores in general non-hacking problems. That is just discorteous to other players (add here rant about the regexp trick and how leading scores used to be worth pursuing).

The short version is: *_your function should return a zero and also have a zero score/size_*

The long version comes with a little history:

There is a long tradition of attempting to modify the scoring function in Cody to be able to create problems that score solutions, for example, based on the solution running-time instead of the solution code-complexity. There is, of course, a parallel tradition of Cody players trying to "game" the system into getting the lowest possible score for their solutions.
 
Cody players are a very resourceful crowd, and very early into the game they found that overwriting the solution file (after it was evaluated) did the trick: Cody would then evaluate your solution size/code-complexity from the contents of the overwritten file so problem creators could overwrite the solutions with specially-crafted files that would return the desired solution score. Also solvers could overwrite their own files to get a 0 score if they so wished, simply adding

!echo "%" > my_fcn_name.m

to their solutions.

That state of affairs, naturally, perhaps sadly, did not last long, and Cody machinery was modified to score the solutions _before_ the testsuite was run.

Of course this fix lasted even shorter, and Cody players found that the variable where that score was being stored could be accessed from the testsuite code using evalin('caller',...) or assignin('caller',...) syntax (yes, that variable was very amicably named _score_). So cody creators could now add the line

assignin('caller','score',0);

to their testsuite to give players a 0 (or any arbitrary) score.

This new scenario lasted for quite some time, probably because while problem creators could still modify the scoring function as they wish and create all forms of problems that departed from the size/complexity-based scoring, problem solvers could not do the same to get any arbitrary score. From the solution function perspective the variable _score_ was two(!) steps up in the stack, and there is simply no way to use evalin('caller',...) syntax recursively along the lines of

evalin('caller','assignin(''caller'',''score'',0)');
 
Somewhat recently this situation changed again and Cody started using the Unit Testing framework to run solutions. That put _a lot_ of layers between the testsuite and the coveted workspace where the _score_ variable lived, making the assignin trick obsolete. In addition key Cody functionality was hidden into .p files, which added a small burden to exploring the inner workings of Cody, and the old _score_ variable was nowhere to be found in those new functions.

Your job in this problem, following this proud tradition, is to get a zero score. Also your solution function should return a 0 as well, just to make it _do_ something.

A few pointers to get you started would be:

* the now somewhat obsolete <http://www.mathworks.com/matlabcentral/cody/problems/1769-singularity-2-0-easier singularity> series
* the folder ~/+cody
* <http://www.mathworks.com/help/matlab/ref/dbstack.html dbstack>

Good luck and please hack responsibly!

ps1. if you are thinking of submitting an empty solution, no, that does not count (that is not a function and that is not returning any number).

ps2. if you are thinking of copy/pasting my own _SetSolutionScore_ trick, that will not work here, sorry! (it is protected so that it only works when the testsuite code uses it; if you manage to disable this protection and make it work from within your solution file I will accept that as well as a valid solution)

ps3. if you want to use _SetSolutionScore_ to be able to assign not-size-based scores in your own problems, simply copy/paste the relevant code in <http://www.mathworks.com/matlabcentral/cody/problems/1192-say-something-funny/solutions/new#test_suite_body this problem testsuite>. _SetSolutionScore_, like the old _assignin_ trick, will not interfere with other problems (solvers cannot copy/paste your testsuite code to get zero-scores in other problems)

*note: please refrain from using this sort of Cody tricks to get leading scores in general non-hacking problems. That is just discorteous to other players* (add here rant about the regexp trick and how leading scores used to be worth pursuing).

Solve

Solution Stats

101 Solutions
12 Solvers

Last Solution submitted on Oct 17, 2022

Last 200 Solutions

Problem Comments

1 Comment

1 Comment

Alfonso Nieto-Castanon on 28 Oct 2017

this problem is working again (note: there have been a few changes to Cody machinery so many of the old tricks no longer work :)

Solution Comments

Solution 963036

1 Comment

1 Comment

Mikhail on 8 Sep 2016

I managed to pass your testsuite and yet have a solution of non-zero-size.
Funny, eh?

Solution 690285

1 Comment

1 Comment

Alfonso Nieto-Castanon on 23 Jun 2015

Thanks for catching that! I modified the testsuite to fix this but will not rescore this solution (I am trying my testsuite to *only* pass solutions that will get a zero score in Cody as well; it is a bit hard to do that without being too heavy handed and/or interfering with the ways solvers might get that zero score)

Solution 689411

1 Comment

1 Comment

Adrian Stannard on 24 Nov 2020

"Please refrain from using this sort of Cody tricks to get leading scores in general non-hacking problems. That is just discourteous to other players". Yet you do exactly this on Problem 1. What a tit.

Problem Recent Solvers12

Problem Tags

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!