gpu

Motivation

Currently lots of C++ based unit tests are executed directly from test.sh/win-test.sh for example:
https://github.com/pytorch/pytorch/blob/0bd8d0951dcb4063c0f7552a7404bd7f0e7b6e6f/.jenkins/pytorch/test.sh#L317

Which have following drawbacks:

• It excluded those test runtime from auto-sharding/auto-categorization
• Make them subject of running on only particular platform (

The current Field APIs, including ScalarField, MatrixField, and Structfield (after #2627) use assertions statements to check input validity, for example,

https://github.com/taichi-dev/taichi/blob/03e2923d103704048c101051d337fa31f9dbb1de/python/taichi/lang/matrix.py#L207

In software engineering practice, assertion is used to verify whether the program itself is implemented correctly regardles

At this moment relu_layer op doesn't allow threshold configuration, and legacy RELU op allows that.
We should add configuration option to relu_layer.

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

Hi ,

I have tried out both loss.backward() and model_engine.backward(loss) for my code. There are several subtle differences that I have observed , for one retain_graph = True does not work for model_engine.backward(loss) . This is creating a problem since buffers are not being retained every time I run the code for some reason.

Please look into this if you could.

the .pcd file format allows for fields to be extended. this means it can neatly hold data about the label or object of a point. this can be very handy for ML tasks. However, the open3d file io does not appear to be able to read other fields other than the xyz, rgb, normals etc . I haven't been able to find where in the open3d structure the code for the file io pcd loading is implemented to att

Our users are often confused by the output from programs such as zip2john sometimes being very large (multi-gigabyte). Maybe we should identify and enhance these programs to output a message to stderr to explain to users that it's normal for the output to be very large - maybe always or maybe only when the output size is above a threshold (e.g., 1 million bytes?)

I want to preemptively start this thread to survey for suggestions. A cursory search lead me to this promising repository https://github.com/enigo-rs/enigo

Since closing the window is a common point of failure, that will be the focus for the first pass of testing as I learn how to use the library.

Components for testing:

• bridge
• editor
• renderer
• settings
• wind

https://github.com/brendangregg/FlameGraph

Is your feature request related to a problem? Please describe.

The row_equality_comparator constructor currently accepts a bool to indicate if nulls are considered equal or not. In libcudf, we prefer to use scoped enums instead of bools and we already have a [`

Describe the Problem

plot_model currently has the save argument which can be used to save the plots. It does not provide the functionality to decide where to save the plot and with what name. Right now it saves the plot with predefined names in the current working directory.

Describe the solution you'd like

We can have another argument save_path which is used whenever the `

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.