File: h5_writeAttribute.Rd

package info (click to toggle)
r-bioc-rhdf5 2.50.2%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,584 kB
  • sloc: ansic: 8,521; cpp: 91; makefile: 11; python: 9; sh: 6
file content (64 lines) | stat: -rw-r--r-- 1,989 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/h5writeAttr.R
\name{h5_writeAttribute}
\alias{h5_writeAttribute}
\alias{h5writeAttribute}
\alias{h5writeAttribute.array}
\title{Write an R object as an HDF5 attribute}
\usage{
h5writeAttribute(
  attr,
  h5obj,
  name,
  h5loc,
  encoding = NULL,
  variableLengthString = FALSE,
  asScalar = FALSE,
  checkForNA = TRUE
)

\method{h5writeAttribute}{array}(
  attr,
  h5obj,
  name,
  h5loc,
  encoding = NULL,
  variableLengthString = FALSE,
  asScalar = FALSE,
  checkForNA = TRUE
)
}
\arguments{
\item{attr}{The R object to be written as an HDF5 attribute.}

\item{h5obj}{Normally an object of class \linkS4class{H5IdComponent} representing a
H5 object identifier (file, group, or dataset). See
\code{\link{H5Fcreate}}, \code{\link{H5Fopen}}, \code{\link{H5Gcreate}},
\code{\link{H5Gopen}}, \code{\link{H5Dcreate}}, or \code{\link{H5Dopen}} to
create an object of this kind.  This argument can also be given the path to
an HDF5 file.}

\item{name}{The name of the attribute to be written.}

\item{h5loc}{The location of the group or dataset within a file to which the
attribute should be attached. This argument is only used if the
\code{h5obj} argument is the path to an HDF5 file, otherwise it is ignored.}

\item{encoding}{The encoding of the string data type. Valid options are
"ASCII" and "UTF-8".}

\item{variableLengthString}{Whether character vectors should be written as
variable-length strings into the attributes.}

\item{asScalar}{Whether length-1 \code{attr} should be written into a scalar
dataspace.}

\item{checkForNA}{Whether a \code{attr} should be checked for \code{NA}
values before being written.  This only applies of \code{attr} is of type
logical.  Testing for \code{NA} values can be slow if the object to be
written is large, so if you are sure no such values will be present this
argument can be used to disable the testing.}
}
\description{
Write an R object as an HDF5 attribute
}