Difference between revisions of "User:Samolson"

From REU@MU
Jump to: navigation, search
(Week 1 (5/30/2017))
Line 7: Line 7:
 
*Research CS Discovery, Code.org curriculum for Circuit Playground and IDE AppLab
 
*Research CS Discovery, Code.org curriculum for Circuit Playground and IDE AppLab
 
*Help finish project overview paragraph
 
*Help finish project overview paragraph
 
 
===Week 2 (6/4)===
 
===Week 2 (6/4)===
 
*Read "MUzECS: Embedded Blocks for Exploring Computer Science"
 
*Read "MUzECS: Embedded Blocks for Exploring Computer Science"
Line 17: Line 16:
 
*Why won't the IDE work on Chromebook?
 
*Why won't the IDE work on Chromebook?
 
*Read "To Block or not to Block, That is the Question: Students' Perceptions of Blocks-based Programming"
 
*Read "To Block or not to Block, That is the Question: Students' Perceptions of Blocks-based Programming"
 
 
===Week 3 (6/11)===
 
===Week 3 (6/11)===
 
*Research other applications built with Blockly
 
*Research other applications built with Blockly
Line 52: Line 50:
 
===Week 7 (7/9)===
 
===Week 7 (7/9)===
 
*Continue reading "Design of a blocks-based environment for introductory programming in Python"
 
*Continue reading "Design of a blocks-based environment for introductory programming in Python"
 +
*Explore Microsoft MakeCode (note to never be lazy with names)
 +
*Attend working lunch
 +
*Explore process for creation of new blocks in MUzECS IDE
 +
===Week 8 (7/16)===
 +
*Start research paper for submission to Blocks and Beyond Workshop, 2017
 +
*Create poster design
 +
*Complete abstract for research paper, and submit to Blocks and Beyond
 +
*Attend working lunch
 +
*Read "Controversy on how to teach CS1"
 +
*Read "Initialization in Scratch"
 +
===Week 9 (7/23)===
 +
*Continue reading "Initialization in Scratch"
 +
*Create two diagrams comparing procedural programming with event-driven programming styles
 +
*Write "Block Design" section for research paper
 +
*Work on poster
 +
*Finish poster
 +
*Stay up till 6AM completing paper for submission
 +
*Attend working lunch
 +
===Week 10 (7/30)===
 +
*Rehearse short spiel/hook and longer description for poster session
 +
*Draft outline for formal talk
 +
*Finish slideshow and notecards
 +
*Give 15 minute presentation on project
 +
*Submit post-REU survey

Revision as of 22:51, 10 August 2017

Week 1 (5/30/2017)

  • Init new wiki page for Sam Olson
  • Set up Arduino hardware and software, and familiarize with interface
  • Set up Adafruit Circuit Playground hardware and software, and familiarize with interface
  • Continue to work with Arduino and MUzECS shield
  • Read "A Browser-based IDE for the MUzECS Platform"
  • Research CS Discovery, Code.org curriculum for Circuit Playground and IDE AppLab
  • Help finish project overview paragraph

Week 2 (6/4)

  • Read "MUzECS: Embedded Blocks for Exploring Computer Science"
  • Brainstorm methods to survey local schools utilizing the MUzECS platform
  • Responsible Conduct of Research training
  • Develop research question first draft
  • Attend working lunch
  • Investigate MUzECS IDE platform version 3, get working on Linux, Windows, and MacOS
  • Why won't the IDE work on Chromebook?
  • Read "To Block or not to Block, That is the Question: Students' Perceptions of Blocks-based Programming"

Week 3 (6/11)

  • Research other applications built with Blockly
  • Continue reading "To Block or not to Block, That is the Question: Students' Perceptions of Blocks-based Programming"
  • Complete CITI RCR Session 1
  • Attend working lunch
  • Why can't MUzECS board be detected by MUzECS IDE or Codebender or AppLab on Chromebook?
  • Not enough data for current research question -- rethink research question

Week 4 (6/18)

  • Try programming Circuit Playground with MUzECS IDE
  • Research parameters to support Circuit Playground on avrgirl
  • Research Circuit Playground-specific code blocks from AppLab
  • Attend working lunch
  • Scan code.org for Johnny-Five usage
  • Investigate error with installing Firmata on Circuit Playground via MUzECS: "could not reconnect after resetting board."
  • Setup Bash on Ubuntu on Windows
  • Attempt building MUzECS IDE
  • Research Circuit Playground Express
  • Create rough outline for presentation

Week 5 (6/25)

  • Attend talk on research presentations
  • Finish building MUzECS IDE
  • Work on presentation outline
  • Prepare slideshow presentation
  • Give 8 minute presentation on research so far

Week 6 (7/2)

  • Build MUzECS IDE on desktop (without David)
  • Set milestones for now until due dates
  • Explore johnny-five API for Circuit Playground
  • Order Circuit Playground Express
  • Attend working lunch
  • Explore site and submissions for Blocks and Beyond Workshop, 2015 IEEE
  • Read "Design of a blocks-based environment for introductory programming in Python"

Week 7 (7/9)

  • Continue reading "Design of a blocks-based environment for introductory programming in Python"
  • Explore Microsoft MakeCode (note to never be lazy with names)
  • Attend working lunch
  • Explore process for creation of new blocks in MUzECS IDE

Week 8 (7/16)

  • Start research paper for submission to Blocks and Beyond Workshop, 2017
  • Create poster design
  • Complete abstract for research paper, and submit to Blocks and Beyond
  • Attend working lunch
  • Read "Controversy on how to teach CS1"
  • Read "Initialization in Scratch"

Week 9 (7/23)

  • Continue reading "Initialization in Scratch"
  • Create two diagrams comparing procedural programming with event-driven programming styles
  • Write "Block Design" section for research paper
  • Work on poster
  • Finish poster
  • Stay up till 6AM completing paper for submission
  • Attend working lunch

Week 10 (7/30)

  • Rehearse short spiel/hook and longer description for poster session
  • Draft outline for formal talk
  • Finish slideshow and notecards
  • Give 15 minute presentation on project
  • Submit post-REU survey