Error in limma : maimages (cannot open the connection)
1
0
Entering edit mode
naving2uk • 0
@naving2uk-7663
Last seen 8.9 years ago
United Kingdom

am trying to read and normalize an Agilent dataset but i have this error :

Error in file(file, "r") : cannot open the connection, and aslo when i tried this code to check the files :

targets$FileName[!file.exists(targets$FileName)]

 

its works with out problem

 

I used targets$FileName the out put all the file name  with information in targets file ?

no problem , and i specify the path : x <-read.maimages(targets$FileName,path="C:\Users\navin\Desktop\Ad2",source="agilent.median"); but i have this error :

Error: '\U' used without hex digits in character string starting ""C:\U"   :( 

I used targets$FileName the out put is all the file name  with information in targets file ?

no problem , and i specify the path : 

x <-read.maimages(targets$FileName,path="C:\Users\navin\Desktop\Ad2",source="agilent.median"); but i have this error :

Error: '\U' used without hex digits in character string starting ""C:\U"   :( 

 

limma • 1.3k views
ADD COMMENT
0
Entering edit mode

What code did you use that gave the error message "cannot open the connection"?

None of the code you give in your post could have given that error.

ADD REPLY
0
Entering edit mode
@sean-davis-490
Last seen 12 weeks ago
United States

To answer your first question: "cannot open connection" usually means that the file is not accessible or does not exist.

To answer your second question, the path separators in R are always "/" and not "\", so you'll want to make that change.

 

ADD COMMENT
0
Entering edit mode

Thank you for your reply Sean , but the files are exist and i wrote down if you realize my post : 

I used targets$FileName to check the files existence so its work , all the file come out , iam using RStudio  do i need to  put the path ? 

ADD REPLY

Login before adding your answer.

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