Commit 5db4e15
Output attr="false" from PyMJCF when False is explicitly specified.
Before this change, setting any keyword attribute to False meant the attribute wasn't specified at all. This is fine for attributes where the default is false, but wrong for other keyword attributes.
In particular, since commit google-deepmind/mujoco@4bfc2c0, ctrllimited and similar attributes changed their default value from "false" to "auto", breaking some models that specify forcelimited=False and forcerange=something.
Also in this commit: update the ctrllimited and similar attributes' schemas to include the value "auto".
PiperOrigin-RevId: 468699407
Change-Id: I7f64d2e757678a00aec8b1cfa33894ac1b7f5b5b1 parent 3b801da commit 5db4e15
5 files changed
Lines changed: 71 additions & 51 deletions
File tree
- dm_control
- mjcf
- test_assets
- suite/utils
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
184 | 184 | | |
185 | 185 | | |
186 | 186 | | |
187 | | - | |
| 187 | + | |
188 | 188 | | |
189 | 189 | | |
190 | 190 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
252 | 252 | | |
253 | 253 | | |
254 | 254 | | |
| 255 | + | |
| 256 | + | |
| 257 | + | |
| 258 | + | |
| 259 | + | |
| 260 | + | |
| 261 | + | |
| 262 | + | |
| 263 | + | |
| 264 | + | |
| 265 | + | |
| 266 | + | |
| 267 | + | |
| 268 | + | |
| 269 | + | |
| 270 | + | |
| 271 | + | |
| 272 | + | |
| 273 | + | |
255 | 274 | | |
256 | 275 | | |
257 | 276 | | |
| |||
0 commit comments