Mirror
/
ardupilot
mirror of https://github.com/ArduPilot/ardupilot
5
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
46,603 Commits 71 Branches 508 Tags 635 MiB
Commit Graph

60 Commits

Author SHA1 Message Date
Peter Barker fdb31a6419 autotest: param_parse.py: validate @User field to be Standard or Avanced 2020-09-22 14:56:04 +10:00
Peter Barker 9e148f245b autotest: param_parse.py: correct parsing of Values fields 
the regex used to parse the values field later is rather strict - no
spaces allowed around the : for example.

Canonicalise the string before trying to do anything more with it
(including validation)
 2020-09-15 11:09:52 +10:00
Pierre Kancir 4930142b6e Tools: add generator for MP parameter xml 2020-08-05 22:32:33 +10:00
Peter Barker d1170db4bf Tools: allow parameters to be specified on a per-vehicle basis 2020-06-16 11:21:47 +10:00
Peter Barker ffaa60b9ed autotest: stop emitting duplicate rangefinder headings 
This was only an issue for the Wasp rangefinder block, which drops stuff
in at the top level by specifying the same subgroup name as the top
level.
 2020-06-02 09:37:33 +10:00
Peter Barker 691ae58a79 Tools: rename APMrover2 to Rover 2020-04-14 09:50:34 +09:00
Pierre Kancir 5d299eb584 Tools: add error keyword on param parse for newcomers 2020-04-02 08:11:42 +11:00
Rishabh c859287310 Tools: param_metadata: check for duplicate enteries in parameter value field 2020-03-24 10:26:04 +11:00
Peter Barker 4c964dd89f autotest: param_parse.py: allow cr to exist on empty lines in prog_param 
This should fix parameter building on the Windows CI autotest.

We allow empty lines between @Param blocks and the parameter (and, in
fact, require it before multi-entry @GROUPINFOs like vectors).

The regex wasn't taking into account Windows will have \r\n on that empty
line rather than just \n
 2020-03-06 15:40:25 +11:00
Peter Barker a9f3f9af40 autotest: attempt to fix param-parse crlf issue 2020-03-01 20:50:56 +11:00
Peter Barker 293692cc24 autotest: strip whitespace from parameter attribute values 
Attempt to fix \r\n issue on Azure cygwin tests
 2020-02-21 19:51:15 +11:00
Peter Barker c4d282f05b autotest: param_parse.py: whitespace-only line is param block delimiter 
Several parameters were missing from the documentation because there was
a line with just trailing whitespace immediately after a parameter
metadata block.

Be more lenient.
 2020-02-19 15:09:16 +11:00
Peter Barker 5d5f9b77e8 autotest: include AP_Vehicle parameters in documenation 2020-02-13 21:31:20 +11:00
Patrick José Pereira 4518e2b8f2 Tools: Add JSONEmit in param_parse 
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
 2020-01-21 10:00:33 +11:00
Andrew Tridgell 4b8972433a Tools: fixed handling of bitmask in param metdata 
this prevents ARMING_CHECK from getting invalid values for the bitmask
 2019-07-01 19:22:03 +10:00
Pierre Kancir 1101cc05e6 Tools: param_parse: update OptionParser to ArgumentParser 2019-04-02 19:57:13 +11:00
Michael du Breuil bb7abc2935 Tools: Allow specifying parameter metadata format 
Also removes unneeded passing of a file pointer
 2018-12-11 10:24:40 +11:00
Michael du Breuil 681d8416e2 Tools: Add an EDN parameter emitter 2018-12-11 10:24:40 +11:00
Pierre Kancir 4f35992049 Tools: make param_parse.py error more explicit 
Signed-off-by: Pierre Kancir <pierre.kancir@azurdrones.com>
 2018-10-10 11:22:45 +11:00
Peter Barker 27657bfd40 Tools: param_metadata: flake8 compliance 2018-10-08 14:56:24 +11:00
Hamish Willee 329b972845 Tools: param_metadata: Add parser code to include uniq ref from path 2018-10-08 14:56:09 +11:00
Peter Barker 7772279785 Tools: param_parse.py - fix vehicle-specific values 2018-08-06 12:27:56 +10:00
Peter Barker 8fdcd7e1f5 Tools: hide parameter in documentation if no values present 2018-07-17 12:08:27 +10:00
Pierre Kancir 6c43ab27c1 Tools: remove trailling semilocons 2018-07-12 21:13:02 +10:00
Peter Barker 338af9e142 Tools: correct misleading comment on per-vehicle parameter descriptions 2018-03-21 21:05:42 +11:00
Peter Barker 5ac5a68d17 Tools: param_parse.py: replace @PREFIX in values with library prefix 2018-03-14 15:44:00 +11:00
Peter Barker 0b4dcdde35 Tools: param_parse.py: allow whitespace between vehicles 
Also add sanity check that the vehicles you're limitting to we know
about
 2017-12-16 11:08:35 +11:00
