octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #34843] insufficient information on mat read f


From: anonymous
Subject: [Octave-bug-tracker] [bug #34843] insufficient information on mat read failure
Date: Wed, 16 Nov 2011 18:53:56 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20100101 Firefox/6.0.2

URL:
  <http://savannah.gnu.org/bugs/?34843>

                 Summary: insufficient information on mat read failure
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Wed 16 Nov 2011 06:53:55 PM UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Documentation
                  Status: None
             Assigned to: None
         Originator Name: Charlie
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.4.2
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Hi,

I am trying to load a fairly large .mat file created by Matlab and I'm getting
a lot of errors like those shown below

using octave 3.4.2 and java-1.2.8

eg.
error: load: invalid element type = 0

zero is very common 65535 also and raft of less frequent values.

Do these numbers actually represent something related to "data element type"
or are they spurious values output because octave is incorrectly parsing the
data?

ie does this mean I have a dozen formats that are not supported or probably
just one ?

If it's just one I may have a go at fixing it or getting the data in an
acceptable format.

Shouldn't Octave be trapping this a bit better?


There seems to insufficient information to know what it can't handle and to do
something about it.

Also I have seen allusions to this issue that some formats are not yet
supported but there seems no list of what is and isn't supported that would
enable to work around it.


It would seem better if this incompatibility was at least properly documented.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?34843>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]