Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

timesteps instead of number of timepoints #67

Open
lucywowen opened this issue Jun 13, 2018 · 0 comments
Open

timesteps instead of number of timepoints #67

lucywowen opened this issue Jun 13, 2018 · 0 comments

Comments

@lucywowen
Copy link
Collaborator

Use time steps (in dataframes) instead of numpy arrays. index argument that can pass a dataframe (inferred or explicitly specified which would override) or a numpy array with index (if missing, inferred).

Update:

Weights function
timecorr (format data, not hypertools) force to return timecrystal
helpers:

  • all weights functions (should take index instead of number of timepoints)
  • wcorr (takes weights matrix now, but make sure that the timepoints are processed in the correct order)
  • smooth function (really nonfunctional after... same with timepoint decoder... and predict)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants