generated from rh-robotics/Basecode
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d096bd3
commit 83e108b
Showing
3 changed files
with
311 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
name: Deploy Javadocs to GitHub Pages | ||
|
||
# Keep up to date with master, not a branch. | ||
on: | ||
push: | ||
branches: [master] | ||
workflow_dispatch: | ||
|
||
# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages | ||
permissions: | ||
contents: read | ||
pages: write | ||
id-token: write | ||
|
||
# Allow one concurrent deployment | ||
concurrency: | ||
group: "pages" | ||
cancel-in-progress: true | ||
|
||
# Jobs | ||
jobs: | ||
# Generate the docs. | ||
deploy: | ||
environment: | ||
name: github-pages | ||
url: ${{ steps.deployment.outputs.page_url }} | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: Checkout repository | ||
uses: actions/checkout@v2 | ||
|
||
- name: Set up JDK 17 | ||
uses: actions/setup-java@v2 | ||
with: | ||
distribution: 'zulu' | ||
java-version: 17 | ||
|
||
- name: Install dependencies | ||
run: sudo apt-get install -y graphviz | ||
|
||
- name: Build and generate Javadocs | ||
run: ./gradlew generateDebugJavadoc -PgenerateUML --no-daemon | ||
|
||
- name: Deploy to GitHub Pages | ||
uses: actions/upload-pages-artifact@v1 | ||
with: | ||
path: './TeamCode/build/docs/javadoc/' | ||
|
||
- name: Deploy to GitHub Pages | ||
id: deployment | ||
uses: actions/deploy-pages@v1 |
File renamed without changes.
260 changes: 260 additions & 0 deletions
260
TeamCode/src/main/java/org/firstinspires/ftc/teamcode/auton/VisionTest.java
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,260 @@ | ||
/* | ||
* Copyright (c) 2019 OpenFTC Team | ||
* | ||
* Permission is hereby granted, free of charge, to any person obtaining a copy | ||
* of this software and associated documentation files (the "Software"), to deal | ||
* in the Software without restriction, including without limitation the rights | ||
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
* copies of the Software, and to permit persons to whom the Software is | ||
* furnished to do so, subject to the following conditions: | ||
* | ||
* The above copyright notice and this permission notice shall be included in all | ||
* copies or substantial portions of the Software. | ||
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE | ||
* SOFTWARE. | ||
*/ | ||
|
||
package org.firstinspires.ftc.teamcode.auton; | ||
|
||
import com.qualcomm.robotcore.eventloop.opmode.LinearOpMode; | ||
import com.qualcomm.robotcore.eventloop.opmode.TeleOp; | ||
|
||
import org.firstinspires.ftc.robotcore.external.hardware.camera.WebcamName; | ||
import org.opencv.core.Mat; | ||
import org.opencv.core.Point; | ||
import org.opencv.core.Scalar; | ||
import org.opencv.imgproc.Imgproc; | ||
import org.openftc.easyopencv.OpenCvCamera; | ||
import org.openftc.easyopencv.OpenCvCameraFactory; | ||
import org.openftc.easyopencv.OpenCvCameraRotation; | ||
import org.openftc.easyopencv.OpenCvPipeline; | ||
import org.openftc.easyopencv.OpenCvWebcam; | ||
|
||
@TeleOp | ||
public class VisionTest extends LinearOpMode | ||
{ | ||
OpenCvWebcam webcam; | ||
|
||
@Override | ||
public void runOpMode() | ||
{ | ||
/* | ||
* Instantiate an OpenCvCamera object for the camera we'll be using. | ||
* In this sample, we're using a webcam. Note that you will need to | ||
* make sure you have added the webcam to your configuration file and | ||
* adjusted the name here to match what you named it in said config file. | ||
* | ||
* We pass it the view that we wish to use for camera monitor (on | ||
* the RC phone). If no camera monitor is desired, use the alternate | ||
* single-parameter constructor instead (commented out below) | ||
*/ | ||
int cameraMonitorViewId = hardwareMap.appContext.getResources().getIdentifier("cameraMonitorViewId", "id", hardwareMap.appContext.getPackageName()); | ||
webcam = OpenCvCameraFactory.getInstance().createWebcam(hardwareMap.get(WebcamName.class, "Webcam"), cameraMonitorViewId); | ||
|
||
// OR... Do Not Activate the Camera Monitor View | ||
//webcam = OpenCvCameraFactory.getInstance().createWebcam(hardwareMap.get(WebcamName.class, "Webcam 1")); | ||
|
||
/* | ||
* Specify the image processing pipeline we wish to invoke upon receipt | ||
* of a frame from the camera. Note that switching pipelines on-the-fly | ||
* (while a streaming session is in flight) *IS* supported. | ||
*/ | ||
webcam.setPipeline(new SamplePipeline()); | ||
|
||
/* | ||
* Open the connection to the camera device. New in v1.4.0 is the ability | ||
* to open the camera asynchronously, and this is now the recommended way | ||
* to do it. The benefits of opening async include faster init time, and | ||
* better behavior when pressing stop during init (i.e. less of a chance | ||
* of tripping the stuck watchdog) | ||
* | ||
* If you really want to open synchronously, the old method is still available. | ||
*/ | ||
webcam.setMillisecondsPermissionTimeout(5000); // Timeout for obtaining permission is configurable. Set before opening. | ||
webcam.openCameraDeviceAsync(new OpenCvCamera.AsyncCameraOpenListener() | ||
{ | ||
@Override | ||
public void onOpened() | ||
{ | ||
/* | ||
* Tell the webcam to start streaming images to us! Note that you must make sure | ||
* the resolution you specify is supported by the camera. If it is not, an exception | ||
* will be thrown. | ||
* | ||
* Keep in mind that the SDK's UVC driver (what OpenCvWebcam uses under the hood) only | ||
* supports streaming from the webcam in the uncompressed YUV image format. This means | ||
* that the maximum resolution you can stream at and still get up to 30FPS is 480p (640x480). | ||
* Streaming at e.g. 720p will limit you to up to 10FPS and so on and so forth. | ||
* | ||
* Also, we specify the rotation that the webcam is used in. This is so that the image | ||
* from the camera sensor can be rotated such that it is always displayed with the image upright. | ||
* For a front facing camera, rotation is defined assuming the user is looking at the screen. | ||
* For a rear facing camera or a webcam, rotation is defined assuming the camera is facing | ||
* away from the user. | ||
*/ | ||
webcam.startStreaming(320, 240, OpenCvCameraRotation.UPRIGHT); | ||
} | ||
|
||
@Override | ||
public void onError(int errorCode) | ||
{ | ||
/* | ||
* This will be called if the camera could not be opened | ||
*/ | ||
} | ||
}); | ||
|
||
telemetry.addLine("Waiting for start"); | ||
telemetry.update(); | ||
|
||
/* | ||
* Wait for the user to press start on the Driver Station | ||
*/ | ||
waitForStart(); | ||
|
||
while (opModeIsActive()) | ||
{ | ||
/* | ||
* Send some stats to the telemetry | ||
*/ | ||
telemetry.addData("Frame Count", webcam.getFrameCount()); | ||
telemetry.addData("FPS", String.format("%.2f", webcam.getFps())); | ||
telemetry.addData("Total frame time ms", webcam.getTotalFrameTimeMs()); | ||
telemetry.addData("Pipeline time ms", webcam.getPipelineTimeMs()); | ||
telemetry.addData("Overhead time ms", webcam.getOverheadTimeMs()); | ||
telemetry.addData("Theoretical max FPS", webcam.getCurrentPipelineMaxFps()); | ||
telemetry.update(); | ||
|
||
/* | ||
* NOTE: stopping the stream from the camera early (before the end of the OpMode | ||
* when it will be automatically stopped for you) *IS* supported. The "if" statement | ||
* below will stop streaming from the camera when the "A" button on gamepad 1 is pressed. | ||
*/ | ||
if(gamepad1.a) | ||
{ | ||
/* | ||
* IMPORTANT NOTE: calling stopStreaming() will indeed stop the stream of images | ||
* from the camera (and, by extension, stop calling your vision pipeline). HOWEVER, | ||
* if the reason you wish to stop the stream early is to switch use of the camera | ||
* over to, say, Vuforia or TFOD, you will also need to call closeCameraDevice() | ||
* (commented out below), because according to the Android Camera API documentation: | ||
* "Your application should only have one Camera object active at a time for | ||
* a particular hardware camera." | ||
* | ||
* NB: calling closeCameraDevice() will internally call stopStreaming() if applicable, | ||
* but it doesn't hurt to call it anyway, if for no other reason than clarity. | ||
* | ||
* NB2: if you are stopping the camera stream to simply save some processing power | ||
* (or battery power) for a short while when you do not need your vision pipeline, | ||
* it is recommended to NOT call closeCameraDevice() as you will then need to re-open | ||
* it the next time you wish to activate your vision pipeline, which can take a bit of | ||
* time. Of course, this comment is irrelevant in light of the use case described in | ||
* the above "important note". | ||
*/ | ||
webcam.stopStreaming(); | ||
//webcam.closeCameraDevice(); | ||
} | ||
|
||
/* | ||
* For the purposes of this sample, throttle ourselves to 10Hz loop to avoid burning | ||
* excess CPU cycles for no reason. (By default, telemetry is only sent to the DS at 4Hz | ||
* anyway). Of course in a real OpMode you will likely not want to do this. | ||
*/ | ||
sleep(100); | ||
} | ||
} | ||
|
||
/* | ||
* An example image processing pipeline to be run upon receipt of each frame from the camera. | ||
* Note that the processFrame() method is called serially from the frame worker thread - | ||
* that is, a new camera frame will not come in while you're still processing a previous one. | ||
* In other words, the processFrame() method will never be called multiple times simultaneously. | ||
* | ||
* However, the rendering of your processed image to the viewport is done in parallel to the | ||
* frame worker thread. That is, the amount of time it takes to render the image to the | ||
* viewport does NOT impact the amount of frames per second that your pipeline can process. | ||
* | ||
* IMPORTANT NOTE: this pipeline is NOT invoked on your OpMode thread. It is invoked on the | ||
* frame worker thread. This should not be a problem in the vast majority of cases. However, | ||
* if you're doing something weird where you do need it synchronized with your OpMode thread, | ||
* then you will need to account for that accordingly. | ||
*/ | ||
class SamplePipeline extends OpenCvPipeline | ||
{ | ||
boolean viewportPaused; | ||
|
||
/* | ||
* NOTE: if you wish to use additional Mat objects in your processing pipeline, it is | ||
* highly recommended to declare them here as instance variables and re-use them for | ||
* each invocation of processFrame(), rather than declaring them as new local variables | ||
* each time through processFrame(). This removes the danger of causing a memory leak | ||
* by forgetting to call mat.release(), and it also reduces memory pressure by not | ||
* constantly allocating and freeing large chunks of memory. | ||
*/ | ||
|
||
@Override | ||
public Mat processFrame(Mat input) | ||
{ | ||
/* | ||
* IMPORTANT NOTE: the input Mat that is passed in as a parameter to this method | ||
* will only dereference to the same image for the duration of this particular | ||
* invocation of this method. That is, if for some reason you'd like to save a copy | ||
* of this particular frame for later use, you will need to either clone it or copy | ||
* it to another Mat. | ||
*/ | ||
|
||
/* | ||
* Draw a simple box around the middle 1/2 of the entire frame | ||
*/ | ||
Imgproc.rectangle( | ||
input, | ||
new Point( | ||
input.cols()/4, | ||
input.rows()/4), | ||
new Point( | ||
input.cols()*(3f/4f), | ||
input.rows()*(3f/4f)), | ||
new Scalar(0, 255, 0), 4); | ||
|
||
/** | ||
* NOTE: to see how to get data from your pipeline to your OpMode as well as how | ||
* to change which stage of the pipeline is rendered to the viewport when it is | ||
* tapped, please see {@link PipelineStageSwitchingExample} | ||
*/ | ||
|
||
return input; | ||
} | ||
|
||
@Override | ||
public void onViewportTapped() | ||
{ | ||
/* | ||
* The viewport (if one was specified in the constructor) can also be dynamically "paused" | ||
* and "resumed". The primary use case of this is to reduce CPU, memory, and power load | ||
* when you need your vision pipeline running, but do not require a live preview on the | ||
* robot controller screen. For instance, this could be useful if you wish to see the live | ||
* camera preview as you are initializing your robot, but you no longer require the live | ||
* preview after you have finished your initialization process; pausing the viewport does | ||
* not stop running your pipeline. | ||
* | ||
* Here we demonstrate dynamically pausing/resuming the viewport when the user taps it | ||
*/ | ||
|
||
viewportPaused = !viewportPaused; | ||
|
||
if(viewportPaused) | ||
{ | ||
webcam.pauseViewport(); | ||
} | ||
else | ||
{ | ||
webcam.resumeViewport(); | ||
} | ||
} | ||
} | ||
} |