Closed jvillemare closed 6 years ago
I created the branch https://github.com/FlintHill/SUAS-Competition/tree/gcs-webui-emergent-target-addition to commit my changes.
One additional note: The description will be a max of 1000 characters. @DarkmatterVale could implement a server-side check, but it's not strictly necessary since we'll be on a closed network.
Here's what the new specification's pane looks like, now:
Edit: The image on the far-right is with the mouse hovering over the STANDARD | EMERGENT
tab selector.
Looks good. Do I need to code in the server-side submission now?
@DarkmatterVale yes. In my commit, https://github.com/FlintHill/SUAS-Competition/commit/2c346037512aa9ce56afe210fb56bf08577ea4e7 , I now send the submit the data for standard
and emergent
targets:
Standard Target:
Emergent Target:
I talked with @DarkmatterVale : Waiting on opportunity to do full test with Interop. server and all GCS.
@DarkmatterVale : Successfully tested the flask_gcs.py
script with you, connected to Interop, and the target was successfully received by the server. Here are the results of the submission from the client-end:
Both target submissions had the same result:
Completed in #114
Summary
Add a new tab on the specifications pill of GCS:WebUI to submit emergent targets.
Purpose
Emergent targets are dummies, typically dressed in firefighter gear, located in some vague, but specified area. They only require a few details to be submitted: the geolocation and location description of emergent. They do not require shape, color, orientation, etc.
Since emergent targets, and other targets are differentiated, we need two tabs in the Specifications Pane to support sending two different type of targets.
Off-axis target will not be included because it will not be attempted.
Specifics
The same
/post/target
endpoint should be expanded to support the submission of the current standard targets and new emergent targets.Standard Target
Emergent Target
Delegation
I will add in the tabs and other code into the GCS:WebUI, @DarkmatterVale will work on writing in
flask_gcs.py.