CUDA

The Github issue tracker URL in error messages should be updated to use issue templates

Originally posted by @esc in numba/numba#7223 (comment)

It would be great to have FBeta, F2, or F0.5 metrics to be implemented without the need for a custom metric class defined by user.

catboost version: 0.26

The depth configuration defined on this line:

https://github.com/intel-isl/Open3D/blob/master/examples/python/reconstruction_system/sensors/realsense_recorder.py#L114

is not compatible with the RealSense L515 camera. The following exception is raised:

Traceback (most recent call last):
  File "./examples/python/reconstruction_system/sensors/realsense_recorder.py", line 126, in <m

Describe the bug
Clipping a DataFrame or Series using ints causes a cudf Failure because it won't handle the different dtypes (int and float)

Steps/Code to reproduce bug

data = cudf.Series([-0.43, 0.1234, 1.5, -1.31])
data.clip(0, 1)

...
  File "cudf/_lib/replace.pyx", line 216, in cudf._lib.replace.clip
  File "cudf/_lib/replace.pyx", line 198, in cudf._lib.replace.clamp

Current implementation of join can be improved by performing the operation in a single call to the backend kernel instead of multiple calls.

This is a fairly easy kernel and may be a good issue for someone getting to know CUDA/ArrayFire internals. Ping me if you want additional info.

First of all, great library!

I am having some confusion in understanding the role of values_first2 in set_difference_by_key as mentioned here.

In general terms, the result of set difference D = A - B will not contain values from B therefore values_first2 can never be part of D. So `val

请问可以直接training tmfile出来吗? 因为tengine-convert-tool covert 会有error

tengine-lite library version: 1.4-dev
Get input tensor failed

或是有例子能training出下面tmfile 呢?
![Screenshot from 2021-05-27 07-01-46](https://user-images.githubusercontent.com/40915044/11

Report needed documentation

Report needed documentation
While the estimator guide offers a great breakdown of how to use many of the tools in api_context_managers.py, it would be helpful to have information right in the docstring during development to more easily understand what is actually going on in each of the provided functions/classes/methods. This is particularly important for

In python, you can write python -c 'print(42)' to start an interpreter on the input. Similarly, it would be nice to be able to write futhark run -c 'iota 42' or echo "iota 42" | futhark run - to run the interpreter on some simple input.