Error (missing file for blas 3.3.0 ?)
by Darcoux Christine
Hi
I am trying to run the heat.py example. I have installed
boost-numeric-bindings from GIT, but the heat example still fails with
the following error :
In file included from
/tmp/codepy-compiler-cache-v5-uid1000/717268f4a00443b963da108fc3daed63/module.cpp:2:0:
/usr/include/hedge/volume_operators.hpp:31:49: fatal error:
boost/numeric/bindings/blas/blas3.hpp: No such file or directory
compilation terminated.
I am using blas version 3.3.0.
Help would be appreciated.
Christine
8 years, 10 months
Trying to Read From Gmsh
by Daniel Gempesaw
Hi,
I'm trying to read in a geometry/mesh from gmsh into hedge. Using the
generate_gmsh function gives a strange error, there is no apparent syntax
error (semicolons and quotation marks all appropriately placed, as far as I
can tell.) It's somehow expecting the end of the file halfway through the
last line; I tried switching around which line was last to no avail.
>>> from hedge.mesh.reader.gmsh import generate_gmsh
>>> CHANNEL = """
... Point(1) = {0, 0, 0, 0.01};
... Point(2) = {0, 10, 0, 0.01};
... Point(3) = {40, 10, 0, 0.01};
... Point(4) = {40, 0, 0, 0.01};
... Point(5) = {30, 0, 0, 0.01};
... Point(6) = {30, 2.5, 0, 0.01};
... Point(7) = {25, 2.5, 0, 0.01};
... Point(8) = {25, 0, 0, 0.01};
... Point(9) = {20, 0, 0, 0.01};
... Point(10) = {20, 2.5, 0, 0.01};
... Point(11) = {15, 2.5, 0, 0.01};
... Point(12) = {15, 0, 0, 0.01};
... Line(1) = {1, 2};
... Line(2) = {2, 3};
... Line(3) = {3, 4};
... Line(4) = {4, 5};
... Line(5) = {5, 6};
... Line(6) = {6, 7};
... Line(7) = {7, 8};
... Line(8) = {8, 9};
... Line(9) = {9, 10};
... Line(10) = {10, 11};
... Line(11) = {11, 12};
... Line(12) = {12, 1};
... Physical Line("noslip") = {2, 4, 5, 7, 8, 9, 11, 12, 6, 10};
... Physical Line("inflow") = {1};
... Physical Line("outflow")= {3};"""
>>> generate_gmsh(CHANNEL, 2)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/daniel/karen/src/hedge/hedge/mesh/reader/gmsh.py", line 315,
in generate_gmsh
runner.__enter__()
File "/home/daniel/karen/src/meshpy/meshpy/gmsh.py", line 88, in __enter__
raise GmshError(msg)
meshpy.gmsh.GmshError: gmsh execution failed with message:
Info : Running 'gmsh -2 -o /tmp/tmpC_qzkG/output.msh -nopopup
/tmp/tmpC_qzkG/temp.geo'
Info : Started on Wed Feb 23 19:11:14 2011
Info : Reading '/tmp/tmpC_qzkG/temp.geo'
Info : Read '/tmp/tmpC_qzkG/temp.geo'
Info : Meshing 1D...
Info : Meshing curve 1 (Line)
Info : Meshing curve 2 (Line)
Info : Meshing curve 3 (Line)
Info : Meshing curve 4 (Line)
Info : Meshing curve 5 (Line)
Info : Meshing curve 6 (Line)
Info : Meshing curve 7 (Line)
Info : Meshing curve 8 (Line)
Info : Meshing curve 9 (Line)
Info : Meshing curve 10 (Line)
Info : Meshing curve 11 (Line)
Info : Meshing curve 12 (Line)
Info : Mesh 1D complete (0.008 s)
Info : Meshing 2D...
Info : Mesh 2D complete (0 s)
Info : 10990 vertices 11002 elements
Info : Writing '/tmp/tmpC_qzkG/output.msh'
Info : Wrote '/tmp/tmpC_qzkG/output.msh'
Info : Stopped on Wed Feb 23 19:11:14 2011
Error : End of file in string
Error : '/tmp/tmpC_qzkG/temp.geo', line 27 : syntax error (utflow)
Error : End of file in string
So, I tried making the mesh manually using gmsh and reading that in using
read_gmsh, but I ran into a second error about how an LU decomposition
failed, which I fear may reflect a lack of memory? Any suggestions would be
welcome.
>>> mesh = read_gmsh(filename='channel.msh',force_dimension=None,
> periodicity=None,allow_internal_boundaries=True)
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "/home/daniel/karen/src/hedge/hedge/mesh/reader/gmsh.py", line 297,
> in read_gmsh
> tag_mapper=tag_mapper)
> File "/home/daniel/karen/src/hedge/hedge/mesh/reader/gmsh.py", line 531,
> in parse_gmsh
> hedge_el = el_class(el_nr, vertex_indices, hedge_vertices)
> File "/home/daniel/karen/src/hedge/hedge/mesh/element.py", line 59, in
> __init__
> self.inverse_map = map.inverted()
> RuntimeError: lu decomposition failed
Thanks,
Daniel Gempesaw
8 years, 10 months
Regression Check Failed
by Andreas Kloeckner
Hi there,
I'm sorry to report that the regression check failed.
Details are attached.
- Your guilty conscience
8 years, 11 months
square, naca results
by Islam El Salawi
Hi there,
Receiving results from the square and naca examples I am wondering if I
missed something to install. Cuda works fine and there are no errors, but
the results are far away from being realistic. I posted this problem
already once and I was asking if I took the right initialization settings.
But I am pretty sure that the error source is somewhere else. I've attached
a screenshot of the streamlines surrounding the square. As you can see the
vectors close to the noslip boundary condation on the wall of the square
are not null. The velocity range reaches from a value about 34 to a max of
37, although there are expected some negative velocities behind the square.
This can be observed for the naca example, too, though I didn't attach a
pic of its streamlines. But here are the error and out logs of the square
example. Maybe this helps to show where the problem is.
error log:
/home/elsalawi/src/hedge/hedge/optemplate/mappers/__init__.py:889:
UserWarning: No minimum degree for quadrature tag 'gasdyn_vol'
specified--falling back to nodal evaluation
"falling back to nodal evaluation" % expr.op.quadrature_tag)
/home/elsalawi/src/hedge/hedge/optemplate/mappers/__init__.py:889:
UserWarning: No minimum degree for quadrature tag 'gasdyn_face'
specified--falling back to nodal evaluation
"falling back to nodal evaluation" % expr.op.quadrature_tag)
/home/elsalawi/src/hedge/hedge/backends/cuda/__init__.py:230: UserWarning:
could not achieve Metis partition after 5 attempts, falling back to greedy
% attempt_count)
/home/elsalawi/src/hedge/hedge/discretization/__init__.py:1468:
UserWarning: hedge.discretization.Filter is deprecated. Use
hedge.optemplate.FilterOperator directly.
warn("hedge.discretization.Filter is deprecated. "
/home/elsalawi/src/env/lib/python2.6/site-packages/pycuda-2011.1-py2.6-linux-x86_64.egg/pycuda/compiler.py:112:
UserWarning: The CUDA compiler suceeded, but said the following:
ptxas warning : Too big maxrregcount value specified 256, will be ignored
+stdout+stderr)
/home/elsalawi/src/hedge/hedge/backends/cuda/fluxgather.py:765:
UserWarning: Flux count in flux execution plan different from actual flux
count.
You may want to specify the tune_for= kwarg in the Discretization
constructor.
warn("Flux count in flux execution plan different from actual flux
count.\n"
/home/elsalawi/src/hedge/hedge/vector_primitives.py:181: UserWarning: using
unoptimized linear combination routine
warn("using unoptimized linear combination routine")
out log:
4020 elements
microblocking=True -> time=0
actual flux exec plan: regs=51(+205) threads=36 smem=1712 occ=0.312500
pfaces=9 mbs_per_block=1 mb_elements=8 direct_store
actual diff op exec plan: seg_matrix regs=16(+48) threads=240 smem=2688
occ=1.000000 par=(p15) segment_size=16 unroll=10
actual flux local exec plan: seg_matrix regs=13(+51) threads=240 smem=3584
occ=1.000000 par=(p15) segment_size=16 unroll=12 prefetch_branch=True
---------------------------------------------
order 3
---------------------------------------------
#elements= 4020
step.max=0 | t_sim.max=0 | t_step.max=0.479783
step.max=1 | t_sim.max=4.44621e-05 | t_step.max=0.497759
step.max=2 | t_sim.max=8.89242e-05 | t_step.max=0.421514
step.max=3 | t_sim.max=0.000133386 | t_step.max=0.421752
step.max=4 | t_sim.max=0.000177848 | t_step.max=0.404847
step.max=5 | t_sim.max=0.000222311 | t_step.max=0.454917
step.max=6 | t_sim.max=0.000266773 | t_step.max=0.412949
step.max=7 | t_sim.max=0.000311235 | t_step.max=0.429991
step.max=8 | t_sim.max=0.000355697 | t_step.max=0.471234
step.max=9 | t_sim.max=0.000400159 | t_step.max=0.454614
step.max=10 | t_sim.max=0.000444621 | t_step.max=0.471272
...
Regards,
Islam
--
NEU: FreePhone - kostenlos mobil telefonieren und surfen!
Jetzt informieren: http://www.gmx.net/de/go/freephone
8 years, 11 months
Regression Check Failed
by Andreas Kloeckner
Hi there,
I'm sorry to report that the regression check failed.
Details are attached.
- Your guilty conscience
8 years, 11 months
Regression Check Failed
by Andreas Kloeckner
Hi there,
I'm sorry to report that the regression check failed.
Details are attached.
- Your guilty conscience
8 years, 11 months
Regression Check Failed
by Andreas Kloeckner
Hi there,
I'm sorry to report that the regression check failed.
Details are attached.
- Your guilty conscience
8 years, 11 months
Regression Check Failed
by Andreas Kloeckner
Hi there,
I'm sorry to report that the regression check failed.
Details are attached.
- Your guilty conscience
8 years, 11 months
Regression Check Failed
by Andreas Kloeckner
Hi there,
I'm sorry to report that the regression check failed.
Details are attached.
- Your guilty conscience
8 years, 11 months
Regression Check Failed
by Andreas Kloeckner
Hi there,
I'm sorry to report that the regression check failed.
Details are attached.
- Your guilty conscience
8 years, 11 months
