Skip to content

Commit 1b716ea

Browse files
rmackay9peterbarker
rmackay9
authored and
peterbarker
committed
chat: assistant files use unix line endings
1 parent 8976169 commit 1b716ea

24 files changed

+697
-697
lines changed

‎MAVProxy/modules/mavproxy_chat/assistant_setup/assistant_instructions.txt‎

Lines changed: 54 additions & 54 deletions
Large diffs are not rendered by default.

‎MAVProxy/modules/mavproxy_chat/assistant_setup/copter_flightmodes.txt‎

Lines changed: 29 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,29 @@
1-
This file holds the Copter flight mode name to number mapping
2-
3-
STABILIZE = 0, // pilot directly controls the airframe angle with roll, pitch and yaw stick inputs. Pilot directly controls throttle
4-
ACRO = 1, // pilot directly controls the body-frame angular rate. pilot directly controls throttle
5-
ALT_HOLD = 2, // pilot directly controls the vehicle roll, pitch and yaw angles. Pilot's throttle control controls climb rate
6-
AUTO = 3, // fully automatic waypoint control using mission commands
7-
GUIDED = 4, // fully automatic fly to coordinate or fly at velocity/direction using mavlink commands.
8-
LOITER = 5, // pilot controls the vehicle's 3D speed and acceleration with roll, pitch and throttle input. Heading is controlled with the yaw stick
9-
RTL = 6, // automatic return to launching point
10-
CIRCLE = 7, // automatic circular flight with automatic throttle
11-
LAND = 9, // automatic landing with horizontal position control
12-
DRIFT = 11, // semi-autonomous position, yaw and throttle control. rarely used.
13-
SPORT = 13, // manual earth-frame angular rate control with manual throttle. very rarely used
14-
FLIP = 14, // automatically flip the vehicle 360 degrees
15-
AUTOTUNE = 15, // automatically tune the vehicle's roll and pitch gains
16-
POSHOLD = 16, // automatic position hold with manual override, with automatic throttle. very similar to Loiter mode
17-
BRAKE = 17, // full-brake using inertial/GPS system, no pilot input
18-
THROW = 18, // throw to launch mode using inertial/GPS system, no pilot input
19-
AVOID_ADSB = 19, // automatic avoidance of manned vehicle. very rarely used
20-
GUIDED_NOGPS = 20, // guided mode but only accepts attitude and altitude commands
21-
SMART_RTL = 21, // SMART_RTL returns vehicle home by retracing its steps
22-
FLOWHOLD = 22, // FLOWHOLD holds position with optical flow without rangefinder. similar to Loiter. very rarely used
23-
FOLLOW = 23, // follow attempts to follow another vehicle or ground station
24-
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.
25-
SYSTEMID = 25, // System ID mode produces automated system identification signals in the controllers. very rarely used
26-
AUTOROTATE = 26, // Autonomous autorotation. Used only for traditional helicopters
27-
AUTO_RTL = 27, // return to launch but using an Auto mission starting from the DO_LAND_START command
28-
TURTLE = 28, // Flip vehicle to recover after crash
29-
1+
This file holds the Copter flight mode name to number mapping
2+
3+
STABILIZE = 0, // pilot directly controls the airframe angle with roll, pitch and yaw stick inputs. Pilot directly controls throttle
4+
ACRO = 1, // pilot directly controls the body-frame angular rate. pilot directly controls throttle
5+
ALT_HOLD = 2, // pilot directly controls the vehicle roll, pitch and yaw angles. Pilot's throttle control controls climb rate
6+
AUTO = 3, // fully automatic waypoint control using mission commands
7+
GUIDED = 4, // fully automatic fly to coordinate or fly at velocity/direction using mavlink commands.
8+
LOITER = 5, // pilot controls the vehicle's 3D speed and acceleration with roll, pitch and throttle input. Heading is controlled with the yaw stick
9+
RTL = 6, // automatic return to launching point
10+
CIRCLE = 7, // automatic circular flight with automatic throttle
11+
LAND = 9, // automatic landing with horizontal position control
12+
DRIFT = 11, // semi-autonomous position, yaw and throttle control. rarely used.
13+
SPORT = 13, // manual earth-frame angular rate control with manual throttle. very rarely used
14+
FLIP = 14, // automatically flip the vehicle 360 degrees
15+
AUTOTUNE = 15, // automatically tune the vehicle's roll and pitch gains
16+
POSHOLD = 16, // automatic position hold with manual override, with automatic throttle. very similar to Loiter mode
17+
BRAKE = 17, // full-brake using inertial/GPS system, no pilot input
18+
THROW = 18, // throw to launch mode using inertial/GPS system, no pilot input
19+
AVOID_ADSB = 19, // automatic avoidance of manned vehicle. very rarely used
20+
GUIDED_NOGPS = 20, // guided mode but only accepts attitude and altitude commands
21+
SMART_RTL = 21, // SMART_RTL returns vehicle home by retracing its steps
22+
FLOWHOLD = 22, // FLOWHOLD holds position with optical flow without rangefinder. similar to Loiter. very rarely used
23+
FOLLOW = 23, // follow attempts to follow another vehicle or ground station
24+
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.
25+
SYSTEMID = 25, // System ID mode produces automated system identification signals in the controllers. very rarely used
26+
AUTOROTATE = 26, // Autonomous autorotation. Used only for traditional helicopters
27+
AUTO_RTL = 27, // return to launch but using an Auto mission starting from the DO_LAND_START command
28+
TURTLE = 28, // Flip vehicle to recover after crash
29+

