New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Understanding meaning of duplicate Sectors but different Camera and CCD in tess_stars2px_function_entry output? #16
Comments
Maybe an additional helper function, something like the following (based on L1415-1447 in "tess_stars2px_reverse_function_entry"):
Although, I'm not sure what the optional flags for "combinedFits" and "noCollateral" mean. There doesn't seem to be documentation for these flags. I assume noCollateral refers to inclusion/exclusion of pixels in collateral data (https://heasarc.gsfc.nasa.gov/docs/tess/data-products.html#collateral-data) but not sure about "combinedFits". |
While making a target list, I noticed that some targets have duplicate sector outputs but differing Camera and CCD outputs.
For example, TIC 278779899 (TESS mag 8) has duplicate sector outputs of 7,7 with different values for Camera (3,4) and CCD (3,2). I thought maybe setting aberrate=True might change the result for improved pixel accuracy but that doesn't seem to be the case.
See example code below:
Does this simply mean the target falls in between CCDs of the adjacent cameras? This is also the result with the updated TESS Web Viewing Tool website (https://heasarc.gsfc.nasa.gov/wsgi-scripts/TESS/TESS-point_Web_Tool/TESS-point_Web_Tool/wtv_v2.0.py/)
I can see that within the "tess_stars2px_reverse_function_entry" there is a string output for edgeWarn for targets within 6 pixels of the edge of a CCD, which in this target stars' case, happens to get flagged as 1 with the use of
python -m tess_stars2px -t 278779899
Is there a way to reproduce the edge warning with the "tess_stars2px_function_entry" function?
The text was updated successfully, but these errors were encountered: