David Wendt

> Can we file a follow-up issue (or update this PR) for the other radix sort function to align these two definitions? This one is using `storage type is integral`...

@gpucibot merge

Sorry, there is no workaround for this. Scientific notation is used for numbers less then 0.0001 or greater than 1,000,000.

Ah. That is a good idea. Can we close this then?

The WSL2 requirements are listed here: https://docs.nvidia.com/cuda/wsl-user-guide/index.html#known-limitations-for-linux-cuda-apps The RAPIDS requirements are documented here: https://rapids.ai/start.html#requirements From https://github.com/rapidsai/cudf/issues/9427#issuecomment-975902493 it looks like we may need to update the requirements page specifically for WSL2...

Closing this as resolved. Feel free to reopen if there is new information.

The `make docs_cudf` works for me. What error are you seeing? Also, if you are using `ninja` instead of `make` then it would be `ninja docs_cudf`.

I looked into this a bit and was not able to find CUPTI calls occurring when the `--profile` flag is used. Analysis started here: https://github.com/NVIDIA/nvbench/blob/2ce4e425eeaf7453ee10ead99f6408d41c733813/nvbench/option_parser.cu#L427-L430 Where the `--profile` flag is...

These are all wrapped by a single `is_cupti_required()` call https://github.com/NVIDIA/nvbench/blob/2ce4e425eeaf7453ee10ead99f6408d41c733813/nvbench/state.cuh#L217-L226 which is checked in the here: https://github.com/NVIDIA/nvbench/blob/2ce4e425eeaf7453ee10ead99f6408d41c733813/nvbench/detail/state_exec.cuh#L125-L127 only if `run_once` is not enabled. And `run_once` is enabled when `--profile` is...

> Hm, it could be simply even linking with `cupti` could cause the incompatibility with GPU metric collection in Nsight. There is an `NVBENCH_HAS_CUPTI` compile flag so I could try...