* changed the namespace of randomization tools to experimental
* moved randomization UI code to experimental namespace
* updated docs to emphasize that the randomization tools are experimental
* updated changelog
- Removed native sampling (through jobs) capability from all samplers and parameters as no users have so far needed this, and it introduces additional complexity to the code
- Removed native sampling from the newly introduced AnimationCurveSampler.
- Removed the sampler initialization and cleanup functions based on feedback.
- Modified all randomization tests to not use native sampling
- Removed native sampling related sections from docs
* addressed feedback
- new test for keypoint labeler
- added ClearMaterialProperties method to IGroundTruthGenerator
- Other fixes
* docs clarification
* Update CHANGELOG.md
* added missing interface method implementation for HDRP
* Amending dataset schema to describe correct coordinate system (#255)
The summary for the 3d bounding box states the coordinates are from the sensor's reference frame, but the string for the translational component says it's global. I *think* this is just a typo in the doc, so correcting the description to match the summary for this type of entry.
* Adding supported version badges (#256)
* Cloud rendering support (#227)
* Adding support for cloud rendering in the run simulation window
* minor fixes
* minor update
* Update BoundingBox3DLabeler.cs
* Update BoundingBox3DLabeler.cs
* inner mesh scaling and disabled renderes
* A fix that prevents normal sampler returning values outsi...
- shouldCheckValidRange field excluded from JSON serialization. If the limits block is provided, it means range should be checked.
- added some checking and error messages for the cases where the user tries to provide or change the valid range for a scalar from the json config. this is not supported.
Additional scenario configs:
- Ability to add valid ranges for all samplers (except for animation curve sampler)
- Ability to add valid range to non sampler numeric scalars through the [Range] attribute
- A new compile definition symbol for exposing the valid ranges of samplers in the scenario UI
- Ability to enable or disable a randomizer through the app-param (for this to work, the already existing enabled property is serialized and deserialized. Code was added to treat properties the same as fields during (de)serialization to achieve this)
- New flag in randomizers to denote whether their enabled state can be switched by the user on datamaker. This is purely used on datamaker.
Steven Leal
GitHub
Jon Hogins
Mohsen Kamalzadeh
Steven Borkman
Wesley Mareovich Smith
You-Cyuan Jhang
GitHub Enterprise