Peter Barker d1128e7be4 Tools: param_parse.py: replace comments with debug statements 2017-12-16 11:08:35 +11:00
Peter Barker eeb15d7fd5 Tools: param_parse.py: make comment consistent 2017-12-16 11:08:35 +11:00
Peter Barker 825832be93 Tools: param_parse.py: add a map for vehicle name to a true-name to be used in code 
Where true-name is something like "Rover" and the normal name remains
the directory name (e.g. "APMrover2")
 2017-12-16 11:08:35 +11:00
Peter Barker e0125a68e7 Tools: param_parse.py: use single regex for params everywhere 2017-12-16 11:08:35 +11:00
Peter Barker a45ab6b84c Tools: param_parse.py: correct example comment 2017-12-16 11:08:35 +11:00
Peter Barker ea2c156c7f Tools: param_parse.py: understand tagging of parameters for specific vehicles 2017-12-16 11:08:35 +11:00
Francisco Ferreira eda5d9265f
Tools: add new no-emit option to param_parse.py so that only validation is done 2017-07-18 14:15:39 +01:00
Jacob Walser b752594fe5 param_metadata: Markdown parameter formatter 2017-06-20 14:53:17 +10:00
Dr.-Ing. Amilcar Do Carmo Lucas d7c7deacdf Tools: Follow SI units conventions 
http://physics.nist.gov/cuu/Units/units.html
http://physics.nist.gov/cuu/Units/outside.html
and
http://physics.nist.gov/cuu/Units/checklist.html
http://www.bipm.org/en/publications/si-brochure/
http://www1.bipm.org/en/CGPM/db/3/2/   g_n unit for G-force
one further constrain is that only printable (7bit) ASCII characters are allowed

Add a validation so that Travis can validate the units
Use full text unit information when generating .wiki, .rst and .html documentation
Use both unit symbol and unit full text when generating .xml
 2017-05-17 18:07:25 +10:00
Andrew Tridgell 496ed18530 autotest: sort libraries by name 2017-02-07 10:37:24 +11:00
Andrew Tridgell de59f27e14 autotest: fixed parameter generation for recursive libraries 2017-02-06 15:12:32 +11:00
Pierre Kancir bec09b9a57 autotest: python3 support 2016-11-09 11:48:22 -03:00
Pierre Kancir 9e1ffcae5d Tools: update python coding style 
Tools: update PrintVersion.py coding style

autotest: update python coding style

pysim: update python coding style

jsb_sim: update Python coding style

param_metadata: update Python coding style
 2016-09-01 13:05:11 +10:00
Peter Barker a8e9fc19b0 Tools: allow param parser to emit ReStructured Text 2016-03-17 16:10:11 +11:00
Don Gagne 07c0c6d519 autotest: Validate Range meta data for correctness 2015-12-27 16:10:43 +11:00
Andrew Tridgell b6ed86465b autotest: prioritise .cpp projects over .pde projects 2015-05-30 15:21:25 +09:00
Andrew Tridgell dfc7878b14 autotest: fixed cpp files for parameter parsing 2015-05-21 11:42:32 +10:00
Aaron Curtis 068febda1f Tools: Fix broken duplicate check for adding new libraries to the data structure 2014-06-28 13:17:45 +10:00
Andrew Tridgell 4f33e4e114 autotest: fixed handling for wiki and xml generation 2013-09-12 10:01:30 +10:00
Andrew Tridgell bfd61fec15 param_metadata: support .pde files for parameter autodocs 2013-09-12 09:51:59 +10:00
Andrew Tridgell d510f8f722 autotest: added generation of Parameters.html for wordpress 
this generates APM docs for wordpress
 2013-05-27 08:25:24 +10:00
Andrew Tridgell 5818dce3d2 param_metadata: fixed parameter parsing for multi-parameter objects 
also adds more error checking
 2013-05-21 17:02:13 +10:00
Kevin Hester 9885cc7ed1 Docs: Add XML emit to param_parse.py. See below for more details... 
I've refactored the param_parse tool to use various 'emitters'.  An emitter
can take parameter info and output it in a particular format.  Currently the
only supported emitters are the wiki and XML formats.

The goal of these changes is to create a standard machine readable description
of parameters - mainly for use by ground control stations, but it will also
enable spiffy scripting environments where code can refer symbolically to
vehicle parameters (reflectionish).

Open issue: Is there any sort of Ardupilot build id which can be included in
the generated XML?  That would ensure that we select the correct paramdefs
for the load on the target (possibly by asking the target for a SHA or
somesuch).  If that issue is resolved, then the filename for the XML
file should probably be something like:
arduplane-ca5742ac.pdef.xml.

It is worth noting that I've proposed a suffix of ".pdef.xml" for these file
types.  This facilitates automated file handling on Android devices.  On
Android you can register 'handlers' for particular file extensions and if
the user tries to open that extension in email or a web browser your app
will be given a chance to do something about it.  The 'outer' xml extension
will allow naive editors to know that at least this is an xml file.

I will include a sample of the XML format with the pull-request for this CL.
 2013-03-10 17:47:42 +11:00