The only way to see the current viewing level is to use "edlev",

"Last real peak" is really in the eye of the beholder.

You have two parameters that somewhat describe the intensities in a 2D spectrum.

Y_MAX is the highest intensity and S_DEV is a standard deviation of all points. Based on these two you can calculate a MI that is reasonable for the spectrum.

You can define the peak picking regions with F1P and F2P in both dimensions.

The execute the peak picking the first region with "PP nodia" and for all subsequent regions with "pp nodia append". This way you can piece together a series of regions.

Dear Joseph,

you can use f1p and f2p to define a region. After you type plotreg the defined region is displayed on screen. The command pps picks peaks only in this region.

If you define then another strip the peaks in the first strip are unfortunately overwritten by the next pps command...but maybe it helps.

Alfred

Alfred Ross if you use the command "pps append" it does not overwrite the first region. So, define limits -> plotreg -> pps -> define new limits -> plotreg -> pps append -> repeat

Just wanted to provide some more clarification, in case anyone is attempting to use scripts to do this, as I have been.

In python for Topspin, there are (at least) two options to peak pick with a silent option. Option 1 is to use "PP("silent")", and option 2 is to use "XCMD("pps")". Both will allow you to append by extending the argument to either "PP("silent append")"or "XCMD("pps append")". However, it states in the topspin documentation that you should not use XCMD when there is a native instance of a topspin command, such as with PP().

However, it seems there is an odd behavior with the "append" command. For instance, if I set PPMPNUM to 1000, and the MI to a VERY low number (MI = 0.00005) then PP("silent"), it limits the number of peaks to the expected 1000, but if I define a second region and follow up with PP('silent append'), the 1000 peak limit is ignored completely. (in the example I have pulled up at the moment, the second instance picks 2700+ peaks, for a total of 3700+ peaks).

At first, I thought it was just bypassing PPMPNUM for the second peak pick event, but:

If I re-declare PPMPNUM, setting it to 100 peaks, then the second instance of PP("silent append") picks 1100 peaks. Essentially, it seems to be evaluating the second peak picking event as PPMPNUM(old value)+PPMPNUM(new value).

To confuse it even more, if I set PPMPNUM(new value) as zero, the program seems to evaluate it as null and returns to the first scenario's behavior.

I have attached an example script for those who are curious, but since this all essentially is peak picking noise, I imagine this as more of a thought experiment than an actual limitation or problem.