GSoC 2017 mentors and projects

158 views
Skip to first unread message

Max Linke

unread,
Nov 23, 2016, 5:13:45 PM11/23/16
to MDnalysis-devel
Hi All

GSoC 2017 is getting closer and we should start to think about new
projects
and add descriptions for them. I've added a new projects

[wiki-page](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2017-Project-Ideas)
with some projects from last year that would still be great to have
this time.

I can be the official org admin again but I won't be a primary mentor
next
year as I anticipate to be busy finishing up several projects. Others
who want
to be a primary mentor, like Richard and Jonathon this year, should
either
pick a project on the ideas page and enter them self as mentors or
add new
projects. I recommend that you feel passionate about the project. I
noticed
myself as a mentor that I had more fun doing it when I worked on a
project
that I cared about.

New projects that would fit GSoC:
- Add universal random access to all readers #314
- Unify Analysis classes API where applicable.

There have also been some other possible fits in the issue tracker
recently
but I can't find them right now.

If David is OK with it we could also offer datreant based projects with
MDAnalysis.

best Max

Richard Gowers

unread,
Nov 25, 2016, 10:45:43 AM11/25/16
to MDnalysis-devel
I think I'll be free to mentor someone this year, I'll double check the dates.

With the parallelisation project, I think this is a good project, but we should probably do some groundwork to have an analysis case ready.  To avoid having to download a huge trajectory, we could write a script that creates a trajectory that follows an analytical function (eg move atoms according to a sine function).  We could then have the analysis do distance between two atoms, which should follow the same analytical function.

I'm pretty keen to get cellgrid done, I think this would be a very nice library feature.

Richard

Jonathan Barnoud

unread,
Nov 25, 2016, 11:17:18 AM11/25/16
to mdnalys...@googlegroups.com
I would be happy to mentor as well. But I did not think yet about what project to offer. Is there a deadline?

Best,
Jonathan
--
You received this message because you are subscribed to the Google Groups "MDnalysis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mdnalysis-dev...@googlegroups.com.
To post to this group, send email to mdnalys...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mdnalysis-devel/34469741-66a8-45bc-a8fa-5a4665cc6cb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Richard Gowers

unread,
Nov 25, 2016, 11:25:42 AM11/25/16
to MDnalysis-devel
https://developers.google.com/open-source/gsoc/timeline

Looks like Feb 9th.  Iirc last year we got feedback that our project ideas weren't well presented, so perhaps this year we should do something like strictly 1 project per mentor to try and make them all good quality.

Max Linke

unread,
Nov 25, 2016, 12:08:10 PM11/25/16
to mdnalys...@googlegroups.com
> I would be happy to mentor as well. But I did not think yet about
> what project to offer. Is there a deadline?

Nice to hear. Then we just need one more person and we have two full
mentor teams. About a deadline I just emailed early so you have time to
think about a project. GSoC usually works best when the mentors are
themselves invested in the project.
That is the hard deadline. But we should already have some project ideas
before and iterate on them.

> Iirc last year we got feedback that our project
> ideas weren't well presented, so perhaps this year we should do
> something like strictly 1 project per mentor to try and make them all
> good quality.

Maybe not 1 project per main-mentor that we offer. 2-3 should still be
fine to offer. But I would also go for quality instead of quantity. If
we have a better overview of the problem our self it will also help the
student later. I would argue though that the discussions about the
project ideas should happen in issues to which we link in the ideas
pages. The ideas page itself should contain a short description of the
problem.

For the parallelization program we should have do a bit of research on
serializing atomgroups beforehand.

best Max
>> <https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2017-Project-Ideas>)
>> send an email to mdnalysis-dev...@googlegroups.com <javascript:>.
>> To post to this group, send email to mdnalys...@googlegroups.com
>> <javascript:>.
>> <https://groups.google.com/d/msgid/mdnalysis-devel/34469741-66a8-45bc-a8fa-5a4665cc6cb3%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout
>> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-dev...@googlegroups.com>.
> To post to this group, send email to mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mdnalysis-devel/a9ee5467-c304-4084-84fd-059381a73931%40googlegroups.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/a9ee5467-c304-4084-84fd-059381a73931%40googlegroups.com?utm_medium=email&utm_source=footer>.

Jan Domanski

unread,
Nov 25, 2016, 2:19:32 PM11/25/16
to mdnalys...@googlegroups.com
I wanna give it a shot actually

To unsubscribe from this group and stop receiving emails from it, send an email to mdnalysis-dev...@googlegroups.com.
To post to this group, send email to mdnalys...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mdnalysis-devel/888aba87-6f79-e805-8249-4cba9d5720db%40gmail.com.

Oliver Beckstein

unread,
Nov 25, 2016, 6:21:56 PM11/25/16
to mdnalys...@googlegroups.com

> On 25 Nov, 2016, at 10:08, Max Linke <max.l...@gmail.com> wrote:
>
> For the parallelization program we should have do a bit of research on serializing atomgroups beforehand.

Serialization is important to discuss. Random access for all readers is essential.

Mahzad (at ASU) has also been benchmarking a range of file formats (DCD, XTC, NCDF) with a dask-based parallelizaton for a map-reduce approach on local and XSEDE HPC resources. She's in the process of putting it together as a technical report that can be more easily discussed. The efficiency and scalability depends highly on the file format (!) and the hardware (SSD, Lustre, NFS, …) as well presumably on how expensive the computation is. It's not entirely straightforward to decide what the best approach is. It should be an interesting discussion. I'd like to find out which approach(es) to paralellization are the most promising and if there is anything that we can do in MDAnalysis to facilitate these approaches.

