Numpy for maya 2019

JHarford · November 28, 2019, 1:11pm

I have a couple questions releating to Numpy -

First : Has anyone built Numpy for Maya 2019 ? I have searched far and wide and have found no results as of yet. Only Maya 2018 <

Second : If I use functions from a Numpy lib or other module for a commercial or distributable plug-in, do those then also need to be included in the plugin distibution and is there an additional license for that.

Thanks

tfox_TD · November 28, 2019, 6:09pm

The numpy for Maya 2018 on Windows works for 2019. We’re using it at work.

Also, the numpy license is really short, pretty straightforward, and really permissive. I’m no lawyer, but what I see is, as long as you include that license text somewhere in your docs, you should be fine.

JHarford · November 29, 2019, 12:34am

Thanks tFox - All installed ! and good to know about the license.

While I’ve got you , - has getRawPoints() been removed entirely now ? It’s not accessible through python in 19 and has been removed from the C++ API docs as far as I can tell.
I’m looking for the fastest way to get data into numpy arrays.

tfox_TD · November 29, 2019, 9:41pm

Hmm, I haven’t used getRawPoints() in a while, so I didn’t even realize it was gone. That always seemed a bit hack-ish to me anyway. The module I wrote uses the more consistent get methods to do the IO.

gist.github.com

https://gist.github.com/tbttfox/9ca775bf629c7a1285c27c8d9d961bca

mayaToNumpy.py

from maya import OpenMaya as om
import numpy as np
from ctypes import c_float, c_double, c_int, c_uint

_CONVERT_DICT = {
	om.MPointArray:		  (float, 4, c_double, om.MScriptUtil.asDouble4Ptr),
	om.MFloatPointArray:  (float, 4, c_float , om.MScriptUtil.asFloat4Ptr),
	om.MVectorArray:	  (float, 3, c_double, om.MScriptUtil.asDouble3Ptr),
	om.MFloatVectorArray: (float, 3, c_float , om.MScriptUtil.asFloat3Ptr),
	om.MDoubleArray:	  (float, 1, c_double, om.MScriptUtil.asDoublePtr),

This file has been truncated. show original

JHarford · June 7, 2020, 1:53pm

Hey tfox,

Hope you’re well in these odd times.
Do you have an updated version of this script please ? As It is not working with maya 2019/20.

Thanks,
Joe

tfox_TD · June 7, 2020, 2:02pm

I’ve been using it just fine in Maya 2019 and 2020. What errors are you getting?

JHarford · June 7, 2020, 2:20pm

Hey Tyler,
I was just emailing you back. I had an old version that threw up some errors. I see you updated it and grabbed the latest off the github.
No errors now. I’m reading through it to make sure I understand how to use it.
I’m currently using

meshFn.getPoints(om.MSpace.kWorld)

of an object, creating a np array from that, doing some numpy magic and setting it back with

gen = (om.MPoint(x) for x in self.currentPos)
self.meshFn.setPoints(gen, om.MSpace.kWorld)

I’m hoping to use your script to bypass those timecoming elements.

JHarford · June 7, 2020, 2:30pm

It may be that i’m just not understanding how to pass in the right information into the inPtAttr.
If you wouldn’t mind explaining what the attr or how to find that plug, might look like for the point data for example, I should be on the right track.
Thanks again

tfox_TD · July 30, 2020, 4:46pm

First, this is API 1.0 ONLY. It looks like you’re trying to use api 2.0

There’s 2 sets of functions in that module mayaToNumpy/numpyToMaya and getNumpyAttr/setNumpyAttr

The first set is used to convert between OpenMaya and numpy arrays. The second set is for setting data directly to node attributes. Since you’re working with an MFnMesh, then you’ll want to use the first set like this to get the data:

mpoints = om.MPointArray()
meshFn.getPoints(mpoints)
points = mayaToNumpy(mpoints)

And like this to set the data:

mpoints = numpyToMaya(points, om.MPointArray)
meshFn.setPoints(mpoints)

JHarford · June 7, 2020, 3:23pm

Thanks Tyler.
1.0 solved my issues.

This is approx - 2.5 * faster and I suspect that will scale with the amount of data.

Great work on this script, and really appreciate the help