Here, you define the range in delta, xptar, and yptar that you wish to populate for each spectrometer. As a rule, you shouldn't need to change these much for different kinematics, as long as you start out with cuts that cover the full acceptance (except with the longer cryotargets). Your cuts (especially the delta cuts) do not need to cover the entire acceptance of the spectrometer, but you DO need to make sure that you only look at data within these limits when you analyze the Ntuples. Events will be generated beyond the limits you give here, but the normalization will not be correct outside of these limits. SIMC does increase the limits you give it in order to account for resolution, energy loss, and multiple scattering. Therefore, you should not need to artificially increase your generation limits well beyond the range in which you wish to analyze the data, but it's always wise to do a test with larger limits in order to insure that you don't loose counts. Because these are given for the electron vs hadron arm (rather than HMS vs SOS), you need to swap the SPedge.e.* limits with the SPedge.p.* limits if you go from putting electrons in the HMS to electrons in the SOS (and possibly increase or decrease them, depending on the cuts you will use in the analysis).
In the following example, hms_e_flag was set to zero, and so the electron arm is the SOS. Therefore, the delta range is fairly large, and the 90 mr in plane and 50 mr out of plane are somewhat larger than the SOS octagon. Note that the SOS will accept events well beyond +/-22%. If you want to simulate that data, then you need to increase these limits. However, as long as you are applying a delta cut that is below +/-22%, this is OK.
SPedge.e.delta.min = -22.0 ; delta min (%) (SPECTROMETER ACCEPTANCE!) SPedge.e.delta.max = 22.0 ; delta max (%) SPedge.e.yptar.min = -90.0 ; yptar min (mrad) SPedge.e.yptar.max = 90.0 ; yptar max (mrad) SPedge.e.xptar.min = -50.0 ; xptar min (mrad) SPedge.e.xptar.max = 50.0 ; xptar max (mrad)