Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Digest for mdnalysis-discussion@googlegro ups.com - 2 Messages in 1 Topic
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  17 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
bipin singh  
View profile  
 More options Nov 5 2012, 1:07 am
From: bipin singh <bipinel...@gmail.com>
Date: Mon, 5 Nov 2012 11:37:52 +0530
Local: Mon, Nov 5 2012 1:07 am
Subject: Re: [mdnalysis-discussion] Digest for mdnalysis-discussion@googlegroups.com - 2 Messages in 1 Topic

Thanks Sebastian for your reply.
I was able to install the MDAnalysis package after installing some
dependencies required for it.
Now I am trying to use Native contact module of this program as follows, at
the python interpreter:

>import MDAnalysis
>import MDAnalysis.analysis.contacts
>C = MDAnalysis.analysis.contacts.ContactAnalysis('md.gro','traj.xtc')

which resulted in segmentation fault. Am I doing this in correct way or I
have to provide the PSF/DCD format of topology and trajectory respectively ?

On Sun, Nov 4, 2012 at 10:48 AM, <mdnalysis-discussion@googlegroups.com>wrote:

--
-----------------------
*Regards,*
Bipin Singh

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Oliver Beckstein  
View profile  
 More options Nov 5 2012, 11:53 am
From: Oliver Beckstein <orbec...@gmail.com>
Date: Mon, 5 Nov 2012 09:53:03 -0700
Local: Mon, Nov 5 2012 11:53 am
Subject: Re: [mdnalysis-discussion] Digest for mdnalysis-discussion@googlegroups.com - 2 Messages in 1 Topic
Hi,

On 4 Nov, 2012, at 23:07, bipin singh wrote:

> Thanks Sebastian for your reply.
> I was able to install the MDAnalysis package after installing some dependencies required for it.
> Now I am trying to use Native contact module of this program as follows, at the python interpreter:

> >import MDAnalysis
> >import MDAnalysis.analysis.contacts
> >C = MDAnalysis.analysis.contacts.ContactAnalysis('md.gro','traj.xtc')

> which resulted in segmentation fault. Am I doing this in correct way or I have to provide the PSF/DCD format of topology and trajectory respectively ?

Segmentation fault is bad.

Can you do the following in python:

import MDAnalysis
u = MDAnalysis.Universe('md.gro','traj.xtc')
print u

If this works then also install the test cases and run all the unit tests as described at https://code.google.com/p/mdanalysis/wiki/UnitTests

import MDAnalysis.tests
MDAnalysis.tests.test(label="full")

Let us know the results.

Oliver

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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
bipin singh  
View profile  
 More options Nov 6 2012, 12:38 am
From: bipin singh <bipinel...@gmail.com>
Date: Tue, 6 Nov 2012 11:08:46 +0530
Local: Tues, Nov 6 2012 12:38 am
Subject: Re: [mdnalysis-discussion] Digest for mdnalysis-discussion@googlegroups.com - 2 Messages in 1 Topic

Thank you Sir, for your reply.
I followed your suggestion and used the following commands:

 >import MDAnalysis
 >u = MDAnalysis.Universe('md.gro','traj.xtc')

But again it resulted in segmentation fault.

On Tue, Nov 6, 2012 at 10:54 AM, <mdnalysis-discussion@googlegroups.com>wrote:

--
-----------------------
*Regards,*
Bipin Singh

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Discussion subject changed to "seg fault" by Oliver Beckstein
Oliver Beckstein  
View profile  
 More options Nov 6 2012, 12:09 pm
From: Oliver Beckstein <orbec...@gmail.com>
Date: Tue, 6 Nov 2012 10:09:47 -0700
Local: Tues, Nov 6 2012 12:09 pm
Subject: Re: [mdnalysis-discussion] seg fault
Hi Bipin Singh,

On 5 Nov, 2012, at 22:38, bipin singh wrote:

> Thank you Sir, for your reply.
> I followed your suggestion and used the following commands:

>  >import MDAnalysis
>  >u = MDAnalysis.Universe('md.gro','traj.xtc')

> But again it resulted in segmentation fault.

This looks like a problem with incompatible libraries.

