Another way to sort: X_HIT

Sample file attached for your reference.

This is the normal path with X_HIT(n,2).

This is the ghost path with X_HIT(n,3). It means the ray reflects from the front surface.

This is the case with X_HIT(n,4). This means the ray refracts from the back surface.

By the way, the filter string may not work if the keyword input is not set to English. Below is the difference between English and Chinese input.

In the second screenshot you have sone extra spaces in the filter string. Does that affect it?

Hey Mark, 

In the second screenshot, the “extra space” is actually a Unicode space in non-English keyboard.  So this non-English space would cause issues since OpticStudio doesn’t know how to parse it.  With a “normal” ASCII space, it doesn’t matter how many you use between & or | as long a Xn values are in contact and any values between parenthesis are valid.

I do want to note the beauty of the Jn filter string (similar to Gn).  This will show the ghost images off of a certain lens (it doesn't really matter which face the ghost occurs because you need at least 2 Fresnel reflections from a lens to get ghost rays to the detector plane) while zeroing out all previous energy in the segment (all “direct” transmission of the original ray is ignored).  It is quite useful to analyze just the ghost energy from a specific lens.  

Oh brother! Some poor developer will lose hair trying to accommodate that one!