Gamayun

top

Modules

Files

by unit depth scope from to

What the square measures

source compare with shared tasks ≥ edges per node

How the map is drawn

top

What Gamayun stores, and what you can look up here

Elements

prefix	element	where it comes from	example
`term:`			term:validation
`module:`			module:server
`dir:`			dir:<path>
`file:`			file:<path>
`ident:`			ident:<Name>
`sym:`			sym:<file#Name>
`dataset`			dataset

Relations of a project built from a task database

relation	means	rule
`term characterizes module / dir / file`
`term not_in module`
`term anchor_of module`
`term names file`
`file co_changes_with file`
`term narrower_than term`
`module depends_on module`
`part_of`, `task_count`, `train_tasks`

Relations of a project built from a folder

relation	means	rule
`term characterizes file / dir / module / sym`
`ident defined_in file / sym`
`ident used_in file / sym`
`ident has_part term`
`sym member_of sym`
`term related_to term`
`term is_a term`
`term same_as term`
`term variant_of term`
`term is function_word / domain_core`

In this project

Build a project

Project name Task database (.db) — or files: a folder of documents / code (no database) Git repository (optional, adds module depends_on) Keep the ontology in