-
Notifications
You must be signed in to change notification settings - Fork 67
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
Merge dev and do new release #386
Conversation
…into fastshermanmorrison
…OAs for EcorrKernelNoise signals
…son, and updated fastshermanmorrison-pulsar in requirements_dev.txt
I think we need to merge |
Ah maybe not. It's the usual suspect: |
It turns out that enterprise_extensions has some dependencies on the dev branch. Is it an idea to just merge dev as-is to accommodate, and deal with tempo2/pint optional dependencies and feather later? Those can go into the dev branch when ready. |
@vhaasteren I think that's a good idea. Lately, I have been more busy than I thought I would be. So let's go ahead and merge and then work on these extra features. |
The tests weren't passing because of libstempo/TEMPO2.... Those issues should be solved now. Maybe the tests will pass on rerunning them? |
Two more issues now: TEMPO2 can't be found on the Mac installs and 3.7 is still required for merging. |
Add "CHIME" to def nanograv_backends(backend_flags):
added "VEGAS" to list as requested
Update selections.py for "CHIME" and "VEGAS"
As described in issue #385, merge dev->master and do a new release
All other changes postponed for merge into master. Those will get updated on the new dev branch