You'll need to tell us exactly

- your operating system
- your version of the gcc compiler (gcc -V)
- your version of Python, NumPy, SciPy

Download the tar file from https://code.google.com/p/mdanalysis/downloads/detail?name=MDAnalysis... unpack and build

tar zxvf MDAnalysis-0.7.6.tar.gz
cd MDAnalysis-0.7.6
python setup.py build

Send the whole output from the 'build' process. For me this looks like (with most of it omitted as '...') like this:

$ python setup.py build
running build
running build_py
creating build
creating build/lib.macosx-10.6-universal-2.6
creating build/lib.macosx-10.6-universal-2.6/MDAnalysis
...
gcc-4.2 -Wl,-F. -bundle -undefined dynamic_lookup -arch i386 -arch ppc -arch x86_64 build/temp.macosx-10.6-universal-2.6/src/xdrfile/libxdrfile_wrap.o build/temp.macosx-10.6-universal-2.6/src/xdrfile/xdrfile.o build/temp.macosx-10.6-universal-2.6/src/xdrfile/xdrfile_trr.o build/temp.macosx-10.6-universal-2.6/src/xdrfile/xdrfile_xtc.o -o build/lib.macosx-10.6-universal-2.6/MDAnalysis/coordinates/xdrfile/_libxdrf ile.so

On the mailing list there was one other instance of segfault, which was fixed by reinstalling numpy and scipy:
https://groups.google.com/forum/#!searchin/mdnalysis-discussion/segme...

But until we have some better idea where the problem lies I cannot say much more.

Oliver

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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
bipin singh  
View profile  
 More options Nov 6 2012, 12:46 pm
From: bipin singh <bipinel...@gmail.com>
Date: Tue, 6 Nov 2012 23:16:24 +0530
Local: Tues, Nov 6 2012 12:46 pm
Subject: Re: [mdnalysis-discussion] seg fault

Hello Sir,

Thank you for your help. I am mentioning below the information you asked to
provide.

*Operating system*:Ubuntu 10.10
*gcc compiler version*: 4.4.5
*Python version*: 2.6.6
*Numpy version*: 1:1.3.0-3build1
*Scipy version*: 0.7.2-2ubuntu1

I will try to send the detail output of the build process ASAP.

On Tue, Nov 6, 2012 at 10:39 PM, Oliver Beckstein <orbec...@gmail.com>wrote:

--
-----------------------
Thanks and Regards,
Bipin Singh

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Oliver Beckstein  
View profile  
 More options Nov 6 2012, 12:55 pm
From: Oliver Beckstein <orbec...@gmail.com>
Date: Tue, 6 Nov 2012 10:55:46 -0700
Local: Tues, Nov 6 2012 12:55 pm
Subject: Re: [mdnalysis-discussion] seg fault

On 6 Nov, 2012, at 10:46, bipin singh wrote:

> Thank you for your help. I am mentioning below the information you asked to provide.

> Operating system:Ubuntu 10.10
> gcc compiler version: 4.4.5
> Python version: 2.6.6
> Numpy version: 1:1.3.0-3build1
> Scipy version: 0.7.2-2ubuntu1

That looks like a system it should work on — maybe someone else on the list had experience with this setup?

> I will try to send the detail output of the build process ASAP.

Ok, thanks.

I added a page https://code.google.com/p/mdanalysis/wiki/QuestionsAndAnswers#Why_do_... and maybe this already gives you some ideas what to try next.

Oliver

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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Sébastien Buchoux  
View profile  
 More options Nov 6 2012, 2:58 pm
From: Sébastien Buchoux <sebastien.buch...@gmail.com>
Date: Tue, 06 Nov 2012 20:58:37 +0100
Local: Tues, Nov 6 2012 2:58 pm
Subject: Re: [mdnalysis-discussion] seg fault
On 11/06/2012 06:46 PM, bipin singh wrote:

> Hello Sir,

> Thank you for your help. I am mentioning below the information you asked to
> provide.

> *Operating system*:Ubuntu 10.10

Ubuntu 10.10 (Codename Maverick Meerkat) is not supported since last
April (See: https://wiki.ubuntu.com/Releases). I would suggest you
upgrade your system to Ubuntu 12.04 LTS (Codename Precise Pangolin, the
latest "Long Time Support" version) or Ubuntu 12.10 (Codename Quantic
Quetzal, the lastest version)

> *gcc compiler version*: 4.4.5
> *Python version*: 2.6.6
> *Numpy version*: 1:1.3.0-3build1
> *Scipy version*: 0.7.2-2ubuntu1

As mentioned by Oliver, this setup should be OK.

> I will try to send the detail output of the build process ASAP.

Yes, this output will be useful to solve your problem and/or a potential
bug.

S b


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Oliver Beckstein  
View profile  
 More options Nov 6 2012, 3:11 pm
From: Oliver Beckstein <orbec...@gmail.com>
Date: Tue, 6 Nov 2012 13:11:06 -0700
Local: Tues, Nov 6 2012 3:11 pm
Subject: Re: [mdnalysis-discussion] seg fault

On 6 Nov, 2012, at 12:58, Sébastien Buchoux wrote:

>> Thank you for your help. I am mentioning below the information you asked to
>> provide.

>> *Operating system*:Ubuntu 10.10

Just another thought: Did you try one of the pre-built Ubuntu packages?
http://code.google.com/p/mdanalysis/wiki/Install#Installing_using_bin...

Oliver

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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
bipin singh  
View profile  
 More options Nov 6 2012, 11:31 pm
From: bipin singh <bipinel...@gmail.com>
Date: Wed, 7 Nov 2012 10:01:05 +0530
Local: Tues, Nov 6 2012 11:31 pm
Subject: Re: [mdnalysis-discussion] seg fault

Thank you sebastien for your suggestion. I know that Ubuntu10.10 is
outdated. Sorry but currently I can not afford to upgrade it to 12.XX
because I think I have to reinstall all the other programs (huge in
number), which are currently installed on my current Ubuntu version.

On Wed, Nov 7, 2012 at 1:28 AM, Sébastien Buchoux <

--
-----------------------
*Regards,*
Bipin Singh

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
bipin singh  
View profile  
 More options Nov 6 2012, 11:43 pm
From: bipin singh <bipinel...@gmail.com>
Date: Wed, 7 Nov 2012 10:13:48 +0530
Local: Tues, Nov 6 2012 11:43 pm
Subject: Re: [mdnalysis-discussion] seg fault

Please find below the output from the build process, using the command

>python setup.py build

########################################################################### ##############
running build
running build_py
creating build
creating build/lib.linux-i686-2.6
creating build/lib.linux-i686-2.6/MDAnalysis
copying MDAnalysis/__init__.py -> build/lib.linux-i686-2.6/MDAnalysis
creating build/lib.linux-i686-2.6/MDAnalysis/core
copying MDAnalysis/core/log.py -> build/lib.linux-i686-2.6/MDAnalysis/core
copying MDAnalysis/core/transformations.py ->
build/lib.linux-i686-2.6/MDAnalysis/core
copying MDAnalysis/core/util.py -> build/lib.linux-i686-2.6/MDAnalysis/core
copying MDAnalysis/core/units.py -> build/lib.linux-i686-2.6/MDAnalysis/core
copying MDAnalysis/core/__init__.py ->
build/lib.linux-i686-2.6/MDAnalysis/core
copying MDAnalysis/core/Timeseries.py ->
build/lib.linux-i686-2.6/MDAnalysis/core
copying MDAnalysis/core/AtomGroup.py ->
build/lib.linux-i686-2.6/MDAnalysis/core
copying MDAnalysis/core/Selection.py ->
build/lib.linux-i686-2.6/MDAnalysis/core
creating build/lib.linux-i686-2.6/MDAnalysis/topology
copying MDAnalysis/topology/PrimitivePDBParser.py ->
build/lib.linux-i686-2.6/MDAnalysis/topology
copying MDAnalysis/topology/PDBParser.py ->
build/lib.linux-i686-2.6/MDAnalysis/topology
copying MDAnalysis/topology/CRDParser.py ->
build/lib.linux-i686-2.6/MDAnalysis/topology
copying MDAnalysis/topology/__init__.py ->
build/lib.linux-i686-2.6/MDAnalysis/topology
copying MDAnalysis/topology/core.py ->
build/lib.linux-i686-2.6/MDAnalysis/topology
copying MDAnalysis/topology/TOPParser.py ->
build/lib.linux-i686-2.6/MDAnalysis/topology
copying MDAnalysis/topology/PQRParser.py ->
build/lib.linux-i686-2.6/MDAnalysis/topology
copying MDAnalysis/topology/PDBQTParser.py ->
build/lib.linux-i686-2.6/MDAnalysis/topology
copying MDAnalysis/topology/PSFParser.py ->
build/lib.linux-i686-2.6/MDAnalysis/topology
copying MDAnalysis/topology/GROParser.py ->
build/lib.linux-i686-2.6/MDAnalysis/topology
copying MDAnalysis/topology/tables.py ->
build/lib.linux-i686-2.6/MDAnalysis/topology
creating build/lib.linux-i686-2.6/MDAnalysis/selections
copying MDAnalysis/selections/charmm.py ->
build/lib.linux-i686-2.6/MDAnalysis/selections
copying MDAnalysis/selections/gromacs.py ->
build/lib.linux-i686-2.6/MDAnalysis/selections
copying MDAnalysis/selections/__init__.py ->
build/lib.linux-i686-2.6/MDAnalysis/selections
copying MDAnalysis/selections/vmd.py ->
build/lib.linux-i686-2.6/MDAnalysis/selections
copying MDAnalysis/selections/pymol.py ->
build/lib.linux-i686-2.6/MDAnalysis/selections
copying MDAnalysis/selections/base.py ->
build/lib.linux-i686-2.6/MDAnalysis/selections
creating build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/XTC.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/TRJ.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/TRR.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/XYZ.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/PDBQT.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/GRO.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/__init__.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/LAMMPS.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/DCD.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/core.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/CRD.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/PQR.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/PDB.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
copying MDAnalysis/coordinates/base.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates
creating build/lib.linux-i686-2.6/MDAnalysis/coordinates/xdrfile
copying MDAnalysis/coordinates/xdrfile/XTC.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates/xdrfile
copying MDAnalysis/coordinates/xdrfile/libxdrfile.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates/xdrfile
copying MDAnalysis/coordinates/xdrfile/TRR.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates/xdrfile
copying MDAnalysis/coordinates/xdrfile/__init__.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates/xdrfile
copying MDAnalysis/coordinates/xdrfile/statno.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates/xdrfile
copying MDAnalysis/coordinates/xdrfile/core.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates/xdrfile
creating build/lib.linux-i686-2.6/MDAnalysis/coordinates/pdb
copying MDAnalysis/coordinates/pdb/__init__.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates/pdb
copying MDAnalysis/coordinates/pdb/extensions.py ->
build/lib.linux-i686-2.6/MDAnalysis/coordinates/pdb
creating build/lib.linux-i686-2.6/MDAnalysis/util
copying MDAnalysis/util/LAMMPSParser.py ->
build/lib.linux-i686-2.6/MDAnalysis/util
copying MDAnalysis/util/__init__.py ->
build/lib.linux-i686-2.6/MDAnalysis/util
copying MDAnalysis/util/Transformation.py ->
build/lib.linux-i686-2.6/MDAnalysis/util
creating build/lib.linux-i686-2.6/MDAnalysis/KDTree
copying MDAnalysis/KDTree/KDTree.py ->
build/lib.linux-i686-2.6/MDAnalysis/KDTree
copying MDAnalysis/KDTree/__init__.py ->
build/lib.linux-i686-2.6/MDAnalysis/KDTree
copying MDAnalysis/KDTree/CKDTree.py ->
build/lib.linux-i686-2.6/MDAnalysis/KDTree
copying MDAnalysis/KDTree/NeighborSearch.py ->
build/lib.linux-i686-2.6/MDAnalysis/KDTree
creating build/lib.linux-i686-2.6/MDAnalysis/analysis
copying MDAnalysis/analysis/helanal.py ->
build/lib.linux-i686-2.6/MDAnalysis/analysis
copying MDAnalysis/analysis/hbonds.py ->
build/lib.linux-i686-2.6/MDAnalysis/analysis
copying MDAnalysis/analysis/gnm.py ->
build/lib.linux-i686-2.6/MDAnalysis/analysis
copying MDAnalysis/analysis/__init__.py ->
build/lib.linux-i686-2.6/MDAnalysis/analysis
copying MDAnalysis/analysis/leaflet.py ->
build/lib.linux-i686-2.6/MDAnalysis/analysis
copying MDAnalysis/analysis/distances.py ->
build/lib.linux-i686-2.6/MDAnalysis/analysis
copying MDAnalysis/analysis/align.py ->
build/lib.linux-i686-2.6/MDAnalysis/analysis
copying MDAnalysis/analysis/density.py ->
build/lib.linux-i686-2.6/MDAnalysis/analysis
copying MDAnalysis/analysis/nuclinfo.py ->
build/lib.linux-i686-2.6/MDAnalysis/analysis
copying MDAnalysis/analysis/contacts.py ->
build/lib.linux-i686-2.6/MDAnalysis/analysis
creating build/lib.linux-i686-2.6/MDAnalysis/builder
copying MDAnalysis/builder/charmm.py ->
build/lib.linux-i686-2.6/MDAnalysis/builder
copying MDAnalysis/builder/__init__.py ->
build/lib.linux-i686-2.6/MDAnalysis/builder
creating build/lib.linux-i686-2.6/MDAnalysis/tests
copying MDAnalysis/tests/__init__.py ->
build/lib.linux-i686-2.6/MDAnalysis/tests
copying MDAnalysis/tests/datafiles.py ->
build/lib.linux-i686-2.6/MDAnalysis/tests
running build_ext
building 'coordinates._dcdmodule' extension
creating build/temp.linux-i686-2.6
creating build/temp.linux-i686-2.6/src
creating build/temp.linux-i686-2.6/src/dcd
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -fPIC
-I/usr/lib/python2.6/dist-packages/numpy/core/include -Isrc/dcd/include
-I/usr/include/python2.6 -c src/dcd/dcd.c -o
build/temp.linux-i686-2.6/src/dcd/dcd.o
src/dcd/include/endianswap.h:32: warning: ‘swap2_unaligned’ defined but not
used
src/dcd/include/endianswap.h:96: warning: ‘swap2_aligned’ defined but not
used
src/dcd/include/fastio.h:140: warning: ‘fio_open’ defined but not used
src/dcd/include/fastio.h:159: warning: ‘fio_fclose’ defined but not used
src/dcd/include/fastio.h:232: warning: ‘fio_read_int32’ defined but not used
src/dcd/include/fastio.h:236: warning: ‘fio_write_str’ defined but not used
src/dcd/include/readdcd.h:626: warning: ‘jump_to_dcdstep’ defined but not
used
gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
build/temp.linux-i686-2.6/src/dcd/dcd.o -o
build/lib.linux-i686-2.6/MDAnalysis/coordinates/_dcdmodule.so
building 'coordinates.dcdtimeseries' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -fPIC
-I/usr/lib/python2.6/dist-packages/numpy/core/include -Isrc/dcd/include
-I/usr/include/python2.6 -c src/dcd/dcdtimeseries.c -o
build/temp.linux-i686-2.6/src/dcd/dcdtimeseries.o
src/dcd/include/endianswap.h:32: warning: ‘swap2_unaligned’ defined but not
used
src/dcd/include/endianswap.h:96: warning: ‘swap2_aligned’ defined but not
used
src/dcd/include/fastio.h:140: warning: ‘fio_open’ defined but not used
src/dcd/include/fastio.h:159: warning: ‘fio_fclose’ defined but not used
src/dcd/include/fastio.h:219: warning: ‘fio_ftell’ defined but not used
src/dcd/include/fastio.h:232: warning: ‘fio_read_int32’ defined but not used
src/dcd/include/fastio.h:236: warning: ‘fio_write_str’ defined but not used
src/dcd/include/readdcd.h:169: warning: ‘read_dcdheader’ defined but not
used
src/dcd/include/readdcd.h:502: warning: ‘read_dcdstep’ defined but not used
src/dcd/include/readdcd.h:758: warning: ‘close_dcd_read’ defined but not
used
src/dcd/include/readdcd.h:690: warning: ‘write_dcdheader’ defined but not
used
src/dcd/include/readdcd.h:653: warning: ‘write_dcdstep’ defined but not used
gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
build/temp.linux-i686-2.6/src/dcd/dcdtimeseries.o -o
build/lib.linux-i686-2.6/MDAnalysis/coordinates/dcdtimeseries.so
building 'core.distances' extension
creating build/temp.linux-i686-2.6/src/numtools
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall ...

read more »


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
bipin singh  
View profile  
 More options Nov 7 2012, 12:06 pm
From: bipin singh <bipinel...@gmail.com>
Date: Wed, 7 Nov 2012 22:36:09 +0530
Local: Wed, Nov 7 2012 12:06 pm
Subject: Re: [mdnalysis-discussion] seg fault

I was trying the Ubuntu packages but they require some more recent versions
of python (>= 2.7.1-0ubuntu2) and has some other dependency requirements.

In the mean time I tried the debugger as suggested by you. But all the
program exited normally without any seg. fault. I am appending the output
got by running the debugger:

#######################################################################
(gdb) run -c "import MDAnalysis; print MDAnalysis.__version__"
Starting program: /usr/bin/python -c "import MDAnalysis; print
MDAnalysis.__version__"
[Thread debugging using libthread_db enabled]
0.7.6

Program exited normally.
(gdb) run -c "import MDAnalysis; print MDAnalysis.Universe"
Starting program: /usr/bin/python -c "import MDAnalysis; print
MDAnalysis.Universe"
[Thread debugging using libthread_db enabled]
<class 'MDAnalysis.core.AtomGroup.Universe'>

Program exited normally.
##########################################################################

--
-----------------------
*Regards,*
Bipin Singh

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
bipin singh  
View profile  
 More options Nov 7 2012, 1:01 pm
From: bipin singh <bipinel...@gmail.com>
Date: Wed, 7 Nov 2012 23:31:23 +0530
Local: Wed, Nov 7 2012 1:01 pm
Subject: Re: [mdnalysis-discussion] seg fault

I am appending the output got by running the suggested command on my .xtc
trajectory:

########################################################################### ###############
(gdb) run -c "import MDAnalysis; print MDAnalysis.Universe('md.pdb',
'traj.xtc')"
Starting program: /usr/bin/python -c "import MDAnalysis; print
MDAnalysis.Universe('b4md.pdb', 'sixb_rerun_widvelfromnpt_md450_nopbc.xtc')"
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x0127274b in xdrfile_write_int (ptr=0xbfffde9c, ndata=1, xfp=0x0) at
src/xdrfile/xdrfile.c:258
258        while(i<ndata && xdr_int((XDR *)(xfp->xdr),ptr+i))
(gdb)
########################################################################### ###############
On Wed, Nov 7, 2012 at 11:21 PM, Oliver Beckstein <orbec...@gmail.com>wrote:

