Giter Club home page Giter Club logo

engrid's People

Contributors

ftpronk avatar mtav avatar ogloth avatar opoplawski avatar petebachant avatar philippose avatar wyldckat avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

engrid's Issues

Error message when starting Mesh -> Create/improve surface mesh

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
16 [enGrid] bug block always 2011-10-10 19:05 2011-12-23 18:38

Reporter: skandersen Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 1.3beta  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: Error message when starting Mesh -> Create/improve surface mesh
Description: I am trying to follow the Damper tutorial but with my own geometry. When I get to the step "Mesh -> Create/improve surface mesh" the following error message is displayed:

This seems to be a bug in enGrid

file: updatedesiredmeshdensity.cpp
line:248
Steps To Reproduce:
Additional Information:
Attached Files: 1197_in_shaft.tar.gz (445 KB) 2011-10-10 19:05

Hierarchical boundary code assignment

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
17 [enGrid] feature request feature sometimes 2011-12-23 18:53 2011-12-23 18:53

Reporter: wyldckat Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 1.3beta  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: Hierarchical boundary code assignment
Description: After the Issue 0000015 was processed, the following conclusion was reached:
   enGrid needs a better assignment system for boundary codes, specially in highly complex geometries.

The idea is to have at least a two level boundary code assignment system, where the primary layer is the one already existing, while the second would be used for listing boundary codes that are associated to the parent boundary code.
Steps To Reproduce:
Additional Information: Example - On the Damper Duct tutorial, there could be 3 parent boundary codes and then each have their own children:
  Symmetry_plane - code 1
  Duct - code 2:
    back (3)
    top (4)
    bottom (5)
    left (6)
    right (7)

  Damper - code 8:
    top (9)
    bottom (10)
    left (11)
    right (12)
    back (13)

Name merging could then happen behind the scenes, translating for example to:
  Duct_back (3)
  Duct_top (4)
  Duct_bottom (5)
  Duct_left (6)
  Duct_right (7)

The Duct code 2 would then only be occupied for the children reference system.
Attached Files:

Old 1.2 settings still exist the Settings dialog on enGrid 1.3

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
12 [enGrid] feature request minor always 2011-09-08 08:25 2011-09-08 09:38

Reporter: wyldckat Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 1.3beta  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: Old 1.2 settings still exist the Settings dialog on enGrid 1.3
Description: Outdated settings still crawl into the Global Settings dialog (menu Tools -> Configure enGrid).
Some form of deactivation or clean up should be put into practice, specially since people are at the moment using both 1.2 and 1.3 versions of enGrid.
Steps To Reproduce:
Additional Information:
Attached Files:

no-return-in-nonvoid-function

Hello!
I can not build a package in OBS.
OBS has a RPMLINT check and its output gave me the following errors:

[ 935s] E: engrid no-return-in-nonvoid-function /home/abuild/rpmbuild/BUILD/engrid-2.0.0git.20150324/src/build/libengrid/../../libengrid/cadinterface.h:125, 126
[ 935s] E: engrid no-return-in-nonvoid-function /home/abuild/rpmbuild/BUILD/engrid-2.0.0git.20150324/src/build/libengrid/../../libengrid/edgelengthsource.h:43
[ 935s] E: engrid no-return-in-nonvoid-function /home/abuild/rpmbuild/BUILD/engrid-2.0.0git.20150324/src/libengrid/cadinterface.h:125, 126
[ 935s] E: engrid no-return-in-nonvoid-function /home/abuild/rpmbuild/BUILD/engrid-2.0.0git.20150324/src/libengrid/cgaltricadinterface.cpp:292, 297
[ 935s] E: engrid no-return-in-nonvoid-function /home/abuild/rpmbuild/BUILD/engrid-2.0.0git.20150324/src/libengrid/edgelengthsource.h:43

Thank you for the attention, hope this report helps development.

create surface mesh always results in crash

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8 [enGrid] bug crash always 2011-08-28 20:59 2011-12-26 15:48

Reporter: dominikchrist Platform:  
Assigned To: wyldckat OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.3beta  
Product Build: Resolution: fixed  
Projection: none      
ETA: none  

Summary: create surface mesh always results in crash
Description: Hello everyone,

