What trajectory format are you using for TUPA?
-Dan
On Wed, Nov 13, 2024 at 5:07 PM Guberman-Pfeffer, Matthew
<Matthew_Guberman-Pfe.baylor.edu> wrote:
>
> Hi Dan,
>
> I’m encountering the following issue: I understand that the system becomes un-aligned with the x-axis after RMS fitting. Now I’m trying to use the TUPÂ program to compute the electric field, and when PBC conditions are applied by TUPÂ (which uses MDAnalysis) something goes wrong because the electric field becomes astronomical. If I turn off periodic conditions or delete the solvent, the problem goes away entirely. Curiously, the issue only happens for some (not all) frames) of the trajectory. The problem also does not happen if I do not RMS-fit, but I was told that the electric field is not physically meaningful in that case.
>
> I’m really perplexed and scrambling for an explanation/fix. Could the issue be the way the x-axis un-aligned system is being handled? What can you suggest?
>
> Best,
> Matthew
>
>
>
>
>
> On Nov 11, 2024, at 8:18 AM, Guberman-Pfeffer, Matthew <Matthew_Guberman-Pfe.baylor.edu> wrote:
>
> Hi Dan,
>
> Thanks for explaining the warning! Otherwise, did my cpptraj script for centering and RMS-fitting looked OK?
>
> Best,
> Matthew
>
>
>
> On Nov 11, 2024, at 8:04 AM, Daniel Roe <daniel.r.roe.gmail.com> wrote:
>
> Hi,
>
> On Sun, Nov 10, 2024 at 11:45 PM Guberman-Pfeffer, Matthew via AMBER
> <amber.ambermd.org> wrote:
>
>
> Warning: Set 1; unit cell is not X-aligned. Box cannot be properly stored as Amber NetCDF trajectory.
>
>
> When you RMS-fit in cpptraj, the atom coordinates and unit cell
> vectors are rotated according to the calculated best-fit rotation. In
> the Amber NetCDF format (along with many other trajectory formats),
> unit cell vectors are stored as 3x lengths and 3x angles - 6 numbers
> total. The reason this works is that the unit cell is assumed to be
> X-aligned; i.e. the unit cell X vector is colinear with the global X
> axis vector (the Y and Z components of the X-axis vector coordinate
> are 0). Once you rotate the unit cell vectors the unit cell X-axis
> vector is no longer colinear, so the unit cell can no longer be
> described with just 3x lengths and 3x angles. The consequence of this
> is that imaging will no-longer work properly with that trajectory,
> which is why cpptraj prints the warning. If you want to keep the
> rotated unit cell vectors, the only solution at the moment is to use a
> trajectory format that stores the full unit cell vector coordinates
> (like TRR or XTC). If you don't care about the unit cell
> vectors/imaging, you can just remove the unit cell information with
> the 'nobox' keyword of 'trajout'.
>
> Hopefully this makes sense.
>
> -Dan
>
>
>
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Thu Nov 14 2024 - 06:30:02 PST
