Eric Shi
Eric Shi
Hi @jinz2014, thanks for the suggestion. I'll update you when we have added this feature.
With Warp 1.5.0, the `wp.launch()` function now accepts a `block_dim` argument to specify the number of threads per block: https://nvidia.github.io/warp/modules/runtime.html#warp.launch
This issue should be fixed with the 1.3.2 release: https://github.com/NVIDIA/warp/releases
Hi @Irene-123, thanks for volunteering! I think @daedalus5 might already be working on this issue. The other two you expressed an interest in should be open for you to take...
> That's great, thank you @shi-eric Is there a discord channel to have a discussion? Yes, there is a channel for Warp in the Omniverse Discord server ([link](https://discord.com/invite/nvidiaomniverse))
af57ae5 should contain a fix for the issue and will be included in the next Warp release at the beginning of February.
Warp 1.6.0 is now out, so I'm making this issue as resolved.
Hi @fajar7xx, we have no experience with this distribution. Could you please provide some error messages that illustrate what you're seeing? For example, can you provide: - Output of `nvidia-smi`...
A quick look at the issue shows that the type annotations get turned into strings with `from __future__ import annotations` ([postponed evaluation of annotations](https://peps.python.org/pep-0563/)), which interferes with the Warp `Var.type`...
Sorry we weren't able to address this issue before removing `warp.sim` from the codebase. As of Warp v1.10, the `warp.sim` module has been removed. It was deprecated back in v1.8...