Currently there is no ability for augur export v2 to export custom branch labels.
In general, node-data.json defines traits for nodes via the following structure,
{
"nodes": {
"NODE_NAME": {
"TRAIT_NAME": "VALUE"
}
}
}
which augur export v2 maps onto nodes as such:
"NODE_NAME": {
"node_attrs": {
"TRAIT_NAME": {
"value": "VALUE"
},
}
}
There are two "special-case" situations which are relevant here:
-
if TRAIT_NAME == "clade_annotation" then augur will export this as a branch label rather than a node_attr. "clade_annotation" is typically produced by augur clades and is how we get clade labelling in most of our datasets.
-
augur export v2 automatically creates a branch label for "aa" if a node-data file with "aa_muts" is provided.
These two cases are the only time that augur export adds information to the branch_attrs of a node. This means that there is no ability for augur export v2 to set custom branch labels for (internal) nodes.
Currently there is no ability for
augur export v2to export custom branch labels.In general,
node-data.jsondefines traits for nodes via the following structure,{ "nodes": { "NODE_NAME": { "TRAIT_NAME": "VALUE" } } }which
augur export v2maps onto nodes as such:There are two "special-case" situations which are relevant here:
if
TRAIT_NAME == "clade_annotation"then augur will export this as a branch label rather than a node_attr. "clade_annotation" is typically produced byaugur cladesand is how we get clade labelling in most of our datasets.augur export v2automatically creates a branch label for "aa" if a node-data file with "aa_muts" is provided.These two cases are the only time that augur export adds information to the
branch_attrsof a node. This means that there is no ability foraugur export v2to set custom branch labels for (internal) nodes.