Jonathan -- Thank you, this is exactly what I need. Two more questions.
1. Is the order of the vertices in faceVertexIDs important? 2. Is the order of faces in cellFaceIDs important? Must they wind clockwise or counterclockwise? Thanks, Jamie On Wed, Jun 15, 2016 at 1:56 PM, Guyer, Jonathan E. Dr. (Fed) < [email protected]> wrote: > The first three arguments to the Mesh2D constructor are (all that is) > required: > > class Mesh2D(Mesh): > def __init__(self, vertexCoords, faceVertexIDs, cellFaceIDs, ...): > > All other arguments have default values assigned. > > For your case: > > vertexCoords is of shape (2, N) where N is the number of vertices > faceVertexIDs is of shape (2, M) where M is the number of faces > cellFaceIDs is of shape (3, P) where P is the number of cells > > faceVertexIDs and cellFaceIDs are 0-based, as they are indices into the > preceding array > > > On Jun 15, 2016, at 1:29 PM, James Pringle <[email protected]> wrote: > > > > Well, I am motivated to give it a go, since I only have the summer to > make progress on project and it is blocking my research progress right now. > Can you give me a pointer to where the appropriate quantities are defined? > I can certainly write code to make the transformations, but it is a bit > hard without understanding precisely what is defined in the Mesh2D object. > I have made a simple Mesh2D object, but I am not sure which of the > attributes, etc, are absolutely required, or how they are precisely defined. > > > > Perhaps most useful for me would be > > • a definition of which parts of the Mesh2D object must exist > > • and the format of those parts, in particular the a face to > vertex array and a > > cell to face array > > Or you could point me to the appropriate part of the Gmsh code so I can > go from there. I presume poking around in fipy.Gmsh2D would be a good place > to start? Is there a better place to start? > > > > I would love any documentation on the details of the Mesh2D object. > > > > Thanks, > > Jamie Pringle > > University of New Hampshire > > > > On Wed, Jun 15, 2016 at 12:21 PM, Daniel Wheeler < > [email protected]> wrote: > > Hi Jamie, > > > > There is no automated way to make a FiPy mesh from Scipy's Delaunay > > object. The problem is that FiPy needs a face to vertex array and a > > cell to face array while the Delaunay object just has the cell to > > vertex array. The functionality to extract the face to vertex array > > and cell to face array is in FiPy because it must be done for Gmsh, > > however, it is not abstracted in so that it can be reused. > > > > It is certainly possible to make the correct arrays with Numpy and > > pass them to the Mesh2D object, but it's a bit of work to write the > > code. If I find some time I might give it a go, but I don't know when > > I will get to it. > > > > Cheers, > > > > Daniel > > > > On Tue, Jun 14, 2016 at 4:15 PM, James Pringle <[email protected]> wrote: > > > Daniel et al. -- > > > > > > As referenced earlier in this thread, I have a complex domain with > holes > > > in it; I now have it broken up into triangles, based on the Delaunay > package > > > in SciPy. I have > > > > > > Locations of all vertex coordinates, > > > list of vertices that make up faces > > > list of faces that make cells > > > list of faces that make up all the internal and external boundaries. > > > > > > Can you point me to any code or documentation that would help me > understand > > > how to make this into a Mesh2D object? I am having a devil of a time > > > figuring out from the manual online. The best would be something that > used > > > the output of either the triangles or scipy.spatial.Delaunay() > packaged. My > > > equation is of the form > > > > > > 0=J(Psi,A(x,y)) + \Del(B(x,y)*\Del Psi) > > > > > > > > > and I can get the coefficients A(x,y) and B(x,y) on either the faces > or in > > > the cell centers are needed. > > > > > > Thank you. > > > Jamie Pringle > > > University of New Hampshire > > > > -- > > Daniel Wheeler > > _______________________________________________ > > fipy mailing list > > [email protected] > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ctcms.nist.gov_fipy&d=CwICAg&c=c6MrceVCY5m5A_KAUkrdoA&r=oMf1-WHpUHeD7kN3S7612CDdF2TDPqDF9R-n-71Ks1Y&m=Q6M6XDjzGDlxMDgrY-riZ7Q70Abl5Aq7SRrTwZNYsws&s=yiO9QAq_3EUy9lVY5F76Tc9mnaB5Ubclilpum_QCUOE&e= > > [ NIST internal ONLY: > https://urldefense.proofpoint.com/v2/url?u=https-3A__email.nist.gov_mailman_listinfo_fipy&d=CwICAg&c=c6MrceVCY5m5A_KAUkrdoA&r=oMf1-WHpUHeD7kN3S7612CDdF2TDPqDF9R-n-71Ks1Y&m=Q6M6XDjzGDlxMDgrY-riZ7Q70Abl5Aq7SRrTwZNYsws&s=yIJJw-iQknimZfYCRrZmk7V2eHSJrCtcAehgVbGeiDk&e= > ] > > > > _______________________________________________ > > fipy mailing list > > [email protected] > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ctcms.nist.gov_fipy&d=CwIGaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=oMf1-WHpUHeD7kN3S7612CDdF2TDPqDF9R-n-71Ks1Y&m=iGk4QC0NEBSkRipnXJcMmV0qOdCYUWc6oQMIUpAmqyI&s=1tQAVl8UCyd9BiwQBhF_rRh-tByp33vxeyiD9YAxw3E&e= > > [ NIST internal ONLY: > https://urldefense.proofpoint.com/v2/url?u=https-3A__email.nist.gov_mailman_listinfo_fipy&d=CwIGaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=oMf1-WHpUHeD7kN3S7612CDdF2TDPqDF9R-n-71Ks1Y&m=iGk4QC0NEBSkRipnXJcMmV0qOdCYUWc6oQMIUpAmqyI&s=7yd1h-JO1QFeqXahL2kb-tCDlDKBlKe_3W98fKFBlj0&e= > ] > > > _______________________________________________ > fipy mailing list > [email protected] > > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ctcms.nist.gov_fipy&d=CwIGaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=oMf1-WHpUHeD7kN3S7612CDdF2TDPqDF9R-n-71Ks1Y&m=iGk4QC0NEBSkRipnXJcMmV0qOdCYUWc6oQMIUpAmqyI&s=1tQAVl8UCyd9BiwQBhF_rRh-tByp33vxeyiD9YAxw3E&e= > [ NIST internal ONLY: > https://urldefense.proofpoint.com/v2/url?u=https-3A__email.nist.gov_mailman_listinfo_fipy&d=CwIGaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=oMf1-WHpUHeD7kN3S7612CDdF2TDPqDF9R-n-71Ks1Y&m=iGk4QC0NEBSkRipnXJcMmV0qOdCYUWc6oQMIUpAmqyI&s=7yd1h-JO1QFeqXahL2kb-tCDlDKBlKe_3W98fKFBlj0&e= > ] >
_______________________________________________ fipy mailing list [email protected] http://www.ctcms.nist.gov/fipy [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
