zr-v4

Commit Graph

Author	SHA1	Message	Date
Peter Barker	691ae58a79	Tools: rename APMrover2 to Rover	5 years ago
Pierre Kancir	5d299eb584	Tools: add error keyword on param parse for newcomers	5 years ago
Rishabh	c859287310	Tools: param_metadata: check for duplicate enteries in parameter value field	5 years ago
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	5 years ago
Peter Barker	a9f3f9af40	autotest: attempt to fix param-parse crlf issue	5 years ago
Peter Barker	293692cc24	autotest: strip whitespace from parameter attribute values Attempt to fix \r\n issue on Azure cygwin tests	5 years ago
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.	5 years ago
Peter Barker	5d5f9b77e8	autotest: include AP_Vehicle parameters in documenation	5 years ago
Patrick José Pereira	4518e2b8f2	Tools: Add JSONEmit in param_parse Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>	5 years ago
Andrew Tridgell	4b8972433a	Tools: fixed handling of bitmask in param metdata this prevents ARMING_CHECK from getting invalid values for the bitmask	6 years ago
Pierre Kancir	1101cc05e6	Tools: param_parse: update OptionParser to ArgumentParser	6 years ago
Michael du Breuil	bb7abc2935	Tools: Allow specifying parameter metadata format Also removes unneeded passing of a file pointer	6 years ago
Michael du Breuil	681d8416e2	Tools: Add an EDN parameter emitter	6 years ago
Pierre Kancir	4f35992049	Tools: make param_parse.py error more explicit Signed-off-by: Pierre Kancir <pierre.kancir@azurdrones.com>	6 years ago
Peter Barker	27657bfd40	Tools: param_metadata: flake8 compliance	6 years ago
Hamish Willee	329b972845	Tools: param_metadata: Add parser code to include uniq ref from path	6 years ago
Peter Barker	7772279785	Tools: param_parse.py - fix vehicle-specific values	7 years ago
Peter Barker	8fdcd7e1f5	Tools: hide parameter in documentation if no values present	7 years ago
Pierre Kancir	6c43ab27c1	Tools: remove trailling semilocons	7 years ago
Peter Barker	338af9e142	Tools: correct misleading comment on per-vehicle parameter descriptions	7 years ago
Peter Barker	5ac5a68d17	Tools: param_parse.py: replace @PREFIX in values with library prefix	7 years ago
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	7 years ago
Peter Barker	d1128e7be4	Tools: param_parse.py: replace comments with debug statements	7 years ago
Peter Barker	eeb15d7fd5	Tools: param_parse.py: make comment consistent	7 years ago
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")	7 years ago
Peter Barker	e0125a68e7	Tools: param_parse.py: use single regex for params everywhere	7 years ago
Peter Barker	a45ab6b84c	Tools: param_parse.py: correct example comment	7 years ago
Peter Barker	ea2c156c7f	Tools: param_parse.py: understand tagging of parameters for specific vehicles	7 years ago
Francisco Ferreira	eda5d9265f	Tools: add new no-emit option to param_parse.py so that only validation is done	8 years ago
Jacob Walser	b752594fe5	param_metadata: Markdown parameter formatter	8 years ago
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	8 years ago
Andrew Tridgell	496ed18530	autotest: sort libraries by name	8 years ago
Andrew Tridgell	de59f27e14	autotest: fixed parameter generation for recursive libraries	8 years ago
Pierre Kancir	bec09b9a57	autotest: python3 support	8 years ago
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	9 years ago
Peter Barker	a8e9fc19b0	Tools: allow param parser to emit ReStructured Text	9 years ago
Don Gagne	07c0c6d519	autotest: Validate Range meta data for correctness	9 years ago
Andrew Tridgell	b6ed86465b	autotest: prioritise .cpp projects over .pde projects	10 years ago
Andrew Tridgell	dfc7878b14	autotest: fixed cpp files for parameter parsing	10 years ago
Aaron Curtis	068febda1f	Tools: Fix broken duplicate check for adding new libraries to the data structure	11 years ago
Andrew Tridgell	4f33e4e114	autotest: fixed handling for wiki and xml generation	12 years ago
Andrew Tridgell	bfd61fec15	param_metadata: support .pde files for parameter autodocs	12 years ago
Andrew Tridgell	d510f8f722	autotest: added generation of Parameters.html for wordpress this generates APM docs for wordpress	12 years ago
Andrew Tridgell	5818dce3d2	param_metadata: fixed parameter parsing for multi-parameter objects also adds more error checking	12 years ago
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.	12 years ago
Andrew Tridgell	58a0cfc0b3	params: fixed ordering of vehicle parsing this keeps it consistent in the wiki	12 years ago
Andrew Tridgell	4683df4a21	params: fixed parsing of value lists with -1 elements	12 years ago
Andreas M. Antonopoulos	c0f8f6251b	param_parser: input validation bug fix	13 years ago
Andreas M. Antonopoulos	de64c05f8e	param_parser: cosmetic Arduplane: doc fixes	13 years ago
Andreas M. Antonopoulos	186a3e4f6a	param_parser - better tolerance for missing parameters	13 years ago

1 2

55 Commits (1f1383ab64396221a53c49f21134340ebea47c67)