Occasional seg faults in RMA
1
0
Entering edit mode
Crispin Miller ★ 1.1k
@crispin-miller-264
Last seen 10.2 years ago
Hi, Has anyone else experienced segmentation faults in rma()? We're still using R-1.7.1 and haven't upgraded bioconductor to 1.3 yet. It appears to be happening during the 'Calculating Expression' phase, and seems to be intermittent (I haven't been able to identify a pattern). We have written our own package with some C routines in, and I'm calling rma() after loading that package, but before calling any of these C functions (which seem to work fine anyway). Am I right to assume that this is not likely to be the source of the problem? Any adivce would be most welcome! Thanks, Crispin Crispin Miller Bioinformatics Group Leader, The Paterson Institute For Cancer Research +44 161 446 3176 -------------------------------------------------------- This email is confidential and intended solely for the use o...{{dropped}}
Cancer Cancer • 977 views
ADD COMMENT
0
Entering edit mode
@matloob-qureshi-507
Last seen 10.2 years ago
Hi Crispin, I've had the occasional segmentation fault using the rma() function too. Our rather simplistic solution was to switch to using espresso for the time being. It does run significantly more slowly than rma but it works ok for our purposes. eset <- expresso(data, bgcorrect.method="rma", normalize.method="constant", pmcorrect.method="pmonly", summary.method="avgdiff") Hope this is useful. Matloob On Fri, 31 Oct 2003, Crispin Miller wrote: > Hi, > Has anyone else experienced segmentation faults in rma()? We're still > using R-1.7.1 and haven't upgraded bioconductor to 1.3 yet. > It appears to be happening during the 'Calculating Expression' phase, > and seems to be intermittent (I haven't been able to identify a > pattern). > > We have written our own package with some C routines in, and I'm calling > rma() after loading that package, but before calling any of these C > functions (which seem to work fine anyway). > Am I right to assume that this is not likely to be the source of the > problem? > > Any adivce would be most welcome! > > Thanks, > Crispin > > > > > > Crispin Miller > Bioinformatics Group Leader, > The Paterson Institute For Cancer Research > +44 161 446 3176 > > -------------------------------------------------------- > > > This email is confidential and intended solely for the use o...{{dropped}} > > _______________________________________________ > Bioconductor mailing list > Bioconductor@stat.math.ethz.ch > https://www.stat.math.ethz.ch/mailman/listinfo/bioconductor >
ADD COMMENT
0
Entering edit mode
The correct expresso call for RMA is eset <- expresso(data, bgcorrect.method="rma", normalize.method="quantiles", pmcorrect.method="pmonly", summary.method="medianpolish") On Fri, 2003-10-31 at 07:53, Matloob Qureshi wrote: > Hi Crispin, > I've had the occasional segmentation fault using the rma() function > too. Our rather simplistic solution was to switch to using espresso for the > time being. It does run significantly more slowly than rma but it works ok > for our purposes. > > eset <- expresso(data, bgcorrect.method="rma", > normalize.method="constant", pmcorrect.method="pmonly", > summary.method="avgdiff") > > Hope this is useful. > > Matloob
ADD REPLY

Login before adding your answer.

Traffic: 852 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