Mimir:Spring 2017 Steve Saunders Log

From Openitware
Jump to: navigation, search


Week Ending February 20, 2017

Task
  • Review of chapter 3 which is the teams choice of focus
  • Add in Perl section from previous draft unless entire chapter copied by team
  • Split Perl section into 2 sections
    • One section for to focus on the imperative nature of the language
    • One section for the programming tutorial (tie to questions or homework
Results
  • Tasks entered Saturday AM
  • Chapter 3 already copied in before review
  • Request clarification on meeting notes for task for Gayathri and myself
  • Lecture assignment setup for reuse in chapter 3
  • Lecture assignment was beneficial practice for Wiki editing
  • Chapter 3 review observations:
    • Majority of chapter is on programming and not imperative languages
    • Perl section quite complete, team may need to reassign members to Python
  • Will suggest the following based on review notes above:
    • Increase the content for main topic of imperative programming
    • Consider if programming sections should move to an appendix
      • Python is early in syllabus but may not belong in chapter
      • Python should be considered OOP which can be considered imperative extension
Plan
  • Use this weeks lecture assignment to create usable section for chapter
  • Keep a backup of section under edit for easy replacement
  • Import section in to begin edit in Wiki
  • Review content to determine if any references needed or re-write
Concerns
  • Chapter subject is Imperative programming and a lot of focus is on specific language programming technique

Week Ending February 27, 2017

Task
  • Add sections to chapter 4 for content before LISP section
  • Review 1st four sections of Perl section in chapter 3 (lower priority)
    • Correct any errors found
Results
  • Defined several sections above programming section
  • Add higher level divider for programming section
  • Move content to appropriate section
  • Add minor comments for update next session
  • Chapter 3 Perl section not reviewed
Plan
  • Change focus to chapter 4. This is so team can split into smaller groups that will work on either chapter 3 or chapter 4.
  • Develop the pre-LISP section of chapter 4
    • Determine is intro section still needed if expanded upon
    • Add more setions, some possibilties are:
      • Difference to imperative programming
      • Side effects
      • Examples for all
  • Previous plan of first four Perl highlights in Perl of chapter 3 per clarification with the team previous week, this will be a lower priority
Concerns
  • Format may need adjustments
  • There is content and image in introduction that may need to move to LISP section
  • Most of chapter 4 is on LISP programming and not functional programming

Week Ending March 6, 2017

Task
  • Add outline into sub-sections of Chapter 4 sections 1.1 and 1.2 (Intro and descriptions of what is functional programming)
Results
  • Download several papers for review of functional program content found during some LISP research for HW2
  • Work on additional sub-sections to add to page
Plan
  • Add bullets to use as guides to adding content for description of functional programming
Concerns
  • Overall chapter does not have enough content
  • From last week: Most of chapter 4 is on LISP programming and not functional programming
  • Team already considering chapter 5 updates

Week Ending March 20, 2017

Task
  • Spring break week, minor edits
Results
  • Create new section with previous introduction
  • Add content and examples into math section
Plan
  • Continue edit the main introduction
  • Separate out old material
  • Start the math related section
Concerns
  • Formatting math symbols (leave out initially)
  • Check that math formulas and content is correct

Week Ending March 27, 2017

Task
  • Complete the general concept part of the match section
  • Add lambda calculus information
  • Start new section, either compare to imperative or description
Results
  • Added sentences with mention of lambda calculus (ref needed to Yale paper)
  • Added section / paragraph with differences compared to imperative
  • Symbol notation not used, put plain function text in "code" style blocks.
Plan
  • Continue math section development with simple demonstration of concepts
  • Look up math symbol notation and update formulas if applicable
  • Find content related to Lambda Calculus
Concerns
  • Adding references when needed.

Week Ending April 3, 2017

Task
  • This week is dedicated to GRC poster development
Results
  • Upload example poster to team shared google drive
  • Modify abstract for header
  • Create bullets in text file for team to review
Plan
  • Work on poster content
  • Work on implementing content into poster
  • Load example to google drive for team to review
Concerns
  • Empty poster draft not in 48x36 format

Week Ending April 10, 2017

Task
  • Review GRC poster proposals
  • Add content to mathematical program section
  • Add recursion section
  • Add first class function section
  • Remove "bullet" style notes from content
Results
  • Re-format preferred GRC poster to 48x36 size
  • Adjust GRC poster content, colors and arrangement to proposed final draft
  • Added recusion section 4.3.4
  • Added first class function section 3.3.3
  • Complete edits on mathematical programming section
  • Remove temporary notes
  • In functional languages list add R and add or modify descriptions
  • Only started chapter 3 audit April 10th
  • Minor cleanup of this log
Plan
  • Complete GRC poster
  • Complete section 4.2, 4.3.1-5
  • Start audit of chapter 3 content
Concerns
  • GRC poster table of contents snap shot may not be clear
  • Need to properly reference sentence on lambda calculus

Week Ending April 17, 2017

Task
  • Complete GRC poster with team
  • Complete section 4.2, 4.3.1-5
  • Continue review of chapter 3 content for references
Results
  • Team has completed and submitted poster
  • Completed final proposed content for sections 4.2, 4.3
  • Review of chapter 3 content for references not completed
Plan
  • Complete section 4.2, 4.3.1-5
  • Continue audit of chapter 3 content
Concerns
  • GRC poster printed in time

Week Ending April 24, 2017

Task
  • Continue review of chapter 3 content for references
Results
  • GRC poster done
  • All of weeks time spent continuing debug of HW4, submitted without completion per assignment
Plan
  • Complete audit of chapter 3 content
Concerns
  • HW4 preventing dedicating any other time for Mimir work

Week Ending May 1, 2017

Task
  • Continue review of chapter 3 content for references
  • Add reference section
  • Add numbered reference in content
  • Add reference to papers, authors and websites at bottom of page
Results
  • Added reference section
  • Scan content for sources
  • Add reference number inside content in [] brackets
  • Add references in reference section at end of chapter
  • Chapter 3 complete
Plan
  • Complete audit of chapter 3 content
Concerns
  • Completing lecture notes this week for both weeks

Week Ending May 8, 2017

Task
  • Review of chapter 4 content for sources (one already noted)
  • Add reference section to chapter 4
  • Add reference numbers in content
  • Add details of source at bottom of chapter
Results
  • Create chapter 4 reference section.
  • Add reference to paper used for ideas in introduction (Hudak)
  • Scan LISP history, add single reference to historical sentence
Plan
  • Create chapter 4 reference section in format of chapter 3
  • Scan content to determine references
  • Add already marked reference from intro section
Concerns
  • Completing week 12 lecture notes
  • Study for test
  • Submitting project design