LAio¶
<auto-generated stub>
Related methods¶
def deleteFile(x: Rep[String]): Rep[Unit]
def fileExists(x: Rep[String]): Rep[Boolean]
def fileLength(x: Rep[String]): Rep[Long]
def readMatrix(path: Rep[String]): Rep[DenseMatrix[Double]]
def readMatrix(path: Rep[String], delim: Rep[String]): Rep[DenseMatrix[Double]]
def readMatrix(path: Rep[String], schemaBldr: (Rep[String]) => Rep[Elem], delim: Rep[String] = unit("\s+"), trim: Rep[Boolean] = true): Rep[DenseMatrix[Elem]]
def readMatrixAndParse(path: Rep[String], schemaBldr: (Rep[DenseVector[String]]) => Rep[DenseVector[Elem]], delim: Rep[String] = unit("\s+"), trim: Rep[Boolean] = true): Rep[DenseMatrix[Elem]]
def readVector(path: Rep[String]): Rep[DenseVector[Double]] For fusion and cluster execution, reads should be pure. however, in that case we need a different way to order them with respect to writes / deletes. one solution would be to implicitly convert strings to mutable file objects, and (manually) CSE future conversions to return the original mutable object. Currently, reading and writing the same file in the same program is not supported, unless there is an alternate dependency chain from the output being written to the input (e.g. the output vector or matrix explicitly depends on the one being read).
def readVector(path: Rep[String], schemaBldr: (Rep[String]) => Rep[Elem]): Rep[DenseVector[Elem]]
def readVectorAndParse(path: Rep[String], schemaBldr: (Rep[DenseVector[String]]) => Rep[Elem], delim: Rep[String] = unit("\s+"), trim: Rep[Boolean] = true): Rep[DenseVector[Elem]]
def writeMatrix(m: Rep[DenseMatrix[Elem]], path: Rep[String], delim: Rep[String] = unit(" ")): Rep[Unit]
def writeVector(v: Rep[DenseVector[Elem]], path: Rep[String]): Rep[Unit]