This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
haas:fall2015:data:projects [2015/10/11 20:51] – [Break Week] wedge | haas:fall2015:data:projects [2015/12/05 11:06] (current) – [Projects] wedge | ||
---|---|---|---|
Line 14: | Line 14: | ||
* [[/ | * [[/ | ||
* [[/ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
======Class Stats====== | ======Class Stats====== | ||
- | ^ DATA ^ dsi0 ^ sln0 ^ sln1 ^ sll0 ^ sll1 ^ project | + | * [[/ |
- | ^ lowscore:| | + | |
- | ^ avgscore:| 75 | 91 | 71 | 72 | 70 | 27 | 24 | 31 | 82 | | + | ======Project FAQs====== |
- | ^ hiscore:| 100 | 100 | 100 | 100 | 100 | 37 | 28 | 36 | 101 | | + | |
- | ^ median:| 79 | 100 | 81 | 96 | 84 | | + | |
- | ^ mode:| 100 | 100 | 97 | 97 | 100 | | + | ======Week 13====== |
- | ^ range:| 100 | 100 | 100 | 100 | 100 | | + | * End of Course Experience released! Check the bottom of your Opus. |
- | ^ passed:| 75% | 90% | 80% | 80% | 75% | | + | * Note that you must be signed in to view/edit it. |
- | ^ As:| 40% | 85% | 25% | 60% | 45% | | + | * **eoce0** project, after 2 released updates, now starts to compile and operate as expected. Still likely a few more updates upcoming, but we may be at a point where you can commence implementation. |
- | ^ Bs:| | + | * mktree() functionality now provided (should be all you need to commence work on addnode() and traverse_s()). |
- | ^ Cs:| 25% | 0% | 25% | 10% | 15% | | + | * Project pages for the tree part of **eoce0** and the entirety of **eoce1** are now available. |
- | ^ Ds:| 0% | 0% | 0% | 10% | 5% | | + | * The **eoce1** project is now available. |
- | ^ Fs:| 25% | 10% | 20% | 20% | 25% | | + | * Starting next week, the IPKA (In-Person Knowledge Assessment) will be available. |
- | ^ submit: | + | |
+ | ======Week 12====== | ||
+ | * **dll1** results are in- surprisingly, | ||
+ | * work on the stack project is underway, I've had some good questions already. Please, keep them coming. | ||
+ | * queues (**dlq0**) will be the new project for the week... and will be very similar to stacks. | ||
+ | * **dlq0** may be the last weekly project before the EoCE. | ||
+ | | ||
+ | | ||
+ | ======Week 11====== | ||
+ | * We're nearing the end of our active list explorations. It has been a long journey, fraught with frustrating logic errors, lots of debugging experience, and a whole lot of time. I have been very pleased with the progress I see from so many.. don't just look at things at the moment, look at how far you've come. There have been some truly amazing improvements. | ||
+ | | ||
+ | * **dll2**: adding **qty** to your list implementation, | ||
+ | * **dls0**: stack implementation (on top of list) | ||
+ | | ||
+ | * more than a few of you seemingly forgot to submit **dln0**. You had fully working projects, but just didn't officially submit it. I manually handled it. This time. | ||
+ | * **dll0** was simultaneously more difficult for some, yet easier for others. Those who have been doing well seemed to get hit, whereas those who have been catching up had some real breakthroughs. | ||
+ | * Some **dll1** observations: | ||
+ | * be mindful of the second (prior) pointer. Just because you've done something before in singly doesn' | ||
+ | * all sorting does **not** require swapping. Only some sorts use swaps. For those having trouble getting swap to cooperate with your sort attempts, you can either fix swap (a worthy pursuit, if not rushed), or go about sorting in a different way. | ||
+ | * don't go and look up existing sort algorithms, that's probably how you got to this issue in the first place. Plot out how you would accomplish a sort... work through the logic. Following the algorithm someone else made vs. figuring out one on your own? The latter will produce understanding at a much higher rate. | ||
+ | ======Week | ||
+ | * Can you believe it-- week #10! | ||
+ | * We continue our linked list reimplementation, | ||
+ | * with doubly linked nodes, your implementations should be simultaneously simpler and more complex (simpler because you don't need as many extra steps to set things up, more complex because there are twice as many pointers to connect!) | ||
+ | * remember: draw pictures, work logic out on paper, get plenty of sleep, and use the debugger! | ||
+ | * I mean it: don't pull last-minute all-nighters with this stuff- the more tired you are, the less sense things will make. Brute forcing it will not help. | ||
+ | * you are quite capable in accomplishing all that is at play, and to grow considerably as a developer (and isn't that the overall point)? | ||
+ | * sll3 and sll4 have been evaluated | ||
+ | * some seemed to have a late start on sll3, not understanding its basic premise | ||
+ | * sll4 saw some interesting trends: | ||
+ | * appeared more difficult for some (maybe they got too used to nodes as a tool and not as a concept?) | ||
+ | * for those who saw the commonality, | ||
+ | * while sll4 was a more involved project than sll3, many did better on sll4 than they did on sll2 (the next most involved project) | ||
+ | ======Week 9====== | ||
+ | * Doubly-linked stuff is unveiled this week, and it kicks off our first rebuild (second implementation of code). | ||
+ | * Please strive to do a fresh implementation, | ||
+ | * Course status has been moved into its own status page, and updated. Check it out for some interesting hints at trends. | ||
+ | * As past trends seem to indicated, sll2 was a more challenging project than some previous. | ||
+ | * At the same time, we seemed to fare much better than prior semesters, and many problems were actually expected as part of the learning process (sll2 relies on past code more than previous projects, so it routed out more bugs that were previously uncaught). | ||
+ | * Conversely, this project was the watershed moment for a few people who achieved their enlightenment. Quite interesting results all around. | ||
+ | * So don't despair! Many who had trouble were doing some amazing things-- improving debugging skills, fixing sloppy code... those things only serve to improve your skills. | ||
+ | ======Week 8====== | ||
+ | * A few people took advantage of the break and got an early start on things. I thank you for that. | ||
+ | * Graphs are still graphing, so be sure to check out the metrics page for **sll2** (and then **sll3**/ | ||
+ | * People are still reinventing the wheel unnecessarily. Please remember, you wrote other functions for a reason. | ||
+ | * People are still not drawing pictures. You NEED to draw this out... that blank uncertainty when you're not sure how to proceed? Pictures will help. So will the debugger when you've got code (but pictures should be utilized throughout). | ||
+ | * Rigging up solutions based on counting will naturally make the code more complex. It is familiar and comfortable, | ||
======Break Week====== | ======Break Week====== | ||
* I have evaluated sll1! No real surprises, and I think everyone actively working on the projects are starting to get a feel for what is going on. | * I have evaluated sll1! No real surprises, and I think everyone actively working on the projects are starting to get a feel for what is going on. |