pygraphistry

pygraphistry copied to clipboard

**Describe the bug** * PlotterBase is not in the main nav * Plottable is not in the main nav We should have a few descriptions at the top of each...

lmeyerov

**Describe the bug** Each nav sections should expand to show methods, not just class names 

lmeyerov

**Describe the bug** All the `(compute|layout)_(cugraph|igraph)` methods support different built-in algorithms, which are explicitly lists in variables like https://github.com/graphistry/pygraphistry/blob/master/graphistry/plugins/cugraph.py#L167 However, the docs do not expose & link those, so users...

lmeyerov

**Describe the bug** 2  nav issues - [ ] `graphistry.plugins.cugraph` is missing from the nav - [ ] methods are not listed in the nav for...

lmeyerov

[FEA] faiss-gpu support

1

**Is your feature request related to a problem? Please describe.** We are getting some conda version conflicts with faiss-cpu, so switching to pip for now, but it'd probably be even...

lmeyerov

**Describe the bug** When providing an api key, if a username is also provided, an unexpected error appears about not having set a password Provided a confusing onboarding for a...

lmeyerov

**Describe the bug** Render equals false URL_params values do not seem to get set such as play=0 . This prevents core workflows like specifying a custom layout for embedded web...

lmeyerov

Presumably there are some cases where we expect cuCat to outperform dirty_cat -- thoughts on how to make into runnable tests, separate from the functional tests?

lmeyerov

I'm guessing: PyGraphistry integration: - github ci: default off - github ci: explicit opt-out - local dev: as part of regular gpu-enabled tests cuCat repo: ???

lmeyerov

**Is your feature request related to a problem? Please describe.** setup.py pins dirty_cat to 0.2, but 0.4 is out and includes features like datetime support . I don't remember why...

lmeyerov