<p>How would you be penalized if your code mostly, but then caused an ArrayIndexOutOfBounds exception because you accidentally went 1 beyond the last index of an array in a while loop?</p>
<p>Don’t you have to modify the act method, though, to make the bug remember its previous location/direction?</p>
<p>As for MC, I, unlike everyone else here, finished with 15-20 minutes to spare…I think my reading of all the loops was helped by doing Math contests, and it made it easier for me to recognise patters.</p>
<p>for the gridworld frq, what if you forgot to include a method… how many points off?</p>
<p>@garfieldliker </p>
<p>You override the act method
public void act()
{
//remember location & direction
super.act()
}</p>
<p>@garfieldliker yeah you had to modify the act method but as long as you called super.act it calls the unmodified act method of bug. But as long as the code works I don’t think ap graders will care whether super was used are not.</p>
<p>Hey guys on the gridworld FRQ did you have to call restore() in the act method? I was confused if it wanted us to actually call restore()</p>
<p>Yes, if you didn’t call it then the condition the question was asking for would not be met.</p>
<p>my biggest problems with the loops in mc tends to be that you’re never sure if you missed a tiny detail which can throw your whole answer off. There is usually time to check all the answers for the questions to make sure that none of the other answers work but for this test one a few questions I had to just pick the answer and go with it.</p>
<p>wait why did we have to call restore() in the act method itself. Wouldn’t that just repeteatedly put you into the same spot?</p>
<p>Yeah, that’s not right. You didn’t need to call restore(). The point was that if the user wanted to go back to the previous location and direction, they could do it using restore().</p>
<p>Hey guys,</p>
<p>I thought the test was ok. The MC was medium but since I am a freshmen and this is my first AP test my time management wasn’t good and finished only a minute before time was called. :(</p>
<p>As for FRQ it was the easiest thing in the world. I was a little worried with two-dimensional arrays for a little bit but I was able to remember all the code for looping through a 2d array thanks to the Barron’s book.</p>
<p>I HAVE A MAJOR QUESTION:</p>
<p>How hard are the FRQ’s graded?</p>
<p>I did well but I am wondering if they are super picky and check for efficiency and neatness and all that stuff. Will the only think tested be functionality?</p>
<p>If it is only functionality I am thinking I got a 40 on FRQ and maybe low 30’s for MC. I think that is a 5.</p>
<p>I called restore at the end of act but when I just plugged it into eclipse it does nothing. Who remembers the exact instructions on the test?</p>
<p>@compsci yeah i thought calling restore at the end of act would just make your bug stay where it is. </p>
<p>@youngster they mostly check for functionality but sometimes they might specify to not use code that could have otherwise been called by a getter public method. I don’t really think they care about efficiency. They might get very annoyed at inefficient code, but i don’t think they will dock points for it.</p>
<p>I don’t think we had to call the restore() method from the act() method. I think we just had to write it. Because as seen in the other examples, first ALL of the Actors in the grid “acted”, and THEN restore() was called on the bug. So, from there, you can conclude that restore() shouldn’t be included inside the act() method.</p>
<p>You think calling restore at the end would warrant points off? I mean the question was ambiguous. It didn’t explicitly state don’t call it.</p>
<p>Also, did you guys initialize your variables storing the previous location and direction to the bugs current location/direction when you declared them?</p>
<p>@youngster9
They are graded by rubric based on what they wanted to see, specific things. Whether you declared certain variables, called certain methods, traversed through certain arrays. Some incorrect attempts may get points but bonus points for correctness. </p>
<p>I am angry at myself. I would take a look at the loops, cancel out a few answers based on values I find produced, and if I couldn’t get a definitive answer in under around 2 minutes I would just put in a logical assumption and move on. But on the other hand I could have compiled in my mind and lost valuable time. I feel I got 2/3rds of the questions correct based off this.
The FRQ was a whole different story. The ONLY thing I had trouble with was traversing a 2D array, which I luckily got right in my recall of how to do it.</p>
<p>@HxCKhaos - It could, but maybe one point maximum. Not a lot, so don’t sweat it!</p>
<p>The first question on the FRQ, did you guys only have like 2 lines?</p>
<p>Yeah I think you are right about not calling it. It’s just ridiculous that they would tell us to design a method and not make it really clear to either call it or not call it. How many points off is that?</p>