9 | | === Download tQN === |
| 14 | == Exported fields are == |
| 15 | |
| 16 | !ReporterId = BAC clone Id |
| 17 | |
| 18 | !GeneSymbol = Gene symbols of genes mapped to the BAC clone. Could be bundled using: |
| 19 | |
| 20 | Chromosome |
| 21 | |
| 22 | Cytoband |
| 23 | |
| 24 | !StartPosition = Start position in BP for the BAC clone |
| 25 | |
| 26 | !EndPosition = End position in BP for the BAC clone |
| 27 | |
| 28 | M = Log2(ratio) |
| 29 | |
| 30 | Note that the CGH formats do require probes to be exported to have a |
| 31 | genomic mapping. |
| 32 | |
| 33 | |
| 34 | == Formats == |
| 35 | |
| 36 | === Standard Format === |
| 37 | |
| 38 | Format of header line is the above common columns and then the assays |
| 39 | with assay names in the header. |
| 40 | |
| 41 | === Lite Format === |
| 42 | |
| 43 | Format of header line is reporterId, chromosome, start, stop, and then |
| 44 | the assays with assay names in the header. NOTE: This format is |
| 45 | compatible with MeV CGH viewer. |
| 46 | |
| 47 | === Sample Name export === |
| 48 | |
| 49 | Only the sample names are exported into a file. No spot data. |
| 50 | |
| 51 | === Sample Name and annotation export === |
| 52 | |
| 53 | The sample name and a chosen annotation is exported into a file. No |
| 54 | spot data. |
| 55 | |
| 56 | === Annotation statistics === |
| 57 | |
| 58 | By specifying in the appropiate text field below in the format |
| 59 | e.g. `|ER status|brca_family_status|..|` you can get a summary of how |
| 60 | many assays has a certain annotation value for each of the specified |
| 61 | annotation types. |
| 62 | |
| 63 | === BED format === |
| 64 | |
| 65 | This creates a format similar to BED format as defined by UCSC and |
| 66 | Ensembl. Contains four columns; chr, start, stop, amd reporterId. You |
| 67 | can use BED files to create your own tracks in the UCSC genome |
| 68 | browser. |
| 69 | |
| 70 | === Single file Lite === |
| 71 | |
| 72 | This creates one file for each assays. The file name speciefed as a |
| 73 | parameter will be the suffix to the assay name. E.g specifying |
| 74 | myfile.txt will create a file for Ca13928 as Ca13928_myfile.txt .The |
| 75 | format of the individual files are the Lite format (see above). |
| 76 | |
| 77 | === Complete annotations to file === |
| 78 | |
| 79 | The annotations for all assays are printed to a file. Blanks are |
| 80 | filled with NA |
| 81 | |
| 82 | === Selected annotations to file === |
| 83 | |
| 84 | Only selected annotations and their assays are printed to file. Blanks |
| 85 | are filled with NA. |
| 86 | |
| 87 | === Mev + annotations === |
| 88 | |
| 89 | An MeV compatible file is printed containing annotations. This format |
| 90 | is experimental and needs to be completed. |
| 91 | |
| 92 | === Annotation Display dump for selected annotations === |
| 93 | |
| 94 | For annotation display option. Enter selected annotations in the |
| 95 | format: |
| 96 | {{{|ER Status|p_brca_family_status|etc..|}}} |
| 97 | These annotations will be separated and a matrix created with N rows = |
| 98 | N samples and for each annotation value type, a column will be made |
| 99 | with N rows, where each row entry is 1 (annotation value exists for |
| 100 | this assay) or 0, no annotation value. |
| 101 | |
| 102 | == Parameters == |
| 103 | |
| 104 | 1. [Optional] Give a valid full file name for the created file. |
| 105 | |
| 106 | 2. [Optional] Sort the data as well. NOTE! Using the sort option may require you to increase the RAM usage considerably if working with large data sets. |
| 107 | |
| 108 | 3. Select export mode. Either standard or standard_lite as described above, or format suitable for Agilent CGH-analytics software. |
| 109 | |
| 110 | 4. Select annotation for sample name and annotation export |
| 111 | |
| 112 | 5. Define annotation types for annotation statistics in the form `|ERstatus|brca_family_status|...|` |
| 113 | |
| 114 | |
| 115 | == Download and installation == |
| 116 | |
| 117 | There is currently no detailed notes on how to install the plug-in in |
| 118 | BASE 1, please fall back on the BASE 1 documentation on how to install |
| 119 | plug-ins. |
| 120 | |
| 121 | === BASE 2 === |
| 122 | |
| 123 | In BASE 2 this plug-in can be run using the |
| 124 | Base1PluginExecuter. Simply create a configuration for the CGH Data |
| 125 | Dumper following these steps: |
| 126 | |
| 127 | 1. To be written. |
| 128 | |
| 129 | |
| 130 | == License == |
| 131 | |
| 132 | This plug-in is released under the |
| 133 | [http://www.gnu.org/copyleft/gpl.html GNU General Public License]. |