Tweet
Originally posted by sanwen
View Post
-
I came across the same problem when running R in a linux server. How do you fix it?
-
You can download the R file with some other means (wget, web browser), "cd" to the download directory and source it locally in R with
However, to install Bioconductor packages, you need a working internet connection. Contact your systems administrator and ask him/her to help you set up R with your proxy (you could also try what ioatomis did).Code:source("biocLite.R")Comment
-
Thank U
Yes I've solved it, the problem is due to Web-limitation on that server nodes...but I didn't notice it at first...haha...thank U for your advice, it's really helped
Originally posted by sarvidsson View PostComment
-
Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.07-01-2026, 11:43 AM
-
I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.
Here are nine questions we think about, in roughly the order they matter, before...
Comment