Anonymizer NeMo Platform SDK Resources
The anonymizer.config module (from the NVIDIA NeMo Anonymizer library) builds AnonymizerConfig objects in a context-agnostic way. Once you are ready to execute that config against the NeMo Platform Anonymizer service, you use objects from the nemo_platform SDK. This page describes the NeMo Platform-specific objects.
AnonymizerResource
The AnonymizerResource is the entry point for working with Anonymizer on NeMo Platform. It wraps the streaming preview endpoint and job submission for the plugin service.
A AnonymizerResource is accessed directly from a NeMoPlatform instance:
An AsyncAnonymizerResource with the same surface is available via AsyncNeMoPlatform.anonymizer.
request is a PreviewRequest or AnonymizerRequest instance from nemo_anonymizer_plugin.app.task_config. Both accept the same config, data, model_configs, and selected_models fields; PreviewRequest adds num_records.
Both preview and run call the plugin service, so they require model_configs and reject local file paths in data.source — use a fileset reference or http(s) URL.
AnonymizerPreviewResult
AnonymizerResource.preview collects the frame stream and returns an AnonymizerPreviewResult once the stream completes.
More about preview results
AnonymizerPreviewResult holds everything in memory; nothing is persisted to disk by default. The dataset and trace_dataset fields are regular pandas DataFrames and can be saved with to_csv / to_parquet.
AnonymizerJobResource
AnonymizerResource.run returns an AnonymizerJobResource. You can also use AnonymizerResource.get_job_resource to get one for an existing job.
The async variant (AsyncAnonymizerJobResource) exposes the same surface with async def methods.
AnonymizerJobResults
download_artifacts returns an AnonymizerJobResults object that loads parquet / JSON artifacts into memory. The same class also works for the local run run flow — point it at the artifact directory the local job results manager logs:
More about job results
AnonymizerJobResults reads files lazily — methods load the corresponding parquet or JSON only when called. The underlying directory layout is:
By default, download_artifacts saves the tarball contents to a local directory named after the job; pass path= to override.
Request Models
Both request models live in nemo_anonymizer_plugin.app.task_config.
Request Fields
AnonymizerRequest defines the execution fields below, run jobs use AnonymizerRequest directly and process the full input file.
PreviewRequest extends AnonymizerRequest with num_records
AnonymizerInputSpec
The plugin-owned API-boundary input spec:
Fileset references can take any of the three forms fileset://<workspace>/<fileset>#<path>, <workspace>/<fileset>#<path>, or <fileset>#<path>, and must resolve to a single .csv or .parquet file.
SelectedModelsOverrides
Partial role → alias overrides for the three workflows. Each section is optional and is merged on top of the bundled default selection by the library.
Supplying overrides without model_configs raises a config validation error.