search

naiad-auv / naiad-auv-report

1 stars 2 forks source link

To Do #3

Open debajyoti7 opened 10 years ago

debajyoti7 commented 10 years ago
  1. Structure for technical reports Structure the different technical reports based on subsystems rather than hardware/software.
  2. Directory for unfinished code Trials, failed demos, Matlab tests etc
  3. Responsible persons for subsystems: Assign, make list on gogle doc and share
  4. Divide work for proofreading
christofferholmstedt commented 10 years ago

Structure for technical reports: DONE Responsibility for each report: DONE Proofreading is done with the "free-for-all" method: DONE

Not sure about (2), what did we say about that one?

debajyoti7 commented 10 years ago

for 2, we decided to have a separate place for Demo/tutorials showing the functionalities of the developed code, if and where needed. If I remember, Daniel and Aseem had some stuff to put up.

christofferholmstedt commented 10 years ago

As in the "example" directory or another demo directory?

debajyoti7 commented 10 years ago

Same.

/debajyoti On 15 Jan 2014 07:30, "Christoffer Holmstedt" notifications@github.com wrote:

As in the "example" directory or another demo directory?

— Reply to this email directly or view it on GitHubhttps://github.com/naiad-auv/naiad-auv-report/issues/3#issuecomment-32337997 .