gpu

🐛 Bug

--- Logging error ---
Traceback (most recent call last):
  File "/scratch/rzou/pt/workspace-env/lib/python3.7/logging/__init__.py", line 1025, in emit
    msg = self.format(record)
  File "/scratch/rzou/pt/workspace-env/lib/python3.7/logging/__init__.py", line 869, in format
    return fmt.format(record)
  File "/scratch/rzou/pt/workspace-env/lib/python3.7/site-packages/_pytes

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.

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?)

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

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

For feature engineering tasks, I'd like to be able to determine whether a datetime is the beginning or end of a year, like I can in pandas.

import pandas as pd
​
s = pd.Series(["2021-02-27", "2020-03-31"], dtype="datetime64[ms]")
s.dt.is_year_end
0    False
1    False
dtype: bool

import pandas as pd
​
s = pd.Series(["2021-01-01", "2020-04-01"], dtype="datet

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.

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