enumeray model
Create author projects and govern model publications, ownership and history.
Use when: You are adapting scientific code for Enumeray or maintaining a published model.
Role and prerequisites: Model owner or current co-admin. Install enumeray, configure the API and log in. Use an account or delegated token with the required permissions. Example IDs must be replaced with IDs from your service.
Example
Section titled “Example”enumeray model init scalar-double --directory ./scalar-author --kind python --io json --driver processenumeray model listEvery command also accepts the profile, API, JSON and timeout options.
Choose a subcommand
Section titled “Choose a subcommand”| Command | Purpose |
|---|---|
release |
Manage one saved publication release through explicit activation. |
init |
Generate a runnable local author starter with declarations, wrappers, tests and fixtures. |
list |
Discover listed models and models visible to your account. |
get |
Inspect model metadata, access capability and the visible current publication. |
create |
Create a model resource and import optional author metadata. |
validate |
Validate a complete editable publication offline. |
publications |
List the retained publications of a model you administer. |
publication |
Inspect one immutable publication candidate and its validation state. |
revoke-publication |
Permanently revoke one model publication while preserving accepted history. |
retire-publication |
Request retirement of unused publication installation configuration. |
publish |
Activate a ready publication using the previously observed current ID. |
runs |
Inspect run history for a model you currently administer. |
audit |
Read audit history for one managed model. |
members |
Read a model’s owner, co-admins and governance generation. |
member-add |
Add a model co-admin at an observed generation. |
member-remove |
Remove a model co-admin at an observed generation. |
transfer |
Propose model ownership transfer to a named account. |
accept-transfer |
Accept model ownership proposed to your account. |
archive |
Archive a model at an observed generation. |
Result and next step
Section titled “Result and next step”Choose a subcommand below. The group itself performs no operation.
Follow the complete author workflow for testing, installation and publication.
Exact syntax, defaults and accepted values
Create author projects and manage model publications, ownership and history
Usage: enumeray model [OPTIONS] <COMMAND>
Commands: release Save, resume, review and explicitly activate one publication release init Create a runnable author project locally, without credentials or installation list List the model catalogue visible to your account, one page at a time get Inspect model metadata, current publication and execution destination create Create model catalogue metadata from explicit fields or a publication source validate Validate an editable publication source locally without credentials publications List this model's immutable publications and candidates publication Inspect an exact publication, readiness and captured execution settings revoke-publication Permanently revoke this publication while preserving its accepted history retire-publication Retire this publication's installation configuration after its work drains publish Activate a validated candidate; omit --expected-current for first publication runs List this model's run history with model administrator authority audit Read one page of this model's audit history members Inspect the model owner, co-administrators and current model generation member-add Add a model co-administrator at the observed model generation member-remove Remove a model co-administrator at the observed model generation transfer Propose model ownership transfer to an account that must accept it accept-transfer Accept the named model ownership transfer as its recipient archive Permanently archive the model at its observed model generation help Print this message or the help of the given subcommand(s)
Options: --api <API> User API origin override; credentials never cross origins. Host/runner commands use explicit configuration --profile <PROFILE> Named local user API/login profile; host/runner commands use explicit configuration [default: default] --config <CONFIG> Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json --json Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol --timeout <TIMEOUT> User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60] -h, --help Print helpDocumentation 205dcb3116ea · public sources 8c70356d340f · built .Download documentation identity.