for testing, I created a simple cube using a CAD program. I can import the cube as STL without problems. Next, I want to create a surface mesh but engrid crashes everytime I click "ok" in the window called "surface mesher".

To reproduce:
1) Import->STL and select "Box.STL" (attached)
2) Mesh-> create/improve surface mesh and hit "ok"

Thanks for your help in advance
Best regards
-Dominik

Steps To Reproduce:
Additional Information:
Attached Files: Box.STL (1 KB) 2011-08-28 20:59

1.3 beta/1.2 on Win 7 and 1.2 on Ubuntu

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
10 [enGrid] bug crash always 2011-09-02 16:11 2011-12-26 15:55

Reporter: studioa Platform:  
Assigned To: wyldckat OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.3beta  
Product Build: Resolution: fixed  
Projection: none      
ETA: none  

Summary: 1.3 beta/1.2 on Win 7 and 1.2 on Ubuntu
Description: After preparing the mesh, once hit "create/improve surface mesh" EnGrid crashes. This did not happen with small (I've tried with a rectangular HVAC pipe).
Attached the .zip folder that contain: original Blender mesh, export to EnGrid, etc.

This example is set up to simulate a simple air flow in a room 10x15x8 feet, that has an "inlet" and an "outlet".

Similarly the program crashes with other files - that I can upload if needed.

Crashes happens running Win7, Win Vista and Ubuntu.

Thanks for your help and great work!
Steps To Reproduce:
Additional Information:
Attached Files: ROOM_10x15x8.zip (175 KB) 2011-09-02 16:11
SETTINGS_CRASH.zip (243 KB) 2011-09-08 14:29

Invalid cells in boundary layer

Hello,

I have tried to mesh a propeller blade with engrid. The surface mesh is created outside engrid with gmsh ("bamg" surface mesh algorithm).
I did the steps:

  1. import Gmsh ascii v2
  2. create prism boundary layer (default settings except "stretching factor" which is set to 1.7)
  3. create/improve volume mesh
  4. divide prismatic boundary layer
  5. export OpenFOAM (grid only)
    Everything works without errors, but the final mesh contains negative volume cells where the trailing edge hits the hub. The number of problem cells increases, if the "stretching factor" in step 2 is decreased.
    Perhaps this case is of interest as testcase for further code development. I put it here: http://kroegeronline.net/exchange/rotor_domain.tgz

I used engrid built from the current commit of the "release-1.4" branch.

Regards, Hannes

STL help mode for importing imperfect STL files

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6 [enGrid] feature request major sometimes 2011-07-28 16:27 2011-07-28 16:35

Reporter: wyldckat Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 1.3beta  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: STL help mode for importing imperfect STL files
Description: Actually this is currently an issue common to all current versions of enGrid.

Whenever we try to import an STL geometry that visually seems all OK, if there is a somewhat hidden imperfection, the whole import process is compromised!

It would be very helpful that there was an option for helping detect the problematic areas, so that these can be fixed during export/generation of the STL file. At least for people that don't have access or experience with advanced STL debugging applications.
Steps To Reproduce:
Additional Information:
Attached Files: zoom in.png (60 KB) 2011-07-28 16:27
Zoom out.png (140 KB) 2011-07-28 16:28
bug-feature-report.png (361 KB) 2011-07-28 16:29

Recent tests with Fedora 17 and Gcc 4.7.0

Seen in discussion http://engits.eu/vanilla/index.php?p=/discussion/287/compiling-error/ - there is a patch there: http://engits.eu/vanilla/index.php?p=/discussion/287/compiling-error/#Item_8

Two errors were triggered by Gcc 4.7.0:

  1. page defined in MultiPageWidgetPage* page is a redefinition made of another variable a few lines above. I have no idea how any other compiler allowed that to happen, even MSVC! Either way, Gcc 4.7.0 is a lot more stricter.
  2. File src/libengrid/guimainwindow.cpp - missing reference to dup and dup2, since they moved from their usual place onto a more proper place, namely unistd.h.

Problems with git clone in build.bash from release-1.4

Since I don't have permissions to modify the release-1.4 branch, here's the report ;) :

