-
Notifications
You must be signed in to change notification settings - Fork 4
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
SciPy 2020 Birds of a Feather Session #18
Comments
Could you post a read-only link to the google doc here (when it is available)? Thanks! |
bummed that I missed this! @ksunden I'd like to take a look at the doc when you get a chance |
Here is a link to the doc (with emails removed since I'm posting it without any auth) If you wish to contact an individual, I may be able to get you in touch (though many of them are pretty easy to find via github). The format largely was "each person (who wanted to) talk briefly about their problem space, current solutions, and frustrations" then we had a bit of "which projects can we rally around". I think the video will be posted to Enthought's youtube page in a few days, but not 100% sure (and it is likely missing the text chat that was also going on) Many of the participants had projects they work with, but don't envision being more widely useful outside of their current scope/research group. A few that are looking to be more broadly useful to the community:
As authors of yaq, @untzag and I think our plan moving forward is to use yaq for direct hardware communication, then integrate into bluesky for higher level operations. |
Here's a recording of the session: https://www.youtube.com/watch?v=6HxVbK14EDI |
I don't know yaq but I started a project some year ago with similar goal I think : |
Hello all,
@untzag and I are hosting a BoF at the SciPy 2020 Conference on hardware interfacing and instrumentation in python.
We intend to discuss many of the things that have been discussed in this repo.
For those attending the conference, the BoF is this Tuesday 2020-07-07 at 17:00 CDT
We are planning on having a collaboratively edited google doc.
If anybody is interested who cannot attend, let me know, and I can get you access to the doc/include you in further email communications.
The text was updated successfully, but these errors were encountered: