Categories
News

RumiCar Simulator v11.1.0 released

We have released RumiCar Simulator v11.1.0. The release notes below are also available on GitHub.


v11.1.0

Calls to the learning API (RC_*) with a different number of arguments from the real-car libraries now stop with a runtime error with a line number, and an outdated description of the second argument of RC_steer in the system guide was corrected (Stage BP; the driving physics is untouched — driving on the shipped courses and the result of the shipped official sample race are unchanged; the official sample race’s verifyHash e9f1da0b and the frozen hashes f0–f3 are the same as before, and only the resultSha256 of the result file was re-pinned because it includes the version (engineVer)). Your program may behave differently — the following calls, which ran with only a warning in v11.0.0, are now errors. (1) Number of arguments — a call with too few or too many arguments, such as RC_steer(), RC_drive(FORWARD), RC_read(), RC_setup(1) or RC_steer(LEFT, 100, 1), stops a C++ or Python program with a runtime error with a line number, “RC_drive() takes 2 argument(s) (1 given)”. The accepted numbers are the same as in the real libraries (the declarations of Arduino RumiCar-lib v0.6.0 and the defs of RasPi RumiCar.py 0.6.0): RC_setup 0, RC_steer 1-2, RC_drive 2, RC_read 1, the optional RC_wheel_speed 1, Python’s RC_params 0 and RC_state 1 (the import RumiCar → RumiCar.RC_drive(...) form too). In the real libraries Python raises a TypeError and Arduino fails to compile; up to v11.0.0 the simulator counted a missing argument as 0, warned and kept running (a program that would not run on the real car ran in the simulator). A C++ error appears when that line runs (the real Arduino stops at compile time, so a mistake in a branch that never runs is not found in the simulator). JavaScript programs still count a missing argument as 0 and warn. The handling of a value that is not a number (a string that is not digits, None, a list: 0 with a warning the first time) is unchanged. (2) Corrected explanation — the system guide’s “Program API (learning side)” still said “the second argument of RC_steer works only when the proportional steering servo (optional equipment) is fitted; without it the call returns 0″ (the behaviour up to v10.5.0). It now describes the behaviour since v11.0.0 (the strength 0-255 on the default car too; leaving it out is the same as 255, 0 is the same as CENTER, CENTER ignores it) and mentions the argument-count error. “Handling of arguments” in §12 of the physics model explanation (ja/en) was corrected the same way. (3) Verification — this removes the difference left by the check of the four RumiCar environments (Arduino RumiCar-lib v0.6.0, RasPi RumiCar.py 0.6.0, RumiCar-Zero2Cam 0.5.0 and this simulator): the handling of missing arguments. Section F was added to the verification gate wf_bo1_steer (18 wrong argument counts in C++ and Python are errors, correct counts are not, JavaScript is unchanged); the permanent gates stay at 82. Unchanged: the driving physics, the ranging, the values and warnings of RC_* with the correct number of arguments, the behaviour of JavaScript programs, the deterministic engine of official races (🏁), the saved-data formats, and the tabletop courses.


Verifying this release yourself

git clone https://github.com/RumiCar-group/RumiCar-Simulator.git
cd RumiCar-Simulator
node wf_run_all.mjs        # the full assertion-gate suite

The suite runs from a fresh clone with no dependencies beyond Node.js.
The real-browser checks under browser/ additionally need npm install and a display.

How this site is built (v1.6.0)

Some components are open source:

Enjoyed the machinery? The main event is our autonomous-driving simulator — it runs in your browser.
Try the simulator → / GitHub →