The latest build.bash (for reference, this one: https://github.com/enGits/engrid/blob/f9a76cc450d0610e015b540ef45bb1ff138cc90e/build.bash) is relying on the https address for the git clone.

The problem is that the https port doesn't always work, since some firewalls have issues with it. Therefore, I suggest the following code instead of a single clone:

for url_address in git://github.com/enGits/engrid.git \
    https://github.com/enGits/engrid.git \
    git://repo.or.cz/engrid-github.git \
    http://repo.or.cz/r/engrid-github.git; do

  if git clone $url_address engrid ; then
    break;
  else
    echo "Repository $url_address failed. Trying the next one..."
  fi
done

The ones at repo.or.cz were mirrors setup by me, because we already know from OpenFOAM that Github doesn't always work as expected, while repo.or.cz has been more reliable for some companies to use (due to firewall restrictions).

Buttons for exporting, importing and resetting global settings

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
11 [enGrid] feature request feature always 2011-09-08 07:50 2011-09-08 07:50

Reporter: wyldckat Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 1.3beta  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: Buttons for exporting, importing and resetting global settings
Description: After the incident with bug report 0000009, it came to me that 3 buttons (or some other interface method) should exist for ex/importing the global settings (menu Tools -> Configure enGrid), namely:
* Export;
* Import;
* Reset to default.
Steps To Reproduce:
Additional Information:
Attached Files:

Using the setting "minimal number of cells across" >0 will partially override rules

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
13 [enGrid] bug major always 2011-09-08 09:29 2012-03-30 10:33

Reporter: wyldckat Platform:  
Assigned To: ogloth OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 1.3beta  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: Using the setting "minimal number of cells across" >0 will partially override rules
Description: This was detected in bug 0000009, but this seems to be a global bug, not just related to the version for Windows.

Basically, if we follow the Damper Duct tutorial until the end of the section"http://engits.eu/wiki/index.php/Tutorials/Version1.3/DamperDuct#Improve_Damper_Edges", [^] while using the global setting "minimal number of cells across" with a value of 1, the defined rules in that tutorial section will not be properly followed.

Proof is in the attached file "enGrid 1.3_beta - rules not followed.png". When the aforementioned value is 0, then the image looks like the one in the tutorial: "enGrid 1.3_beta - rules followed.png"
Steps To Reproduce:
Additional Information:
Attached Files: enGrid 1.3_beta - rules not followed.png (233 KB) 2011-09-08 09:29
enGrid 1.3_beta - rules followed.png (219 KB) 2011-09-08 09:29

Finish updating compiling instructions for Windows+enGrid 1.4

Still need to finish updating instructions on the following wiki pages:

  • [[enGrid 1.4] Building on Windows with MSVC2008](../wiki/[enGrid 1.4] Building on Windows with MSVC2008)
  • [[enGrid 1.4] Building on Windows](../wiki/[enGrid 1.4] Building on Windows)
  • [[enGrid 1.4] Building the final installer for Windows with NSIS](../wiki/[enGrid 1.4] Building the final installer for Windows with NSIS)

projection error (wrong side of object)

Nodes sometime get projected to the wrong side of an object. A good example is a cylinder with just one boundary code for the whole 360 degrees. This is an issue with discrete (triangulated) geometries and might be handled by comparing the local mesh normal with the projected geometry normal.

catch NETGEN problems

Sometimes strange behaviour and bugs occur during the NETGEN library call. The problems often lead to memory flooding or crashes. Ideally problems should be detected and the NETGEN call should be aborted.

How this can be achieved is not clear to me at the moment.

Ubuntu 14.04 Compatibility

While running the build script in Ubuntu 14.04, the only thing I noticed was "/usr/bin/ld: cannot find -ltcl8.5"

The fix is simple: add tcl8.5 to the apt-get line.
A newer version probably gets installed instead of this one.

After installing this package and running the build script again, engrid launches. I don't know if it works yet.

Unable to split boundary surfaces after setting surface meshing parameters

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
14 [enGrid] bug major always 2011-09-15 14:57 2011-09-15 14:57

Reporter: wyldckat Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 1.3beta  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: Unable to split boundary surfaces after setting surface meshing parameters
Description: OS: Windows, but probably also happens in Linux.

Steps:
1. Define surfaces that belong to each boundary surface.
2. Go to the menu "Mesh -> edit surface parameters" and set parameters for each surface. In my case, I had only two boundary surfaces. Include dedicated rules for relating each surface.
3. Save the project and create the surface mesh.
4. Save the project in another file.

5. Go back to the first project (with another enGrid) and create new boundary surfaces, by taking some of them from the other surface boundaries.
6. Go to the menu "Mesh -> edit surface parameters" and a dialog appears with the message "This seems to be a bug in enGrid... libengrid\guicreatesurfacemesh.cpp; line:83"
Steps To Reproduce:
Additional Information: 7. Joining back the separated surfaces onto the original one will unblock the dialog.
8. Removing the dedicated rules and creating the new boundaries again will no longer block the dialog.
Attached Files:

libengrid\meshpartition.cpp(332) : warning C4553: '==' : operator has no effect; did you intend '='?

MSVC2008 gives this warning:

  libengrid\meshpartition.cpp(332) : warning C4553: '==' : operator has no effect; did you intend '='?

It refers to "found == true;" from here:

bool MeshPartition::hasBC(vtkIdType id_node, int bc)
{
  bool found = false;
  for (int j = 0; j < n2bcGSize(id_node); ++j) {
    if (n2bcG(id_node, j) == bc) {
      found == true;
      break;
    }
  }
  return found;
}

This is a clear indication that something is not right here...

Desktop mode and console

Hi,
this is no real issue but I'm beginning with that techno and I'd like to know if there is a way to use engrid with command lines only?

Cheers

meshing of multiple volumes does not work

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4 [enGrid] bug major always 2011-07-21 10:29 2011-07-21 10:30

Reporter: ogloth Platform:  
Assigned To: ogloth OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 1.3beta  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: meshing of multiple volumes does not work
Description: Volume meshing with multiple volumes and prismatic layers on the dividing surface is broken. It can be reproduced with the tutorials/03_TwoCubes from the GIT repository (branch release-1.3)
Steps To Reproduce:
Additional Information:
Attached Files:

Compiling under openSUSE 12.2

I am trying to compile the latest release-1.4 branch and I am getting the following errors:

guieditboundaryconditions.cpp: In member function ‘void GuiEditBoundaryConditions::setupSolvers()’:
guieditboundaryconditions.cpp:332:26: error: redeclaration of ‘MultiPageWidgetPage* page’
guieditboundaryconditions.cpp:312:3: error: ‘QString page’ previously declared here
make[2]: *** [release/guieditboundaryconditions.o] Error 1
make[2]: Leaving directory `/home/cfd/engrid/src/libengrid'
make[1]: *** [release] Error 2
make[1]: Leaving directory `/home/cfd/engrid/src/libengrid'
make: *** [sub-libengrid-libengrid-pro-make_default-ordered] Error 2

which branch should I use to compile under Linux?

Best regards,

George

Finish updating installation instructions and scripts for enGrid 1.4

On the wiki page [enGrid-1.4]-Installation, the instructions have been updated to expect the scripts (build.bash and setup_pathes.sh) to be fully merged from the branch window-1.4 to release-1.4.

Additionally, tests are still needed to confirm if these updates will work with the already mentioned Linux Distributions.

Further notes:

  • As mentioned, on the branch windows-1.4 you can find the updated scripts build.bash and setup_pathes.sh. I haven't tested these yet, since these are hard-coded in build.bash to work with the branch release-1.4...
  • ...And also because I haven't had time to test them either.
  • I propose that we use this issue report to divide the test machines into two or more parts and test them on virtual and/or real machines.
  • Already added openSUSE 12.2, Fedora 16+17 and Ubuntu 12.04 to the scripts and wiki page.

Blender import w loose verts

If the geometry exported from Blender has some loose geometry like detached vertices, Engrid segfaults upon create/improve surface mesh, even though engrid says the surface mesh is OK... so either the Blender export script has to make sure only surface related geometry is exported, or Engrid has to omit unused vertices when reading in...

Import surface mesh from Gmsh 2.6.1

Hello,

recently I got problems during import of gmsh surface meshes, created with latest version of gmsh. I guess this might be due to changes in the gmsh format.

For my case, the gmsh header contained an additional section between the keywords "$EndMeshFormat" and "$Nodes" with the patch names, which irritated engrid.
The current header looked like this:
$MeshFormat
2.2 0 8
$EndMeshFormat
$PhysicalNames
10
2 1 "rotor_upstream"
...
3 10 "blade"
$EndPhysicalNames
$Nodes
34428
...
.

To handle this, e.g. the following change around line 134 in gmshreader.cpp might be useful:

    /*
    f >> word;
    if (word != "$Nodes") EG_ERR_RETURN("$Nodes expected");
    */
    while (word != "$Nodes")
    {
        f >> word;
        if (f.status() != QTextStream::Ok) EG_ERR_RETURN("$Nodes expected");
    }

Regards, Hannes

High amount of used RAM after OpenFOAM mesh export

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
18 [enGrid] bug minor always 2012-01-12 10:06 2012-03-30 10:24

Reporter: unauthenticated Platform:  
Assigned To: ogloth OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 1.3beta  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: High amount of used RAM after OpenFOAM mesh export
Description: Hello,

this might be a litte "bug" I notice while working with this great tool (version 1.3beta on Ubuntu 10.04).
Before exporting my mesh (about 1.7m cells) engrid uses about 380 MB RAM, after the export of the OpenFOAM mesh is done, it drops back to 1060 MB.
Is this due to a feature, I did not consider or is there a missing deallocation of memory?


Greetings
Andreas
Steps To Reproduce:
Additional Information:
Attached Files:

"master branch" and "new concept" Installation

Hi all,
im succesfully installed engrid 1.4 in ubuntu 14.04 even having some troubles.
I would like how to install new concept version in such distro. I assume that I cannot use build.bash script because it is installing version 1.4.
Which installation method do I need to use in order to install these two new branches on my ubuntu?

Thnaks!

crash for boundary layer on parallel surfaces

Original report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2 [enGrid] bug minor always 2011-02-17 08:35 2011-02-17 08:36

Reporter: ogloth Platform:  
Assigned To: ogloth OS:  
Priority: normal OS Version:  
Status: assigned Product Version: GIT.master  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: crash for boundary layer on parallel surfaces
Description: The program crashes under the following condition:
  - a boundary layer is created on one surface
  - this surface is next to a surface without boundary layer
  - both surfaces are parallel

At least a decent error information should be given instead of a crash. In future versions it would be nice if this could be handled flawlessly.
Steps To Reproduce:
Additional Information:
Attached Files:

Unable to import cases created with OpenFOAM 2.3

As reported in this thread: http://www.cfd-online.com/Forums/engrid/138251-error-importing-openfoam-case-engrid.html - there is a new entry "inGroups" for each boundary in the file "constant/polyMesh/boundary".
For example, see the tutorial "incompressible/icoFoam/elbow".

Steps for solving this issue:

  1. Write in the FAQ about the workaround: http://www.cfd-online.com/Forums/engrid/138251-error-importing-openfoam-case-engrid.html#post500283
  2. Add compatibility in enGrid.

Windows only - error at "updatedesiredmeshdensity.cpp line 248" when starting the surface mesher

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7 [enGrid] bug major always 2011-08-03 10:44 2011-08-24 14:41

Reporter: wyldckat Platform:  
Assigned To: wyldckat OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.3beta  
Product Build: Resolution: fixed  
Projection: none      
ETA: none  

Summary: Windows only - error at "updatedesiredmeshdensity.cpp line 248" when starting the surface mesher
Description: One of the reports: http://engits.eu/vanilla/index.php?p=/discussion/comment/644/#Comment_644 [^]

Following the tutorial http://engits.eu/wiki/index.php/Tutorials/Version1.3/DamperDuct [^] will result in this same error, but only in Windows, both 32 and 64bit.
Steps To Reproduce:
Additional Information: As a side note, in enGrid 1.2 for Windows, after the surface mesher is done, it reports crazy values:

  total nodes : 10579
  total cells : 21190
897019412 direct projections
10693 full searches
secs. for class SurfaceMesher: 253


"direct projections" and "full searches" are not being initialized properly, hence the weird values. This is a minor issue and for now it didn't feel that it was necessary to open another bug report for it...
Attached Files:

facefinder.cpp:100: += on uninit data ?

facefinder.cpp:100:7: warning: variable 'ave_num_faces' is uninitialized when used here [-Wuninitialized]

  ave_num_faces += double(m_Faces[cell].size());

Suggest init local variable ave_num_faces to zero before first use.

Unable to export to and run with OpenFOAM 1.7, 2.0 and 2.1

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
19 [enGrid] bug major always 2012-03-14 11:43 2012-04-09 09:27

Reporter: wyldckat Platform:  
Assigned To: wyldckat OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 1.3beta  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: Unable to export to and run with OpenFOAM 1.7, 2.0 and 2.1
Description: This is a half-bug/half-feature request, because enGrid 1.3.0 is still not fully compatible with OpenFOAM versions (at least) after 1.6.x.

The necessary changes are:
* Exporting the case, with the file structure compliant with the latest versions. At least fvSchemes/divSchemes needs reviewing.
* For launching the solvers, it's necessary to update how the environment is handled. It's also possible that this was a problem only on Windows, but most likely the issue is related to problems with where the builds are located now. The current version places all builds inside a "platforms" folder.
Steps To Reproduce:
Additional Information:
Attached Files:

Boundary Layer mesh will not be created

Hello again,

I ran into problems when creating boundary layers on a geometry with several patches.
After creating the surface mesh, I wanted to create the boundary layers on 14 of the 20 available patches with 25k triangles (these patches are next to each other, if this is important). After my 32 GB of RAM where not enough for this task, I went to another workstation, where the creation of the boundary layers is runnig for about 24 hours now on a 2,4 GHz core using about 140 GB of RAM and not dropping any message to the logfiles or the terminal it was startet from since the following:

creating boundary layer mesh)
preparing prismatic layer


