Boom. Go fishies. This is a bunch of empty classes with stuff we talk…

…ed about that we may need. It may be unorganized and not for top efficiency. So. Good luck folks. Do what you need! But be productive

We added:
-a autodrive folder
-a "singer movement" folder that contains the note flow, which is in the singer, the shooting wheels, and the intake wheels
-and some other stuff.

autoDrive/autoDrive.py

@@ -0,0 +1 @@
+#auto drive stuff

climberControl/climberControl.py

@@ -0,0 +1,2 @@
+#needs a sparkmax, relay thing
+#the relay thing(?) should basically be a solenoid that automatically braces/locks/something so we stay up when the time is done

humanInterface/operatorInterface.py

@@ -0,0 +1 @@
+#Need operator controls

singerMovement/elevator.py

@@ -0,0 +1,2 @@
+#controlling the height of the singer on the elevator
+#might need new classes, or to get rid of this class. Whatever you need!

singerMovement/noteFlow/intake.py

@@ -0,0 +1 @@
+#intake wheels inside the singer and the ones on the bottom of the robot? For now. Under the assumption that we will always spin these at the same time?

singerMovement/noteFlow/noteDetector.py

@@ -0,0 +1 @@
+#Time of flight sensor

singerMovement/noteFlow/shooting.py

@@ -0,0 +1 @@
+#SparkMAX for the shooter wheels

singerMovement/singerAngle.py

@@ -0,0 +1 @@
+#Controlling the angle of the singer

utils/allianceTransformUtils.py

@@ -12,8 +12,8 @@
  Utilities to help transform from blue alliance to red if needed
  We went rogue and chose a coordinate system where the origin is always in the 
  bottom left on the blue alliance
-"""
-class AllianceTransformUtils:
+
+ class AllianceTransformUtils:
     @staticmethod
     def transformX(in):
         if DriverStation.getAlliance() == AllianceStationID.Red:
@@ -23,4 +23,6 @@ def transformX(in):
     
     def transformY(in):
         return in
+"""
+