Oh, thank you!  I thought I had solved the CDF problem when I figured out
that this package requires a copy of the CDF file to be in the working
directory, because the CDF-specific error messages went away.

I can now get it to find my cdf file but still doesn't like it, but I will
go away and Google some more and try to figure it out.

Thanks again for getting me on the right track!
Mikki

On Tue, Jul 12, 2011 at 12:21 PM, Harris A. Jaffee <hj@jhu.edu> wrote:

> On Jul 12, 2011, at 11:59 AM, M Behnke wrote:
>
>> debug: cdfFile <- findCdf(chipType)
>> Browse[2]>
>> debug: unitNames <- readCdfUnitNames(cdfFile)
>> Browse[2]>
>> Error in dirname(filename) : a character vector argument expected
>>
>
> Yes, it's useful!  Apparently, cdfFile was NULL, as in this orchestrated
> failure?
>
>        > readCdfUnitNames(NULL)
>
>        Error in dirname(filename) : a character vector argument expected
>
> The problem seems to be with the value of findCdf() rather than your
> pathname variable.
> I think you need to specify something non-NULL for the 'cdf' argument to
> updateCelUnits,
> or else incorporate it into the 'data' argument -- or maybe the optional
> arguments:
>
>     cdf: A (optional) CDF 'list' structure either with field 'indices'
>          or fields 'x' and 'y'.  If 'NULL', the unit names (and from
>          there the cell indices) are inferred from the names of the
>          elements in 'data'.
>
>    data: A 'list' structure in a format similar to what is returned by
>          'readCelUnits'() for _a single CEL file only_.
>
>     ...: Optional arguments passed to 'readCdfCellIndices'(), which is
>          called if 'cdf' is not given.
>
>
>
>

	[[alternative HTML version deleted]]

