Skip to content

Commit dd41bc2

Browse files
committed
IMPROVEMENT: SPDX tags and codacy lint fixes
1 parent d10464d commit dd41bc2

24 files changed

+183
-72
lines changed

ARCHITECTURE.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,9 @@
11
# Software architecture
2+
<!--
3+
SPDX-FileCopyrightText: 2024 Amilcar do Carmo Lucas <[email protected]>
4+
5+
SPDX-License-Identifier: GPL-3.0-or-later
6+
-->
27

38
Before we decided on a software architecture or programming language or toolkit we gathered software requirements as presented below.
49

BLOG-discuss1.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,9 @@
11
![Cinewhoop Diatone Taycan MX-C|586x500](upload://naJEdzmLeF8hvzupJCpLBT7tZay.jpeg)
2+
<!--
3+
SPDX-FileCopyrightText: 2024 Amilcar do Carmo Lucas <[email protected]>
4+
5+
SPDX-License-Identifier: GPL-3.0-or-later
6+
-->
27

38
For illustrative purposes, we will use the small 3'' multicopter depicted above, but the tuning sequence we developed at [IAV GmbH](https://www.iav.com/) will work on almost any other multicopter.
49

BLOG-discuss2.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,9 @@
11
Continuation from the Blog post above....
2+
<!--
3+
SPDX-FileCopyrightText: 2024 Amilcar do Carmo Lucas <[email protected]>
4+
5+
SPDX-License-Identifier: GPL-3.0-or-later
6+
-->
27

38
For better accuracy, you should do that for all directions and take the average. In our case, we got:
49

BLOG.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,9 @@
1-
# How to methodically tune (almost) any multicopter using ArduCopter 4.4.x
1+
# How to methodically tune any ArduCopter
2+
<!--
3+
SPDX-FileCopyrightText: 2024 Amilcar do Carmo Lucas <[email protected]>
4+
5+
SPDX-License-Identifier: GPL-3.0-or-later
6+
-->
27

38
![Cinewhoop Diatone Taycan MX-C](cinewhoop.png)
49

CODE_OF_CONDUCT.md

Lines changed: 40 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
ArduPilot Methodic Configurator Developer Code of Conduct
22
=========================================================
3+
<!--
4+
SPDX-FileCopyrightText: 2024 Amilcar do Carmo Lucas <[email protected]>
5+
6+
SPDX-License-Identifier: GPL-3.0-or-later
7+
-->
38

49
Rev 1.0 Apr 3nd 2024
510

@@ -24,51 +29,51 @@ Our Pledge
2429
In the interest of fostering an open and welcoming environment, we as
2530
developers and maintainers pledge to:
2631

27-
- Endeavour to make participation in our project and our community a
28-
harassment-free experience for everyone, regardless of age, body
29-
size, disability, ethnicity, gender identity and expression, level
30-
of experience, nationality, personal appearance, race, religion, or
31-
sexual identity and orientation.
32-
- Endeavour to understand the intent of development activities they
33-
undertake, where there may be reason to think that the vehicle may
34-
be used as a weapon or in an application where it is effectively in
35-
control of human life.
36-
- Not knowingly support or facilitate the weaponization of systems
37-
using Ardupilot or ArduPilot Methodic Configurator
38-
- ArduPilot and ArduPilot Methodic Configurator are NOT certified for
39-
use in applications where ArduPilot is effectively in control of human
40-
lives. Members of the development team must not knowingly assist in
41-
projects where ArduPilot will be in control of human lives.
42-
“In control of human lives” includes but isn’t limited to manned
43-
aircraft.
32+
- Endeavor to make participation in our project and our community a
33+
harassment-free experience for everyone, regardless of age, body
34+
size, disability, ethnicity, gender identity and expression, level
35+
of experience, nationality, personal appearance, race, religion, or
36+
sexual identity and orientation.
37+
- Endeavor to understand the intent of development activities they
38+
undertake, where there may be reason to think that the vehicle may
39+
be used as a weapon or in an application where it is effectively in
40+
control of human life.
41+
- Not knowingly support or facilitate the weaponization of systems
42+
using ArduPilot or ArduPilot Methodic Configurator
43+
- ArduPilot and ArduPilot Methodic Configurator are NOT certified for
44+
use in applications where ArduPilot is effectively in control of human
45+
lives. Members of the development team must not knowingly assist in
46+
projects where ArduPilot will be in control of human lives.
47+
“In control of human lives” includes but isn’t limited to manned
48+
aircraft.
4449

4550
Our Standards
4651
-------------
4752

4853
Examples of behavior that contributes to achieving the aims of ArduPilot
4954
Methodic Configurator include:
5055

51-
- Using welcoming and inclusive language
52-
- Being respectful of differing viewpoints and experiences
53-
- Gracefully accepting constructive criticism
54-
- Focusing on what is best for the community
55-
- Showing empathy towards other community members
56+
- Using welcoming and inclusive language
57+
- Being respectful of differing viewpoints and experiences
58+
- Gracefully accepting constructive criticism
59+
- Focusing on what is best for the community
60+
- Showing empathy towards other community members
5661

5762
Examples of unacceptable behavior by contributors include:
5863

59-
- The use of sexualized language or imagery and unwelcome sexual
60-
attention or advances
61-
- Trolling, insulting/derogatory comments, and personal or political
62-
attacks
63-
- Public or private harassment
64-
- Publishing others’ private information, such as a physical or
65-
electronic address, without explicit permission
66-
- Modifying ArduPilot Methodic Configurator code to intentionally support
67-
weaponization
68-
- Knowingly designing, testing or using weaponized systems running
69-
ArduPilot Methodic Configurator
70-
- Other conduct which could reasonably be considered inappropriate in
71-
a public or professional setting
64+
- The use of sexualized language or imagery and unwelcome sexual
65+
attention or advances
66+
- Trolling, insulting/derogatory comments, and personal or political
67+
attacks
68+
- Public or private harassment
69+
- Publishing others’ private information, such as a physical or
70+
electronic address, without explicit permission
71+
- Modifying ArduPilot Methodic Configurator code to intentionally support
72+
weaponization
73+
- Knowingly designing, testing or using weaponized systems running
74+
ArduPilot Methodic Configurator
75+
- Other conduct which could reasonably be considered inappropriate in
76+
a public or professional setting
7277

7378
Our Responsibilities
7479
--------------------

CONTRIBUTING.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,9 @@
11
# Contributing
2+
<!--
3+
SPDX-FileCopyrightText: 2024 Amilcar do Carmo Lucas <[email protected]>
4+
5+
SPDX-License-Identifier: GPL-3.0-or-later
6+
-->
27

38
## How to contribute to the ArduPilot Methodic Configurator project?
49

LICENSE.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
GNU GENERAL PUBLIC LICENSE
22
Version 3, 29 June 2007
3+
<!--
4+
SPDX-FileCopyrightText: 2024 Amilcar do Carmo Lucas <[email protected]>
5+
6+
SPDX-License-Identifier: GPL-3.0-or-later
7+
-->
38

49
Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
510
Everyone is permitted to copy and distribute verbatim copies

MANIFEST.in

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,6 @@
1+
# SPDX-FileCopyrightText: 2024 Amilcar do Carmo Lucas <[email protected]>
2+
#
3+
# SPDX-License-Identifier: GPL-3.0-or-later
14
recursive-include MethodicConfigurator/vehicle_templates *.param
25
recursive-include MethodicConfigurator/vehicle_templates *.json
36
recursive-include MethodicConfigurator/vehicle_templates *.jpg

MethodicConfigurator/extract_param_defaults.py

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -206,6 +206,7 @@ def output_params(params: Dict[str, float], format_type: str = 'missionplanner',
206206
elif format_type == "qgcs":
207207
print(f"{sysid} {compid} {param_name:<15} {param_value:.6f} {MAV_PARAM_TYPE_REAL32}")
208208

209+
209210
def main():
210211
args = parse_arguments()
211212
parameter_values = extract_parameter_values(args.bin_file, args.type)

MethodicConfigurator/frontend_tkinter_template_overview.py

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -117,6 +117,7 @@ def on_row_double_click(self, event):
117117
ProgramSettings.store_template_dir(selected_template_relative_path)
118118
self.root.destroy()
119119

120+
120121
def argument_parser():
121122
"""
122123
Parses command-line arguments for the script.
@@ -134,6 +135,7 @@ def argument_parser():
134135
'providing a clear and intuitive interface for parameter management.')
135136
return add_common_arguments_and_parse(parser)
136137

138+
137139
def main():
138140
args = argument_parser()
139141

@@ -143,5 +145,6 @@ def main():
143145

144146
print(ProgramSettings.get_recently_used_dirs()[0])
145147

148+
146149
if __name__ == "__main__":
147150
main()

0 commit comments

Comments
 (0)