This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58
The list of candidates will appear below. Please manually reload the page every few minutes untill the 'Processing complete' message appears.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J0418017+711356,2461149.6826,11.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J0418017+711356 20260419.1826 11.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,11.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 11.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,12.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 12.24CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,12.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 12.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.17,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.17CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 491637312871393664,2461149.6826,14.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 491637312871393664 20260419.1826 14.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 488216324179547008,2461149.6826,13.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 488216324179547008 20260419.1826 13.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,13.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 13.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,13.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,12.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 12.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 488508210157299328,2461149.6826,11.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 488508210157299328 20260419.1826 11.95CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,11.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 11.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,10.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 10.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,11.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 11.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,12.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 12.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,12.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 12.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,12.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 12.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,13.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 13.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,13.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 13.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,13.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 13.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,13.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 13.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,13.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 13.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 549598343207361920,2461149.6826,13.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 549598343207361920 20260419.1826 13.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.1826* 03 25 30.04 +73 13 31.7 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,13.75,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 13.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,13.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 13.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J066.2543+74.2694,2461149.6826,14.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J066.2543+74.2694 20260419.1826 14.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.1826* 03 34 24.71 +74 24 27.5 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 544824611614302720,2461149.6826,14.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 544824611614302720 20260419.1826 14.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 498912682530433280,2461149.6826,14.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 498912682530433280 20260419.1826 14.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 491603094871342336,2461149.6826,14.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 491603094871342336 20260419.1826 14.23CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.1826* 03 26 22.96 +74 07 47.4 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 500461550816679040,2461149.6826,14.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 500461550816679040 20260419.1826 14.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.1826* 03 22 41.30 +73 23 47.0 14.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.6826,14.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.1826 14.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461049.69585608 09.01.2026 04:41:51.965 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
First image: 2461049.69585608 09.01.2026 04:41:51.965 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Last image: 2461149.68292493 19.04.2026 04:23:14.714 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 7
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.51
Magnitude-Size filter: Disabled
For each source choose aperture with the smallest scatter: YES
Photometric errors rescaling: NO
Number of identified bad images: 0
Number of SysRem iterations: 0
User-specified moving object: none
Computation time: 9 seconds
Number of parallel threads: 24
SExtractor parameter file: default.sex
Some important SExtractor parameters:
DETECT_MINAREA 10.0 # minimum number of pixels above threshold
DETECT_THRESH 10.0 # or , in mag.arcsec-2
ANALYSIS_THRESH 10.0 # or , in mag.arcsec-2
SATUR_LEVEL 55000.0 # level (in ADUs) at which arises saturation
GAIN 0.37 # detector gain in e-/ADU
Total objects detected (at least 2 times): 16808
Objects passed selection criteria: 16780
Measurements per detected object (mean, median, min, max): 3.4 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.4 4.0 2 4
Average stars detected per image: 14760.5
Average stars matched: 14351.5 (97.2291 %)
Memory usage VmPeak: 121332 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Apr 16 15:05:05 CDT 2026
VaST build number 1.0rc89-19-g55e4b97d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sun Apr 19 00:15:05 CDT 2026
Host name: tau
############################################################
## VaST run with SExtractor config file default.sex.telephoto_lens_vSTL ##
Images processed 4
Images used for photometry 4
Ref. image: 2461049.69585608 09.01.2026 04:41:51.965 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
First image: 2461049.69585608 09.01.2026 04:41:51.965 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Last image: 2461149.68292493 19.04.2026 04:23:14.714 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 151
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.20
Magnitude-Size filter: Disabled
For each source choose aperture with the smallest scatter: YES
Photometric errors rescaling: NO
Number of identified bad images: 0
Number of SysRem iterations: 0
User-specified moving object: none
Computation time: 51 seconds
Number of parallel threads: 24
SExtractor parameter file: default.sex
Some important SExtractor parameters:
DETECT_MINAREA 2.0 # minimum number of pixels above threshold
DETECT_THRESH 3.0 # or , in mag.arcsec-2
ANALYSIS_THRESH 3.0 # or , in mag.arcsec-2
SATUR_LEVEL 57000.0 # level (in ADUs) at which arises saturation
GAIN 0.83 # detector gain in e-/ADU
WEIGHT_TYPE BACKGROUND
Total objects detected (at least 2 times): 116033
Objects passed selection criteria: 115758
Measurements per detected object (mean, median, min, max): 3.5 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.5 4.0 2 4
Average stars detected per image: 105892
Average stars matched: 102054 (96.3756 %)
Memory usage VmPeak: 1942316 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Apr 16 15:05:05 CDT 2026
VaST build number 1.0rc89-19-g55e4b97d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sun Apr 19 00:28:18 CDT 2026
Host name: tau
############################################################
Updating neverexclude_list.txt
'/var/www/nmw_calibration/neverexclude_list.txt' -> './neverexclude_list.txt'
Choosing bad regions list
'/var/www/nmw_calibration/TTUQ1b1x1/TTUQ1_bad_region.lst' -> 'bad_region.lst'
wait
*------ default.sex.telephoto_lens_onlybrightstars_v1 ------*
'default.sex.telephoto_lens_onlybrightstars_v1' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_onlybrightstars_v1
./vast --norotation --noflagimage --starmatchraius 3.5 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
SExtractor catalog cache: saved Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat to cache
SExtractor catalog cache: saved Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_onlybrightstars_v1
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
Checking WCS cache directory local_wcs_cache
Checking WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Found WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Checking WCS cache directory /home/NMW_web_upload/solved_reference_images
Checking WCS cache directory /dataX/kirx/NMW_NG_rt3_autumn2019/solved_reference_images
The reference JD(UT) for computing planet and comet positions: 2461149.68219115
Re-using ../asassn_transients_list.txt
'../asassn_transients_list.txt' -> 'asassn_transients_list.txt'
Re-using ../tocp_transients_list.txt
'../tocp_transients_list.txt' -> 'tocp_transients_list.txt'
Re-using ../tns_transients_list.txt
'../tns_transients_list.txt' -> 'tns_transients_list.txt'
Plate-solving the images
wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits exists and is non-empty
Saving wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits to local_wcs_cache/
'wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits' -> 'local_wcs_cache/wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits'
wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits exists and is non-empty
Saving wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits to local_wcs_cache/
'wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits' -> 'local_wcs_cache/wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits'
wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits exists and is non-empty
Saving wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits to local_wcs_cache/
'wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits' -> 'local_wcs_cache/wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits'
wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits exists and is non-empty
Saving wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits to local_wcs_cache/
'wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits' -> 'local_wcs_cache/wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits (1st reference image)
verification OK: wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Image size: 941.4'x627.0' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 04:47:16.792 +69:58:46.61 J2000 4789.000 3195.000
###################################
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits (1st new image)
verification OK: wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
Image size: 932.0'x615.6' 15.5(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.84"/pix along the X axis and 5.78"/pix along the Y axis
Image center: 04:48:42.697 +70:00:19.09 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 04:47:16.792 +69:58:46.61
Second-epoch image center 04:48:42.697 +70:00:19.09
Angular distance between the image centers 0.1251 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits (2nd new image)
verification OK: wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
Image size: 932.0'x615.5' 15.5(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.84"/pix along the X axis and 5.78"/pix along the Y axis
Image center: 04:48:45.557 +70:00:45.19 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 04:47:16.792 +69:58:46.61
Second-epoch image center 04:48:45.557 +70:00:45.19
Angular distance between the image centers 0.1307 deg.
###################################
###################################
# Check the image center offset between the first and the second second-epoch image (shift should be applied between the second-epoch images)
Second-epoch first image center 04:48:42.697 +70:00:19.09
Second-epoch second image center 04:48:45.557 +70:00:45.19
Angular distance between the image centers 0.00832 deg.
###################################
Running solve_plate_with_UCAC5...
Preparing for ar aprallel run
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits &> /tmp/tmp.52liOIdzWp
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits &> /tmp/tmp.cIgirQzZG0
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits &> /tmp/tmp.rMdRtDreRB
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits &> /tmp/tmp.XxPmNsaga6
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
Calibrating the magnitude scale
Found non-empty wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
____ Start of magnitude calibration ____
PHOTOMETRIC_CALIBRATION=TYCHO2_V
Calibrating the magnitude scale with Tycho-2 stars
util/transients/transient_factory_test31.sh is checking for the presence of non-empty wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits and wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
Tycho-2 catalog is found at lib/catalogs/tycho2
Tycho-2 catalog and the derived bright star exclusion list are ready
Checking for the presence of non-empty wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits and wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
Found non-empty wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits and wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
The reference image (wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits) and catalog (wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat) found
'wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat' -> 'wcsmag.cat'
Read 17535 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 44.4953 to 100.0749 deg, Dec +62.8164 to +75.4615 deg
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.00
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.01
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.02
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.03
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.04
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.05
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.06
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.07
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.08
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.09
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.10
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.11
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.12
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.13
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.14
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.15
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.16
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.17
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.18
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.19
Tycho-2 catalog search boundaries: RA 44.4953 to 100.0749 deg, Dec 62.8164 to 75.4615 deg
Loaded 14408 Tycho-2 stars within the image boundaries (VT and BT non-zero).
Relation between the catalog and instrumental magnitudes is written to calib.txt
Stars used for magnitude calibration (good matches): 7701 out of 8346 total matches.
Matched with Tycho-2 8346 out of 17535 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.930229
a=0.000000 b=1.000000 c=22.930229
From vast_summary.log: estimated ref. image limiting mag.: -7.51
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.42
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.42
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 5 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.0 pix Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
2.0 pix Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
2.1 pix fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
2.1 pix fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
Limiting magnitude estimates:
15.4 mag. Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
15.4 mag. Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
15.0 mag. fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
14.9 mag. fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
All-image limiting magnitude estimate: 14.9 (SNR ) 12.0 (80% of stars) with default.sex.telephoto_lens_onlybrightstars_v1
The first estimate is the magnitude of a star detected with a signal-to-noise ratio of following Karpov (2025, Acta Polytechnica, 65, 50).
This value should be representative of the faintest stars clearly visible in the image.
The brighter of the limiting magnitude estimates for the two second-epoch images is reported here.
The second estimate is the 80th percentile of the magnitude distribution of stars detected on all four images.
This value is representative of the faintest object that may enter the candidate transients list.
The hard cut-off for the candidate transients is 15.0 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.52liOIdzWp (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits' -> 'wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
WCS_IMAGE_NAME=wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
WCS-calibrated image found: wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Checking if the catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits alredy exist and is non-empty...
Catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
WCS catalog name: wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1440, passed=17535
Got 17535 stars (including 16074 good ones) from the SExtractor catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
util/solve_plate_with_UCAC5 got 17535 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.4'
Seting catalog search parameters based on the expected field of view 941.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013075 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010460 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 970 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 969 matched stars entering correct_measured_positions(), 950 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.37"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 969 matched stars entering correct_measured_positions(), 17045 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.32"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 970 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 969 matched stars entering correct_measured_positions(), 17045 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.32"
Accuracy estimation diagnostic: 969 matched stars entering correct_measured_positions(), 17045 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.32"
Excluding outliers - 969 stars left (next iteration limit 1065)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits -region wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.cIgirQzZG0 (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits' -> 'wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
WCS_IMAGE_NAME=wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
WCS-calibrated image found: wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
Checking if the catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits alredy exist and is non-empty...
Catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
WCS catalog name: wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1424, passed=17523
Got 17523 stars (including 16079 good ones) from the SExtractor catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat
util/solve_plate_with_UCAC5 got 17523 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.4'
Seting catalog search parameters based on the expected field of view 941.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013075 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010460 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 949 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.36"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 17070 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.32"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 17071 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.32"
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 17071 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.32"
Excluding outliers - 970 stars left (next iteration limit 1067)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits -region wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.rMdRtDreRB (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
WCS_IMAGE_NAME=wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
WCS-calibrated image found: wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
Checking if the catalog wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits alredy exist and is non-empty...
Catalog wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
WCS catalog name: wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=884, passed=12199
Got 12199 stars (including 11304 good ones) from the SExtractor catalog wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat
util/solve_plate_with_UCAC5 got 12199 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.0'
Seting catalog search parameters based on the expected field of view 932.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012944 (46.6 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010356 (37.3 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 268 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 220 matched stars entering correct_measured_positions(), 168 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.48"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 214 matched stars entering correct_measured_positions(), 2546 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.29"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 317 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 287 matched stars entering correct_measured_positions(), 2573 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.03"
Accuracy estimation diagnostic: 285 matched stars entering correct_measured_positions(), 3341 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.42"
Excluding outliers - 285 stars left (next iteration limit 235)
The image catalog is written to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits -region wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.XxPmNsaga6 (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
WCS_IMAGE_NAME=wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
WCS-calibrated image found: wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
Checking if the catalog wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits alredy exist and is non-empty...
Catalog wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
WCS catalog name: wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=876, passed=12154
Got 12154 stars (including 11265 good ones) from the SExtractor catalog wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat
util/solve_plate_with_UCAC5 got 12154 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.0'
Seting catalog search parameters based on the expected field of view 932.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012944 (46.6 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010356 (37.3 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 262 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 216 matched stars entering correct_measured_positions(), 161 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.03"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 211 matched stars entering correct_measured_positions(), 2534 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.36"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 314 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 280 matched stars entering correct_measured_positions(), 2564 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.13"
Accuracy estimation diagnostic: 280 matched stars entering correct_measured_positions(), 3329 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.40"
Excluding outliers - 280 stars left (next iteration limit 232)
The image catalog is written to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits -region wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits'
Saving fully-calibrated image wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits'
Saving fully-calibrated image wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits'
Saving fully-calibrated image wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits'
Preparing the HTML report for the field Cam-06-Q1b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Adding exclusion_list_gaiadr2.txt__out21126.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out21365.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out21465.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out21548.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out21549.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 16s
Pre-generating preview images in parallel...
Done pre-generating preview images.
Pre-generating finding charts in parallel...
Done pre-generating finding charts.
make_report_in_HTML.sh Pre-generation: 3s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21126_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 21126_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:16:34.02 +70:30:52.0 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=11.78, MAG_FAINT_SEARCH_LIMIT=12.76)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21365_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 21365_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21465_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 21465_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21548_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 21548_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21549_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 21549_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
make_report_in_HTML.sh Phase 2 (HTML assembly): 0s
make_report_in_HTML.sh TOTAL: 19s
Prepared the HTML report for the field Cam-06-Q1b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
*------ done with default.sex.telephoto_lens_onlybrightstars_v1 ------*
#### The local exclusion list is exclusion_list_local.txt ####
04:18:01.17 +71:13:43.0
05:10:53.29 +74:08:56.7
05:13:17.89 +69:36:37.3
05:38:42.61 +70:52:04.4
wait
*------ default.sex.telephoto_lens_vSTL ------*
'default.sex.telephoto_lens_vSTL' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_vSTL
./vast --norotation --noflagimage --starmatchraius 3.5 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
SExtractor catalog cache: saved Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat to cache
SExtractor catalog cache: saved Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Creating symlink local_wcs_cache/wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
Creating symlink local_wcs_cache/wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
Creating symlink local_wcs_cache/wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
Creating symlink local_wcs_cache/exclusion_list.txt
Checking WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Found WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Checking WCS cache directory /home/NMW_web_upload/solved_reference_images
Checking WCS cache directory /dataX/kirx/NMW_NG_rt3_autumn2019/solved_reference_images
Plate-solving the images
wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits exists and is non-empty
wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits exists and is non-empty
wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits exists and is non-empty
wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits exists and is non-empty
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits (1st reference image)
verification OK: wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Image size: 941.4'x627.0' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 04:47:16.792 +69:58:46.61 J2000 4789.000 3195.000
###################################
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits (1st new image)
verification OK: wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
Image size: 932.0'x615.6' 15.5(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.84"/pix along the X axis and 5.78"/pix along the Y axis
Image center: 04:48:42.697 +70:00:19.09 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 04:47:16.792 +69:58:46.61
Second-epoch image center 04:48:42.697 +70:00:19.09
Angular distance between the image centers 0.1251 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits (2nd new image)
verification OK: wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
Image size: 932.0'x615.5' 15.5(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.84"/pix along the X axis and 5.78"/pix along the Y axis
Image center: 04:48:45.557 +70:00:45.19 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 04:47:16.792 +69:58:46.61
Second-epoch image center 04:48:45.557 +70:00:45.19
Angular distance between the image centers 0.1307 deg.
###################################
###################################
# Check the image center offset between the first and the second second-epoch image (shift should be applied between the second-epoch images)
Second-epoch first image center 04:48:42.697 +70:00:19.09
Second-epoch second image center 04:48:45.557 +70:00:45.19
Angular distance between the image centers 0.00832 deg.
###################################
Running solve_plate_with_UCAC5...
Preparing for ar aprallel run
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits &> /tmp/tmp.YFrNg1NSKw
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits &> /tmp/tmp.B3LyunVEJv
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits &> /tmp/tmp.KjazR2R0TM
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits &> /tmp/tmp.Rt282ZRaVS
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
Calibrating the magnitude scale
Found non-empty wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
____ Start of magnitude calibration ____
PHOTOMETRIC_CALIBRATION=TYCHO2_V
Calibrating the magnitude scale with Tycho-2 stars
util/transients/transient_factory_test31.sh is checking for the presence of non-empty wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits and wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
Tycho-2 catalog is found at lib/catalogs/tycho2
Tycho-2 catalog and the derived bright star exclusion list are ready
Checking for the presence of non-empty wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits and wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
Found non-empty wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits and wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
The reference image (wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits) and catalog (wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat) found
'wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat' -> 'wcsmag.cat'
Read 121322 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 44.3972 to 100.3253 deg, Dec +62.8165 to +75.4640 deg
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.00
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.01
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.02
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.03
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.04
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.05
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.06
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.07
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.08
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.09
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.10
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.11
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.12
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.13
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.14
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.15
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.16
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.17
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.18
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.19
Tycho-2 catalog search boundaries: RA 44.3972 to 100.3253 deg, Dec 62.8165 to 75.4640 deg
Loaded 14499 Tycho-2 stars within the image boundaries (VT and BT non-zero).
Relation between the catalog and instrumental magnitudes is written to calib.txt
Stars used for magnitude calibration (good matches): 6542 out of 8413 total matches.
Matched with Tycho-2 8413 out of 121322 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.798908
a=0.000000 b=1.000000 c=22.798908
From vast_summary.log: estimated ref. image limiting mag.: -7.20
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.60
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.60
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 132 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
1.9 pix Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
1.9 pix Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
1.9 pix fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
1.9 pix fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
Limiting magnitude estimates:
15.6 mag. Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
15.6 mag. Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
15.2 mag. fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
15.2 mag. fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
All-image limiting magnitude estimate: 15.2 (SNR ) 14.6 (80% of stars) with default.sex.telephoto_lens_vSTL
The first estimate is the magnitude of a star detected with a signal-to-noise ratio of following Karpov (2025, Acta Polytechnica, 65, 50).
This value should be representative of the faintest stars clearly visible in the image.
The brighter of the limiting magnitude estimates for the two second-epoch images is reported here.
The second estimate is the 80th percentile of the magnitude distribution of stars detected on all four images.
This value is representative of the faintest object that may enter the candidate transients list.
The hard cut-off for the candidate transients is 15.0 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.YFrNg1NSKw (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits' -> 'wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
WCS_IMAGE_NAME=wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
WCS-calibrated image found: wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Checking if the catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits alredy exist and is non-empty...
Catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
WCS catalog name: wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=20, blended=10875, passed=121302
Got 121302 stars (including 110227 good ones) from the SExtractor catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
util/solve_plate_with_UCAC5 got 121302 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.4'
Seting catalog search parameters based on the expected field of view 941.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013075 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010460 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 956 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.35"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 118877 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.35"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 118876 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.35"
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 118876 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.34"
Excluding outliers - 970 stars left (next iteration limit 1067)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits -region wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.B3LyunVEJv (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits' -> 'wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
WCS_IMAGE_NAME=wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
WCS-calibrated image found: wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
Checking if the catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits alredy exist and is non-empty...
Catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
WCS catalog name: wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=28, blended=10830, passed=121526
Got 121526 stars (including 110505 good ones) from the SExtractor catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat
util/solve_plate_with_UCAC5 got 121526 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.4'
Seting catalog search parameters based on the expected field of view 941.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013075 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010460 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 946 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.36"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 119031 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.35"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 119030 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.35"
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 119030 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.34"
Excluding outliers - 970 stars left (next iteration limit 1067)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits -region wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.KjazR2R0TM (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
WCS_IMAGE_NAME=wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
WCS-calibrated image found: wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
Checking if the catalog wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits alredy exist and is non-empty...
Catalog wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
WCS catalog name: wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=36, blended=6549, passed=91783
Got 91783 stars (including 85079 good ones) from the SExtractor catalog wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat
util/solve_plate_with_UCAC5 got 91783 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.0'
Seting catalog search parameters based on the expected field of view 932.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012944 (46.6 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010356 (37.3 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 766 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 278 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 230 matched stars entering correct_measured_positions(), 182 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.35"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 221 matched stars entering correct_measured_positions(), 20532 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.23"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 766 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 327 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 291 matched stars entering correct_measured_positions(), 20552 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.20"
Accuracy estimation diagnostic: 291 matched stars entering correct_measured_positions(), 27028 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.56"
Excluding outliers - 291 stars left (next iteration limit 243)
The image catalog is written to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits -region wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.Rt282ZRaVS (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
WCS_IMAGE_NAME=wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
WCS-calibrated image found: wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
Checking if the catalog wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits alredy exist and is non-empty...
Catalog wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
WCS catalog name: wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=27, blended=6452, passed=91681
Got 91681 stars (including 85081 good ones) from the SExtractor catalog wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat
util/solve_plate_with_UCAC5 got 91681 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.0'
Seting catalog search parameters based on the expected field of view 932.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012944 (46.6 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010356 (37.3 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 275 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 226 matched stars entering correct_measured_positions(), 176 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.88"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 217 matched stars entering correct_measured_positions(), 20073 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.13"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 766 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 320 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 285 matched stars entering correct_measured_positions(), 20093 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.11"
Accuracy estimation diagnostic: 285 matched stars entering correct_measured_positions(), 26452 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.86"
Excluding outliers - 285 stars left (next iteration limit 238)
The image catalog is written to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits -region wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Saving fully-calibrated image wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
Saving fully-calibrated image wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-22-11_20.00sec_-4.90C_LIGHTs_0333.fits
Saving fully-calibrated image wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_Cam-06-Q1b1x1_232406_TTUQ1b1x1_1194696_uIH4jT58/wcs_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334.fits
Preparing the HTML report for the field Cam-06-Q1b1x1 with default.sex.telephoto_lens_vSTL
Adding exclusion_list_gaiadr2.txt__out142002.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out142003.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out142004.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out142022.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out142036.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out142037.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out142044.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out142049.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out143030.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out143367.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out144204.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out144412.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out144469.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out144620.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out144655.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out144680.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out144835.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out145170.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out141964.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141993.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141994.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142012.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142026.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142031.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142041.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142046.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142051.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142058.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142060.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142062.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142195.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142310.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142590.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142767.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142826.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142947.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143376.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143383.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143409.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143443.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143447.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143463.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143646.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143861.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143901.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143917.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144062.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144069.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144418.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144572.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144631.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144672.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144716.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144884.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144987.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145007.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145102.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145103.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145266.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 79s
Pre-generating preview images in parallel...
Done pre-generating preview images.
Pre-generating finding charts in parallel...
Done pre-generating finding charts.
make_report_in_HTML.sh Pre-generation: 28s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141956_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 141956_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141960_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 141960_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:14:53.79 +73:52:22.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141962_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 141962_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (34.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141964_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 141964_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141972_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 141972_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141974_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 141974_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141990_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 141990_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141993_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 141993_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141994_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 141994_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141995_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 141995_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142002_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142002_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:10:20.75 +68:27:14.9 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.53, MAG_FAINT_SEARCH_LIMIT=15.51)GAIADR2_OUTPUT=# 4.162 490823987802450304 062.58643385899 +68.45298278478 14.5019 13.8006 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.162#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142003_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142003_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:19:32.69 +73:04:42.8 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.61, MAG_FAINT_SEARCH_LIMIT=15.59)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142004_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142004_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:20:22.71 +70:53:06.1 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.50, MAG_FAINT_SEARCH_LIMIT=15.48)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142009_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142009_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142010_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142010_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142012_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142012_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142021_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142021_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (18.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142022_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142022_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:41:26.11 +73:57:15.1 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.12, MAG_FAINT_SEARCH_LIMIT=15.10)GAIADR2_OUTPUT=# 1.478 544619758854261376 055.35783716600 +73.95450894550 14.1317 13.5446 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#1.478#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142026_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142026_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142031_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142031_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142032_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142032_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:55:18.41 +68:37:29.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142035_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142035_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (18.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142036_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142036_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:44:10.35 +66:08:12.8 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.71, MAG_FAINT_SEARCH_LIMIT=14.69)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142037_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142037_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:08:39.82 +71:27:17.1 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.80, MAG_FAINT_SEARCH_LIMIT=14.78)GAIADR2_OUTPUT=# 0.843 501098923964224768 062.16659691307 +71.45466036470 13.8017 13.2074 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#0.843#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142041_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142041_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142044_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142044_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:26:00.09 +70:23:10.9 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.54, MAG_FAINT_SEARCH_LIMIT=14.52)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142045_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142045_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:58:02.68 +65:53:38.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142046_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142046_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142047_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142047_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (36.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142049_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142049_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:23:03.46 +72:39:34.3 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.16, MAG_FAINT_SEARCH_LIMIT=14.14)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142051_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142051_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142052_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142052_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:50:36.77 +72:48:41.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142054_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142054_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142056_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142056_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142058_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142058_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142060_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142060_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142062_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142062_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142195_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142195_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142263_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142263_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:31:11.48 +71:05:31.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142310_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142310_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142546_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142546_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:13:20.16 +72:06:35.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142552_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142552_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142590_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142590_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142767_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142767_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142788_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142788_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:13:40.74 +72:09:24.6 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142795_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142795_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:48:59.15 +72:12:09.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142818_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 142818_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142826_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142826_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142947_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 142947_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143030_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143030_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:13:01.22 +68:33:56.7 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.16, MAG_FAINT_SEARCH_LIMIT=14.14)GAIADR2_OUTPUT=# 4.716 490831375146520192 063.25470684757 +68.56444728982 13.2105 12.6478 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.716#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143080_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143080_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:55:26.88 +74:20:30.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143193_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143193_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:55:21.61 +67:27:31.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143267_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143267_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (26.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143281_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143281_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:55:37.13 +66:02:14.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143367_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143367_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:11:53.32 +71:17:59.3 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.55, MAG_FAINT_SEARCH_LIMIT=14.53)GAIADR2_OUTPUT=# 2.494 501039687775270144 062.97415330040 +71.29953309549 14.0177 13.3055 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#2.494#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143376_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 143376_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143383_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 143383_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143407_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143407_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:45:47.59 +72:07:41.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143409_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 143409_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143426_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143426_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:02:17.62 +70:20:18.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143443_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 143443_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143447_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 143447_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143463_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 143463_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143510_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143510_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:05:43.34 +68:39:44.1 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143557_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143557_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:36:21.61 +73:19:27.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143618_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143618_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:56:13.38 +71:48:17.1 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143627_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143627_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143646_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 143646_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143666_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143666_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:57:23.84 +71:25:02.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143752_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143752_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:23:00.73 +72:23:27.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143797_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143797_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:20:26.56 +65:08:33.2 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143824_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143824_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143861_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 143861_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143875_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 143875_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143901_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 143901_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143917_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 143917_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144012_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144012_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144025_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144025_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144034_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144034_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (18.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144053_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144053_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144062_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 144062_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144069_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 144069_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144093_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144093_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144124_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144124_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144204_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144204_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:29:14.61 +70:32:28.9 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.19, MAG_FAINT_SEARCH_LIMIT=15.17)GAIADR2_OUTPUT=# 5.687 500055143832034944 067.30903025158 +70.54281652335 14.0722 13.2992 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.687#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144234_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144234_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144275_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144275_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144283_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144283_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:56:06.87 +69:11:09.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144306_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144306_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144340_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144340_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (18.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144347_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144347_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144363_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144363_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:50:51.69 +73:54:43.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144412_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144412_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:50:01.94 +71:09:28.7 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.26, MAG_FAINT_SEARCH_LIMIT=15.24)GAIADR2_OUTPUT=# 4.177 495224336415689728 057.50941408576 +71.15689450452 14.1154 13.1984 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.177#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144416_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144416_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:01:44.47 +71:10:26.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144418_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 144418_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144453_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144453_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144469_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144469_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:04:51.38 +71:07:26.8 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.39, MAG_FAINT_SEARCH_LIMIT=15.37)GAIADR2_OUTPUT=# 0.971 495088134413785216 061.21491345771 +71.12413540209 14.2967 13.8357 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#0.971#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144556_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144556_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:55:51.25 +73:31:47.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144572_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 144572_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144620_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144620_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:53:23.10 +70:15:22.3 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.59, MAG_FAINT_SEARCH_LIMIT=15.57)GAIADR2_OUTPUT=# 2.712 494939837783101568 058.34746304792 +70.25556221843 14.5129 13.7876 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#2.712#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144631_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 144631_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144655_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144655_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:51:01.98 +73:06:46.8 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.49, MAG_FAINT_SEARCH_LIMIT=15.47)GAIADR2_OUTPUT=# 5.243 543718674716151424 057.75705350849 +73.11158576503 14.2810 13.4098 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.243#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144665_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144665_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144672_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 144672_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144680_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144680_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:43:00.29 +73:41:43.9 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.46, MAG_FAINT_SEARCH_LIMIT=15.44)GAIADR2_OUTPUT=# 3.612 544554440991671936 055.75179231623 +73.69453793760 14.3590 13.7856 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.612#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144716_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 144716_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144772_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144772_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:13:47.63 +71:34:09.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144826_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144826_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144835_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144835_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:12:52.17 +72:36:19.7 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.52, MAG_FAINT_SEARCH_LIMIT=15.50)GAIADR2_OUTPUT=# 5.626 501372633639848448 063.21542497128 +72.60402221917 14.3828 13.6321 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.626#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144882_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144882_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144884_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 144884_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144894_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144894_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:04:40.24 +71:07:02.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144913_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144913_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:23:14.81 +71:32:58.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144916_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 144916_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144987_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 144987_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145007_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 145007_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145042_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 145042_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (29.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145075_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 145075_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145087_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 145087_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (21.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145102_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 145102_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145103_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 145103_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145138_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 145138_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145146_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 145146_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145148_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 145148_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145170_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 145170_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:20:06.20 +69:30:16.1 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.82, MAG_FAINT_SEARCH_LIMIT=15.80)GAIADR2_OUTPUT=# 3.358 496901469605680256 065.02659409815 +69.50536608034 14.8356 14.1407 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.358#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145194_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 145194_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145266_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
Preparing report for the candidate 145266_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145330_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 145330_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34249_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 34249_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (23.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 89441_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 89441_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 03:30:08.33 +68:45:53.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 46725_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 46725_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
**** FOUND 04:18:01.48 +71:13:56.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 12441_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334
The candidate 12441_fd_Cam-06-Q1b1x1_2026-04-18_23-23-14_20.00sec_-4.90C_LIGHTs_0334 did not pass the final checks
Rejecting candidate due to large distance (24.4") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 2s
make_report_in_HTML.sh TOTAL: 109s
Prepared the HTML report for the field Cam-06-Q1b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
04:18:01.17 +71:13:43.0
05:10:53.29 +74:08:56.7
05:13:17.89 +69:36:37.3
05:38:42.61 +70:52:04.4
03:53:07.46 +74:41:40.2
05:00:45.91 +69:22:17.9
04:11:55.93 +73:29:46.5
04:02:26.23 +73:49:28.5
05:47:47.03 +71:31:12.0
03:41:16.23 +66:17:02.2
03:42:21.92 +64:48:31.7
04:23:06.71 +73:36:31.2
04:50:07.56 +67:38:40.2
04:20:20.60 +74:28:33.7
03:42:59.48 +65:15:18.8
05:21:42.89 +73:12:29.4
06:03:24.68 +66:39:45.3
04:26:15.89 +74:20:46.5
04:59:22.76 +70:27:55.9
05:30:41.31 +64:21:08.9
04:17:16.03 +66:58:59.7
04:09:45.80 +68:22:53.0
04:19:10.07 +74:36:17.9
03:49:47.33 +66:14:53.1
04:48:25.47 +74:26:29.4
04:17:40.18 +67:04:02.3
04:10:05.72 +73:24:14.0
03:25:30.04 +73:13:31.7
04:36:42.90 +67:22:50.0
04:49:51.39 +72:55:24.4
04:54:54.07 +71:07:54.2
04:49:57.27 +72:52:56.1
04:25:06.50 +74:16:43.6
03:34:24.71 +74:24:27.5
05:14:12.00 +72:16:54.9
04:37:22.95 +66:31:20.4
03:38:40.53 +65:56:52.1
04:24:04.59 +68:14:40.1
04:49:43.06 +69:03:30.4
05:05:25.67 +74:23:23.4
03:26:22.96 +74:07:47.4
04:03:33.02 +73:49:51.9
04:29:24.48 +72:16:49.5
03:22:41.30 +73:23:47.0
05:06:26.53 +69:38:25.5
########### Completed Cam-06-Q1b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ1.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
04:18:01.17 +71:13:43.0
05:10:53.29 +74:08:56.7
05:13:17.89 +69:36:37.3
05:38:42.61 +70:52:04.4
03:53:07.46 +74:41:40.2
05:00:45.91 +69:22:17.9
04:11:55.93 +73:29:46.5
04:02:26.23 +73:49:28.5
05:47:47.03 +71:31:12.0
03:41:16.23 +66:17:02.2
03:42:21.92 +64:48:31.7
04:23:06.71 +73:36:31.2
04:50:07.56 +67:38:40.2
04:20:20.60 +74:28:33.7
03:42:59.48 +65:15:18.8
05:21:42.89 +73:12:29.4
06:03:24.68 +66:39:45.3
04:26:15.89 +74:20:46.5
04:59:22.76 +70:27:55.9
05:30:41.31 +64:21:08.9
04:17:16.03 +66:58:59.7
04:09:45.80 +68:22:53.0
04:19:10.07 +74:36:17.9
03:49:47.33 +66:14:53.1
04:48:25.47 +74:26:29.4
04:17:40.18 +67:04:02.3
04:10:05.72 +73:24:14.0
03:25:30.04 +73:13:31.7
04:36:42.90 +67:22:50.0
04:49:51.39 +72:55:24.4
04:54:54.07 +71:07:54.2
04:49:57.27 +72:52:56.1
04:25:06.50 +74:16:43.6
03:34:24.71 +74:24:27.5
05:14:12.00 +72:16:54.9
04:37:22.95 +66:31:20.4
03:38:40.53 +65:56:52.1
04:24:04.59 +68:14:40.1
04:49:43.06 +69:03:30.4
05:05:25.67 +74:23:23.4
03:26:22.96 +74:07:47.4
04:03:33.02 +73:49:51.9
04:29:24.48 +72:16:49.5
03:22:41.30 +73:23:47.0
05:06:26.53 +69:38:25.5
###################################################################################
04:18:01.17 +71:13:43.0 -- not an asteroid (will add it to exclusion list)
05:10:53.29 +74:08:56.7 -- not an asteroid (will add it to exclusion list)
05:13:17.89 +69:36:37.3 -- not an asteroid (will add it to exclusion list)
05:38:42.61 +70:52:04.4 -- not an asteroid (will add it to exclusion list)
03:53:07.46 +74:41:40.2 -- not an asteroid (will add it to exclusion list)
05:00:45.91 +69:22:17.9 -- not an asteroid (will add it to exclusion list)
04:11:55.93 +73:29:46.5 -- not an asteroid (will add it to exclusion list)
04:02:26.23 +73:49:28.5 -- not an asteroid (will add it to exclusion list)
05:47:47.03 +71:31:12.0 -- not an asteroid (will add it to exclusion list)
03:41:16.23 +66:17:02.2 -- not an asteroid (will add it to exclusion list)
03:42:21.92 +64:48:31.7 -- not an asteroid (will add it to exclusion list)
04:23:06.71 +73:36:31.2 -- not an asteroid (will add it to exclusion list)
04:50:07.56 +67:38:40.2 -- not an asteroid (will add it to exclusion list)
04:20:20.60 +74:28:33.7 -- not an asteroid (will add it to exclusion list)
03:42:59.48 +65:15:18.8 -- not an asteroid (will add it to exclusion list)
05:21:42.89 +73:12:29.4 -- not an asteroid (will add it to exclusion list)
06:03:24.68 +66:39:45.3 -- not an asteroid (will add it to exclusion list)
04:26:15.89 +74:20:46.5 -- not an asteroid (will add it to exclusion list)
04:59:22.76 +70:27:55.9 -- not an asteroid (will add it to exclusion list)
05:30:41.31 +64:21:08.9 -- not an asteroid (will add it to exclusion list)
04:17:16.03 +66:58:59.7 -- not an asteroid (will add it to exclusion list)
04:09:45.80 +68:22:53.0 -- not an asteroid (will add it to exclusion list)
04:19:10.07 +74:36:17.9 -- not an asteroid (will add it to exclusion list)
03:49:47.33 +66:14:53.1 -- not an asteroid (will add it to exclusion list)
04:48:25.47 +74:26:29.4 -- not an asteroid (will add it to exclusion list)
04:17:40.18 +67:04:02.3 -- not an asteroid (will add it to exclusion list)
04:10:05.72 +73:24:14.0 -- not an asteroid (will add it to exclusion list)
03:25:30.04 +73:13:31.7 -- not an asteroid (will add it to exclusion list)
04:36:42.90 +67:22:50.0 -- not an asteroid (will add it to exclusion list)
04:49:51.39 +72:55:24.4 -- not an asteroid (will add it to exclusion list)
04:54:54.07 +71:07:54.2 -- not an asteroid (will add it to exclusion list)
04:49:57.27 +72:52:56.1 -- not an asteroid (will add it to exclusion list)
04:25:06.50 +74:16:43.6 -- not an asteroid (will add it to exclusion list)
03:34:24.71 +74:24:27.5 -- not an asteroid (will add it to exclusion list)
05:14:12.00 +72:16:54.9 -- not an asteroid (will add it to exclusion list)
04:37:22.95 +66:31:20.4 -- not an asteroid (will add it to exclusion list)
03:38:40.53 +65:56:52.1 -- not an asteroid (will add it to exclusion list)
04:24:04.59 +68:14:40.1 -- not an asteroid (will add it to exclusion list)
04:49:43.06 +69:03:30.4 -- not an asteroid (will add it to exclusion list)
05:05:25.67 +74:23:23.4 -- not an asteroid (will add it to exclusion list)
03:26:22.96 +74:07:47.4 -- not an asteroid (will add it to exclusion list)
04:03:33.02 +73:49:51.9 -- not an asteroid (will add it to exclusion list)
04:29:24.48 +72:16:49.5 -- not an asteroid (will add it to exclusion list)
03:22:41.30 +73:23:47.0 -- not an asteroid (will add it to exclusion list)
05:06:26.53 +69:38:25.5 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
03:22:41.30 +73:23:47.0 -- does not seem to be a hot pixel (will add it to exclusion list)
03:25:30.04 +73:13:31.7 -- does not seem to be a hot pixel (will add it to exclusion list)
03:26:22.96 +74:07:47.4 -- does not seem to be a hot pixel (will add it to exclusion list)
03:34:24.71 +74:24:27.5 -- does not seem to be a hot pixel (will add it to exclusion list)
03:38:40.53 +65:56:52.1 -- does not seem to be a hot pixel (will add it to exclusion list)
03:41:16.23 +66:17:02.2 -- does not seem to be a hot pixel (will add it to exclusion list)
03:42:21.92 +64:48:31.7 -- does not seem to be a hot pixel (will add it to exclusion list)
03:42:59.48 +65:15:18.8 -- does not seem to be a hot pixel (will add it to exclusion list)
03:49:47.33 +66:14:53.1 -- does not seem to be a hot pixel (will add it to exclusion list)
03:53:07.46 +74:41:40.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:02:26.23 +73:49:28.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:03:33.02 +73:49:51.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:09:45.80 +68:22:53.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:10:05.72 +73:24:14.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:11:55.93 +73:29:46.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:17:16.03 +66:58:59.7 -- does not seem to be a hot pixel (will add it to exclusion list)
04:17:40.18 +67:04:02.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:18:01.17 +71:13:43.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:19:10.07 +74:36:17.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:20:20.60 +74:28:33.7 -- does not seem to be a hot pixel (will add it to exclusion list)
04:23:06.71 +73:36:31.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:24:04.59 +68:14:40.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:25:06.50 +74:16:43.6 -- does not seem to be a hot pixel (will add it to exclusion list)
04:26:15.89 +74:20:46.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:29:24.48 +72:16:49.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:36:42.90 +67:22:50.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:37:22.95 +66:31:20.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:48:25.47 +74:26:29.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:49:43.06 +69:03:30.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:49:51.39 +72:55:24.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:49:57.27 +72:52:56.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:50:07.56 +67:38:40.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:54:54.07 +71:07:54.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:59:22.76 +70:27:55.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:00:45.91 +69:22:17.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:05:25.67 +74:23:23.4 -- does not seem to be a hot pixel (will add it to exclusion list)
05:06:26.53 +69:38:25.5 -- does not seem to be a hot pixel (will add it to exclusion list)
05:10:53.29 +74:08:56.7 -- does not seem to be a hot pixel (will add it to exclusion list)
05:13:17.89 +69:36:37.3 -- does not seem to be a hot pixel (will add it to exclusion list)
05:14:12.00 +72:16:54.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:21:42.89 +73:12:29.4 -- does not seem to be a hot pixel (will add it to exclusion list)
05:30:41.31 +64:21:08.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:38:42.61 +70:52:04.4 -- does not seem to be a hot pixel (will add it to exclusion list)
05:47:47.03 +71:31:12.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:03:24.68 +66:39:45.3 -- does not seem to be a hot pixel (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_nohotpixels' -> 'exclusion_list_index_html.txt'
# Count candidates with no identification (that also don't look like hot pix)
03:22:41.30 +73:23:47.0 -- not a known variable star
03:25:30.04 +73:13:31.7 -- not a known variable star
03:26:22.96 +74:07:47.4 -- not a known variable star
03:34:24.71 +74:24:27.5 -- not a known variable star
03:38:40.53 +65:56:52.1 -- not a known variable star
03:41:16.23 +66:17:02.2 -- not a known variable star
03:42:21.92 +64:48:31.7 -- not a known variable star
03:42:59.48 +65:15:18.8 -- not a known variable star
03:49:47.33 +66:14:53.1 -- not a known variable star
03:53:07.46 +74:41:40.2 -- not a known variable star
04:02:26.23 +73:49:28.5 -- not a known variable star
04:03:33.02 +73:49:51.9 -- not a known variable star
04:09:45.80 +68:22:53.0 -- not a known variable star
04:10:05.72 +73:24:14.0 -- not a known variable star
04:11:55.93 +73:29:46.5 -- not a known variable star
04:17:16.03 +66:58:59.7 -- not a known variable star
04:17:40.18 +67:04:02.3 -- not a known variable star
04:18:01.17 +71:13:43.0 -- a known variable star
04:19:10.07 +74:36:17.9 -- not a known variable star
04:20:20.60 +74:28:33.7 -- not a known variable star
04:23:06.71 +73:36:31.2 -- not a known variable star
04:24:04.59 +68:14:40.1 -- not a known variable star
04:25:06.50 +74:16:43.6 -- not a known variable star
04:26:15.89 +74:20:46.5 -- not a known variable star
04:29:24.48 +72:16:49.5 -- not a known variable star
04:36:42.90 +67:22:50.0 -- not a known variable star
04:37:22.95 +66:31:20.4 -- not a known variable star
04:48:25.47 +74:26:29.4 -- not a known variable star
04:49:43.06 +69:03:30.4 -- not a known variable star
04:49:51.39 +72:55:24.4 -- not a known variable star
04:49:57.27 +72:52:56.1 -- not a known variable star
04:50:07.56 +67:38:40.2 -- not a known variable star
04:54:54.07 +71:07:54.2 -- not a known variable star
04:59:22.76 +70:27:55.9 -- not a known variable star
05:00:45.91 +69:22:17.9 -- not a known variable star
05:05:25.67 +74:23:23.4 -- not a known variable star
05:06:26.53 +69:38:25.5 -- not a known variable star
05:10:53.29 +74:08:56.7 -- not a known variable star
05:13:17.89 +69:36:37.3 -- not a known variable star
05:14:12.00 +72:16:54.9 -- not a known variable star
05:21:42.89 +73:12:29.4 -- not a known variable star
05:30:41.31 +64:21:08.9 -- not a known variable star
05:38:42.61 +70:52:04.4 -- not a known variable star
05:47:47.03 +71:31:12.0 -- not a known variable star
06:03:24.68 +66:39:45.3 -- not a known variable star
Found 44 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
45 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 45 (excluding asteroids and hot pixels, 44 new), not updating the exclusion list!
###################################################################################
Not allowed to update the exclusion list IS_THIS_TEST_RUN=NO ALLOW_EXCLUSION_LIST_UPDATE= NO
The observatory MPC code is V36
############################################################
Positions of planets computed with util/planet_finder/main.py for JD(UT)2461149.68219115 -observatory V36
00:24:35.18 -00:12:26.8 Mercury (-0.1mag)
03:24:18.00 +19:00:37.1 Venus (-3.9mag)
00:26:52.35 +01:51:24.1 Mars (1.2mag)
07:14:07.79 +22:43:44.2 Jupiter (-2.1mag)
00:30:35.48 +00:57:44.9 Saturn (0.9mag)
03:48:22.54 +19:49:38.7 Uranus (5.8mag)
00:11:15.13 -00:12:46.8 Neptune (7.8mag)
20:33:53.02 -22:52:46.9 Pluto (14.5mag)
03:10:30.40 +22:24:25.9 Moon (-8.7mag)
-rw-r--r-- 1 apache apache 362 Apr 19 00:15 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461149.68219115:
07:14:00.29 +22:43:59.9 Io (5.8mag)
07:14:02.96 +22:43:57.2 Europa (5.9mag)
07:13:48.53 +22:44:25.5 Ganymede (5.4mag)
07:14:23.22 +22:43:03.5 Callisto (6.6mag)
07:17:19.33 +22:29:55.5 Himalia (15.4mag)
07:14:11.09 +22:43:38.2 Thebe (16.2mag)
07:17:34.62 +23:00:15.2 Elara (17.3mag)
07:13:13.66 +23:22:04.6 Pasiphae (17.4mag)
07:22:23.13 +22:42:03.4 Carme (18.5mag)
00:30:26.54 +00:58:06.6 Titan (8.8mag)
00:30:34.52 +00:58:01.0 Rhea (10.1mag)
00:30:10.72 +00:57:23.6 Iapetus (11.5mag)
00:30:31.47 +00:58:12.9 Hyperion (14.8mag)
00:32:09.80 +01:06:12.1 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 19 00:15 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461149.68219115:
15:51:44.87 -18:24:02.4 JWST
16:18:41.04 +49:51:06.8 Chandra
17:35:46.52 -44:29:17.3 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 19 00:15 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461149.68219115 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:53:11.26 -28:58:11.6 13.9mag P/2010 H2 (Vales)
05:09:03.97 -69:30:51.8 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:33:09.77 +31:27:35.0 17.2mag C/2017 K2 (PANSTARRS)
17:30:04.01 +10:55:16.7 17.6mag C/2021 G2 (ATLAS)
23:11:01.89 +29:21:29.3 17.1mag C/2022 E2 (ATLAS)
04:32:57.98 +26:07:24.0 16.0mag C/2022 N2 (PANSTARRS)
09:04:10.46 +32:01:47.4 16.2mag C/2022 QE78 (ATLAS)
08:31:36.98 +00:10:39.5 17.4mag C/2022 R6 (PANSTARRS)
18:52:54.88 +18:47:47.4 17.6mag C/2023 A3 (Tsuchinshan-ATLAS)
15:39:36.22 -11:28:29.0 17.5mag P/2023 B1 (PANSTARRS)
09:06:14.95 -11:22:53.2 17.7mag C/2023 F3 (ATLAS)
21:57:17.21 +63:05:50.9 17.5mag C/2023 H5 (Lemmon)
19:16:16.19 -03:47:27.4 14.1mag C/2023 R1 (PANSTARRS)
21:24:18.23 +86:21:25.7 17.8mag C/2023 X2 (Lemmon)
06:19:31.63 +63:30:10.5 17.2mag C/2024 A1 (ATLAS)
05:19:58.52 +19:18:49.8 11.3mag C/2024 E1 (Wierzchos)
16:17:10.24 +06:54:35.3 17.4mag C/2024 G6 (ATLAS)
20:21:37.68 +16:08:53.0 14.6mag C/2024 J3 (ATLAS)
03:29:15.08 -21:54:27.6 16.3mag C/2024 T5 (ATLAS)
05:19:26.86 +44:30:54.1 17.7mag C/2025 J1 (Borisov)
13:25:44.29 +47:21:53.9 15.3mag C/2025 L1 (ATLAS)
03:30:23.22 -26:43:08.0 17.9mag C/2025 Q3 (ATLAS)
00:18:25.65 +17:00:00.9 8.1mag C/2025 R3 (PANSTARRS)
12:52:45.19 +03:12:05.8 17.4mag C/2025 Y1 (ATLAS)
03:51:32.15 +02:19:52.3 14.2mag C/2026 A1 (MAPS)
00:08:28.50 +37:47:03.1 14.7mag C/2026 B2 (Sun-Gao)
18:49:07.28 -09:32:47.4 11.6mag 10P/Tempel
14:55:57.98 +02:51:41.8 14.3mag 24P/Schaumasse
11:02:00.22 -01:25:38.2 15.7mag 29P/Schwassmann-Wachmann
10:37:33.60 -03:51:26.6 17.0mag 43P/Wolf-Harrington
01:53:36.46 +18:01:36.0 17.3mag 47P/Ashbrook-Jackson
07:16:43.20 +36:19:21.5 17.0mag 63P/Wild
23:33:04.76 -11:04:22.5 15.7mag 65P/Gunn
04:11:50.58 +22:19:35.2 15.9mag 76P/West-Kohoutek-Ikemura
01:12:38.36 +08:51:02.4 14.3mag 78P/Gehrels
23:12:32.05 -08:26:58.0 14.7mag 88P/Howell
02:19:28.95 +21:28:37.6 15.1mag 93P/Lovas
05:00:53.17 +32:27:04.5 16.2mag 123P/West-Hartley
08:32:14.59 +36:53:41.7 16.2mag 124P/Mrkos
02:38:09.38 +14:43:17.7 16.4mag 128P/Shoemaker-Holt
02:53:47.73 +14:52:28.0 17.5mag 131P/Mueller
01:43:01.93 +14:17:42.0 10.5mag 141P/Machholz
01:51:28.41 +06:03:38.8 10.5mag 141P-A/Machholz
00:35:20.64 +01:52:26.0 12.4mag 141P-D/Machholz
02:22:00.24 +07:48:59.0 17.9mag 141P-I/Machholz
01:11:16.78 +00:04:45.4 15.0mag 162P/SidingSpring
14:45:48.37 +00:14:26.0 17.7mag 210P/Christensen
21:47:50.53 -10:41:09.1 17.7mag 218P/LINEAR
17:17:09.51 -13:32:48.5 16.1mag 235P/LINEAR
05:41:24.15 +34:55:32.2 16.8mag 240P/NEAT
07:40:07.74 -04:49:53.5 17.8mag 242P/Spahr
22:24:52.17 -20:06:53.6 17.8mag 260P/McNaught
02:04:44.39 +21:15:25.2 18.0mag 295P/LINEAR
15:41:20.45 +07:11:37.6 17.5mag 391P/Kowalski
07:35:29.05 +21:22:20.7 17.7mag 450P/LONEOS
05:40:33.61 +44:50:48.5 17.5mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.8K Apr 19 00:15 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
14:49:14.13 -27:29:20.60 ASASSN-26cu 2026-04-16.06 14.03
17:21:59.44 -38:54:04.60 ASASSN-26ct 2026-04-14.4 15.15
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
14:49:14.13 -27:29:20.60 2026-04-16.06 14.03
12:23:20.40 +04:53:39.10 AT2026ixd 2026-04-12.14 17.65
17:46:09.76 -61:19:50.40 SN2026icy 2026-04-12.2 17.03
09:25:46.42 +02:13:46.30 SN2026gud 2026-04-11.98 16.49
16:52:15.46 -60:27:45.90 ASASSN-26cs 2026-04-12.4 15.5
04:20:55.37 -51:15:31.10 ASASSN-26cr 2026-04-12.01 15.37
22:25:39.35 +36:45:06.90 AT2026ihl 2026-04-10.48 14.21
19:40:44.94 +00:41:03.80 AT2026imw 2026-04-10.32 16.06
19:52:04.70 +05:53:33.50 ASASSN-26cq 2026-04-9.31 14.98
16:08:18.39 -64:11:08.80 ASASSN-26cp 2026-04-9.29 13.32
09:22:22.90 -61:02:43.70 SN2026idh 2026-04-7.97 16.34
05:06:54.12 -19:42:26.40 AT2026imr 2026-04-8 17.49
07:14:55.34 -36:03:21.40 AT2026hei 2026-04-8.12 16.7
21:35:33.14 -19:01:34.80 AT2026ihm 2026-04-8.36 16.7
04:28:24.08 -32:25:35.30 AT2026imo 2026-04-8.02 16.81
05:10:35.79 -39:38:40.80 SN 2026hnn 2026-04-7.04 17.07
09:54:32.04 -01:17:25.80 ASASSN-26cn 2026-04-7.01 15.58
07:46:24.43 -77:29:36.30 ASASSN-26co 2026-04-7.15 15.11
05:00:45.52 -29:51:06.20 AT2026hvw 2026-04-6.03 16.51
19:49:33.10 -23:37:11.00 ASASSN-26cl 2026-04-5.29 14.98
19:32:43.55 -22:39:33.40 ASASSN-26cm 2026-04-4.3 13.88
18:08:57.38 +76:48:23.60 ASASSN-26ck 2026-04-2.37 15.38
16:16:36.10 +44:52:30.20 AT2026hyy 2026-04-2.58 13.81
21:55:23.31 -34:48:53.90 ASASSN-26cj 2026-03-30.4 -1.47
11:19:50.81 -27:51:50.40 SN2026gvk 2026-03-30 15.28
11:53:57.02 -23:09:46.20 SN2026gzx 2026-03-28.75 15.27
07:13:46.14 -33:10:15.70 ASASSN-26ci 2026-03-28.15 15.14
09:03:36.09 -67:58:13.00 SN2026hkg 2026-03-28.19 15.82
07:03:00.72 +39:14:43.00 SN2026fin 2026-03-28.27 15.82
05:35:42.79 -63:44:05.60 ASASSN-26ch 2026-03-28.12 13.14
11:23:19.04 +34:22:38.00 SN2026fwt 2026-03-27.3 16.56
19:03:49.79 +37:04:05.20 ASASSN-26ce 2026-03-26.56 16.3
20:26:56.07 -52:54:06.50 AT2026hiy 2026-03-26.35 16.95
05:25:54.76 -30:15:35.80 ASASSN-26cg 2026-03-25.07 16.88
06:57:16.49 -26:54:37.20 SN2026fzb 2026-03-25.14 15.8
14:37:38.23 -43:00:52.30 ASASSN-26cd 2026-03-24.24 12.52
17:34:53.03 +06:04:29.70 AT2026gzl 2026-03-23.27 15.82
08:30:02.60 -35:12:47.50 ASASSN-26cf 2026-03-23.2 14.82
16:54:25.33 +37:49:56.60 SN 2026evz 2026-03-21.32 17.54
17:06:19.20 -18:54:19.50 ASASSN-26bx 2026-03-21.25 16.39
19:01:16.28 -29:29:23.10 ASASSN-26bw 2026-03-21.33 15.81
08:46:05.75 +10:47:39.80 ASASSN-26ca 2026-03-21.13 14.27
12:14:58.16 +63:47:16.20 SN 2026fvx 2026-03-21.12 15.6
18:02:55.90 -75:23:02.60 ASASSN-26bz 2026-03-21.32 16.16
12:16:02.87 -53:16:33.70 ASASSN-26cc 2026-03-20.08 3.93
13:08:21.85 +29:13:44.20 SN 2026fmh 2026-03-20.16 -0.33
19:56:38.48 -34:45:21.50 ASASSN-26cb 2026-03-20.35 -3.26
14:32:41.15 -41:38:48.50 ASASSN-26by 2026-03-20.15 -1.31
13:00:42.99 +37:18:34.60 SN2026fjc 2026-03-19.5 15.97
06:02:44.21 -04:11:06.20 ASASSN-26bv 2026-03-19.19 15.67
12:20:27.90 -45:55:38.40 ASASSN-26bt 2026-03-19.05 16.24
07:49:57.30 -56:14:35.10 ASASSN-26bu 2026-03-19.19 15.74
06:04:29.75 +53:23:34.00 SN 2026eza 2026-03-18.2 17.48
11:54:57.87 +69:19:28.90 AT2026fsf 2026-03-18.14 16.95
10:44:46.95 +58:27:29.30 SN 2026enn 2026-03-18.13 17.53
20:45:54.04 -73:26:43.00 AT 2026ezy 2026-03-18.13 16.83
06:53:18.10 -59:10:49.30 ASASSN-26bs 2026-03-18.02 16.93
07:45:09.29 -62:14:36.20 ASASSN-26br 2026-03-16.16 16.78
19:24:27.93 -52:04:36.40 AT 2023uk 2026-03-16.35 14.2
04:52:54.50 -15:20:57.10 AT2026fhw 2026-03-14.06 SDSS
11:10:34.24 +02:58:48.10 SN2026drr 2026-03-14.08 0.2
07:26:45.73 -27:45:13.90 ASASSN-26bo 2026-03-14.17 13.8
16:35:46.94 +58:12:28.40 SN2026ebt 2026-03-12.41 17.12
13:01:19.45 +15:42:15.00 SN2026ehe 2026-03-12.11 -0.29
09:15:55.41 +10:08:09.70 SN2026efq 2026-03-12.16 0.06
03:31:20.92 -35:29:29.00 SN2026evh 2026-03-12.05 17.29
06:26:19.15 -85:18:28.10 AT2026ffp 2026-03-12.16 0.37
14:16:42.30 -41:18:36.50 AT2026fij 2026-03-12.05 15.97
10:45:04.71 +00:06:13.10 SN 2026exe 2026-03-11.78 16.48
18:07:45.58 +69:43:01.00 SN2026ess 2026-03-12.37 17.37
13:11:03.58 +49:06:31.80 AT2026ewa 2026-03-12.42 16.77
15:03:25.23 -63:11:22.20 ASASSN-26bp 2026-03-11.92 13.33
13:09:37.25 -35:50:25.20 AT2024cmo 2026-03-11.12 16.29
13:06:01.97 -15:50:14.40 AT2026fdy 2026-03-10.33 16.68
11:30:09.67 -47:26:43.70 ASASSN-26bn 2026-03-10.12 15.2
05:03:25.25 -24:16:50.40 (= Gaia 2026-03-9.09 14.32
03:42:32.53 -04:17:53.70 ASASSN-26bm 2026-03-8.04 15.22
04:31:00.53 -68:29:50.20 ASASSN-26bl 2026-03-7.9 10.26
16:18:17.61 +41:25:11.40 SN 2026dkf 2026-03-6.31 16.7
13:45:00.35 +61:16:50.90 SN 2026ejl 2026-03-6.41 -0.66
09:27:45.48 -37:49:32.80 ASASSN-26bk 2026-03-2.3 13.11
20:22:01.20 +23:47:47.30 ASASSN-26bi 2026-02-28.51 15.86
11:16:22.10 +29:26:22.80 AT2026enm 2026-02-28.39 16.88
08:05:59.83 -48:39:35.60 ASASSN-26bh 2026-02-26.05 14.64
13:24:27.02 -45:57:01.40 ASASSN-26bg 2026-02-26.35 15.28
17:27:50.95 -68:28:46.40 ASASSN-26bf 2026-02-26.3 16.28
18:03:39.37 +19:58:46.70 ASASSN-26be 2026-02-25.58 14.8
17:40:18.19 +07:20:59.60 SN 2026crm 2026-02-24.34 16.9
18:38:36.11 -79:28:58.40 ASASSN-26bb 2026-02-24.36 16.11
17:43:29.75 +11:24:00.60 ASASSN-26bc 2026-02-23.37 -3.37
16:59:41.08 -80:01:51.20 ASASSN-26bd 2026-02-23.3 14.38
11:23:31.77 -08:39:15.40 SN2026cff 2026-02-23.15 -1.08
14:55:17.39 -05:56:05.30 SN2026dmk 2026-02-23.22 -0.76
12:28:15.19 +44:27:20.80 SN2026cjz 2026-02-23.47 15.62
12:12:29.55 -02:40:43.30 AT2026dsk 2026-02-23.4 17.21
09:21:05.29 +06:11:42.80 SN2026chr 2026-02-23.1 17.39
16:05:38.61 +18:06:07.40 SN 2026dsy 2026-02-23.36 17.15
-rw-r--r-- 1 apache apache 5.8K Apr 19 00:15 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
09:54:46.47 +69:06:31.7 PNV J09544647+6906317 2026-01-26.8081 19.3mag
18:08:51.99 -26:16:21.9 TCP J18085199-2616219 2026-01-31.8519 12.2mag
08:01:11.02 -03:43:14.1 TCP J08011102-0343141 2026-02-08.8090 15.10Cmag
05:19:15.40 -02:04:51.5 TCP J05191540-0204515 2026-02-13.4306 14.5mag
10:52:41.26 +36:40:08.9 TCP J10524126+3640089 2026-02-17.6065 17.4mag
05:50:50.81 +36:22:45.1 TCP J05505081+3622451 2026-02-17.5511 15.7mag
00:42:51.33 +41:13:49.1 PNV J00425133+4113491 2026-02-20.738 18.3mag
00:43:04.88 +41:29:41.4 PNV J00430488+4129414 2026-02-20.5923 18.84Cmag
17:43:29.74 +11:24:00.3 TCP J17432974+1124003 2026-02-22.3773 13.6mag
09:55:01.59 +69:08:42.7 PNV J09550159+6908427 2026-02-20.893 19.0mag
07:03:25.76 -12:41:40.1 TCP J07032576-1241401 2026-03-10.4268 15.4mag
00:42:36.82 +41:16:05.8 PNV J00423682+4116058 2026-03-12.5744 17.24Cmag
07:26:45.79 -27:45:14.1 TCP J07264579-2745141 2026-03-17.4417 14.8mag
17:57:19.56 -28:08:14.7 TCP J17571956-2808147 2026-03-19.7972 14.5mag
08:46:05.73 +10:47:39.7 TCP J08460573+1047397 2026-03-21.1936 14.5mag
09:55:38.83 +69:05:21.7 PNV J09553883+6905217 2026-04-01.893 19.4mag
19:32:43.67 -22:39:30.7 TCP J19324367-2239307 2026-04-05.4395 13.6mag
16:16:36.03 +44:52:28.9 TCP J16163603+4452289 2026-04-05.6655 14.2mag
00:43:38.36 +41:15:32.4 PNV J00433836+4115324 2026-04-08.079 17.2mag
15:41:11.68 +59:18:26.8 TCP J15411168+5918268 2026-04-12.9625 19.2mag
-rw-r--r-- 1 apache apache 188K Apr 19 00:15 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
17:08:30.580 +41:56:13.61 AT 2026jje 2026-04-03.89 21.47
16:48:25.780 +33:00:44.35 AT 2026jjd 2026-04-03.85 21.29
16:46:02.450 +30:55:42.15 AT 2026jjc 2026-04-03.80 19.57
16:51:04.120 +44:26:50.06 AT 2026jjb 2026-03-30.84 21.02
12:10:02.030 +43:26:37.06 AT 2026jja 2026-03-28.87 21.46
17:56:59.910 +48:20:04.31 AT 2026jiz 2026-03-27.87 20.99
15:23:12.550 +15:30:01.81 AT 2026jiy 2026-03-27.82 21.09
12:45:41.400 +53:52:15.13 AT 2026jix 2026-03-24.70 20.56
12:05:28.040 +47:18:05.03 AT 2026jiw 2026-03-24.69 20.17
12:49:49.680 +44:27:28.62 AT 2026jiv 2026-03-24.69 21.87
12:17:57.600 +45:03:04.77 AT 2026jiu 2026-03-24.69 20.4
11:39:16.940 +45:15:03.67 AT 2026jit 2026-03-24.66 21.06
14:17:33.100 +43:22:03.41 AT 2026jis 2026-03-22.80 20.74
14:45:33.130 +38:26:13.04 AT 2026jir 2026-03-22.80 21.14
14:42:55.800 +38:18:34.13 AT 2026jiq 2026-03-22.80 21.14
12:43:36.900 +28:13:26.06 AT 2026jip 2026-03-20.69 21.81
13:50:42.590 +38:45:33.09 AT 2026jio 2026-03-29.93 20.87
19:45:48.257 -49:40:35.86 AT 2026jin 2026-04-12.35 18.142
23:14:08.648 +35:53:12.54 AT 2026jim 2026-03-28.53 17.909
07:22:52.030 +11:04:39.45 AT 2026jil 2026-04-11.54 18.4
-rw-r--r-- 1 apache apache 30K Apr 19 00:15 tns_transients_list.txt
