The shortcuts are now working perfectly. Thanks!
On Mon, Dec 8, 2008 at 10:51 PM, Henrik Bengtsson <[EMAIL PROTECTED]>wrote:
>
> The updated affxparser is now available on BioC. Let me know if this
> solves your latest problem. /Henrik
>
> On Fri, Dec 5, 2008 at 2:36 AM, Henrik Bengtsson <[EMAI
The updated affxparser is now available on BioC. Let me know if this
solves your latest problem. /Henrik
On Fri, Dec 5, 2008 at 2:36 AM, Henrik Bengtsson <[EMAIL PROTECTED]> wrote:
> Hi again,
>
> I take that patch back - it won't help you. Instead I went to the
> source and fixed affxparser.
Hi again,
I take that patch back - it won't help you. Instead I went to the
source and fixed affxparser. I've committed a bug fix to BioConductor
- both to the release (now v1.14.1) and the developers versions
(v1.15.1). You'll have to wait for the next BioC build cycle which
should happen wit
Hi,
wow this turns out to be a never ending story ;) So, this time it is
actually a problem with the affxparser package and the Affymetrix
Fusion SDK library it uses.
If you look at the output of print(cdf) or getChipType(cdf) you'll
find that the chip type reported is wrong - it contains a ful
And again! The change you made seems to be doing something odd with
how the directories are created when you start processing the data:
So my working directory is "G:\BGC_EXPERIMENTS\MAQC_Analysis\" and I
have shortcuts to both rawData and annotationData. When I ran the
RMABackground correction i
Sorry, just one more follow up on the shortcuts. Is it correct that
they will only work for the top level directories, e.g. a shortcut to
"rawData" or "annotationData" in the working directory? I tried to
place a shortcut within rawData and it did not work. I also tried to
use shortcuts to the act
Hi Henrik,
It worked!!! Thanks so much for working through it with me - I really
appreciate it. I was a little frustrated with the aroma.affymetrix
directory requirements at first, but with doing a little more reading
and the shortcuts, I can see its actually a very clever way of keeping
things o
Hi,
On Wed, Dec 3, 2008 at 6:36 AM, pwhiteusa <[EMAIL PROTECTED]> wrote:
>
> Sorry I missed the 0 and -1 at the edge of the screen. See below, but
> basically when the mode was set to 1 (executable), it returned the
> error (-1), the other modes all returned a 0.
thanks. Then it wasn't what I t
Sorry I missed the 0 and -1 at the edge of the screen. See below, but
basically when the mode was set to 1 (executable), it returned the
error (-1), the other modes all returned a 0.
On Dec 2, 4:22 pm, "Henrik Bengtsson" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> thanks. Almost there. Unfortunately,
Hi,
thanks. Almost there. Unfortunately, you left out the one answer I
was most interest in; see below.
On Tue, Dec 2, 2008 at 12:34 PM, pwhiteusa <[EMAIL PROTECTED]> wrote:
>
> Hi Henrik,
>
> The results are interspersed below:
>
> On Nov 26, 4:27 pm, "Henrik Bengtsson" <[EMAIL PROTECTED]> wr
Hi Henrik,
The results are interspersed below:
On Nov 26, 4:27 pm, "Henrik Bengtsson" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> so this is a bit confusing. I've been trying to reproduce it myself
> over a local Windows network, but I cannot. I did however locate a
> potential problem where R incorr
Hi,
so this is a bit confusing. I've been trying to reproduce it myself
over a local Windows network, but I cannot. I did however locate a
potential problem where R incorrectly believes it does not have the
permission to read the file, which might be what you are experience.
Could you please t
12 matches
Mail list logo