[devel]→[master] Preparation of v1.3.0
#361
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Otherwise the environment does not source the setup.sh script of Ignition
Bump Ignition distribution to Edifice
* Vendor Physics system gazebosim/gz-sim@1924de9 * Custom Physics features * Disable using Ignition Dome in CI/CD * Enable Physics system profiling * Use upstream components to reset the base velocity * Fix updating the GUI state with paused run
Address sdformat11 deprecations
Simplify passing the physics parameters to the `Server`
Align empty world with upstream
…ics_engines Prepare multiple physics engines support
…ction Improve how links with no collision elements are handled in contact detection
…ritance Move inheritance from `ModelWithFile` to `ICubGazeboABC`
Suppress stack trace stderr by redirecting to null
Allow inserting worlds from file containing models
Disable joint velocity limits in the manipulation example
Allow specifying different pos and rot weights for POSE IK targets
…plication Application of external wrenches: new `empty` method and new Python test
Bump Ignition distribution to Fortress
* Vendor Physics system gazebosim/gz-sim@4c35f6c * Custom Physics features * Revert upstream PR 690 It causes a performance regression when contacts are involved
Minor cleanup
|
Waiting only for the Still in the TODO list before merging:
|
Check for a compatible Ignition distribution in the system when importing the `scenario` Python package
…ization Fix positivity option of model randomizations
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Edit: see update on renaming in #361 (comment).
While I'd like to bring Edifice support to the Stable channel, I'm still unsure how to deal the temporary
scenar-ioname in PyPI introduced in #346. The renaming is currently blocked and is tracked in #359.What I propose is the following. Move forward with the existing status and document in the release notes:
scenar-iothat this is a temporary name and it will change in one of the next minor releases.gym-ignitionas they are already (sincescenar-iois new). Read next point for more details.gym-ignitionare not affected by this change and should not perform any action. Also, users should not notice any difference. In fact, the newgym-ignition>=1.3.0depends onscenar-ioand this new package will be installed automatically. Furthermore, the future renaming of Claim thescenarioname in PyPI and update the project #359 should not affect these users since the renamedscenariopackage will replacescenar-ioand will be installed similarly asgym-ignition>=1.X.0dependency.What do you think @traversaro?
There are few features I'd like to try finalizing before the release:
setup.pytosetup.cfgMove content fromsetup.pytosetup.cfg#355Add support to bullet physics engine Add support to bullet physics engine #340 (needs a ign-physics release)cmake-build-extensionto deal with Splitscenarioandgym-ignitionPython packages #346