`renderObjectImage` slows the `step` function dramatically - can it be its own action?
See original GitHub issueFrom quick timings on a few machines, step
with movement actions takes .1 to .15 seconds when renderObjectImage=False
. This time per step jumps up to .8-.9 seconds with renderObjectImage=True
. In some applications, we don’t need the object segmentation mask at every timestep. Would it be possible to make renderObjectImage
an action instead, such that we can take a step to render and get the object segmentation frame (a slow step), but have the rest of the steps not bothering generating it so that the simulator runs faster?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Using a Step Functions API action to continue a new ...
To start workflow executions from a Task state. Open the Step Functions console and choose Create state machine ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is now fixed with 1a2bdf51801e72bcc39366d6af00fb801cc5b2ec and 1a2bdf51801e72bcc39366d6af00fb801cc5b2ec
Hey Jesse, this is supported, but not currently documented, with: