io
High level I/O operators.
Reads an object/model back from a file created by write command.
Reads an object/model back from a file created by write command.
Reads an ARFF file.
Reads an ARFF file.
Reads binary sparse dataset.
Reads binary sparse dataset. Each item is stored as an integer array, which are the indices of nonzero elements in ascending order
Reads a CSV file with response variable.
Reads a CSV file with response variable.
Reads GCT microarray gene expression file.
Reads GCT microarray gene expression file.
Reads a LivSVM file.
Reads a LivSVM file.
Reads PCL microarray gene expression file.
Reads PCL microarray gene expression file.
Reads RES microarray gene expression file.
Reads RES microarray gene expression file.
Reads spare dataset in coordinate triple tuple list format.
Reads spare dataset in coordinate triple tuple list format. Coordinate file stores a list of (row, column, value) tuples:
instanceID attributeID value instanceID attributeID value instanceID attributeID value instanceID attributeID value ... instanceID attributeID value instanceID attributeID value instanceID attributeID value
Ideally, the entries are sorted (by row index, then column index) to improve random access times. This format is good for incremental matrix construction.
Optionally, there may be 2 header lines
D // The number of instances W // The number of attributes
or 3 header lines
D // The number of instances W // The number of attributes N // The total number of nonzero items in the dataset.
These header lines will be ignored.
the file path.
the starting index of array. By default, it is 0 as in C/C++ and Java. But it could be 1 to parse data produced by other programming language such as Fortran.
Reads Harwell-Boeing column-compressed sparse matrix.
Reads Harwell-Boeing column-compressed sparse matrix.
Reads a delimited text file with response variable.
Reads a delimited text file with response variable. By default, the parser expects a white-space-separated-values file. Each line in the file corresponds to a row in the table. Within a line, fields are separated by white spaces, each field belonging to one table column. This class can also be used to read other text tabular files by setting delimiter character such ash ','. The file may contain comment lines (starting with '%') and missing values (indicated by placeholder '?').
the file path
optional response variable attribute and the column index of response variable. The column index starts at 0.
delimiter string
the start of comment lines
the missing value placeholder
true if the first row is header/column names
true if the first column is row id/names
an attribute dataset
Reads TXT microarray gene expression file.
Reads TXT microarray gene expression file. The TXT format is a tab delimited file format that describes an expression dataset. It is organized as follows:
The first line contains the labels Name and Description followed by the identifiers for each sample in the dataset. The Description is optional.
Line format:
Name(tab)Description(tab)(sample 1 name)(tab)(sample 2 name) (tab) ... (sample N name)
Example:
Name Description DLBC1_1 DLBC2_1 ... DLBC58_0
The remainder of the file contains data for each of the genes. There is one line for each gene. Each line contains the gene name, gene description, and a value for each sample in the dataset. If the first line contains the Description label, include a description for each gene. If the first line does not contain the Description label, do not include descriptions for any gene. Gene names and descriptions can contain spaces since fields are separated by tabs.
Line format:
(gene name) (tab) (gene description) (tab) (col 1 data) (tab) (col 2 data) (tab) ... (col N data)
Example:
AFFX-BioB-5_at AFFX-BioB-5_at (endogenous control) -104 -152 -158 ... -44
Reads a Wavefront OBJ file.
Reads a Wavefront OBJ file. The OBJ file format is a simple format of 3D geometry including the position of each vertex, the UV position of each texture coordinate vertex, vertex normals, and the faces that make each polygon defined as a list of vertices, and texture vertices. Vertices are stored in a counter-clockwise order by default, making explicit declaration of face normals unnecessary. OBJ coordinates have no units, but OBJ files can contain scale information in a human readable comment line.
Note that we parse only vertex and face elements. All other information ignored.
the file path
a tuple of vertex array and edge array.
Writes an object/model to a file.
Writes an object/model to a file.
I/O functions.