prism quads : 0
prism triangles : 0
stray quads : 0
stray triangles : 28538


WARNING: RestrictLocalH called, creating mesh-size tree

If you need it, I could post the engrid files, so you can work on this case.

Would be nice, if you could help me. Thank you.

Regards
Andreas

Cannot divide prism layer: "maximal increment : inf"

I have compiled the latest commit 1a26da5 in the "master" branch on github (in order to use the polyhedral mesh export) on Ubuntu 12.04 64bit.
Everything works so far except the step "divide prismatic boundary layer".
When I start it, I get the following output

dividing boundary layer into 11 layers:

maximal increment : inf
min(y) : 0
max(y) : 0

tol=0
secs. for undefined: 3

I have created the surface mesh with gmsh and imported it using Import >> GMSH (v2 ASCII).

I tracked some variables in GuiDivideBoundaryLayer::createEdges and the problem seems to be that the field "node_meshdensity_desired" contains only zeros. It seems to me that this is only set somewhere during surface meshing, but I'm not sure.

endless loop for volume meshing

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
5 [enGrid] bug major always 2011-07-22 08:30 2011-12-26 15:37

Reporter: bengits Platform:  
Assigned To: wyldckat OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.3beta  
Product Build: Resolution: fixed  
Projection: none      
ETA: none  