‎MAVProxy/modules/mavproxy_chat/assistant_setup/delete_wakeup_timers.json‎

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
1-
{
2-
"type": "function",
3-
"function": {
4-
"name": "delete_wakeup_timers",
5-
"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.",
6-
"parameters": {
7-
"type": "object",
8-
"properties": {
9-
"message": {"type": "string", "description": "wakeup message of timers to be deleted. regex values are accepted."}
10-
},
11-
"required": []
12-
}
13-
}
14-
}
1+
{
2+
"type": "function",
3+
"function": {
4+
"name": "delete_wakeup_timers",
5+
"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.",
6+
"parameters": {
7+
"type": "object",
8+
"properties": {
9+
"message": {"type": "string", "description": "wakeup message of timers to be deleted. regex values are accepted."}
10+
},
11+
"required": []
12+
}
13+
}
14+
}

‎MAVProxy/modules/mavproxy_chat/assistant_setup/get_all_parameters.json‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
1-
{
2-
"type": "function",
3-
"function": {
4-
"name": "get_all_parameters",
5-
"description": "Get all available parameter names and values",
6-
"parameters": {
7-
"type": "object",
8-
"properties": {},
9-
"required": []
10-
}
11-
}
12-
}
1+
{
2+
"type": "function",
3+
"function": {
4+
"name": "get_all_parameters",
5+
"description": "Get all available parameter names and values",
6+
"parameters": {
7+
"type": "object",
8+
"properties": {},
9+
"required": []
10+
}
11+
}
12+
}

‎MAVProxy/modules/mavproxy_chat/assistant_setup/get_available_mavlink_messages.json‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
1-
{
2-
"type": "function",
3-
"function": {
4-
"name": "get_available_mavlink_messages",
5-
"description": "Get a list of mavlink message names that can be retrieved using the get_mavlink_message function",
6-
"parameters": {
7-
"type": "object",
8-
"properties": {},
9-
"required": []
10-
}
11-
}
12-
}
1+
{
2+
"type": "function",
3+
"function": {
4+
"name": "get_available_mavlink_messages",
5+
"description": "Get a list of mavlink message names that can be retrieved using the get_mavlink_message function",
6+
"parameters": {
7+
"type": "object",
8+
"properties": {},
9+
"required": []
10+
}
11+
}
12+
}

