NAME
iTOL_uploader - batch upload trees and data to iTOL
SYNOPSIS
iTOL_uploader.pl options
DESCRIPTION
Use iTOL_uploader.pl to upload your phylogenetic trees and datasets to iTOL through its batch upload interface. Your trees and datasets must be in plain text format. If you want to upload into your iTOL account, you must first enable the batch upload through a link in 'Account settings' on your personal account page. This will create a unique 'Upload ID' which you must use when uploading (through the 'uploadID' option).
GENERAL OPTIONS
Separate options and their values with a space.
- --help
- display this message
- --config
- read upload options from a file (format described below); example file available at http://itol.embl.de/help/upload.cfg
- --treeFile
- file containing the tree
- --treeFormat
- tree format (newick, nexus or phyloxml)
- --treeName
- tree name
- --treeDescription
- longer description of the tree, used only if uploading into an iTOL account
- --uploadID
- Your upload ID, which is generated when you enable batch uploading in your account (in the 'Account settings').
- --projectName
- Required if uploadID is specified. Project name is case sensitive, and should be unique in your account. We recommend creating a separate project for batch uploaded trees.
- --showInternalIDs
- displays internal node IDs in popups when you mouseover them
- --fontStylesFile
- defines font styles for leaf labels in exported trees
- --internalNamesFile
- defines custom names for internal nodes in the tree
- --HGTFile
- defines horizontal gene transfers
- --colorDefinitionFile
- defines color ranges, clade and leaf label colors
- --preCollapsedFile
- defined which clades should be collapsed by default; useful for large trees
- --assignTaxonomy
- if you tree uses NCBI tax IDs, the names for leaves and internal nodes will be automatically assigned during upload
- --midpointRoot
- tree will be midpoint re-rooted during upload
- --ncbiFile
- instead of uploading a tree, iTOL can automatically generate one from a file containing a list of NCBI tax IDs. NCBI taxonomy will be pruned based on your IDs and a Newick tree generated.
- --ncbiFormat
- format of the tree generated using NCBI tax IDs:
- 'namesFull'
- generated tree will contain scientific names and internal nodes will not be collapsed
- 'namesCollapsed'
- scientific names will be used, and internal nodes with only one child removed
- 'idsFull'
- tree will contain NCBI taxonomy IDs and internal nodes will not be collapsed
- 'idsCollapsed'
- NCBI taxonomy IDs will be used, and internal nodes with only one child removed
DATASET UPLOAD OPTIONS
Up to 10 datasets can be uploaded, replace 'dataset1' as needed for others (ie. dataset2 for the second dataset and so on). Dataset file, label, separator and type are required, other parameters are optional.
- --dataset1File
- file containing the dataset
- --dataset1Label
- label for the dataset, used in the legends
- --dataset1Separator
- field separator used in the dataset file: 'space', 'tab' or 'comma'
- --dataset1Type
- dataset type
- 'binary'
- Binary data
- 'simplebar'
- Simple bar chart
- 'multibar'
- Multi-value bar chart or Pie chart
- 'gradient'
- Color gradient
- 'colorstrip'
- Color strips
- 'time'
- Time series
- 'domains'
- Protein domain architecture
- 'heatmap'
- Heatmap
- 'boxplot'
- Boxplot
- --dataset1Color
- used in the legends and for datasets where the color is not specified in the dataset file
- --dataset1StripWidth
- used in 'gradient' and 'colorstrip'; strip will have the specified width in pixels (valid range: 10 - 100)
- --dataset1PreventOverlap
- used in 'gradient' and 'colorstrip'; if set to 1, all other dataset types will start after the end of the last strip dataset
- --dataset1MultiBarAlign
- used in 'multibar'; if set to 1, each field's start will be aligned
- --dataset1PieTransparent
- used in 'multibar'; if transprent, you will be able to see overlapping pie charts, but the colors will be slightly changed
- --dataset1PieRadiusMax
- used in 'multibar'; pie chart radii will be scaled to match the selected values (valid range 10-500)
- --dataset1PieRadiusMin
- used in 'multibar'; pie chart radii will be scaled to match the selected values (valid range 10-500)
- --dataset1BarSizeMax
- used in 'multibar', 'simplebar' and 'time'; maximum value in the dataset will have this pixel size (valid range 1-5000)
- --dataset1ProtSizeMax
- used in 'domains'; longest protein in the dataset will have this pixel size (valid range 1-5000)
- --dataset1BoxplotSize
- used in 'boxplot'; largest value in the dataset will be at this pixel (valid range 1-5000)
- --dataset1BoxplotRawData
- used in 'boxplot'; if you provide the raw data, iTOL will automatically calculate the values needed to display the boxplots
- --dataset1BoxplotUpperPercentile
- used in 'boxplot'; values above the set percentile will be included in the box (valid range 0-99)
- --dataset1BoxplotLowerPercentile
- used in 'boxplot'; values below the set percentile will be included in the box (valid range 1-100)
- --dataset1BoxplotStepConstant
- used in 'boxplot'; this constant multiplied with the box size will define the related whisker size (valid value >0)
- --dataset1BoxplotCalculateExtremes
- used in 'boxplot'; if set to 0, only the boxes and whiskers will be calculated
- --dataset1BranchColoringType
- used in 'colorstrip'; specifies the effect of the dataset on branch coloring:
- 'none'
- no coloring, show only leaf boxes (Default)
- 'branch'
- color branches only, don't display boxes
- 'both'
- color branches and show boxes
- --dataset1HeatmapBoxWidth
- used in 'heatmap'; pixel width of an individual value's box in the heatmap. Total width for the dataset cannot exceed 5000 px.
- --dataset1MinPointValue
- used in 'heatmap'; minimum value
- --dataset1MidPointValue
- used in 'heatmap'; mid-point value
- --dataset1MaxPointValue
- used in 'heatmap'; maximum value
- --dataset1MinPointColor
- used in 'heatmap'; color of the minimum value
- --dataset1MidPointColor
- used in 'heatmap'; color of the mid-point value
- --dataset1MaxPointColor
- used in 'heatmap'; color of the maximum value
USING A CONFIGURATION FILE
If you are uploading several datasets, the command line becomes hard to handle and its length could reach your shell limit. Therefore, we provided an option of using a separate plain text config file to specify the upload parameters. To use a configuration file, simply use the --config option to specify its location.
The configuration file should contain one parameter per line. Use the = sign to assign values to the parameters. Please note that you should backslash the hash sign in color definitions. Here is an example configuration file:
treeFile = tree_of_life.tree
treeFormat = newick
treeName = upload test
uploadID = aNrrwThf6vrDtWdZeaA1Ya
projectName = Batch test
dataset1File = tree_of_life.heatmap200
dataset1Label = heatmap_batch
dataset1Separator = tab
dataset1Type = heatmap
dataset1Color = \#FF00FF
dataset1HeatmapBoxWidth = 10
dataset1MinPointValue = -1000
dataset1MinPointColor = \#ff0000
dataset1MidPointValue = 0
dataset1MidPointColor = \#000000
dataset1MaxPointValue = 1000
dataset1MaxPointColor = \#0000ff
dataset2File = tree_of_life.multi4
dataset2Label = multibar_batch
dataset2Separator = tab
dataset2Type = multibar
dataset2Color = \#0000FF
dataset2BarSizeMax = 2000
SEE ALSO
iTOL Home page : http://itol.embl.de
iTOL Help : http://itol.embl.de/help/help.shtml
AUTHOR
Ivica Letunic <ivica@letunic.com>
Contact me if you have any questions or comments.