If you'd like to post .geo file and the .msh file to pastebin or gist, I'll take a look.
On Aug 13, 2013, at 9:08 PM, John Assael <[email protected]> wrote: > I dont know why but I get an empty array []... I am on MacOSX. > > > On Tue, Aug 13, 2013 at 11:02 PM, Guyer, Jonathan E. Dr. > <[email protected]> wrote: > If you import such a mesh, what happens if you `print > mesh.physicalCells.keys()`? > > > On Aug 13, 2013, at 2:42 PM, John Assael <[email protected]> wrote: > > > I also tried it with no success... I ended up defining the subdomains with > > equations using the x,y cellcenters. > > Thank you very much for your continuous help! > > > > > > On Tue, Aug 13, 2013 at 8:28 PM, Guyer, Jonathan E. Dr. > > <[email protected]> wrote: > > On Aug 13, 2013, at 9:29 AM, John Assael <[email protected]> wrote: > > > > > Hi, > > > I have a problem when I am saving my mesh from gmsh (.msh file), fipy > > > does not recognise the Physical Groups, that I have defined. > > > More specifically, although my .geo file contains entries like: Physical > > > Surface(100) = {37}; > > > when I try to access mesh.physicalCells[100] from fipy, I get a KeyError > > > for key '100' that does not exist. > > > However when I replicate this procedure with the .geo file the Physical > > > groups get recognised. > > > So, how can I access a surface in an already defined mesh file? > > > > Try mesh.physicalCells["100"]. The keys are strings. > > > > > > > > > > _______________________________________________ > > fipy mailing list > > [email protected] > > http://www.ctcms.nist.gov/fipy > > [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] > > > > > > > > -- > > ..:: ic3man.gr ::.. > > software | design | development > > _/_/_/ email: [email protected] > > _/_/_/ www : http://www.ic3man.gr > > ------------------------------------------------------------------ > > This e-mail and any attachments are confidential. You may not copy > > or disseminate any information contained in them to anyone other > > than the intended recipient. If you are not the intended recipient > > please contact the sender by reply e-mail and destroy all copies > > of the original message immediately. > > ------------------------------------------------------------------ > > _______________________________________________ > > 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 ] > > > > -- > ..:: ic3man.gr ::.. > software | design | development > _/_/_/ email: [email protected] > _/_/_/ www : http://www.ic3man.gr > ------------------------------------------------------------------ > This e-mail and any attachments are confidential. You may not copy > or disseminate any information contained in them to anyone other > than the intended recipient. If you are not the intended recipient > please contact the sender by reply e-mail and destroy all copies > of the original message immediately. > ------------------------------------------------------------------ > _______________________________________________ > 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 ]
