3/29 lecture feedback results about 66 responses 4 1KnowP5.2-hints-compute-pwm: 1) very bad 14 1KnowP5.2-hints-compute-pwm: 2) bad 34 1KnowP5.2-hints-compute-pwm: 3) ok 13 1KnowP5.2-hints-compute-pwm: 4) good 2 1KnowP5.2-hints-compute-pwm: 5) very good 3 1LecP5.2-hints-compute-pwm: 1) very bad 7 1LecP5.2-hints-compute-pwm: 2) bad 40 1LecP5.2-hints-compute-pwm: 3) ok 17 1LecP5.2-hints-compute-pwm: 4) good 2 2KnowP5.2-hints-Plain-Condorcet-algorithm: 1) very bad 10 2KnowP5.2-hints-Plain-Condorcet-algorithm: 2) bad 43 2KnowP5.2-hints-Plain-Condorcet-algorithm: 3) ok 12 2KnowP5.2-hints-Plain-Condorcet-algorithm: 4) good 1 2LecP5.2-hints-Plain-Condorcet-algorithm: 1) very bad 7 2LecP5.2-hints-Plain-Condorcet-algorithm: 2) bad 36 2LecP5.2-hints-Plain-Condorcet-algorithm: 3) ok 23 2LecP5.2-hints-Plain-Condorcet-algorithm: 4) good 5 3KnowP5.3-hints-polygon: 1) very bad 17 3KnowP5.3-hints-polygon: 2) bad 26 3KnowP5.3-hints-polygon: 3) ok 18 3KnowP5.3-hints-polygon: 4) good 1 3KnowP5.3-hints-polygon: 5) very good 1 3LecP5.3-hints-polygon: 1) very bad 14 3LecP5.3-hints-polygon: 2) bad 36 3LecP5.3-hints-polygon: 3) ok 15 3LecP5.3-hints-polygon: 4) good 1 3LecP5.3-hints-polygon: 5) very good 6 4Know-$sparse$: 6 4Know-$sparse$: 1) very bad 17 4Know-$sparse$: 2) bad 28 4Know-$sparse$: 3) ok 9 4Know-$sparse$: 4) good 1 4Know-$sparse$: 5) very good 1 4Lec-$sparse$: 8 4Lec-$sparse$: 0) don't remember seeing it 2 4Lec-$sparse$: 1) very bad 10 4Lec-$sparse$: 2) bad 35 4Lec-$sparse$: 3) ok 9 4Lec-$sparse$: 4) good 2 4Lec-$sparse$: 5) very good 2 6LecOverall: 1) very bad 7 6LecOverall: 2) bad 38 6LecOverall: 3) ok 19 6LecOverall: 4) good 1 6LecOverall: 5) very good 56 6LecPace: 3) ok 9 6LecPace: 4) too fast 2 6LecPace: 5) way too fast ---- q> The helpful hints for the project will hopefully come to good use in q> applying them to the project. It is very useful to go over the topics, q> as well as some of the methods for completing the projects in class. ---- q> too difficult... ---- q> I don't understand the logic behind taking two classes to explain q> how to do one part of a project. More time should have been spent on q> dealing with p5.3. My partbner and I have no idea how to approach it. q> Hopefully at office hours today and tomorrow it will be better q> explained, we'll see. ---- q> I must say, it is INCREDIBLY helpful to have the lecturer go over q> project-related material and hints in lecture as I think without q> it most of us would still be pretty lost trying to complete P5.2 q> and P5.3. Thanks! ---- q> i understand what i have to do for the project, i am just not sure q> right now how to get everything into matlab code. it seems very q> easy on paper and my understanding of what i have to do is good. q> i just don't know about my matlab skills. i thought that the hints q> and demonstrations were very helpful. i think it will be easier to q> put the stuff into code now that i know what i have to do. plus, the q> chalkboard was better for the examples than the white sheet of paper q> with the black pen. it was much easier to keep track of things when q> i didn't have to wait for you to refer back to other sheets of paper. ---- q> This project, while a good application, has taken two lectures to q> explain, and still I don't understand how it fits in to the overall q> program. I wish we would have spent more time learning 2-D arrays q> because I am very uncomfortable with them now, despite practicing with q> them on matlab. I wish there were some sort of catch up/extra lecture q> on 2-D arrays and how they apply to these problems and E11. While there q> is the review lecture, people who already understand this material will q> be there and it will be crowded/not a friendly learning environment q> like the other catch up session was. ---- q> i found this lecture to be helpful. i wrote you last time that q> you did not connect the material to actaul matlab code. this time q> i understood the concepts and also understand how they relate to q> matlab code. seemed like a well organized lecture that was given at q> a good moderate speed. ---- q> The hints were really helpful, especially for the ones on P5.2. q> Thanks! We went over the bonus material really quickly though. ---- q> decent job and pace ---- q> A good wrap up for Matlab. I was sad that we didn't get to really delve q> into cell arrays, file operations, and GUI. I read all that stuff in q> the book and I thought it was pretty neat. I guess GUI wouldn't come q> until CS 211 with Java. Oh well. Time for Java! ---- q> Glad I didn't sleep through this one ---- q> I didn't quite understand why we discussed $sparse$, some idea of an q> application would have been more helpful. ---- q> maybe we could extend the due date for p5.2??? ---- q> I was extremely lost in this lecture and I would like to meet with q> you so that you can help me understand it a little better. ---- q> I think it would have been more beneficial to go over how to draw q> the boundaries instead of reiterating how to check points, or to have q> done both. ---- q> I still do not understand how to write a program to implement q> condorcet voting. I do understand the principle of condorcet voting. ---- q> I'm sorry that the Matlab portion of the course is over because we q> haven't done 3-D plotting yet. I think this is something that will q> be particularly useful to scientists/mathematicians/engineers and q> yet it's not being taught. ---- q> The material we went over in lecture was too simplified to be helpful q> on the project. ---- q> I understand what hints you are giving us for the most part, but q> when i go to use them in trying to write the program, im not sure q> how to use them as statements. Especially with the voting problem, q> i understand the concept when you use the arrows to represent the q> candidate and the defeats, but how do you actually apply the "arrow" q> idea to Matlab. This is where i run into problems.. i understand q> the 'what' to use, but cant figure out the 'how' to apply them in q> correspondance with matlab. I think visual hints in matlab would be q> helpful especially when you introduce new functions in Matlab, then q> it helps us understand them better. ---- q> finding the explanation of p5.2 wasnt explained adequately - too much q> time was spend on finding whether point was on the right side of the q> line - which was very straight forward - this part of the project is q> proving to be more difficult ---- q> Lecture still seems disorganized. ---- q> not quite sure how to relate teh hints given to code ---- q> After you setthe boundary lines, how do you write code to scan over q> every point and make it an interior only when every condition is met?