Read coordinate data from a binary netCDF trajectory file.
read.ncdf(trjfile, headonly = FALSE, verbose = TRUE, time = FALSE, first = NULL, last = NULL, stride = 1, cell = FALSE, at.sel = NULL)
name of trajectory file to read. A vector if treat a batch of files
logical, if TRUE only trajectory header information is returned. If FALSE only trajectory coordinate data is returned.
logical, if TRUE print details of the reading process.
logical, if TRUE the
starting time or frame number to read; If NULL, start from the begining of the file(s).
read data until
take at every
logical, if TRUE and
an object of class ‘select’ indicating a subset of atomic coordinates to be read.
Reads a AMBER netCDF format trajectory file with the help of David W. Pierce's (UCSD) ncdf4 package available from CRAN.
A list of trajectory header data, a numeric matrix of xyz coordinates with a frame/structure per row and a Cartesian coordinate per column, or a numeric matrix of cell information with a frame/structure per row and lengths and angles per column. If time=TRUE, row names of returned coordinates or cell are set to be the physical time of corresponding frames.
See AMBER documentation for netCDF format description.
NetCDF binary trajectory files are supported by the AMBER modules sander, pmemd and ptraj. Compared to formatted trajectory files, the binary trajectory files are smaller, higher precision and significantly faster to read and write.
NetCDF provides for file portability across architectures, allows for backwards compatible extensibility of the format and enables the files to be self-describing. Support for this format is available in VMD.
If you experience problems reading your trajectory file with read.ncdf() consider first reading your file into VMD and from there exporting a new DCD trajectory file with the 'save coordinates' option. This new file should be easily read with read.dcd().