--
-----------------------
*Regards,*
Bipin Singh

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
bipin singh  
View profile  
 More options Nov 7 2012, 11:59 pm
From: bipin singh <bipinel...@gmail.com>
Date: Thu, 8 Nov 2012 10:29:00 +0530
Subject: Re: [mdnalysis-discussion] seg fault

Hello Sir,
Just for your information. I want to convey that, I have tried six
different trajectories(.xtc) and the same error occurred in every case, so
I think the error is not specific to a particular trajectory.
On Wed, Nov 7, 2012 at 11:49 PM, Oliver Beckstein <orbec...@gmail.com>wrote:

--
-----------------------
*Regards,*
Bipin Singh

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
bipin singh  
View profile  
 More options Nov 8 2012, 12:08 am
From: bipin singh <bipinel...@gmail.com>
Date: Thu, 8 Nov 2012 10:38:32 +0530
Local: Thurs, Nov 8 2012 12:08 am
Subject: Re: [mdnalysis-discussion] seg fault

I am appending the output got by running test cases:

########################################################################### #

>>> from MDAnalysis.tests.datafiles import PSF, DCD, GRO, XTC, TRR
>>> print MDAnalysis.Universe(PSF, DCD)

<Universe with 3341 atoms>
>>> print MDAnalysis.Universe(GRO, XTC)

