MAplot: Binning grid too coarse for current (small) bandwidth
0
0
Entering edit mode
neverstop • 0
@neverstop-7227
Last seen 7.9 years ago

I have 49 samples. I need to compare different normalizations applied to Affymetrix data. A way to do that is by using the function MAplot. The problem is that I get some warnings I don't understand:
> MAplot(Data, plot.method="smoothScatter",cex=0.5,cex.main=0.5)


Attaching package: ‘hgu133plus2cdf’

The following objects are masked from ‘package:hgu133acdf’:

    i2xy, xy2i

Warning messages:
1: In KernSmooth::bkde2D(x, bandwidth = bandwidth, gridsize = nbin,  :
  Binning grid too coarse for current (small) bandwidth: consider increasing 'gridsize'
2: In KernSmooth::bkde2D(x, bandwidth = bandwidth, gridsize = nbin,  :
  Binning grid too coarse for current (small) bandwidth: consider increasing 'gridsize'
3: In KernSmooth::bkde2D(x, bandwidth = bandwidth, gridsize = nbin,  :
  Binning grid too coarse for current (small) bandwidth: consider increasing 'gridsize'
4: In KernSmooth::bkde2D(x, bandwidth = bandwidth, gridsize = nbin,  :
  Binning grid too coarse for current (small) bandwidth: consider increasing 'gridsize'
5: In KernSmooth::bkde2D(x, bandwidth = bandwidth, gridsize = nbin,  :
  Binning grid too coarse for current (small) bandwidth: consider increasing 'gridsize'
6: In KernSmooth::bkde2D(x, bandwidth = bandwidth, gridsize = nbin,  :
  Binning grid too coarse for current (small) bandwidth: consider increasing 'gridsize'
7: In KernSmooth::bkde2D(x, bandwidth = bandwidth, gridsize = nbin,  :
  Binning grid too coarse for current (small) bandwidth: consider increasing 'gridsize'
8: In KernSmooth::bkde2D(x, bandwidth = bandwidth, gridsize = nbin,  :
  Binning grid too coarse for current (small) bandwidth: consider increasing 'gridsize'

 

Thank you.


affy affymetrix affymetrics affymetrixchip • 2.2k views
ADD COMMENT

Login before adding your answer.

Traffic: 448 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6