command line interface to ERK (emergent representation of knowledge)

usage: pyerk [-h] [-nk NUMBER_OF_NEW_KEYS] [-l MOD_PATH PREFIX]
             [-lp PACKAGE_TOML_PATH] [-rwd] [-pad path] [-grp reportconf-path]
             [-vis uri] [-i] [-dj] [-djs] [-ac] [-ik path_to_mod]
             [-utd path_to_erk_package] [--dbg] [--version]
             [inputfile]

Positional Arguments

inputfile

input file

Named Arguments

-nk, --new-keys

generate new keys

-l, --load-mod

load module (.py file) from path with prefix.

-lp, --load-package

load erk package (represented by erkpackage.tomle file)

-rwd, --relative-to-workdir

DEPRECATED; specifies that the module path is interpreted relative to working dir (not the modules install path)

Default: False

-pad, --parse-ackrep-data

parse ackrep data repository, create items and relations. specify path to ackrep_data base dir (…/ackrep_data)

-grp, --generate-report

generate report based on configuration file (e.g. reportconf.toml)

-vis, --visualize

create a visualization for the entity

-i, --interactive-session

start an interactive session (with the specified module/package loaded)

Default: False

-dj, --start-django

start the django server from the current directory

Default: False

-djs, --start-django-shell

start the django shell from the current directory (mainly useful for development)

Default: False

-ac, --create-autocomplete-candidates

create a file with autocomplete candidates in the current workdir

Default: False

-ik, --insert-keys-for-placeholders

replace `_newitemkey_ = ` with appropriate short keys

-utd, --update-test-data

create a subset of the erkpackage (e.g. OCSE) and store it in the test_data dir of pyerk-core

--dbg

start debug routine

--version

print the version and exit

Default: False