<Universe with 47681 atoms>
>>> print MDAnalysis.Universe(GRO, TRR)

<Universe with 47681 atoms>
>>> import MDAnalysis.tests
>>> MDAnalysis.tests.test(label="full")

Running unit tests for numpy
NumPy version 1.3.0
NumPy is installed in /usr/lib/python2.6/dist-packages/numpy
Python version 2.6.6 (r266:84292, Sep 15 2010, 15:52:39) [GCC 4.4.5]
nose version 0.11.1

----------------------------------------------------------------------
Ran 0 tests in 0.015s

OK
<nose.result.TextTestResult run=0 errors=0 failures=0>
########################################################################### #

--
-----------------------
*Regards,*
Bipin Singh

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
bipin singh  
View profile  
 More options Nov 9 2012, 12:20 am
From: bipin singh <bipinel...@gmail.com>
Date: Fri, 9 Nov 2012 10:50:43 +0530
Local: Fri, Nov 9 2012 12:20 am
Subject: Re: [mdnalysis-discussion] seg fault

I am trying to provide the answers of the questions asked by you:

1) How did you create your xtcs?

I have created my .xtc from .trr using trjconv module of GROMACS.

2) Which version of Gromacs?

I have used GROMACS 4.5.3 version.

3) What does 'gmxcheck -f your.xtc' produce?

