New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gmsh2D does not respect background mesh #326
Comments
In the course of diagnosing and fixing this, I found that
Trac comment by guyer on 06-29-2012 at 14:41 |
Fixed with r5253 Trac comment by guyer on 06-29-2012 at 16:22 |
In 557e653:
Trac comment by Jonathan E. Guyer guyer@nist.gov on 06-12-2013 at 14:14 |
In 1acb86c:
Trac comment by Jonathan E. Guyer guyer@nist.gov on 06-12-2013 at 14:14 |
In 9b616ba:
Trac comment by Jonathan E. Guyer guyer@nist.gov on 06-12-2013 at 14:14 |
In 2861b2a:
Trac comment by Jonathan E. Guyer guyer@nist.gov on 06-12-2013 at 14:14 |
In 56ebe4d:
Trac comment by Jonathan E. Guyer guyer@nist.gov on 06-12-2013 at 14:14 |
Marking milestone Trac comment by guyer on 09-30-2013 at 21:44 |
The same mesh is generated in both cases.
This turns out to be a problem with the writing of the POSFile for the background
There are a couple of problems with this.
cellTopology == t["triangle"]
view-name
(just after$View
) is emptyvar.name
is''
It turns out that some other 2D meshes don't even get this far
This turns out to be due to
nodes[~nodes.mask]
in [trunk/fipy/meshes/gmshImport.py@5233#L352 POSFile._writeValue()]Imported from trac ticket #448, created by guyer on 06-29-2012 at 09:02, last modified: 09-30-2013 at 21:44
The text was updated successfully, but these errors were encountered: