Subject: Changing residue numbering when transferring/simulating peaks
From: blankforlife
Date: May 4, 2018

Next: 1325


When transferring peaks from a BMRB, residue numbers appear to automatically use the first residue numbering (which starts from 1) rather than the second residue numbering, sometimes specified under _Atom_chem_shift.Auth_seq_ID. Is there a way to manually change the first residue number for transferred/simulated peaks or to force it to use another reside number column? Or must the BMRB file be altered or each peak residue number be changed to accomplish this?