Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Perhaps not really an answer, but comment fields are somewhat limited:</p> <p>I find the backtrace odd: it jumps from <code>ax.set_ylabel</code> to <code>return _wrapit(a, 'reshape', newshape, order=order)</code>, without any intermediate call inside matplotlib (eg, I would expect a call to <code>fromnumeric.reshape</code> from within <code>set_ylabel</code>. The only occurence of <code>reshape</code> in your code is </p> <pre><code>ZZ=np.reshape </code></pre> <p>so perhaps the culprit is that, and somehow the order has gotten messed up in the backtrace.</p> <pre><code>ZZ=np.reshape(Z,XX.shape) </code></pre> <p>fails if <code>Z</code> and <code>XX</code> have incompatible shapes. I assume <code>X</code>, <code>Y</code> and <code>Z</code> do have compatible shapes when calling <code>plot_data()</code>. Since <code>XX</code> is created in the <code>meshgrid()</code> call, <code>y</code> or <code>x</code> may have incorrect dimensions. As <code>x</code> and <code>y</code> are created by calling <code>set()</code> on <code>X</code> and <code>Y</code>, this could be where things go wrong: values occurring multiple times in <code>X</code> or <code>Y</code> could mess up things, even if it all concerns floating point values.</p> <p>So I would verify the shape (length) of <code>X</code>, <code>Y</code> and <code>Z</code>, and then that of <code>x</code> and <code>y</code> as well.</p> <p>I notice an</p> <pre><code>unpack_format="&gt;%dL" % buff_size` </code></pre> <p>line which suggests the data are actually longs, not floating point (making it easier to run into the problem of values occurring multiple times). Then again, <code>unpack_format</code> is nowhere used.</p>
    singulars
    1. This table or related slice is empty.
    1. PONumpy reshape yields a different size error
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO`unpack_format` is a left over line from the old version, I will double check the length of the variables however.
      singulars
      1. PO
      1. USBas Jansen
    2. COX,Y and Z are all of the same length. x and y are expected (and should) be difference size however. The data reflects time-based measurements where X is the time and Y,Z are the actual measurement points.
      singulars
      1. PO
      1. USBas Jansen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload