From help-request at octave dot org Wed Jun 1 07:26:11 2005 Subject: Re: general load/save (in)compatibility From: SITI HAJAR A BAKAR To: help at octave dot org Date: Wed, 01 Jun 2005 21:57:31 +1000 Hello all, Im afraid I wont be contirbuting any answers to this topic, just more questions. Where do .csv files come into the picture for this? ----- Original Message ----- From: "John W. Eaton" Date: Saturday, May 28, 2005 4:40 am Subject: Re: general load/save (in)compatibility > On 27-May-2005, Ben Barrowes wrote: > > | David Bateman wrote: > | > | > Ben Barrowes wrote: > > | I understand. Many of the posts I have seen in the mailing lists > call > | for fairly strict compatibility standards in order to make > things matlab > | compatible, so I thought I would point a few things out. > > Yes, but again, bug-for-bug compatibility is not a goal. > > | >> - matlab's default save filetype is a matfile, instead of > an > | >> octave -text file (octave's default), why is > default_save_options = > | >> "-text"? Wouldn't it make sense to be compatible with matlab? > Fix=> > | >> set default_save_options = "-mat"; > | > > | > Why... Octave has its own formats, why should a competitors > file > | > format be the default... Octave gives you the > default_save_options > | > variable so set it to "-mat" in your .octaverc file and you > will have > | > the behaviour you want while not penalizing other users. > > Yes, and also if we were to use the MAT file format as the > default, we > would not be able to save all data types that can be present in > Octave. The nice thing about Octave's formats are that they are > extensible, so user-defined data types written in C++ can also be > saved and loaded. > > | I don't see the -mat-ascii switch available in the load/save > helps. > | Also, it doesn't seem to be recognized in 2.9.3: > | octave:13> save -mat-ascii test1 aa > | warning: save: no such variable `test1' > | octave:14> > | > | will this be in 3.0? > > Yes, that is the plan, but someone must implement it first. > > | >> - octave apparently has no way to load ascii files > containing > | >> numbers only. > > This is false. Octave should be able to do this just fine. If it is > not working for you, then perhaps there is a bug? > > | For example, if test2 contains: > | >> $ more test2 > | >> 8.0000000e+00 1.0000000e+00 6.0000000e+00 > | >> 3.0000000e+00 5.0000000e+00 7.0000000e+00 > | >> 4.0000000e+00 9.0000000e+00 2.0000000e+00 > | >> matlab will put this into a variable called test2 when called > with| >> >> load test2 > > Octave should do the same, and here is what I see with a copy of > Octave built from the current CVS or 2.1.69, using the data you show > above: > > octave:1> load ("test2") > octave:2> test2 > test2 = > > 8 1 6 > 3 5 7 > 4 9 2 > > octave:3> a = load ("test2") > a = > > 8 1 6 > 3 5 7 > 4 9 2 > > Seems to work correcty. But if you think you have found a bug, then > please send the file that does not load for you as an attachment > so we > get all the characters, precisely as you see them on your system. > > jwe > > > > ------------------------------------------------------------- > Octave is freely available under the terms of the GNU GPL. > > Octave's home on the web: http://www.octave.org > How to fund new projects: http://www.octave.org/funding.html > Subscription information: http://www.octave.org/archive.html > ------------------------------------------------------------- > > ------------------------------------------------------------- Octave is freely available under the terms of the GNU GPL. Octave's home on the web: http://www.octave.org How to fund new projects: http://www.octave.org/funding.html Subscription information: http://www.octave.org/archive.html -------------------------------------------------------------