# Atoms  29751
Precision 0.001 (nm)
Last frame      50000 time 100000.000
Item        #frames Timestep (ps)
Step         50001    2
Time         50001    2
Lambda           0
Coords       50001    2
Velocities       0
Forces           0
Box          50001    2

I am dumping the output produced by running

>>> MDAnalysis.tests.test(label="full", extra_argv=["--exe"])

########################################################################### #################################
>>> MDAnalysis.tests.test(label="full", extra_argv=["--exe"])

Running unit tests for numpy
NumPy version 1.3.0
NumPy is installed in /usr/lib/python2.6/dist-packages/numpy
Python version 2.6.6 (r266:84292, Sep 15 2010, 15:52:39) [GCC 4.4.5]
nose version 0.11.1
Fitted frame    98/98  [100.0%]
..E..creating
/tmp/bipin/python26_intermediate/compiler_aa0a423c34a704de9b08c95a98137791
0.0 percent done
.HBonds frame     1/1 [100.0%]
.HBonds frame     1/1 [100.0%]
.HBonds frame     1/1 [100.0%]
./usr/local/lib/python2.6/dist-packages/MDAnalysis-0.7.6-py2.6-linux-i686.e gg/MDAnalysis/analysis/hbonds.py:571:
DeprecationWarning: _get_bonded_hydrogens_list() does not always find all
hydrogens; detect_hydrogens='distance' is safer.
  category=DeprecationWarning)
