Each time a single `izernike` command inputs zk perturbation to M1. We explore all zk4-22, for various rotation angles. For `rotCamInDeg` passed as `rotSkyPos` in the `inst` file, there is no dependence on the angle when simulating a single star on the boresight - all rotation angles yield the same results . For example, results of inputting 250 nm of zk13, at various rotation angles (result are numerically the same). This is what the test assumed - that there is no dependence on the rotation with `rotSkyPos: 
Inputting different zk at a particular rotation angle is summarized below. There is a peak corresponding to each input zk (marked by a vertical dashed line with color matching the fit results). One panel for zk5:13:

and another panel for zk14:22:

Implementation with `CloseLoopTask` - using that class and its tools, while running only 1 iteration https://github.com/suberlak/AOS/blob/main/AOS_DM-34065_rotation_JM_test-02.ipynb (too slow due to refCat generation for each loop)
Implementation with custom-written functions - much faster b/c refCat and butler only generated once, thereupon same repo used for all data. https://github.com/suberlak/AOS/blob/main/AOS_DM-34065_rotation_JM_test-02_b.ipynb