-
Notifications
You must be signed in to change notification settings - Fork 680
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chat: assistant files use unix line endings
- Loading branch information
Showing
24 changed files
with
697 additions
and
697 deletions.
There are no files selected for viewing
108 changes: 54 additions & 54 deletions
108
MAVProxy/modules/mavproxy_chat/assistant_setup/assistant_instructions.txt
Large diffs are not rendered by default.
Oops, something went wrong.
58 changes: 29 additions & 29 deletions
58
MAVProxy/modules/mavproxy_chat/assistant_setup/copter_flightmodes.txt
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 |
|---|---|---|
| @@ -1,29 +1,29 @@ | ||
| This file holds the Copter flight mode name to number mapping | ||
| STABILIZE = 0, // pilot directly controls the airframe angle with roll, pitch and yaw stick inputs. Pilot directly controls throttle | ||
| ACRO = 1, // pilot directly controls the body-frame angular rate. pilot directly controls throttle | ||
| ALT_HOLD = 2, // pilot directly controls the vehicle roll, pitch and yaw angles. Pilot's throttle control controls climb rate | ||
| AUTO = 3, // fully automatic waypoint control using mission commands | ||
| GUIDED = 4, // fully automatic fly to coordinate or fly at velocity/direction using mavlink commands. | ||
| LOITER = 5, // pilot controls the vehicle's 3D speed and acceleration with roll, pitch and throttle input. Heading is controlled with the yaw stick | ||
| RTL = 6, // automatic return to launching point | ||
| CIRCLE = 7, // automatic circular flight with automatic throttle | ||
| LAND = 9, // automatic landing with horizontal position control | ||
| DRIFT = 11, // semi-autonomous position, yaw and throttle control. rarely used. | ||
| SPORT = 13, // manual earth-frame angular rate control with manual throttle. very rarely used | ||
| FLIP = 14, // automatically flip the vehicle 360 degrees | ||
| AUTOTUNE = 15, // automatically tune the vehicle's roll and pitch gains | ||
| POSHOLD = 16, // automatic position hold with manual override, with automatic throttle. very similar to Loiter mode | ||
| BRAKE = 17, // full-brake using inertial/GPS system, no pilot input | ||
| THROW = 18, // throw to launch mode using inertial/GPS system, no pilot input | ||
| AVOID_ADSB = 19, // automatic avoidance of manned vehicle. very rarely used | ||
| GUIDED_NOGPS = 20, // guided mode but only accepts attitude and altitude commands | ||
| SMART_RTL = 21, // SMART_RTL returns vehicle home by retracing its steps | ||
| FLOWHOLD = 22, // FLOWHOLD holds position with optical flow without rangefinder. similar to Loiter. very rarely used | ||
| FOLLOW = 23, // follow attempts to follow another vehicle or ground station | ||
| ZIGZAG = 24, // ZIGZAG mode is able to fly in a zigzag manner with predefined point A and point B. Normally used for crop spraying vehicles. | ||
| SYSTEMID = 25, // System ID mode produces automated system identification signals in the controllers. very rarely used | ||
| AUTOROTATE = 26, // Autonomous autorotation. Used only for traditional helicopters | ||
| AUTO_RTL = 27, // return to launch but using an Auto mission starting from the DO_LAND_START command | ||
| TURTLE = 28, // Flip vehicle to recover after crash | ||
| This file holds the Copter flight mode name to number mapping | ||
|
|
||
| STABILIZE = 0, // pilot directly controls the airframe angle with roll, pitch and yaw stick inputs. Pilot directly controls throttle | ||
| ACRO = 1, // pilot directly controls the body-frame angular rate. pilot directly controls throttle | ||
| ALT_HOLD = 2, // pilot directly controls the vehicle roll, pitch and yaw angles. Pilot's throttle control controls climb rate | ||
| AUTO = 3, // fully automatic waypoint control using mission commands | ||
| GUIDED = 4, // fully automatic fly to coordinate or fly at velocity/direction using mavlink commands. | ||
| LOITER = 5, // pilot controls the vehicle's 3D speed and acceleration with roll, pitch and throttle input. Heading is controlled with the yaw stick | ||
| RTL = 6, // automatic return to launching point | ||
| CIRCLE = 7, // automatic circular flight with automatic throttle | ||
| LAND = 9, // automatic landing with horizontal position control | ||
| DRIFT = 11, // semi-autonomous position, yaw and throttle control. rarely used. | ||
| SPORT = 13, // manual earth-frame angular rate control with manual throttle. very rarely used | ||
| FLIP = 14, // automatically flip the vehicle 360 degrees | ||
| AUTOTUNE = 15, // automatically tune the vehicle's roll and pitch gains | ||
| POSHOLD = 16, // automatic position hold with manual override, with automatic throttle. very similar to Loiter mode | ||
| BRAKE = 17, // full-brake using inertial/GPS system, no pilot input | ||
| THROW = 18, // throw to launch mode using inertial/GPS system, no pilot input | ||
| AVOID_ADSB = 19, // automatic avoidance of manned vehicle. very rarely used | ||
| GUIDED_NOGPS = 20, // guided mode but only accepts attitude and altitude commands | ||
| SMART_RTL = 21, // SMART_RTL returns vehicle home by retracing its steps | ||
| FLOWHOLD = 22, // FLOWHOLD holds position with optical flow without rangefinder. similar to Loiter. very rarely used | ||
| FOLLOW = 23, // follow attempts to follow another vehicle or ground station | ||
| ZIGZAG = 24, // ZIGZAG mode is able to fly in a zigzag manner with predefined point A and point B. Normally used for crop spraying vehicles. | ||
| SYSTEMID = 25, // System ID mode produces automated system identification signals in the controllers. very rarely used | ||
| AUTOROTATE = 26, // Autonomous autorotation. Used only for traditional helicopters | ||
| AUTO_RTL = 27, // return to launch but using an Auto mission starting from the DO_LAND_START command | ||
| TURTLE = 28, // Flip vehicle to recover after crash | ||
|
|
28 changes: 14 additions & 14 deletions
28
MAVProxy/modules/mavproxy_chat/assistant_setup/delete_wakeup_timers.json
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 |
|---|---|---|
| @@ -1,14 +1,14 @@ | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "delete_wakeup_timers", | ||
| "description": "Delete all active wakeup timers. You can optionally provide a message parameter to filter which timers will be deleted based on their message. When specifying the message parameter, you can use regular expressions (regex) to match patterns within the timer messages. This is useful when you want to delete timers with specific keywords or patterns in their message. For example, to delete all timers containing the word 'hello', you can use the regex '.*hello.*', where the dot-star (.*) pattern matches any character sequence.", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "message": {"type": "string", "description": "wakeup message of timers to be deleted. regex values are accepted."} | ||
| }, | ||
| "required": [] | ||
| } | ||
| } | ||
| } | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "delete_wakeup_timers", | ||
| "description": "Delete all active wakeup timers. You can optionally provide a message parameter to filter which timers will be deleted based on their message. When specifying the message parameter, you can use regular expressions (regex) to match patterns within the timer messages. This is useful when you want to delete timers with specific keywords or patterns in their message. For example, to delete all timers containing the word 'hello', you can use the regex '.*hello.*', where the dot-star (.*) pattern matches any character sequence.", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "message": {"type": "string", "description": "wakeup message of timers to be deleted. regex values are accepted."} | ||
| }, | ||
| "required": [] | ||
| } | ||
| } | ||
| } |
24 changes: 12 additions & 12 deletions
24
MAVProxy/modules/mavproxy_chat/assistant_setup/get_all_parameters.json
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 |
|---|---|---|
| @@ -1,12 +1,12 @@ | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_all_parameters", | ||
| "description": "Get all available parameter names and values", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": {}, | ||
| "required": [] | ||
| } | ||
| } | ||
| } | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_all_parameters", | ||
| "description": "Get all available parameter names and values", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": {}, | ||
| "required": [] | ||
| } | ||
| } | ||
| } |
24 changes: 12 additions & 12 deletions
24
MAVProxy/modules/mavproxy_chat/assistant_setup/get_available_mavlink_messages.json
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 |
|---|---|---|
| @@ -1,12 +1,12 @@ | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_available_mavlink_messages", | ||
| "description": "Get a list of mavlink message names that can be retrieved using the get_mavlink_message function", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": {}, | ||
| "required": [] | ||
| } | ||
| } | ||
| } | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_available_mavlink_messages", | ||
| "description": "Get a list of mavlink message names that can be retrieved using the get_mavlink_message function", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": {}, | ||
| "required": [] | ||
| } | ||
| } | ||
| } |
22 changes: 11 additions & 11 deletions
22
MAVProxy/modules/mavproxy_chat/assistant_setup/get_current_datetime.json
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 |
|---|---|---|
| @@ -1,12 +1,12 @@ | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_current_datetime", | ||
| "description": "Get the current date and time, e.g. 'Saturday, June 24, 2023 6:14:14 PM'", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": {}, | ||
| "required": [] | ||
| } | ||
| } | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_current_datetime", | ||
| "description": "Get the current date and time, e.g. 'Saturday, June 24, 2023 6:14:14 PM'", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": {}, | ||
| "required": [] | ||
| } | ||
| } | ||
| } |
34 changes: 17 additions & 17 deletions
34
MAVProxy/modules/mavproxy_chat/assistant_setup/get_location_plus_dist_at_bearing.json
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 |
|---|---|---|
| @@ -1,17 +1,17 @@ | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_location_plus_dist_at_bearing", | ||
| "description": "Calculate the latitude and longitude given an existing latitude and longitude and a distance in meters and a bearing in degrees", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "latitude": {"type": "number", "description": "latitude in degrees"}, | ||
| "longitude": {"type": "number", "description": "longitude in degrees"}, | ||
| "distance": {"type": "number", "description": "distance to move meters"}, | ||
| "bearing": {"type": "number", "description": "bearing in degrees. 0 is North, 90 is East, etc"} | ||
| }, | ||
| "required": ["latitude", "longitude", "distance", "bearing"] | ||
| } | ||
| } | ||
| } | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_location_plus_dist_at_bearing", | ||
| "description": "Calculate the latitude and longitude given an existing latitude and longitude and a distance in meters and a bearing in degrees", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "latitude": {"type": "number", "description": "latitude in degrees"}, | ||
| "longitude": {"type": "number", "description": "longitude in degrees"}, | ||
| "distance": {"type": "number", "description": "distance to move meters"}, | ||
| "bearing": {"type": "number", "description": "bearing in degrees. 0 is North, 90 is East, etc"} | ||
| }, | ||
| "required": ["latitude", "longitude", "distance", "bearing"] | ||
| } | ||
| } | ||
| } |
34 changes: 17 additions & 17 deletions
34
MAVProxy/modules/mavproxy_chat/assistant_setup/get_location_plus_offset.json
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 |
|---|---|---|
| @@ -1,17 +1,17 @@ | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_location_plus_offset", | ||
| "description": "Calculate the latitude and longitude given an existing latitude and longitude and distances (in meters) North and East", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "latitude": {"type": "number", "description": "latitude in degrees"}, | ||
| "longitude": {"type": "number", "description": "longitude in degrees"}, | ||
| "distance_north": {"type": "number", "description": "distance to move North in meters"}, | ||
| "distance_east": {"type": "number", "description": "distance to move East in meters"} | ||
| }, | ||
| "required": ["latitude", "longitude", "distance_north", "distance_east"] | ||
| } | ||
| } | ||
| } | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_location_plus_offset", | ||
| "description": "Calculate the latitude and longitude given an existing latitude and longitude and distances (in meters) North and East", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "latitude": {"type": "number", "description": "latitude in degrees"}, | ||
| "longitude": {"type": "number", "description": "longitude in degrees"}, | ||
| "distance_north": {"type": "number", "description": "distance to move North in meters"}, | ||
| "distance_east": {"type": "number", "description": "distance to move East in meters"} | ||
| }, | ||
| "required": ["latitude", "longitude", "distance_north", "distance_east"] | ||
| } | ||
| } | ||
| } |
28 changes: 14 additions & 14 deletions
28
MAVProxy/modules/mavproxy_chat/assistant_setup/get_mavlink_message.json
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 |
|---|---|---|
| @@ -1,14 +1,14 @@ | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_mavlink_message", | ||
| "description": "Get a mavlink message including all fields and values sent by the vehicle. The list of available messages can be retrieved using the get_available_mavlink_messages", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "message": {"type": "string", "description": "mavlink message name (e.g. HEARTBEAT, VFR_HUD, GLOBAL_POSITION_INT, etc)"} | ||
| }, | ||
| "required": ["message"] | ||
| } | ||
| } | ||
| } | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_mavlink_message", | ||
| "description": "Get a mavlink message including all fields and values sent by the vehicle. The list of available messages can be retrieved using the get_available_mavlink_messages", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "message": {"type": "string", "description": "mavlink message name (e.g. HEARTBEAT, VFR_HUD, GLOBAL_POSITION_INT, etc)"} | ||
| }, | ||
| "required": ["message"] | ||
| } | ||
| } | ||
| } |
30 changes: 15 additions & 15 deletions
30
MAVProxy/modules/mavproxy_chat/assistant_setup/get_mode_mapping.json
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 |
|---|---|---|
| @@ -1,15 +1,15 @@ | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_mode_mapping", | ||
| "description": "Get a list of mode names to mode numbers available for this vehicle. If the name or number parameter is provided only that mode's name and number will be returned. If neither name nor number is provided the full list of available modes will be returned", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "name": {"type": "string", "description": "flight mode name (e.g. Guided, Loiter, RTL)"}, | ||
| "number": {"type": "number", "description": "flight mode number"} | ||
| }, | ||
| "required": [] | ||
| } | ||
| } | ||
| } | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_mode_mapping", | ||
| "description": "Get a list of mode names to mode numbers available for this vehicle. If the name or number parameter is provided only that mode's name and number will be returned. If neither name nor number is provided the full list of available modes will be returned", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "name": {"type": "string", "description": "flight mode name (e.g. Guided, Loiter, RTL)"}, | ||
| "number": {"type": "number", "description": "flight mode number"} | ||
| }, | ||
| "required": [] | ||
| } | ||
| } | ||
| } |
30 changes: 15 additions & 15 deletions
30
MAVProxy/modules/mavproxy_chat/assistant_setup/get_parameter.json
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 |
|---|---|---|
| @@ -1,15 +1,15 @@ | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_parameter", | ||
| "description": "Get a vehicle parameter's value. The full list of available parameters and their values is available using the get_all_parameters function", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "name": {"type": "string", "description": "parameter name (e.g. ARMING_CHECK, LOG_BITMASK). Regex expressions are supported"}, | ||
| "value": {"type": "number", "description": "parameter value"} | ||
| }, | ||
| "required": ["name"] | ||
| } | ||
| } | ||
| } | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_parameter", | ||
| "description": "Get a vehicle parameter's value. The full list of available parameters and their values is available using the get_all_parameters function", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "name": {"type": "string", "description": "parameter name (e.g. ARMING_CHECK, LOG_BITMASK). Regex expressions are supported"}, | ||
| "value": {"type": "number", "description": "parameter value"} | ||
| }, | ||
| "required": ["name"] | ||
| } | ||
| } | ||
| } |
28 changes: 14 additions & 14 deletions
28
MAVProxy/modules/mavproxy_chat/assistant_setup/get_parameter_description.json
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 |
|---|---|---|
| @@ -1,14 +1,14 @@ | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_parameter_description", | ||
| "description": "Get vehicle parameter descriptions including description, units, min and max", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "name": {"type": "string", "description": "parameter name (e.g. ARMING_CHECK, LOG_BITMASK). Regex expressions are supported. set to * to get all parameter descriptions"} | ||
| }, | ||
| "required": ["name"] | ||
| } | ||
| } | ||
| } | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_parameter_description", | ||
| "description": "Get vehicle parameter descriptions including description, units, min and max", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "name": {"type": "string", "description": "parameter name (e.g. ARMING_CHECK, LOG_BITMASK). Regex expressions are supported. set to * to get all parameter descriptions"} | ||
| }, | ||
| "required": ["name"] | ||
| } | ||
| } | ||
| } |
36 changes: 18 additions & 18 deletions
36
MAVProxy/modules/mavproxy_chat/assistant_setup/get_vehicle_location_and_yaw.json
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 |
|---|---|---|
| @@ -1,18 +1,18 @@ | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_vehicle_location_and_yaw", | ||
| "description": "Get the vehicle's current location including latitude, longitude, altitude above sea level and altitude above home", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "latitude": {"type": "number", "description": "latitude in degrees"}, | ||
| "longitude": {"type": "number", "description": "longitude in degrees"}, | ||
| "altitude_amsl": {"type": "number", "description": "altitude above sea level in meters (aka AMSL)"}, | ||
| "altitude_above_home": {"type": "number", "description": "altitude above home in meters"}, | ||
| "yaw": {"type": "number", "description": "vehicle yaw (aka heading) in degrees"} | ||
| }, | ||
| "required": [] | ||
| } | ||
| } | ||
| } | ||
| { | ||
| "type": "function", | ||
| "function": { | ||
| "name": "get_vehicle_location_and_yaw", | ||
| "description": "Get the vehicle's current location including latitude, longitude, altitude above sea level and altitude above home", | ||
| "parameters": { | ||
| "type": "object", | ||
| "properties": { | ||
| "latitude": {"type": "number", "description": "latitude in degrees"}, | ||
| "longitude": {"type": "number", "description": "longitude in degrees"}, | ||
| "altitude_amsl": {"type": "number", "description": "altitude above sea level in meters (aka AMSL)"}, | ||
| "altitude_above_home": {"type": "number", "description": "altitude above home in meters"}, | ||
| "yaw": {"type": "number", "description": "vehicle yaw (aka heading) in degrees"} | ||
| }, | ||
| "required": [] | ||
| } | ||
| } | ||
| } |
Oops, something went wrong.