start-jsk / 2015-semi Goto Github PK

baxter_vision_exampleとnao_practiceは他に必要なpackageがあるので、各自branchを切ってそのbranch上で削除してしまっても構いません。
master branchはすべて残してあります。

https://m.youtube.com/watch?v=Fmpvt-Q-EvI

酒の肴にどうぞ
@furushchev

@k-okada 先生
今週、空いているお時間はありますでしょうか。
もう2台PCをお借りしたいのと、OSの新規インストールが必要か必要じゃないかなどについて落ち着いて話したいです。

issueを３個ぐらい書いて下さい．できれば，このリポジトリ以外のところで．書いたら，ここに報告しておいて下さい．

実機の使い方のドキュメントは @snozawa さんから送ってくれる
ソースは https://github.com/jsk-enshu/robot-programming

右腕をうごかすときはinverse-kinematicsの引数に:rarm、左腕は:larmを明示しなければエラーが出る。

(setq c1 (instance cascaded-coords :init))
(send c1 :locate #f(1200 0 1000))
(send *baxter* :rarm :inverse-kinematics c1 :rotation-axis nil :debug t)

どうすればいいですか？

締切り 10/28 まで

kinectから画素ごとのdepth情報を直接いじって画像処理してみたいです。
jsk_recognitionのどれかdepth情報を使っているプログラムを探して参照にしようと思っています。

Gazebo + Nao : https://github.com/ros-naoqi/nao_virtual

@knorth55
maybe you want to do this...
Anyone else to participate?
https://www.youtube.com/watch?v=Q4bMcUk6pcw

fetch simulation http://docs.fetchrobotics.com/gazebo.html
http://ros-logger.blogspot.jp/2015/07/playing-with-fetch-and-freight-robots.html

http://wiki.ros.org/rtmros_nextage/Tutorials
これ見て一通りやってみる。hydroはindigoに読み替える。

ルールはこちら
http://archives.simplelists.com/pickingchallenge2016/cache/3300513/2.pdf

• PHASE 1 “Robot Proposal Entry Period”: Entrant or Entrant Teams who wish to enter the Challenge
  may visit http://amazonpickingchallenge.org/ (“Challenge Site”) and submit the entry information
  required including, but not limited to: Entrant name, email address, team size, mailing address, daytime
  phone number, confirmation of age, and include an overview of their Robot in the form provided
  (collectively, a “Proposal Entry”).
• PHASE 2 “Robot Proposal Review Period”: All eligible Proposal Entries will be judged and scored by
  a review panel chosen by the Sponsor (“Review Panel”). The Review Panel will rank Proposal Entries
  based on the maturity and flexibility of the proposed design and the likelihood the design will result in
  successful performance in the Finalist Event (the “Review Criteria”). The Sponsor reserves the right to
  assess Proposal Entries in the manner determined by the Sponsor, which may include interviews or
  discussions with certain Entrants/Entrant Teams.
  The sixteen (16) Proposal Entries ranked highest by the Review Panel will be deemed potential inalists
  (subject to verification and compliance with these Official Rules) and will be invited to attend RoboCup
  2016 scheduled to take place in Leipzig, Germany from June 30 to July 4, 2016 where they will have the opportunity to have their Robot compete against other finalist Robots (the “Finalist Event”). In the event of a tie, all tied Proposal Entries will be re-reviewed by an additional “tie-breaking” panel member selected by Sponsor who will use the Review Criteria above to break the tie. Sponsor’s decisions are final and binding in all matters relating to this Challenge.
• PHASE 3 “Finalist Notification Period”: Potential finalists are subject to verification by the Challenge
  Entities. Potential finalists will be notified by email at the email address provided at time of Proposal
  Entry. Potential finalists (and if an Entrant Team, all members of such team) will be required to complete and return a Participation Agreement, within the timeframe stated on the notification. If any email notification is returned as undeliverable, if a potential finalist does not respond within the required number of days specified by Sponsor, or if information collected within the clearance documentation, entry, or background check is found in non-compliance with these Official Rules, raises other issues of significant concern to Sponsor or a potential winner decides to decline the prize for any reason whatsoever, Sponsor shall have no further obligation to such potential finalist and the applicable prize will be forfeited and may be awarded to a runner-up potential finalist time-permitting and at the Sponsor’s sole discretion.
• PHASE 4 “Finalist Event”:
  Overview
  The Finalist Event will consist of two tasks:
  • A pick task to remove target items from a shelf and place them in a tote, and
  • A stow task to take target items from a tote and place them into the shelf.