Path: news.mathworks.com!not-for-mail
From: <HIDDEN>
Newsgroups: comp.soft-sys.matlab
Subject: Re: fopen(machineformat=vaxd)
Date: Sat, 18 Oct 2008 23:06:01 +0000 (UTC)
Organization: Universit&#228;t Heidelberg
Lines: 14
Message-ID: <gddq4p$k2t$1@fred.mathworks.com>
References: <gdcld5$2jj$1@fred.mathworks.com> <gdd73e$71t$1@fred.mathworks.com>
Reply-To: <HIDDEN>
NNTP-Posting-Host: webapp-03-blr.mathworks.com
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: fred.mathworks.com 1224371161 20573 172.30.248.38 (18 Oct 2008 23:06:01 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Sat, 18 Oct 2008 23:06:01 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 869888
Xref: news.mathworks.com comp.soft-sys.matlab:496001


Thanks James!
 
> I may be able to write some custom code for you ... I just did something similar on another newsgroup thread recently. Is the file just a pure binary file with only D-FLOAT numbers? How many per record? What system are you reading these on? Do you know if your system is big-endian or little-endian?

It would be a big hack! I'm working with C3D files, which contain a section with mixed CHAR, INT8, UINT16, FLOAT32.
Afterwards a big block of binary records is following and finally **any** kind of supplemental data are allowed.

I have about trial 20.000 files and assume 20% of them use the VaxD format.

I'm enormously surprised that Matlab has removed this important feature from FOPEN! It worked since Matlab 4 (or even earlier), you find the VAXD-Format in Octave and Scilab. Unfortunately, I cannot find any documentation for this loss of features on the Mathworks web docs. By the way, where do I find the documentation for former releases?

So the best solution for me would be a conversion in 6.5.1: Read in VAXD and develop a function to write in little-endian. That's no fun.

Kind regards, Jan