I really like this toolbox. I have tried it some time in Matlab.
Is there any hope that k-Wave will run in Octave within some time?
With a fix for one example of an aged version of k-Wave and a suggestion to suppress the visualization I don't see much going on.
I am quite a noob in programming, Matlab/Octave and k-Wave; it would take me ages (which I don't have) to fix this. Any hope?
Hi styxed,
To be honest, we haven't spent any time on it recently as it wasn't obvious that anyone was using k-Wave with Octave. However, we can certainly take a look. Is there any particular functions that you are using? What are the error messages that you receive?
Brad.
Actually... it is working very well in Octave. The first times I ran my code in Octave it gave errors about some try-catch error structure. I can't get the exact error back since now the same code is running like a charm :) It probably had something to do with missing or old Octave packages.
I am working on a 2D model with a time- and location-varying source through a heterogeneous medium (a reflector and an area with high damping (medium.alpha_coeff as array with same size as grid)) with some sensor element directivity. And it works perfectly.
Thanks, and sorry for the false alarm.
Erik
Edit: I am working on Ubuntu 12.04 with Octave 3.6.1 and k-Wave B.0.5
Hi Ahmet,
We don't currently have any plans to port k-Wave to SCILAB. There are some minor syntax differences that would be relatively easy to change (e.g., boolean variables, predefined variables, conditional statements, etc). However, I'm not sure about SCILAB support for MATLAB classes. Similarly, for the built in HTML help, which forms a big part of making k-Wave accessible to new users. If you're looking for a free alternative to MATLAB, you could try Octave.
Brad.
Hi all,
Coming from a background of Matlab and FieldII. Just getting started in Octave (no longer have access to a Matlab license) and k-wave. Hoping to help other Octave users by documenting the differences I find. First issue: Octave appears to handle calls to object methods differently.
Per the Octave documentation
disp (obj); # both are
obj.disp (); # equalAs a result,
kgrid.setTime(kgrid, Nt, dT)
fails because kgrid the object is being passed twice, first through the dot notation and then as the first argument. As a result, the second argument is being set as the obj again and functions on the second argument then fail.
To remedy this, either call the function as kgrid.setTime(Nt, dT) or setTime(kgrid, Nt, dT).
Hi ahd123,
Thanks for posting your solutions!
Brad
You must log in to post.