HBonds frame     1/1 [100.0%]
.HBonds frame     1/1 [100.0%]
.HBonds frame     1/1 [100.0%]
................F......................../usr/local/lib/python2.6/dist-pack ages/MDAnalysis-0.7.6-py2.6-linux-i686.egg/MDAnalysis/core/AtomGroup.py:108 1:
DeprecationWarning: velocities() will become an attribute 'velocities' in
0.8
  category=DeprecationWarning)
..../usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'N' for Atom (name=N) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HT1' for Atom (name=HT1)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HT2' for Atom (name=HT2)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HT3' for Atom (name=HT3)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'CA' for Atom (name=CA) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HA' for Atom (name=HA)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'CB' for Atom (name=CB)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HB1' for Atom (name=HB1)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HB2' for Atom (name=HB2)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'CG' for Atom (name=CG)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HG1' for Atom (name=HG1)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HG2' for Atom (name=HG2)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'SD' for Atom (name=SD)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'CE' for Atom (name=CE) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HE1' for Atom (name=HE1)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HE2' for Atom (name=HE2)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HE3' for Atom (name=HE3)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'C' for Atom (name=C) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'O' for Atom (name=O) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HN' for Atom (name=HN)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'CD' for Atom (name=CD) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HD1' for Atom (name=HD1)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HD2' for Atom (name=HD2)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'NE' for Atom (name=NE) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'HE' for Atom (name=HE) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'CZ' for Atom (name=CZ)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'NH1' for Atom (name=NH1)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'H' for Atom (name=HH11) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'H' for Atom (name=HH12) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'NH2' for Atom (name=NH2)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'H' for Atom (name=HH21) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'H' for Atom (name=HH22) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HB' for Atom (name=HB)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'CG2' for Atom (name=CG2)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'H' for Atom (name=HG21) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'H' for Atom (name=HG22) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'H' for Atom (name=HG23) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'CG1' for Atom (name=CG1)
with given element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'H' for Atom (name=HG11) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Used element 'H' for Atom (name=HG12) with given
element ''
  warnings.warn(msg, PDBConstructionWarning)
