Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

simplifying API

See original GitHub issue

The API could be simplified in a few places. For example:

In hyp.plot we could include an align flag that runs hyp.tools.align on the data if set to True (default: False).
In hyp.tools.align and hyp.tools.procrustes we could include a ndimsflag that runs hyp.tools.reduce on the dataset prior to alignment if not None (default: None)
In hyp.tools.align and hyp.tools.procrustes, if the data matrices don’t have the same numbers of features, we should zero-pad all of the matrices to ensure they have the same number of features as the matrix with the most features
in hyp.tools.load we could include align and ndims flags that pass the data through the appropriate other functions (hyp.tools.reduce, followed by hyp.tools.align) so that the reduced/aligned data are returned from the start, without needed to save extra copies of the dataset

Issue Analytics

State:
Created 6 years ago
Comments:20 (14 by maintainers)

Top GitHub Comments

1reaction

andrewheussercommented, Jun 5, 2017

all good! pushing to pip!

1reaction

andrewheussercommented, Jun 2, 2017

@jeremymanning - re dataframes, we do not do any reordering. If the input data is a dataframe (or list of dfs) we:

transform all text columns into binary dummy variables (see here leaving the numerical columns as they are
turn the whole df into a np array
optionally output the column labels if return_labels=True

I’ll add an issue to check to see if the column labels are the same across dfs when reducing. if they are the same, just out of order, they will be resorted.

@rarredon I will be working on hypertools all day today, so ping me if you need clarification as things come up!