Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial Server Setup #9

Open
25 of 27 tasks
len0rd opened this issue Nov 27, 2018 · 2 comments
Open
25 of 27 tasks

Initial Server Setup #9

len0rd opened this issue Nov 27, 2018 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@len0rd
Copy link
Member

len0rd commented Nov 27, 2018

Here's what's left todo for the server to be ready for basic client interaction:

  • Outgoing autonomous Dao wrapper
  • Classification handler
  • Brandon response chopping off key names (something with python 2 vs 3 and how they represent attr?) -> it was because it was on python2
  • Handle updating or inserting with POST/PUT if a row with an image_id already exists(upsert)
  • Upsert for image/crop POST
  • dockerize - easy connecting to external ROS_MASTER
  • CI tests for all server api functionality
  • EASY demo. That'll launch the docker image and dump a rosbag into the database for fast testing
  • All the interop submission stuff
  • Target binning on each classification PUT and POST
  • Set all images tied to a target as sent when one is sent?
  • Need a place to store the path for a cropped autonomous image facepalm
  • Attribute averaging pre submission (majority rules on classifiers and avg lat long)
  • Save submitted targets in auvsi's 'Object File Format' in the event of submission failure
  • Support multiple crops from single raw image
  • Client-side image classification code
  • investigate need to add focal length info to table. Is it stored in the jpg file by default? ... -> it's not :''(
  • get/publish focal length info and store in database
  • Change inherited_submission status to mean a new classification has inherited submission if its target has already been submitted (ie: all classifications at time of submission receive submitted status)
  • change the manual_cropped timestamp to be a straight copy of its corresponding raw image
  • interop submission as a ros service instead of pub/sub?
  • Top-level dev setup script
  • easy server-side way to reset ALL tables

interop submission stuff

  • modify interop_pkg to stop doing a bunch of extra unnecessary processing
  • submitted_target table for all autonomous and manual targets queued for submission
  • ^^ getSubmitted handler polls from this
  • ROS Handler work with this table and publish when there are subscribers
@len0rd len0rd added the enhancement New feature or request label Nov 27, 2018
@len0rd len0rd self-assigned this Nov 27, 2018
@len0rd len0rd mentioned this issue Nov 27, 2018
len0rd added a commit that referenced this issue Nov 27, 2018
@len0rd
Copy link
Member Author

len0rd commented Nov 27, 2018

currently just classification POST does an upsert. think it makes sense in a post, but prolly not a put

This was referenced Nov 29, 2018
@len0rd
Copy link
Member Author

len0rd commented Dec 4, 2018

  • Fix conda GUI setup to include pip ttkthemes

len0rd added a commit that referenced this issue Jan 8, 2019
…n stuff. only major piece left is interop submission
@len0rd len0rd mentioned this issue Jan 14, 2019
len0rd added a commit that referenced this issue Jan 15, 2019
len0rd added a commit that referenced this issue Jan 15, 2019
@len0rd len0rd mentioned this issue Jan 16, 2019
len0rd added a commit that referenced this issue Jan 16, 2019
@len0rd len0rd mentioned this issue Jan 22, 2019
len0rd added a commit that referenced this issue Jan 24, 2019
…ith a target ('submitted'), or if it was attached to a target after the fact and not submitted to the judge server ('inherited_submission')
len0rd added a commit that referenced this issue Jan 24, 2019
…ated image-id. if the image_id is bogus, then it just does the current ts
This was referenced Jan 31, 2019
@len0rd len0rd mentioned this issue Feb 4, 2019
@len0rd len0rd mentioned this issue Feb 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant