Open GoogleCodeExporter opened 9 years ago
Whatever the problem is, let's make sfepy more robust to raise a meaningful
exception
at the right place. + a test for it.
Original comment by ondrej.c...@gmail.com
on 11 Jun 2008 at 3:25
I used "hg bisect" and here is what I got:
The first bad revision is:
changeset: 180:c73e7db416dd
user: Robert Cimrman <cimrman3@ntc.zcu.cz>
date: Tue May 06 18:03:32 2008 +0200
summary: fixed MatInQPDataCache to work with diffusion tensor in vertices,
in
well, I think it doesn't need any more comments. :) Do you know how to fix it?
Original comment by ondrej.c...@gmail.com
on 11 Jun 2008 at 11:00
This patch makes it run with the latest sfepy:
diff --git a/sfe/terms/cachesBasic.py b/sfe/terms/cachesBasic.py
--- a/sfe/terms/cachesBasic.py
+++ b/sfe/terms/cachesBasic.py
@@ -341,7 +341,7 @@ class MatInQPDataCache( DataCache ):
# dq_state_in_qp() works for vectors -> make a view of
# shape (nEl, nQP, nRow * nCol, 1).
- vshape = shape[0:2] + (nm.prod( mat.shape[1:] ), 1)
+ vshape = shape[0:2] + (mat.shape[1], 1)
## print self
## print self.shape, ckey
## print vshape
Could you please explain me (or even better in the comments in the sources)
what is
this supposed to do? And then let's write a test for this, as clearly it can be
broken sometimes.
Original comment by ondrej.c...@gmail.com
on 11 Jun 2008 at 11:12
I will check it. The problem is that the tests do not cover special solvers as
schroedinger.py - I will make a test veryfing if it runs.
Original comment by robert.c...@gmail.com
on 12 Jun 2008 at 11:20
Fixed (the input files).
Explanation: MatInQPDataCache is a class that can, for example, interpolate
material
data from vertices into Gauss points of the elements. The changeset 180
broadened the
possible input data shapes, but I forgot to fix also the schreodinger input
files.
Test it please.
Original comment by robert.c...@gmail.com
on 12 Jun 2008 at 11:58
Works well now. Thanks!
Original comment by ondrej.c...@gmail.com
on 12 Jun 2008 at 1:29
Migrated to http://github.com/sfepy/sfepy/issues/43
Original comment by robert.c...@gmail.com
on 30 Jan 2012 at 10:24
Original issue reported on code.google.com by
ondrej.c...@gmail.com
on 11 Jun 2008 at 3:21