I copied it from the website. I find it easier to learn/understand code when I retype it. That said, Gmsh is working when I run the file from github. I hadn't tried that before. I guess it raises the question of why Gmsh is giving me errors when I copy the exact same code into a new script by hand.
For what it's worth, here's what I was trying to run before. I think you'll see the Gmsh code is the same as what is in your example On Thu, Mar 24, 2016 at 3:53 PM, Guyer, Jonathan E. Dr. (Fed) < [email protected]> wrote: > OK, thank you. > > Diffusion_Circle.py is not the name of our example; did you just copy it > or has it been changed in any way? What happens if you run > examples/diffusion/circle.py as-is? > > If they haven't been deleted already, please email me the files > c:\users\ddesan~1\appdata\local\temp\tmpzs_8ji.msh > c:\users\ddesan~1\appdata\local\temp\tmp2hf2nq.geo > > > > On Mar 24, 2016, at 1:17 PM, Daniel DeSantis <[email protected]> wrote: > > > Ok, I don't know what changed, but I reinstalled literally everything on > my system. Python, fipy, gmsh, etc. It seems, for the moment that gmsh 2.11 > is reading now. I'm still getting the error about not producing any cells. > > > > To answer your questions, I'm running Windows 7 Professional. > > > > Running gmsh --version at the command line gets me Gmsh 2.11.0 > > > > Here's the errors from running the circle example: > > > > Exception WindowsError: (32, 'The process cannot access the file because > it is being used by another process', > 'c:\\users\\ddesan~1\\appdata\\local\\temp\\tmpzs_8ji.msh') in <bound > method MSHFile.__del__ of <fipy.meshes.gmshMesh.MSHFile instance at > 0x0000000019FE09C8>> ignored > > Traceback (most recent call last): > > > > File "<ipython-input-8-44aa13cad657>", line 1, in <module> > > > runfile('C:/Users/ddesantis/Dropbox/PythonScripts/FiPy/Diffusion_Circle.py', > wdir='C:/Users/ddesantis/Dropbox/PythonScripts/FiPy') > > > > File > "C:\Users\ddesantis\AppData\Local\Continuum\Anaconda2\lib\site-packages\spyderlib\widgets\externalshell\sitecustomize.py", > line 699, in runfile > > execfile(filename, namespace) > > > > File > "C:\Users\ddesantis\AppData\Local\Continuum\Anaconda2\lib\site-packages\spyderlib\widgets\externalshell\sitecustomize.py", > line 74, in execfile > > exec(compile(scripttext, filename, 'exec'), glob, loc) > > > > File > "C:/Users/ddesantis/Dropbox/PythonScripts/FiPy/Diffusion_Circle.py", line > 27, in <module> > > ''' % locals()) > > > > File > "C:\Users\ddesantis\AppData\Local\Continuum\Anaconda2\lib\site-packages\fipy\meshes\gmshMesh.py", > line 1585, in __init__ > > self._orderedCellVertexIDs_data) = self.mshFile.read() > > > > File > "C:\Users\ddesantis\AppData\Local\Continuum\Anaconda2\lib\site-packages\fipy\meshes\gmshMesh.py", > line 809, in read > > raise GmshException(errStr) > > > > GmshException: Gmsh hasn't produced any cells! Check your Gmsh code. > > > > Gmsh output: > > Info : Running 'gmsh > c:\users\ddesan~1\appdata\local\temp\tmp2hf2nq.geo -2 -nopopup -format msh > -o c:\users\ddesan~1\appdata\local\temp\tmpisuemv.msh' [Gmsh 2.11.0, 1 > node, max. 1 thread] > > Info : Started on Thu Mar 24 13:13:57 2016 > > Info : Reading 'c:\users\ddesan~1\appdata\local\temp\tmp2hf2nq.geo'... > > Info : Done reading > 'c:\users\ddesan~1\appdata\local\temp\tmp2hf2nq.geo' > > Info : Meshing 1D... > > Info : Done meshing 1D (0 s) > > Info : Meshing 2D... > > Info : Done meshing 2D (0 s) > > Info : 1 vertices 1 elements > > Info : Writing 'c:\users\ddesan~1\appdata\local\temp\tmpisuemv.msh'... > > Info : Done writing > 'c:\users\ddesan~1\appdata\local\temp\tmpisuemv.msh' > > Info : Stopped on Thu Mar 24 13:13:57 2016 > > > > On Thu, Mar 24, 2016 at 12:49 PM, Guyer, Jonathan E. Dr. (Fed) < > [email protected]> wrote: > > What platform are you running on? > > > > Gmsh 2.0 is ancient and it's possible we've broken compatibility in some > way (although I don't think so). What happens if you type `gmsh --version` > at the command-line with one of the newer versions of Gmsh you've tried? > > > > > > On Mar 24, 2016, at 11:56 AM, Daniel DeSantis <[email protected]> > wrote: > > > > > Trevor, > > > > > > I have tried the develop branch and up-to-date Gmsh version. I had to > back it up to Gmsh 2.0 to avoid the error. Not sure why that seems to be. > > > > > > Thanks, > > > > > > Dan > > > > > > On Thu, Mar 24, 2016 at 11:43 AM, Keller, Trevor (Fed) < > [email protected]> wrote: > > > Hi Daniel, > > > > > > > > > examples/diffusion/circle.py executes cleanly for me, with FiPy > 3.1-dev131-g77851ef and Gmsh 2.11.0. > > > > > > This looks like an installation problem. The up-to-date FiPy codebase > should work smoothly with more recent versions of Gmsh than 2.0. From your > post, it's unclear whether you've recently pulled the develop branch from > github, or manually applied the changes in that pull request to an older > release. Please update both Gmsh and FiPy, then post the specific error > messages it returns. > > > > > > > > > Thanks, > > > > > > Trevor > > > > > > > > > From: [email protected] <[email protected]> on behalf of > Daniel DeSantis <[email protected]> > > > Sent: Wednesday, March 23, 2016 4:09 PM > > > To: FIPY > > > Subject: Error: Gmsh hasn't produced any cells! > > > > > > Hello, > > > > > > I'm getting an error when trying to run the diffusion circle example. > I keep getting the following error: > > > > > > GmshException: Gmsh hasn't produced any cells! Check your Gmsh code. > > > > > > Gmsh output: > > > > > > > > > I'm running Gmsh 2.0. Any other version gives me errors with the > version number despite having fixed the error as described here: > https://github.com/usnistgov/fipy/pull/442 > > > > > > > > > Does anyone have any suggestions on how I can get Gmsh to produce the > cells it's supposed to? Or perhaps someone could explain a different method > of importing a gmsh file? I don't mind creating something in gmsh and then > importing it separately if that's easier? > > > > > > Thank you! > > > > > > -- > > > Daniel DeSantis > > > > > > > > > > > > _______________________________________________ > > > fipy mailing list > > > [email protected] > > > http://www.ctcms.nist.gov/fipy > > > [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] > > > > > > > > > > > > > > > -- > > > Daniel DeSantis > > > > > > > > > _______________________________________________ > > > fipy mailing list > > > [email protected] > > > http://www.ctcms.nist.gov/fipy > > > [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] > > > > > > _______________________________________________ > > fipy mailing list > > [email protected] > > http://www.ctcms.nist.gov/fipy > > [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] > > > > > > > > -- > > Daniel DeSantis > > > > > > _______________________________________________ > > fipy mailing list > > [email protected] > > http://www.ctcms.nist.gov/fipy > > [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] > > > _______________________________________________ > fipy mailing list > [email protected] > http://www.ctcms.nist.gov/fipy > [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] > -- Daniel DeSantis
Diffusion_Circle.py
Description: Binary data
_______________________________________________ fipy mailing list [email protected] http://www.ctcms.nist.gov/fipy [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
