Comments (4)
Hi, actually the prob_correction
function contains two strategies: (1) Use the likelihood ratio test (Line 344-348); (2) Use the probabilistic label correction (Line 350-355).
Depending on the confidence level, prob_correction
function will automatically choose which strategy to adopt. You can consider this function as a combination of two strategies. Also please note that our PLC framework is general, and any label correction algorithm can be incorporated into it. Thus, here, in the prob_correction
function we show two examples of label correction strategies.
Finally, for the probabilistic label correction strategy, it works as follows. For a given sample, we update its label according to the predicted posterior distribution. More specifically, we randomly sample a new label according to this posterior distribution, and then assign it to this sample.
from plc.
Hi, pxiangwu. Thanks for your detailed answer. I still have a question about the probabilistic label correction strategy. Will it introduce new noise when adopting the random way based on the predicted posterior distribution? I want to apply this method to semantic segmentaion, so I am doubt this will introduce new noise. Besides, I notice that in the code you released, only in the train_clothing_1M
, you chose the prob_correction
, while for the datasets (CIFAR and food101), you simply used the lrt_correction
. Can we safely replace these settings to prob_correction
? Thank you very much.
from plc.
Hi, for the probabilistic label correction strategy, empirically it achieves better performance in certain situations.
However, please note that, after one iteration, this strategy may introduce new label noise. But it can be proved that this strategy is able to converge and correct the labels eventually (under our iterative label refinement framework). Therefore, prob_correction
can also be applied to semantic segmentation. But I am not sure if it would achieve much better performance than the likelihood ratio test for such a task.
In train_clothing_1M
, we found that prob_correction
achieved better performance than lrt_correction
. As a result, we finally chose this strategy for clothing1M. However, for CIFAR and food101, we found that both strategies achieved almost similar performances. Therefore we adopted lrt_correction
for these datasets. Also, to demonstrate several examples of our PLC framework, we preserved lrt_correction
for CIFAR and food101, and did not replace it with prob_correction
in our code.
from plc.
Thanks for your reply. I got it.
from plc.
Related Issues (5)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from plc.