Oliver

--
Oliver Beckstein * orbe...@gmx.net
skype: orbeckst * orbe...@gmail.com

Richard Gowers

unread,
Nov 25, 2016, 6:38:53 PM11/25/16
to mdnalys...@googlegroups.com

For what it's worth, I've got a PR up that gives random access to all readers.

I'd be very interested in reading that technical report.


--
You received this message because you are subscribed to a topic in the Google Groups "MDnalysis-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mdnalysis-devel/QlwoL1_Etns/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mdnalysis-dev...@googlegroups.com.
To post to this group, send email to mdnalys...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mdnalysis-devel/5F3D3C34-D0D0-4717-B21D-A94ACCF413B6%40gmail.com.

Max Linke

unread,
Dec 1, 2016, 4:01:26 AM12/1/16
to mdnalys...@googlegroups.com
Random Access is now available in develop. We can start to formalize it
in the next release with regard to offset handling.

For the serialization discussion. In which issue/wikipage/mail thread
did we make the most progress. I know we did discuss this in several
places. It would be nice to gather that information in one place.

About the parralel backend. I would like to have support for joblib
(that means multiprocessing library) since it's by far the easiest
library I have come across to parallelize a for loop.

It would be realy nice it Mahzad could make the report public for all of us.

Max

Manuel Nuno Melo

unread,
Dec 1, 2016, 4:31:52 AM12/1/16
to mdnalys...@googlegroups.com
Parallelization is definitely a hot topic to pursue, in all those aspects. I'd be very happy to mentor someone in that project. (My feeling is that dask/joblib may be a bit too high level to get max performance out of it, though)

As I stated earlier I'd rather focus on a single potential project, and this would be it for me. If no-one chooses it, too bad, I'll mentor some other time.


--
You received this message because you are subscribed to the Google Groups "MDnalysis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mdnalysis-devel+unsubscribe@googlegroups.com.
To post to this group, send email to mdnalysis-devel@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mdnalysis-devel/e9ae7387-a5e2-19ad-4b92-618d034d17f1%40gmail.com.

Oliver Beckstein

unread,
Dec 1, 2016, 8:04:23 PM12/1/16
to mdnalys...@googlegroups.com

> On 1 Dec, 2016, at 02:31, Manuel Nuno Melo <manuel.n...@gmail.com> wrote:
>
> Parallelization is definitely a hot topic to pursue, in all those aspects. I'd be very happy to mentor someone in that project. (My feeling is that dask/joblib may be a bit too high level to get max performance out of it, though)

I think for parallelization we simply have to do a lot of prototyping to figure out what works, if there are common patterns, and if and how it makes sense to support it inside MDAnalysis.

>
> On Dec 1, 2016 9:01 AM, "Max Linke" <max.l...@gmail.com> wrote:
>
>
>> On 11/26/2016 12:23 AM, Oliver Beckstein wrote:
[…]
>>>
>>> Mahzad (at ASU) has also been benchmarking a range of file formats (DCD, XTC, NCDF) with a dask-based parallelizaton for a map-reduce approach on local and XSEDE HPC resources. She's in the process of putting it together as a technical report that can be more easily discussed. The efficiency and scalability depends highly on the file format (!) and the hardware (SSD, Lustre, NFS, …) as well presumably on how expensive the computation is. It's not entirely straightforward to decide what the best approach is. It should be an interesting discussion. I'd like to find out which approach(es) to paralellization are the most promising and if there is anything that we can do in MDAnalysis to facilitate these approaches.
>>>
>>
[…]
>>
>> It would be realy nice it Mahzad could make the report public for all of us.

She just has to finish writing it…

Max Linke

unread,
Dec 26, 2016, 7:05:46 AM12/26/16
to mdnalys...@googlegroups.com
As a reminder it would be nice if mentors could assign themselves to
ideas on the [ideas-page]. You can also add projects that extend last
year's projects, i.e. the auxillary framework and dependent analysis.

Volunteering this year are: Manuel, Richard, Jonathan and Jan

Merry Christmas everyone
Max

[ideas-page]
https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2017-Project-Ideas

Max Linke

unread,
Jan 16, 2017, 3:12:00 PM1/16/17
to mdnalys...@googlegroups.com
News for the GSoC application. I'm the administrator for NumFOCUS this
year and asked that we can take part under their umbrella. It shouldn't
be a problem that we aren't a NumFOCUS affiliated project right now.

https://github.com/numfocus/gsoc/issues/153

best Max

Richard Gowers

unread,
Jan 17, 2017, 6:36:42 AM1/17/17
to MDnalysis-devel
Ok I've put myself down for the CellGrid integration and new formats projects.

With the parallelisation project, maybe we should make the scope of this clearer?  (To the best of my understanding...) Realistically what this will need is for Universe to get serialised, and then used with something like dask.  Then once this is complete we can look at making it work automagically with AnalysisBase (but not before!).

Currently the Py3 port doesn't have an assigned mentor, which should mean it doesn't get offered unless someone steps up.  I wasn't sure if there was really enough coherent content there for a GSOC project?  I think it's mostly the DCD port that Tyler and Max have started, then odds and ends until the tests pass?

Jonathan Barnoud

unread,
Jan 17, 2017, 6:52:22 AM1/17/17
to mdnalys...@googlegroups.com
I can step up for python 3. The extend of the work is still unknown until the DCD reader is finished, though. It may be too small for GSoC.

