-
Notifications
You must be signed in to change notification settings - Fork 41
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
blog post for new set operations #44
Comments
The risk is to have too many posts released at the same time. I can write a draft tomorrow, though. It would describe the use of the operators on a concrete example such as generating a gromacs index file for a complex system (http://pubs.acs.org/doi/abs/10.1021/ja507832e?journalCode=jacsat). |
I thought it was a good self-contained topic for a blog post and it would fit nicely into our series of posts introducing new things in the upcoming release.
If you think we have too many posts and/or it's too much of a burden then scrap it. (I admit, I like having a blog post because then it's easy to link people to the specific posts, either in mail conversation or from a tweet.) – ultimately, if @jbarnoud feels we don't need the post, close the issue.
… On 1 Apr, 2017, at 02:34, Max Linke ***@***.***> wrote:
Sure we need a post about that? The docs are already guide good and fairly short. I would include it into the release announcement blog post with some example and a link to the docs. That should be nice enough.
Or do you want more @orbeckst
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
--
Oliver Beckstein * [email protected]
skype: orbeckst * [email protected]
|
We could hold it back to avoid too many at once, I think it'd still work a few weeks after 16 is released. |
@richardjgowers I am perfectly fine with that. It will be a reminder that upgrading is cool. |
@jbarnoud do you want to do this at some point or should we just close it? |
On 06/20/2017 11:23 PM, Oliver Beckstein wrote:
@jbarnoud <https://github.com/jbarnoud> do you want to do this at some
point or should we just close it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#44 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABUWulpwlxsoGvVXSs1uuCargnur4dDRks5sGDhigaJpZM4MeqGC>.
I keep thinking this would be a nice post to have. It just keep going
down in my todo list.
|
I am happy to close it and if you feel like it, re-open... It's not crucial but I remember a nice demo of yours a while back (or was it the PR/issue?) on how to make complicated lipid selections that was an almost complete post. |
Give a brief intro to MDAnalysis/mdanalysis#726
The text was updated successfully, but these errors were encountered: