Hi Mike,
First, It would be better to discuss the code issue in this GOOGLE group instead of a private one, so other users can learn if they have similar ones.
Thank you for sharing your trajectory file. I just had a check (sorry for the late response), my laptop can process the file to frame 222 but also crash by using your command:
cac Test.lammpstrj Test.lammpstrj xy 50 300 1 {index 0 to 5975} 3 0.0324 0.1 3 0.5 0.5
Here the atomselection parameter is modified, you have 5976 water atoms with index starting from 0, so your atomselection parameter should be {index 0 to 5975}. Your previous command made two mistakes here:1, you didn't start from 0, and the number of atoms is wrong.
----------------------- PLEASE NOTE -----------------------
VMD atom index start from 0
I think there does exist a memory problem. But don't worry, this can be addressed. I suggest you do the following:
Solution_1
1, Load your whole trajectory into VMD;
2, Save the frames you would like to compute in VMD;
3. Load the new saved smaller trajectory file, and do the calculation.
Try this command:
cac Test.lammpstrj Test.lammpstrj xy 0 250 1 {index 0 to 5975} 3 0.0324 0.1 3 0.5 0.5
But this may still cause the memory problem, if so, try the next.
Solution_2
You said you can compute about 80 frames, this is good. Please note, it is unnecessary to set the step as 1, you can use a larger step, such as 5 or 10, so you can still compute frome frame 50 and stop at frame 300, but with a much smaller number of computed frames, such as only 50 if the step is 5, that normally can still give you a smooth profile I think.
Try this command:
cac Test.lammpstrj Test.lammpstrj xy 50 300 5 {index 0 to 5975} 3 0.0324 0.1 3 0.5 0.5
I hope that can help you.
Best regards,
Yuxiang