paeg1aprobe
1
0
Entering edit mode
Lana Schaffer ★ 1.3k
@lana-schaffer-1056
Last seen 10.1 years ago
Hi, I am trying to install the paeg1acdf and probe files from the Meta data site on to my windows platform. paeg1 P. aeruginosa Source,Win32 Source, Win32 The paeg1acdf was installed properly but the paeg1aprobe could not be installed. First of all the probe directory is called "paeruginosaprobe" and can be installed with that name. However, Bioconductor looks for the name "paeg1aprobe" when installing with gcrma, for instance. >>Error in getProbePackage(probepackagename) : >> Environment paeg1aprobe was not found in the Bioconductor repository. This message comes when the directory name is changed to 'paeg1aprobe' before install: >>Error in library(pkg, character.only = TRUE) : >> There is no package called 'paeg1aprobe' (I could try changing the name after install?) Can someone suggest something to help me get the probe file installed? Lana [[alternative HTML version deleted]]
cdf probe gcrma cdf probe gcrma • 635 views
ADD COMMENT
0
Entering edit mode
Seth Falcon ★ 7.4k
@seth-falcon-992
Last seen 10.1 years ago
Hi Lana, > The paeg1acdf was installed properly but the paeg1aprobe could not be > installed. First of all the probe > directory is called "paeruginosaprobe" and can be installed with that > name. However, Bioconductor looks > for the name "paeg1aprobe" when installing with gcrma, for instance. One thing you could try is to manually download the probe package you want. You should be able to do this by sending your browser to the following URL: http://www.bioconductor.org/data/probes/Packages/ paeruginosaprobe_1.0.zip Then in the R Windows GUI there is a menu option to install a package from a local zip file. I'm not sure why you are getting the error messages you posted, but perhaps this provides a work-around for the time being. + seth
ADD COMMENT

Login before adding your answer.

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