Image courtesy Bernard Oh @ Flickr

You’re almost there!  Congrats on making it all the way here.  Yes, we know you still have so many features and refinements to do (and we hope you will do them), but it’s now time to set things aside and make sure you have all of your current work documented for your peers to review this coming week.  Yes, we also know you are doing so many other projects as the summer is coming to an end now.

In the week ahead, you will be judging the final outcome of your peers’ projects too.  Importantly, we need you to turn in your peer evaluations on time.  We need these evaluations on time, as we need to wrap up the Orbital grading, so as to meet the deadlines for assigning the 4 S/U credits for the course (CP3108B).

Look to the recent post by Prof. Lee for the Evaluation 3 milestone criteria for which your project will be graded by.  In the week following your peer review, do keep in mind you will have to do one final evaluation of your peers’ reviews on your project, so that you can give credit and thanks to all of those reviews that were helpful (including your own advisors and mentors).

Good luck!  Stay strong — you’ve come all this way.  Give each other encouragement to stay the course!  There’s only the ultra-fun Splashdown to go!

Photo Credits: Philipp Pohle @ Flickr
Photo Credits: Philipp Pohle @ Flickr

Dear all:

Your second Orbital hurdle is here!  Please make sure to put up your project’ revised README and log into Skylab (see Slack later for details on what to put, no later than 29 Jun 11:59pm SGT, but preferably as soon as possible).

Thanks to the groups who have at least put in a preliminary or final project README and log into their EG group.  Note that you need to inform your EG adviser in advance of the deadline if for some reason you cannot make the deadline.  You must inform your advisers in advance, or lateness may count against your eligibility for getting credit for Orbital.

In the following week, you’ll also need to do the peer evaluations of your three peer teams in your evaluation group. These evaluations are due in Skylab no later than 6 Jul 11:59pm (exactly 1 week later).

Dear students:

We’re almost at the end of Orbital!  We hope your summer self-study journey has been productive and that you have learned and broadened your horizons significantly on the topic of your choice.  Now that you’ve finished the final official Project README, video and log, it’s time to wrap up by evaluating your peers, and preparing for Splashdown on 22 Aug (Friday).

We’ll be posting a separate announcement about Splashdown later next week but for now, let’s concentrate on the evaluation of peer feedback.  This is the (very quick 1 question) evaluation that you do to assess how useful your peers have been in their feedback and critique of your project.  You’ll need to evaluate your peers as well as your adviser on this.  Details about this process are available on Post @1273 in Piazza and also as an 11-minute video recording on YouTube.

A quick note:  Those of you trying for higher levels of achievement may plan to get a lot more done on your project between now and Splashdown to meet that level of achievements’ criteria.  That’s fine — your peers will evaluate you on what you’ve done up to Evaluation 3, but you can petition (by writing to your adviser or to us (Min and Wee Sun) directly) to have your project re-reviewed for the higher level of achievement.  Make sure to do this by Splashdown (22 Aug) as that is the hard deadline for determining level of achievements, and we are likely to need to see your project’s outcome during the showcase to assess your final achievement level.

 

Photo Credits: Philipp Pohle @ Flickr
Photo Credits: Philipp Pohle @ Flickr

Dear all:

Your second Orbital hurdle is here!  Please make sure to put up your project’ revised README and log into Piazza (see pinned posts @793 and the updated @235) no later than 30 Jun 11:59pm SGT, but preferably as soon as possible).  Make these posts visible to all in your EG.

Thanks to the groups who have at least put in a preliminary or final project README and log into their EG group.  Note that you need to inform your EG adviser in advance of the deadline if for some reason you cannot make the deadline.  You must inform your advisers in advance, or lateness may count against your eligibility for getting credit for Orbital.

In the next week, you’ll also need to do the peer evaluations of your three peer teams in your evaluation group listed in Post @235. These evaluations are due as private posts addressed only to your adviser no later than 7 Jul 11:59pm (exactly 1 week later).

Screen Shot 2014-06-01 at 7.48.56 am
Photo Credits: James M @ Flickr

Dear all:

Your first Orbital hurdle is here!  Please make sure to put up your project’s README and log into Piazza (see pinned posts @233, @224) no later than 2 Jun 11:59pm SGT, but preferably as soon as possible).

Thanks to the 13 or so groups who have at least put in a preliminary or final project README and log into their EG group.

In the next week, you’ll also need to do the peer evaluations of your three peer teams in your evaluation group listed in Post @235. These evaluations are due as private posts addressed only to your advisor no later than 9 Jun 11:59pm (exactly 1 week later).

 

 

Courtesy: billsoPHOTO @ Flickr

To help you with what is expected for the first peer evaluation, we have done a sample project report, evaluation and response for the example Giftbook project. To see it:

  • On IVLE, under CS3108B_Orbital, go to Project -> **MISSION CONTROL** (Orbital Instructing Staff) -> Project Wiki to find the project report
  • You can find a sample evaluation of the project in the Folders.
  • The project report also contains a response to the peer review — after peer evaluation is completed on Monday 2 June, we will send you a copy of the feedback provided by your peers, and you are supposed to respond in your report by Wed 5 June.

A critical component of this programme that we take from other massive open online courses, is that the student cohort helps themselves through the problem.  One student’s problem may have been faced by many, and a good vehicle that helps to record questions and answer them is an important component in helping students find answers.

To address this, we are going to use askbot, an open source Django project that builds a forum similar to IVLE but with voting mechanisms and easy authentication via OpenID (e.g., Google account, FaceBook account).

We hope that all students will participate and help on the askbot forum.  Student’s participation will be a factor in the S/U grading of the student projects.

Jump to the Orbital Askbot forum here.