DATASET_ARROWS #Arrow datasets are visualized as sets of arrows outside the tree, with an optional backbone line/rectangle behind them #lines starting with a hash are comments and ignored during parsing #=================================================================# # MANDATORY SETTINGS # #=================================================================# #select the separator which is used to delimit the data below (TAB,SPACE or COMMA).This separator must be used throughout this file. #SEPARATOR TAB #SEPARATOR SPACE SEPARATOR COMMA #label is used in the legend table (can be changed later) DATASET_LABEL,label1 #dataset color (can be changed later) COLOR,#ff0000 #=================================================================# # OPTIONAL SETTINGS # #=================================================================# #=================================================================# # all other optional settings can be set or changed later # # in the web interface (under 'Datasets' tab) # #=================================================================# #dataset scale: you can simply set the values where the scale will be drawn #DATASET_SCALE,100,200,1000 #or you can specify value, label, color, width, style and label size factor for each scale line (dash separated, format: VALUE-LABEL-COLOR-WIDTH-DASHED-LABEL_SCALE_FACTOR)) #DATASET_SCALE,100-amino acid 100-#0000ff-5-1-1,200-line at aa200-#ff0000-1-0-2,1000-3rd aa line-#00ff00-5-1-1 #Each dataset can have a legend, which is defined using LEGEND_XXX fields below #For each row in the legend, there should be one shape, color and label. #Optionally, you can define an exact legend position using LEGEND_POSITION_X and LEGEND_POSITION_Y. To use automatic legend positioning, do NOT define these values #Optionally, shape scaling can be present (LEGEND_SHAPE_SCALES). For each shape, you can define a scaling factor between 0 and 1. #To order legend entries horizontally instead of vertically, set LEGEND_HORIZONTAL to 1 #Shape should be a number between 1 and 12, or any protein domain shape definition (RE, HH, HV...). #1: square #2: circle #3: star #4: right pointing triangle #5: left pointing triangle #6: checkmark #7: solid line #8: dashed line #9: dotted line #10:arrow left #11:arrow right #12:bidirectional arrow #LEGEND_TITLE,Dataset legend #LEGEND_SCALE,1 #LEGEND_POSITION_X,100 #LEGEND_POSITION_Y,100 #LEGEND_HORIZONTAL,0 #LEGEND_SHAPES,1,2,3 #LEGEND_COLORS,#ff0000,#00ff00,#0000ff #LEGEND_LABELS,value1,value2,value3 #LEGEND_SHAPE_SCALES,1,1,0.5 #maximum width #WIDTH,1000 #always show internal values; if set, values associated to internal nodes will be displayed even if these nodes are not collapsed. It could cause overlapping in the dataset display. #SHOW_INTERNAL,0 #show dashed lines between leaf labels and the dataset #DASHED_LINES,1 #left margin, used to increase/decrease the spacing to the next dataset. Can be negative, causing datasets to overlap. #MARGIN,0 #arrow height factor; Default height of each arrow will be slightly less than the available space between leaves, but you can set a multiplication factor here to increase/decrease it (values from 0 to 1 will decrease it, values above 1 will increase it) #HEIGHT_FACTOR,1 #arrows are aligned to the node lines by default. Using BAR_SHIFT, you can move them all up/down by a fixed amount #BAR_SHIFT,0 #display or hide the text labels for each arrow #SHOW_ARROW_LABELS,1 #set the size factor for the text labels #LABEL_SIZE_FACTOR,1 #with LABELS_ON_TOP set to 0, label text which does not fit into the arrow will be hidden #LABELS_ON_TOP,0 #rotate all domain labels by a custom angle #LABEL_ROTATION,0 #if set to 1, calculate the domain label color automatically, based on the darkness of the domain. Labels will be white or black. #LABEL_AUTO_COLOR,1 #Position of the label, relative to the arrow (start and end are relative to the arrow direction) #can be one of: start, end or center #LABEL_POSITION,center #shift all labels horizontally and/or vertically #LABEL_SHIFT_X,0 #LABEL_SHIFT_Y,0 #color of the background rectangle backbone displayed behind the arrows #BACKBONE_COLOR,#aaaaaa #height of the background rectangle (in pixels) #BACKBONE_HEIGHT,10 #border width; if set above 0, a border of specified width (in pixels) will be drawn around the arrow shapes #BORDER_WIDTH,0 #border color; used when BORDER_WIDTH is above 0 #BORDER_COLOR,#0000ff #=================================================================# # Actual data follows after the "DATA" keyword # #=================================================================# #Internal tree nodes can be specified using IDs directly, or using the 'last common ancestor' method described in iTOL help pages DATA #Each node can have one set of arrow definitions assigned, with the backbone size/width defined in field 2, followed by an unlimited number of arrow definitions #Each arrow definition consists of 10 mandatory parts, separated with vertical lines: #START|END|START_COLOR|END_COLOR|LABEL|LABEL_COLOR|ARROW_HEIGHT_FACTOR|BOX_HEIGHT_FACTOR|HEAD_WIDTH_LEFT|HEAD_WIDHT_RIGHT|...followed by any 'mark' defintions #The mandatory 10 arrow definition parts can be followed by any number of "mark" definitions, which are rendered as vertical bars within the arrow. #Each mark definition consists of 3 parts: #START|END|COLOR #an example for leaf node 9606: a 500 wide backbone will be overlaid with 2 arrows (shown on the help page) #9606,500,10|110|#0000ff|#ff0000|arrow1|#ffffff|0.75|0.5|0|10|30|35|#ffff00,120|220|#00ff00|#00ff00|arrow2|#000000|1|1|-20|20|180|190|#ffffff|185|186|#000000