Dataset.set_attrs — Set several Dataset manifest attributes.
tf = Dataset.set_attrs(ds, attrs) merges the fields of a scalar attribute structure into one manifest update.
Syntax
tf = Dataset.set_attrs(ds, attrs)Inputs
ds- Type
Any- Required
- Yes
- Default
- —
- Description
- Managed Dataset receiver.
attrs- Type
Any- Required
- Yes
- Default
- —
- Description
- Attribute structure.
Returns
tf- Type
LogicalArray- Description
- Logical result.
Errors
RUNMAT:Data:Error- When
- A Dataset family receiver, argument, manifest, payload, or filesystem operation fails.
- Message
data: operation failed
RunMat:data:ManifestConflict- When
- A transaction's expected manifest sequence no longer matches the stored manifest.
- Message
data: manifest conflict
RunMat:data:TransactionNotFound- When
- The transaction is absent from the process-local registry.
- Message
data: transaction not found
Persistence
Each stored attribute value must be a string scalar (including a one-element string array), character row vector, finite scalar double, fixed-width integer scalar, or scalar logical value. Numeric/logical array carriers, nonscalar string arrays, character matrices or pages, cells, and nested structs require explicit encoding and are rejected at JSON serialization. Typed missing strings store as JSON null and decode as missing strings. Empty strings and literal spellings such as <missing> remain ordinary text.
The update advances the manifest timestamp and sequence once. Scalar integer fields retain their exact mathematical values as JSON numbers, though JSON does not preserve a narrow integer storage class.
Example
Store two attributes
schema = struct(); schema.arrays = struct();
ds = data.create('setattrs.data', schema);
a = struct('source', 'sensor', 'stage', 'ready');
tf = Dataset.set_attrs(ds, a);Using Dataset.set_attrs with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how Dataset.set_attrs changes the result.
Run a small Dataset.set_attrs example, explain the result, then change one input and compare the output.
FAQ
Does this replace every existing field?⌄
No. Supplied fields are merged into the existing manifest attribute map.
Related Io functions
Data
commit · data.copy · data.create · data.delete · data.exists · data.export · data.import · data.inspect · data.list · data.move · data.open · DataArray.chunk_shape · DataArray.codec · DataArray.dtype · DataArray.fill · DataArray.name · DataArray.rank · DataArray.read · DataArray.resize · DataArray.shape · DataArray.write · Dataset.array · Dataset.arrays · Dataset.attrs · Dataset.begin · Dataset.get_attr · Dataset.has_array · Dataset.id · Dataset.path · Dataset.refresh · Dataset.set_attr · Dataset.snapshot · Dataset.version · DataTransaction.abort · DataTransaction.commit · DataTransaction.create_array · DataTransaction.delete_array · DataTransaction.fill · DataTransaction.id · DataTransaction.resize · DataTransaction.set_attr · DataTransaction.set_attrs · DataTransaction.status · DataTransaction.write
Repl Fs
addpath · cd · copyfile · delete · dir · exist · fileattrib · fileparts · filesep · fullfile · genpath · getenv · getpref · isenv · isfile · isfolder · ispref · ls · matlabroot · memmapfile · memmapfile.subsasgn · memmapfile.subsref · mkdir · movefile · open · opentoline · path · pathsep · pcode · pwd · readstruct · rehash · restoredefaultpath · rmdir · rmpath · run · savepath · setenv · setpref · system · tempdir · tempname · uigetdir · uigetfile · uiputfile · unsetenv · userpath · what · winqueryreg · xmlread · xmlwrite
Tabular
arrayDatastore · csvread · csvwrite · detectImportOptions · dlmread · dlmwrite · fileDatastore · getvaropts · parquetDatastore · parquetinfo · parquetread · readcell · readmatrix · readtable · readtimetable · setvaropts · setvartype · spreadsheetImportOptions · writecell · writematrix · writetable · writetimetable · xlsread · xlswrite
Filetext
fclose · feof · fgetl · fgets · fileread · filewrite · fopen · fprintf · fread · frewind · fwrite · readlines · writelines
Import
Json
Related guides
Source you can read
Every RunMat function's source is public. Read exactly how Dataset.set_attrs is executed, line by line, in Rust.
- View the source for Dataset.set_attrs in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.
- RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
- Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.