ufunc data seems to be missing #144

Activity

1. rgommers

   added

   bugSomething isn't workingSomething isn't working

   on Feb 4, 2021
2. kgryte commented on Feb 4, 2021

   

   kgryte

   on Feb 4, 2021

   Contributor

   More actions

   Does this have to do with the Python-C bridge? Meaning, I am not sure that the tooling currently picks up C-level argument handling, which could be applicable for ufuncs.
3. rgommers commented on Feb 4, 2021

   

   rgommers

   on Feb 4, 2021

   MemberAuthor

   More actions

   Ah yes, that's it (unfortunately). Pretty much all functions that are not ufuncs have a thin Python shim and will be picked up, ufuncs aren't.

   👍React with 👍1Reacted by Athan
4. rgommers

   added

   enhancementNew feature or requestNew feature or request

   and removed

   bugSomething isn't workingSomething isn't working

   on Feb 4, 2021
5. saulshanabrook commented on Apr 5, 2021

   

   saulshanabrook

   on Apr 5, 2021

   Contributor

   More actions

   The ufunc data is available, see in the file you referenced:
    

   # usage.dask: 58
   # usage.hvplot: 1
   # usage.koalas: 5
   # usage.matplotlib: 127
   # usage.networkx: 5
   # usage.orange3: 6
   # usage.pandas: 34
   # usage.prophet: 2
   # usage.scipy: 296
   # usage.seaborn: 1
   # usage.skimage: 51
   # usage.sklearn: 32
   # usage.statsmodels: 47
   # usage.xarray: 30
   sin: numpy.ufunc

   Since ufuncs are a custom object, not just a function, we record them as such. If you then look at the same file, you will see a class ufunc which has the overloads for all the calls:

   class ufunc:
   
       # usage.dask: 1
       __module__: ClassVar[object]
   
       @overload
       def __call__(self, _0: pandas.core.frame.DataFrame, _1: int, /):
           """
           usage.dask: 85
           usage.koalas: 24
           """
           ...
   
       @overload
       def __call__(self, _0: int, _1: int, /):
           """
           usage.dask: 1
           usage.koalas: 1
           usage.matplotlib: 2
           usage.scipy: 135
           usage.skimage: 1
           usage.sklearn: 3
           usage.statsmodels: 10
           usage.xarray: 4
           """
           ...

   ---

   So it is currently showing the number of times each ufunc is retrieved from the ufunc module (the first stats) and then also how ufuncs are called generally (the second stats).

   We could also show the product of these, showing per ufunc instance how it's called.

   Currently, ufuncs all show up as defined in the numpy module, because it's hard to find where they were defined (#70)

   👍React with 👍1Reacted by Athan
6. mattip commented on Sep 5, 2025

   

   mattip

   on Sep 5, 2025

   More actions

   In numpy/numpy#29675 this subject came up in connection with the where kwarg. I see it is used in class ufunc (rarely). So that is for all ufuncs together, right?

   1. Is there a way to figure out which ufunc is actually being used?
   2. There is a usage like this

   def __call__(
           self,
           _0: object,
           /,
           *_args: object,
           out: object = ...,
           dtype: Union[type, Literal["float64", "float32"], numpy.dtype] = ...,
           casting: Literal["no", "unsafe"] = ...,
           axis: int = ...,
           where: Union[bool, numpy.ndarray, numpy.bool_] = ...,
           sig: str = ...,
           output_dtypes: Union[Tuple[Type[float], Type[float]], Type[float]] = ...,
       ):
   

   with a lot of hits. That looks like a static typing call, and not an actual code usage, correct?

   The actual subject of this issue "ufunc data seems to be missing" has been answered, can the issue be closed?