Biobase typo in example of AnnotatedDataFrame man page
1
0
Entering edit mode
James F. Reid ▴ 610
@james-f-reid-3148
Last seen 9.6 years ago
Dear BioC, answering to a recent query on the mailing list I noticed a small typo in the example provided in the AnnotatedDataFrame help page: AnnotatedDataFrame(data=df, varMetaData=metaData) should be AnnotatedDataFrame(data=df, varMetadata=metaData) also, no error is given when calling directly AnnotatedDataFrame (the varMetadata slot is empty) but calling new('AnnotatedDataFrame') produces an error where 'varMetaData' is not a valid slot name. Best. J.
• 693 views
ADD COMMENT
0
Entering edit mode
@martin-morgan-1513
Last seen 5 days ago
United States
On 03/02/2012 03:42 AM, James F. Reid wrote: > Dear BioC, > > answering to a recent query on the mailing list I noticed a small typo > in the example provided in the AnnotatedDataFrame help page: > > AnnotatedDataFrame(data=df, varMetaData=metaData) > should be > AnnotatedDataFrame(data=df, varMetadata=metaData) Thanks for the typo... > > also, no error is given when calling directly AnnotatedDataFrame (the > varMetadata slot is empty) but calling new('AnnotatedDataFrame') > produces an error where 'varMetaData' is not a valid slot name. I think what you mean is that AnnotatedDataFrame(varMetaData=data.frame()) doesn't result in an error. but should. These are both fixed in the devel branch, Biobase 2.15.4. Thanks! Martin > > Best. > J. > > _______________________________________________ > Bioconductor mailing list > Bioconductor at r-project.org > https://stat.ethz.ch/mailman/listinfo/bioconductor > Search the archives: > http://news.gmane.org/gmane.science.biology.informatics.conductor -- Computational Biology Fred Hutchinson Cancer Research Center 1100 Fairview Ave. N. PO Box 19024 Seattle, WA 98109 Location: M1-B861 Telephone: 206 667-2793
ADD COMMENT

Login before adding your answer.

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