Can Genotype Call (GTC) files be used as input for GenomeStudio?
Last updated
Last updated
© 2023 Illumina, Inc. All rights reserved. All trademarks are the property of Illumina, Inc. or their respective owners. Trademark information: illumina.com/company/legal.html. Privacy policy: illumina.com/company/legal/privacy.html
When using GTC files instead of intensity data (IDAT) files as input for creating a GenomeStudio workspace, a sample sheet must be used.
Create a project sample sheet if one is not already available. For reference, see Sample sheet guidelines for GenomeStudio.
Proceed to GenomeStudio project creation. During project creation in GenomeStudio v2.0.5:
Select "Use sample sheet to load sample intensities" in Project Wizard then select Next.
· GTC files cannot be used as input when the "Load sample intensities by selecting directories with intensity files" option is selected.
Browse to the .csv sample sheet.
Browse to the data repository folder where the .gtc files are saved.
· When the data repository/source folder contains both .idat and .gtc files, GenomeStudio will preferentially load the .gtc files.
· Ideally, save .gtc and .idat files in separate folders.
Browse to the manifest repository (folder where the .bpm manifest is located).
· To prevent discrepancies in the genotype calls, make sure that this .bpm manifest is the same .bpm manifest used to generate the GTC files. 5. Select Next.
If a cluster file is available, check the box next to "Import cluster positions from a cluster file" and browse to the .egt cluster file.
· To prevent discrepancies, make sure that this .egt cluster file is the same .egt cluster file used to generate the GTC files.
Select Finish.
Note: Genotype Call (GTC) files can be generated for genotyping arrays, but not for methylation array data. Methylation array data is analyzed using GenomeStudio v2011.1.
Additional resources:
· Sample sheet guidelines for GenomeStudio
· Which files are required and optional when creating a GenomeStudio project?
For any feedback or questions regarding this article (Illumina Knowledge Article #5917), contact Illumina Technical Support techsupport@illumina.com.