[aroma.affymetrix] Re: how to find out genome build version for the annotation files

Hi, the aroma.affymetrix annotation files have an "na"-tag indication the NetAffx release/version, e.g. Mapping250K_Nsp,na26,HB20080915.ugp >From this we know that data from the Affymetrix NetAffx release 26 was used. From there you have to go to the NetAffx Analysis Center to find out what

[aroma.affymetrix] how to find out genome build version for the annotation files

Hi, I am analyzing affy500K and affy100K dataset. I want to find out a way to find out which genome build (hg16, hg17 or hg18) the annotation files are based on. Any idea? Thanks, Yupu --~--~-~--~~~---~--~~ When reporting problems on aroma.affymetrix, make su

[aroma.affymetrix] Re: aroma.affymetrix and HTHGU133A microarrays

Hi Jen. I have used aroma.affymetrix on HT_HG-U133_Plus_PM arrays previously without issues. I'll take a quick stab and if that doesn't work, we'll have to investigate further. Usually when the numbers in the ChipEffectSet are all zero, it means that the files were created, but the fits w

[aroma.affymetrix] cbs_error_in_250k_sty_cn_analysis_

Hi All I am analyzing 250k sty samples (only) (paired: healthy Vs tumor). No. of samples around 72 (36 each, paired). I am following the tutorial posted on http://groups.google.com/group/aroma-affymetrix/web/paired-total-copy-number-analysis. Till identification of copy-number regions in tumor-n