API review

Proposer: Alex Sorokin

Present at review:

• Alex Sorokin
• Caroline Pantofaru
• Eric Berger

Question / concerns / comments

Enter your thoughts on the API and any questions / concerns you have here. Please sign your name. Anything you want to address in the API review should be marked down here before the start of the meeting.

• wiki should be on the server

• separate HIT groups by session -> add flag in the session.

• no dollar max for the session?
  • Special permission to give bonus
  • Dollar max per session
  • Dollar max per user
• Dump a yaml file with a task definitions.
• Storing/creating everything from code.
• version control, backups

• Discuss ImageRefernce

• Annotate bag file

• Name/Scope of ExternalAnnotation:

  • ExternalAnnotationOutline/ ExternalAnnotationBox ??

• Server reference to ExternalAnnotation

• BoundingBox v.s. ImageGeometry region of interest

  • Alex: sensor_msgs/RegionOfInterest uses uint32 for box size. We use floating point numbers and because of different image sizes, I am reluctant to introduce arbitrary rounding of the annotations to get into uint32.

cv_mech_turk2:

• submit_image. tar file

• what happens when this is streamed as ExternalAnnotation

• unsupported elements?

mech_turk_ros:

• snapper? ImageSnapper:

  • remove frame_id
  • sub: image (sensor_msgs/Image)

  • param: server, session, submission_mode ->submit_enabled:true/*false*, img_dir -> jpeg_output_dir

  • Snapper image naming:
    • uid = run_id.topic.timestamp
    • image= uid.jpg
• link_topic - server passthrough
  • "publishes": /annotations (mech_turk_ros_msgs/ExternalAnnotation)
  • all

• ExternalAnnotation -> ExternalImageAnnotation

  • Reference to the server?
  • uid

• ImageReference -> just uid

• Is link_topic ok? Are there better alternatives? Will the problems go away soon with more ROS tools?
  • Link topic is internal to the mech_turk_ros. Once configured, it provides /annotation topic which publishes annotations received from the server.
  • In the future (a) it is ROS-level feature or (b) it can be implemented over non-ROS API.
  • link_topic needs to be renamed. ? connect_external_annotator
• Getting image and image information by the UID
  • Internal for now.
  • future: add API to retrieve the data per image

Meeting agenda

To be filled out by proposer based on comments gathered during API review period

Conclusion

Package status change mark change manifest)

• Review session_2_messages

• Review annotate_image_action

• Install wiki on vm7: what kind of wiki? Add wiki in the recommended server config.

• Come up with task versioning/download procedure. (write up the procedure for assigning/releasing task definition)

• Require permission to assign grades

• Define image UID (write up on the wiki)

• Formal naming for generalization of the 3 main components: Task, Image, Annotation. Current: Task, HIT or WorkUnit, Submission or WorkProduct.

• BoundingBox v.s. sensor_msgs/RegionOfInterest

• How to get run_id? rospy.get_param("/run_id") ?

---