Summary: endless loop for volume meshing
Description: If no values for the edge lengths are present -- usually the case if volume meshing is called without meshing the surface in enGrid -- the program enters an endless loop
Steps To Reproduce:
Additional Information:
Attached Files:

Engrid crashes loading OpenFOAM meshes bigger than 16 Million cells

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
3 [enGrid] bug crash always 2011-06-07 13:51 2011-12-26 16:00

Reporter: ayoros00 Platform:  
Assigned To: ogloth OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 1.2  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: Engrid crashes loading OpenFOAM meshes bigger than 16 Million cells
Description: Hello,

Since I found Engrid very usefull, I tried it with different OpenFOAM meshes.

Everything goes fine with small meshes, but when it comes to bigger meshes (more than 16 million cells), Engrid crashes loading the OpenFOAM case.

To be sure it comes from mesh size, I tried with simple squares mesh with more or less cells.

Maybe this comes from my install, or from modifications I made.

I hope you can help me.

Thanks,
Fabien
Steps To Reproduce:
Additional Information:
Attached Files: _unknown_-bugreport.txt (25 KB) 2011-06-07 13:51

EnGrid 1.3 beta cannot save OpenFOAM complete case

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
15 [enGrid] bug minor always 2011-09-15 17:40 2011-12-23 18:56