/usr/local/lib/python2.6/dist-packages/Bio/PDB/Atom.py:99:
PDBConstructionWarning: Could not assign element 'HD3' for ...

read more »


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
bipin singh  
View profile  
 More options Nov 9 2012, 12:25 am
From: bipin singh <bipinel...@gmail.com>
Date: Fri, 9 Nov 2012 10:55:33 +0530
Local: Fri, Nov 9 2012 12:25 am
Subject: Re: [mdnalysis-discussion] seg fault

Regarding your 4th question, I have tested the same commands with
trajectory (.xtc) containing 3 frames but this time it did not showed any
error.

On Thu, Nov 8, 2012 at 11:34 PM, Oliver Beckstein <orbec...@gmail.com>wrote:

--
-----------------------
*Regards,*
Bipin Singh

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Oliver Beckstein  
View profile  
 More options Nov 13 2012, 1:19 pm
From: Oliver Beckstein <orbec...@gmail.com>
Date: Tue, 13 Nov 2012 10:19:10 -0800 (PST)
Local: Tues, Nov 13 2012 1:19 pm
Subject: Re: [mdnalysis-discussion] seg fault

Hi Bipin,

Regarding your 4th question, I have tested the same commands with

>> trajectory (.xtc) containing 3 frames but this time it did not showed any
>> error.

On 9 Nov, 2012, at 10:58, bipin singh wrote:

I have tried to produce the minimum size "test" trajectory which can

> produce the seg. fault (turn out to be in ~2.5GB). I am giving the link for
> the same, Please try to download and check for the error on your side.

I tried your test trajectory with MDAnalysis-0.7.7-devel (but there
shouldn't be any differences compared to the 0.7.6 that you used, at least
not in this respect because that part of the code did not change):

   - on Linux Ubuntu 12.04.1 x86_64

Linux  3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012 x86_64
x86_64 x86_64 GNU/Linux
Python 2.7.3

   - on Mac OS X 10.6.8 i386

Darwin 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011;
root:xnu-1504.15.3~1/RELEASE_I386 i386 i386

and both work:

>>> u = MDAnalysis.Universe("test.pdb", "test.xtc")
>>> print u

<Universe with 32956 atoms>
>>> print u.trajectory

< XTCReader 'test.xtc' with 25001 frames of 32956 atoms (0 fixed) >

I'm also able to analyze it, e.g.

protein = u.selectAtoms("protein")
rgyr = [(u.trajectory.time, protein.radiusOfGyration()) for ts in
u.trajectory[::10]]

Thus, I cannot reproduce your error, which makes it more difficult to fix.

One possibility is that it has something to do with the size of your
trajectory. Under certain circumstances (32-bit linux without setting
certain compilation flags for large file support) there's a 2 GB file size
limit. Can you try to produce

   1. a very short trajectory (only a few frames)
   2. a trajectory a bit smaller than 2GB and
   3. one a bit larger than 2GB

check which ones lead to the seg fault.

Also send the output of 'uname -a', perhaps you have a 32-bit system?

If anyone else has *any* ideas what could be going on, I'd be happy to hear
them!

Thanks,
Oliver


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »