This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq
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 06.4319* 23 31 11.01 +58 36 31.4 10.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,10.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
target 20260406.4319 10.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 06.4319* 23 49 03.26 +61 01 27.2 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,11.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
target 20260406.4319 11.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 06.4319* 23 43 25.25 +61 39 45.1 11.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,11.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 20260406.4319 11.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 06.4319* 00 35 25.81 +61 14 50.3 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
V1302 Cas,2461136.9319,11.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
V1302 Cas 20260406.4319 11.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 06.4319* 00 35 02.75 +61 19 05.8 10.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
V0826 Cas,2461136.9319,10.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
V0826 Cas 20260406.4319 10.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 06.4319* 00 18 48.96 +63 06 00.8 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 431373119208759168,2461136.9319,13.94,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 431373119208759168 20260406.4319 13.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 28 23.23 +62 02 49.4 14.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,14.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 20260406.4319 14.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 38 15.45 +60 57 58.2 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 57 46.55 +60 12 20.1 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 24 12.98 +62 15 51.0 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.79,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 20260406.4319 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 38 04.25 +61 30 33.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2012530793400489856,2461136.9319,13.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 2012530793400489856 20260406.4319 13.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 06.4319* 00 11 24.44 +57 49 31.2 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J002.8566+57.8227,2461136.9319,13.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
ATO J002.8566+57.8227 20260406.4319 13.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 06.4319* 23 40 46.93 +63 26 00.8 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 00 07 58.15 +63 26 00.0 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 36 31.47 +61 28 53.4 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 23 26 10.25 +61 31 23.9 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 00 15 59.43 +59 25 38.1 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.04,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 20260406.4319 13.04CV 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 06.4319* 00 26 46.37 +63 59 09.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 00 20 48.63 +62 51 16.8 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 430614761127483264,2461136.9319,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
Gaia DR3 430614761127483264 20260406.4319 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 06.4319* 23 26 17.55 +61 37 44.7 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 00 32 05.19 +63 08 18.6 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J003205.87+630814.5,2461136.9319,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
ZTF J003205.87+630814.5 20260406.4319 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 09 55.25 +62 32 56.4 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.04,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 20260406.4319 13.04CV 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 06.4319* 23 45 44.95 +58 00 45.6 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J356.4580+58.0106,2461136.9319,12.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
ATO J356.4580+58.0106 20260406.4319 12.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 06.4319* 23 27 29.73 +61 19 46.5 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 51 31.92 +62 59 46.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 00 34 26.87 +62 34 19.4 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.85,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 20260406.4319 12.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 05 25.60 +57 56 06.7 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.69,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 20260406.4319 12.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 09 33.62 +63 07 45.7 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.78,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 20260406.4319 12.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 37 38.49 +58 39 30.2 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.83,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 20260406.4319 12.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 06 35.71 +58 24 28.0 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J001.6500+58.4074,2461136.9319,12.25,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.6500+58.4074 20260406.4319 12.25CV 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 06.4319* 23 26 29.01 +61 35 35.1 11.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,11.14,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 20260406.4319 11.14CV 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 06.4319* 23 26 34.43 +61 35 52.6 11.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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
target 20260406.4319 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 06.4319* 23 26 41.99 +61 22 03.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,11.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 20260406.4319 11.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 06.4319* 23 47 31.94 +58 42 08.7 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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
target 20260406.4319 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 06.4319* 00 10 03.32 +63 53 17.8 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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
target 20260406.4319 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 06.4319* 00 01 54.33 +60 18 55.9 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J000.4673+60.3247,2461136.9319,11.78,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.4673+60.3247 20260406.4319 11.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 26 04.39 +61 37 32.3 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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
target 20260406.4319 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 06.4319* 23 38 38.69 +58 52 39.6 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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
target 20260406.4319 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 06.4319* 23 51 50.90 +63 54 05.5 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.14,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 20260406.4319 12.14CV 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 06.4319* 00 21 26.32 +59 14 02.1 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
FQ Cas,2461136.9319,11.87,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
FQ Cas 20260406.4319 11.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 55 54.85 +58 07 04.6 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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
target 20260406.4319 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 06.4319* 00 09 01.76 +63 07 17.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 431513994152510208,2461136.9319,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 431513994152510208 20260406.4319 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 06.4319* 23 26 17.87 +61 36 33.3 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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
target 20260406.4319 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 06.4319* 00 20 37.05 +61 51 30.4 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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
target 20260406.4319 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 06.4319* 23 27 15.58 +60 49 00.4 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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
target 20260406.4319 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 06.4319* 23 34 45.43 +60 27 13.3 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2012215753257632000,2461136.9319,12.42,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 2012215753257632000 20260406.4319 12.42CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 44 34.01 +61 05 32.3 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.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
target 20260406.4319 12.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.66,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 20260406.4319 12.66CV 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 06.4319* 23 28 09.79 +61 53 50.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.66,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 20260406.4319 12.66CV 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 06.4319* 23 26 43.14 +61 35 11.3 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.69,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 20260406.4319 12.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 06 52.80 +58 55 09.7 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.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
target 20260406.4319 12.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 06.4319* 00 09 22.42 +59 39 23.2 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J002.3361+59.6510,2461136.9319,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 J002.3361+59.6510 20260406.4319 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 06.4319* 23 26 03.65 +61 37 02.5 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.66,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 20260406.4319 12.66CV 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 06.4319* 00 21 01.14 +62 26 01.7 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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 20260406.4319 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 06.4319* 23 32 37.01 +57 30 48.6 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1998814733743492736,2461136.9319,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 1998814733743492736 20260406.4319 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 06.4319* 00 36 59.53 +63 06 29.7 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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 20260406.4319 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 06.4319* 23 58 05.29 +61 02 12.8 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2011698879716758400,2461136.9319,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 2011698879716758400 20260406.4319 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 06.4319* 23 43 43.41 +61 38 14.8 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.70,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 20260406.4319 12.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.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 20260406.4319 12.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 06.4319* 23 26 51.14 +62 16 38.9 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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 20260406.4319 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 06.4319* 00 17 16.92 +63 30 59.0 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 431422425444350336,2461136.9319,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 431422425444350336 20260406.4319 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 06.4319* 23 37 59.23 +58 00 52.3 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J233800.31+580058.6,2461136.9319,12.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
ZTF J233800.31+580058.6 20260406.4319 12.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 06.4319* 23 26 52.99 +62 16 40.8 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.87,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 20260406.4319 12.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 41 58.52 +61 46 52.3 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2012904081908125696,2461136.9319,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
Gaia DR3 2012904081908125696 20260406.4319 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 06.4319* 23 29 43.41 +61 28 56.8 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J232941.64+612901.6,2461136.9319,12.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
ZTF J232941.64+612901.6 20260406.4319 12.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 39 48.56 +61 18 30.8 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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 20260406.4319 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 06.4319* 00 19 07.94 +60 19 14.6 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.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
target 20260406.4319 12.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 06.4319* 00 34 19.76 +58 51 51.7 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 425026630717538560,2461136.9319,12.59,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 425026630717538560 20260406.4319 12.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 03 24.94 +66 01 13.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.00,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 20260406.4319 13.00CV 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 06.4319* 00 01 50.25 +60 18 56.9 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J000.4673+60.3247,2461136.9319,12.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
ATO J000.4673+60.3247 20260406.4319 12.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 06.4319* 23 25 40.90 +62 47 48.9 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 23 25 59.79 +62 32 19.6 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.20,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 20260406.4319 13.20CV 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 06.4319* 23 25 24.29 +60 28 50.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2012359475744686464,2461136.9319,13.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 2012359475744686464 20260406.4319 13.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!
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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 00 15 23.05 +58 25 48.9 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J003.8126+58.4254,2461136.9319,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
ATO J003.8126+58.4254 20260406.4319 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 06.4319* 23 47 05.27 +61 58 45.6 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.04,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 20260406.4319 13.04CV 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 06.4319* 23 32 30.76 +59 11 13.6 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 58 46.13 +61 10 36.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 00 17 04.16 +63 32 12.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 00 27 05.57 +60 41 10.0 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.83,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 20260406.4319 12.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 26 04.87 +61 40 44.4 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.22CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 12 27.63 +62 50 58.4 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 47 07.27 +61 58 00.1 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 30 34.22 +61 21 23.8 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 26 14.50 +61 36 34.8 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 00 09 31.62 +58 40 30.1 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J002.3916+58.6834,2461136.9319,12.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
ATO J002.3916+58.6834 20260406.4319 12.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 06.4319* 00 35 14.84 +62 59 25.6 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 430725850467231488,2461136.9319,12.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
Gaia DR3 430725850467231488 20260406.4319 12.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 06.4319* 00 31 26.40 +63 18 40.5 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 430792817600836352,2461136.9319,12.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 430792817600836352 20260406.4319 12.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 06.4319* 00 24 05.24 +61 20 00.7 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NO Cas,2461136.9319,12.89,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
NO Cas 20260406.4319 12.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 34 23.22 +62 34 15.1 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.00,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 20260406.4319 13.00CV 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 06.4319* 00 18 55.71 +61 24 45.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.03,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 20260406.4319 13.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 39 25.70 +58 42 32.0 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.11,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 20260406.4319 13.11CV 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 06.4319* 00 18 18.63 +65 29 22.2 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 23 41 00.00 +61 53 50.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 26 04.60 +61 35 23.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 23 57 05.06 +64 54 34.7 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 41 50.50 +61 46 41.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2012904081908125696,2461136.9319,13.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 2012904081908125696 20260406.4319 13.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 06.4319* 23 59 41.66 +63 30 22.5 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J359.8943+63.5019,2461136.9319,13.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
ATO J359.8943+63.5019 20260406.4319 13.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 06.4319* 23 45 13.66 +62 42 06.1 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 59 07.25 +60 39 40.5 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 00 00 55.89 +60 21 27.8 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 26 24.59 +62 17 17.3 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 51 37.24 +58 59 18.7 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 49 34.29 +61 16 01.9 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 00 00 00.67 +60 17 24.7 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 52 12.52 +62 33 17.4 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J235210.56+623326.6,2461136.9319,13.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
ZTF J235210.56+623326.6 20260406.4319 13.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 06.4319* 23 33 45.36 +57 56 36.5 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 00 17 29.59 +62 48 13.1 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 23 48 30.54 +57 53 11.4 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 00 15 35.26 +61 43 39.1 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 00 02 26.20 +63 18 45.8 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 431589276337302656,2461136.9319,13.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
Gaia DR3 431589276337302656 20260406.4319 13.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 06.4319* 23 54 14.18 +64 19 24.5 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 00 19 08.65 +63 51 02.8 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 59 35.83 +63 32 19.3 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 00 30 07.45 +60 07 45.6 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 00 05 21.48 +58 33 56.0 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.17,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 20260406.4319 13.17CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 07 02.70 +63 11 02.0 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 431528524016120576,2461136.9319,13.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
Gaia DR3 431528524016120576 20260406.4319 13.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 06.4319* 00 27 11.54 +60 23 29.4 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.20,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 20260406.4319 13.20CV 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 06.4319* 23 58 38.93 +62 34 50.2 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2012825260667144576,2461136.9319,13.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
Gaia DR3 2012825260667144576 20260406.4319 13.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 06.4319* 23 36 49.09 +62 15 17.8 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 25 14.20 +60 31 01.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.33CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 23 48.89 +61 21 10.2 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2015644442834536832,2461136.9319,13.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 2015644442834536832 20260406.4319 13.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 06.4319 2461136.9319 13.14 00:30:35.68 +62:20:56.5
120.51621 -0.42492 galactic Cas Second-epoch detections are separated by 6.8" and 7.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 430360915687082880 | 00:30:41.63 +62:21:14.4 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=VARIABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: B 1966UppAn...5d...1O [O66] 8:1145
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 06.4319* 00 30 35.68 +62 20 56.5 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 430360915687082880,2461136.9319,13.14,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 430360915687082880 20260406.4319 13.14CV 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 06.4319* 00 19 29.64 +62 41 18.6 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 431266535312656384,2461136.9319,13.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 431266535312656384 20260406.4319 13.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 06.4319* 00 09 31.52 +64 59 41.6 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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!
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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 56 58.03 +66 02 55.8 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 00 20 25.46 +62 02 12.6 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.22CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 41 45.24 +61 51 28.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 23 44 20.84 +62 52 52.9 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 23 51 41.08 +59 40 49.2 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 06 48.23 +63 18 52.6 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.44,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 20260406.4319 13.44CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 24 12.00 +62 36 19.4 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 24 42.80 +58 11 37.7 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.80,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 20260406.4319 13.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 02 02.36 +61 10 40.0 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 429480894069202432,2461136.9319,13.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 429480894069202432 20260406.4319 13.45CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 10 56.22 +59 42 02.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.20,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 20260406.4319 13.20CV 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 06.4319* 00 15 25.01 +59 45 55.5 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 41 17.56 +62 00 26.0 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2015924195521105024,2461136.9319,13.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
Gaia DR3 2015924195521105024 20260406.4319 13.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 06.4319* 00 29 19.18 +63 26 57.3 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 430985644451644928,2461136.9319,13.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 430985644451644928 20260406.4319 13.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 06.4319* 00 27 11.16 +60 41 49.8 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 428836511532472960,2461136.9319,13.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 428836511532472960 20260406.4319 13.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 06.4319* 00 00 05.72 +60 16 33.9 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 16 02.01 +63 07 33.7 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.52,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 20260406.4319 13.52CV 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 06.4319* 00 16 13.19 +61 01 18.1 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 429571913013933568,2461136.9319,13.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
Gaia DR3 429571913013933568 20260406.4319 13.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 00 10 35.90 +60 01 34.8 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J002.6312+60.0252,2461136.9319,13.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
ATO J002.6312+60.0252 20260406.4319 13.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 06.4319* 00 02 01.98 +60 27 38.2 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J000204.34+602726.2,2461136.9319,13.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
ZTF J000204.34+602726.2 20260406.4319 13.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 05 37.84 +61 16 37.9 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 23 25 23.48 +58 31 24.7 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 02 25.07 +63 14 01.8 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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
Mean magnitude and position on the discovery images:
2026 04 06.4319 2461136.9319 13.49 00:07:42.99 +63:05:50.4
118.00977 0.64418 galactic Cas Second-epoch detections are separated by 6.4" and 6.7 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 431515879625201920 | 00:07:41.42 +63:05:15.3 (Gaia DR3) | 2021A&A...648A..44M | | Gaia3var=NOT_AVAILABLE (the VSX policy as of May 2022 seems to be NOT to regard variables from 2021A&A...648A..44M as 'known' for the lack of classification)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 07 42.99 +63 05 50.4 13.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.0rc89 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 431515879625201920,2461136.9319,13.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
Large-amplitude variable Gaia DR2 431515879625201920 20260406.4319 13.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 06.4319* 23 48 29.17 +63 09 26.4 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J234827.94+630947.3,2461136.9319,13.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
ZTF J234827.94+630947.3 20260406.4319 13.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 06.4319* 23 33 59.78 +62 15 36.4 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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
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 06.4319* 00 00 08.14 +64 23 02.6 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 43 52.88 +61 33 20.7 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2012842165655452288,2461136.9319,13.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 2012842165655452288 20260406.4319 13.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 06.4319* 00 08 40.03 +63 17 13.4 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 59 50.78 +64 23 14.2 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 36 12.52 +63 34 55.6 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 28 41.35 +63 28 45.8 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.79,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 20260406.4319 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 42 59.68 +60 49 40.9 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2012570277044984064,2461136.9319,13.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 2012570277044984064 20260406.4319 13.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 06.4319* 23 37 37.18 +61 42 23.7 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 52 08.17 +61 11 17.9 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2011933964748119424,2461136.9319,13.60,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 2011933964748119424 20260406.4319 13.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 43 20.89 +61 27 22.4 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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
target 20260406.4319 13.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 06.4319* 23 29 39.29 +61 52 56.4 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 00 19 02.40 +61 25 24.0 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 428930107461052928,2461136.9319,13.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
Gaia DR3 428930107461052928 20260406.4319 13.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,14.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 20260406.4319 14.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,14.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
target 20260406.4319 14.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 35 49.18 +65 24 23.0 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.82,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 20260406.4319 13.82CV 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 06.4319* 23 34 44.88 +61 28 01.7 14.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,14.04,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 20260406.4319 14.04CV 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 06.4319* 23 37 05.98 +61 09 49.2 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,14.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 20260406.4319 14.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 00 18 51.74 +59 05 34.2 11.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS 1566905,2461136.9319,11.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
NSVS 1566905 20260406.4319 11.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 06.4319* 00 08 35.68 +60 36 18.8 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,13.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 20260406.4319 13.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 06.4319* 23 37 13.88 +62 01 38.6 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2015607811047868928,2461136.9319,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
Gaia DR3 2015607811047868928 20260406.4319 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 06.4319* 00 35 53.37 +60 37 13.0 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J003553.23+603714.5,2461136.9319,12.04,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
ASASSN-V J003553.23+603714.5 20260406.4319 12.04CV 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 06.4319* 00 28 33.93 +59 15 25.3 13.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
MNIC V9,2461136.9319,12.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
MNIC V9 20260406.4319 12.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 06.4319* 00 20 25.33 +62 06 04.6 9.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,9.58,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 20260406.4319 9.58CV 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 06.4319* 23 55 07.77 +58 44 60.0 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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
target 20260406.4319 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 06.4319* 00 34 25.49 +64 30 20.7 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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 20260406.4319 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 06.4319* 23 57 48.00 +58 26 27.4 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.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
target 20260406.4319 12.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 06.4319* 00 12 45.81 +62 44 21.6 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 431305018222881920,2461136.9319,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
Gaia DR3 431305018222881920 20260406.4319 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 06.4319* 00 28 08.68 +60 29 31.2 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSV 168,2461136.9319,11.52,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
NSV 168 20260406.4319 11.52CV 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 06.4319* 00 34 42.72 +65 36 40.7 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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 20260406.4319 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 06.4319* 23 41 13.20 +63 17 37.1 11.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J234111.26+631757.0,2461136.9319,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
ZTF J234111.26+631757.0 20260406.4319 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 06.4319* 00 04 55.82 +60 17 56.6 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,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 20260406.4319 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 06.4319* 00 34 31.28 +61 56 32.4 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J0034316+615643,2461136.9319,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
NSVS J0034316+615643 20260406.4319 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 06.4319* 00 32 54.77 +58 24 23.8 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J003254.54+582420.6,2461136.9319,12.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
ASASSN-V J003254.54+582420.6 20260406.4319 12.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 06.4319* 00 39 16.58 +64 26 56.1 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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461136.9319,12.59,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 20260406.4319 12.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 06.4319* 23 26 51.95 +60 57 38.0 12.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.0rc89 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2015390524370242560,2461136.9319,12.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
Gaia DR3 2015390524370242560 20260406.4319 12.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
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461036.58829464 27.12.2025 02:06:58.657 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
First image: 2461036.58829464 27.12.2025 02:06:58.657 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Last image: 2461136.93230062 06.04.2026 10:22:20.774 /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 11
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.98
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): 21652
Objects passed selection criteria: 21530
Measurements per detected object (mean, median, min, max): 2.7 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.7 2.0 2 4
Average stars detected per image: 15075
Average stars matched: 13893.5 (92.1625 %)
Memory usage VmPeak: 124720 kB
Software: VaST 1.0rc89 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Fri Apr 3 15:05:04 CDT 2026
VaST build number 1.0rc88-382-g85e3caff
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-03)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Mon Apr 6 05:44:31 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.58829464 27.12.2025 02:06:58.657 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
First image: 2461036.58829464 27.12.2025 02:06:58.657 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Last image: 2461136.93230062 06.04.2026 10:22:20.774 /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 303
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.61
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: 76 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): 146392
Objects passed selection criteria: 145992
Measurements per detected object (mean, median, min, max): 2.7 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.7 2.0 2 4
Average stars detected per image: 106422
Average stars matched: 97070.5 (91.213 %)
Memory usage VmPeak: 1907048 kB
Software: VaST 1.0rc89 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Fri Apr 3 15:05:04 CDT 2026
VaST build number 1.0rc88-382-g85e3caff
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-03)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Mon Apr 6 05:54:32 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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
SExtractor catalog cache: saved Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat to cache
SExtractor catalog cache: saved Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.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: 2461136.93152927
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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits exists and is non-empty
Saving wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits to local_wcs_cache/
'wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits' -> 'local_wcs_cache/wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits'
wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits exists and is non-empty
Saving wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits to local_wcs_cache/
'wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits' -> 'local_wcs_cache/wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits'
wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits exists and is non-empty
Saving wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits to local_wcs_cache/
'wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits' -> 'local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits'
wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits exists and is non-empty
Saving wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits to local_wcs_cache/
'wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits' -> 'local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits'
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 00:00:01.853 +61:59:36.76
Second-epoch image center 00:00:30.655 +61:58:33.70
Angular distance between the image centers 0.0590 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 00:00:01.853 +61:59:36.76
Second-epoch image center 00:00:33.827 +61:59:09.64
Angular distance between the image centers 0.0630 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 00:00:30.655 +61:58:33.70
Second-epoch second image center 00:00:33.827 +61:59:09.64
Angular distance between the image centers 0.01176 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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits &> /tmp/tmp.wdF3KbYNjc
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits &> /tmp/tmp.WSw14J1lAn
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits &> /tmp/tmp.CZ1bFMC5nb
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits &> /tmp/tmp.X7ZisBGYV5
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
Calibrating the magnitude scale
Found non-empty wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits and wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits and wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
Found non-empty wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits and wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
The reference image (wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits) and catalog (wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat) found
'wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat' -> 'wcsmag.cat'
Read 25547 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0005 to 359.9978 deg, Dec +55.3501 to +67.4045 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.0005 to 359.9978 deg, Dec 55.3501 to 67.4045 deg
Loaded 133072 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): 14110 out of 15859 total matches.
Matched with Tycho-2 15859 out of 25547 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.955169
a=0.000000 b=1.000000 c=22.955169
From vast_summary.log: estimated ref. image limiting mag.: -7.98
Updating vast_summary.log: Estimated ref. image limiting mag.: 14.98
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 14.98
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 8 candidate transients before the final filtering. (Hard limit: 3000)
Median FWHM seeing for isolated stars:
2.5 pix Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
2.5 pix Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
2.6 pix fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
2.6 pix fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
Limiting magnitude estimates:
15.0 mag. Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
15.0 mag. Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
14.1 mag. fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
14.1 mag. fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
All-image limiting magnitude estimate: 14.1 (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.wdF3KbYNjc (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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits' -> 'wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WCS-calibrated image found: wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Checking if the catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WCS catalog name: wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=3206, passed=25547
Got 25547 stars (including 22312 good ones) from the SExtractor catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
util/solve_plate_with_UCAC5 got 25547 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 341.2187 through 0 to 19.8663, gap 19.8663 to 341.2187
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.4 to 67.4)
Done reading UCAC5 zone files...
Matched 977 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 976 matched stars entering correct_measured_positions(), 950 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.54"
Removing outliers...
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 976 matched stars entering correct_measured_positions(), 24870 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.47"
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 341.2185 through 0 to 19.8666, gap 19.8666 to 341.2185
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.4 to 67.4)
Done reading UCAC5 zone files...
Matched 977 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
WARNING: Accuracy estimation diagnostic: 976 matched stars entering correct_measured_positions(), 24870 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.47"
WARNING: Accuracy estimation diagnostic: 976 matched stars entering correct_measured_positions(), 24870 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.48"
Excluding outliers - 976 stars left (next iteration limit 1073)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits -region wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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.WSw14J1lAn (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/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits' -> 'wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WCS-calibrated image found: wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
Checking if the catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WCS catalog name: wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=3160, passed=25477
Got 25477 stars (including 22297 good ones) from the SExtractor catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat
util/solve_plate_with_UCAC5 got 25477 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 341.2186 through 0 to 19.8660, gap 19.8660 to 341.2186
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.4 to 67.4)
Done reading UCAC5 zone files...
Matched 978 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 944 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.58"
Removing outliers...
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 24335 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.52"
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 341.2185 through 0 to 19.8672, gap 19.8672 to 341.2185
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 978 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
WARNING: Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 24333 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.52"
WARNING: Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 24332 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.55"
Excluding outliers - 977 stars left (next iteration limit 1074)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits -region wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.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.CZ1bFMC5nb (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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1042, passed=12841
Got 12841 stars (including 11793 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat
util/solve_plate_with_UCAC5 got 12841 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.1'
Seting catalog search parameters based on the expected field of view 924.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012835 (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.010268 (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 341.6611 through 0 to 19.0509, gap 19.0509 to 341.6611
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 56.0 to 67.2)
Done reading UCAC5 zone files...
Matched 339 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 263 matched stars entering correct_measured_positions(), 193 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.67"
Removing outliers...
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 255 matched stars entering correct_measured_positions(), 3426 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.55"
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 341.6675 through 0 to 19.0561, gap 19.0561 to 341.6675
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 368 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
WARNING: Accuracy estimation diagnostic: 306 matched stars entering correct_measured_positions(), 3454 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.54"
WARNING: Accuracy estimation diagnostic: 301 matched stars entering correct_measured_positions(), 3820 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.05"
Excluding outliers - 301 stars left (next iteration limit 280)
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits -region wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.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.X7ZisBGYV5 (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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1057, passed=12931
Got 12931 stars (including 11865 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat
util/solve_plate_with_UCAC5 got 12931 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.1'
Seting catalog search parameters based on the expected field of view 924.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012835 (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.010268 (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 341.6631 through 0 to 19.0508, gap 19.0508 to 341.6631
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 56.0 to 67.2)
Done reading UCAC5 zone files...
Matched 335 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 254 matched stars entering correct_measured_positions(), 183 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.26"
Removing outliers...
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 245 matched stars entering correct_measured_positions(), 3213 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.72"
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 341.6670 through 0 to 19.0555, gap 19.0555 to 341.6670
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 365 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
WARNING: Accuracy estimation diagnostic: 300 matched stars entering correct_measured_positions(), 3234 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.69"
WARNING: Accuracy estimation diagnostic: 299 matched stars entering correct_measured_positions(), 3727 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.01"
Excluding outliers - 299 stars left (next iteration limit 269)
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits -region wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits'
Saving fully-calibrated image wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits'
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits'
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits'
Preparing the HTML report for the field Cas-02-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Adding exclusion_list_local.txt__out10459.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out10636.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31913.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out32866.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out33050.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 20s
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: 4s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31913_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 31913_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32843_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 32843_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32866_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 32866_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32915_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 32915_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33050_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 33050_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33897_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 33897_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 10636_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 10636_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 10459_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 10459_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
make_report_in_HTML.sh Phase 2 (HTML assembly): 0s
make_report_in_HTML.sh TOTAL: 24s
Prepared the HTML report for the field Cas-02-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 ####
00:35:02.75 +61:19:05.8
00:35:25.81 +61:14:50.3
23:31:11.01 +58:36:31.4
23:49:03.26 +61:01:27.2
23:43:25.25 +61:39:45.1
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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
SExtractor catalog cache: saved Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat to cache
SExtractor catalog cache: saved Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Creating symlink local_wcs_cache/wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
Creating symlink local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
Creating symlink local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits exists and is non-empty
wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits exists and is non-empty
wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits exists and is non-empty
wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits exists and is non-empty
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 00:00:01.853 +61:59:36.76
Second-epoch image center 00:00:30.655 +61:58:33.70
Angular distance between the image centers 0.0590 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 00:00:01.853 +61:59:36.76
Second-epoch image center 00:00:33.827 +61:59:09.64
Angular distance between the image centers 0.0630 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 00:00:30.655 +61:58:33.70
Second-epoch second image center 00:00:33.827 +61:59:09.64
Angular distance between the image centers 0.01176 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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits &> /tmp/tmp.7WPzRnAVrZ
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits &> /tmp/tmp.1p1MafOOx3
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits &> /tmp/tmp.RiwZQImTZI
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits &> /tmp/tmp.2ubOK2qWMK
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
Calibrating the magnitude scale
Found non-empty wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits and wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits and wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
Found non-empty wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits and wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
The reference image (wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits) and catalog (wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat) found
'wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat' -> 'wcsmag.cat'
Read 170710 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0001 to 360.0000 deg, Dec +55.3116 to +67.4209 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 360.0000 deg, Dec 55.3116 to 67.4209 deg
Loaded 133731 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): 10993 out of 16914 total matches.
Matched with Tycho-2 16914 out of 170710 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.762297
a=0.000000 b=1.000000 c=22.762297
From vast_summary.log: estimated ref. image limiting mag.: -7.61
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.15
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.15
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 272 candidate transients before the final filtering. (Hard limit: 3000)
Median FWHM seeing for isolated stars:
2.3 pix Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
2.3 pix Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
2.4 pix fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
2.4 pix fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
Limiting magnitude estimates:
15.1 mag. Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
15.1 mag. Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
14.3 mag. fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
14.3 mag. fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
All-image limiting magnitude estimate: 14.3 (SNR ) 13.7 (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.7WPzRnAVrZ (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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits' -> 'wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WCS-calibrated image found: wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Checking if the catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WCS catalog name: wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=35, blended=28495, passed=170675
Got 170675 stars (including 141953 good ones) from the SExtractor catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
util/solve_plate_with_UCAC5 got 170675 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 341.2187 through 0 to 20.1102, gap 20.1102 to 341.2187
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 975 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 959 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.53"
Removing outliers...
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 167939 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.51"
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 341.2185 through 0 to 20.1102, gap 20.1102 to 341.2185
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 975 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
WARNING: Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 167939 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.51"
WARNING: Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 167944 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.54"
Excluding outliers - 974 stars left (next iteration limit 1071)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits -region wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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.1p1MafOOx3 (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/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits' -> 'wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WCS-calibrated image found: wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
Checking if the catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WCS catalog name: wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=60, blended=28344, passed=170985
Got 170985 stars (including 142400 good ones) from the SExtractor catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat
util/solve_plate_with_UCAC5 got 170985 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 341.2186 through 0 to 20.0818, gap 20.0818 to 341.2186
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 973 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 953 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.55"
Removing outliers...
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 166835 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.53"
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 341.2184 through 0 to 20.0827, gap 20.0827 to 341.2184
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 973 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
WARNING: Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 166834 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.53"
WARNING: Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 166834 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.56"
Excluding outliers - 972 stars left (next iteration limit 1069)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits -region wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.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.RiwZQImTZI (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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=10, blended=8447, passed=85691
Got 85691 stars (including 77181 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat
util/solve_plate_with_UCAC5 got 85691 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.1'
Seting catalog search parameters based on the expected field of view 924.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012835 (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.010268 (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 341.2905 through 0 to 19.1779, gap 19.1779 to 341.2905
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 313 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 231 matched stars entering correct_measured_positions(), 157 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.64"
Removing outliers...
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 222 matched stars entering correct_measured_positions(), 16652 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.42"
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 238.1732 through 0 to 19.1900, gap 19.1900 to 238.1732
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 327 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
WARNING: Accuracy estimation diagnostic: 267 matched stars entering correct_measured_positions(), 16674 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.41"
WARNING: Accuracy estimation diagnostic: 266 matched stars entering correct_measured_positions(), 20094 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.52"
Excluding outliers - 266 stars left (next iteration limit 244)
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits -region wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.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.2ubOK2qWMK (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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=10, blended=8338, passed=85274
Got 85274 stars (including 76858 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat
util/solve_plate_with_UCAC5 got 85274 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.1'
Seting catalog search parameters based on the expected field of view 924.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012835 (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.010268 (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 341.2922 through 0 to 19.2818, gap 19.2818 to 341.2922
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 313 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 230 matched stars entering correct_measured_positions(), 156 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.03"
Removing outliers...
Correcting the measured astrometric positions...
WARNING: Accuracy estimation diagnostic: 222 matched stars entering correct_measured_positions(), 17194 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.97"
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 238.1125 through 0 to 19.2899, gap 19.2899 to 238.1125
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 326 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
WARNING: Accuracy estimation diagnostic: 262 matched stars entering correct_measured_positions(), 17216 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.97"
WARNING: Accuracy estimation diagnostic: 257 matched stars entering correct_measured_positions(), 19556 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.55"
Excluding outliers - 257 stars left (next iteration limit 244)
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits -region wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Saving fully-calibrated image wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-21-14_20.00sec_-5.00C_LIGHT_0427.fits
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.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-06_CI_Cas-02-Q2b1x1_053037_TTUQ2b1x1_26149_iTgmjRkq/wcs_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428.fits
Preparing the HTML report for the field Cas-02-Q2b1x1 with default.sex.telephoto_lens_vSTL
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
Adding exclusion_list_gaiadr2.txt__out187936.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out193967.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out194002.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out205340.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out207558.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out07777.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out102223.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out111971.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out119947.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out138165.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145313.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out169818.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out181704.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out18826.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193930.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193931.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193937.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193948.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193957.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193960.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193964.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193971.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193972.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193975.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193985.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193986.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193987.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193991.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193992.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193993.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193994.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193998.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193999.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194000.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194001.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194003.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194004.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194009.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194010.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194012.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194016.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out196900.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out196901.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out196975.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out197208.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out197993.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out198424.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out198652.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out198667.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out198818.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out198974.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out199173.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out199175.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out199279.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out199559.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out200163.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out200353.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out200870.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out201128.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out201216.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out201313.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out201606.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out201683.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out201820.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out201961.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out202146.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out202260.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out202420.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out202736.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out202932.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out203122.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out203269.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out203317.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out203469.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out203657.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out203678.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out203710.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out203737.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out203787.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out203912.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out204000.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out204031.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out204546.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out204610.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out204636.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out204821.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out204905.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205169.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205409.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205505.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205510.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205542.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205624.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205689.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205737.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205891.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205922.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206042.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206195.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206243.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206247.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206267.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206315.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206356.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206517.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206536.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206630.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206677.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206789.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206799.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206800.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206841.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206929.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207126.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207395.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207479.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207517.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207520.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207544.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207604.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207701.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207733.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207997.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208002.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208127.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208156.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208282.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208384.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208392.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208502.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208585.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208587.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208645.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208658.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208665.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208735.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208894.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209065.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209116.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209264.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209308.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209486.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209572.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209589.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209627.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209643.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209673.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209676.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209696.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209714.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209770.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210382.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210388.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210408.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210455.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210473.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210499.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210523.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210578.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210817.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210820.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210966.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210972.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210991.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210999.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out211521.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out211717.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out211747.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out211924.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out211959.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out212187.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out212366.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out212411.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out212431.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out212435.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out212568.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out212708.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out212987.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out213532.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out213628.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out214594.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out214705.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out214920.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out48326.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out52924.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out58687.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out62873.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out71810.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out82205.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out90694.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out92948.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out94769.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 252s
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: 123s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193930_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193930_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193931_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193931_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193937_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193937_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193948_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193948_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193952_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 193952_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193957_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193957_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193960_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193960_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193964_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193964_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193967_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 193967_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 00:28:45.83 +61:01:46.5 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.15, MAG_FAINT_SEARCH_LIMIT=14.13)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193971_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193971_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193972_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193972_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193975_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193975_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193976_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 193976_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193985_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193985_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193986_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193986_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193987_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193987_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193991_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193991_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193992_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193992_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193993_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193993_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193994_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193994_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193997_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 193997_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193998_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193998_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193999_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 193999_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194000_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 194000_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194001_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 194001_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194002_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 194002_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 00:25:16.07 +60:23:14.0 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.77, MAG_FAINT_SEARCH_LIMIT=13.75)GAIADR2_OUTPUT=# 5.054 428735115944077312 006.31934934333 +60.38798044792 12.7800 11.7152 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.054#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194003_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 194003_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194004_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 194004_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194009_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 194009_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194010_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 194010_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194012_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 194012_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194014_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 194014_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194016_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 194016_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194286_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 194286_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194848_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 194848_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 23:31:11.23 +58:36:31.9 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194955_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 194955_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 195957_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 195957_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 196900_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 196900_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 196901_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 196901_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 196975_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 196975_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 197208_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 197208_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 197295_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 197295_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 197726_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 197726_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 197993_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 197993_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 197999_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 197999_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198424_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 198424_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198605_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 198605_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198626_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 198626_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198652_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 198652_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198667_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 198667_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198701_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 198701_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198798_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 198798_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198818_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 198818_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198974_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 198974_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 199173_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 199173_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 199175_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 199175_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 199279_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 199279_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 199559_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 199559_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 200040_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 200040_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 200163_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 200163_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 200353_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 200353_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 200870_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 200870_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 200929_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 200929_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (47291.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201084_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 201084_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 00:36:20.73 +60:18:20.5 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201128_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 201128_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201216_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 201216_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201313_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 201313_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201333_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 201333_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201466_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 201466_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201522_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 201522_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201606_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 201606_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201683_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 201683_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201820_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 201820_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201961_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 201961_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 202146_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 202146_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 202260_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 202260_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 202420_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 202420_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 202736_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 202736_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 202831_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 202831_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 202883_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 202883_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (22.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 202929_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 202929_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 202932_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 202932_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203122_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 203122_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203226_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 203226_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 00:05:16.86 +61:19:39.1 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203269_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 203269_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203317_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 203317_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203469_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 203469_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203657_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 203657_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203678_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 203678_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203710_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 203710_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203737_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 203737_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203787_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 203787_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203912_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 203912_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204000_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 204000_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204031_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 204031_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204063_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 204063_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204197_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 204197_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204208_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 204208_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204443_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 204443_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204523_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 204523_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204546_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 204546_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204564_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 204564_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (28478.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204610_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 204610_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204636_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 204636_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204821_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 204821_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204905_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 204905_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205169_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 205169_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205340_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 205340_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 00:32:53.93 +59:02:47.6 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.70, MAG_FAINT_SEARCH_LIMIT=13.68)GAIADR2_OUTPUT=# 3.674 428034349079349248 008.22462915791 +59.04553576972 11.8632 10.3260 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.674#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205409_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 205409_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205462_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 205462_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205505_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 205505_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205509_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 205509_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205510_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 205510_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205542_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 205542_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205624_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 205624_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205689_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 205689_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205707_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 205707_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 00:29:27.15 +60:49:49.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205737_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 205737_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205891_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 205891_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205922_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 205922_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205970_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 205970_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (156945.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206042_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206042_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206118_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 206118_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206195_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206195_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206243_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206243_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206247_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206247_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206267_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206267_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206315_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206315_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206356_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206356_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206404_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 206404_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206517_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206517_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206536_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206536_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206548_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 206548_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206630_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206630_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206650_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 206650_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (28.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206677_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206677_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206789_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206789_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206799_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206799_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206800_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206800_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206835_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 206835_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206841_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206841_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206929_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 206929_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207126_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 207126_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207219_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 207219_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207395_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 207395_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207479_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 207479_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207517_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 207517_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207520_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 207520_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207544_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 207544_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207558_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 207558_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 00:30:06.82 +60:08:11.0 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.97, MAG_FAINT_SEARCH_LIMIT=13.95)GAIADR2_OUTPUT=# 4.463 428523597395874048 007.52737483260 +60.13526298110 12.8884 12.3976 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.463#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207604_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 207604_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207701_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 207701_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207733_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 207733_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207912_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 207912_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207997_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 207997_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208002_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208002_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208025_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 208025_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208026_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 208026_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (157051.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208127_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208127_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208156_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208156_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208261_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 208261_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208282_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208282_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208384_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208384_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208392_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208392_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208426_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 208426_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208502_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208502_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208585_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208585_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208587_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208587_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208645_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208645_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208658_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208658_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208665_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208665_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208672_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 208672_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208735_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208735_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208894_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 208894_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209012_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 209012_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209027_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 209027_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209065_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209065_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209066_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 209066_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (28566.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209116_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209116_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209237_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 209237_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (22.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209251_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 209251_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209264_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209264_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209308_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209308_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209354_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 209354_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 00:24:28.83 +60:36:00.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209486_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209486_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209572_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209572_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209589_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209589_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209627_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209627_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209643_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209643_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209673_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209673_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209676_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209676_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209696_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209696_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209706_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 209706_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (28548.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209714_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209714_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209770_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 209770_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209780_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 209780_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (157787.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209878_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 209878_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (24.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209884_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 209884_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210056_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 210056_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210382_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210382_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210388_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210388_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210408_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210408_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210455_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210455_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210473_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210473_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210499_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210499_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210523_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210523_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210578_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210578_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210817_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210817_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210820_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210820_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210922_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 210922_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210966_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210966_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210972_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210972_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210991_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210991_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210999_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 210999_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211521_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 211521_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211717_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 211717_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211747_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 211747_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211924_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 211924_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211959_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 211959_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212187_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 212187_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212366_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 212366_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212411_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 212411_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212430_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 212430_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212431_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 212431_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212435_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 212435_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212465_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 212465_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (159200.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212568_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 212568_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212708_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 212708_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212987_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 212987_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 213020_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 213020_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 213105_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 213105_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 213532_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 213532_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 213628_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 213628_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214111_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 214111_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214144_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 214144_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214594_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 214594_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214705_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 214705_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214920_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 214920_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 215126_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 215126_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 215353_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 215353_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 215475_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 215475_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (158369.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187936_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 187936_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 00:32:25.65 +60:34:12.9 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.46, MAG_FAINT_SEARCH_LIMIT=14.44)GAIADR2_OUTPUT=# 2.553 428611931978401024 008.10682973602 +60.57095886828 12.0615 10.4455 VARIABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#2.553#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 23283_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 23283_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 119947_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 119947_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 94769_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 94769_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 27991_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 27991_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 91927_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 91927_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 92225_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 92225_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 23:49:03.83 +61:01:28.9 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 71810_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 71810_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 82205_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 82205_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 111971_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 111971_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 62873_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 62873_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138165_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 138165_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 18826_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 18826_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 133657_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 133657_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169818_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 169818_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 120115_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 120115_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 113814_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 113814_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52924_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 52924_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 71228_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 71228_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 00:35:25.56 +61:14:53.5 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 90694_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 90694_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 07777_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 07777_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 48326_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 48326_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 102223_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 102223_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58687_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 58687_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145313_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 145313_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 181704_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 181704_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 51255_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 51255_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 135878_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 135878_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
**** FOUND 00:31:43.14 +57:54:13.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 92948_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
Preparing report for the candidate 92948_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 69913_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 69913_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 71937_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428
The candidate 71937_fd_Cas-02-Q2b1x1_2026-04-06_05-22-20_20.00sec_-5.00C_LIGHT_0428 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 9s
make_report_in_HTML.sh TOTAL: 384s
Prepared the HTML report for the field Cas-02-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
00:35:02.75 +61:19:05.8
00:35:25.81 +61:14:50.3
23:31:11.01 +58:36:31.4
23:49:03.26 +61:01:27.2
23:43:25.25 +61:39:45.1
00:34:42.72 +65:36:40.7
00:04:55.82 +60:17:56.6
00:28:33.93 +59:15:25.3
00:18:51.74 +59:05:34.2
23:55:07.77 +58:44:60.0
00:32:54.77 +58:24:23.8
23:57:48.00 +58:26:27.4
00:39:16.58 +64:26:56.1
00:34:25.49 +64:30:20.7
00:18:48.96 +63:06:00.8
23:28:23.23 +62:02:49.4
17:56:39.94 +63:38:42.0
23:38:15.45 +60:57:58.2
23:57:46.55 +60:12:20.1
23:24:12.98 +62:15:51.0
23:38:04.25 +61:30:33.3
00:11:24.44 +57:49:31.2
23:40:46.93 +63:26:00.8
00:07:58.15 +63:26:00.0
23:36:31.47 +61:28:53.4
23:26:10.25 +61:31:23.9
00:15:59.43 +59:25:38.1
00:26:46.37 +63:59:09.3
00:20:48.63 +62:51:16.8
23:26:17.55 +61:37:44.7
00:32:05.19 +63:08:18.6
00:09:55.25 +62:32:56.4
23:45:44.95 +58:00:45.6
23:27:29.73 +61:19:46.5
23:51:31.92 +62:59:46.3
00:34:26.87 +62:34:19.4
00:05:25.60 +57:56:06.7
00:09:33.62 +63:07:45.7
23:37:38.49 +58:39:30.2
00:06:35.71 +58:24:28.0
23:26:29.01 +61:35:35.1
23:26:34.43 +61:35:52.6
23:26:41.99 +61:22:03.4
23:47:31.94 +58:42:08.7
00:10:03.32 +63:53:17.8
00:01:54.33 +60:18:55.9
23:26:04.39 +61:37:32.3
23:38:38.69 +58:52:39.6
23:51:50.90 +63:54:05.5
00:21:26.32 +59:14:02.1
23:55:54.85 +58:07:04.6
00:09:01.76 +63:07:17.0
23:26:17.87 +61:36:33.3
00:20:37.05 +61:51:30.4
23:27:15.58 +60:49:00.4
23:34:45.43 +60:27:13.3
23:44:34.01 +61:05:32.3
23:29:50.03 +65:16:39.4
23:28:09.79 +61:53:50.9
23:26:43.14 +61:35:11.3
00:06:52.80 +58:55:09.7
00:09:22.42 +59:39:23.2
23:26:03.65 +61:37:02.5
00:21:01.14 +62:26:01.7
23:32:37.01 +57:30:48.6
00:36:59.53 +63:06:29.7
23:58:05.29 +61:02:12.8
23:43:43.41 +61:38:14.8
23:34:08.10 +64:01:16.5
23:26:51.14 +62:16:38.9
00:17:16.92 +63:30:59.0
23:37:59.23 +58:00:52.3
23:26:52.99 +62:16:40.8
23:41:58.52 +61:46:52.3
23:29:43.41 +61:28:56.8
23:28:35.59 +64:31:26.4
23:39:48.56 +61:18:30.8
00:19:07.94 +60:19:14.6
00:34:19.76 +58:51:51.7
00:03:24.94 +66:01:13.3
00:01:50.25 +60:18:56.9
23:25:40.90 +62:47:48.9
23:25:59.79 +62:32:19.6
23:25:24.29 +60:28:50.3
23:29:06.48 +65:32:07.7
00:15:23.05 +58:25:48.9
23:47:05.27 +61:58:45.6
23:32:30.76 +59:11:13.6
23:58:46.13 +61:10:36.3
00:17:04.16 +63:32:12.3
00:27:05.57 +60:41:10.0
23:26:04.87 +61:40:44.4
00:12:27.63 +62:50:58.4
23:47:07.27 +61:58:00.1
23:30:34.22 +61:21:23.8
23:26:14.50 +61:36:34.8
00:09:31.62 +58:40:30.1
00:35:14.84 +62:59:25.6
00:31:26.40 +63:18:40.5
00:24:05.24 +61:20:00.7
00:34:23.22 +62:34:15.1
00:18:55.71 +61:24:45.3
23:39:25.70 +58:42:32.0
00:18:18.63 +65:29:22.2
23:41:00.00 +61:53:50.3
23:26:04.60 +61:35:23.3
23:57:05.06 +64:54:34.7
23:41:50.50 +61:46:41.3
23:59:41.66 +63:30:22.5
23:45:13.66 +62:42:06.1
23:59:07.25 +60:39:40.5
00:00:55.89 +60:21:27.8
23:26:24.59 +62:17:17.3
23:51:37.24 +58:59:18.7
23:49:34.29 +61:16:01.9
00:00:00.67 +60:17:24.7
23:52:12.52 +62:33:17.4
23:33:45.36 +57:56:36.5
00:17:29.59 +62:48:13.1
23:48:30.54 +57:53:11.4
00:15:35.26 +61:43:39.1
00:02:26.20 +63:18:45.8
23:54:14.18 +64:19:24.5
00:19:08.65 +63:51:02.8
16:06:27.67 +63:36:09.4
23:59:35.83 +63:32:19.3
00:30:07.45 +60:07:45.6
00:05:21.48 +58:33:56.0
00:07:02.70 +63:11:02.0
00:27:11.54 +60:23:29.4
23:58:38.93 +62:34:50.2
23:36:49.09 +62:15:17.8
23:25:14.20 +60:31:01.3
23:32:38.33 +63:56:12.0
23:23:48.89 +61:21:10.2
00:30:35.68 +62:20:56.5
00:19:29.64 +62:41:18.6
00:09:31.52 +64:59:41.6
23:33:01.06 +63:57:36.5
23:56:58.03 +66:02:55.8
00:20:25.46 +62:02:12.6
23:41:45.24 +61:51:28.3
23:44:20.84 +62:52:52.9
23:51:41.08 +59:40:49.2
00:06:48.23 +63:18:52.6
00:24:12.00 +62:36:19.4
23:24:42.80 +58:11:37.7
23:25:41.59 +65:38:59.7
00:02:02.36 +61:10:40.0
00:10:56.22 +59:42:02.3
00:15:25.01 +59:45:55.5
23:41:17.56 +62:00:26.0
00:29:19.18 +63:26:57.3
00:27:11.16 +60:41:49.8
00:00:05.72 +60:16:33.9
00:16:02.01 +63:07:33.7
00:16:13.19 +61:01:18.1
16:03:44.54 +63:36:28.4
00:10:35.90 +60:01:34.8
00:02:01.98 +60:27:38.2
00:05:37.84 +61:16:37.9
23:25:23.48 +58:31:24.7
00:02:25.07 +63:14:01.8
00:07:42.99 +63:05:50.4
23:48:29.17 +63:09:26.4
23:33:59.78 +62:15:36.4
00:00:08.14 +64:23:02.6
23:43:52.88 +61:33:20.7
00:08:40.03 +63:17:13.4
23:59:50.78 +64:23:14.2
23:36:12.52 +63:34:55.6
23:28:41.35 +63:28:45.8
23:42:59.68 +60:49:40.9
23:37:37.18 +61:42:23.7
23:52:08.17 +61:11:17.9
23:43:20.89 +61:27:22.4
23:29:39.29 +61:52:56.4
00:19:02.40 +61:25:24.0
23:31:12.92 +64:54:07.8
16:03:08.99 +63:35:19.4
00:35:49.18 +65:24:23.0
23:34:44.88 +61:28:01.7
23:37:05.98 +61:09:49.2
23:41:13.20 +63:17:37.1
00:12:45.81 +62:44:21.6
00:34:31.28 +61:56:32.4
00:20:25.33 +62:06:04.6
23:37:13.88 +62:01:38.6
00:35:53.37 +60:37:13.0
00:28:08.68 +60:29:31.2
23:26:51.95 +60:57:38.0
00:08:35.68 +60:36:18.8
########### Completed Cas-02-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 ####
23:31:11.01 +58:36:31.4
23:49:03.26 +61:01:27.2
23:43:25.25 +61:39:45.1
00:35:25.81 +61:14:50.3
00:35:02.75 +61:19:05.8
00:18:48.96 +63:06:00.8
23:28:23.23 +62:02:49.4
17:56:39.94 +63:38:42.0
23:38:15.45 +60:57:58.2
23:57:46.55 +60:12:20.1
23:24:12.98 +62:15:51.0
23:38:04.25 +61:30:33.3
00:11:24.44 +57:49:31.2
23:40:46.93 +63:26:00.8
00:07:58.15 +63:26:00.0
23:36:31.47 +61:28:53.4
23:26:10.25 +61:31:23.9
00:15:59.43 +59:25:38.1
00:26:46.37 +63:59:09.3
00:20:48.63 +62:51:16.8
23:26:17.55 +61:37:44.7
00:32:05.19 +63:08:18.6
00:09:55.25 +62:32:56.4
23:45:44.95 +58:00:45.6
23:27:29.73 +61:19:46.5
23:51:31.92 +62:59:46.3
00:34:26.87 +62:34:19.4
00:05:25.60 +57:56:06.7
00:09:33.62 +63:07:45.7
23:37:38.49 +58:39:30.2
00:06:35.71 +58:24:28.0
23:26:29.01 +61:35:35.1
23:26:34.43 +61:35:52.6
23:26:41.99 +61:22:03.4
23:47:31.94 +58:42:08.7
00:10:03.32 +63:53:17.8
00:01:54.33 +60:18:55.9
23:26:04.39 +61:37:32.3
23:38:38.69 +58:52:39.6
23:51:50.90 +63:54:05.5
00:21:26.32 +59:14:02.1
23:55:54.85 +58:07:04.6
00:09:01.76 +63:07:17.0
23:26:17.87 +61:36:33.3
00:20:37.05 +61:51:30.4
23:27:15.58 +60:49:00.4
23:34:45.43 +60:27:13.3
23:44:34.01 +61:05:32.3
23:29:50.03 +65:16:39.4
23:28:09.79 +61:53:50.9
23:26:43.14 +61:35:11.3
00:06:52.80 +58:55:09.7
00:09:22.42 +59:39:23.2
23:26:03.65 +61:37:02.5
00:21:01.14 +62:26:01.7
23:32:37.01 +57:30:48.6
00:36:59.53 +63:06:29.7
23:58:05.29 +61:02:12.8
23:43:43.41 +61:38:14.8
23:34:08.10 +64:01:16.5
23:26:51.14 +62:16:38.9
00:17:16.92 +63:30:59.0
23:37:59.23 +58:00:52.3
23:26:52.99 +62:16:40.8
23:41:58.52 +61:46:52.3
23:29:43.41 +61:28:56.8
23:28:35.59 +64:31:26.4
23:39:48.56 +61:18:30.8
00:19:07.94 +60:19:14.6
00:34:19.76 +58:51:51.7
00:03:24.94 +66:01:13.3
00:01:50.25 +60:18:56.9
23:25:40.90 +62:47:48.9
23:25:59.79 +62:32:19.6
23:25:24.29 +60:28:50.3
23:29:06.48 +65:32:07.7
00:15:23.05 +58:25:48.9
23:47:05.27 +61:58:45.6
23:32:30.76 +59:11:13.6
23:58:46.13 +61:10:36.3
00:17:04.16 +63:32:12.3
00:27:05.57 +60:41:10.0
23:26:04.87 +61:40:44.4
00:12:27.63 +62:50:58.4
23:47:07.27 +61:58:00.1
23:30:34.22 +61:21:23.8
23:26:14.50 +61:36:34.8
00:09:31.62 +58:40:30.1
00:35:14.84 +62:59:25.6
00:31:26.40 +63:18:40.5
00:24:05.24 +61:20:00.7
00:34:23.22 +62:34:15.1
00:18:55.71 +61:24:45.3
23:39:25.70 +58:42:32.0
00:18:18.63 +65:29:22.2
23:41:00.00 +61:53:50.3
23:26:04.60 +61:35:23.3
23:57:05.06 +64:54:34.7
23:41:50.50 +61:46:41.3
23:59:41.66 +63:30:22.5
23:45:13.66 +62:42:06.1
23:59:07.25 +60:39:40.5
00:00:55.89 +60:21:27.8
23:26:24.59 +62:17:17.3
23:51:37.24 +58:59:18.7
23:49:34.29 +61:16:01.9
00:00:00.67 +60:17:24.7
23:52:12.52 +62:33:17.4
23:33:45.36 +57:56:36.5
00:17:29.59 +62:48:13.1
23:48:30.54 +57:53:11.4
00:15:35.26 +61:43:39.1
00:02:26.20 +63:18:45.8
23:54:14.18 +64:19:24.5
00:19:08.65 +63:51:02.8
16:06:27.67 +63:36:09.4
23:59:35.83 +63:32:19.3
00:30:07.45 +60:07:45.6
00:05:21.48 +58:33:56.0
00:07:02.70 +63:11:02.0
00:27:11.54 +60:23:29.4
23:58:38.93 +62:34:50.2
23:36:49.09 +62:15:17.8
23:25:14.20 +60:31:01.3
23:32:38.33 +63:56:12.0
23:23:48.89 +61:21:10.2
00:30:35.68 +62:20:56.5
00:19:29.64 +62:41:18.6
00:09:31.52 +64:59:41.6
23:33:01.06 +63:57:36.5
23:56:58.03 +66:02:55.8
00:20:25.46 +62:02:12.6
23:41:45.24 +61:51:28.3
23:44:20.84 +62:52:52.9
23:51:41.08 +59:40:49.2
00:06:48.23 +63:18:52.6
00:24:12.00 +62:36:19.4
23:24:42.80 +58:11:37.7
23:25:41.59 +65:38:59.7
00:02:02.36 +61:10:40.0
00:10:56.22 +59:42:02.3
00:15:25.01 +59:45:55.5
23:41:17.56 +62:00:26.0
00:29:19.18 +63:26:57.3
00:27:11.16 +60:41:49.8
00:00:05.72 +60:16:33.9
00:16:02.01 +63:07:33.7
00:16:13.19 +61:01:18.1
16:03:44.54 +63:36:28.4
00:10:35.90 +60:01:34.8
00:02:01.98 +60:27:38.2
00:05:37.84 +61:16:37.9
23:25:23.48 +58:31:24.7
00:02:25.07 +63:14:01.8
00:07:42.99 +63:05:50.4
23:48:29.17 +63:09:26.4
23:33:59.78 +62:15:36.4
00:00:08.14 +64:23:02.6
23:43:52.88 +61:33:20.7
00:08:40.03 +63:17:13.4
23:59:50.78 +64:23:14.2
23:36:12.52 +63:34:55.6
23:28:41.35 +63:28:45.8
23:42:59.68 +60:49:40.9
23:37:37.18 +61:42:23.7
23:52:08.17 +61:11:17.9
23:43:20.89 +61:27:22.4
23:29:39.29 +61:52:56.4
00:19:02.40 +61:25:24.0
23:31:12.92 +64:54:07.8
16:03:08.99 +63:35:19.4
00:35:49.18 +65:24:23.0
23:34:44.88 +61:28:01.7
23:37:05.98 +61:09:49.2
00:18:51.74 +59:05:34.2
00:08:35.68 +60:36:18.8
23:37:13.88 +62:01:38.6
00:35:53.37 +60:37:13.0
00:28:33.93 +59:15:25.3
00:20:25.33 +62:06:04.6
23:55:07.77 +58:44:60.0
00:34:25.49 +64:30:20.7
23:57:48.00 +58:26:27.4
00:12:45.81 +62:44:21.6
00:28:08.68 +60:29:31.2
00:34:42.72 +65:36:40.7
23:41:13.20 +63:17:37.1
00:04:55.82 +60:17:56.6
00:34:31.28 +61:56:32.4
00:32:54.77 +58:24:23.8
00:39:16.58 +64:26:56.1
23:26:51.95 +60:57:38.0
###################################################################################
23:31:11.01 +58:36:31.4 -- not an asteroid (will add it to exclusion list)
23:49:03.26 +61:01:27.2 -- not an asteroid (will add it to exclusion list)
23:43:25.25 +61:39:45.1 -- not an asteroid (will add it to exclusion list)
00:35:25.81 +61:14:50.3 -- not an asteroid (will add it to exclusion list)
00:35:02.75 +61:19:05.8 -- not an asteroid (will add it to exclusion list)
00:18:48.96 +63:06:00.8 -- not an asteroid (will add it to exclusion list)
23:28:23.23 +62:02:49.4 -- not an asteroid (will add it to exclusion list)
17:56:39.94 +63:38:42.0 -- not an asteroid (will add it to exclusion list)
23:38:15.45 +60:57:58.2 -- not an asteroid (will add it to exclusion list)
23:57:46.55 +60:12:20.1 -- not an asteroid (will add it to exclusion list)
23:24:12.98 +62:15:51.0 -- not an asteroid (will add it to exclusion list)
23:38:04.25 +61:30:33.3 -- not an asteroid (will add it to exclusion list)
00:11:24.44 +57:49:31.2 -- not an asteroid (will add it to exclusion list)
23:40:46.93 +63:26:00.8 -- not an asteroid (will add it to exclusion list)
00:07:58.15 +63:26:00.0 -- not an asteroid (will add it to exclusion list)
23:36:31.47 +61:28:53.4 -- not an asteroid (will add it to exclusion list)
23:26:10.25 +61:31:23.9 -- not an asteroid (will add it to exclusion list)
00:15:59.43 +59:25:38.1 -- not an asteroid (will add it to exclusion list)
00:26:46.37 +63:59:09.3 -- not an asteroid (will add it to exclusion list)
00:20:48.63 +62:51:16.8 -- not an asteroid (will add it to exclusion list)
23:26:17.55 +61:37:44.7 -- not an asteroid (will add it to exclusion list)
00:32:05.19 +63:08:18.6 -- not an asteroid (will add it to exclusion list)
00:09:55.25 +62:32:56.4 -- not an asteroid (will add it to exclusion list)
23:45:44.95 +58:00:45.6 -- not an asteroid (will add it to exclusion list)
23:27:29.73 +61:19:46.5 -- not an asteroid (will add it to exclusion list)
23:51:31.92 +62:59:46.3 -- not an asteroid (will add it to exclusion list)
00:34:26.87 +62:34:19.4 -- not an asteroid (will add it to exclusion list)
00:05:25.60 +57:56:06.7 -- not an asteroid (will add it to exclusion list)
00:09:33.62 +63:07:45.7 -- not an asteroid (will add it to exclusion list)
23:37:38.49 +58:39:30.2 -- not an asteroid (will add it to exclusion list)
00:06:35.71 +58:24:28.0 -- not an asteroid (will add it to exclusion list)
23:26:29.01 +61:35:35.1 -- not an asteroid (will add it to exclusion list)
23:26:34.43 +61:35:52.6 -- not an asteroid (will add it to exclusion list)
23:26:41.99 +61:22:03.4 -- not an asteroid (will add it to exclusion list)
23:47:31.94 +58:42:08.7 -- not an asteroid (will add it to exclusion list)
00:10:03.32 +63:53:17.8 -- not an asteroid (will add it to exclusion list)
00:01:54.33 +60:18:55.9 -- not an asteroid (will add it to exclusion list)
23:26:04.39 +61:37:32.3 -- not an asteroid (will add it to exclusion list)
23:38:38.69 +58:52:39.6 -- not an asteroid (will add it to exclusion list)
23:51:50.90 +63:54:05.5 -- not an asteroid (will add it to exclusion list)
00:21:26.32 +59:14:02.1 -- not an asteroid (will add it to exclusion list)
23:55:54.85 +58:07:04.6 -- not an asteroid (will add it to exclusion list)
00:09:01.76 +63:07:17.0 -- not an asteroid (will add it to exclusion list)
23:26:17.87 +61:36:33.3 -- not an asteroid (will add it to exclusion list)
00:20:37.05 +61:51:30.4 -- not an asteroid (will add it to exclusion list)
23:27:15.58 +60:49:00.4 -- not an asteroid (will add it to exclusion list)
23:34:45.43 +60:27:13.3 -- not an asteroid (will add it to exclusion list)
23:44:34.01 +61:05:32.3 -- not an asteroid (will add it to exclusion list)
23:29:50.03 +65:16:39.4 -- not an asteroid (will add it to exclusion list)
23:28:09.79 +61:53:50.9 -- not an asteroid (will add it to exclusion list)
23:26:43.14 +61:35:11.3 -- not an asteroid (will add it to exclusion list)
00:06:52.80 +58:55:09.7 -- not an asteroid (will add it to exclusion list)
00:09:22.42 +59:39:23.2 -- not an asteroid (will add it to exclusion list)
23:26:03.65 +61:37:02.5 -- not an asteroid (will add it to exclusion list)
00:21:01.14 +62:26:01.7 -- not an asteroid (will add it to exclusion list)
23:32:37.01 +57:30:48.6 -- not an asteroid (will add it to exclusion list)
00:36:59.53 +63:06:29.7 -- not an asteroid (will add it to exclusion list)
23:58:05.29 +61:02:12.8 -- not an asteroid (will add it to exclusion list)
23:43:43.41 +61:38:14.8 -- not an asteroid (will add it to exclusion list)
23:34:08.10 +64:01:16.5 -- not an asteroid (will add it to exclusion list)
23:26:51.14 +62:16:38.9 -- not an asteroid (will add it to exclusion list)
00:17:16.92 +63:30:59.0 -- not an asteroid (will add it to exclusion list)
23:37:59.23 +58:00:52.3 -- not an asteroid (will add it to exclusion list)
23:26:52.99 +62:16:40.8 -- not an asteroid (will add it to exclusion list)
23:41:58.52 +61:46:52.3 -- not an asteroid (will add it to exclusion list)
23:29:43.41 +61:28:56.8 -- not an asteroid (will add it to exclusion list)
23:28:35.59 +64:31:26.4 -- not an asteroid (will add it to exclusion list)
23:39:48.56 +61:18:30.8 -- not an asteroid (will add it to exclusion list)
00:19:07.94 +60:19:14.6 -- not an asteroid (will add it to exclusion list)
00:34:19.76 +58:51:51.7 -- not an asteroid (will add it to exclusion list)
00:03:24.94 +66:01:13.3 -- not an asteroid (will add it to exclusion list)
00:01:50.25 +60:18:56.9 -- not an asteroid (will add it to exclusion list)
23:25:40.90 +62:47:48.9 -- not an asteroid (will add it to exclusion list)
23:25:59.79 +62:32:19.6 -- not an asteroid (will add it to exclusion list)
23:25:24.29 +60:28:50.3 -- not an asteroid (will add it to exclusion list)
23:29:06.48 +65:32:07.7 -- not an asteroid (will add it to exclusion list)
00:15:23.05 +58:25:48.9 -- not an asteroid (will add it to exclusion list)
23:47:05.27 +61:58:45.6 -- not an asteroid (will add it to exclusion list)
23:32:30.76 +59:11:13.6 -- not an asteroid (will add it to exclusion list)
23:58:46.13 +61:10:36.3 -- not an asteroid (will add it to exclusion list)
00:17:04.16 +63:32:12.3 -- not an asteroid (will add it to exclusion list)
00:27:05.57 +60:41:10.0 -- not an asteroid (will add it to exclusion list)
23:26:04.87 +61:40:44.4 -- not an asteroid (will add it to exclusion list)
00:12:27.63 +62:50:58.4 -- not an asteroid (will add it to exclusion list)
23:47:07.27 +61:58:00.1 -- not an asteroid (will add it to exclusion list)
23:30:34.22 +61:21:23.8 -- not an asteroid (will add it to exclusion list)
23:26:14.50 +61:36:34.8 -- not an asteroid (will add it to exclusion list)
00:09:31.62 +58:40:30.1 -- not an asteroid (will add it to exclusion list)
00:35:14.84 +62:59:25.6 -- not an asteroid (will add it to exclusion list)
00:31:26.40 +63:18:40.5 -- not an asteroid (will add it to exclusion list)
00:24:05.24 +61:20:00.7 -- not an asteroid (will add it to exclusion list)
00:34:23.22 +62:34:15.1 -- not an asteroid (will add it to exclusion list)
00:18:55.71 +61:24:45.3 -- not an asteroid (will add it to exclusion list)
23:39:25.70 +58:42:32.0 -- not an asteroid (will add it to exclusion list)
00:18:18.63 +65:29:22.2 -- not an asteroid (will add it to exclusion list)
23:41:00.00 +61:53:50.3 -- not an asteroid (will add it to exclusion list)
23:26:04.60 +61:35:23.3 -- not an asteroid (will add it to exclusion list)
23:57:05.06 +64:54:34.7 -- not an asteroid (will add it to exclusion list)
23:41:50.50 +61:46:41.3 -- not an asteroid (will add it to exclusion list)
23:59:41.66 +63:30:22.5 -- not an asteroid (will add it to exclusion list)
23:45:13.66 +62:42:06.1 -- not an asteroid (will add it to exclusion list)
23:59:07.25 +60:39:40.5 -- not an asteroid (will add it to exclusion list)
00:00:55.89 +60:21:27.8 -- not an asteroid (will add it to exclusion list)
23:26:24.59 +62:17:17.3 -- not an asteroid (will add it to exclusion list)
23:51:37.24 +58:59:18.7 -- not an asteroid (will add it to exclusion list)
23:49:34.29 +61:16:01.9 -- not an asteroid (will add it to exclusion list)
00:00:00.67 +60:17:24.7 -- not an asteroid (will add it to exclusion list)
23:52:12.52 +62:33:17.4 -- not an asteroid (will add it to exclusion list)
23:33:45.36 +57:56:36.5 -- not an asteroid (will add it to exclusion list)
00:17:29.59 +62:48:13.1 -- not an asteroid (will add it to exclusion list)
23:48:30.54 +57:53:11.4 -- not an asteroid (will add it to exclusion list)
00:15:35.26 +61:43:39.1 -- not an asteroid (will add it to exclusion list)
00:02:26.20 +63:18:45.8 -- not an asteroid (will add it to exclusion list)
23:54:14.18 +64:19:24.5 -- not an asteroid (will add it to exclusion list)
00:19:08.65 +63:51:02.8 -- not an asteroid (will add it to exclusion list)
16:06:27.67 +63:36:09.4 -- not an asteroid (will add it to exclusion list)
23:59:35.83 +63:32:19.3 -- not an asteroid (will add it to exclusion list)
00:30:07.45 +60:07:45.6 -- not an asteroid (will add it to exclusion list)
00:05:21.48 +58:33:56.0 -- not an asteroid (will add it to exclusion list)
00:07:02.70 +63:11:02.0 -- not an asteroid (will add it to exclusion list)
00:27:11.54 +60:23:29.4 -- not an asteroid (will add it to exclusion list)
23:58:38.93 +62:34:50.2 -- not an asteroid (will add it to exclusion list)
23:36:49.09 +62:15:17.8 -- not an asteroid (will add it to exclusion list)
23:25:14.20 +60:31:01.3 -- not an asteroid (will add it to exclusion list)
23:32:38.33 +63:56:12.0 -- not an asteroid (will add it to exclusion list)
23:23:48.89 +61:21:10.2 -- not an asteroid (will add it to exclusion list)
00:30:35.68 +62:20:56.5 -- not an asteroid (will add it to exclusion list)
00:19:29.64 +62:41:18.6 -- not an asteroid (will add it to exclusion list)
00:09:31.52 +64:59:41.6 -- not an asteroid (will add it to exclusion list)
23:33:01.06 +63:57:36.5 -- not an asteroid (will add it to exclusion list)
23:56:58.03 +66:02:55.8 -- not an asteroid (will add it to exclusion list)
00:20:25.46 +62:02:12.6 -- not an asteroid (will add it to exclusion list)
23:41:45.24 +61:51:28.3 -- not an asteroid (will add it to exclusion list)
23:44:20.84 +62:52:52.9 -- not an asteroid (will add it to exclusion list)
23:51:41.08 +59:40:49.2 -- not an asteroid (will add it to exclusion list)
00:06:48.23 +63:18:52.6 -- not an asteroid (will add it to exclusion list)
00:24:12.00 +62:36:19.4 -- not an asteroid (will add it to exclusion list)
23:24:42.80 +58:11:37.7 -- not an asteroid (will add it to exclusion list)
23:25:41.59 +65:38:59.7 -- not an asteroid (will add it to exclusion list)
00:02:02.36 +61:10:40.0 -- not an asteroid (will add it to exclusion list)
00:10:56.22 +59:42:02.3 -- not an asteroid (will add it to exclusion list)
00:15:25.01 +59:45:55.5 -- not an asteroid (will add it to exclusion list)
23:41:17.56 +62:00:26.0 -- not an asteroid (will add it to exclusion list)
00:29:19.18 +63:26:57.3 -- not an asteroid (will add it to exclusion list)
00:27:11.16 +60:41:49.8 -- not an asteroid (will add it to exclusion list)
00:00:05.72 +60:16:33.9 -- not an asteroid (will add it to exclusion list)
00:16:02.01 +63:07:33.7 -- not an asteroid (will add it to exclusion list)
00:16:13.19 +61:01:18.1 -- not an asteroid (will add it to exclusion list)
16:03:44.54 +63:36:28.4 -- not an asteroid (will add it to exclusion list)
00:10:35.90 +60:01:34.8 -- not an asteroid (will add it to exclusion list)
00:02:01.98 +60:27:38.2 -- not an asteroid (will add it to exclusion list)
00:05:37.84 +61:16:37.9 -- not an asteroid (will add it to exclusion list)
23:25:23.48 +58:31:24.7 -- not an asteroid (will add it to exclusion list)
00:02:25.07 +63:14:01.8 -- not an asteroid (will add it to exclusion list)
00:07:42.99 +63:05:50.4 -- not an asteroid (will add it to exclusion list)
23:48:29.17 +63:09:26.4 -- not an asteroid (will add it to exclusion list)
23:33:59.78 +62:15:36.4 -- not an asteroid (will add it to exclusion list)
00:00:08.14 +64:23:02.6 -- not an asteroid (will add it to exclusion list)
23:43:52.88 +61:33:20.7 -- not an asteroid (will add it to exclusion list)
00:08:40.03 +63:17:13.4 -- not an asteroid (will add it to exclusion list)
23:59:50.78 +64:23:14.2 -- not an asteroid (will add it to exclusion list)
23:36:12.52 +63:34:55.6 -- not an asteroid (will add it to exclusion list)
23:28:41.35 +63:28:45.8 -- not an asteroid (will add it to exclusion list)
23:42:59.68 +60:49:40.9 -- not an asteroid (will add it to exclusion list)
23:37:37.18 +61:42:23.7 -- not an asteroid (will add it to exclusion list)
23:52:08.17 +61:11:17.9 -- not an asteroid (will add it to exclusion list)
23:43:20.89 +61:27:22.4 -- not an asteroid (will add it to exclusion list)
23:29:39.29 +61:52:56.4 -- not an asteroid (will add it to exclusion list)
00:19:02.40 +61:25:24.0 -- not an asteroid (will add it to exclusion list)
23:31:12.92 +64:54:07.8 -- not an asteroid (will add it to exclusion list)
16:03:08.99 +63:35:19.4 -- not an asteroid (will add it to exclusion list)
00:35:49.18 +65:24:23.0 -- not an asteroid (will add it to exclusion list)
23:34:44.88 +61:28:01.7 -- not an asteroid (will add it to exclusion list)
23:37:05.98 +61:09:49.2 -- not an asteroid (will add it to exclusion list)
00:18:51.74 +59:05:34.2 -- not an asteroid (will add it to exclusion list)
00:08:35.68 +60:36:18.8 -- not an asteroid (will add it to exclusion list)
23:37:13.88 +62:01:38.6 -- not an asteroid (will add it to exclusion list)
00:35:53.37 +60:37:13.0 -- not an asteroid (will add it to exclusion list)
00:28:33.93 +59:15:25.3 -- not an asteroid (will add it to exclusion list)
00:20:25.33 +62:06:04.6 -- not an asteroid (will add it to exclusion list)
23:55:07.77 +58:44:60.0 -- not an asteroid (will add it to exclusion list)
00:34:25.49 +64:30:20.7 -- not an asteroid (will add it to exclusion list)
23:57:48.00 +58:26:27.4 -- not an asteroid (will add it to exclusion list)
00:12:45.81 +62:44:21.6 -- not an asteroid (will add it to exclusion list)
00:28:08.68 +60:29:31.2 -- not an asteroid (will add it to exclusion list)
00:34:42.72 +65:36:40.7 -- not an asteroid (will add it to exclusion list)
23:41:13.20 +63:17:37.1 -- not an asteroid (will add it to exclusion list)
00:04:55.82 +60:17:56.6 -- not an asteroid (will add it to exclusion list)
00:34:31.28 +61:56:32.4 -- not an asteroid (will add it to exclusion list)
00:32:54.77 +58:24:23.8 -- not an asteroid (will add it to exclusion list)
00:39:16.58 +64:26:56.1 -- not an asteroid (will add it to exclusion list)
23:26:51.95 +60:57:38.0 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:00.67 +60:17:24.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:05.72 +60:16:33.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:08.14 +64:23:02.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:55.89 +60:21:27.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:50.25 +60:18:56.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:54.33 +60:18:55.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:01.98 +60:27:38.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:02.36 +61:10:40.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:25.07 +63:14:01.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:26.20 +63:18:45.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:24.94 +66:01:13.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:55.82 +60:17:56.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:21.48 +58:33:56.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:25.60 +57:56:06.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:37.84 +61:16:37.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:35.71 +58:24:28.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:48.23 +63:18:52.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:52.80 +58:55:09.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:02.70 +63:11:02.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:42.99 +63:05:50.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:58.15 +63:26:00.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:35.68 +60:36:18.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:40.03 +63:17:13.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:01.76 +63:07:17.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:22.42 +59:39:23.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:31.52 +64:59:41.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:31.62 +58:40:30.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:33.62 +63:07:45.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:55.25 +62:32:56.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:03.32 +63:53:17.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:35.90 +60:01:34.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:56.22 +59:42:02.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:24.44 +57:49:31.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:27.63 +62:50:58.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:45.81 +62:44:21.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:23.05 +58:25:48.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:25.01 +59:45:55.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:35.26 +61:43:39.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:59.43 +59:25:38.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:02.01 +63:07:33.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:13.19 +61:01:18.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:04.16 +63:32:12.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:16.92 +63:30:59.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:29.59 +62:48:13.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:18.63 +65:29:22.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:48.96 +63:06:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:51.74 +59:05:34.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:55.71 +61:24:45.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:02.40 +61:25:24.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:07.94 +60:19:14.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:08.65 +63:51:02.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:29.64 +62:41:18.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:25.33 +62:06:04.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:25.46 +62:02:12.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:37.05 +61:51:30.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:48.63 +62:51:16.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:01.14 +62:26:01.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:26.32 +59:14:02.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:05.24 +61:20:00.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:12.00 +62:36:19.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:46.37 +63:59:09.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:05.57 +60:41:10.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:11.16 +60:41:49.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:11.54 +60:23:29.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:08.68 +60:29:31.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:33.93 +59:15:25.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:19.18 +63:26:57.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:07.45 +60:07:45.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:35.68 +62:20:56.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:26.40 +63:18:40.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:05.19 +63:08:18.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:54.77 +58:24:23.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:19.76 +58:51:51.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:23.22 +62:34:15.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:25.49 +64:30:20.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:26.87 +62:34:19.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:31.28 +61:56:32.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:42.72 +65:36:40.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:02.75 +61:19:05.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:14.84 +62:59:25.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:25.81 +61:14:50.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:49.18 +65:24:23.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:53.37 +60:37:13.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:59.53 +63:06:29.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:16.58 +64:26:56.1 -- does not seem to be a hot pixel (will add it to exclusion list)
16:03:08.99 +63:35:19.4 -- does not seem to be a hot pixel (will add it to exclusion list)
16:03:44.54 +63:36:28.4 -- does not seem to be a hot pixel (will add it to exclusion list)
16:06:27.67 +63:36:09.4 -- does not seem to be a hot pixel (will add it to exclusion list)
17:56:39.94 +63:38:42.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:48.89 +61:21:10.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:12.98 +62:15:51.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:42.80 +58:11:37.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:14.20 +60:31:01.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:23.48 +58:31:24.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:24.29 +60:28:50.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:40.90 +62:47:48.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:41.59 +65:38:59.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:59.79 +62:32:19.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:03.65 +61:37:02.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:04.39 +61:37:32.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:04.60 +61:35:23.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:04.87 +61:40:44.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:10.25 +61:31:23.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:14.50 +61:36:34.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:17.55 +61:37:44.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:17.87 +61:36:33.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:24.59 +62:17:17.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:29.01 +61:35:35.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:34.43 +61:35:52.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:41.99 +61:22:03.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:43.14 +61:35:11.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:51.14 +62:16:38.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:51.95 +60:57:38.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:52.99 +62:16:40.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:15.58 +60:49:00.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:29.73 +61:19:46.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:09.79 +61:53:50.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:23.23 +62:02:49.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:35.59 +64:31:26.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:41.35 +63:28:45.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:06.48 +65:32:07.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:39.29 +61:52:56.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:43.41 +61:28:56.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:50.03 +65:16:39.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:34.22 +61:21:23.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:11.01 +58:36:31.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:12.92 +64:54:07.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:30.76 +59:11:13.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:37.01 +57:30:48.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:38.33 +63:56:12.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:01.06 +63:57:36.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:45.36 +57:56:36.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:59.78 +62:15:36.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:08.10 +64:01:16.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:44.88 +61:28:01.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:45.43 +60:27:13.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:12.52 +63:34:55.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:31.47 +61:28:53.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:49.09 +62:15:17.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:05.98 +61:09:49.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:13.88 +62:01:38.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:37.18 +61:42:23.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:38.49 +58:39:30.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:59.23 +58:00:52.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:04.25 +61:30:33.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:15.45 +60:57:58.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:38.69 +58:52:39.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:25.70 +58:42:32.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:48.56 +61:18:30.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:46.93 +63:26:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:00.00 +61:53:50.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:13.20 +63:17:37.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:17.56 +62:00:26.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:45.24 +61:51:28.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:50.50 +61:46:41.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:58.52 +61:46:52.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:59.68 +60:49:40.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:20.89 +61:27:22.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:25.25 +61:39:45.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:43.41 +61:38:14.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:52.88 +61:33:20.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:20.84 +62:52:52.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:34.01 +61:05:32.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:13.66 +62:42:06.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:44.95 +58:00:45.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:05.27 +61:58:45.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:07.27 +61:58:00.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:31.94 +58:42:08.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:29.17 +63:09:26.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:30.54 +57:53:11.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:03.26 +61:01:27.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:34.29 +61:16:01.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:31.92 +62:59:46.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:37.24 +58:59:18.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:41.08 +59:40:49.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:50.90 +63:54:05.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:08.17 +61:11:17.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:12.52 +62:33:17.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:14.18 +64:19:24.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:07.77 +58:44:60.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:54.85 +58:07:04.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:58.03 +66:02:55.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:05.06 +64:54:34.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:46.55 +60:12:20.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:48.00 +58:26:27.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:05.29 +61:02:12.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:38.93 +62:34:50.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:46.13 +61:10:36.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:07.25 +60:39:40.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:35.83 +63:32:19.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:41.66 +63:30:22.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:50.78 +64:23:14.2 -- 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:00.67 +60:17:24.7 -- not a known variable star
00:00:05.72 +60:16:33.9 -- not a known variable star
00:00:08.14 +64:23:02.6 -- not a known variable star
00:00:55.89 +60:21:27.8 -- not a known variable star
00:01:50.25 +60:18:56.9 -- not a known variable star
00:01:54.33 +60:18:55.9 -- not a known variable star
00:02:01.98 +60:27:38.2 -- a known variable star
00:02:02.36 +61:10:40.0 -- a known variable star
00:02:25.07 +63:14:01.8 -- not a known variable star
00:02:26.20 +63:18:45.8 -- not a known variable star
00:03:24.94 +66:01:13.3 -- not a known variable star
00:04:55.82 +60:17:56.6 -- not a known variable star
00:05:21.48 +58:33:56.0 -- not a known variable star
00:05:25.60 +57:56:06.7 -- not a known variable star
00:05:37.84 +61:16:37.9 -- not a known variable star
00:06:35.71 +58:24:28.0 -- not a known variable star
00:06:48.23 +63:18:52.6 -- not a known variable star
00:06:52.80 +58:55:09.7 -- not a known variable star
00:07:02.70 +63:11:02.0 -- not a known variable star
00:07:42.99 +63:05:50.4 -- not a known variable star
00:07:58.15 +63:26:00.0 -- not a known variable star
00:08:35.68 +60:36:18.8 -- not a known variable star
00:08:40.03 +63:17:13.4 -- not a known variable star
00:09:01.76 +63:07:17.0 -- a known variable star
00:09:22.42 +59:39:23.2 -- not a known variable star
00:09:31.52 +64:59:41.6 -- not a known variable star
00:09:31.62 +58:40:30.1 -- not a known variable star
00:09:33.62 +63:07:45.7 -- not a known variable star
00:09:55.25 +62:32:56.4 -- not a known variable star
00:10:03.32 +63:53:17.8 -- not a known variable star
00:10:35.90 +60:01:34.8 -- not a known variable star
00:10:56.22 +59:42:02.3 -- not a known variable star
00:11:24.44 +57:49:31.2 -- not a known variable star
00:12:27.63 +62:50:58.4 -- not a known variable star
00:12:45.81 +62:44:21.6 -- not a known variable star
00:15:23.05 +58:25:48.9 -- not a known variable star
00:15:25.01 +59:45:55.5 -- not a known variable star
00:15:35.26 +61:43:39.1 -- not a known variable star
00:15:59.43 +59:25:38.1 -- not a known variable star
00:16:02.01 +63:07:33.7 -- not a known variable star
00:16:13.19 +61:01:18.1 -- a known variable star
00:17:04.16 +63:32:12.3 -- not a known variable star
00:17:16.92 +63:30:59.0 -- not a known variable star
00:17:29.59 +62:48:13.1 -- not a known variable star
00:18:18.63 +65:29:22.2 -- not a known variable star
00:18:48.96 +63:06:00.8 -- a known variable star
00:18:51.74 +59:05:34.2 -- not a known variable star
00:18:55.71 +61:24:45.3 -- not a known variable star
00:19:02.40 +61:25:24.0 -- not a known variable star
00:19:07.94 +60:19:14.6 -- not a known variable star
00:19:08.65 +63:51:02.8 -- not a known variable star
00:19:29.64 +62:41:18.6 -- not a known variable star
00:20:25.33 +62:06:04.6 -- not a known variable star
00:20:25.46 +62:02:12.6 -- not a known variable star
00:20:37.05 +61:51:30.4 -- not a known variable star
00:20:48.63 +62:51:16.8 -- a known variable star
00:21:01.14 +62:26:01.7 -- not a known variable star
00:21:26.32 +59:14:02.1 -- a known variable star
00:24:05.24 +61:20:00.7 -- not a known variable star
00:24:12.00 +62:36:19.4 -- not a known variable star
00:26:46.37 +63:59:09.3 -- not a known variable star
00:27:05.57 +60:41:10.0 -- not a known variable star
00:27:11.16 +60:41:49.8 -- not a known variable star
00:27:11.54 +60:23:29.4 -- not a known variable star
00:28:08.68 +60:29:31.2 -- a known variable star
00:28:33.93 +59:15:25.3 -- a known variable star
00:29:19.18 +63:26:57.3 -- a known variable star
00:30:07.45 +60:07:45.6 -- not a known variable star
00:30:35.68 +62:20:56.5 -- not a known variable star
00:31:26.40 +63:18:40.5 -- not a known variable star
00:32:05.19 +63:08:18.6 -- a known variable star
00:32:54.77 +58:24:23.8 -- a known variable star
00:34:19.76 +58:51:51.7 -- not a known variable star
00:34:23.22 +62:34:15.1 -- not a known variable star
00:34:25.49 +64:30:20.7 -- not a known variable star
00:34:26.87 +62:34:19.4 -- not a known variable star
00:34:31.28 +61:56:32.4 -- a known variable star
00:34:42.72 +65:36:40.7 -- not a known variable star
00:35:02.75 +61:19:05.8 -- a known variable star
00:35:14.84 +62:59:25.6 -- a known variable star
00:35:25.81 +61:14:50.3 -- a known variable star
00:35:49.18 +65:24:23.0 -- not a known variable star
00:35:53.37 +60:37:13.0 -- a known variable star
00:36:59.53 +63:06:29.7 -- not a known variable star
00:39:16.58 +64:26:56.1 -- not a known variable star
16:03:08.99 +63:35:19.4 -- not a known variable star
16:03:44.54 +63:36:28.4 -- not a known variable star
16:06:27.67 +63:36:09.4 -- not a known variable star
17:56:39.94 +63:38:42.0 -- not a known variable star
23:23:48.89 +61:21:10.2 -- a known variable star
23:24:12.98 +62:15:51.0 -- not a known variable star
23:24:42.80 +58:11:37.7 -- not a known variable star
23:25:14.20 +60:31:01.3 -- not a known variable star
23:25:23.48 +58:31:24.7 -- not a known variable star
23:25:24.29 +60:28:50.3 -- not a known variable star
23:25:40.90 +62:47:48.9 -- not a known variable star
23:25:41.59 +65:38:59.7 -- not a known variable star
23:25:59.79 +62:32:19.6 -- not a known variable star
23:26:03.65 +61:37:02.5 -- not a known variable star
23:26:04.39 +61:37:32.3 -- not a known variable star
23:26:04.60 +61:35:23.3 -- not a known variable star
23:26:04.87 +61:40:44.4 -- not a known variable star
23:26:10.25 +61:31:23.9 -- not a known variable star
23:26:14.50 +61:36:34.8 -- not a known variable star
23:26:17.55 +61:37:44.7 -- not a known variable star
23:26:17.87 +61:36:33.3 -- not a known variable star
23:26:24.59 +62:17:17.3 -- not a known variable star
23:26:29.01 +61:35:35.1 -- not a known variable star
23:26:34.43 +61:35:52.6 -- not a known variable star
23:26:41.99 +61:22:03.4 -- not a known variable star
23:26:43.14 +61:35:11.3 -- not a known variable star
23:26:51.14 +62:16:38.9 -- not a known variable star
23:26:51.95 +60:57:38.0 -- a known variable star
23:26:52.99 +62:16:40.8 -- not a known variable star
23:27:15.58 +60:49:00.4 -- not a known variable star
23:27:29.73 +61:19:46.5 -- not a known variable star
23:28:09.79 +61:53:50.9 -- not a known variable star
23:28:23.23 +62:02:49.4 -- not a known variable star
23:28:35.59 +64:31:26.4 -- not a known variable star
23:28:41.35 +63:28:45.8 -- not a known variable star
23:29:06.48 +65:32:07.7 -- not a known variable star
23:29:39.29 +61:52:56.4 -- not a known variable star
23:29:43.41 +61:28:56.8 -- a known variable star
23:29:50.03 +65:16:39.4 -- not a known variable star
23:30:34.22 +61:21:23.8 -- not a known variable star
23:31:11.01 +58:36:31.4 -- not a known variable star
23:31:12.92 +64:54:07.8 -- not a known variable star
23:32:30.76 +59:11:13.6 -- not a known variable star
23:32:37.01 +57:30:48.6 -- not a known variable star
23:32:38.33 +63:56:12.0 -- not a known variable star
23:33:01.06 +63:57:36.5 -- not a known variable star
23:33:45.36 +57:56:36.5 -- not a known variable star
23:33:59.78 +62:15:36.4 -- not a known variable star
23:34:08.10 +64:01:16.5 -- not a known variable star
23:34:44.88 +61:28:01.7 -- not a known variable star
23:34:45.43 +60:27:13.3 -- not a known variable star
23:36:12.52 +63:34:55.6 -- not a known variable star
23:36:31.47 +61:28:53.4 -- not a known variable star
23:36:49.09 +62:15:17.8 -- not a known variable star
23:37:05.98 +61:09:49.2 -- not a known variable star
23:37:13.88 +62:01:38.6 -- not a known variable star
23:37:37.18 +61:42:23.7 -- not a known variable star
23:37:38.49 +58:39:30.2 -- not a known variable star
23:37:59.23 +58:00:52.3 -- a known variable star
23:38:04.25 +61:30:33.3 -- not a known variable star
23:38:15.45 +60:57:58.2 -- not a known variable star
23:38:38.69 +58:52:39.6 -- not a known variable star
23:39:25.70 +58:42:32.0 -- not a known variable star
23:39:48.56 +61:18:30.8 -- not a known variable star
23:40:46.93 +63:26:00.8 -- not a known variable star
23:41:00.00 +61:53:50.3 -- not a known variable star
23:41:13.20 +63:17:37.1 -- a known variable star
23:41:17.56 +62:00:26.0 -- not a known variable star
23:41:45.24 +61:51:28.3 -- not a known variable star
23:41:50.50 +61:46:41.3 -- not a known variable star
23:41:58.52 +61:46:52.3 -- not a known variable star
23:42:59.68 +60:49:40.9 -- a known variable star
23:43:20.89 +61:27:22.4 -- not a known variable star
23:43:25.25 +61:39:45.1 -- not a known variable star
23:43:43.41 +61:38:14.8 -- not a known variable star
23:43:52.88 +61:33:20.7 -- not a known variable star
23:44:20.84 +62:52:52.9 -- not a known variable star
23:44:34.01 +61:05:32.3 -- not a known variable star
23:45:13.66 +62:42:06.1 -- not a known variable star
23:45:44.95 +58:00:45.6 -- not a known variable star
23:47:05.27 +61:58:45.6 -- not a known variable star
23:47:07.27 +61:58:00.1 -- not a known variable star
23:47:31.94 +58:42:08.7 -- not a known variable star
23:48:29.17 +63:09:26.4 -- a known variable star
23:48:30.54 +57:53:11.4 -- not a known variable star
23:49:03.26 +61:01:27.2 -- not a known variable star
23:49:34.29 +61:16:01.9 -- not a known variable star
23:51:31.92 +62:59:46.3 -- not a known variable star
23:51:37.24 +58:59:18.7 -- not a known variable star
23:51:41.08 +59:40:49.2 -- not a known variable star
23:51:50.90 +63:54:05.5 -- not a known variable star
23:52:08.17 +61:11:17.9 -- a known variable star
23:52:12.52 +62:33:17.4 -- a known variable star
23:54:14.18 +64:19:24.5 -- not a known variable star
23:55:07.77 +58:44:60.0 -- not a known variable star
23:55:54.85 +58:07:04.6 -- not a known variable star
23:56:58.03 +66:02:55.8 -- not a known variable star
23:57:05.06 +64:54:34.7 -- not a known variable star
23:57:46.55 +60:12:20.1 -- not a known variable star
23:57:48.00 +58:26:27.4 -- not a known variable star
23:58:05.29 +61:02:12.8 -- not a known variable star
23:58:38.93 +62:34:50.2 -- a known variable star
23:58:46.13 +61:10:36.3 -- not a known variable star
23:59:07.25 +60:39:40.5 -- not a known variable star
23:59:35.83 +63:32:19.3 -- not a known variable star
23:59:41.66 +63:30:22.5 -- not a known variable star
23:59:50.78 +64:23:14.2 -- not a known variable star
Found 165 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
192 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 192 (excluding asteroids and hot pixels, 165 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)2461136.93152927 -observatory V36
23:21:25.83 -06:20:47.4 Mercury (0.3mag)
02:22:37.94 +13:57:17.6 Venus (-3.9mag)
23:50:35.52 -02:08:07.2 Mars (1.2mag)
07:08:47.15 +22:52:18.5 Jupiter (-2.2mag)
00:24:52.23 +00:21:54.5 Saturn (0.9mag)
03:45:46.10 +19:41:14.3 Uranus (5.8mag)
00:09:33.74 -00:23:28.0 Neptune (7.8mag)
20:33:15.07 -22:52:29.1 Pluto (14.5mag)
16:07:59.31 -26:58:39.9 Moon (-11.4mag)
-rw-r--r-- 1 apache apache 362 Apr 6 05:44 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461136.93152927:
07:08:44.51 +22:52:20.9 Io (5.7mag)
07:08:58.02 +22:51:54.5 Europa (5.8mag)
07:08:45.76 +22:52:28.7 Ganymede (5.3mag)
07:08:15.84 +22:53:13.9 Callisto (6.5mag)
07:12:29.66 +22:44:41.1 Himalia (15.3mag)
07:08:51.44 +22:52:09.9 Thebe (16.2mag)
07:12:27.70 +23:13:30.3 Elara (17.2mag)
07:07:00.98 +23:37:19.4 Pasiphae (17.3mag)
07:17:18.72 +22:49:16.4 Carme (18.4mag)
00:24:47.72 +00:21:54.1 Titan (8.8mag)
00:24:48.87 +00:22:06.7 Rhea (10.1mag)
00:24:52.25 +00:23:26.4 Iapetus (11.5mag)
00:24:54.85 +00:21:42.1 Hyperion (14.8mag)
00:26:36.29 +00:31:42.1 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 6 05:44 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461136.93152927:
14:47:35.23 -08:33:11.6 JWST
17:18:46.37 +42:37:25.2 Chandra
08:53:19.10 -50:21:38.0 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 6 05:44 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461136.93152927 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:47:15.91 -28:14:54.1 13.9mag P/2010 H2 (Vales)
05:00:14.36 -70:08:07.4 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:30:36.56 +31:22:38.1 17.1mag C/2017 K2 (PANSTARRS)
17:30:56.62 +09:23:57.3 17.6mag C/2021 G2 (ATLAS)
23:07:25.79 +28:52:34.5 17.0mag C/2022 E2 (ATLAS)
04:18:15.84 +25:46:15.8 15.9mag C/2022 N2 (PANSTARRS)
09:01:53.33 +31:54:37.6 16.1mag C/2022 QE78 (ATLAS)
08:30:00.11 -01:12:18.9 17.3mag C/2022 R6 (PANSTARRS)
18:55:33.32 +17:42:56.6 17.5mag C/2023 A3 (Tsuchinshan-ATLAS)
15:43:26.96 -11:39:26.3 17.6mag P/2023 B1 (PANSTARRS)
09:12:41.51 -13:27:44.4 17.5mag C/2023 F3 (ATLAS)
21:43:45.77 +62:23:01.2 17.5mag C/2023 H5 (Lemmon)
19:26:15.93 -03:36:38.8 14.3mag C/2023 R1 (PANSTARRS)
21:42:35.48 +84:38:28.7 17.8mag C/2023 X2 (Lemmon)
06:14:34.88 +63:34:51.3 17.0mag C/2024 A1 (ATLAS)
04:51:38.73 +14:39:39.1 10.4mag C/2024 E1 (Wierzchos)
16:24:58.31 +04:49:02.1 17.4mag C/2024 G6 (ATLAS)
20:17:38.50 +12:44:42.6 14.7mag C/2024 J3 (ATLAS)
03:17:58.38 -23:53:02.9 16.4mag C/2024 T5 (ATLAS)
05:08:53.62 +47:46:09.2 17.7mag C/2025 J1 (Borisov)
14:18:08.45 +37:37:57.8 14.8mag C/2025 L1 (ATLAS)
03:10:43.28 -24:46:58.8 17.8mag C/2025 Q3 (ATLAS)
22:54:12.69 +19:50:15.9 10.1mag C/2025 R3 (PANSTARRS)
12:58:17.13 +02:24:28.4 17.5mag C/2025 Y1 (ATLAS)
01:35:25.40 +04:36:35.7 7.5mag C/2026 A1 (MAPS)
23:31:32.39 +35:17:49.7 14.3mag C/2026 B2 (Sun-Gao)
18:24:15.47 -10:12:26.4 12.4mag 10P/Tempel
15:12:36.41 +04:05:34.8 13.2mag 24P/Schaumasse
11:05:41.31 -01:51:18.2 15.7mag 29P/Schwassmann-Wachmann
17:56:53.81 -09:59:00.4 17.7mag 40P/Vaisala
10:38:49.50 -04:55:32.4 16.7mag 43P/Wolf-Harrington
01:33:55.40 +15:50:16.7 17.1mag 47P/Ashbrook-Jackson
06:53:44.43 +39:01:49.5 17.0mag 63P/Wild
23:16:37.73 -12:37:30.0 15.7mag 65P/Gunn
03:38:17.43 +17:49:38.7 15.8mag 76P/West-Kohoutek-Ikemura
00:44:36.22 +06:19:59.1 14.4mag 78P/Gehrels
22:33:19.00 -12:12:07.4 14.5mag 88P/Howell
01:43:49.67 +18:00:55.0 15.1mag 93P/Lovas
04:37:21.00 +31:44:33.1 16.3mag 123P/West-Hartley
08:18:09.23 +42:46:43.9 16.2mag 124P/Mrkos
02:18:34.96 +13:17:04.7 16.4mag 128P/Shoemaker-Holt
02:28:52.02 +13:17:06.3 17.5mag 131P/Mueller
00:37:04.95 +09:42:14.0 11.2mag 141P/Machholz
00:47:02.40 +01:17:19.9 11.3mag 141P-A/Machholz
23:37:28.03 -02:20:52.5 14.0mag 141P-D/Machholz
01:16:12.02 +02:57:27.1 17.9mag 141P-I/Machholz
00:35:48.34 -06:17:58.3 15.2mag 162P/SidingSpring
10:30:53.70 +31:29:30.6 17.8mag 164P/Christensen
06:18:52.20 +24:31:01.7 17.8mag 198P/ODAS
15:08:16.89 -01:09:55.6 17.4mag 210P/Christensen
21:09:41.46 -13:45:50.2 17.4mag 218P/LINEAR
17:12:44.07 -15:02:48.3 16.2mag 235P/LINEAR
05:14:09.70 +33:52:43.6 16.6mag 240P/NEAT
07:34:17.51 -06:15:29.1 17.6mag 242P/Spahr
15:45:52.20 +06:19:36.1 17.5mag 391P/Kowalski
07:30:59.12 +21:18:48.3 17.6mag 450P/LONEOS
05:22:15.02 +45:35:47.9 17.4mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.9K Apr 6 05:44 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
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.70 -27:51:49.80 SN2026gvk 2026-03-30 15.48
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.80 -63:44:05.50 ASASSN-26ch 2026-03-27.86 13.02
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.88 -53:16:33.80 ASASSN-26cc 2026-03-20.04 15.48
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.89 -15:50:13.40 AT2026fdy 2026-03-10.5 16.39
11:30:09.70 -47:26:45.00 ASASSN-26bn 2026-03-10.3 15.14
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.33 -37:49:33.00 ASASSN-26bk 2026-03-2.06 13.58
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.29 +19:58:46.30 ASASSN-26be 2026-02-25.56 14.95
17:40:18.19 +07:20:59.60 SN 2026crm 2026-02-24.34 16.9
18:38:36.11 -79:28:58.40 ASASSN-26bb 2026-02-24.36 16.11
17:43:29.75 +11:24:00.60 ASASSN-26bc 2026-02-23.37 -3.37
16:59:41.08 -80:01:51.20 ASASSN-26bd 2026-02-23.3 14.38
11:23:31.77 -08:39:15.40 SN2026cff 2026-02-23.15 -1.08
14:55:17.39 -05:56:05.30 SN2026dmk 2026-02-23.22 -0.76
12:28:15.19 +44:27:20.80 SN2026cjz 2026-02-23.47 15.62
12:12:29.55 -02:40:43.30 AT2026dsk 2026-02-23.4 17.21
09:21:05.29 +06:11:42.80 SN2026chr 2026-02-23.1 17.39
16:05:38.61 +18:06:07.40 SN 2026dsy 2026-02-23.36 17.15
04:55:50.66 -29:52:57.70 SN 2026dpg 2026-02-23.11 15.75
04:21:28.18 -53:22:54.40 AT2026drl 2026-02-21.03 17.31
11:50:37.32 +55:21:13.70 SN 2026dix 2026-02-21.43 16.39
16:21:19.69 -63:47:29.40 ASASSN-26az 2026-02-21.03 17.02
02:45:30.93 -54:17:43.10 SN 2026cju 2026-02-21.04 17.54
01:58:40.68 +47:34:50.10 ASASSN-26av 2026-02-21.09 15.97
18:35:53.01 -42:31:38.90 ASASSN-26aw 2026-02-21.12 15.89
11:40:18.88 -39:45:09.20 ASASSN-26ax 2026-02-21.08 15.73
02:26:23.52 -51:42:29.80 ASASSN-26ay 2026-02-21.04 13.93
08:46:07.66 +01:17:43.90 ASASSN-26ba 2026-02-20.23 15.43
14:15:47.69 -48:05:16.40 SN2026dez 2026-02-19.19 15.93
17:25:53.90 -23:28:31.50 ASASSN-26au 2026-02-18.33 15.82
16:07:59.09 -24:00:10.00 SN2026cmv 2026-02-17.28 16.19
18:15:01.25 -37:43:36.70 ASASSN-26at 2026-02-16.36 15.94
13:01:07.22 -11:25:16.10 AT2026bzh 2026-02-12.16 17.22
10:56:29.81 -07:07:25.30 SN 2026bre 2026-02-12.16 17.15
08:55:43.51 -53:26:11.50 ASASSN-26as 2026-02-12.2 16.54
06:33:50.98 -41:46:25.10 ASASSN-26ar 2026-02-12.04 16.42
12:15:22.43 +23:59:39.60 SN2026bzg 2026-02-11.27 16.32
08:01:10.95 -03:43:14.30 AT2026coj 2026-02-9.25 13.73
12:44:00.18 -57:03:46.80 ASASSN-26aq 2026-02-9.18 16
06:26:33.34 -54:06:39.90 AT2026cih 2026-02-8.06 17.26
23:08:59.40 -88:59:11.60 SN 2026bsu 2026-02-8.03 16.02
01:04:14.94 -62:31:02.30 SN 2026azk 2026-02-8.04 16.41
-rw-r--r-- 1 apache apache 5.8K Apr 6 05:44 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
06:57:11.19 -17:24:43.9 TCP J06571119-1724439 2026-01-18.5375 14.2mag
00:42:52.23 +41:01:44.7 PNV J00425223+4101447 2026-01-19.5505 18.74Cmag
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
-rw-r--r-- 1 apache apache 187K Apr 6 05:44 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
03:28:17.606 -27:41:55.66 AT 2026huw 2026-03-22.00 22.983
03:33:45.089 -26:56:57.92 AT 2026huv 2026-03-22.00 22.754
03:34:56.740 -28:52:22.60 AT 2026huu 2026-03-07.04 22.581
09:54:07.147 +02:31:26.93 AT 2026hut 2026-02-23.17 21.969
09:58:55.929 +02:50:43.70 AT 2026hus 2026-03-07.13 23.075
18:10:28.390 -00:15:37.94 AT 2026hur 2026-03-29.85 15.81
12:25:24.050 -04:47:33.90 AT 2026huq 2026-03-29.26 17.856
20:57:23.355 -24:44:41.72 AT 2026hup 2026-03-29.38 18.333
15:25:55.004 +07:49:25.15 AT 2026huo 2026-03-29.08 19.198
16:37:31.883 -66:34:41.26 AT 2026hun 2026-03-19.31 19.546
04:02:43.436 -46:55:47.58 AT 2026hum 2026-02-19.05 22.54
06:43:09.512 +11:30:54.69 AT 2026hul 2026-03-29.21 19.022
14:19:10.599 -33:29:33.62 AT 2026huk 2026-03-29.24 19.7
13:34:24.360 +36:48:31.82 AT 2026huj 2026-03-20.71 20.85
07:36:21.380 +15:56:54.55 AT 2026hui 2026-03-18.71 20.7
11:53:11.050 +21:20:34.15 AT 2026huh 2026-03-17.78 21.68
11:11:02.080 +21:51:43.20 AT 2026hug 2026-03-17.78 21.19
11:58:25.850 +16:51:27.33 AT 2026huf 2026-03-17.78 21.62
07:42:32.090 +18:28:41.88 AT 2026hue 2026-03-17.76 21.39
09:40:01.520 +16:17:02.86 AT 2026hud 2026-03-17.76 20.71
-rw-r--r-- 1 apache apache 30K Apr 6 05:44 tns_transients_list.txt
