Prev: Problem with 2D wavelet transform (dwt2)
Next: How to make a 3D object out of a surface
From: Rune Allnor on 30 May 2010 02:53
On 30 Mai, 03:50, TideMan <mul...(a)gmail.com> wrote:
> On May 30, 11:27 am, Nicholas Kinar <n.ki...(a)usask.ca> wrote:
>
> > > By explaining what the problem is? This is a fairly trivial
> > > exercise...
>
> > > Rune
>
> > Perhaps trivial to you, Rune; I've been using either Fortran/C/C++ for a
> > long time, but you know more of Matlab than I do at this time.
>
> > Nicholas
>
> Oh dear, now you've torn it.
> Mentioning Fortran and Rune in the same sentence is like pouring
> gasoline on a fire...................

Of course not. This guy does the sensible thing: He moves away
from fortran. No need to flame somebody who both agrees with me
and already does what I would have adviced him to...

Rune
From: Rune Allnor on 30 May 2010 02:57
On 30 Mai, 01:24, Nicholas Kinar <n.ki...(a)usask.ca> wrote:

> However, this has given me yet another idea.  Perhaps I could write a
> MEX file in C.  The MEX program would parse the data as I please and
> then return it to Matlab. To me, this seems much easier than trying to
> work with all of these cell arrays.

That would be a very good idea, yes. It would be the preferred way,
as you would be able to re-use your file parser in non-matlab
programs down the line.

However, if you want to return non-trivial data from the files,
you will soon find you need to work with the cell arrays anyway.
You might prefer to work the cell arrays from the matlab prompt
and not in MEX.

Rune
First  |  Prev  | 
Pages: 1 2 3 4
Prev: Problem with 2D wavelet transform (dwt2)
Next: How to make a 3D object out of a surface