Hi Thilini,
The violation is subject to the calculated structure of that job not the previous one. Even if you change the restraint to meet the criterion from the current structure, it does not guarantee it is the solved problem in the next structure calculated. So, you have to run multiple times with fixed restraints. Also, if you are running “automated NOE analysis” options like AUDANA/AUDASA or PONDEROSA-X, it can introduce disabled restraint from the previous run. It has to be “constraints only-X” options.
Best,
Woonghee
--
Woonghee Lee, I.E.I.P., M.S., Ph.D.
Assistant Professor
Department of Chemistry
University of Colorado Denver
1151 Arapahoe St. (Science Bldg.) Rm 4128A
Denver, CO 80217-3364, USA
Office: +1-303-315-7672
https://poky.clas.ucdenver.edu
https://poky.clas.ucdenver.edu/wlee-group
https://clas.ucdenver.edu/chemistry/woonghee-lee
Shipping/Mailing Address:
Woonghee Lee
1201 5th St. UCD CHEM-194
P.O. Box 173364 (USPS)
Denver, CO 80204, USA
From: Thilini O Ukwaththage <tuk...@lsu.edu>
Date: Thursday, April 8, 2021 at 9:51 AM
To: "Lee, Woonghee" <WOONGH...@UCDENVER.EDU>
Subject: Set to imit does not work
Dear Dr. Lee,
Hope you are doing good!
I am using PONDEROSA analyzer and when I use the "set to limit" option on some distance constraints, it does not change the number of violations to zero (nothing happens) and they are reappearing in the next distance constraints after submitting with Ponderosa client. (But some distance constraints work fine with set to limit option, not all constraints have that problem) Can you let me know how to fix this problem. I am using ponderosa analyzer built on 2020/01/21.
Thank you
Regards
Thilini