Skip to content

Commit 203d452

Browse files
committed
Fixed tables again...
1 parent b08221e commit 203d452

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

how-to-edit-gwas-and-genomic-prediction-file-formats.html

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ <h1 class="header-title">How-to: Edit GWAS and Genomic Prediction File Formats</
9292
<li>IID = Individual ID</li>
9393
</ul>
9494
<p>In this example, I don't have FIDs so the IID is just repeated for both.</p>
95-
<table>
95+
<table border="1" style="width:100%" align="center">
9696
<thead>
9797
<tr>
9898
<th>FID</th>
@@ -121,7 +121,7 @@ <h1 class="header-title">How-to: Edit GWAS and Genomic Prediction File Formats</
121121
</table>
122122

123123
<p>This is slightly different from the Tassel tab-delimited format for phenotypes:</p>
124-
<table>
124+
<table border="1" style="width:100%" align="center">
125125
<thead>
126126
<tr>
127127
<th>&lt;Trait&gt;</th>
@@ -148,7 +148,7 @@ <h1 class="header-title">How-to: Edit GWAS and Genomic Prediction File Formats</
148148

149149
<p>Tassel will allow you to save a phenotype file into either Tassel or Plink format.</p>
150150
<p>If you're running GAPIT, then the phenotype file is read into an R dataframe. That means that the delimiter used is less important since files can be read with "read.csv" or "read.table". However, you will generally want the file to looks like this:</p>
151-
<table>
151+
<table border="1" style="width:100%" align="center">
152152
<thead>
153153
<tr>
154154
<th>Taxa</th>
@@ -177,7 +177,7 @@ <h1 class="header-title">How-to: Edit GWAS and Genomic Prediction File Formats</
177177
<p>It's also worth noting that while the first 11 HapMap columns are required for GAPIT, only three of them are used ("rs" a.k.a. SNP name, "chrom" and "pos"). So, the other eight columns may be filled with "NA".</p>
178178
<p>Now, let's assume instead that you want to run Plink or GEMMA. GEMMA can use Plink file formats, so let's use that common format. Conversion from VCF to Plink files is easily acheived using Tassel or vcftools. </p>
179179
<p>To begin, Plink requires both a PED (pedigree) and MAP (genetic map) file. Plink PED file format requires all markers be biallelic and the file look like so (header included here for clarity -- not in actual PED file):</p>
180-
<table>
180+
<table border="1" style="width:100%" align="center">
181181
<thead>
182182
<tr>
183183
<th>FamilyID</th>
@@ -218,7 +218,7 @@ <h1 class="header-title">How-to: Edit GWAS and Genomic Prediction File Formats</
218218
</table>
219219

220220
<p>And the Plink MAP file looks like (again, header included for clarity only):</p>
221-
<table>
221+
<table border="1" style="width:100%" align="center">
222222
<thead>
223223
<tr>
224224
<th>chromosome</th>

0 commit comments

Comments
 (0)