This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg
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!
TCP 2026 04 18.4563* 00 11 24.87 +46 51 12.8 12.9 U And 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,2461148.9563,12.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 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!
TCP 2026 04 18.4563* 00 10 08.63 +45 52 00.3 12.5 U And 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,2461148.9563,12.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 12 40.99 +46 39 28.1 12.7 U And 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 392190403148782080,2461148.9563,12.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 392190403148782080 20260418.4563 12.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
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 18.4563* 00 25 37.73 +48 33 21.9 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461148.9563,12.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 05 20.93 +47 50 54.3 12.5 U And 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,2461148.9563,12.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 01 35.05 +47 32 39.6 12.6 U And 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,2461148.9563,12.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 03 45.22 +44 29 26.6 12.3 U And 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 384982971287011712,2461148.9563,12.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 384982971287011712 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 08 19.61 +48 21 08.9 12.5 U And 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,2461148.9563,12.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 25 17.32 +49 51 09.6 12.3 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,2461148.9563,12.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 20 35.20 +47 35 36.6 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461148.9563,12.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 21 26.11 +48 58 01.3 12.3 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,2461148.9563,12.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 10 14.24 +46 24 55.5 12.2 U And 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,2461148.9563,12.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 08 32.63 +48 53 27.3 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 393586684135798144,2461148.9563,12.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 393586684135798144 20260418.4563 12.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!
TCP 2026 04 18.4563* 23 57 33.59 +46 30 48.3 12.3 U And 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 1927172995611509888,2461148.9563,12.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 1927172995611509888 20260418.4563 12.35CV 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 18.4563* 00 05 00.96 +46 35 39.7 12.1 U And 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 387078155117309312,2461148.9563,12.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 387078155117309312 20260418.4563 12.06CV 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 18.4563* 00 07 21.22 +46 36 34.0 11.4 U And 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 386979306446031232,2461148.9563,11.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386979306446031232 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 14 41.71 +46 51 19.5 11.2 U And 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 392207548658221312,2461148.9563,11.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 392207548658221312 20260418.4563 11.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 00 20.39 +46 04 22.7 11.2 U And 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 386710475852391424,2461148.9563,11.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386710475852391424 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 24 36.39 +49 04 57.9 11.0 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
ATO J006.1513+49.0829,2461148.9563,11.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J006.1513+49.0829 20260418.4563 11.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 13 20.82 +46 36 35.3 11.0 U And 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 392186726656777984,2461148.9563,11.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 392186726656777984 20260418.4563 11.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 23 57 30.26 +48 17 25.7 9.4 U And 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 1939610705511944064,2461148.9563,9.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 1939610705511944064 20260418.4563 9.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!
TCP 2026 04 18.4563* 00 06 33.47 +46 28 40.6 10.3 U And 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
ATO J001.6565+46.4844,2461148.9563,10.34,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.6565+46.4844 20260418.4563 10.34CV 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 18.4563* 00 15 03.85 +47 15 03.8 10.4 U And 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 392315957930666368,2461148.9563,10.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 392315957930666368 20260418.4563 10.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!
TCP 2026 04 18.4563* 00 07 52.19 +44 04 41.8 10.4 U And 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 386261080537712256,2461148.9563,10.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386261080537712256 20260418.4563 10.41CV 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 18.4563* 00 08 05.16 +44 53 35.4 10.5 U And 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
ATO J002.0227+44.8830,2461148.9563,10.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J002.0227+44.8830 20260418.4563 10.51CV 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 18.4563* 00 08 13.04 +46 04 33.8 10.5 U And 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
ATO J002.0549+46.0761,2461148.9563,10.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J002.0549+46.0761 20260418.4563 10.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 23 19.95 +46 33 51.8 10.6 U And 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,2461148.9563,10.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 10.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!
TCP 2026 04 18.4563* 23 55 47.98 +45 06 40.6 10.8 U And 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 1926090831354818816,2461148.9563,10.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 1926090831354818816 20260418.4563 10.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 18.4563* 00 15 45.24 +45 30 22.4 11.0 U And 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,2461148.9563,10.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 10.99CV 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 18.4563* 00 21 03.53 +47 36 14.3 11.0 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
ATO J005.2708+47.6044,2461148.9563,11.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J005.2708+47.6044 20260418.4563 11.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 10 16.65 +49 00 01.1 11.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 393561876404915840,2461148.9563,11.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 393561876404915840 20260418.4563 11.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 16 05.47 +46 59 36.8 11.2 U And 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,2461148.9563,11.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 11.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 02 09.49 +42 08 07.7 11.2 U And 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,2461148.9563,11.22,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 11.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!
TCP 2026 04 18.4563* 23 57 14.32 +45 56 54.3 11.2 U And 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 1926384370896570112,2461148.9563,11.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 1926384370896570112 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 24 07.51 +46 17 08.3 11.4 U And 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 391990639928120576,2461148.9563,11.36,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 391990639928120576 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 04 30.34 +47 01 10.5 11.4 U And 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
ATO J001.1309+47.0170,2461148.9563,11.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.1309+47.0170 20260418.4563 11.40CV 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 18.4563* 00 01 42.12 +46 36 22.7 11.5 U And 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
ATO J000.4293+46.6268,2461148.9563,11.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J000.4293+46.6268 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 09 49.18 +46 02 02.8 11.5 U And 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 386814963817326080,2461148.9563,11.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386814963817326080 20260418.4563 11.51CV 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 18.4563* 00 09 56.12 +46 22 42.7 11.5 U And 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,2461148.9563,11.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 11.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 18.4563* 00 19 05.93 +50 00 27.8 11.5 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 394494537143489664,2461148.9563,11.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 394494537143489664 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 17 32.35 +50 15 56.4 11.6 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,2461148.9563,11.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 11.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 18.4563 2461148.9563 11.54 00:21:28.63 +44:22:14.6
117.30359 -18.17336 galactic And Second-epoch detections are separated by 3.4" and 4.0 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 | Gaia DR3 varaible 385684322267342080 | 00:21:29.43 +44:21:34.5 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F0 (LAMOST DR5)
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!
TCP 2026 04 18.4563* 00 21 28.63 +44 22 14.6 11.5 U And 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 varaible 385684322267342080,2461148.9563,11.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 varaible 385684322267342080 20260418.4563 11.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 06 55.76 +46 08 05.4 11.6 U And 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
ATO J001.7355+46.1348,2461148.9563,11.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.7355+46.1348 20260418.4563 11.63CV 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 18.4563* 00 25 12.52 +50 11 54.6 11.6 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 394656577666088960,2461148.9563,11.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 394656577666088960 20260418.4563 11.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 19 38.45 +46 30 12.3 11.7 U And 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 392043622644246144,2461148.9563,11.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 392043622644246144 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 00 57.14 +44 33 13.1 11.8 U And 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 385042035677008512,2461148.9563,11.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 385042035677008512 20260418.4563 11.76CV 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 18.4563 2461148.9563 11.72 00:11:06.67 +46:40:49.3
115.76797 -15.62968 galactic And Second-epoch detections are separated by 3.1" and 3.9 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 386939277351062016 | 00:11:09.30 +46:40:32.9 (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) SpType: G3 (LAMOST DR5)
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!
TCP 2026 04 18.4563* 00 11 06.67 +46 40 49.3 11.7 U And 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
Large-amplitude variable Gaia DR2 386939277351062016,2461148.9563,11.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386939277351062016 20260418.4563 11.72CV 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 18.4563* 00 20 27.45 +49 12 22.2 11.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,2461148.9563,11.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 11.81CV 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 18.4563* 00 17 19.23 +44 57 47.3 11.6 U And 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 385948235121614592,2461148.9563,11.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 385948235121614592 20260418.4563 11.63CV 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 18.4563* 00 08 29.52 +45 02 25.4 11.7 U And 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
ATO J002.1254+45.0329,2461148.9563,11.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J002.1254+45.0329 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 08 02.58 +46 30 04.5 11.8 U And 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 386966009227332096,2461148.9563,11.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386966009227332096 20260418.4563 11.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 07 09.68 +45 43 12.1 11.7 U And 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 386836266854962688,2461148.9563,11.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386836266854962688 20260418.4563 11.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!
TCP 2026 04 18.4563* 23 57 20.26 +48 06 22.4 11.9 U And 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
ATO J359.3365+48.1062,2461148.9563,11.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J359.3365+48.1062 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 01 22.12 +46 44 46.4 11.8 U And 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,2461148.9563,11.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 11.81CV 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 18.4563* 00 17 32.06 +45 44 43.0 12.0 U And 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
ATO J004.3678+45.7494,2461148.9563,12.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J004.3678+45.7494 20260418.4563 12.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 04 48.21 +44 03 44.9 11.9 U And 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 384959950262372224,2461148.9563,11.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 384959950262372224 20260418.4563 11.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 02 11.05 +50 19 52.0 11.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,2461148.9563,11.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 11.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 02 45.76 +47 14 34.9 12.0 U And 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,2461148.9563,11.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 11.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!
TCP 2026 04 18.4563* 23 54 57.17 +46 52 40.3 12.0 U And 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,2461148.9563,11.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 08 24.91 +44 57 39.8 11.9 U And 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,2461148.9563,11.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 23 45.50 +49 19 27.7 12.0 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
ATO J005.9595+49.3152,2461148.9563,11.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J005.9595+49.3152 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 03 11.15 +45 52 59.6 11.9 U And 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,2461148.9563,11.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 11.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!
TCP 2026 04 18.4563* 00 16 37.01 +47 13 48.2 12.0 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 392266028933381632,2461148.9563,11.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 392266028933381632 20260418.4563 11.99CV 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 18.4563* 00 21 25.94 +44 22 23.3 12.1 U And 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 385687272908324224,2461148.9563,12.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 385687272908324224 20260418.4563 12.06CV 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 18.4563* 00 12 06.06 +45 51 25.4 12.0 U And 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 386887600305868544,2461148.9563,12.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386887600305868544 20260418.4563 12.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 23 58 26.70 +48 35 39.7 12.1 U And 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 1939636440956849280,2461148.9563,12.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 1939636440956849280 20260418.4563 12.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 18.4563 2461148.9563 12.06 00:13:00.32 +46:48:05.2
116.12052 -15.56139 galactic And Second-epoch detections are separated by 3.7" and 3.9 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 392198069665570560 | 00:13:04.15 +46:47:48.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) J-Ks=0.406+/-0.032 (G)
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!
TCP 2026 04 18.4563* 00 13 00.32 +46 48 05.2 12.1 U And 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
Large-amplitude variable Gaia DR2 392198069665570560,2461148.9563,12.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 392198069665570560 20260418.4563 12.06CV 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 18.4563* 00 08 57.11 +44 53 11.7 12.1 U And 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,2461148.9563,12.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 09 08.00 +48 43 25.3 12.3 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 393575963897486592,2461148.9563,12.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 393575963897486592 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 25 11.59 +48 04 07.5 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461148.9563,12.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 04 20.53 +42 07 10.1 12.1 U And 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
ATO J001.0762+42.1094,2461148.9563,12.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.0762+42.1094 20260418.4563 12.07CV 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 18.4563* 00 12 23.06 +47 53 49.5 12.2 U And 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 393116054501831040,2461148.9563,12.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 393116054501831040 20260418.4563 12.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 03 55.81 +49 40 52.9 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J000.9825+49.6832,2461148.9563,12.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J000.9825+49.6832 20260418.4563 12.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!
TCP 2026 04 18.4563* 23 54 40.38 +44 53 46.8 12.1 U And 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,2461148.9563,12.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.06CV 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 18.4563* 00 15 00.49 +46 47 04.6 12.1 U And 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 392204112684387584,2461148.9563,12.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 392204112684387584 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 23 02.89 +44 30 13.1 12.1 U And 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
ATO J005.7626+44.5032,2461148.9563,12.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J005.7626+44.5032 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 16 04.90 +49 53 06.0 12.1 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 394455607559460096,2461148.9563,12.08,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 394455607559460096 20260418.4563 12.08CV 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 18.4563* 23 57 08.47 +45 57 30.6 12.2 U And 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,2461148.9563,12.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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!
TCP 2026 04 18.4563* 23 53 06.61 +47 04 44.3 12.0 U And 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 1927381627946681984,2461148.9563,12.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 1927381627946681984 20260418.4563 12.01CV 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 18.4563* 00 04 26.52 +43 37 19.1 12.2 U And 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
ATO J001.0991+43.6141,2461148.9563,12.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.0991+43.6141 20260418.4563 12.19CV 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 18.4563* 00 07 42.33 +42 42 09.8 12.1 U And 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,2461148.9563,12.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 09 49.98 +48 59 47.9 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461148.9563,12.22,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 15 49.07 +42 39 01.2 12.3 U And 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 varaible 383841437699267840,2461148.9563,12.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 varaible 383841437699267840 20260418.4563 12.28CV 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 18.4563* 00 14 41.39 +47 22 49.6 12.3 U And 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 392319874940806272,2461148.9563,12.30,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 392319874940806272 20260418.4563 12.30CV 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 18.4563* 23 50 36.75 +47 03 38.9 12.2 U And 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
ATO J357.6483+47.0604,2461148.9563,12.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J357.6483+47.0604 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 20 51.19 +44 52 26.9 12.3 U And 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 385841208832577664,2461148.9563,12.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 385841208832577664 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 19 15.89 +47 21 45.6 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J004.8141+47.3630,2461148.9563,12.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J004.8141+47.3630 20260418.4563 12.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 23 58 01.88 +43 43 14.5 12.2 U And 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,2461148.9563,12.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 07 10.71 +46 21 14.4 12.2 U And 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 386881896587567616,2461148.9563,12.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386881896587567616 20260418.4563 12.19CV 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 18.4563* 00 02 36.08 +44 57 42.9 12.5 U And 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,2461148.9563,12.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 13 16.71 +46 26 10.2 12.4 U And 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
ATO J003.3234+46.4484,2461148.9563,12.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J003.3234+46.4484 20260418.4563 12.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 15 39.99 +45 53 22.7 12.4 U And 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,2461148.9563,12.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 22 42.08 +48 01 05.1 12.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
ATO J005.6779+48.0160,2461148.9563,12.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J005.6779+48.0160 20260418.4563 12.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 13 02.71 +48 43 54.5 12.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,2461148.9563,12.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.40CV 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 18.4563* 00 14 28.18 +46 03 16.6 12.3 U And 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 386155669157825152,2461148.9563,12.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386155669157825152 20260418.4563 12.28CV 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 18.4563* 00 20 30.77 +44 02 49.7 12.4 U And 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 varaible 385700024667835264,2461148.9563,12.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 varaible 385700024667835264 20260418.4563 12.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 18.4563* 23 59 29.66 +44 37 14.6 12.3 U And 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
ZTF J235929.46+443702.6,2461148.9563,12.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 J235929.46+443702.6 20260418.4563 12.29CV 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 18.4563* 00 17 08.10 +48 28 49.1 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 392817880693512576,2461148.9563,12.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 392817880693512576 20260418.4563 12.65CV 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 18.4563* 23 57 30.30 +48 02 02.1 12.5 U And 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
ATO J359.3855+48.0280,2461148.9563,12.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J359.3855+48.0280 20260418.4563 12.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 18.4563* 00 22 21.14 +46 00 41.5 12.3 U And 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 391878867698721792,2461148.9563,12.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 391878867698721792 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 00 07.89 +49 01 30.6 12.3 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
VARIABLE_NAME,2461148.9563,12.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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
VARIABLE_NAME 20260418.4563 12.29CV 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 18.4563* 00 06 14.66 +45 18 19.7 12.4 U And 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 386429275754126720,2461148.9563,12.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386429275754126720 20260418.4563 12.40CV 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 18.4563* 00 14 11.52 +46 13 05.8 12.5 U And 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,2461148.9563,12.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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
Mean magnitude and position on the discovery images:
2026 04 18.4563 2461148.9563 12.53 00:21:09.50 +44:57:54.4
117.32101 -17.57650 galactic And Second-epoch detections are separated by 4.3" and 4.0 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 | Gaia DR3 varaible 385796541170538624 | 00:21:09.50 +44:57:54.4 (user input) | | 2022yCat.1358....0G | (position from user input) Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') J-Ks=1.274+/-0.225 (Very red! L if it's a dwarf)
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!
TCP 2026 04 18.4563* 00 21 09.50 +44 57 54.4 12.5 U And 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 varaible 385796541170538624,2461148.9563,12.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 varaible 385796541170538624 20260418.4563 12.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 03 56.39 +46 27 46.0 12.4 U And 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,2461148.9563,12.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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 18.4563* 00 03 25.73 +47 34 55.9 12.3 U And 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 387236519150100992,2461148.9563,12.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 387236519150100992 20260418.4563 12.35CV 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 18.4563* 00 00 56.64 +43 15 27.2 12.4 U And 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 384489973465493632,2461148.9563,12.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 384489973465493632 20260418.4563 12.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 23 52 56.17 +47 09 38.1 12.6 U And 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
WISE J235256.4+470939,2461148.9563,12.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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
WISE J235256.4+470939 20260418.4563 12.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 07 49.56 +50 03 09.3 12.5 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
ATO J001.9550+50.0576,2461148.9563,12.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.9550+50.0576 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 02 12.55 +45 57 35.9 12.3 U And 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 386716385727588736,2461148.9563,12.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386716385727588736 20260418.4563 12.35CV 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 18.4563* 00 18 47.16 +48 23 36.1 12.5 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,2461148.9563,12.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 18 37.52 +47 43 36.2 12.5 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,2461148.9563,12.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 25 26.62 +46 40 25.4 12.5 U And 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,2461148.9563,12.50,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.50CV 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 18.4563* 00 00 31.28 +45 22 44.4 12.5 U And 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 386593549662621440,2461148.9563,12.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386593549662621440 20260418.4563 12.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!
TCP 2026 04 18.4563* 23 53 37.02 +45 57 48.4 12.5 U And 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
ATO J358.3958+45.9656,2461148.9563,12.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J358.3958+45.9656 20260418.4563 12.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 18.4563* 00 07 25.11 +46 44 11.7 12.5 U And 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 386987552783198592,2461148.9563,12.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386987552783198592 20260418.4563 12.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 23 57 09.10 +42 48 45.3 12.6 U And 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 1921870081097207552,2461148.9563,12.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 1921870081097207552 20260418.4563 12.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 21 52.60 +48 24 47.2 12.6 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,2461148.9563,12.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 05 09.98 +45 32 20.7 12.8 U And 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 386645570306983424,2461148.9563,12.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 386645570306983424 20260418.4563 12.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 11 44.63 +47 49 55.5 12.8 U And 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 393096027071802368,2461148.9563,12.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 393096027071802368 20260418.4563 12.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 18 36.79 +46 21 23.5 12.6 U And 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,2461148.9563,12.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 12 35.71 +43 17 41.4 12.9 U And 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,2461148.9563,12.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 12.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 18.4563* 00 06 07.47 +47 45 17.2 13.1 U And 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,2461148.9563,13.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 13.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!
TCP 2026 04 18.4563* 00 11 26.81 +46 03 58.5 13.0 U And 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
2MASS J00112718+4603580,2461148.9563,12.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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
2MASS J00112718+4603580 20260418.4563 12.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!
TCP 2026 04 18.4563* 00 07 54.33 +46 16 37.9 13.1 U And 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,2461148.9563,13.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 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 20260418.4563 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461036.57699117 27.12.2025 01:50:42.037 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
First image: 2461036.57699117 27.12.2025 01:50:42.037 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Last image: 2461148.95654228 18.04.2026 10:57:15.253 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 4
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.88
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): 18402
Objects passed selection criteria: 18334
Measurements per detected object (mean, median, min, max): 2.8 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.8 2.0 2 4
Average stars detected per image: 13214.8
Average stars matched: 12134.5 (91.8254 %)
Memory usage VmPeak: 121816 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Apr 16 15:05:05 CDT 2026
VaST build number 1.0rc89-19-g55e4b97d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sat Apr 18 06:14:52 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: 2461036.57699117 27.12.2025 01:50:42.037 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
First image: 2461036.57699117 27.12.2025 01:50:42.037 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Last image: 2461148.95654228 18.04.2026 10:57:15.253 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 290
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.48
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: 55 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): 117002
Objects passed selection criteria: 116684
Measurements per detected object (mean, median, min, max): 2.9 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.9 2.0 2 4
Average stars detected per image: 90446.2
Average stars matched: 82869 (91.6224 %)
Memory usage VmPeak: 2007256 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Apr 16 15:05:05 CDT 2026
VaST build number 1.0rc89-19-g55e4b97d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sat Apr 18 06:17:06 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/TTUQ2b1x1/TTUQ2_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 4 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
SExtractor catalog cache: saved And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat to cache
SExtractor catalog cache: saved And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.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/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.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: 2461148.95597999
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_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits exists and is non-empty
Saving wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits to local_wcs_cache/
'wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits' -> 'local_wcs_cache/wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits'
wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits exists and is non-empty
Saving wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits to local_wcs_cache/
'wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits' -> 'local_wcs_cache/wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits'
wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits exists and is non-empty
Saving wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits to local_wcs_cache/
'wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits' -> 'local_wcs_cache/wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits'
wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits exists and is non-empty
Saving wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits to local_wcs_cache/
'wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits' -> 'local_wcs_cache/wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits (1st reference image)
verification OK: wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Image size: 924.9'x628.2' 15.4(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.80"/pix along the X axis and 5.90"/pix along the Y axis
Image center: 00:00:19.361 +45:58:07.34 J2000 4789.000 3195.000
###################################
The image scale is 5.80"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.8" and 8.7"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits (1st new image)
verification OK: wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
Image size: 917.5'x627.9' 15.3(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.75"/pix along the X axis and 5.90"/pix along the Y axis
Image center: 23:59:59.813 +46:02:45.18 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 00:00:19.361 +45:58:07.34
Second-epoch image center 23:59:59.813 +46:02:45.18
Angular distance between the image centers 0.0957 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits (2nd new image)
verification OK: wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
Image size: 938.9'x624.4' 15.6(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.88"/pix along the X axis and 5.86"/pix along the Y axis
Image center: 00:00:00.569 +46:03:08.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 00:00:19.361 +45:58:07.34
Second-epoch image center 00:00:00.569 +46:03:08.58
Angular distance between the image centers 0.0998 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 23:59:59.813 +46:02:45.18
Second-epoch second image center 00:00:00.569 +46:03:08.58
Angular distance between the image centers 0.00686 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/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits &> /tmp/tmp.4JSx7Yxmyx
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits &> /tmp/tmp.avfDBPQb49
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits &> /tmp/tmp.nkBubiPYGH
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits &> /tmp/tmp.NuQUGV53Gr
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
Calibrating the magnitude scale
Found non-empty wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.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_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.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_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
Found non-empty wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
The reference image (wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits) and catalog (wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat) found
'wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat' -> 'wcsmag.cat'
Read 21978 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0038 to 359.9998 deg, Dec +39.9518 to +51.2135 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 0.0038 to 359.9998 deg, Dec 39.9518 to 51.2135 deg
Loaded 169717 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): 58 out of 66 total matches.
Matched with Tycho-2 66 out of 21978 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.835338
a=0.000000 b=1.000000 c=22.835338
From vast_summary.log: estimated ref. image limiting mag.: -7.88
Updating vast_summary.log: Estimated ref. image limiting mag.: 14.96
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 14.96
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 3 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.5 pix And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
2.5 pix And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
2.6 pix fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
2.6 pix fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
Limiting magnitude estimates:
15.0 mag. And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
15.0 mag. And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
14.2 mag. fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
14.2 mag. fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
All-image limiting magnitude estimate: 14.2 (SNR ) 11.4 (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.4JSx7Yxmyx (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits' -> 'wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS_IMAGE_NAME=wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS-calibrated image found: wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Checking if the catalog wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits alredy exist and is non-empty...
Catalog wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS catalog name: wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2256, passed=21978
Got 21978 stars (including 19693 good ones) from the SExtractor catalog wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
util/solve_plate_with_UCAC5 got 21978 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.9'
Seting catalog search parameters based on the expected field of view 924.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012846 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010277 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4507 through 0 to 12.6948, gap 12.6948 to 348.4507
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.2)
Done reading UCAC5 zone files...
Matched 203 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 146 matched stars entering correct_measured_positions(), 68 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.79"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 141 matched stars entering correct_measured_positions(), 2320 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.33"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4573 through 0 to 12.6998, gap 12.6998 to 348.4573
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.2)
Done reading UCAC5 zone files...
Matched 230 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 175 matched stars entering correct_measured_positions(), 2338 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.32"
Accuracy estimation diagnostic: 173 matched stars entering correct_measured_positions(), 3009 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.42"
Excluding outliers - 173 stars left (next iteration limit 155)
The image catalog is written to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits -region wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.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.avfDBPQb49 (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits' -> 'wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS_IMAGE_NAME=wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS-calibrated image found: wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Checking if the catalog wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits alredy exist and is non-empty...
Catalog wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS catalog name: wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2250, passed=22050
Got 22050 stars (including 19777 good ones) from the SExtractor catalog wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat
util/solve_plate_with_UCAC5 got 22050 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.9'
Seting catalog search parameters based on the expected field of view 924.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012846 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010277 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4512 through 0 to 12.6947, gap 12.6947 to 348.4512
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.2)
Done reading UCAC5 zone files...
Matched 202 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 142 matched stars entering correct_measured_positions(), 69 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.99"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 135 matched stars entering correct_measured_positions(), 2248 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.05"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4583 through 0 to 12.7006, gap 12.7006 to 348.4583
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.2)
Done reading UCAC5 zone files...
Matched 223 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 175 matched stars entering correct_measured_positions(), 2273 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.04"
Accuracy estimation diagnostic: 172 matched stars entering correct_measured_positions(), 3100 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.65"
Excluding outliers - 172 stars left (next iteration limit 148)
The image catalog is written to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits -region wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.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.nkBubiPYGH (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
WCS_IMAGE_NAME=wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
WCS-calibrated image found: wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
Checking if the catalog wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits alredy exist and is non-empty...
Catalog wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
WCS catalog name: wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat
SExtractor catalog parsing summary: zero_flux=9, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=893, passed=12825
Got 12825 stars (including 11927 good ones) from the SExtractor catalog wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat
util/solve_plate_with_UCAC5 got 12825 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 917.5'
Seting catalog search parameters based on the expected field of view 917.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012743 (45.9 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010194 (36.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.0312 through 0 to 12.1186, gap 12.1186 to 348.0312
Reading UCAC5 zone files...
Searching UCAC5 zones 651 to 708 (Dec 40.2 to 51.3)
Done reading UCAC5 zone files...
Matched 575 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 542 matched stars entering correct_measured_positions(), 490 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.33"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 542 matched stars entering correct_measured_positions(), 6961 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.86"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.0288 through 0 to 12.1256, gap 12.1256 to 348.0288
Reading UCAC5 zone files...
Searching UCAC5 zones 651 to 708 (Dec 40.2 to 51.3)
Done reading UCAC5 zone files...
Matched 587 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 559 matched stars entering correct_measured_positions(), 6966 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.74"
Accuracy estimation diagnostic: 557 matched stars entering correct_measured_positions(), 7107 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.00"
Excluding outliers - 557 stars left (next iteration limit 596)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits -region wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.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.NuQUGV53Gr (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
WCS_IMAGE_NAME=wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
WCS-calibrated image found: wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
Checking if the catalog wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits alredy exist and is non-empty...
Catalog wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
WCS catalog name: wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=837, passed=12739
Got 12739 stars (including 11889 good ones) from the SExtractor catalog wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat
util/solve_plate_with_UCAC5 got 12739 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 938.9'
Seting catalog search parameters based on the expected field of view 938.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013040 (46.9 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010432 (37.6 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 347.4706 through 0 to 12.1323, gap 12.1323 to 347.4706
Reading UCAC5 zone files...
Searching UCAC5 zones 651 to 708 (Dec 40.3 to 51.3)
Done reading UCAC5 zone files...
Matched 945 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 943 matched stars entering correct_measured_positions(), 921 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.71"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 943 matched stars entering correct_measured_positions(), 12461 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.70"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 347.4681 through 0 to 12.1333, gap 12.1333 to 347.4681
Reading UCAC5 zone files...
Searching UCAC5 zones 651 to 708 (Dec 40.3 to 51.3)
Done reading UCAC5 zone files...
Matched 945 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 943 matched stars entering correct_measured_positions(), 12462 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.70"
Accuracy estimation diagnostic: 943 matched stars entering correct_measured_positions(), 12462 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.75"
Excluding outliers - 943 stars left (next iteration limit 1037)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits -region wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.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_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits'
Saving fully-calibrated image wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits'
Saving fully-calibrated image wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits'
Saving fully-calibrated image wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits'
Preparing the HTML report for the field And-01-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
make_report_in_HTML.sh Phase 1 (network queries): 0s
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: 0s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31969_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 31969_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:12:06.59 +48:12:19.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32333_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 32333_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (164.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32733_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 32733_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (84.2") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 0s
make_report_in_HTML.sh TOTAL: 0s
Prepared the HTML report for the field And-01-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
*------ done with default.sex.telephoto_lens_onlybrightstars_v1 ------*
#### The local exclusion list is exclusion_list_local.txt ####
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 4 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
SExtractor catalog cache: saved And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat to cache
SExtractor catalog cache: saved And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Creating symlink local_wcs_cache/wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Creating symlink local_wcs_cache/wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
Creating symlink local_wcs_cache/wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.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_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits exists and is non-empty
wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits exists and is non-empty
wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits exists and is non-empty
wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits exists and is non-empty
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits (1st reference image)
verification OK: wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Image size: 924.9'x628.2' 15.4(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.80"/pix along the X axis and 5.90"/pix along the Y axis
Image center: 00:00:19.361 +45:58:07.34 J2000 4789.000 3195.000
###################################
The image scale is 5.80"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.8" and 8.7"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits (1st new image)
verification OK: wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
Image size: 917.5'x627.9' 15.3(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.75"/pix along the X axis and 5.90"/pix along the Y axis
Image center: 23:59:59.813 +46:02:45.18 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 00:00:19.361 +45:58:07.34
Second-epoch image center 23:59:59.813 +46:02:45.18
Angular distance between the image centers 0.0957 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits (2nd new image)
verification OK: wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
Image size: 938.9'x624.4' 15.6(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.88"/pix along the X axis and 5.86"/pix along the Y axis
Image center: 00:00:00.569 +46:03:08.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 00:00:19.361 +45:58:07.34
Second-epoch image center 00:00:00.569 +46:03:08.58
Angular distance between the image centers 0.0998 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 23:59:59.813 +46:02:45.18
Second-epoch second image center 00:00:00.569 +46:03:08.58
Angular distance between the image centers 0.00686 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/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits &> /tmp/tmp.ISOeASTuqO
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits &> /tmp/tmp.ze5vbIKtX0
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits &> /tmp/tmp.IoDpCiILjp
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits &> /tmp/tmp.CZEtfsNVqW
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
Calibrating the magnitude scale
Found non-empty wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.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_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.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_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
Found non-empty wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
The reference image (wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits) and catalog (wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat) found
'wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat' -> 'wcsmag.cat'
Read 142009 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0001 to 359.9998 deg, Dec +39.9057 to +51.2155 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 0.0001 to 359.9998 deg, Dec 39.9057 to 51.2155 deg
Loaded 170564 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): 91 out of 117 total matches.
Matched with Tycho-2 117 out of 142009 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 21.227567
a=0.000000 b=1.000000 c=21.227567
From vast_summary.log: estimated ref. image limiting mag.: -7.48
Updating vast_summary.log: Estimated ref. image limiting mag.: 13.75
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 13.75
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 237 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.2 pix And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
2.2 pix And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
2.4 pix fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
2.3 pix fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
Limiting magnitude estimates:
13.7 mag. And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
13.7 mag. And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
13.0 mag. fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
13.0 mag. fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
All-image limiting magnitude estimate: 13.0 (SNR ) 12.5 (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.ISOeASTuqO (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits' -> 'wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS_IMAGE_NAME=wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS-calibrated image found: wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Checking if the catalog wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits alredy exist and is non-empty...
Catalog wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS catalog name: wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=47, blended=18012, passed=141962
Got 141962 stars (including 123722 good ones) from the SExtractor catalog wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
util/solve_plate_with_UCAC5 got 141962 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.9'
Seting catalog search parameters based on the expected field of view 924.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012846 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010277 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4418 through 0 to 12.7147, gap 12.7147 to 348.4418
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 204 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 151 matched stars entering correct_measured_positions(), 79 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.98"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 145 matched stars entering correct_measured_positions(), 15623 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.14"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4528 through 0 to 12.7273, gap 12.7273 to 348.4528
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 220 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 178 matched stars entering correct_measured_positions(), 15632 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.13"
Accuracy estimation diagnostic: 177 matched stars entering correct_measured_positions(), 18852 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.12"
Excluding outliers - 177 stars left (next iteration limit 159)
The image catalog is written to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits -region wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.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.ze5vbIKtX0 (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits' -> 'wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS_IMAGE_NAME=wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS-calibrated image found: wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Checking if the catalog wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits alredy exist and is non-empty...
Catalog wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS catalog name: wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=51, blended=18105, passed=141752
Got 141752 stars (including 123429 good ones) from the SExtractor catalog wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat
util/solve_plate_with_UCAC5 got 141752 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.9'
Seting catalog search parameters based on the expected field of view 924.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012846 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010277 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4216 through 0 to 12.6947, gap 12.6947 to 348.4216
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 199 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 147 matched stars entering correct_measured_positions(), 78 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.76"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 141 matched stars entering correct_measured_positions(), 15342 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.76"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4333 through 0 to 12.6945, gap 12.6945 to 348.4333
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 222 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 177 matched stars entering correct_measured_positions(), 15356 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.73"
Accuracy estimation diagnostic: 176 matched stars entering correct_measured_positions(), 20031 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.04"
Excluding outliers - 176 stars left (next iteration limit 155)
The image catalog is written to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits -region wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.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.IoDpCiILjp (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
WCS_IMAGE_NAME=wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
WCS-calibrated image found: wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
Checking if the catalog wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits alredy exist and is non-empty...
Catalog wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
WCS catalog name: wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat
SExtractor catalog parsing summary: zero_flux=4, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=17, blended=7400, passed=84448
Got 84448 stars (including 76955 good ones) from the SExtractor catalog wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat
util/solve_plate_with_UCAC5 got 84448 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 917.5'
Seting catalog search parameters based on the expected field of view 917.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012743 (45.9 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010194 (36.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 347.9864 through 0 to 12.1721, gap 12.1721 to 347.9864
Reading UCAC5 zone files...
Searching UCAC5 zones 650 to 708 (Dec 40.2 to 51.3)
Done reading UCAC5 zone files...
Matched 576 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 550 matched stars entering correct_measured_positions(), 505 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.21"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 548 matched stars entering correct_measured_positions(), 48087 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.50"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 347.9824 through 0 to 12.1775, gap 12.1775 to 347.9824
Reading UCAC5 zone files...
Searching UCAC5 zones 650 to 708 (Dec 40.2 to 51.3)
Done reading UCAC5 zone files...
Matched 585 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 570 matched stars entering correct_measured_positions(), 48094 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.49"
Accuracy estimation diagnostic: 570 matched stars entering correct_measured_positions(), 50539 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 1.70"
Excluding outliers - 570 stars left (next iteration limit 602)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits -region wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.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.CZEtfsNVqW (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
WCS_IMAGE_NAME=wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
WCS-calibrated image found: wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
Checking if the catalog wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits alredy exist and is non-empty...
Catalog wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
WCS catalog name: wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=25, blended=6909, passed=85385
Got 85385 stars (including 78381 good ones) from the SExtractor catalog wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat
util/solve_plate_with_UCAC5 got 85385 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 938.9'
Seting catalog search parameters based on the expected field of view 938.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013040 (46.9 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010432 (37.6 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 347.4705 through 0 to 12.2221, gap 12.2221 to 347.4705
Reading UCAC5 zone files...
Searching UCAC5 zones 651 to 708 (Dec 40.2 to 51.3)
Done reading UCAC5 zone files...
Matched 938 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 937 matched stars entering correct_measured_positions(), 919 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.70"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 937 matched stars entering correct_measured_positions(), 84046 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.69"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 347.4697 through 0 to 12.2219, gap 12.2219 to 347.4697
Reading UCAC5 zone files...
Searching UCAC5 zones 651 to 708 (Dec 40.2 to 51.3)
Done reading UCAC5 zone files...
Matched 938 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 937 matched stars entering correct_measured_positions(), 84046 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.69"
Accuracy estimation diagnostic: 937 matched stars entering correct_measured_positions(), 84046 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.73"
Excluding outliers - 937 stars left (next iteration limit 1030)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits -region wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.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_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Saving fully-calibrated image wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Saving fully-calibrated image wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/wcs_fd_And-01-Q2b1x1_2026-04-18_05-56-26_20.00sec_-4.90C_LIGHT_0285.fits
Saving fully-calibrated image wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-18_CI_And-01-Q2b1x1_061225_TTUQ2b1x1_1523355_G2eZH0eg/wcs_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286.fits
Preparing the HTML report for the field And-01-Q2b1x1 with default.sex.telephoto_lens_vSTL
Adding exclusion_list_gaiadr2.txt__out167956.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out161713.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161721.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161723.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161729.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161730.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161732.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161739.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161742.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161747.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161749.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161754.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161756.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161757.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161759.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161782.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161806.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161810.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161811.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161812.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161813.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out162979.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164896.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164924.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164929.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165127.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165276.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165401.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out166590.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out166704.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out167070.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out167516.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out167520.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out167915.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out168018.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out168323.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out168888.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out169178.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out169363.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out169592.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out169729.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out169806.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out169898.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out170300.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out170654.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out170872.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out170965.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out171144.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out171201.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out171239.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out171573.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out171783.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out171841.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out172494.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out172501.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out172574.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out172618.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out172889.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out173008.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out173169.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out173293.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out173316.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out173374.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out173762.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out173905.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out173919.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out173934.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out173994.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out174116.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out174129.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out174256.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out174368.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out174491.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out174604.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out174705.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out174891.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out174905.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175080.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175182.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175351.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175403.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175407.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175411.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175477.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175588.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175603.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175926.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175965.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176020.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176241.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176261.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176339.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176434.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176584.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176611.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176878.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176905.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176936.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177099.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177279.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177351.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177490.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177655.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177677.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177863.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177892.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178083.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178108.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178110.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178123.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178394.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178433.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178547.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178652.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178827.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178886.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178981.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out179169.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out179175.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out179231.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out179338.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out179891.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out179979.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out180055.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out180101.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 171s
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: 77s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161713_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161713_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161721_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161721_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161723_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161723_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161729_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161729_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161730_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161730_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161732_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161732_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161739_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161739_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161742_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161742_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161747_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161747_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161749_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161749_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161754_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161754_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161756_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161756_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161757_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161757_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161759_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161759_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161761_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 161761_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161763_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 161763_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (127.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161782_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161782_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161785_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 161785_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (108.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161800_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 161800_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (301.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161806_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161806_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161810_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161810_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161811_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161811_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161812_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161812_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161813_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 161813_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161815_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 161815_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (200.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 162937_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 162937_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:12:06.57 +48:12:20.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 162979_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 162979_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 163560_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 163560_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (84.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 163567_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 163567_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (164.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 163901_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 163901_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:16:22.96 +43:36:55.9 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164896_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 164896_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164924_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 164924_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164929_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 164929_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165019_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 165019_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165089_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 165089_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:16:27.53 +43:36:54.6 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165127_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 165127_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165276_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 165276_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165401_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 165401_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166202_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 166202_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166590_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 166590_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166604_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 166604_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (245.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166704_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 166704_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166786_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 166786_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167045_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 167045_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (114.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167070_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 167070_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167192_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 167192_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (66.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167299_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 167299_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 23:50:37.77 +47:30:32.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167409_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 167409_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:05:31.04 +48:29:22.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167513_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 167513_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (324.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167516_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 167516_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167520_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 167520_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167619_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 167619_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167650_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 167650_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (316.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167794_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 167794_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (26.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167915_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 167915_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167956_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 167956_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:22:26.60 +46:13:49.8 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=11.25, MAG_FAINT_SEARCH_LIMIT=12.23)GAIADR2_OUTPUT=# 5.720 391975659082049792 005.61288504072 +46.23121423297 12.2186 11.2083 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.720#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168014_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 168014_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168018_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 168018_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168323_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 168323_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168430_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 168430_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:05:48.29 +45:47:23.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168433_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 168433_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (23.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168724_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 168724_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168825_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 168825_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (137.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168888_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 168888_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168891_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 168891_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (22.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168933_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 168933_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (31.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169064_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 169064_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:18:30.07 +43:59:38.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169178_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 169178_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169203_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 169203_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (23.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169245_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 169245_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (55.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169280_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 169280_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (67.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169363_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 169363_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169592_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 169592_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169667_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 169667_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (401.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169692_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 169692_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (327.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169729_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 169729_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169806_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 169806_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169898_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 169898_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169933_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 169933_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (315.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170220_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 170220_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (62.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170300_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 170300_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170428_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 170428_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (316.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170454_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 170454_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170654_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 170654_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170692_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 170692_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170872_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 170872_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170939_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 170939_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (27.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170965_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 170965_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170978_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 170978_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:03:20.57 +49:54:42.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171144_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 171144_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171201_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 171201_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171239_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 171239_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171262_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 171262_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:13:02.63 +49:56:52.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171311_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 171311_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (82.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171363_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 171363_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (232.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171372_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 171372_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:20:09.88 +48:50:55.6 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171573_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 171573_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171618_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 171618_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171638_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 171638_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:02:17.17 +44:32:06.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171700_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 171700_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (285.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171783_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 171783_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171793_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 171793_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (25.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171841_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 171841_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172017_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172017_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:16:47.71 +49:29:29.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172048_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172048_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (25.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172107_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172107_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:01:31.82 +47:56:36.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172153_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172153_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (35.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172191_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172191_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (87.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172224_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172224_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172287_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172287_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:06:30.04 +47:25:02.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172292_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172292_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (202.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172339_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172339_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (23.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172494_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 172494_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172501_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 172501_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172563_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172563_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (110.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172574_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 172574_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172589_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172589_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (361.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172615_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172615_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:17:16.73 +47:55:43.8 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172618_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 172618_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172653_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172653_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172703_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172703_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:05:49.91 +49:36:52.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172796_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172796_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 23:55:22.76 +47:21:20.3 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172809_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172809_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (151.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172889_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 172889_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172997_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 172997_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (139.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173008_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 173008_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173169_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 173169_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173193_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 173193_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173251_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 173251_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (120.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173285_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 173285_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173293_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 173293_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173316_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 173316_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173325_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 173325_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173374_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 173374_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173405_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 173405_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (58.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173462_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 173462_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (169.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173762_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 173762_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173883_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 173883_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:06:11.67 +47:44:10.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173905_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 173905_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173919_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 173919_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173934_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 173934_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173994_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 173994_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174038_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 174038_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:05:35.00 +43:22:48.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174116_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 174116_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174129_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 174129_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174256_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 174256_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174325_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 174325_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (124.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174368_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 174368_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174430_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 174430_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174491_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 174491_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174509_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 174509_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (168.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174537_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 174537_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:08:31.71 +46:07:25.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174604_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 174604_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174705_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 174705_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174733_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 174733_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174783_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 174783_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (23.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174891_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 174891_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174905_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 174905_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175080_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 175080_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175182_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 175182_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175188_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 175188_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (166.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175351_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 175351_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175392_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 175392_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:04:29.23 +46:25:05.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175403_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 175403_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175407_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 175407_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175411_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 175411_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175477_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 175477_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175561_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 175561_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:05:03.19 +45:14:46.7 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175588_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 175588_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175603_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 175603_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175712_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 175712_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (25.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175769_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 175769_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (118.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175926_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 175926_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175965_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 175965_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176020_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 176020_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176241_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 176241_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176255_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 176255_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:05:30.10 +46:40:48.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176261_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 176261_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176339_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 176339_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176434_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 176434_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176584_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 176584_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176611_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 176611_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176617_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 176617_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (142.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176743_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 176743_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (27.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176878_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 176878_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176905_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 176905_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176936_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 176936_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177099_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 177099_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177279_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 177279_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177351_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 177351_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177358_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 177358_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (314.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177413_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 177413_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177420_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 177420_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177436_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 177436_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177452_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 177452_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (44.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177490_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 177490_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177655_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 177655_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177677_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 177677_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177831_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 177831_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (175.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177863_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 177863_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177874_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 177874_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (300.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177877_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 177877_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (78.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177892_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 177892_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178083_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 178083_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178088_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 178088_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (151.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178108_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 178108_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178110_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 178110_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178123_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 178123_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178204_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 178204_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (25.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178322_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 178322_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (25.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178394_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 178394_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178433_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 178433_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178547_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 178547_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178562_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 178562_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (33.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178652_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 178652_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178751_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 178751_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178827_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 178827_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178886_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 178886_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178981_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 178981_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179130_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 179130_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (186.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179151_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 179151_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (17.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179169_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 179169_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179175_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 179175_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179230_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 179230_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (24.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179231_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 179231_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179338_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 179338_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179372_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 179372_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (78.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179891_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 179891_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179979_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 179979_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 180055_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 180055_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 180101_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
Preparing report for the candidate 180101_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57324_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 57324_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (216.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 59955_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 59955_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 23:50:36.07 +47:31:26.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52886_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 52886_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
**** FOUND 00:19:50.16 +47:42:37.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 118010_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 118010_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (44.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 77205_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 77205_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (369.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 30636_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286
The candidate 30636_fd_And-01-Q2b1x1_2026-04-18_05-57-15_20.00sec_-5.00C_LIGHT_0286 did not pass the final checks
Rejecting candidate due to large distance (33.7") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 13s
make_report_in_HTML.sh TOTAL: 261s
Prepared the HTML report for the field And-01-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
00:11:24.87 +46:51:12.8
00:10:08.63 +45:52:00.3
00:12:40.99 +46:39:28.1
00:25:37.73 +48:33:21.9
00:05:20.93 +47:50:54.3
00:01:35.05 +47:32:39.6
00:03:45.22 +44:29:26.6
00:08:19.61 +48:21:08.9
00:25:17.32 +49:51:09.6
00:20:35.20 +47:35:36.6
00:21:26.11 +48:58:01.3
00:10:14.24 +46:24:55.5
00:08:32.63 +48:53:27.3
23:57:33.59 +46:30:48.3
00:05:00.96 +46:35:39.7
00:07:21.22 +46:36:34.0
00:14:41.71 +46:51:19.5
00:00:20.39 +46:04:22.7
00:24:36.39 +49:04:57.9
00:13:20.82 +46:36:35.3
23:57:30.26 +48:17:25.7
00:06:33.47 +46:28:40.6
00:15:03.85 +47:15:03.8
00:07:52.19 +44:04:41.8
00:08:05.16 +44:53:35.4
00:08:13.04 +46:04:33.8
00:23:19.95 +46:33:51.8
23:55:47.98 +45:06:40.6
00:15:45.24 +45:30:22.4
00:21:03.53 +47:36:14.3
00:10:16.65 +49:00:01.1
00:16:05.47 +46:59:36.8
00:02:09.49 +42:08:07.7
23:57:14.32 +45:56:54.3
00:24:07.51 +46:17:08.3
00:04:30.34 +47:01:10.5
00:01:42.12 +46:36:22.7
00:09:49.18 +46:02:02.8
00:09:56.12 +46:22:42.7
00:19:05.93 +50:00:27.8
00:17:32.35 +50:15:56.4
00:21:28.63 +44:22:14.6
00:06:55.76 +46:08:05.4
00:25:12.52 +50:11:54.6
00:19:38.45 +46:30:12.3
00:00:57.14 +44:33:13.1
00:11:06.67 +46:40:49.3
00:20:27.45 +49:12:22.2
00:17:19.23 +44:57:47.3
00:08:29.52 +45:02:25.4
00:08:02.58 +46:30:04.5
00:07:09.68 +45:43:12.1
23:57:20.26 +48:06:22.4
00:01:22.12 +46:44:46.4
00:17:32.06 +45:44:43.0
00:04:48.21 +44:03:44.9
00:02:11.05 +50:19:52.0
00:02:45.76 +47:14:34.9
23:54:57.17 +46:52:40.3
00:08:24.91 +44:57:39.8
00:23:45.50 +49:19:27.7
00:03:11.15 +45:52:59.6
00:16:37.01 +47:13:48.2
00:21:25.94 +44:22:23.3
00:12:06.06 +45:51:25.4
23:58:26.70 +48:35:39.7
00:13:00.32 +46:48:05.2
00:08:57.11 +44:53:11.7
00:09:08.00 +48:43:25.3
00:25:11.59 +48:04:07.5
00:04:20.53 +42:07:10.1
00:12:23.06 +47:53:49.5
00:03:55.81 +49:40:52.9
23:54:40.38 +44:53:46.8
00:15:00.49 +46:47:04.6
00:23:02.89 +44:30:13.1
00:16:04.90 +49:53:06.0
23:57:08.47 +45:57:30.6
23:53:06.61 +47:04:44.3
00:04:26.52 +43:37:19.1
00:07:42.33 +42:42:09.8
00:09:49.98 +48:59:47.9
00:15:49.07 +42:39:01.2
00:14:41.39 +47:22:49.6
23:50:36.75 +47:03:38.9
00:20:51.19 +44:52:26.9
00:19:15.89 +47:21:45.6
23:58:01.88 +43:43:14.5
00:07:10.71 +46:21:14.4
00:02:36.08 +44:57:42.9
00:13:16.71 +46:26:10.2
00:15:39.99 +45:53:22.7
00:22:42.08 +48:01:05.1
00:13:02.71 +48:43:54.5
00:14:28.18 +46:03:16.6
00:20:30.77 +44:02:49.7
23:59:29.66 +44:37:14.6
00:17:08.10 +48:28:49.1
23:57:30.30 +48:02:02.1
00:22:21.14 +46:00:41.5
00:06:14.66 +45:18:19.7
00:14:11.52 +46:13:05.8
00:21:09.50 +44:57:54.4
00:03:56.39 +46:27:46.0
00:03:25.73 +47:34:55.9
00:00:56.64 +43:15:27.2
23:52:56.17 +47:09:38.1
00:07:49.56 +50:03:09.3
00:02:12.55 +45:57:35.9
00:18:47.16 +48:23:36.1
00:18:37.52 +47:43:36.2
00:25:26.62 +46:40:25.4
00:00:31.28 +45:22:44.4
23:53:37.02 +45:57:48.4
00:07:25.11 +46:44:11.7
23:57:09.10 +42:48:45.3
00:21:52.60 +48:24:47.2
00:05:09.98 +45:32:20.7
00:11:44.63 +47:49:55.5
00:18:36.79 +46:21:23.5
00:12:35.71 +43:17:41.4
00:06:07.47 +47:45:17.2
00:11:26.81 +46:03:58.5
00:07:54.33 +46:16:37.9
########### Completed And-01-Q2b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ2.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
00:11:24.87 +46:51:12.8
00:10:08.63 +45:52:00.3
00:12:40.99 +46:39:28.1
00:25:37.73 +48:33:21.9
00:05:20.93 +47:50:54.3
00:01:35.05 +47:32:39.6
00:03:45.22 +44:29:26.6
00:08:19.61 +48:21:08.9
00:25:17.32 +49:51:09.6
00:20:35.20 +47:35:36.6
00:21:26.11 +48:58:01.3
00:10:14.24 +46:24:55.5
00:08:32.63 +48:53:27.3
23:57:33.59 +46:30:48.3
00:05:00.96 +46:35:39.7
00:07:21.22 +46:36:34.0
00:14:41.71 +46:51:19.5
00:00:20.39 +46:04:22.7
00:24:36.39 +49:04:57.9
00:13:20.82 +46:36:35.3
23:57:30.26 +48:17:25.7
00:06:33.47 +46:28:40.6
00:15:03.85 +47:15:03.8
00:07:52.19 +44:04:41.8
00:08:05.16 +44:53:35.4
00:08:13.04 +46:04:33.8
00:23:19.95 +46:33:51.8
23:55:47.98 +45:06:40.6
00:15:45.24 +45:30:22.4
00:21:03.53 +47:36:14.3
00:10:16.65 +49:00:01.1
00:16:05.47 +46:59:36.8
00:02:09.49 +42:08:07.7
23:57:14.32 +45:56:54.3
00:24:07.51 +46:17:08.3
00:04:30.34 +47:01:10.5
00:01:42.12 +46:36:22.7
00:09:49.18 +46:02:02.8
00:09:56.12 +46:22:42.7
00:19:05.93 +50:00:27.8
00:17:32.35 +50:15:56.4
00:21:28.63 +44:22:14.6
00:06:55.76 +46:08:05.4
00:25:12.52 +50:11:54.6
00:19:38.45 +46:30:12.3
00:00:57.14 +44:33:13.1
00:11:06.67 +46:40:49.3
00:20:27.45 +49:12:22.2
00:17:19.23 +44:57:47.3
00:08:29.52 +45:02:25.4
00:08:02.58 +46:30:04.5
00:07:09.68 +45:43:12.1
23:57:20.26 +48:06:22.4
00:01:22.12 +46:44:46.4
00:17:32.06 +45:44:43.0
00:04:48.21 +44:03:44.9
00:02:11.05 +50:19:52.0
00:02:45.76 +47:14:34.9
23:54:57.17 +46:52:40.3
00:08:24.91 +44:57:39.8
00:23:45.50 +49:19:27.7
00:03:11.15 +45:52:59.6
00:16:37.01 +47:13:48.2
00:21:25.94 +44:22:23.3
00:12:06.06 +45:51:25.4
23:58:26.70 +48:35:39.7
00:13:00.32 +46:48:05.2
00:08:57.11 +44:53:11.7
00:09:08.00 +48:43:25.3
00:25:11.59 +48:04:07.5
00:04:20.53 +42:07:10.1
00:12:23.06 +47:53:49.5
00:03:55.81 +49:40:52.9
23:54:40.38 +44:53:46.8
00:15:00.49 +46:47:04.6
00:23:02.89 +44:30:13.1
00:16:04.90 +49:53:06.0
23:57:08.47 +45:57:30.6
23:53:06.61 +47:04:44.3
00:04:26.52 +43:37:19.1
00:07:42.33 +42:42:09.8
00:09:49.98 +48:59:47.9
00:15:49.07 +42:39:01.2
00:14:41.39 +47:22:49.6
23:50:36.75 +47:03:38.9
00:20:51.19 +44:52:26.9
00:19:15.89 +47:21:45.6
23:58:01.88 +43:43:14.5
00:07:10.71 +46:21:14.4
00:02:36.08 +44:57:42.9
00:13:16.71 +46:26:10.2
00:15:39.99 +45:53:22.7
00:22:42.08 +48:01:05.1
00:13:02.71 +48:43:54.5
00:14:28.18 +46:03:16.6
00:20:30.77 +44:02:49.7
23:59:29.66 +44:37:14.6
00:17:08.10 +48:28:49.1
23:57:30.30 +48:02:02.1
00:22:21.14 +46:00:41.5
00:00:07.89 +49:01:30.6
00:06:14.66 +45:18:19.7
00:14:11.52 +46:13:05.8
00:21:09.50 +44:57:54.4
00:03:56.39 +46:27:46.0
00:03:25.73 +47:34:55.9
00:00:56.64 +43:15:27.2
23:52:56.17 +47:09:38.1
00:07:49.56 +50:03:09.3
00:02:12.55 +45:57:35.9
00:18:47.16 +48:23:36.1
00:18:37.52 +47:43:36.2
00:25:26.62 +46:40:25.4
00:00:31.28 +45:22:44.4
23:53:37.02 +45:57:48.4
00:07:25.11 +46:44:11.7
23:57:09.10 +42:48:45.3
00:21:52.60 +48:24:47.2
00:05:09.98 +45:32:20.7
00:11:44.63 +47:49:55.5
00:18:36.79 +46:21:23.5
00:12:35.71 +43:17:41.4
00:06:07.47 +47:45:17.2
00:11:26.81 +46:03:58.5
00:07:54.33 +46:16:37.9
###################################################################################
00:11:24.87 +46:51:12.8 -- not an asteroid (will add it to exclusion list)
00:10:08.63 +45:52:00.3 -- not an asteroid (will add it to exclusion list)
00:12:40.99 +46:39:28.1 -- not an asteroid (will add it to exclusion list)
00:25:37.73 +48:33:21.9 -- not an asteroid (will add it to exclusion list)
00:05:20.93 +47:50:54.3 -- not an asteroid (will add it to exclusion list)
00:01:35.05 +47:32:39.6 -- not an asteroid (will add it to exclusion list)
00:03:45.22 +44:29:26.6 -- not an asteroid (will add it to exclusion list)
00:08:19.61 +48:21:08.9 -- not an asteroid (will add it to exclusion list)
00:25:17.32 +49:51:09.6 -- not an asteroid (will add it to exclusion list)
00:20:35.20 +47:35:36.6 -- not an asteroid (will add it to exclusion list)
00:21:26.11 +48:58:01.3 -- not an asteroid (will add it to exclusion list)
00:10:14.24 +46:24:55.5 -- not an asteroid (will add it to exclusion list)
00:08:32.63 +48:53:27.3 -- not an asteroid (will add it to exclusion list)
23:57:33.59 +46:30:48.3 -- not an asteroid (will add it to exclusion list)
00:05:00.96 +46:35:39.7 -- not an asteroid (will add it to exclusion list)
00:07:21.22 +46:36:34.0 -- not an asteroid (will add it to exclusion list)
00:14:41.71 +46:51:19.5 -- not an asteroid (will add it to exclusion list)
00:00:20.39 +46:04:22.7 -- not an asteroid (will add it to exclusion list)
00:24:36.39 +49:04:57.9 -- not an asteroid (will add it to exclusion list)
00:13:20.82 +46:36:35.3 -- not an asteroid (will add it to exclusion list)
23:57:30.26 +48:17:25.7 -- not an asteroid (will add it to exclusion list)
00:06:33.47 +46:28:40.6 -- not an asteroid (will add it to exclusion list)
00:15:03.85 +47:15:03.8 -- not an asteroid (will add it to exclusion list)
00:07:52.19 +44:04:41.8 -- not an asteroid (will add it to exclusion list)
00:08:05.16 +44:53:35.4 -- not an asteroid (will add it to exclusion list)
00:08:13.04 +46:04:33.8 -- not an asteroid (will add it to exclusion list)
00:23:19.95 +46:33:51.8 -- not an asteroid (will add it to exclusion list)
23:55:47.98 +45:06:40.6 -- not an asteroid (will add it to exclusion list)
00:15:45.24 +45:30:22.4 -- not an asteroid (will add it to exclusion list)
00:21:03.53 +47:36:14.3 -- not an asteroid (will add it to exclusion list)
00:10:16.65 +49:00:01.1 -- not an asteroid (will add it to exclusion list)
00:16:05.47 +46:59:36.8 -- not an asteroid (will add it to exclusion list)
00:02:09.49 +42:08:07.7 -- not an asteroid (will add it to exclusion list)
23:57:14.32 +45:56:54.3 -- not an asteroid (will add it to exclusion list)
00:24:07.51 +46:17:08.3 -- not an asteroid (will add it to exclusion list)
00:04:30.34 +47:01:10.5 -- not an asteroid (will add it to exclusion list)
00:01:42.12 +46:36:22.7 -- not an asteroid (will add it to exclusion list)
00:09:49.18 +46:02:02.8 -- not an asteroid (will add it to exclusion list)
00:09:56.12 +46:22:42.7 -- not an asteroid (will add it to exclusion list)
00:19:05.93 +50:00:27.8 -- not an asteroid (will add it to exclusion list)
00:17:32.35 +50:15:56.4 -- not an asteroid (will add it to exclusion list)
00:21:28.63 +44:22:14.6 -- not an asteroid (will add it to exclusion list)
00:06:55.76 +46:08:05.4 -- not an asteroid (will add it to exclusion list)
00:25:12.52 +50:11:54.6 -- not an asteroid (will add it to exclusion list)
00:19:38.45 +46:30:12.3 -- not an asteroid (will add it to exclusion list)
00:00:57.14 +44:33:13.1 -- not an asteroid (will add it to exclusion list)
00:11:06.67 +46:40:49.3 -- not an asteroid (will add it to exclusion list)
00:20:27.45 +49:12:22.2 -- not an asteroid (will add it to exclusion list)
00:17:19.23 +44:57:47.3 -- not an asteroid (will add it to exclusion list)
00:08:29.52 +45:02:25.4 -- not an asteroid (will add it to exclusion list)
00:08:02.58 +46:30:04.5 -- not an asteroid (will add it to exclusion list)
00:07:09.68 +45:43:12.1 -- not an asteroid (will add it to exclusion list)
23:57:20.26 +48:06:22.4 -- not an asteroid (will add it to exclusion list)
00:01:22.12 +46:44:46.4 -- not an asteroid (will add it to exclusion list)
00:17:32.06 +45:44:43.0 -- not an asteroid (will add it to exclusion list)
00:04:48.21 +44:03:44.9 -- not an asteroid (will add it to exclusion list)
00:02:11.05 +50:19:52.0 -- not an asteroid (will add it to exclusion list)
00:02:45.76 +47:14:34.9 -- not an asteroid (will add it to exclusion list)
23:54:57.17 +46:52:40.3 -- not an asteroid (will add it to exclusion list)
00:08:24.91 +44:57:39.8 -- not an asteroid (will add it to exclusion list)
00:23:45.50 +49:19:27.7 -- not an asteroid (will add it to exclusion list)
00:03:11.15 +45:52:59.6 -- not an asteroid (will add it to exclusion list)
00:16:37.01 +47:13:48.2 -- not an asteroid (will add it to exclusion list)
00:21:25.94 +44:22:23.3 -- not an asteroid (will add it to exclusion list)
00:12:06.06 +45:51:25.4 -- not an asteroid (will add it to exclusion list)
23:58:26.70 +48:35:39.7 -- not an asteroid (will add it to exclusion list)
00:13:00.32 +46:48:05.2 -- not an asteroid (will add it to exclusion list)
00:08:57.11 +44:53:11.7 -- not an asteroid (will add it to exclusion list)
00:09:08.00 +48:43:25.3 -- not an asteroid (will add it to exclusion list)
00:25:11.59 +48:04:07.5 -- not an asteroid (will add it to exclusion list)
00:04:20.53 +42:07:10.1 -- not an asteroid (will add it to exclusion list)
00:12:23.06 +47:53:49.5 -- not an asteroid (will add it to exclusion list)
00:03:55.81 +49:40:52.9 -- not an asteroid (will add it to exclusion list)
23:54:40.38 +44:53:46.8 -- not an asteroid (will add it to exclusion list)
00:15:00.49 +46:47:04.6 -- not an asteroid (will add it to exclusion list)
00:23:02.89 +44:30:13.1 -- not an asteroid (will add it to exclusion list)
00:16:04.90 +49:53:06.0 -- not an asteroid (will add it to exclusion list)
23:57:08.47 +45:57:30.6 -- not an asteroid (will add it to exclusion list)
23:53:06.61 +47:04:44.3 -- not an asteroid (will add it to exclusion list)
00:04:26.52 +43:37:19.1 -- not an asteroid (will add it to exclusion list)
00:07:42.33 +42:42:09.8 -- not an asteroid (will add it to exclusion list)
00:09:49.98 +48:59:47.9 -- not an asteroid (will add it to exclusion list)
00:15:49.07 +42:39:01.2 -- not an asteroid (will add it to exclusion list)
00:14:41.39 +47:22:49.6 -- not an asteroid (will add it to exclusion list)
23:50:36.75 +47:03:38.9 -- not an asteroid (will add it to exclusion list)
00:20:51.19 +44:52:26.9 -- not an asteroid (will add it to exclusion list)
00:19:15.89 +47:21:45.6 -- not an asteroid (will add it to exclusion list)
23:58:01.88 +43:43:14.5 -- not an asteroid (will add it to exclusion list)
00:07:10.71 +46:21:14.4 -- not an asteroid (will add it to exclusion list)
00:02:36.08 +44:57:42.9 -- not an asteroid (will add it to exclusion list)
00:13:16.71 +46:26:10.2 -- not an asteroid (will add it to exclusion list)
00:15:39.99 +45:53:22.7 -- not an asteroid (will add it to exclusion list)
00:22:42.08 +48:01:05.1 -- not an asteroid (will add it to exclusion list)
00:13:02.71 +48:43:54.5 -- not an asteroid (will add it to exclusion list)
00:14:28.18 +46:03:16.6 -- not an asteroid (will add it to exclusion list)
00:20:30.77 +44:02:49.7 -- not an asteroid (will add it to exclusion list)
23:59:29.66 +44:37:14.6 -- not an asteroid (will add it to exclusion list)
00:17:08.10 +48:28:49.1 -- not an asteroid (will add it to exclusion list)
23:57:30.30 +48:02:02.1 -- not an asteroid (will add it to exclusion list)
00:22:21.14 +46:00:41.5 -- not an asteroid (will add it to exclusion list)
00:00:07.89 +49:01:30.6 -- asteroid (will NOT add it to exclusion list)
00:06:14.66 +45:18:19.7 -- not an asteroid (will add it to exclusion list)
00:14:11.52 +46:13:05.8 -- not an asteroid (will add it to exclusion list)
00:21:09.50 +44:57:54.4 -- not an asteroid (will add it to exclusion list)
00:03:56.39 +46:27:46.0 -- not an asteroid (will add it to exclusion list)
00:03:25.73 +47:34:55.9 -- not an asteroid (will add it to exclusion list)
00:00:56.64 +43:15:27.2 -- not an asteroid (will add it to exclusion list)
23:52:56.17 +47:09:38.1 -- not an asteroid (will add it to exclusion list)
00:07:49.56 +50:03:09.3 -- not an asteroid (will add it to exclusion list)
00:02:12.55 +45:57:35.9 -- not an asteroid (will add it to exclusion list)
00:18:47.16 +48:23:36.1 -- not an asteroid (will add it to exclusion list)
00:18:37.52 +47:43:36.2 -- not an asteroid (will add it to exclusion list)
00:25:26.62 +46:40:25.4 -- not an asteroid (will add it to exclusion list)
00:00:31.28 +45:22:44.4 -- not an asteroid (will add it to exclusion list)
23:53:37.02 +45:57:48.4 -- not an asteroid (will add it to exclusion list)
00:07:25.11 +46:44:11.7 -- not an asteroid (will add it to exclusion list)
23:57:09.10 +42:48:45.3 -- not an asteroid (will add it to exclusion list)
00:21:52.60 +48:24:47.2 -- not an asteroid (will add it to exclusion list)
00:05:09.98 +45:32:20.7 -- not an asteroid (will add it to exclusion list)
00:11:44.63 +47:49:55.5 -- not an asteroid (will add it to exclusion list)
00:18:36.79 +46:21:23.5 -- not an asteroid (will add it to exclusion list)
00:12:35.71 +43:17:41.4 -- not an asteroid (will add it to exclusion list)
00:06:07.47 +47:45:17.2 -- not an asteroid (will add it to exclusion list)
00:11:26.81 +46:03:58.5 -- not an asteroid (will add it to exclusion list)
00:07:54.33 +46:16:37.9 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:20.39 +46:04:22.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:31.28 +45:22:44.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:56.64 +43:15:27.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:57.14 +44:33:13.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:22.12 +46:44:46.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:35.05 +47:32:39.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:42.12 +46:36:22.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:09.49 +42:08:07.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:11.05 +50:19:52.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:12.55 +45:57:35.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:36.08 +44:57:42.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:45.76 +47:14:34.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:11.15 +45:52:59.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:25.73 +47:34:55.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:45.22 +44:29:26.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:55.81 +49:40:52.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:56.39 +46:27:46.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:20.53 +42:07:10.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:26.52 +43:37:19.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:30.34 +47:01:10.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:48.21 +44:03:44.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:00.96 +46:35:39.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:09.98 +45:32:20.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:20.93 +47:50:54.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:07.47 +47:45:17.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:14.66 +45:18:19.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:33.47 +46:28:40.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:55.76 +46:08:05.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:09.68 +45:43:12.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:10.71 +46:21:14.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:21.22 +46:36:34.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:25.11 +46:44:11.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:42.33 +42:42:09.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:49.56 +50:03:09.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:52.19 +44:04:41.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:54.33 +46:16:37.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:02.58 +46:30:04.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:05.16 +44:53:35.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:13.04 +46:04:33.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:19.61 +48:21:08.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:24.91 +44:57:39.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:29.52 +45:02:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:32.63 +48:53:27.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:57.11 +44:53:11.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:08.00 +48:43:25.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:49.18 +46:02:02.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:49.98 +48:59:47.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:56.12 +46:22:42.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:08.63 +45:52:00.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:14.24 +46:24:55.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:16.65 +49:00:01.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:06.67 +46:40:49.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:24.87 +46:51:12.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:26.81 +46:03:58.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:44.63 +47:49:55.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:06.06 +45:51:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:23.06 +47:53:49.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:35.71 +43:17:41.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:40.99 +46:39:28.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:00.32 +46:48:05.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:02.71 +48:43:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:16.71 +46:26:10.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:20.82 +46:36:35.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:11.52 +46:13:05.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:28.18 +46:03:16.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:41.39 +47:22:49.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:41.71 +46:51:19.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:00.49 +46:47:04.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:03.85 +47:15:03.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:39.99 +45:53:22.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:45.24 +45:30:22.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:49.07 +42:39:01.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:04.90 +49:53:06.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:05.47 +46:59:36.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:37.01 +47:13:48.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:08.10 +48:28:49.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:19.23 +44:57:47.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:32.06 +45:44:43.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:32.35 +50:15:56.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:36.79 +46:21:23.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:37.52 +47:43:36.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:47.16 +48:23:36.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:05.93 +50:00:27.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:15.89 +47:21:45.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:38.45 +46:30:12.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:27.45 +49:12:22.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:30.77 +44:02:49.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:35.20 +47:35:36.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:51.19 +44:52:26.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:03.53 +47:36:14.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:09.50 +44:57:54.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:25.94 +44:22:23.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:26.11 +48:58:01.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:28.63 +44:22:14.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:52.60 +48:24:47.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:21.14 +46:00:41.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:42.08 +48:01:05.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:02.89 +44:30:13.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:19.95 +46:33:51.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:45.50 +49:19:27.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:07.51 +46:17:08.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:36.39 +49:04:57.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:11.59 +48:04:07.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:12.52 +50:11:54.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:17.32 +49:51:09.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:26.62 +46:40:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:37.73 +48:33:21.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:36.75 +47:03:38.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:56.17 +47:09:38.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:06.61 +47:04:44.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:37.02 +45:57:48.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:40.38 +44:53:46.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:57.17 +46:52:40.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:47.98 +45:06:40.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:08.47 +45:57:30.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:09.10 +42:48:45.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:14.32 +45:56:54.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:20.26 +48:06:22.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:30.26 +48:17:25.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:30.30 +48:02:02.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:33.59 +46:30:48.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:01.88 +43:43:14.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:26.70 +48:35:39.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:29.66 +44:37:14.6 -- 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)
00:00:20.39 +46:04:22.7 -- not a known variable star
00:00:31.28 +45:22:44.4 -- not a known variable star
00:00:56.64 +43:15:27.2 -- not a known variable star
00:00:57.14 +44:33:13.1 -- not a known variable star
00:01:22.12 +46:44:46.4 -- not a known variable star
00:01:35.05 +47:32:39.6 -- not a known variable star
00:01:42.12 +46:36:22.7 -- not a known variable star
00:02:09.49 +42:08:07.7 -- not a known variable star
00:02:11.05 +50:19:52.0 -- not a known variable star
00:02:12.55 +45:57:35.9 -- not a known variable star
00:02:36.08 +44:57:42.9 -- not a known variable star
00:02:45.76 +47:14:34.9 -- not a known variable star
00:03:11.15 +45:52:59.6 -- not a known variable star
00:03:25.73 +47:34:55.9 -- not a known variable star
00:03:45.22 +44:29:26.6 -- not a known variable star
00:03:55.81 +49:40:52.9 -- not a known variable star
00:03:56.39 +46:27:46.0 -- not a known variable star
00:04:20.53 +42:07:10.1 -- not a known variable star
00:04:26.52 +43:37:19.1 -- not a known variable star
00:04:30.34 +47:01:10.5 -- not a known variable star
00:04:48.21 +44:03:44.9 -- not a known variable star
00:05:00.96 +46:35:39.7 -- not a known variable star
00:05:09.98 +45:32:20.7 -- not a known variable star
00:05:20.93 +47:50:54.3 -- not a known variable star
00:06:07.47 +47:45:17.2 -- not a known variable star
00:06:14.66 +45:18:19.7 -- not a known variable star
00:06:33.47 +46:28:40.6 -- not a known variable star
00:06:55.76 +46:08:05.4 -- not a known variable star
00:07:09.68 +45:43:12.1 -- not a known variable star
00:07:10.71 +46:21:14.4 -- not a known variable star
00:07:21.22 +46:36:34.0 -- not a known variable star
00:07:25.11 +46:44:11.7 -- not a known variable star
00:07:42.33 +42:42:09.8 -- not a known variable star
00:07:49.56 +50:03:09.3 -- not a known variable star
00:07:52.19 +44:04:41.8 -- not a known variable star
00:07:54.33 +46:16:37.9 -- not a known variable star
00:08:02.58 +46:30:04.5 -- a known variable star
00:08:05.16 +44:53:35.4 -- not a known variable star
00:08:13.04 +46:04:33.8 -- not a known variable star
00:08:19.61 +48:21:08.9 -- not a known variable star
00:08:24.91 +44:57:39.8 -- not a known variable star
00:08:29.52 +45:02:25.4 -- not a known variable star
00:08:32.63 +48:53:27.3 -- not a known variable star
00:08:57.11 +44:53:11.7 -- not a known variable star
00:09:08.00 +48:43:25.3 -- not a known variable star
00:09:49.18 +46:02:02.8 -- not a known variable star
00:09:49.98 +48:59:47.9 -- not a known variable star
00:09:56.12 +46:22:42.7 -- not a known variable star
00:10:08.63 +45:52:00.3 -- not a known variable star
00:10:14.24 +46:24:55.5 -- not a known variable star
00:10:16.65 +49:00:01.1 -- a known variable star
00:11:06.67 +46:40:49.3 -- not a known variable star
00:11:24.87 +46:51:12.8 -- not a known variable star
00:11:26.81 +46:03:58.5 -- a known variable star
00:11:44.63 +47:49:55.5 -- a known variable star
00:12:06.06 +45:51:25.4 -- not a known variable star
00:12:23.06 +47:53:49.5 -- not a known variable star
00:12:35.71 +43:17:41.4 -- not a known variable star
00:12:40.99 +46:39:28.1 -- a known variable star
00:13:00.32 +46:48:05.2 -- not a known variable star
00:13:02.71 +48:43:54.5 -- not a known variable star
00:13:16.71 +46:26:10.2 -- not a known variable star
00:13:20.82 +46:36:35.3 -- a known variable star
00:14:11.52 +46:13:05.8 -- not a known variable star
00:14:28.18 +46:03:16.6 -- not a known variable star
00:14:41.39 +47:22:49.6 -- not a known variable star
00:14:41.71 +46:51:19.5 -- not a known variable star
00:15:00.49 +46:47:04.6 -- not a known variable star
00:15:03.85 +47:15:03.8 -- not a known variable star
00:15:39.99 +45:53:22.7 -- not a known variable star
00:15:45.24 +45:30:22.4 -- not a known variable star
00:15:49.07 +42:39:01.2 -- not a known variable star
00:16:04.90 +49:53:06.0 -- not a known variable star
00:16:05.47 +46:59:36.8 -- not a known variable star
00:16:37.01 +47:13:48.2 -- not a known variable star
00:17:08.10 +48:28:49.1 -- not a known variable star
00:17:19.23 +44:57:47.3 -- not a known variable star
00:17:32.06 +45:44:43.0 -- not a known variable star
00:17:32.35 +50:15:56.4 -- not a known variable star
00:18:36.79 +46:21:23.5 -- not a known variable star
00:18:37.52 +47:43:36.2 -- not a known variable star
00:18:47.16 +48:23:36.1 -- not a known variable star
00:19:05.93 +50:00:27.8 -- not a known variable star
00:19:15.89 +47:21:45.6 -- not a known variable star
00:19:38.45 +46:30:12.3 -- a known variable star
00:20:27.45 +49:12:22.2 -- not a known variable star
00:20:30.77 +44:02:49.7 -- not a known variable star
00:20:35.20 +47:35:36.6 -- not a known variable star
00:20:51.19 +44:52:26.9 -- not a known variable star
00:21:03.53 +47:36:14.3 -- not a known variable star
00:21:09.50 +44:57:54.4 -- not a known variable star
00:21:25.94 +44:22:23.3 -- a known variable star
00:21:26.11 +48:58:01.3 -- not a known variable star
00:21:28.63 +44:22:14.6 -- not a known variable star
00:21:52.60 +48:24:47.2 -- not a known variable star
00:22:21.14 +46:00:41.5 -- not a known variable star
00:22:42.08 +48:01:05.1 -- not a known variable star
00:23:02.89 +44:30:13.1 -- not a known variable star
00:23:19.95 +46:33:51.8 -- not a known variable star
00:23:45.50 +49:19:27.7 -- not a known variable star
00:24:07.51 +46:17:08.3 -- not a known variable star
00:24:36.39 +49:04:57.9 -- not a known variable star
00:25:11.59 +48:04:07.5 -- not a known variable star
00:25:12.52 +50:11:54.6 -- not a known variable star
00:25:17.32 +49:51:09.6 -- not a known variable star
00:25:26.62 +46:40:25.4 -- not a known variable star
00:25:37.73 +48:33:21.9 -- not a known variable star
23:50:36.75 +47:03:38.9 -- not a known variable star
23:52:56.17 +47:09:38.1 -- a known variable star
23:53:06.61 +47:04:44.3 -- not a known variable star
23:53:37.02 +45:57:48.4 -- not a known variable star
23:54:40.38 +44:53:46.8 -- not a known variable star
23:54:57.17 +46:52:40.3 -- not a known variable star
23:55:47.98 +45:06:40.6 -- not a known variable star
23:57:08.47 +45:57:30.6 -- not a known variable star
23:57:09.10 +42:48:45.3 -- not a known variable star
23:57:14.32 +45:56:54.3 -- not a known variable star
23:57:20.26 +48:06:22.4 -- not a known variable star
23:57:30.26 +48:17:25.7 -- a known variable star
23:57:30.30 +48:02:02.1 -- not a known variable star
23:57:33.59 +46:30:48.3 -- a known variable star
23:58:01.88 +43:43:14.5 -- not a known variable star
23:58:26.70 +48:35:39.7 -- not a known variable star
23:59:29.66 +44:37:14.6 -- a known variable star
Found 112 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
124 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 124 (excluding asteroids and hot pixels, 112 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)2461148.95597999 -observatory V36
00:20:33.78 -00:38:48.4 Mercury (-0.0mag)
03:20:43.18 +18:45:15.2 Venus (-3.9mag)
00:24:49.06 +01:37:51.0 Mars (1.2mag)
07:13:46.72 +22:44:18.8 Jupiter (-2.1mag)
00:30:16.33 +00:55:45.6 Saturn (0.9mag)
03:48:13.18 +19:49:08.6 Uranus (5.8mag)
00:11:09.57 -00:13:22.0 Neptune (7.8mag)
20:33:51.39 -22:52:44.1 Pluto (14.5mag)
02:32:24.01 +18:53:58.2 Moon (-8.4mag)
-rw-r--r-- 1 apache apache 362 Apr 18 06:14 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461148.95597999:
07:13:53.38 +22:44:03.4 Io (5.8mag)
07:13:34.85 +22:44:44.0 Europa (5.9mag)
07:13:29.96 +22:44:50.4 Ganymede (5.4mag)
07:14:10.04 +22:43:23.4 Callisto (6.6mag)
07:17:00.32 +22:30:49.5 Himalia (15.3mag)
07:13:48.43 +22:44:17.1 Thebe (16.2mag)
07:17:14.75 +23:01:08.2 Elara (17.3mag)
07:12:49.66 +23:23:02.1 Pasiphae (17.4mag)
07:22:03.09 +22:42:34.1 Carme (18.5mag)
00:30:08.72 +00:56:10.8 Titan (8.8mag)
00:30:19.84 +00:55:57.2 Rhea (10.1mag)
00:29:52.52 +00:55:31.3 Iapetus (11.5mag)
00:30:15.10 +00:56:13.4 Hyperion (14.8mag)
00:31:51.23 +01:04:17.6 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 18 06:14 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461148.95597999:
15:47:35.70 -17:57:42.2 JWST
21:36:55.26 -31:03:51.0 Chandra
09:12:46.37 -52:36:50.6 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 18 06:14 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461148.95597999 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:52:56.06 -28:55:33.9 13.9mag P/2010 H2 (Vales)
05:08:31.71 -69:32:50.6 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:32:59.74 +31:27:16.0 17.2mag C/2017 K2 (PANSTARRS)
17:30:09.52 +10:50:11.8 17.6mag C/2021 G2 (ATLAS)
23:10:51.28 +29:19:42.0 17.1mag C/2022 E2 (ATLAS)
04:32:06.84 +26:06:14.5 16.0mag C/2022 N2 (PANSTARRS)
09:03:59.46 +32:01:40.0 16.2mag C/2022 QE78 (ATLAS)
08:31:29.07 +00:06:11.0 17.4mag C/2022 R6 (PANSTARRS)
18:53:06.60 +18:44:12.7 17.6mag C/2023 A3 (Tsuchinshan-ATLAS)
15:39:51.11 -11:29:07.8 17.5mag P/2023 B1 (PANSTARRS)
09:06:33.12 -11:29:40.7 17.7mag C/2023 F3 (ATLAS)
21:56:36.41 +63:03:13.1 17.5mag C/2023 H5 (Lemmon)
19:16:57.92 -03:46:36.1 14.1mag C/2023 R1 (PANSTARRS)
21:26:31.13 +86:15:19.6 17.8mag C/2023 X2 (Lemmon)
06:19:08.15 +63:30:14.9 17.2mag C/2024 A1 (ATLAS)
05:18:28.17 +19:05:31.4 11.2mag C/2024 E1 (Wierzchos)
16:17:39.49 +06:47:30.0 17.4mag C/2024 G6 (ATLAS)
20:21:27.20 +15:56:50.9 14.6mag C/2024 J3 (ATLAS)
03:28:35.51 -22:00:56.4 16.3mag C/2024 T5 (ATLAS)
05:18:49.26 +44:41:22.8 17.7mag C/2025 J1 (Borisov)
13:28:41.42 +46:58:03.7 15.3mag C/2025 L1 (ATLAS)
03:29:12.77 -26:36:05.1 17.8mag C/2025 Q3 (ATLAS)
00:09:13.40 +17:28:10.0 8.2mag C/2025 R3 (PANSTARRS)
12:53:03.59 +03:09:33.1 17.4mag C/2025 Y1 (ATLAS)
03:46:32.45 +02:23:21.5 14.0mag C/2026 A1 (MAPS)
00:06:28.17 +37:39:31.7 14.7mag C/2026 B2 (Sun-Gao)
18:47:42.42 -09:35:11.4 11.7mag 10P/Tempel
14:56:56.61 +02:56:36.4 14.2mag 24P/Schaumasse
11:02:10.58 -01:26:57.2 15.7mag 29P/Schwassmann-Wachmann
18:01:33.13 -09:31:22.4 18.0mag 40P/Vaisala
10:37:32.35 -03:54:38.7 17.0mag 43P/Wolf-Harrington
01:52:29.02 +17:54:14.9 17.2mag 47P/Ashbrook-Jackson
07:15:21.06 +36:28:49.1 17.0mag 63P/Wild
23:32:10.14 -11:09:31.1 15.7mag 65P/Gunn
04:09:52.42 +22:05:06.1 15.9mag 76P/West-Kohoutek-Ikemura
01:11:01.60 +08:42:33.4 14.3mag 78P/Gehrels
23:10:22.73 -08:39:52.2 14.6mag 88P/Howell
02:17:24.23 +21:17:19.1 15.1mag 93P/Lovas
04:59:29.37 +32:24:52.3 16.2mag 123P/West-Hartley
08:31:20.27 +37:13:40.7 16.2mag 124P/Mrkos
02:37:01.73 +14:38:30.6 16.4mag 128P/Shoemaker-Holt
02:52:22.14 +14:47:18.4 17.5mag 131P/Mueller
01:39:10.18 +14:03:38.2 10.6mag 141P/Machholz
01:47:43.69 +05:47:28.4 10.6mag 141P-A/Machholz
00:31:54.42 +01:37:23.9 12.5mag 141P-D/Machholz
02:18:13.30 +07:32:56.7 17.9mag 141P-I/Machholz
01:09:14.99 -00:17:14.9 15.0mag 162P/SidingSpring
14:47:04.57 +00:10:23.0 17.7mag 210P/Christensen
21:45:49.41 -10:51:34.6 17.7mag 218P/LINEAR
17:17:02.88 -13:38:09.1 16.1mag 235P/LINEAR
05:39:49.21 +34:52:31.7 16.8mag 240P/NEAT
07:39:44.77 -04:54:24.3 17.7mag 242P/Spahr
22:23:03.29 -20:18:55.9 17.8mag 260P/McNaught
02:03:14.33 +21:04:32.4 18.0mag 295P/LINEAR
15:41:38.72 +07:08:54.3 17.5mag 391P/Kowalski
07:35:10.87 +21:22:16.6 17.7mag 450P/LONEOS
05:39:29.14 +44:53:19.5 17.5mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.9K Apr 18 06:14 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
14:49:14.13 -27:29:20.60 ASASSN-26cu 2026-04-16.06 14.03
17:21:59.44 -38:54:04.60 ASASSN-26ct 2026-04-14.4 15.15
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
14:49:14.13 -27:29:20.60 2026-04-16.06 14.03
12:23:20.40 +04:53:39.10 AT2026ixd 2026-04-12.14 17.65
17:46:09.76 -61:19:50.40 SN2026icy 2026-04-12.2 17.03
09:25:46.42 +02:13:46.30 SN2026gud 2026-04-11.98 16.49
16:52:15.46 -60:27:45.90 ASASSN-26cs 2026-04-12.4 15.5
04:20:55.37 -51:15:31.10 ASASSN-26cr 2026-04-12.01 15.37
22:25:39.35 +36:45:06.90 AT2026ihl 2026-04-10.48 14.21
19:40:44.94 +00:41:03.80 AT2026imw 2026-04-10.32 16.06
19:52:04.70 +05:53:33.50 ASASSN-26cq 2026-04-9.31 14.98
16:08:18.39 -64:11:08.80 ASASSN-26cp 2026-04-9.29 13.32
09:22:22.90 -61:02:43.70 SN2026idh 2026-04-7.97 16.34
05:06:54.12 -19:42:26.40 AT2026imr 2026-04-8 17.49
07:14:55.34 -36:03:21.40 AT2026hei 2026-04-8.12 16.7
21:35:33.14 -19:01:34.80 AT2026ihm 2026-04-8.36 16.7
04:28:24.08 -32:25:35.30 AT2026imo 2026-04-8.02 16.81
05:10:35.79 -39:38:40.80 SN 2026hnn 2026-04-7.04 17.07
09:54:32.04 -01:17:25.80 ASASSN-26cn 2026-04-7.01 15.58
07:46:24.43 -77:29:36.30 ASASSN-26co 2026-04-7.15 15.11
05:00:45.52 -29:51:06.20 AT2026hvw 2026-04-6.03 16.51
19:49:33.10 -23:37:11.00 ASASSN-26cl 2026-04-5.29 14.98
19:32:43.55 -22:39:33.40 ASASSN-26cm 2026-04-4.3 13.88
18:08:57.38 +76:48:23.60 ASASSN-26ck 2026-04-2.37 15.38
16:16:36.10 +44:52:30.20 AT2026hyy 2026-04-2.58 13.81
21:55:23.31 -34:48:53.90 ASASSN-26cj 2026-03-30.4 -1.47
11:19:50.81 -27:51:50.40 SN2026gvk 2026-03-30 15.28
11:53:57.02 -23:09:46.20 SN2026gzx 2026-03-28.75 15.27
07:13:46.14 -33:10:15.70 ASASSN-26ci 2026-03-28.15 15.14
09:03:36.09 -67:58:13.00 SN2026hkg 2026-03-28.19 15.82
07:03:00.72 +39:14:43.00 SN2026fin 2026-03-28.27 15.82
05:35:42.79 -63:44:05.60 ASASSN-26ch 2026-03-28.12 13.14
11:23:19.04 +34:22:38.00 SN2026fwt 2026-03-27.3 16.56
19:03:49.79 +37:04:05.20 ASASSN-26ce 2026-03-26.56 16.3
20:26:56.07 -52:54:06.50 AT2026hiy 2026-03-26.35 16.95
05:25:54.76 -30:15:35.80 ASASSN-26cg 2026-03-25.07 16.88
06:57:16.49 -26:54:37.20 SN2026fzb 2026-03-25.14 15.8
14:37:38.23 -43:00:52.30 ASASSN-26cd 2026-03-24.24 12.52
17:34:53.03 +06:04:29.70 AT2026gzl 2026-03-23.27 15.82
08:30:02.60 -35:12:47.50 ASASSN-26cf 2026-03-23.2 14.82
16:54:25.33 +37:49:56.60 SN 2026evz 2026-03-21.32 17.54
17:06:19.20 -18:54:19.50 ASASSN-26bx 2026-03-21.25 16.39
19:01:16.28 -29:29:23.10 ASASSN-26bw 2026-03-21.33 15.81
08:46:05.75 +10:47:39.80 ASASSN-26ca 2026-03-21.13 14.27
12:14:58.16 +63:47:16.20 SN 2026fvx 2026-03-21.12 15.6
18:02:55.90 -75:23:02.60 ASASSN-26bz 2026-03-21.32 16.16
12:16:02.87 -53:16:33.70 ASASSN-26cc 2026-03-20.08 3.93
13:08:21.85 +29:13:44.20 SN 2026fmh 2026-03-20.16 -0.33
19:56:38.48 -34:45:21.50 ASASSN-26cb 2026-03-20.35 -3.26
14:32:41.15 -41:38:48.50 ASASSN-26by 2026-03-20.15 -1.31
13:00:42.99 +37:18:34.60 SN2026fjc 2026-03-19.5 15.97
06:02:44.21 -04:11:06.20 ASASSN-26bv 2026-03-19.19 15.67
12:20:27.90 -45:55:38.40 ASASSN-26bt 2026-03-19.05 16.24
07:49:57.30 -56:14:35.10 ASASSN-26bu 2026-03-19.19 15.74
06:04:29.75 +53:23:34.00 SN 2026eza 2026-03-18.2 17.48
11:54:57.87 +69:19:28.90 AT2026fsf 2026-03-18.14 16.95
10:44:46.95 +58:27:29.30 SN 2026enn 2026-03-18.13 17.53
20:45:54.04 -73:26:43.00 AT 2026ezy 2026-03-18.13 16.83
06:53:18.10 -59:10:49.30 ASASSN-26bs 2026-03-18.02 16.93
07:45:09.29 -62:14:36.20 ASASSN-26br 2026-03-16.16 16.78
19:24:27.93 -52:04:36.40 AT 2023uk 2026-03-16.35 14.2
04:52:54.50 -15:20:57.10 AT2026fhw 2026-03-14.06 SDSS
11:10:34.24 +02:58:48.10 SN2026drr 2026-03-14.08 0.2
07:26:45.73 -27:45:13.90 ASASSN-26bo 2026-03-14.17 13.8
16:35:46.94 +58:12:28.40 SN2026ebt 2026-03-12.41 17.12
13:01:19.45 +15:42:15.00 SN2026ehe 2026-03-12.11 -0.29
09:15:55.41 +10:08:09.70 SN2026efq 2026-03-12.16 0.06
03:31:20.92 -35:29:29.00 SN2026evh 2026-03-12.05 17.29
06:26:19.15 -85:18:28.10 AT2026ffp 2026-03-12.16 0.37
14:16:42.30 -41:18:36.50 AT2026fij 2026-03-12.05 15.97
10:45:04.71 +00:06:13.10 SN 2026exe 2026-03-11.78 16.48
18:07:45.58 +69:43:01.00 SN2026ess 2026-03-12.37 17.37
13:11:03.58 +49:06:31.80 AT2026ewa 2026-03-12.42 16.77
15:03:25.23 -63:11:22.20 ASASSN-26bp 2026-03-11.92 13.33
13:09:37.25 -35:50:25.20 AT2024cmo 2026-03-11.12 16.29
13:06:01.97 -15:50:14.40 AT2026fdy 2026-03-10.33 16.68
11:30:09.67 -47:26:43.70 ASASSN-26bn 2026-03-10.12 15.2
05:03:25.25 -24:16:50.40 (= Gaia 2026-03-9.09 14.32
03:42:32.53 -04:17:53.70 ASASSN-26bm 2026-03-8.04 15.22
04:31:00.53 -68:29:50.20 ASASSN-26bl 2026-03-7.9 10.26
16:18:17.61 +41:25:11.40 SN 2026dkf 2026-03-6.31 16.7
13:45:00.35 +61:16:50.90 SN 2026ejl 2026-03-6.41 -0.66
09:27:45.48 -37:49:32.80 ASASSN-26bk 2026-03-2.3 13.11
20:22:01.20 +23:47:47.30 ASASSN-26bi 2026-02-28.51 15.86
11:16:22.10 +29:26:22.80 AT2026enm 2026-02-28.39 16.88
08:05:59.83 -48:39:35.60 ASASSN-26bh 2026-02-26.05 14.64
13:24:27.02 -45:57:01.40 ASASSN-26bg 2026-02-26.35 15.28
17:27:50.95 -68:28:46.40 ASASSN-26bf 2026-02-26.3 16.28
18:03:39.37 +19:58:46.70 ASASSN-26be 2026-02-25.58 14.8
17:40:18.19 +07:20:59.60 SN 2026crm 2026-02-24.34 16.9
18:38:36.11 -79:28:58.40 ASASSN-26bb 2026-02-24.36 16.11
17:43:29.75 +11:24:00.60 ASASSN-26bc 2026-02-23.37 -3.37
16:59:41.08 -80:01:51.20 ASASSN-26bd 2026-02-23.3 14.38
11:23:31.77 -08:39:15.40 SN2026cff 2026-02-23.15 -1.08
14:55:17.39 -05:56:05.30 SN2026dmk 2026-02-23.22 -0.76
12:28:15.19 +44:27:20.80 SN2026cjz 2026-02-23.47 15.62
12:12:29.55 -02:40:43.30 AT2026dsk 2026-02-23.4 17.21
09:21:05.29 +06:11:42.80 SN2026chr 2026-02-23.1 17.39
16:05:38.61 +18:06:07.40 SN 2026dsy 2026-02-23.36 17.15
-rw-r--r-- 1 apache apache 5.8K Apr 18 06:14 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 18 06:14 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
15:41:49.181 +10:03:08.67 AT 2026jgt 2026-04-10.94 19.05
16:05:45.225 +39:19:22.46 AT 2026jgs 2026-04-11.08 19.85
17:09:17.180 +58:08:27.31 AT 2026jgr 2026-04-10.97 20.21
14:27:07.800 +63:03:09.75 AT 2026jgq 2026-04-07.96 19.63
21:24:26.763 +17:46:17.22 AT 2026jgp 2026-04-10.51 19.5235
21:11:00.071 -12:31:56.57 AT 2026jgo 2026-04-10.51 17.9913
17:04:17.414 +05:53:27.19 AT 2026jgn 2026-04-10.42 20.0079
16:20:49.652 -00:22:10.33 AT 2026jgm 2026-04-10.42 19.437
12:38:24.734 +21:15:54.35 AT 2026jgl 2026-04-10.28 20.5723
13:24:21.892 +04:47:40.06 AT 2026jgk 2026-04-10.27 20.106
12:51:33.318 -00:15:04.90 AT 2026jgj 2026-04-10.27 19.4096
12:05:14.424 +12:01:26.77 AT 2026jgi 2026-04-10.26 20.2481
22:30:32.862 +33:06:00.06 AT 2026jgh 2026-04-08.51 19.6664
16:11:58.319 -09:00:29.25 AT 2026jgg 2026-04-08.41 19.9237
15:03:38.583 +10:04:47.83 AT 2026jgf 2026-04-07.47 20.0529
15:26:23.672 +05:34:01.67 AT 2026jge 2026-04-07.34 20.2566
14:13:26.808 +12:46:43.53 AT 2026jgd 2026-04-07.28 20.201
16:00:54.694 +34:45:50.57 AT 2026jgc 2026-04-07.50 19.9668
16:30:49.348 -18:08:16.31 AT 2026jgb 2026-03-28.50 20.531
13:20:44.619 +15:48:51.00 AT 2026jga 2026-04-10.29 19.1395
-rw-r--r-- 1 apache apache 30K Apr 18 06:14 tns_transients_list.txt
