This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa
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
target,2461146.6775,11.47,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 20260416.1775 11.47CV 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,2461146.6775,14.74,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 20260416.1775 14.74CV 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,2461146.6775,14.86,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 20260416.1775 14.86CV 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,2461146.6775,14.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 20260416.1775 14.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,2461146.6775,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 20260416.1775 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
Gaia DR3 499327267132848384,2461146.6775,14.85,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 499327267132848384 20260416.1775 14.85CV 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,2461146.6775,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 20260416.1775 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,2461146.6775,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 20260416.1775 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,2461146.6775,14.39,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 20260416.1775 14.39CV 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,2461146.6775,14.42,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 20260416.1775 14.42CV 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,2461146.6775,14.39,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 20260416.1775 14.39CV 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,2461146.6775,14.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 20260416.1775 14.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,2461146.6775,14.16,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 20260416.1775 14.16CV 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,2461146.6775,13.91,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 20260416.1775 13.91CV 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,2461146.6775,13.22,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 20260416.1775 13.22CV 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 543517017412313856,2461146.6775,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
Gaia DR3 543517017412313856 20260416.1775 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,2461146.6775,11.57,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 20260416.1775 11.57CV 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,2461146.6775,12.44,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 20260416.1775 12.44CV 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,2461146.6775,12.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 20260416.1775 12.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,2461146.6775,13.13,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 20260416.1775 13.13CV 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,2461146.6775,13.43,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 20260416.1775 13.43CV 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,2461146.6775,13.46,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 20260416.1775 13.46CV 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 16.1775* 03 12 40.99 +71 11 14.2 13.4 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,2461146.6775,13.45,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 20260416.1775 13.45CV 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 16.1775* 03 25 33.72 +73 13 23.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,2461146.6775,13.78,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 20260416.1775 13.78CV 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 16.1775* 03 30 41.90 +73 56 35.3 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
Gaia DR3 544705177163773184,2461146.6775,13.78,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 544705177163773184 20260416.1775 13.78CV 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 501224680607043840,2461146.6775,13.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
Gaia DR3 501224680607043840 20260416.1775 13.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,2461146.6775,13.93,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 20260416.1775 13.93CV 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,2461146.6775,13.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 20260416.1775 13.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!
TCP 2026 04 16.1775* 03 29 06.55 +72 34 20.2 13.9 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,2461146.6775,13.94,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 20260416.1775 13.94CV 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 495750899407105536,2461146.6775,13.86,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 495750899407105536 20260416.1775 13.86CV 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,2461146.6775,13.85,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 20260416.1775 13.85CV 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,2461146.6775,13.93,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 20260416.1775 13.93CV 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
ST Cam,2461146.6775,13.94,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
ST Cam 20260416.1775 13.94CV 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,2461146.6775,14.12,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 20260416.1775 14.12CV 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 550658100617584384,2461146.6775,14.10,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 550658100617584384 20260416.1775 14.10CV 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,2461146.6775,14.27,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 20260416.1775 14.27CV 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,2461146.6775,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
target 20260416.1775 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
Gaia DR3 501570408292887808,2461146.6775,14.21,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 501570408292887808 20260416.1775 14.21CV 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,2461146.6775,14.15,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 20260416.1775 14.15CV 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,2461146.6775,14.26,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 20260416.1775 14.26CV 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,2461146.6775,14.21,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 20260416.1775 14.21CV 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,2461146.6775,14.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 20260416.1775 14.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,2461146.6775,14.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 20260416.1775 14.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,2461146.6775,14.36,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 20260416.1775 14.36CV 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,2461146.6775,14.45,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 20260416.1775 14.45CV 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,2461146.6775,14.33,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 20260416.1775 14.33CV 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 500459008196048384,2461146.6775,14.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
Gaia DR3 500459008196048384 20260416.1775 14.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,2461146.6775,14.36,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 20260416.1775 14.36CV 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,2461146.6775,14.39,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 20260416.1775 14.39CV 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,2461146.6775,14.36,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 20260416.1775 14.36CV 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 496746021851344896,2461146.6775,14.46,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 496746021851344896 20260416.1775 14.46CV 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 500152003934148864,2461146.6775,14.43,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 500152003934148864 20260416.1775 14.43CV 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,2461146.6775,14.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 20260416.1775 14.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
Gaia DR3 501224680607043840,2461146.6775,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
Gaia DR3 501224680607043840 20260416.1775 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,2461146.6775,14.74,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 20260416.1775 14.74CV 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,2461146.6775,14.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 20260416.1775 14.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,2461146.6775,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 20260416.1775 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
Gaia DR3 494232435190402560,2461146.6775,14.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
Gaia DR3 494232435190402560 20260416.1775 14.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,2461146.6775,14.69,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 20260416.1775 14.69CV 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,2461146.6775,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 20260416.1775 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!
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,2461146.6775,14.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 20260416.1775 14.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,2461146.6775,14.78,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 20260416.1775 14.78CV 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,2461146.6775,14.91,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 20260416.1775 14.91CV 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,2461146.6775,14.68,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 20260416.1775 14.68CV 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 543699708140435968,2461146.6775,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
Gaia DR3 543699708140435968 20260416.1775 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
Gaia DR3 497929684776540928,2461146.6775,14.71,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 497929684776540928 20260416.1775 14.71CV 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
Mean magnitude and position on the discovery images:
2026 04 16.1775 2461146.6775 14.80 05:20:05.30 +66:50:10.0
145.14296 16.46017 galactic Cam Second-epoch detections are separated by 8.1" and 2.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Large-amplitude variable Gaia DR2 484172148615036928 | 05:20:05.59 +66:50:04.3 (Gaia DR3) | 2021A&A...648A..44M | | Gaia3var=NOT_AVAILABLE (the VSX policy as of May 2022 seems to be NOT to regard variables from 2021A&A...648A..44M as 'known' for the lack of classification)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
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
Large-amplitude variable Gaia DR2 484172148615036928,2461146.6775,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
Large-amplitude variable Gaia DR2 484172148615036928 20260416.1775 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
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
ZTF J050454.37+730033.9,2461146.6775,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
ZTF J050454.37+730033.9 20260416.1775 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,2461146.6775,14.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 20260416.1775 14.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,2461146.6775,14.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 20260416.1775 14.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,2461146.6775,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 20260416.1775 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,2461146.6775,14.96,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 20260416.1775 14.96CV 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,2461146.6775,14.97,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 20260416.1775 14.97CV 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,2461146.6775,14.96,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 20260416.1775 14.96CV 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,2461146.6775,14.91,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 20260416.1775 14.91CV 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,2461146.6775,11.21,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 20260416.1775 11.21CV 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: 2461146.67783582 16.04.2026 04:15:55.015 /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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: 7 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): 16840
Objects passed selection criteria: 16821
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: 15148.8
Average stars matched: 14742.8 (97.3199 %)
Memory usage VmPeak: 121340 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Wed Apr 15 18:49:36 CDT 2026
VaST build number 1.0rc89-18-ga9a0ae89
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-15)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Wed Apr 15 23:22:33 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: 2461146.67783582 16.04.2026 04:15:55.015 /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 293
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: 56 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): 116432
Objects passed selection criteria: 116159
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: 106608
Average stars matched: 102844 (96.4696 %)
Memory usage VmPeak: 1895860 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Wed Apr 15 18:49:36 CDT 2026
VaST build number 1.0rc89-18-ga9a0ae89
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-15)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Wed Apr 15 23:35:34 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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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: 2461146.67715131
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-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits exists and is non-empty
Saving wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits to local_wcs_cache/
'wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits' -> 'local_wcs_cache/wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits'
wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits exists and is non-empty
Saving wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits to local_wcs_cache/
'wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits' -> 'local_wcs_cache/wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits (1st new image)
verification OK: wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
Image size: 932.1'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:09.116 +69:58:06.62 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:09.116 +69:58:06.62
Angular distance between the image centers 0.0755 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-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits (2nd new image)
verification OK: wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
Image size: 932.1'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:07.392 +69:58:01.58 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:07.392 +69:58:01.58
Angular distance between the image centers 0.0733 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:09.116 +69:58:06.62
Second-epoch second image center 04:48:07.392 +69:58:01.58
Angular distance between the image centers 0.00283 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.b14Ol5V7QM
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.UuolpQVetA
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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits &> /tmp/tmp.lV6kocDCg5
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits &> /tmp/tmp.ExXPBh2GbT
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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 6 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.2 pix fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
2.1 pix fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
15.0 mag. fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
All-image limiting magnitude estimate: 15.0 (SNR ) 12.1 (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.b14Ol5V7QM (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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/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.UuolpQVetA (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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/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.lV6kocDCg5 (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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
WCS_IMAGE_NAME=wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
WCS-calibrated image found: wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
Checking if the catalog wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits alredy exist and is non-empty...
Catalog wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.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-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
WCS catalog name: wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=896, passed=13080
Got 13080 stars (including 12168 good ones) from the SExtractor catalog wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat
util/solve_plate_with_UCAC5 got 13080 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.1'
Seting catalog search parameters based on the expected field of view 932.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012946 (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.010357 (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: 225 matched stars entering correct_measured_positions(), 176 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.13"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 218 matched stars entering correct_measured_positions(), 2854 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.12"
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 326 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 296 matched stars entering correct_measured_positions(), 2888 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.85"
Accuracy estimation diagnostic: 293 matched stars entering correct_measured_positions(), 3801 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.47"
Excluding outliers - 293 stars left (next iteration limit 239)
The image catalog is written to wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits -region wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.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.ExXPBh2GbT (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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
WCS_IMAGE_NAME=wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
WCS-calibrated image found: wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
Checking if the catalog wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits alredy exist and is non-empty...
Catalog wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
WCS catalog name: wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=927, passed=12845
Got 12845 stars (including 11899 good ones) from the SExtractor catalog wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat
util/solve_plate_with_UCAC5 got 12845 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.1'
Seting catalog search parameters based on the expected field of view 932.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012946 (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.010357 (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 272 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 221 matched stars entering correct_measured_positions(), 172 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.12"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 213 matched stars entering correct_measured_positions(), 2801 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 324 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 290 matched stars entering correct_measured_positions(), 2838 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.12"
Accuracy estimation diagnostic: 290 matched stars entering correct_measured_positions(), 3767 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.63"
Excluding outliers - 290 stars left (next iteration limit 234)
The image catalog is written to wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits -region wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/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-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits'
Saving fully-calibrated image wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits'
Preparing the HTML report for the field Cam-06-Q1b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Adding exclusion_list_local.txt__out21320.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 15s
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: 1s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21123_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 21123_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:36:53.31 +70:55:06.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21268_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 21268_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21320_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 21320_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21370_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 21370_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:18:01.16 +71:13:49.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21494_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 21494_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21501_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 21501_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 0s
make_report_in_HTML.sh TOTAL: 16s
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:26:16.32 +74:20:43.2
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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
Creating symlink local_wcs_cache/wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits exists and is non-empty
wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits (1st new image)
verification OK: wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
Image size: 932.1'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:09.116 +69:58:06.62 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:09.116 +69:58:06.62
Angular distance between the image centers 0.0755 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-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits (2nd new image)
verification OK: wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
Image size: 932.1'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:07.392 +69:58:01.58 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:07.392 +69:58:01.58
Angular distance between the image centers 0.0733 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:09.116 +69:58:06.62
Second-epoch second image center 04:48:07.392 +69:58:01.58
Angular distance between the image centers 0.00283 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.HvbApCopSK
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.u4JZ2Y0hr1
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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits &> /tmp/tmp.aBW15JCC4r
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits &> /tmp/tmp.IVXzHSQiFf
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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 258 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
2.0 pix fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
1.9 pix fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
15.2 mag. fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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.HvbApCopSK (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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/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.u4JZ2Y0hr1 (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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/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.aBW15JCC4r (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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
WCS_IMAGE_NAME=wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
WCS-calibrated image found: wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
Checking if the catalog wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits alredy exist and is non-empty...
Catalog wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.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-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
WCS catalog name: wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=28, blended=6619, passed=91915
Got 91915 stars (including 85157 good ones) from the SExtractor catalog wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat
util/solve_plate_with_UCAC5 got 91915 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.1'
Seting catalog search parameters based on the expected field of view 932.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012946 (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.010357 (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 281 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 232 matched stars entering correct_measured_positions(), 183 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.11"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 224 matched stars entering correct_measured_positions(), 20907 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.82"
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 329 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 293 matched stars entering correct_measured_positions(), 20931 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.80"
Accuracy estimation diagnostic: 292 matched stars entering correct_measured_positions(), 27385 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.55"
Excluding outliers - 292 stars left (next iteration limit 246)
The image catalog is written to wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits -region wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.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.IVXzHSQiFf (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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
WCS_IMAGE_NAME=wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
WCS-calibrated image found: wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
Checking if the catalog wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits alredy exist and is non-empty...
Catalog wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
WCS catalog name: wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=32, blended=6858, passed=94394
Got 94394 stars (including 87390 good ones) from the SExtractor catalog wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat
util/solve_plate_with_UCAC5 got 94394 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.1'
Seting catalog search parameters based on the expected field of view 932.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012946 (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.010357 (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 289 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 241 matched stars entering correct_measured_positions(), 190 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.82"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 232 matched stars entering correct_measured_positions(), 22320 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.77"
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 339 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 302 matched stars entering correct_measured_positions(), 22344 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.75"
Accuracy estimation diagnostic: 301 matched stars entering correct_measured_positions(), 28673 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.95"
Excluding outliers - 301 stars left (next iteration limit 255)
The image catalog is written to wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits -region wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/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-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-14-55_20.00sec_-4.90C_LIGHTs_0098.fits
Saving fully-calibrated image wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.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-15_CI_Cam-06-Q1b1x1_231646_TTUQ1b1x1_16551_lQynoZFa/wcs_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099.fits
Preparing the HTML report for the field Cam-06-Q1b1x1 with default.sex.telephoto_lens_vSTL
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
Adding exclusion_list_gaiadr2.txt__out141956.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out141962.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out141987.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out141989.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out141993.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out141997.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out142008.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out142015.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out143471.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out143722.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out144162.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out144196.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out144285.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out144719.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out144968.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out141961.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141970.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141971.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141981.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141982.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141984.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142000.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142003.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142005.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142006.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142013.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142023.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142026.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142036.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142041.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142254.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142500.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142728.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142918.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142998.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143000.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143065.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143314.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143318.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143457.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143477.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143478.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143539.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143551.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143564.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143703.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143727.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143735.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143765.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143874.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143882.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143919.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143982.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144022.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144046.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144064.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144072.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144084.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144104.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144172.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144173.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144181.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144243.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144296.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144298.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144336.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144342.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144457.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144497.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144581.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144612.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144615.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144661.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144671.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144688.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144702.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144712.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144749.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144791.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144851.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144853.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144872.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144881.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144939.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144953.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144959.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144995.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145070.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145094.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out78258.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 134s
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: 49s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141956_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 141956_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:05:19.36 +74:01:25.0 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.97, MAG_FAINT_SEARCH_LIMIT=15.95)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141961_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 141961_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141962_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 141962_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:53:07.71 +74:41:54.6 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.86, MAG_FAINT_SEARCH_LIMIT=15.84)GAIADR2_OUTPUT=# 1.857 550625841121239552 058.28368640035 +74.69881023792 14.7010 14.0643 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#1.857#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141970_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 141970_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141971_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 141971_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141977_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 141977_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:03:54.23 +71:10:44.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141979_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 141979_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (25.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141981_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 141981_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141982_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 141982_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141984_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 141984_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141985_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 141985_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141987_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 141987_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:01:54.30 +72:50:35.1 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.69, MAG_FAINT_SEARCH_LIMIT=15.67)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141989_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 141989_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:55:23.58 +74:35:49.5 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.56, MAG_FAINT_SEARCH_LIMIT=15.54)GAIADR2_OUTPUT=# 2.769 550620721520225664 058.84965324332 +74.59775606739 14.4357 13.6798 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#2.769#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141992_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 141992_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:35:30.87 +70:47:52.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141993_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 141993_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:30:34.46 +68:56:35.7 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.80, MAG_FAINT_SEARCH_LIMIT=15.78)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141995_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 141995_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141997_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 141997_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:27:45.16 +70:23:44.7 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.64, MAG_FAINT_SEARCH_LIMIT=15.62)GAIADR2_OUTPUT=# 3.882 500047103653281408 066.93535552475 +70.39627262646 14.8878 14.2765 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.882#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142000_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142000_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142003_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142003_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142004_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142004_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (25.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142005_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142005_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142006_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142006_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142008_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142008_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:06:45.36 +70:50:34.4 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.37, MAG_FAINT_SEARCH_LIMIT=15.35)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142013_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142013_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142015_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142015_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:40:18.37 +71:44:28.1 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.26, MAG_FAINT_SEARCH_LIMIT=15.24)GAIADR2_OUTPUT=# 2.025 543344222286978304 055.07735798221 +71.74063804230 14.2444 13.5101 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#2.025#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142023_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142023_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142025_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142025_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (18.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142026_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142026_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142027_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142027_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142036_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142036_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142037_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142037_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:34:26.27 +71:29:04.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142039_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142039_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142041_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142041_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142182_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142182_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142249_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142249_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:31:11.83 +71:05:31.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142254_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142254_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142283_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142283_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (15.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142308_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142308_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142313_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142313_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142324_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142324_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142360_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142360_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142395_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142395_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (17.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142396_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142396_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142400_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142400_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142413_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142413_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142417_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142417_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (20.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142434_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142434_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142470_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142470_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:13:19.75 +72:06:35.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142500_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142500_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142559_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142559_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142580_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142580_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142651_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142651_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:00:27.23 +68:34:40.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142658_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142658_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:13:40.62 +72:09:26.2 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142661_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142661_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142690_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142690_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142701_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142701_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142723_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142723_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142728_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142728_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142769_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142769_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:55:26.96 +74:20:31.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142801_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142801_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142827_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142827_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142835_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142835_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142851_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142851_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142866_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142866_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142918_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142918_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142928_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142928_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142943_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142943_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142955_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 142955_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142998_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 142998_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143000_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143000_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143065_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143065_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143072_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143072_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143080_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143080_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143100_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143100_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143113_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143113_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143118_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143118_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143134_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143134_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:45:46.65 +72:07:42.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143140_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143140_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143163_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143163_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143186_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143186_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (22.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143192_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143192_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (15.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143202_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143202_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143217_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143217_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:02:16.99 +70:20:18.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143227_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143227_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:54:15.29 +74:39:33.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143230_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143230_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143242_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143242_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (17.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143264_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143264_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143265_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143265_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:55:20.95 +67:27:32.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143270_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143270_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143285_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143285_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143286_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143286_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143303_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143303_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:05:42.51 +68:39:43.9 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143305_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143305_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143314_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143314_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143318_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143318_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143349_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143349_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143357_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143357_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:56:29.91 +68:51:31.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143362_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143362_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143376_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143376_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143403_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143403_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143419_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143419_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:14:19.16 +70:46:17.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143420_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143420_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:56:12.66 +71:48:17.3 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143449_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143449_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143457_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143457_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143468_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143468_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143471_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143471_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:57:23.41 +71:25:04.3 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.79, MAG_FAINT_SEARCH_LIMIT=14.77)GAIADR2_OUTPUT=# 3.903 495284156721044352 059.34932034119 +71.41693701258 13.7625 13.1437 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.903#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143477_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143477_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143478_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143478_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143539_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143539_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143543_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143543_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143551_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143551_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143557_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143557_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143564_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143564_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143565_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143565_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143575_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143575_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:27:18.48 +71:47:20.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143596_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143596_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143609_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143609_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143614_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143614_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (20.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143622_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143622_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143646_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143646_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143660_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143660_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (38.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143703_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143703_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143705_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143705_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143713_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143713_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (17.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143722_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143722_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:56:16.17 +74:03:52.6 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.00, MAG_FAINT_SEARCH_LIMIT=14.98)GAIADR2_OUTPUT=# 2.454 549832165524704256 059.06838170196 +74.06523412691 14.0179 13.2021 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#2.454#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143727_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143727_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143729_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143729_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:08:57.91 +70:52:42.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143735_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143735_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143742_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143742_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143754_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143754_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143765_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143765_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143778_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143778_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143781_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143781_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143783_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143783_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143792_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143792_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143813_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143813_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (21.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143816_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143816_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (30.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143823_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143823_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143844_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143844_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143874_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143874_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143882_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143882_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143890_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143890_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143912_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143912_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (17.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143919_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143919_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143925_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143925_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (17.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143943_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143943_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:56:06.23 +69:11:09.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143951_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143951_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143952_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143952_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143961_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143961_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143964_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143964_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143982_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 143982_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143985_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143985_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143990_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143990_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143998_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 143998_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144015_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144015_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144022_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144022_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144036_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144036_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:01:44.01 +71:10:29.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144040_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144040_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144046_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144046_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144064_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144064_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144072_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144072_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144076_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144076_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144084_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144084_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144094_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144094_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144104_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144104_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144115_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144115_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144123_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144123_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144134_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144134_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144151_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144151_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144156_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144156_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144162_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144162_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:39:21.23 +72:14:10.7 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.41, MAG_FAINT_SEARCH_LIMIT=15.39)GAIADR2_OUTPUT=# 3.406 543581094026929792 054.84087944550 +72.23571435393 14.2522 13.6421 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.406#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144172_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144172_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144173_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144173_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144181_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144181_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144196_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144196_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:04:50.95 +71:07:24.3 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.44, MAG_FAINT_SEARCH_LIMIT=15.42)GAIADR2_OUTPUT=# 4.002 495088134413785216 061.21491345771 +71.12413540209 14.2967 13.8357 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.002#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144199_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144199_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (21.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144209_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144209_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144215_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144215_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (21.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144216_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144216_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144218_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144218_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144243_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144243_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144248_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144248_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (21.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144276_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144276_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144282_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144282_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144285_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144285_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:33:59.16 +71:41:31.2 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.45, MAG_FAINT_SEARCH_LIMIT=15.43)GAIADR2_OUTPUT=# 1.303 543156892993657856 053.49563646778 +71.69176018998 14.3625 13.3653 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#1.303#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144296_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144296_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144298_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144298_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144308_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144308_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (27.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144309_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144309_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (20.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144314_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144314_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (27.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144321_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144321_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144336_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144336_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144342_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144342_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144346_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144346_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144349_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144349_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (21.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144361_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144361_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (18.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144375_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144375_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144390_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144390_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144391_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144391_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144419_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144419_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (23.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144457_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144457_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144458_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144458_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144462_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144462_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144497_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144497_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144500_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144500_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (21.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144506_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144506_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:13:47.25 +71:34:11.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144570_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144570_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144581_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144581_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144606_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144606_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144609_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144609_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144612_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144612_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144614_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144614_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (21.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144615_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144615_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144619_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144619_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144626_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144626_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144635_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144635_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144647_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144647_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144652_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144652_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144661_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144661_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144668_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144668_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.1 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144671_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144671_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144679_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144679_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (22.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144680_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144680_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144683_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144683_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144688_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144688_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144702_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144702_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144705_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144705_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144706_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144706_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (29.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144711_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144711_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144712_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144712_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144719_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144719_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:02:21.49 +71:33:00.2 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.53, MAG_FAINT_SEARCH_LIMIT=15.51)GAIADR2_OUTPUT=# 4.338 495300507657585280 060.59103246276 +71.54894674508 15.3950 14.7431 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.338#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144720_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144720_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144724_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144724_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144735_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144735_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144749_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144749_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144780_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144780_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144790_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144790_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144791_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144791_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144851_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144851_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144853_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144853_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144872_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144872_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144881_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144881_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144899_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144899_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144902_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144902_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144911_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144911_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144939_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144939_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144950_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144950_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (17.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144953_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144953_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144959_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144959_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144962_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144962_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (18.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144968_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 144968_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:52:13.50 +69:52:41.0 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.96, MAG_FAINT_SEARCH_LIMIT=15.94)GAIADR2_OUTPUT=# 4.270 494860604226582656 058.05929499480 +69.87749896905 14.7036 13.8164 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.270#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144995_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 144995_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145070_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 145070_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145082_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 145082_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145094_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 145094_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 89441_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 89441_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 03:30:07.83 +68:45:53.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 78258_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
Preparing report for the candidate 78258_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 46725_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099
The candidate 46725_fd_Cam-06-Q1b1x1_2026-04-15_23-15-55_20.00sec_-4.90C_LIGHTs_0099 did not pass the final checks
**** FOUND 04:18:01.26 +71:13:56.3 in the exclusion list exclusion_list.txt ****
make_report_in_HTML.sh Phase 2 (HTML assembly): 5s
make_report_in_HTML.sh TOTAL: 188s
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:26:16.32 +74:20:43.2
05:04:34.42 +66:26:47.3
04:50:07.76 +69:35:08.4
05:13:17.42 +70:54:04.1
05:35:43.79 +68:28:57.0
05:22:53.87 +73:35:08.5
04:14:05.11 +68:04:60.0
04:40:16.27 +74:32:37.3
05:14:14.20 +70:50:34.8
04:16:59.67 +66:56:28.5
04:43:21.72 +72:02:37.0
04:46:16.11 +72:37:50.1
03:41:24.40 +73:57:21.6
04:50:48.22 +67:32:44.0
04:34:24.70 +65:49:46.9
03:50:36.12 +72:48:42.1
04:26:16.28 +74:20:51.7
04:59:22.32 +70:27:55.9
04:17:15.64 +66:58:59.2
05:23:35.43 +72:15:26.2
05:27:57.70 +73:37:35.6
04:48:25.67 +74:26:35.1
03:12:40.99 +71:11:14.2
03:25:33.72 +73:13:23.7
03:30:41.90 +73:56:35.3
04:23:00.02 +72:23:27.4
04:54:54.10 +71:07:57.0
05:28:24.41 +72:20:46.6
03:29:06.55 +72:34:20.2
04:26:59.49 +67:44:51.3
05:25:26.50 +70:14:45.7
05:03:23.89 +68:22:01.8
04:51:08.27 +68:10:40.6
04:49:57.45 +72:52:60.0
03:44:46.83 +74:36:13.1
04:55:59.89 +72:50:45.4
04:46:00.44 +67:30:45.3
04:22:57.14 +73:36:29.5
04:32:04.39 +69:05:49.2
04:38:22.26 +74:17:13.8
03:38:39.76 +65:56:54.5
04:24:04.42 +68:14:41.6
05:54:46.99 +73:10:60.0
03:49:46.30 +74:40:32.3
05:14:12.34 +72:16:58.9
04:30:28.21 +69:08:35.9
04:28:21.52 +72:11:46.4
04:37:22.19 +66:31:19.3
04:34:41.05 +70:19:42.8
04:16:54.05 +69:09:51.0
04:35:52.53 +69:27:56.0
04:30:14.89 +71:07:48.9
04:40:34.86 +71:13:47.9
04:23:06.35 +72:23:28.0
04:58:04.76 +72:55:04.3
04:30:33.28 +74:11:32.1
05:00:15.82 +74:37:03.0
04:03:06.95 +70:22:53.1
04:23:06.35 +72:23:42.4
05:31:32.95 +74:01:49.9
05:01:20.64 +74:30:59.5
04:43:49.69 +68:38:10.0
06:02:56.05 +73:35:30.0
05:52:55.42 +72:46:31.4
03:45:21.07 +72:51:12.2
05:07:07.88 +70:13:29.6
05:20:05.30 +66:50:10.0
05:04:58.17 +73:00:40.3
04:54:46.26 +71:42:29.0
04:44:54.83 +69:53:39.7
04:47:02.55 +70:33:33.5
04:41:18.27 +68:47:19.7
05:14:27.00 +73:31:48.6
04:55:28.22 +70:15:54.5
04:57:37.58 +68:06:01.5
05:18:57.21 +64:31:49.8
########### 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:26:16.32 +74:20:43.2
05:04:34.42 +66:26:47.3
04:50:07.76 +69:35:08.4
05:13:17.42 +70:54:04.1
05:35:43.79 +68:28:57.0
05:22:53.87 +73:35:08.5
04:14:05.11 +68:04:60.0
04:40:16.27 +74:32:37.3
05:14:14.20 +70:50:34.8
04:16:59.67 +66:56:28.5
04:43:21.72 +72:02:37.0
04:46:16.11 +72:37:50.1
03:41:24.40 +73:57:21.6
04:50:48.22 +67:32:44.0
04:34:24.70 +65:49:46.9
03:50:36.12 +72:48:42.1
04:26:16.28 +74:20:51.7
04:59:22.32 +70:27:55.9
04:17:15.64 +66:58:59.2
05:23:35.43 +72:15:26.2
05:27:57.70 +73:37:35.6
04:48:25.67 +74:26:35.1
03:12:40.99 +71:11:14.2
03:25:33.72 +73:13:23.7
03:30:41.90 +73:56:35.3
04:23:00.02 +72:23:27.4
04:54:54.10 +71:07:57.0
05:28:24.41 +72:20:46.6
03:29:06.55 +72:34:20.2
04:26:59.49 +67:44:51.3
05:25:26.50 +70:14:45.7
05:03:23.89 +68:22:01.8
04:51:08.27 +68:10:40.6
04:49:57.45 +72:52:60.0
03:44:46.83 +74:36:13.1
04:55:59.89 +72:50:45.4
04:46:00.44 +67:30:45.3
04:22:57.14 +73:36:29.5
04:32:04.39 +69:05:49.2
04:38:22.26 +74:17:13.8
03:38:39.76 +65:56:54.5
04:24:04.42 +68:14:41.6
05:54:46.99 +73:10:60.0
03:49:46.30 +74:40:32.3
05:14:12.34 +72:16:58.9
04:30:28.21 +69:08:35.9
04:28:21.52 +72:11:46.4
04:37:22.19 +66:31:19.3
04:34:41.05 +70:19:42.8
04:16:54.05 +69:09:51.0
04:35:52.53 +69:27:56.0
04:30:14.89 +71:07:48.9
04:40:34.86 +71:13:47.9
04:23:06.35 +72:23:28.0
04:58:04.76 +72:55:04.3
04:30:33.28 +74:11:32.1
05:00:15.82 +74:37:03.0
04:03:06.95 +70:22:53.1
04:23:06.35 +72:23:42.4
05:31:32.95 +74:01:49.9
05:01:20.64 +74:30:59.5
04:43:49.69 +68:38:10.0
06:02:56.05 +73:35:30.0
05:52:55.42 +72:46:31.4
03:45:21.07 +72:51:12.2
05:07:07.88 +70:13:29.6
05:20:05.30 +66:50:10.0
05:04:58.17 +73:00:40.3
04:54:46.26 +71:42:29.0
04:44:54.83 +69:53:39.7
04:47:02.55 +70:33:33.5
04:41:18.27 +68:47:19.7
05:14:27.00 +73:31:48.6
04:55:28.22 +70:15:54.5
04:57:37.58 +68:06:01.5
05:18:57.21 +64:31:49.8
###################################################################################
04:26:16.32 +74:20:43.2 -- not an asteroid (will add it to exclusion list)
05:04:34.42 +66:26:47.3 -- not an asteroid (will add it to exclusion list)
04:50:07.76 +69:35:08.4 -- not an asteroid (will add it to exclusion list)
05:13:17.42 +70:54:04.1 -- not an asteroid (will add it to exclusion list)
05:35:43.79 +68:28:57.0 -- not an asteroid (will add it to exclusion list)
05:22:53.87 +73:35:08.5 -- not an asteroid (will add it to exclusion list)
04:14:05.11 +68:04:60.0 -- not an asteroid (will add it to exclusion list)
04:40:16.27 +74:32:37.3 -- not an asteroid (will add it to exclusion list)
05:14:14.20 +70:50:34.8 -- not an asteroid (will add it to exclusion list)
04:16:59.67 +66:56:28.5 -- not an asteroid (will add it to exclusion list)
04:43:21.72 +72:02:37.0 -- not an asteroid (will add it to exclusion list)
04:46:16.11 +72:37:50.1 -- not an asteroid (will add it to exclusion list)
03:41:24.40 +73:57:21.6 -- not an asteroid (will add it to exclusion list)
04:50:48.22 +67:32:44.0 -- not an asteroid (will add it to exclusion list)
04:34:24.70 +65:49:46.9 -- not an asteroid (will add it to exclusion list)
03:50:36.12 +72:48:42.1 -- not an asteroid (will add it to exclusion list)
04:26:16.28 +74:20:51.7 -- not an asteroid (will add it to exclusion list)
04:59:22.32 +70:27:55.9 -- not an asteroid (will add it to exclusion list)
04:17:15.64 +66:58:59.2 -- not an asteroid (will add it to exclusion list)
05:23:35.43 +72:15:26.2 -- not an asteroid (will add it to exclusion list)
05:27:57.70 +73:37:35.6 -- not an asteroid (will add it to exclusion list)
04:48:25.67 +74:26:35.1 -- not an asteroid (will add it to exclusion list)
03:12:40.99 +71:11:14.2 -- not an asteroid (will add it to exclusion list)
03:25:33.72 +73:13:23.7 -- not an asteroid (will add it to exclusion list)
03:30:41.90 +73:56:35.3 -- not an asteroid (will add it to exclusion list)
04:23:00.02 +72:23:27.4 -- not an asteroid (will add it to exclusion list)
04:54:54.10 +71:07:57.0 -- not an asteroid (will add it to exclusion list)
05:28:24.41 +72:20:46.6 -- not an asteroid (will add it to exclusion list)
03:29:06.55 +72:34:20.2 -- not an asteroid (will add it to exclusion list)
04:26:59.49 +67:44:51.3 -- not an asteroid (will add it to exclusion list)
05:25:26.50 +70:14:45.7 -- not an asteroid (will add it to exclusion list)
05:03:23.89 +68:22:01.8 -- not an asteroid (will add it to exclusion list)
04:51:08.27 +68:10:40.6 -- not an asteroid (will add it to exclusion list)
04:49:57.45 +72:52:60.0 -- not an asteroid (will add it to exclusion list)
03:44:46.83 +74:36:13.1 -- not an asteroid (will add it to exclusion list)
04:55:59.89 +72:50:45.4 -- not an asteroid (will add it to exclusion list)
04:46:00.44 +67:30:45.3 -- not an asteroid (will add it to exclusion list)
04:22:57.14 +73:36:29.5 -- not an asteroid (will add it to exclusion list)
04:32:04.39 +69:05:49.2 -- not an asteroid (will add it to exclusion list)
04:38:22.26 +74:17:13.8 -- not an asteroid (will add it to exclusion list)
03:38:39.76 +65:56:54.5 -- not an asteroid (will add it to exclusion list)
04:24:04.42 +68:14:41.6 -- not an asteroid (will add it to exclusion list)
05:54:46.99 +73:10:60.0 -- not an asteroid (will add it to exclusion list)
03:49:46.30 +74:40:32.3 -- not an asteroid (will add it to exclusion list)
05:14:12.34 +72:16:58.9 -- not an asteroid (will add it to exclusion list)
04:30:28.21 +69:08:35.9 -- not an asteroid (will add it to exclusion list)
04:28:21.52 +72:11:46.4 -- not an asteroid (will add it to exclusion list)
04:37:22.19 +66:31:19.3 -- not an asteroid (will add it to exclusion list)
04:34:41.05 +70:19:42.8 -- not an asteroid (will add it to exclusion list)
04:16:54.05 +69:09:51.0 -- not an asteroid (will add it to exclusion list)
04:35:52.53 +69:27:56.0 -- not an asteroid (will add it to exclusion list)
04:30:14.89 +71:07:48.9 -- not an asteroid (will add it to exclusion list)
04:40:34.86 +71:13:47.9 -- not an asteroid (will add it to exclusion list)
04:23:06.35 +72:23:28.0 -- not an asteroid (will add it to exclusion list)
04:58:04.76 +72:55:04.3 -- not an asteroid (will add it to exclusion list)
04:30:33.28 +74:11:32.1 -- not an asteroid (will add it to exclusion list)
05:00:15.82 +74:37:03.0 -- not an asteroid (will add it to exclusion list)
04:03:06.95 +70:22:53.1 -- not an asteroid (will add it to exclusion list)
04:23:06.35 +72:23:42.4 -- not an asteroid (will add it to exclusion list)
05:31:32.95 +74:01:49.9 -- not an asteroid (will add it to exclusion list)
05:01:20.64 +74:30:59.5 -- not an asteroid (will add it to exclusion list)
04:43:49.69 +68:38:10.0 -- not an asteroid (will add it to exclusion list)
06:02:56.05 +73:35:30.0 -- not an asteroid (will add it to exclusion list)
05:52:55.42 +72:46:31.4 -- not an asteroid (will add it to exclusion list)
03:45:21.07 +72:51:12.2 -- not an asteroid (will add it to exclusion list)
05:07:07.88 +70:13:29.6 -- not an asteroid (will add it to exclusion list)
05:20:05.30 +66:50:10.0 -- not an asteroid (will add it to exclusion list)
05:04:58.17 +73:00:40.3 -- not an asteroid (will add it to exclusion list)
04:54:46.26 +71:42:29.0 -- not an asteroid (will add it to exclusion list)
04:44:54.83 +69:53:39.7 -- not an asteroid (will add it to exclusion list)
04:47:02.55 +70:33:33.5 -- not an asteroid (will add it to exclusion list)
04:41:18.27 +68:47:19.7 -- not an asteroid (will add it to exclusion list)
05:14:27.00 +73:31:48.6 -- not an asteroid (will add it to exclusion list)
04:55:28.22 +70:15:54.5 -- not an asteroid (will add it to exclusion list)
04:57:37.58 +68:06:01.5 -- not an asteroid (will add it to exclusion list)
05:18:57.21 +64:31:49.8 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
03:12:40.99 +71:11:14.2 -- does not seem to be a hot pixel (will add it to exclusion list)
03:25:33.72 +73:13:23.7 -- does not seem to be a hot pixel (will add it to exclusion list)
03:29:06.55 +72:34:20.2 -- does not seem to be a hot pixel (will add it to exclusion list)
03:30:41.90 +73:56:35.3 -- does not seem to be a hot pixel (will add it to exclusion list)
03:38:39.76 +65:56:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
03:41:24.40 +73:57:21.6 -- does not seem to be a hot pixel (will add it to exclusion list)
03:44:46.83 +74:36:13.1 -- does not seem to be a hot pixel (will add it to exclusion list)
03:45:21.07 +72:51:12.2 -- does not seem to be a hot pixel (will add it to exclusion list)
03:49:46.30 +74:40:32.3 -- does not seem to be a hot pixel (will add it to exclusion list)
03:50:36.12 +72:48:42.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:03:06.95 +70:22:53.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:14:05.11 +68:04:60.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:16:54.05 +69:09:51.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:16:59.67 +66:56:28.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:17:15.64 +66:58:59.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:22:57.14 +73:36:29.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:23:00.02 +72:23:27.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:23:06.35 +72:23:28.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:23:06.35 +72:23:42.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:24:04.42 +68:14:41.6 -- does not seem to be a hot pixel (will add it to exclusion list)
04:26:16.28 +74:20:51.7 -- does not seem to be a hot pixel (will add it to exclusion list)
04:26:16.32 +74:20:43.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:26:59.49 +67:44:51.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:28:21.52 +72:11:46.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:30:14.89 +71:07:48.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:30:28.21 +69:08:35.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:30:33.28 +74:11:32.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:32:04.39 +69:05:49.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:34:24.70 +65:49:46.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:34:41.05 +70:19:42.8 -- does not seem to be a hot pixel (will add it to exclusion list)
04:35:52.53 +69:27:56.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:37:22.19 +66:31:19.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:38:22.26 +74:17:13.8 -- does not seem to be a hot pixel (will add it to exclusion list)
04:40:16.27 +74:32:37.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:40:34.86 +71:13:47.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:41:18.27 +68:47:19.7 -- does not seem to be a hot pixel (will add it to exclusion list)
04:43:21.72 +72:02:37.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:43:49.69 +68:38:10.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:44:54.83 +69:53:39.7 -- does not seem to be a hot pixel (will add it to exclusion list)
04:46:00.44 +67:30:45.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:46:16.11 +72:37:50.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:47:02.55 +70:33:33.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:48:25.67 +74:26:35.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:49:57.45 +72:52:60.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:50:07.76 +69:35:08.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:50:48.22 +67:32:44.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:51:08.27 +68:10:40.6 -- does not seem to be a hot pixel (will add it to exclusion list)
04:54:46.26 +71:42:29.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:54:54.10 +71:07:57.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:55:28.22 +70:15:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:55:59.89 +72:50:45.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:57:37.58 +68:06:01.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:58:04.76 +72:55:04.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:59:22.32 +70:27:55.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:00:15.82 +74:37:03.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:01:20.64 +74:30:59.5 -- does not seem to be a hot pixel (will add it to exclusion list)
05:03:23.89 +68:22:01.8 -- does not seem to be a hot pixel (will add it to exclusion list)
05:04:34.42 +66:26:47.3 -- does not seem to be a hot pixel (will add it to exclusion list)
05:04:58.17 +73:00:40.3 -- does not seem to be a hot pixel (will add it to exclusion list)
05:07:07.88 +70:13:29.6 -- does not seem to be a hot pixel (will add it to exclusion list)
05:13:17.42 +70:54:04.1 -- does not seem to be a hot pixel (will add it to exclusion list)
05:14:12.34 +72:16:58.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:14:14.20 +70:50:34.8 -- does not seem to be a hot pixel (will add it to exclusion list)
05:14:27.00 +73:31:48.6 -- does not seem to be a hot pixel (will add it to exclusion list)
05:18:57.21 +64:31:49.8 -- does not seem to be a hot pixel (will add it to exclusion list)
05:20:05.30 +66:50:10.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:22:53.87 +73:35:08.5 -- does not seem to be a hot pixel (will add it to exclusion list)
05:23:35.43 +72:15:26.2 -- does not seem to be a hot pixel (will add it to exclusion list)
05:25:26.50 +70:14:45.7 -- does not seem to be a hot pixel (will add it to exclusion list)
05:27:57.70 +73:37:35.6 -- does not seem to be a hot pixel (will add it to exclusion list)
05:28:24.41 +72:20:46.6 -- does not seem to be a hot pixel (will add it to exclusion list)
05:31:32.95 +74:01:49.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:35:43.79 +68:28:57.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:52:55.42 +72:46:31.4 -- does not seem to be a hot pixel (will add it to exclusion list)
05:54:46.99 +73:10:60.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:02:56.05 +73:35:30.0 -- 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:12:40.99 +71:11:14.2 -- not a known variable star
03:25:33.72 +73:13:23.7 -- not a known variable star
03:29:06.55 +72:34:20.2 -- not a known variable star
03:30:41.90 +73:56:35.3 -- not a known variable star
03:38:39.76 +65:56:54.5 -- not a known variable star
03:41:24.40 +73:57:21.6 -- not a known variable star
03:44:46.83 +74:36:13.1 -- not a known variable star
03:45:21.07 +72:51:12.2 -- not a known variable star
03:49:46.30 +74:40:32.3 -- not a known variable star
03:50:36.12 +72:48:42.1 -- not a known variable star
04:03:06.95 +70:22:53.1 -- not a known variable star
04:14:05.11 +68:04:60.0 -- not a known variable star
04:16:54.05 +69:09:51.0 -- not a known variable star
04:16:59.67 +66:56:28.5 -- not a known variable star
04:17:15.64 +66:58:59.2 -- not a known variable star
04:22:57.14 +73:36:29.5 -- not a known variable star
04:23:00.02 +72:23:27.4 -- not a known variable star
04:23:06.35 +72:23:28.0 -- not a known variable star
04:23:06.35 +72:23:42.4 -- not a known variable star
04:24:04.42 +68:14:41.6 -- not a known variable star
04:26:16.28 +74:20:51.7 -- not a known variable star
04:26:16.32 +74:20:43.2 -- not a known variable star
04:26:59.49 +67:44:51.3 -- a known variable star
04:28:21.52 +72:11:46.4 -- not a known variable star
04:30:14.89 +71:07:48.9 -- not a known variable star
04:30:28.21 +69:08:35.9 -- not a known variable star
04:30:33.28 +74:11:32.1 -- not a known variable star
04:32:04.39 +69:05:49.2 -- not a known variable star
04:34:24.70 +65:49:46.9 -- not a known variable star
04:34:41.05 +70:19:42.8 -- not a known variable star
04:35:52.53 +69:27:56.0 -- not a known variable star
04:37:22.19 +66:31:19.3 -- not a known variable star
04:38:22.26 +74:17:13.8 -- not a known variable star
04:40:16.27 +74:32:37.3 -- not a known variable star
04:40:34.86 +71:13:47.9 -- not a known variable star
04:41:18.27 +68:47:19.7 -- not a known variable star
04:43:21.72 +72:02:37.0 -- not a known variable star
04:43:49.69 +68:38:10.0 -- not a known variable star
04:44:54.83 +69:53:39.7 -- not a known variable star
04:46:00.44 +67:30:45.3 -- not a known variable star
04:46:16.11 +72:37:50.1 -- not a known variable star
04:47:02.55 +70:33:33.5 -- not a known variable star
04:48:25.67 +74:26:35.1 -- not a known variable star
04:49:57.45 +72:52:60.0 -- not a known variable star
04:50:07.76 +69:35:08.4 -- not a known variable star
04:50:48.22 +67:32:44.0 -- not a known variable star
04:51:08.27 +68:10:40.6 -- not a known variable star
04:54:46.26 +71:42:29.0 -- not a known variable star
04:54:54.10 +71:07:57.0 -- not a known variable star
04:55:28.22 +70:15:54.5 -- not a known variable star
04:55:59.89 +72:50:45.4 -- not a known variable star
04:57:37.58 +68:06:01.5 -- not a known variable star
04:58:04.76 +72:55:04.3 -- not a known variable star
04:59:22.32 +70:27:55.9 -- not a known variable star
05:00:15.82 +74:37:03.0 -- not a known variable star
05:01:20.64 +74:30:59.5 -- not a known variable star
05:03:23.89 +68:22:01.8 -- not a known variable star
05:04:34.42 +66:26:47.3 -- not a known variable star
05:04:58.17 +73:00:40.3 -- a known variable star
05:07:07.88 +70:13:29.6 -- not a known variable star
05:13:17.42 +70:54:04.1 -- not a known variable star
05:14:12.34 +72:16:58.9 -- not a known variable star
05:14:14.20 +70:50:34.8 -- not a known variable star
05:14:27.00 +73:31:48.6 -- not a known variable star
05:18:57.21 +64:31:49.8 -- not a known variable star
05:20:05.30 +66:50:10.0 -- not a known variable star
05:22:53.87 +73:35:08.5 -- not a known variable star
05:23:35.43 +72:15:26.2 -- not a known variable star
05:25:26.50 +70:14:45.7 -- not a known variable star
05:27:57.70 +73:37:35.6 -- not a known variable star
05:28:24.41 +72:20:46.6 -- not a known variable star
05:31:32.95 +74:01:49.9 -- not a known variable star
05:35:43.79 +68:28:57.0 -- not a known variable star
05:52:55.42 +72:46:31.4 -- not a known variable star
05:54:46.99 +73:10:60.0 -- not a known variable star
06:02:56.05 +73:35:30.0 -- not a known variable star
Found 74 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
76 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 76 (excluding asteroids and hot pixels, 74 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)2461146.67715131 -observatory V36
00:08:13.25 -01:57:41.7 Mercury (0.0mag)
03:09:30.62 +17:55:26.6 Venus (-3.9mag)
00:18:20.67 +00:55:12.7 Mars (1.2mag)
07:12:42.65 +22:46:06.0 Jupiter (-2.1mag)
00:29:15.61 +00:49:28.4 Saturn (0.9mag)
03:47:44.05 +19:47:35.7 Uranus (5.8mag)
00:10:51.80 -00:15:13.5 Neptune (7.8mag)
20:33:45.74 -22:52:36.3 Pluto (14.5mag)
00:23:59.67 +04:57:23.5 Moon (-8.5mag)
-rw-r--r-- 1 apache apache 361 Apr 15 23:22 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461146.67715131:
07:12:45.59 +22:46:02.2 Io (5.8mag)
07:12:49.24 +22:45:54.4 Europa (5.9mag)
07:12:59.07 +22:45:27.5 Ganymede (5.4mag)
07:13:18.03 +22:44:53.4 Callisto (6.6mag)
07:16:02.42 +22:33:38.6 Himalia (15.3mag)
07:12:39.27 +22:46:12.2 Thebe (16.2mag)
07:16:14.04 +23:03:51.0 Elara (17.3mag)
07:11:36.26 +23:26:00.8 Pasiphae (17.4mag)
07:21:02.12 +22:44:08.3 Carme (18.5mag)
00:29:15.90 +00:49:54.9 Titan (8.8mag)
00:29:14.42 +00:49:31.9 Rhea (10.1mag)
00:28:55.33 +00:49:36.1 Iapetus (11.5mag)
00:29:23.30 +00:49:48.8 Hyperion (14.8mag)
00:30:52.37 +00:58:15.4 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 15 23:22 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461146.67715131:
15:39:13.87 -16:23:03.6 JWST
14:00:56.84 +55:54:59.6 Chandra
08:00:22.84 -38:23:40.7 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 15 23:22 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461146.67715131 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:52:04.58 -28:47:21.6 13.9mag P/2010 H2 (Vales)
05:06:51.69 -69:39:12.5 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:32:29.05 +31:26:18.9 17.2mag C/2017 K2 (PANSTARRS)
17:30:25.13 +10:34:07.2 17.6mag C/2021 G2 (ATLAS)
23:10:16.28 +29:14:09.1 17.1mag C/2022 E2 (ATLAS)
04:29:26.54 +26:02:35.6 16.0mag C/2022 N2 (PANSTARRS)
09:03:27.47 +32:01:07.5 16.2mag C/2022 QE78 (ATLAS)
08:31:06.00 -00:08:03.7 17.3mag C/2022 R6 (PANSTARRS)
18:53:41.40 +18:32:50.2 17.6mag C/2023 A3 (Tsuchinshan-ATLAS)
15:40:37.06 -11:31:08.5 17.5mag P/2023 B1 (PANSTARRS)
09:07:33.20 -11:51:17.3 17.6mag C/2023 F3 (ATLAS)
21:54:23.62 +62:54:59.9 17.5mag C/2023 H5 (Lemmon)
19:19:02.83 -03:44:07.5 14.1mag C/2023 R1 (PANSTARRS)
21:32:11.32 +85:56:09.2 17.8mag C/2023 X2 (Lemmon)
06:17:58.74 +63:30:43.9 17.2mag C/2024 A1 (ATLAS)
05:13:39.30 +18:22:01.8 11.1mag C/2024 E1 (Wierzchos)
16:19:09.78 +06:25:10.2 17.4mag C/2024 G6 (ATLAS)
20:20:51.71 +15:19:20.7 14.6mag C/2024 J3 (ATLAS)
03:26:31.62 -22:21:30.8 16.3mag C/2024 T5 (ATLAS)
05:16:51.72 +45:14:49.5 17.7mag C/2025 J1 (Borisov)
13:38:06.00 +45:36:21.6 15.2mag C/2025 L1 (ATLAS)
03:25:33.26 -26:14:21.5 17.8mag C/2025 Q3 (ATLAS)
23:44:59.14 +18:33:06.5 8.5mag C/2025 R3 (PANSTARRS)
12:54:02.50 +03:01:24.8 17.4mag C/2025 Y1 (ATLAS)
03:29:23.10 +02:36:04.1 13.4mag C/2026 A1 (MAPS)
00:00:04.96 +37:15:07.2 14.6mag C/2026 B2 (Sun-Gao)
18:43:16.87 -09:42:34.6 11.8mag 10P/Tempel
15:00:04.10 +03:11:27.4 14.0mag 24P/Schaumasse
11:02:45.30 -01:31:13.7 15.7mag 29P/Schwassmann-Wachmann
18:01:00.91 -09:36:13.0 17.9mag 40P/Vaisala
10:37:33.42 -04:05:05.3 16.9mag 43P/Wolf-Harrington
01:48:56.84 +17:31:04.1 17.2mag 47P/Ashbrook-Jackson
07:11:05.39 +36:58:29.4 17.0mag 63P/Wild
23:29:16.99 -11:25:46.4 15.7mag 65P/Gunn
04:03:43.28 +21:18:57.5 15.9mag 76P/West-Kohoutek-Ikemura
01:05:57.96 +08:15:48.6 14.3mag 78P/Gehrels
23:03:32.40 -09:20:19.4 14.6mag 88P/Howell
02:10:54.04 +20:41:22.5 15.1mag 93P/Lovas
04:55:08.17 +32:17:50.1 16.2mag 123P/West-Hartley
08:28:34.15 +38:16:46.3 16.2mag 124P/Mrkos
02:33:29.33 +14:23:23.1 16.4mag 128P/Shoemaker-Holt
02:47:53.05 +14:30:53.4 17.5mag 131P/Mueller
01:27:05.70 +13:17:59.1 10.6mag 141P/Machholz
01:35:59.98 +04:56:25.0 10.6mag 141P-A/Machholz
00:21:12.57 +00:50:35.2 12.8mag 141P-D/Machholz
02:06:20.58 +06:41:57.9 17.8mag 141P-I/Machholz
01:02:52.32 -01:26:12.0 15.1mag 162P/SidingSpring
14:51:07.20 -00:02:58.9 17.7mag 210P/Christensen
21:39:21.59 -11:24:21.0 17.6mag 218P/LINEAR
17:16:36.79 -13:54:43.0 16.1mag 235P/LINEAR
05:34:51.83 +34:42:44.5 16.8mag 240P/NEAT
07:38:34.82 -05:08:52.7 17.7mag 242P/Spahr
22:17:21.09 -20:55:58.3 17.9mag 260P/McNaught
01:58:33.01 +20:30:18.8 18.0mag 295P/LINEAR
15:42:34.66 +07:00:08.0 17.5mag 391P/Kowalski
07:34:15.80 +21:21:59.8 17.7mag 450P/LONEOS
05:36:07.70 +45:01:20.4 17.5mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.9K Apr 15 23:22 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
15:25:54.99 +07:49:24.50 2026-04-12.14 16.96
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
04:55:50.66 -29:52:57.70 SN 2026dpg 2026-02-23.11 15.75
04:21:28.18 -53:22:54.40 AT2026drl 2026-02-21.03 17.31
-rw-r--r-- 1 apache apache 5.8K Apr 15 23:22 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 15 23:22 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
15:52:32.558 +54:28:28.21 AT 2026iyo 2026-04-07.50 19.8736
12:10:51.131 -15:24:05.80 AT 2026iyn 2026-04-07.49 19.8
10:03:32.464 +00:47:38.92 AT 2026iym 2026-04-09.07 21.7842
09:57:46.577 +02:32:54.17 AT 2026iyl 2026-04-09.07 21.1159
12:09:21.288 -14:20:40.69 AT 2026iyk 2026-02-24.42 19.0617
11:32:15.323 +26:34:23.97 AT 2026iyi 2026-04-07.27 20.0038
08:41:36.643 +41:14:51.53 AT 2026iyh 2026-03-18.28 20.5874
11:10:47.748 -02:27:00.61 AT 2026iyg 2026-04-07.26 20.12
11:41:25.329 -11:32:16.55 AT 2026iyf 2026-04-07.25 20.8489
09:58:35.594 -17:44:37.57 AT 2026iye 2026-04-08.19 19.4848
07:48:08.582 +43:35:35.35 AT 2026iyd 2026-04-05.16 19.8382
11:13:43.729 +21:50:31.84 AT 2026iyc 2026-04-05.18 20.0005
08:02:45.458 +40:40:22.73 AT 2026iyb 2026-03-26.18 20.4831
13:05:52.496 +64:22:32.75 AT 2026iya 2026-03-08.94 19.29
05:15:26.423 -02:54:24.54 AT 2026ixz 2026-04-08.14 19.1905
14:04:24.118 +43:40:15.80 AT 2026ixt 2026-04-08.93 19.74
13:12:41.279 +38:05:24.08 AT 2026ixs 2026-04-08.93 20.18
13:21:56.843 -04:01:33.33 AT 2026ixr 2026-04-08.90 19.48
12:04:52.343 +69:44:57.80 AT 2026ixq 2026-04-08.89 19.03
21:31:46.671 +04:33:36.35 AT 2026ixp 2026-04-08.51 19.1697
-rw-r--r-- 1 apache apache 30K Apr 15 23:22 tns_transients_list.txt
