Git Product home page Git Product logo

plc's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

plc's Issues

Is this repo consistent with PLC method?(ICLR2021)

The Code uses "lrt_correction"(LRT, ICLR2020) by default.
And the "prob_correction" seems not match PLC, it considers "cur_prob_distri[y_noise[i]]/top_probs[-1]", and no "f(x_i)-1/2,"t>=m","theta=1/2-T" can be found.

tabular data/ noisy instances/ new datasets

Hi,
thanks for sharing your implementation. I have some questions about it:

  1. Does it also work on tabular data?
  2. Is the code tailored to the datasets used in the paper or can one apply it to any data?
  3. Is it possible to identify the noisy instances (return the noisy IDs or the clean set)?

Thanks!

Probability correction function does not seem to be correct

In the probability correction algorithm, the generated labels should be multinoimally distributed among all the aviable labels. However according to the code given, it will just be 0 or 1

The issue come because the code

PLC/utils.py

Lines 336 to 341 in 8c2bcfd

for i in range(f_x.shape[0]):
cur_prob_distri = f_x[i]
cur_prob_distri = softmax(cur_prob_distri)
top_k_idx = np.argsort(cur_prob_distri)[-1:]
top_probs = cur_prob_distri[top_k_idx]

will result in a scalar top_probs. Hence the code to generate new labels

PLC/utils.py

Lines 349 to 353 in 8c2bcfd

else:
top_probs = top_probs / np.sum(top_probs) # normalization
flipped = flipper.multinomial(1, top_probs, 1)[0]
new_label = np.where(flipped == 1)[0]
new_label = top_k_idx[new_label[0]] # new_label shape [1, ]
will result in new_label being just 0 or 1.

Moreover the normalization here

PLC/utils.py

Line 350 in 8c2bcfd

top_probs = top_probs / np.sum(top_probs) # normalization
will result in top_probs always being 1.0 thereby invalidating the whole idea of sampling from distribution.

Is this intended behavior?

Question about the PLC correction

Hello, pxiangwu. You did a great work in the PLC correction. I am confused when reading the "prob_correction“ function in the utils.py file (line 343-355). You mentioned that " If the predicted confidence exceeds this threshold, we use label correction based on likelihood ratio test. Otherwise, we use probabilistic label correction.“ But the 351 th line "flipped = flipper.multinomial(1, top_probs, 1)[0]" seems to generate a random value. Do the lines 350-355 correspond to the PLC corrrection? By the way, when the prediction has a lower confidence than the confidence threshold, its label must be changed using the codes (350-355) ? I am sorry if I understand wrongly. Thank you for your time.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.