‎MAVProxy/modules/mavproxy_chat/assistant_setup/get_current_datetime.json‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
1-
{
2-
"type": "function",
3-
"function": {
4-
"name": "get_current_datetime",
5-
"description": "Get the current date and time, e.g. 'Saturday, June 24, 2023 6:14:14 PM'",
6-
"parameters": {
7-
"type": "object",
8-
"properties": {},
9-
"required": []
10-
}
11-
}
1+
{
2+
"type": "function",
3+
"function": {
4+
"name": "get_current_datetime",
5+
"description": "Get the current date and time, e.g. 'Saturday, June 24, 2023 6:14:14 PM'",
6+
"parameters": {
7+
"type": "object",
8+
"properties": {},
9+
"required": []
10+
}
11+
}
1212
}

‎MAVProxy/modules/mavproxy_chat/assistant_setup/get_location_plus_dist_at_bearing.json‎

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
1-
{
2-
"type": "function",
3-
"function": {
4-
"name": "get_location_plus_dist_at_bearing",
5-
"description": "Calculate the latitude and longitude given an existing latitude and longitude and a distance in meters and a bearing in degrees",
6-
"parameters": {
7-
"type": "object",
8-
"properties": {
9-
"latitude": {"type": "number", "description": "latitude in degrees"},
10-
"longitude": {"type": "number", "description": "longitude in degrees"},
11-
"distance": {"type": "number", "description": "distance to move meters"},
12-
"bearing": {"type": "number", "description": "bearing in degrees. 0 is North, 90 is East, etc"}
13-
},
14-
"required": ["latitude", "longitude", "distance", "bearing"]
15-
}
16-
}
17-
}
1+
{
2+
"type": "function",
3+
"function": {
4+
"name": "get_location_plus_dist_at_bearing",
5+
"description": "Calculate the latitude and longitude given an existing latitude and longitude and a distance in meters and a bearing in degrees",
6+
"parameters": {
7+
"type": "object",
8+
"properties": {
9+
"latitude": {"type": "number", "description": "latitude in degrees"},
10+
"longitude": {"type": "number", "description": "longitude in degrees"},
11+
"distance": {"type": "number", "description": "distance to move meters"},
12+
"bearing": {"type": "number", "description": "bearing in degrees. 0 is North, 90 is East, etc"}
13+
},
14+
"required": ["latitude", "longitude", "distance", "bearing"]
15+
}
16+
}
17+
}

‎MAVProxy/modules/mavproxy_chat/assistant_setup/get_location_plus_offset.json‎

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
1-
{
2-
"type": "function",
3-
"function": {
4-
"name": "get_location_plus_offset",
5-
"description": "Calculate the latitude and longitude given an existing latitude and longitude and distances (in meters) North and East",
6-
"parameters": {
7-
"type": "object",
8-
"properties": {
9-
"latitude": {"type": "number", "description": "latitude in degrees"},
10-
"longitude": {"type": "number", "description": "longitude in degrees"},
11-
"distance_north": {"type": "number", "description": "distance to move North in meters"},
12-
"distance_east": {"type": "number", "description": "distance to move East in meters"}
13-
},
14-
"required": ["latitude", "longitude", "distance_north", "distance_east"]
15-
}
16-
}
17-
}
1+
{
2+
"type": "function",
3+
"function": {
4+
"name": "get_location_plus_offset",
5+
"description": "Calculate the latitude and longitude given an existing latitude and longitude and distances (in meters) North and East",
6+
"parameters": {
7+
"type": "object",
8+
"properties": {
9+
"latitude": {"type": "number", "description": "latitude in degrees"},
10+
"longitude": {"type": "number", "description": "longitude in degrees"},
11+
"distance_north": {"type": "number", "description": "distance to move North in meters"},
12+
"distance_east": {"type": "number", "description": "distance to move East in meters"}
13+
},
14+
"required": ["latitude", "longitude", "distance_north", "distance_east"]
15+
}
16+
}
17+
}

‎MAVProxy/modules/mavproxy_chat/assistant_setup/get_mavlink_message.json‎

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
1-
{
2-
"type": "function",
3-
"function": {
4-
"name": "get_mavlink_message",
5-
"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",
6-
"parameters": {
7-
"type": "object",
8-
"properties": {
9-
"message": {"type": "string", "description": "mavlink message name (e.g. HEARTBEAT, VFR_HUD, GLOBAL_POSITION_INT, etc)"}
10-
},
11-
"required": ["message"]
12-
}
13-
}
14-
}
1+
{
2+
"type": "function",
3+
"function": {
4+
"name": "get_mavlink_message",
5+
"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",
6+
"parameters": {
7+
"type": "object",
8+
"properties": {
9+
"message": {"type": "string", "description": "mavlink message name (e.g. HEARTBEAT, VFR_HUD, GLOBAL_POSITION_INT, etc)"}
10+
},
11+
"required": ["message"]
12+
}
13+
}
14+
}

‎MAVProxy/modules/mavproxy_chat/assistant_setup/get_mode_mapping.json‎

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
1-
{
2-
"type": "function",
3-
"function": {
4-
"name": "get_mode_mapping",
5-
"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",
6-
"parameters": {
7-
"type": "object",
8-
"properties": {
9-
"name": {"type": "string", "description": "flight mode name (e.g. Guided, Loiter, RTL)"},
10-
"number": {"type": "number", "description": "flight mode number"}
11-
},
12-
"required": []
13-
}
14-
}
15-
}
1+
{
2+
"type": "function",
3+
"function": {
4+
"name": "get_mode_mapping",
5+
"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",
6+
"parameters": {
7+
"type": "object",
8+
"properties": {
9+
"name": {"type": "string", "description": "flight mode name (e.g. Guided, Loiter, RTL)"},
10+
"number": {"type": "number", "description": "flight mode number"}
11+
},
12+
"required": []
13+
}
14+
}
15+
}

0 commit comments

Comments
 (0)