Reporter: studioa Platform:  
Assigned To: wyldckat OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 1.3beta  
Product Build: Resolution: fixed  
Projection: none      
ETA: none  

Summary: EnGrid 1.3 beta cannot save OpenFOAM complete case
Description: Trying to save OF complete case will result in this error:

---------------------------
Error
---------------------------
This seems to be a bug in enGrid

file: ..\..\..\libengrid\simplefoamwriter.cpp
line:82


---------------------------
OK
---------------------------


The OF case folder is created, however it's incomplete.

Attached the .zip folder with EnGrid files and the OF case directory.

Running on Win 7.

I was able to reproduce the bug with two different files.

Thanks for your work!
Steps To Reproduce:
Additional Information:
Attached Files: DUCTS_4.zip (905 KB) 2011-09-15 17:40
snapshot01.png (218 KB) 2011-09-19 13:06
blender_separating_faces.jpg (660 KB) 2011-09-22 14:09
EnGrid_0.jpg (426 KB) 2011-09-22 14:10
EnGrid_1.jpg (533 KB) 2011-09-22 14:10
EnGrid_2.jpg (528 KB) 2011-09-22 14:11
OpenFOAM_error.jpg (542 KB) 2011-09-22 15:07
DUCT_S_shape_3D.zip (47 KB) 2011-09-22 15:08
proof_that_it_worked.png (127 KB) 2011-09-24 22:33
First3steps.zip (108 KB) 2011-09-24 22:39