I also thought about proposing time aware slicing (<https://github.com/MDAnalysis/mdanalysis/issues/800>). I'll try to write that down latter today.

I can help with the TNG format.
--
You received this message because you are subscribed to the Google Groups "MDnalysis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mdnalysis-dev...@googlegroups.com.
To post to this group, send email to mdnalys...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mdnalysis-devel/456ebf37-7577-4997-87bd-9e8a10304332%40googlegroups.com.

Richard Gowers

unread,
Jan 17, 2017, 7:01:43 AM1/17/17
to MDnalysis-devel
Yeah time aware slicing would be a fun project.

We can double up on the formats project afaik, so feel free to put yourself down for that one too.  We could also implement your edr reader as an aux in the same project? (mda.Universe(topol.tpr, traj.trr, aux=ener.edr) anyone?)  Maybe edr as aux is big enough for a project on its own?

I also worry with Python3 there's not really a clear theme to the project.. it will be jumping around fixing various small things in the code base.

Max Linke

unread,
Jan 17, 2017, 7:04:22 AM1/17/17
to mdnalys...@googlegroups.com


On 01/17/2017 01:01 PM, Richard Gowers wrote:
> Yeah time aware slicing would be a fun project.
>
> We can double up on the formats project afaik, so feel free to put
> yourself down for that one too. We could also implement your edr reader
> as an aux in the same project? (mda.Universe(topol.tpr, traj.trr,
> aux=ener.edr) anyone?) Maybe edr as aux is big enough for a project on
> its own?
>
> I also worry with Python3 there's not really a clear theme to the
> project.. it will be jumping around fixing various small things in the
> code base.

I would leave python3 out to be honest. After the DCDReader is finished
we can pick at everything that comes up ourselves.
>> <https://groups.google.com/d/msgid/mdnalysis-devel/456ebf37-7577-4997-87bd-9e8a10304332%40googlegroups.com?utm_medium=email&utm_source=footer>https://groups.google.com/d/msgid/mdnalysis-devel/456ebf37-7577-4997-87bd-9e8a10304332%40googlegroups.com
>> <https://groups.google.com/d/msgid/mdnalysis-devel/456ebf37-7577-4997-87bd-9e8a10304332%40googlegroups.com>.
>> For more options, visit https://groups.google.com/d/optout
>> <https://groups.google.com/d/optout>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-dev...@googlegroups.com>.
> To post to this group, send email to mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mdnalysis-devel/48615be8-8f6b-4896-bbfa-1aafd3e692d6%40googlegroups.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/48615be8-8f6b-4896-bbfa-1aafd3e692d6%40googlegroups.com?utm_medium=email&utm_source=footer>.

Jonathan Barnoud

unread,
Jan 17, 2017, 7:06:07 AM1/17/17
to mdnalys...@googlegroups.com

I would wait to see the auxiliary data taking some momentum before investing a student on the feature. Also, once we can feed a numpy array as an auxiliary there is not much more to do to plug the EDR parser.

Richard Gowers

unread,
Jan 17, 2017, 7:06:16 AM1/17/17
to mdnalys...@googlegroups.com
Ok I removed it from the list.

You received this message because you are subscribed to a topic in the Google Groups "MDnalysis-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mdnalysis-devel/QlwoL1_Etns/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mdnalysis-dev...@googlegroups.com.

To post to this group, send email to mdnalys...@googlegroups.com.

Oliver Beckstein

unread,
Jan 17, 2017, 12:07:35 PM1/17/17
to mdnalys...@googlegroups.com
Sorry to jump into the GSOC thread. One other thing that would be useful in the long run would be to move forward with making trajectory readers MDAnalysis-independent. Max has already done this for the Gromacs XDR reader. What I mean by this is that someone else could, in principle, use lib.formats and then use it independently from MDA itself.

Why?

Because between MDAnalysis, mdtraj, pytraj, VMD … we are duplicating code and that's a waste of time and bad software engineering. It would be much better if (eventually) we (the community) have bare-bones readers and then everyone else can use them as part of their library. Generally, people liked that idea, judging from my interactions with others at meetings. Certainly, something like this is not happening overnight but we could take a leadership role and start by moving some of our readers/writers into lib.format. We would then be ready to move forward if we wanted to.

A GSOC project related to trajectory formats could be to

1. formally define the api (basically, numpy arrays or array_like)… follow the Gromacs XDR code
2. move some/all readers/writers to lib.format

Max Linke

unread,
Jan 17, 2017, 12:11:16 PM1/17/17
to mdnalys...@googlegroups.com

I like that idea. The DCD reader will also be independent in the future.


--
You received this message because you are subscribed to the Google Groups "MDnalysis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mdnalysis-dev...@googlegroups.com.
To post to this group, send email to mdnalys...@googlegroups.com.

Hai Nguyen

unread,
Jan 17, 2017, 12:30:17 PM1/17/17
to mdnalys...@googlegroups.com
On Tue, Jan 17, 2017 at 12:07 PM, Oliver Beckstein <orbe...@gmail.com> wrote:
Sorry to jump into the GSOC thread. One other thing that would be useful in the long run would be to move forward with making trajectory readers MDAnalysis-independent. Max has already done this for the Gromacs XDR reader. What I mean by this is that someone else could, in principle, use lib.formats and then use it independently from MDA itself.

Why?

 

Because between MDAnalysis, mdtraj, pytraj, VMD … we are duplicating code and that's a waste of time and bad software engineering. It would be much better if (eventually) we (the community) have bare-bones readers and then everyone else can use them as part of their library. Generally, people liked that idea, judging from my interactions with others at meetings. Certainly, something like this is not happening overnight but we could take a leadership role and start by moving some of our readers/writers into lib.format. We would then be ready to move forward if we wanted to.

I agree with this. Readers are just readers, just for reading data to memory and nothing else. It would be great if different packages can share the reader and focus more
on data analysis (which is the main aim).

Hai
 

A GSOC project related to trajectory formats could be to

1. formally define the api (basically, numpy arrays or array_like)… follow the Gromacs XDR code
2. move some/all readers/writers to lib.format

Oliver

--
Oliver Beckstein * orbe...@gmx.net
skype: orbeckst  * orbe...@gmail.com

--
You received this message because you are subscribed to the Google Groups "MDnalysis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mdnalysis-devel+unsubscribe@googlegroups.com.
To post to this group, send email to mdnalysis-devel@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mdnalysis-devel/AC9516CA-7CB6-4262-B01E-2EF01AE7FDAA%40gmail.com.

Max Linke

unread,
Jan 19, 2017, 11:36:36 AM1/19/17
to mdnalys...@googlegroups.com
While we are talking about new projects.

We could also have a GSoC project to convert the tests from nose to
pytest. Scipy is thinking about such a GSoC project. It would be a very
good fit for someone starting to learn python.

best Max
> Oliver Beckstein * orbe...@gmx.net <mailto:orbe...@gmx.net>
> skype: orbeckst * orbe...@gmail.com <mailto:orbe...@gmail.com>
>
> --
> You received this message because you are subscribed to the Google
> Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>.
> To post to this group, send email to
> mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>.
> <https://groups.google.com/d/msgid/mdnalysis-devel/AC9516CA-7CB6-4262-B01E-2EF01AE7FDAA%40gmail.com>.
> For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-dev...@googlegroups.com>.
> To post to this group, send email to mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mdnalysis-devel/CAFNMPM9c_mrRR%3DxAqhzsg%2BBQXEYPTbcX_marVm4HJwyhoEZx2g%40mail.gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAFNMPM9c_mrRR%3DxAqhzsg%2BBQXEYPTbcX_marVm4HJwyhoEZx2g%40mail.gmail.com?utm_medium=email&utm_source=footer>.

Jonathan Barnoud

unread,
Jan 19, 2017, 12:03:36 PM1/19/17
to mdnalys...@googlegroups.com
It would be a good idea indeed. Does anybody looked at what level of
heacache we are looking at?

Max Linke

unread,
Jan 19, 2017, 12:44:28 PM1/19/17
to mdnalys...@googlegroups.com
Not sure. So first it would be to get all tests running again. Then we
have to get rid of the `yield` stuff to parametrize tests and replace it
with `pytest.mark.parametrize` and see if we can rewrite the tests
with pytest idoms.

Jonathan Barnoud

unread,
Jan 19, 2017, 12:51:57 PM1/19/17
to mdnalys...@googlegroups.com
We might also want to port some of the plugins.

Alse, just for a matter of scale (because I was curious), there are 140
`yield` statements in the tests, spanning 26 files.

Max Linke

unread,
Jan 19, 2017, 1:00:31 PM1/19/17
to mdnalys...@googlegroups.com
Oh this would also mean to replace the tempdir code with the `tmpdir`
parameter available in pytest. This is a lot of work but a GSoC student
could get a reasonable chunk of it done. There are also clear goals that
can be defined.

Richard Gowers

unread,
Jan 20, 2017, 6:31:02 AM1/20/17
to MDnalysis-devel
Yeah I'd be interested in seeing how a pytest refactor would look like.

https://github.com/MDAnalysis/mdanalysis/blob/develop/testsuite/MDAnalysisTests/core/test_groups.py#L15

So something like that with fixtures instead of the test generator.

Manuel Nuno Melo

unread,
Jan 20, 2017, 9:17:47 AM1/20/17
to mdnalys...@googlegroups.com
+1 for the pytest overhaul initiative.

>>>>>     To post to this group, send email to
>>>>>     mdnalys...@googlegroups.com
>>>>>     <mailto:mdnalys...@googlegroups.com>.
>>>>>     To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/mdnalysis-devel/AC9516CA-7CB6-4262-B01E-2EF01AE7FDAA%40gmail.com
>>>>>
>>>>>
>>>>> <https://groups.google.com/d/msgid/mdnalysis-devel/AC9516CA-7CB6-4262-B01E-2EF01AE7FDAA%40gmail.com>.
>>>>>
>>>>>
>>>>>     For more options, visit https://groups.google.com/d/optout
>>>>>     <https://groups.google.com/d/optout>.
>>>>>
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "MDnalysis-devel" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to mdnalysis-dev...@googlegroups.com

--
You received this message because you are subscribed to the Google Groups "MDnalysis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mdnalysis-devel+unsubscribe@googlegroups.com.
To post to this group, send email to mdnalysis-devel@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mdnalysis-devel/995b4574-a1f2-4392-ac31-93aa580b8047%40googlegroups.com.

Jan Domanski

unread,
Jan 21, 2017, 2:47:27 PM1/21/17
to mdnalys...@googlegroups.com
Re pytest overhaul issue, would it be advantageous to have some a single set of tests (a file) converted from nose to py.test – sort of "before and after" example? 

For one thing, it would help to estimate the amount of time needed, secondly, it would be some "preliminary" code for GSoc helping asses the viability of the project. i'm happy to put something together. 


Max Linke

unread,
Jan 21, 2017, 3:10:47 PM1/21/17
to mdnalys...@googlegroups.com

Mosts tests should just work. Some research about porting the plugins to pytest would be good though.


>>>>>     To post to this group, send email to
>>>>>     mdnalys...@googlegroups.com
>>>>>     <mailto:mdnalys...@googlegroups.com>.
>>>>>     To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/mdnalysis-devel/AC9516CA-7CB6-4262-B01E-2EF01AE7FDAA%40gmail.com
>>>>>
>>>>>
>>>>> <https://groups.google.com/d/msgid/mdnalysis-devel/AC9516CA-7CB6-4262-B01E-2EF01AE7FDAA%40gmail.com>.
>>>>>
>>>>>
>>>>>     For more options, visit https://groups.google.com/d/optout
>>>>>     <https://groups.google.com/d/optout>.
>>>>>
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "MDnalysis-devel" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to mdnalysis-dev...@googlegroups.com

--
You received this message because you are subscribed to the Google Groups "MDnalysis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mdnalysis-dev...@googlegroups.com.
To post to this group, send email to mdnalys...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "MDnalysis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mdnalysis-dev...@googlegroups.com.
To post to this group, send email to mdnalys...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "MDnalysis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mdnalysis-dev...@googlegroups.com.
To post to this group, send email to mdnalys...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mdnalysis-devel/CAH5w%3DBdFvkYNrmbKY4LzbO8Q2HE1dgg%3D%3DrA4xgdyMNxxFaxisA%40mail.gmail.com.

Richard Gowers

unread,
Jan 21, 2017, 3:31:11 PM1/21/17
to mdnalys...@googlegroups.com

Hey Jan. Some of the core tests are best maybe, there's a lot of tests where we go through AtomGroup ResidueGroup and SegmentGroup and check they all slice the same. Obviously crying out for a fixture instead.


You received this message because you are subscribed to a topic in the Google Groups "MDnalysis-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mdnalysis-devel/QlwoL1_Etns/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mdnalysis-dev...@googlegroups.com.

To post to this group, send email to mdnalys...@googlegroups.com.

Max Linke

unread,
Feb 4, 2017, 3:43:50 AM2/4/17
to mdnalys...@googlegroups.com
I found an interesting blog post that explains how we can
port some if not most of our nose-plugins to pytest

https://nvbn.github.io/2017/02/02/pytest-leaking/

On 01/21/2017 09:30 PM, Richard Gowers wrote:
> Hey Jan. Some of the core tests are best maybe, there's a lot of tests
> where we go through AtomGroup ResidueGroup and SegmentGroup and check
> they all slice the same. Obviously crying out for a fixture instead.
>
>
> On Sat, 21 Jan 2017, 8:10 p.m. Max Linke, <max.l...@gmail.com
> <mailto:max.l...@gmail.com>> wrote:
>
> Mosts tests should just work. Some research about porting the
> plugins to pytest would be good though.
>
>
> On Sat, Jan 21, 2017, 20:47 Jan Domanski <jan...@gmail.com
> <mailto:jan...@gmail.com>> wrote:
>
> Re pytest overhaul issue, would it be advantageous to have some
> a single set of tests (a file) converted from nose to py.test –
> sort of "before and after" example?
>
> For one thing, it would help to estimate the amount of time
> needed, secondly, it would be some "preliminary" code for GSoc
> helping asses the viability of the project. i'm happy to put
> something together.
>
>
> On 20 January 2017 at 14:17, Manuel Nuno Melo
> <manuel.n...@gmail.com <mailto:manuel.n...@gmail.com>>
> wrote:
>
> +1 for the pytest overhaul initiative.
>
> On Fri, Jan 20, 2017 at 11:31 AM, Richard Gowers
> <richard...@gmail.com <mailto:richard...@gmail.com>>
> https://groups.google.com/d/msgid/mdnalysis-devel/995b4574-a1f2-4392-ac31-93aa580b8047%40googlegroups.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/995b4574-a1f2-4392-ac31-93aa580b8047%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the
> Google Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop receiving emails
> from it, send an email to
> mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-dev...@googlegroups.com>.
> To post to this group, send email to
> mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mdnalysis-devel/CAERWk%3D66NWaWYVteKZodh%3Du6VUaFtP8WhqbakvC9tCd%2B3GtmPQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAERWk%3D66NWaWYVteKZodh%3Du6VUaFtP8WhqbakvC9tCd%2B3GtmPQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the
> Google Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to
> mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-dev...@googlegroups.com>.
> To post to this group, send email to
> mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mdnalysis-devel/CAH5w%3DBdFvkYNrmbKY4LzbO8Q2HE1dgg%3D%3DrA4xgdyMNxxFaxisA%40mail.gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAH5w%3DBdFvkYNrmbKY4LzbO8Q2HE1dgg%3D%3DrA4xgdyMNxxFaxisA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in
> the Google Groups "MDnalysis-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/mdnalysis-devel/QlwoL1_Etns/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-dev...@googlegroups.com>.
> To post to this group, send email to
> mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mdnalysis-devel/CAKRyePDrfWsFhRaMdzuipZ1foaQJpbPvdu-G%3Dgi8-u2J6xSpXw%40mail.gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAKRyePDrfWsFhRaMdzuipZ1foaQJpbPvdu-G%3Dgi8-u2J6xSpXw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google
> Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-dev...@googlegroups.com>.
> To post to this group, send email to mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mdnalysis-devel/CAFk3ehndNRN85U1cACor4y_GruRCtGB%3DZrCEqfbT-_Sh9y%2Bt-A%40mail.gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAFk3ehndNRN85U1cACor4y_GruRCtGB%3DZrCEqfbT-_Sh9y%2Bt-A%40mail.gmail.com?utm_medium=email&utm_source=footer>.

Manuel Nuno Melo

unread,
Feb 6, 2017, 10:32:40 AM2/6/17
to mdnalys...@googlegroups.com
Good find.

On the particular case they implement, it's a leak finder at a lower level than ours, and probably a good idea to add to/replace our check.


On Sat, Feb 4, 2017 at 8:43 AM, Max Linke <max.l...@gmail.com> wrote:
I found an interesting blog post that explains how we can
port some if not most of our nose-plugins to pytest

https://nvbn.github.io/2017/02/02/pytest-leaking/

On 01/21/2017 09:30 PM, Richard Gowers wrote:
Hey Jan. Some of the core tests are best maybe, there's a lot of tests
where we go through AtomGroup ResidueGroup and SegmentGroup and check
they all slice the same. Obviously crying out for a fixture instead.


On Sat, 21 Jan 2017, 8:10 p.m. Max Linke, <max.l...@gmail.com
<mailto:max.l...@gmail.com>> wrote:

    Mosts tests should just work. Some research about porting the
    plugins to pytest would be good though.


    On Sat, Jan 21, 2017, 20:47 Jan Domanski <jan...@gmail.com
    <mailto:jan...@gmail.com>> wrote:

        Re pytest overhaul issue, would it be advantageous to have some
        a single set of tests (a file) converted from nose to py.test –
        sort of "before and after" example?

        For one thing, it would help to estimate the amount of time
        needed, secondly, it would be some "preliminary" code for GSoc
        helping asses the viability of the project. i'm happy to put
        something together.


        On 20 January 2017 at 14:17, Manuel Nuno Melo

        wrote:

            +1 for the pytest overhaul initiative.

            On Fri, Jan 20, 2017 at 11:31 AM, Richard Gowers
            <richard...@gmail.com <mailto:richardjgowers@gmail.com>>
                    >>>>> <mailto:mdnalysis-devel%2Bunsubsc...@googlegroups.com>.

                    >>>>>     To post to this group, send email to
                    >>>>>     mdnalys...@googlegroups.com
                    >>>>>     <mailto:mdnalys...@googlegroups.com>.
                    >>>>>     To view this discussion on the web visit
                    >>>>> https://groups.google.com/d/msgid/mdnalysis-devel/AC9516CA-7CB6-4262-B01E-2EF01AE7FDAA%40gmail.com

                    >>>>>
                    >>>>>
                    >>>>> <https://groups.google.com/d/msgid/mdnalysis-devel/AC9516CA-7CB6-4262-B01E-2EF01AE7FDAA%40gmail.com>.

                    >>>>>
                    >>>>>
                    >>>>>     For more options, visit https://groups.google.com/d/optout
                    >>>>>     <https://groups.google.com/d/optout>.
                    >>>>>
                    >>>>>
                    >>>>> --
                    >>>>> You received this message because you are subscribed to the Google
                    >>>>> Groups "MDnalysis-devel" group.
                    >>>>> To unsubscribe from this group and stop receiving emails from it, send
                    >>>>> an email to mdnalysis-dev...@googlegroups.com
                    >>>>>
                    <mailto:mdnalysis-devel+unsubscr...@googlegroups.com>.

                    >>>>> To post to this group, send email to
                    mdnalys...@googlegroups.com
                    >>>>> <mailto:mdnalys...@googlegroups.com>.
                    >>>>> To view this discussion on the web visit
                    >>>>> https://groups.google.com/d/msgid/mdnalysis-devel/CAFNMPM9c_mrRR%3DxAqhzsg%2BBQXEYPTbcX_marVm4HJwyhoEZx2g%40mail.gmail.com

                    >>>>>
                    >>>>>
                    >>>>> <https://groups.google.com/d/msgid/mdnalysis-devel/CAFNMPM9c_mrRR%3DxAqhzsg%2BBQXEYPTbcX_marVm4HJwyhoEZx2g%40mail.gmail.com?utm_medium=email&utm_source=footer>.

                    >>>>>
                    >>>>>
                    >>>>> For more options, visit https://groups.google.com/d/optout.
                    >>>>
                    >>>
                    >>
                    >

                --
                You received this message because you are subscribed to
                the Google Groups "MDnalysis-devel" group.
                To unsubscribe from this group and stop receiving emails
                from it, send an email to
                mdnalysis-devel+unsubscribe@googlegroups.com
                <mailto:mdnalysis-devel+unsubscr...@googlegroups.com>.

                To post to this group, send email to
                mdnalysis-devel@googlegroups.com
                <mailto:mdnalysis-devel@googlegroups.com>.


                For more options, visit https://groups.google.com/d/optout.


            --
            You received this message because you are subscribed to the
            Google Groups "MDnalysis-devel" group.
            To unsubscribe from this group and stop receiving emails
            from it, send an email to

            To post to this group, send email to
            mdnalysis-devel@googlegroups.com
            <mailto:mdnalysis-devel@googlegroups.com>.


            For more options, visit https://groups.google.com/d/optout.


        --
        You received this message because you are subscribed to the
        Google Groups "MDnalysis-devel" group.
        To unsubscribe from this group and stop receiving emails from
        it, send an email to

        To post to this group, send email to
    You received this message because you are subscribed to a topic in
    the Google Groups "MDnalysis-devel" group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/mdnalysis-devel/QlwoL1_Etns/unsubscribe.
    To unsubscribe from this group and all its topics, send an email to

    To post to this group, send email to

    For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google
Groups "MDnalysis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send
--
You received this message because you are subscribed to the Google Groups "MDnalysis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mdnalysis-devel+unsubscribe@googlegroups.com.
To post to this group, send email to mdnalysis-devel@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mdnalysis-devel/b4107bb2-b5ae-fdb6-b114-1da8e4f73703%40gmail.com.

Max Linke

unread,
Feb 6, 2017, 4:51:11 PM2/6/17
to mdnalys...@googlegroups.com
We should continue future discussions about the testing on the github issue

https://github.com/MDAnalysis/mdanalysis/issues/884

On 02/06/2017 04:32 PM, Manuel Nuno Melo wrote:
> Good find.
>
> On the particular case they implement, it's a leak finder at a lower
> level than ours, and probably a good idea to add to/replace our check.
>
>
> On Sat, Feb 4, 2017 at 8:43 AM, Max Linke <max.l...@gmail.com
> <mailto:max.l...@gmail.com>> wrote:
>
> I found an interesting blog post that explains how we can
> port some if not most of our nose-plugins to pytest
>
> https://nvbn.github.io/2017/02/02/pytest-leaking/
> <https://nvbn.github.io/2017/02/02/pytest-leaking/>
>
> On 01/21/2017 09:30 PM, Richard Gowers wrote:
>
> Hey Jan. Some of the core tests are best maybe, there's a lot of
> tests
> where we go through AtomGroup ResidueGroup and SegmentGroup and
> check
> they all slice the same. Obviously crying out for a fixture instead.
>
>
> On Sat, 21 Jan 2017, 8:10 p.m. Max Linke, <max.l...@gmail.com
> <mailto:max.l...@gmail.com>
> <mailto:max.l...@gmail.com <mailto:max.l...@gmail.com>>>
> wrote:
>
> Mosts tests should just work. Some research about porting the
> plugins to pytest would be good though.
>
>
> On Sat, Jan 21, 2017, 20:47 Jan Domanski <jan...@gmail.com
> <mailto:jan...@gmail.com>
> <mailto:jan...@gmail.com <mailto:jan...@gmail.com>>> wrote:
>
> Re pytest overhaul issue, would it be advantageous to
> have some
> a single set of tests (a file) converted from nose to
> py.test –
> sort of "before and after" example?
>
> For one thing, it would help to estimate the amount of time
> needed, secondly, it would be some "preliminary" code
> for GSoc
> helping asses the viability of the project. i'm happy to put
> something together.
>
>
> On 20 January 2017 at 14:17, Manuel Nuno Melo
> <manuel.n...@gmail.com
> <mailto:manuel.n...@gmail.com>
> <mailto:manuel.n...@gmail.com
> <mailto:manuel.n...@gmail.com>>>
> wrote:
>
> +1 for the pytest overhaul initiative.
>
> On Fri, Jan 20, 2017 at 11:31 AM, Richard Gowers
> <richard...@gmail.com
> <mailto:richard...@gmail.com>
> <mailto:richard...@gmail.com <mailto:richard...@gmail.com>>>
> >>>>> <mailto:orbe...@gmail.com
> <mailto:orbe...@gmx.net
> <mailto:orbe...@gmx.net>>
> >>>>> skype: orbeckst *
> orbe...@gmail.com <mailto:orbe...@gmail.com>
> <mailto:orbe...@gmail.com
> <mailto:orbe...@gmail.com>>
> >>>>>
> >>>>> --
> >>>>> You received this message because
> you are subscribed to the Google
> >>>>> Groups "MDnalysis-devel" group.
> >>>>> To unsubscribe from this group and
> stop receiving emails from it,
> >>>>> send an email to
> mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-dev...@googlegroups.com>
> >>>>>
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com
> <mailto:mdnalysis-devel%252Buns...@googlegroups.com>>.
> >>>>> To post to this group, send email to
> >>>>> mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>
> >>>>>
> <mailto:mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>>.
> >>>>> To view this discussion on the web
> visit
> >>>>>
> https://groups.google.com/d/msgid/mdnalysis-devel/AC9516CA-7CB6-4262-B01E-2EF01AE7FDAA%40gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/AC9516CA-7CB6-4262-B01E-2EF01AE7FDAA%40gmail.com>
>
> >>>>>
> >>>>>
> >>>>>
> <https://groups.google.com/d/msgid/mdnalysis-devel/AC9516CA-7CB6-4262-B01E-2EF01AE7FDAA%40gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/AC9516CA-7CB6-4262-B01E-2EF01AE7FDAA%40gmail.com>>.
>
> >>>>>
> >>>>>
> >>>>> For more options, visit
> https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>
> >>>>>
> <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>>.
> >>>>>
> >>>>>
> >>>>> --
> >>>>> You received this message because you
> are subscribed to the Google
> >>>>> Groups "MDnalysis-devel" group.
> >>>>> To unsubscribe from this group and
> stop receiving emails from it, send
> >>>>> an email to
> mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-dev...@googlegroups.com>
> >>>>>
>
> <mailto:mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>>.
> >>>>> To post to this group, send email to
> mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>
> >>>>> <mailto:mdnalys...@googlegroups.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAFNMPM9c_mrRR%3DxAqhzsg%2BBQXEYPTbcX_marVm4HJwyhoEZx2g%40mail.gmail.com?utm_medium=email&utm_source=footer
> https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
> >>>>
> >>>
> >>
> >
>
> --
> You received this message because you are
> subscribed to
> the Google Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop
> receiving emails
> from it, send an email to
> mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>
>
> <mailto:mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>>.
> To post to this group, send email to
> mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>
> <mailto:mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>>.
> To view this discussion on the web visit
>
> https://groups.google.com/d/msgid/mdnalysis-devel/995b4574-a1f2-4392-ac31-93aa580b8047%40googlegroups.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/995b4574-a1f2-4392-ac31-93aa580b8047%40googlegroups.com>
>
> <https://groups.google.com/d/msgid/mdnalysis-devel/995b4574-a1f2-4392-ac31-93aa580b8047%40googlegroups.com?utm_medium=email&utm_source=footer
> https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed
> to the
> Google Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop receiving emails
> from it, send an email to
> mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>
> <mailto:mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>>.
> To post to this group, send email to
> mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>
> <mailto:mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>>.
> To view this discussion on the web visit
>
> https://groups.google.com/d/msgid/mdnalysis-devel/CAERWk%3D66NWaWYVteKZodh%3Du6VUaFtP8WhqbakvC9tCd%2B3GtmPQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAERWk%3D66NWaWYVteKZodh%3Du6VUaFtP8WhqbakvC9tCd%2B3GtmPQ%40mail.gmail.com>
>
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAERWk%3D66NWaWYVteKZodh%3Du6VUaFtP8WhqbakvC9tCd%2B3GtmPQ%40mail.gmail.com?utm_medium=email&utm_source=footer
> https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed to the
> Google Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop receiving emails
> from
> it, send an email to
> mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>
> <mailto:mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>>.
> To post to this group, send email to
> mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>
> <mailto:mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>>.
>
> To view this discussion on the web visit
>
> https://groups.google.com/d/msgid/mdnalysis-devel/CAH5w%3DBdFvkYNrmbKY4LzbO8Q2HE1dgg%3D%3DrA4xgdyMNxxFaxisA%40mail.gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAH5w%3DBdFvkYNrmbKY4LzbO8Q2HE1dgg%3D%3DrA4xgdyMNxxFaxisA%40mail.gmail.com>
>
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAH5w%3DBdFvkYNrmbKY4LzbO8Q2HE1dgg%3D%3DrA4xgdyMNxxFaxisA%40mail.gmail.com?utm_medium=email&utm_source=footer
> You received this message because you are subscribed to a
> topic in
> the Google Groups "MDnalysis-devel" group.
> To unsubscribe from this topic, visit
>
> https://groups.google.com/d/topic/mdnalysis-devel/QlwoL1_Etns/unsubscribe
> <https://groups.google.com/d/topic/mdnalysis-devel/QlwoL1_Etns/unsubscribe>.
> To unsubscribe from this group and all its topics, send an
> email to
> mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>
> <mailto:mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>>.
> To post to this group, send email to
> mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>
> <mailto:mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>>.
> To view this discussion on the web visit
>
> https://groups.google.com/d/msgid/mdnalysis-devel/CAKRyePDrfWsFhRaMdzuipZ1foaQJpbPvdu-G%3Dgi8-u2J6xSpXw%40mail.gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAKRyePDrfWsFhRaMdzuipZ1foaQJpbPvdu-G%3Dgi8-u2J6xSpXw%40mail.gmail.com>
>
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAKRyePDrfWsFhRaMdzuipZ1foaQJpbPvdu-G%3Dgi8-u2J6xSpXw%40mail.gmail.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAKRyePDrfWsFhRaMdzuipZ1foaQJpbPvdu-G%3Dgi8-u2J6xSpXw%40mail.gmail.com?utm_medium=email&utm_source=footer>>.
> For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop receiving emails from
> it, send
> an email to mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>
> <mailto:mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>>.
> To post to this group, send email to
> mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>
> <mailto:mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mdnalysis-devel/CAFk3ehndNRN85U1cACor4y_GruRCtGB%3DZrCEqfbT-_Sh9y%2Bt-A%40mail.gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAFk3ehndNRN85U1cACor4y_GruRCtGB%3DZrCEqfbT-_Sh9y%2Bt-A%40mail.gmail.com>
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAFk3ehndNRN85U1cACor4y_GruRCtGB%3DZrCEqfbT-_Sh9y%2Bt-A%40mail.gmail.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAFk3ehndNRN85U1cACor4y_GruRCtGB%3DZrCEqfbT-_Sh9y%2Bt-A%40mail.gmail.com?utm_medium=email&utm_source=footer>>.
> For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-devel%2Bunsu...@googlegroups.com>.
> To post to this group, send email to
> mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mdnalysis-devel/b4107bb2-b5ae-fdb6-b114-1da8e4f73703%40gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/b4107bb2-b5ae-fdb6-b114-1da8e4f73703%40gmail.com>.
>
> For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "MDnalysis-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to mdnalysis-dev...@googlegroups.com
> <mailto:mdnalysis-dev...@googlegroups.com>.
> To post to this group, send email to mdnalys...@googlegroups.com
> <mailto:mdnalys...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mdnalysis-devel/CAERWk%3D5%3D%3DoV913RqKk8PXyVH1ir2zVd0r-9yvfpeiaOr1B-FTg%40mail.gmail.com
> <https://groups.google.com/d/msgid/mdnalysis-devel/CAERWk%3D5%3D%3DoV913RqKk8PXyVH1ir2zVd0r-9yvfpeiaOr1B-FTg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
Reply all
Reply to author
Forward
0 new messages