[gmx-users] Re: RMSF error when fitting to average structure

2012-08-16 Thread tdgrant1
No they do not. The trajectory contains all the atoms, including the solvent (~300,000 atoms), whereas the structure passed to -s is the averaged structure from the last 60ns of simulation and only includes the non-solvent atoms (~15,000). Should I rerun rmsf on the last 60ns but select System in

[gmx-users] Re: RMSF error when fitting to average structure

2012-08-16 Thread tdgrant1
This "System" as described by group 0 in the previous message is actually only the solute, a protein-tRNA complex of ~15000 atoms. I tried running only the backbone and even only c-alphas (808 atoms total) and I still received a segmentation fault. -- View this message in context: http://groma

[gmx-users] Re: RMSF error when fitting to average structure

2012-08-16 Thread tdgrant1
Oh okay, thanks. I didn't realize warnings were just that, only warnings and didn't stop the program. The program did not finish however, and the problem was a Segmentation Fault. The output literally was: Select a group: 0 Selected 0: 'System' Reading frame 0 time0.000 WARNING: if

[gmx-users] Re: RMSF error when fitting to average structure

2012-08-16 Thread tdgrant1
Hi Justin, I did indeed correct for periodic boundary conditions prior to running rmsf, so I'm not sure what the problem would be there. Is there any way of producing an average structure from rmsf (or any other program for that matter) that is not output as a .pdb file but as a .tpr file? T

[gmx-users] RMSF error when fitting to average structure

2012-08-16 Thread tdgrant1
Dear all, I have a 70 ns trajectory for which the last 60 ns appears to be equilibrated. I'm attempting to create a plot of RMSF but I want to align it to the equilibrated structure, not the starting structure. I first ran g_rmsf using the starting structure as the reference structure over only

[gmx-users] Re: Distance restraints not working

2012-05-23 Thread tdgrant1
There are a few possibilities. > > 1. Numbering in [distance_restraints] is not based on .gro numbering. The > atom > numbers supplied are only relevant within the [moleculetype] to which they > belong, much like [position_restraints]. Also make sure that the > [distance_restraints] block i