<p>Careful with question discussions.</p>
<p>Did you guys remember not to let your ArrayList loops go out of bounds? When you remove an object from an ArrayList, the ArrayList becomes shorter. So you can’t just use the loop control variable for getting and removing from an ArrayList.</p>
<p>That tripped me up a couple of times on practice tests :)</p>
<p>Free response was a joke. 45 minutes left to doodle…
the curve will certainly not be a bell this year, sorry collegebored</p>
<p>I didn’t let mine out of range. all you had to do was let your int in the loop go int–; after you were done the remove. the size() changes itself. Let’s stop the discussion though. I forgot about the 48 hour rule already. Talk to you guys thursday lol.</p>
<p>General question:</p>
<p>Can you convert an int into a double by assigning it to a double variable?</p>
<p>For example, lets say you have:</p>
<p>int number = 20;</p>
<p>double numberInDouble = number;</p>
<p>Is this the same as casting…?</p>
<p>Yeah he’s right arraylist automatically changes. you just can’t use for each loop when removing because then that’d be the problem, otherwise you’re fine.</p>
<p>Just a general question
Can they mark you off if you sort of mixed up your Arraylist / list instantiations and delcarations?</p>
<p>I may have done something like
name<locations>;
instead of
ArrayList<locations> name;</locations></locations></p>
<p>can they mark you off for
listname.(i) instead of listname.get(i)?</p>
<p>^ yeah you can , but it isn’t really the same as casting, casting doesn’t create a new variable. I doing what you did, the number is automatically cast.</p>
<p>Guys, be careful with CB. Just be patient and go study for your other APs till thursday. </p>
<p>I had about 45 mins left over in the FRQ, but I went over and checked it like four-five times (and I caught mistakes) so I sat the whole test. I had only ten minutes left on the MC tho, I used that for checking as well. It isn’t often that you get any checking time in the MC in AP exams though.</p>
<p>Oh yar, I suppose I could have just decremented it xD</p>
<p>@tito: Thanks.</p>
<p>Hey guys, I’m wondering do we all have the same test?
I thought mine was okay, not too easy, not too hard.
Mine had these FRQ’s
- forgot
- APLine class
- Hiking
- Gridworld</p>
<p>we all have the same test … remember, no discussing (unless you want to risk it)</p>
<p>i hate gridworld. but i like cookies. haha</p>
<p>yahh, you aren’t really supposed to talk about them ;)</p>
<p>//The last 10 pages of this thread in a nutshell
for (int daysLeft = 2; daysLeft>0; daysLeft–)
{
if (hasHubris)
System.out.println(“Wow that test was so easy! easy 5 for me!”);
else if (didntStudy)
System.out.println(“The MC was impossible!”);
else
System.out.println(“I thought the MC was a bit tricky but the FRQs weren’t so bad”);
}
liftEmbargo();
discussFRQs();</p>
<p>@darkeyes</p>
<p>getting a bit of the ole’ ap cs brainwash there?</p>
<p>HAh, i would be the else.</p>
<p>Well, I didn’t think the FRQ section was terrible- to be completely honest, I was dreading it. One question especially was awful for me (as it was for many, I bet).
I was expecting the MC to be a bit easier. A couple questions were just strange and took some time to decode. Otherwise, it was OK.
Am I the only one who feels this liberated and jovial?</p>
<p>Can’t wait until the third week of July… Ideas on the curve?</p>
<p>Yeah the MC was harder than I had expected. I’d expect the curve to be 60-65% for a 5. The reason it is this low is, I believe the standard dev will be more narrow, for example, 54% would be a 4, and 47% would be a 3 or something.</p>
<p>the curve will probably be a bit lower since there are more people taking this exam and since some AB stuff showed up on the exam
I’m expecting something like a 65%-70%ish for a 5</p>