Meeting agenda

Agenda

1. Fun stuff: come for Thanksgiving! (Around 5 PM). Durga, Anthony, Krishna, Ricky.
   
2. As decided earlier, the group will use a blog for all weekly reports. Action: all group members will start a blog and post a link to it on the Wiki. Everyone started their blog. Dr. Jones has posted a link to his blog on the Wiki. Group members will post a link to their blog on the Wiki. Ricky: enable comments. All: make comments in-line. Policy update: put updates / action items on your blog the day of the meeting.
   
3. Misc: I need a receipt from Ricky and a link to Buddy's blog.
   
4. Robotics research group: no one wants to rename; dropped.
   
5. Discuss weekly report. Group members will print a copy for each person and include their name or some distinguishing title on the hard copy.
   
6. Final report schedule:
   1. 25th – second draft.
   2. 2nd – final draft.
7. Durga: limiting case introduction
   
8. Anthony: visual servoing tutorial.
   
9. The workshop policies have been updated. Action: read the updated policy and complete the table by placing dates in cells indicating when you took the workshop.
   

Weekly meeting (20-Nov-08)

Agenda

1. Fun stuff: Friday for lunch'n'bowl? Who's coming to my house for Thanksgiving? (Around 5 PM).
   
2. As decided earlier, the group will use a blog for all weekly reports. Action: all group members will start a blog and post a link to it on the Wiki. Updates: Dr. Jones, Ricky, Durga, Anthony, Krishna have started their blog. Dr. Jones has posted a link to his blog on the Wiki. Helpful hint: by following other group member's blogs, it's easier to track these updates. You can also add a blog list to your blog with links and latest updates from everyone else's blog.
   
3. Robotics research group: a good name? A naming contest? Everyone will bring some new group name suggestions to the next meeting.
   
4. Discuss weekly report. Ricky, Buddy - will bring copies for all group members. Durga, Krishna, Anthony - will create a first-pass weekly meeting blog based on items from the previous meeting. Updates:
   
5. Final report schedule:
   1. 20th – outline to text (rough draft). Has the text been reviewed by other students?
      
   2. 25th – second draft.
   3. 2nd – final draft.
6. Anthony: visual servoing tutorial. Great info! Anthony will post / e-mail his slides for the team to look at. (Done)
   
7. Durga, Ricky will take a thesis writing course from the library. Updates: it was excellent! They're in the process of developing a good Word template for the group.
8. The workshop policies have been updated. Action: read the updated policy and complete the table by placing dates in cells indicating when you took the workshop.
   

Dr. Jones

1. Admin
   1. Provide breadboards for Durga, Krishna. Requested from Dr. Younan. Remind Dr. Jones at the end of the semester to request these again.
   2. Krishna's PC is ready and in the lab. No official desk yet. Action item: request / find a desk.
      
2. Research topics
   1. Finish review paper
   2. Finish limiting-case paper
   3. Begin work on NSF proposal
3. Students
   1. Anthony: give an intro to the Matlab bridge. Done.
   2. Durga: consider kappa = 0 case: fails for kappa < 1e-160. Durga found term causing interval analysis problem, but it's not this term.
      
   3. Krishna: need to take training on the Robotics research group/Policies#Required training page. What's completed so far? Durga, Krishna have taken the TA workshop. No one has taken the plagarism workshop. Also, there's a harassment training workshop required for all TAs that will be added to the policy. Required workshops updated.
      

Blogger and math

Putting a less-than sign in Blogger text confuses it, leading to some corruption. So, use the HTML code instead (&lt followed by a ;).

I don't see any easy way to put math into a blog, unfortunately.

Weekly meeting

Agenda

1. Idea: are weekly reports really a blog? Would that be distracting or useful? If not, is the Wiki a convenient place, or would SVN / Word be better?
   
2. Nice multi-monitor tool (and free): Winsplit revolution.
3. Weekly reports will be...weekly (every Thursday). If you'd like something placed on the agenda, either add it to the Wiki or discuss with Dr. Jones.
4. Robotics research group: a good name? A naming contest?
5. Discuss weekly reports
6. Writing: review with a group member before bringing writing to Dr. Jones.
7. Final report schedule revision:
   1. Today – complete outline (no text written) with all sections above, at least one item per paragraph.
   2. 18th – outline to text (rough draft).
   3. 25th – second draft.
   4. 2nd – final draft.
8. Anthony: visual servoing introduction

Dr. Jones

1. Admin
   1. Request Micro TA for Durga, Krishna; Robotics TA for Ricky. Done.
   2. Provide parts kits for Durga, Krishna. Delivered kits. Need to get breadboards.
   3. Help needed: a group-accessible on-line calendar. Now on Google calendar. Need group feedback: does this work?
2. Research topics
   1. Finish Micro book. Done!
   2. Finish review paper
   3. Finish limiting-case paper
   4. Begin work on NSF proposal
3. Students
   1. Anthony: given an intro to the Matlab bridge.
   2. Durga: consider kappa = 0 case: fails for kappa <>
   3. Krishna: need to take training on the Robotics research group/Policies#Required training page. What's completed so far?

Getting organized: first meeting

Getting organized: a start-up meeting for the group with items for everyone.

Theme: write, write, write!

Agenda

1. Introduce modified group meeting format
2. Weekly report and suggested format. Everyone should (if they don’t have it) create a Wiki page and link to their weekly report on the policies page.
3. Thanksgiving and PC
4. Individual schedule: 15 minute blocks, 2:15 on.
5. NSF proposal

Dr. Jones

1. Request Micro TA for Durga, Krishna; Robotics TA for Ricky
2. Provide parts kits for Durga, Krishna
3. Help needed: a group-accessible on-line calendar
4. Finish Micro book
5. Finish review paper
6. Finish limiting-case paper
7. Begin work on NSF proposal

Durga

1. Limiting-case: find a path to completion with what we have. Need interval analysis of Jacobian on original vs. stable.
2. Final report for DIS: define, illustrate, and derive the dynamic terms.
3. Review limiting-case. Write more text!

Ricky

1. Thesis, proposal, DIS report primary task. Write, write, write. Reference Krishna’s derivations. Use illustrations to show why mechanics work.
2. Tasks on weekly report should be chapters of the thesis, with tasks under that showing what needs to be done for that chapter.

Anthony

1. ViSP work. Show a working model

Krishna

1. Write up derivation. All the long derivations that will be behind Ricky’s paper.

Buddy

1. Support NSF proposal development, be a resource for others (Durga in particular)

Final report schedule / notes

1. Written in IEEE, two-column format. (Krishna can span columns for long derivations.)
2. Abstract (written last), introduction (what is the problem and why is it important), related work (what others have done, with citation. Use Endnote, expect for Krishna), body, results and conclusions.
3. Schedule:
   1. Thu – complete outline (no text written) with all sections above, at least one item per paragraph.
   2. 18th – outline to text (rough draft).
   3. 24th – second draft.
   4. 28th – final draft.