export grid only to openfoam results in cpp error on line 82 of openfoamwriter.cpp

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
21 [enGrid] bug major always 2012-07-04 00:35 2012-07-04 20:53

Reporter: unauthenticated Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 1.3beta  
Product Build: Resolution: open  
Projection: none      
ETA: none  

Summary: export grid only to openfoam results in cpp error on line 82 of openfoamwriter.cpp
Description: see attached file, this is windows version
Steps To Reproduce:
Additional Information:
Attached Files: cylinder.egc (6 KB) 2012-07-04 00:35

Problems following the Damper tutorial in Windows

Original Report:

ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9 [enGrid] bug major always 2011-09-01 09:36 2011-09-07 15:16

Reporter: wyldckat Platform:  
Assigned To: wyldckat OS:  
Priority: normal OS Version:  
Status: closed Product Version: 1.3beta  
Product Build: Resolution: no change required  
Projection: none      
ETA: none  

Summary: Problems following the Damper tutorial in Windows
Description: Following the Damper tutorial for enGrid 1.3, the following section does not work as intended: http://engits.eu/wiki/index.php/Tutorials/Version1.3/DamperDuct#Improve_Damper_Edges [^]

Attached is the resulting output: bug_report_issue_009.png

It meshes too much. It doesn't look like it's obeying properly the rules.
Steps To Reproduce:
Additional Information:
Attached Files: bug_report_issue_009.png (125 KB) 2011-09-01 09:36
possible_bug_settings_01.png (36 KB) 2011-09-07 14:58
possible_bug_settings_02.png (51 KB) 2011-09-07 14:59
possible_bug_settings_03.png (49 KB) 2011-09-07 14:59
default_settings_01.png (37 KB) 2011-09-07 14:59
default_settings_02.png (51 KB) 2011-09-07 15:00
default_settings_03.png (51 KB) 2011-09-07 15:00

Comments from Fedora package review

I'm packaging enGrid for Fedora, and there were a few issues which per Packaging Guidelines ought to be reported upstream. The review is at [1]. The issues pointed out are

  • There are calls to exit in the libengrid library. These should be avoided.
  • There are files with unknown license:
    • ./src/dialoglineedit/dialoglineeditplugin.cpp
    • ./src/dialoglineedit/dialoglineeditplugin.h
    • ./src/dialoglineedit/test.cpp
  • Some changes needed to the qmake pro files might also be of interest: https://smani.fedorapeople.org/review/engrid_build.patch

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1111294

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.