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

Release 0.1 #32

Open
7 of 12 tasks
cbertinato opened this issue Oct 27, 2017 · 3 comments
Open
7 of 12 tasks

Release 0.1 #32

cbertinato opened this issue Oct 27, 2017 · 3 comments

Comments

@cbertinato
Copy link
Collaborator

cbertinato commented Oct 27, 2017

I propose that the goal for this release is basic QC functionality, mainly so we can do some testing in the field. Let's use this issue to track features that we think would be necessary for this use case in the form of a checklist. We can modify and fill this in until we're happy with it.

@cbertinato cbertinato added this to the Initial Release milestone Oct 27, 2017
@bradyzp
Copy link
Member

bradyzp commented Oct 29, 2017

Sounds like a good plan, lets talk about dividing up different areas here and begin work towards this as soon as we finish with the current gui-dev branch.

@cbertinato
Copy link
Collaborator Author

Modified a few of the checklist items. Is Eotvos good to go? I can pick up gravity and trajectory dataframe join after I finish the labeling code. I have some code for alignment, but need to do some work on sub-sample rate alignment. I also have some filtering code that just needs some tests.

@bradyzp
Copy link
Member

bradyzp commented Nov 2, 2017

Eotvos is good to go, just ensure it is utilizing the basic derivative function for now.
The numpy.gradient needs some adjustment and testing before it can be used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants