| Table of Contents | ||
|---|---|---|
|
...
- run ATpneumatics_checkout
- open dome: auxtel/atdome/open_dome.py
- open mirror covers (component: ATPneumatics, cmd: openM1Cover)
- enable corrections:
- With run command, disable dome following.
- run correct pointing (put range for target there)
- try to run latiss_wep_align to focus telescope - may not work, may have to do manual focus sweep
- NOTE: FIND CORRECT AZ POINTING FOR THE DOME
- Find targets of mag 12 +/- 1 at a large range of airmasses/elevations and take images of those without moving dome
- take_image_latiss as engtest → with g band in filter wheel, reason is on-sky, probably
- stop tracking
- point to MOSS and take a series of images there
- take_image_latiss
...
Which x and y coordinates do these source_id values correspond to?
Plotting our four groups of peaks gives me this, which does look like we are plotting the same shape as the images I have that look like the above. However, maybe it's the COM plotting that is being difficult; when I plot grouping by the positions relative to the COM in x and y (as the pairwise distances function does), I get weird chunks in my groupings that don't conform to the expected peak positions. (third image is to illustrate that we have the proper shape by making the x and y scales even, although it's upside down)
Why would the center of mass function be splitting up these groups? The code for the COM groups is:
...
It is applied to the dataframe, and then new columns are added relating to COM. I think it must be the .mean() call from the calculate_com function, because the other major operation is just subtraction and should not throw relative spacing off (should just shift it). This comes into play in our differential_motion_analysis code because the pairwise distances calculates distance using the COM values!
Writing a new function nonCOM_pairwise_distances to see if this is truly the problem
New function does not seem to have changed anything even though I wrote in that the 'centroid_x' and 'centroid_y' columns should be used as opposed to the COM columns.
Think it is swapping the peak id of two values, so I need to re-sort them in the dataframe (add a new column of source id!).