WM-SEMERU · danielrcardenas · May 15, 2026 · Jun 30, 2025 · Jun 30, 2025 · Jun 30, 2025
diff --git a/dvc-data/systems/dronology/bpe_models/java_py_bpe128k.model b/dvc-data/systems/dronology/bpe_models/java_py_bpe128k.model
diff --git a/dvc-data/systems/dronology/bpe_models/java_py_bpe128k.vocab b/dvc-data/systems/dronology/bpe_models/java_py_bpe128k.vocab
diff --git a/dvc-data/systems/dronology/bpe_models/java_py_bpe32k.model b/dvc-data/systems/dronology/bpe_models/java_py_bpe32k.model
diff --git a/dvc-data/systems/dronology/bpe_models/java_py_bpe32k.vocab b/dvc-data/systems/dronology/bpe_models/java_py_bpe32k.vocab
diff --git a/dvc-data/systems/dronology/bpe_models/java_py_bpe8k.model b/dvc-data/systems/dronology/bpe_models/java_py_bpe8k.model
diff --git a/dvc-data/systems/dronology/bpe_models/java_py_bpe8k.vocab b/dvc-data/systems/dronology/bpe_models/java_py_bpe8k.vocab
diff --git a/dvc-data/systems/dronology/bpe_models/java_py_wiki_bpe128k.model b/dvc-data/systems/dronology/bpe_models/java_py_wiki_bpe128k.model
diff --git a/dvc-data/systems/dronology/bpe_models/java_py_wiki_bpe128k.vocab b/dvc-data/systems/dronology/bpe_models/java_py_wiki_bpe128k.vocab
diff --git a/dvc-data/systems/dronology/bpe_models/java_py_wiki_bpe32k.model b/dvc-data/systems/dronology/bpe_models/java_py_wiki_bpe32k.model
diff --git a/dvc-data/systems/dronology/bpe_models/java_py_wiki_bpe32k.vocab b/dvc-data/systems/dronology/bpe_models/java_py_wiki_bpe32k.vocab
diff --git a/dvc-data/systems/dronology/bpe_models/java_py_wiki_bpe8k.model b/dvc-data/systems/dronology/bpe_models/java_py_wiki_bpe8k.model
diff --git a/dvc-data/systems/dronology/bpe_models/java_py_wiki_bpe8k.vocab b/dvc-data/systems/dronology/bpe_models/java_py_wiki_bpe8k.vocab
diff --git a/dvc-data/systems/dronology/bpe_models/train_bpe.py b/dvc-data/systems/dronology/bpe_models/train_bpe.py
@@ -0,0 +1,30 @@
+import sentencepiece as spm
+import os
+
+# Path to your merged CSN corpus
+CORPUS = "pretrain_corpus_code_wiki.txt"  
+
+# Where to write your models
+OUT_DIR = "models"
+os.makedirs(OUT_DIR, exist_ok=True)
+
+# (vocab_size, filename prefix)
+for vocab_size, prefix in [(8000, "bpe8k"),
+                           (32000, "bpe32k"),
+                           (128000, "bpe128k")]:
+    model_path = os.path.join(OUT_DIR, prefix)
+    spm.SentencePieceTrainer.Train(
+        input=CORPUS,
+        model_prefix=model_path,
+        vocab_size=vocab_size,
+        model_type="bpe",
+        character_coverage=1.0,
+        pad_id=0,
+        unk_id=1,
+        bos_id=2,
+        eos_id=3,
+        user_defined_symbols=[],
+        input_sentence_size=0,
+        shuffle_input_sentence=True,
+    )
+    print(f"Trained {prefix}: {model_path}.model (+ .vocab)")
diff --git a/dvc-data/systems/dronology/corpus/dronology_conv.csv b/dvc-data/systems/dronology/corpus/dronology_conv.csv
diff --git a/dvc-data/systems/dronology/corpus/dronology_conv_with_bpe_fixed.csv b/dvc-data/systems/dronology/corpus/dronology_conv_with_bpe_fixed.csv
diff --git a/dvc-data/systems/dronology/corpus/dronology_text.txt b/dvc-data/systems/dronology/corpus/dronology_text.txt
diff --git a/dvc-data/systems/dronology/corpus/req/RE-100.txt b/dvc-data/systems/dronology/corpus/req/RE-100.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Removal of planned flight
+[DESCRIPTION]
+If requested  the _SingleUAVFlightPlanScheduler_ shall unassign the flight plan assigned to a UAV that is awaiting execution.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-101.txt b/dvc-data/systems/dronology/corpus/req/RE-101.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Assigning new flight plan upon completion of previous flight
+[DESCRIPTION]
+If a UAV has pending flight plans  then when it reaches the final waypoint of its current flight plan  the _SingleUAVFlightPlanScheduler_ shall execute the next assigned flight plan.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-103.txt b/dvc-data/systems/dronology/corpus/req/RE-103.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Remove pending plans when return-to-home
+[DESCRIPTION]
+When a UAV's current flight is cancelled  the _SingleUAVFlightPlanScheduler_ shall in turn cancel all scheduled flight plans for that UAV.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-114.txt b/dvc-data/systems/dronology/corpus/req/RE-114.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Display map in UI
+[DESCRIPTION]
+When the _RealTimeFlightUI_ is loaded  a map shall be displayed.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-25.txt b/dvc-data/systems/dronology/corpus/req/RE-25.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+UAV Identification
+[DESCRIPTION]
+The _VehicleCore_ shall assign a unique ID to each activated UAV.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-28.txt b/dvc-data/systems/dronology/corpus/req/RE-28.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+UAV Flight Plan Execution
+[DESCRIPTION]
+The _SingleUAVFlightPlanScheduler_ shall only execute one flight plan at a time for each UAV.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-36.txt b/dvc-data/systems/dronology/corpus/req/RE-36.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Only one instance of each registered drone may be active any any time
+[DESCRIPTION]
+The _UAVActivationManager_ shall ensure that only one instance of each registered drone is active at any time.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-424.txt b/dvc-data/systems/dronology/corpus/req/RE-424.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Return To Home without detours
+[DESCRIPTION]
+"When the ""return to home"" command is issued  the _FlightManager_ shall return the UAV to its original launch location without issuing any additional waypoint or routing commands."
diff --git a/dvc-data/systems/dronology/corpus/req/RE-501.txt b/dvc-data/systems/dronology/corpus/req/RE-501.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Flight route defined as waypoints
+[DESCRIPTION]
+The _FlightRouteManager_ shall define flight routes as an ordered sequence of waypoints in which the first waypoint represents the first target location and the final waypoint represents the final target location.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-505.txt b/dvc-data/systems/dronology/corpus/req/RE-505.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Flight route persistence
+[DESCRIPTION]
+The _FlightRouteManager_ shall persist flight routes.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-508.txt b/dvc-data/systems/dronology/corpus/req/RE-508.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Specify takeoff altitude
+[DESCRIPTION]
+When a flight route requires a customized takeoff altitude that differs from the system's default takeoff altitude  it shall be specified in the flight route.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-510.txt b/dvc-data/systems/dronology/corpus/req/RE-510.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Coordinate system conversion
+[DESCRIPTION]
+When requested  the _CoordinateSystem_ shall transform coordinates to alternate formats.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-516.txt b/dvc-data/systems/dronology/corpus/req/RE-516.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Calculate distances
+[DESCRIPTION]
+When given two coordinates the _CoordinateSystem_ shall compute the distance between them.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-541.txt b/dvc-data/systems/dronology/corpus/req/RE-541.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Predefined flight patterns
+[DESCRIPTION]
+The _MissionPlanner _shall manage predefined FlightPatterns
diff --git a/dvc-data/systems/dronology/corpus/req/RE-545.txt b/dvc-data/systems/dronology/corpus/req/RE-545.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Cancel Mission
+[DESCRIPTION]
+When requested  if a mission is currently active  the _MissionPlanner _shall cancel the active mission.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-547.txt b/dvc-data/systems/dronology/corpus/req/RE-547.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Flight Plan scheduling
+[DESCRIPTION]
+When requested  the _SingleUAVFlightPlanScheduler_ shall schedule a route for execution.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-549.txt b/dvc-data/systems/dronology/corpus/req/RE-549.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Manual Flight Plan Assignment
+[DESCRIPTION]
+If a route contains a specific {{UAV_ID}}  the _SingleUAVFlightPlanScheduler_ shall assign the route to the given UAV.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-551.txt b/dvc-data/systems/dronology/corpus/req/RE-551.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Automatic Flight Plan Assignment
+[DESCRIPTION]
+If a scheduled flight is not manually assigned to a UAV  the _SingleUAVFlightPlanScheduler_ shall assign the route automatically to an UAV
diff --git a/dvc-data/systems/dronology/corpus/req/RE-555.txt b/dvc-data/systems/dronology/corpus/req/RE-555.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Hover at completion of flight
+[DESCRIPTION]
+If a UAV does not have any pending flight plans  then when it reaches the final waypoint of its current flight plan  the _SingleUAVFlightPlanScheduler_ shall notify the UAV to hover in place.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-574.txt b/dvc-data/systems/dronology/corpus/req/RE-574.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Support for GCS connected UAVs
+[DESCRIPTION]
+The _VehicleCore_ shall support UAVs connected via the _GCS_
diff --git a/dvc-data/systems/dronology/corpus/req/RE-576.txt b/dvc-data/systems/dronology/corpus/req/RE-576.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Support for internally simulated UAVs
+[DESCRIPTION]
+The _VehicleCore_ shall support virtual UAVs
diff --git a/dvc-data/systems/dronology/corpus/req/RE-587.txt b/dvc-data/systems/dronology/corpus/req/RE-587.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Deactivates Physical UAVs
+[DESCRIPTION]
+When a UAV is deactivated the _UAVActivationManager_ shall cancel all current and scheduled flight plans
diff --git a/dvc-data/systems/dronology/corpus/req/RE-589.txt b/dvc-data/systems/dronology/corpus/req/RE-589.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Establish maximum number of activated UAVs
+[DESCRIPTION]
+When the maximum numbers of allowed activated UAVs has been reached  the _UAVActivationManager_ shall reject any further activation requests.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-594.txt b/dvc-data/systems/dronology/corpus/req/RE-594.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Simulate takeoff
+[DESCRIPTION]
+When given a takeoff command the _InternalSimulator_ shall move the UAV to the takeoff altitude corresponding to its current longitude and latitude.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-595.txt b/dvc-data/systems/dronology/corpus/req/RE-595.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Simulate goto
+[DESCRIPTION]
+When given a goto command  the _InternalSimulator_ shall update the location of the UAV at increments of {{SIMULATION_STEP_SIZE}} meters  moving it towards the target destination until the destination is reached.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-596.txt b/dvc-data/systems/dronology/corpus/req/RE-596.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Simulate land
+[DESCRIPTION]
+When given a landing command the _InternalSimulator_ shall move the UAV from to the ground altitude corresponding to its current longitude and latitude.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-597.txt b/dvc-data/systems/dronology/corpus/req/RE-597.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Simulate battery
+[DESCRIPTION]
+The _InternalSimulator_ shall approximate the state of the battery
diff --git a/dvc-data/systems/dronology/corpus/req/RE-611.txt b/dvc-data/systems/dronology/corpus/req/RE-611.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Logging of Flight Plan related Events
+[DESCRIPTION]
+The _ActivityLogger_ shall log all flight plan related events.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-616.txt b/dvc-data/systems/dronology/corpus/req/RE-616.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Logging of GCS related events
+[DESCRIPTION]
+The _ActivityLogger_ shall log all commands sent to and messages received from a _CGS_.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-626.txt b/dvc-data/systems/dronology/corpus/req/RE-626.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+UI middleware lists currently active UAVs
+[DESCRIPTION]
+The _UIMiddleware_ shall provide a list of all active UAVs
diff --git a/dvc-data/systems/dronology/corpus/req/RE-628.txt b/dvc-data/systems/dronology/corpus/req/RE-628.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+UI middleware lists all saved flight routes
+[DESCRIPTION]
+The _UIMiddleware_ shall provide a list of all existing routes
diff --git a/dvc-data/systems/dronology/corpus/req/RE-630.txt b/dvc-data/systems/dronology/corpus/req/RE-630.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+UI middleware forwards commands from clients to dronology
+[DESCRIPTION]
+The _UIMiddleware_ accepts commands from UIs and forwards to Dronology
diff --git a/dvc-data/systems/dronology/corpus/req/RE-634.txt b/dvc-data/systems/dronology/corpus/req/RE-634.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+UI middleware provides support for modifying flight routes
+[DESCRIPTION]
+The _UIMiddleware_ shall enable the creation and modification of flight routes
diff --git a/dvc-data/systems/dronology/corpus/req/RE-637.txt b/dvc-data/systems/dronology/corpus/req/RE-637.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+UI middleware supports route assignment to UAV
+[DESCRIPTION]
+The _UIMiddleware_ shall enable an existing route to be assigned to an active UAV.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-639.txt b/dvc-data/systems/dronology/corpus/req/RE-639.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+UI accepts mission plans
+[DESCRIPTION]
+The _UIMiddleware_ shall accept and activate a mission plan upon request.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-643.txt b/dvc-data/systems/dronology/corpus/req/RE-643.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Load default coordinates
+[DESCRIPTION]
+When loading the map view it shall be positioned at the pre-defined location
diff --git a/dvc-data/systems/dronology/corpus/req/RE-646.txt b/dvc-data/systems/dronology/corpus/req/RE-646.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Assign Routes
+[DESCRIPTION]
+The _RouteAssignmentUI_ shall provide means to select an existing routes and assign them to a UAV.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-649.txt b/dvc-data/systems/dronology/corpus/req/RE-649.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Transmit Route assignments to UI Middleware
+[DESCRIPTION]
+When a route is assigned or removed from a UAV  the _RouteAssignmentUI_ shall notify Dronology.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-656.txt b/dvc-data/systems/dronology/corpus/req/RE-656.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Modify assigned routes
+[DESCRIPTION]
+A user may reorder routes or remove flight plans assigned to a UAV as long as the flight has not started execution.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-672.txt b/dvc-data/systems/dronology/corpus/req/RE-672.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Route creation and modification
+[DESCRIPTION]
+The _RouteCreationUI_ shall allow the user to create and modify a route.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-677.txt b/dvc-data/systems/dronology/corpus/req/RE-677.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Delete a route
+[DESCRIPTION]
+The _RouteCreationUI_ shall allow a user to delete a route.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-679.txt b/dvc-data/systems/dronology/corpus/req/RE-679.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Display a list of existing routes
+[DESCRIPTION]
+When the _RouteCreationUI_ is loaded a list of all existing routes shall be displayed.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-681.txt b/dvc-data/systems/dronology/corpus/req/RE-681.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Display activated UAVs
+[DESCRIPTION]
+The _RealTimeFlightUI_ shall display the name and status of all currently activated UAVs
diff --git a/dvc-data/systems/dronology/corpus/req/RE-689.txt b/dvc-data/systems/dronology/corpus/req/RE-689.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Display active routes
+[DESCRIPTION]
+The _RealTimeFlightUI_ shall display all currently active flight plans on the map.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-691.txt b/dvc-data/systems/dronology/corpus/req/RE-691.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+UAV Operations
+[DESCRIPTION]
+The _RealTimeFlightUI_ shall allow users to apply flight operations to one or more selected UAVs.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-693.txt b/dvc-data/systems/dronology/corpus/req/RE-693.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Emergency operations
+[DESCRIPTION]
+The _RealTimeFlightUI_ shall allow users to perform emergency operations (e.g. hovering multiple UAVs  sending multiple UAVs to home) to a group of UAVs
diff --git a/dvc-data/systems/dronology/corpus/req/RE-695.txt b/dvc-data/systems/dronology/corpus/req/RE-695.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Following UAVs
+[DESCRIPTION]
+The _RealTimeFlightUI_ shall allow users to follow one or multiple UAVs on the map.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-701.txt b/dvc-data/systems/dronology/corpus/req/RE-701.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Monitoring Messages
+[DESCRIPTION]
+The _DronologyRuntimeMonitor_ shall provide functionality to retrieve monitoring messages and distribute them to clients
diff --git a/dvc-data/systems/dronology/corpus/req/RE-706.txt b/dvc-data/systems/dronology/corpus/req/RE-706.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Publishing Monitoring Messages
+[DESCRIPTION]
+The _DronologyRuntimeMonitor_ shall be able to receive messages from any Dronology component
diff --git a/dvc-data/systems/dronology/corpus/req/RE-709.txt b/dvc-data/systems/dronology/corpus/req/RE-709.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Connect GCS to Dronology via Middleware
+[DESCRIPTION]
+The _GCSMiddleware_ shall handle multiple _GCS_
diff --git a/dvc-data/systems/dronology/corpus/req/RE-714.txt b/dvc-data/systems/dronology/corpus/req/RE-714.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Groundstation-Middleware Communication Protocol
+[DESCRIPTION]
+The _GCSMiddleware _ shall follow a predefined set of steps to establish a connection between a _GCS_ and Dronology
diff --git a/dvc-data/systems/dronology/corpus/req/RE-722.txt b/dvc-data/systems/dronology/corpus/req/RE-722.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+UAV Messages
+[DESCRIPTION]
+The _GCSMiddleware_ shall handle state messages   monitoring messages  and mode change messages  received from an _GCS_.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-729.txt b/dvc-data/systems/dronology/corpus/req/RE-729.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+UAV Commands
+[DESCRIPTION]
+The _GCSMiddleware_ shall forward commands sent from Dronology to a _GCS_
diff --git a/dvc-data/systems/dronology/corpus/req/RE-759.txt b/dvc-data/systems/dronology/corpus/req/RE-759.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Mission Planning
+[DESCRIPTION]
+The _MissionPlanner_ shall execute flight plans for multiple UAVs concurrently.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-766.txt b/dvc-data/systems/dronology/corpus/req/RE-766.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Multiple Map Types
+[DESCRIPTION]
+The _MapComponent_ shall support different types of map layers (e.g.  terrain  satellite)
diff --git a/dvc-data/systems/dronology/corpus/req/RE-77.txt b/dvc-data/systems/dronology/corpus/req/RE-77.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Waypoint definition
+[DESCRIPTION]
+Each waypoint shall be specified using coordinates that include longitude  latitude  and altitude.
diff --git a/dvc-data/systems/dronology/corpus/req/RE-8.txt b/dvc-data/systems/dronology/corpus/req/RE-8.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+UAV State transitions
+[DESCRIPTION]
+When requested  the _VehicleCore_ shall shall transition the UAV between states according to allowed state transitions as depicted in the UAV state transition diagram
diff --git a/dvc-data/systems/dronology/corpus/req/RE-80.txt b/dvc-data/systems/dronology/corpus/req/RE-80.txt
@@ -0,0 +1,4 @@
+[SUMMARY]
+Visiting waypoints during flight plan 
+[DESCRIPTION]
+When a flight plan is executed  the _VehicleCore_ shall send the next waypoint to the UAV.