.drop_meta_keys

Every schema.rtemis.org config declares a <code>$schema</code>, and so may a nested one:
the family schemas (preprocessor, execution, decomposition, clustering, ...)
all permit <code>$schema</code>, so a <code>preprocessor_config</code> lifted verbatim out of a
standalone preprocessor config file carries its own. Those <code>$</code>-prefixed keys
are document metadata, not <code>setup_*</code> arguments, so they are stripped before a
parsed list is forwarded via <code><a href="/link/do.call()?package=rtemis&version=1.4.3" data-mini-rdoc="rtemis::do.call()">do.call()</a></code>. Anything else unknown still reaches
the <code>setup_*</code> function and fails there.

internal

Machine learning and visualization package with an 'S7' backend featuring
comprehensive type checking and validation, observable runs, and auditable outputs.
The functional API provides one-call access to supervised and unsupervised learning
through train(), cluster(), and decomp(). All configuration steps are performed using
setup functions and validated. A single call to train() can handle preprocessing,
decomposition, hyperparameter tuning, model stacking, and testing with nested resampling.
Supports 'data.frame', 'data.table', and 'tibble' inputs and parallel execution. Plot
methods for trained and resampled supervised models draw interactive figures through
'rtemis.draw'. Includes native implementations of SuperLearner, RuleFit, and Linear
Additive Trees, and supports conformal prediction. The package first appeared in
E.D. Gennatas (2017)
<https://repository.upenn.edu/entities/publication/d81892ea-3087-4b71-a6f5-739c58626d64>.

Efstathios D. Gennatas

rtemis

Schema-Driven Machine Learning and Visualization

E.D. Gennatas

.drop_meta_keys function

<dl><dt>x</dt>
<dd>Named list parsed from JSON, or <code>NULL</code>.</dd></dl>

Arguments

Author

Every schema.rtemis.org config declares a <code>$schema</code>, and so may a nested one:
the family schemas (preprocessor, execution, decomposition, clustering, ...)
all permit <code>$schema</code>, so a <code>preprocessor_config</code> lifted verbatim out of a
standalone preprocessor config file carries its own. Those <code>$</code>-prefixed keys
are document metadata, not <code>setup_*</code> arguments, so they are stripped before a
parsed list is forwarded via <code><a href='https://rdrr.io/r/base/do.call.html'>do.call()</a></code>. Anything else unknown still reaches
the <code>setup_*</code> function and fails there.

Drop JSON document metadata keys from a parsed config list — .drop_meta_keys

<dl>

<dt>x</dt>
<dd>Named list parsed from JSON, or <code>NULL</code>.</dd>

</dl>

.drop_meta_keys: Drop JSON document metadata keys from a parsed config list

Description

Usage

Value

Arguments

Author

Details

Examples