This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR
The list of candidates will appear below. Please manually reload the page every few minutes untill the 'Processing complete' message appears.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2227422064650161920,2461149.8487,11.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 2227422064650161920 20260419.3487 11.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,11.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 20260419.3487 11.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,11.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 20260419.3487 11.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,11.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 20260419.3487 11.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.3487* 00 33 49.24 +70 43 00.5 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,11.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 20260419.3487 11.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,11.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 20260419.3487 11.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 19.3487* 00 29 13.99 +68 43 26.0 11.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,11.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 11.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.3487* 00 52 29.40 +72 25 53.7 10.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,10.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 10.95CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,14.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 20260419.3487 14.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,14.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 20260419.3487 14.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 19.3487* 00 42 07.12 +66 33 55.7 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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 19.3487* 00 49 50.18 +70 45 20.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 536102215936829440,2461149.8487,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
Gaia DR3 536102215936829440 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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
target 20260419.3487 13.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2215319942025058176,2461149.8487,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
Gaia DR3 2215319942025058176 20260419.3487 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
PT Cep,2461149.8487,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
PT Cep 20260419.3487 13.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2213544368181094144,2461149.8487,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
Gaia DR3 2213544368181094144 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2213911918603023360,2461149.8487,12.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 2213911918603023360 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.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 20260419.3487 12.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 12.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 12.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.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 20260419.3487 12.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 12.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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 19.3487* 00 36 22.59 +72 50 41.1 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 12.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx547871,2461149.8487,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
DocumentRef: VOTx547871 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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 19.3487* 00 43 31.57 +71 35 03.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 12.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx555721,2461149.8487,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
DocumentRef: VOTx555721 20260419.3487 13.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2214177210143764992,2461149.8487,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
Gaia DR3 2214177210143764992 20260419.3487 12.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx613260,2461149.8487,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
DocumentRef: VOTx613260 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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
target 20260419.3487 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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 19.3487* 00 43 48.14 +68 03 41.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 12.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2227587880448513152,2461149.8487,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 2227587880448513152 20260419.3487 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 13.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2227854069640021888,2461149.8487,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
Gaia DR3 2227854069640021888 20260419.3487 13.22CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.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
target 20260419.3487 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 13.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 13.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.3487* 00 33 18.03 +72 41 39.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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
target 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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
target 20260419.3487 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 13.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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
target 20260419.3487 13.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2214068427211151616,2461149.8487,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 2214068427211151616 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2210515286667075200,2461149.8487,13.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
Gaia DR3 2210515286667075200 20260419.3487 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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 19.3487* 00 57 13.72 +72 43 54.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx756390,2461149.8487,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
DocumentRef: VOTx756390 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.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 20260419.3487 13.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.3487* 23 52 54.03 +66 26 38.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 13.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 13.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.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 20260419.3487 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.3487* 00 28 00.13 +68 15 13.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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
target 20260419.3487 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!
TCP 2026 04 19.3487* 00 40 06.11 +66 56 02.5 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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
target 20260419.3487 13.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.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 20260419.3487 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.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 20260419.3487 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 13.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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
target 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 13.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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 19.3487* 23 47 22.74 +66 40 48.5 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2209928594134139136,2461149.8487,13.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
Gaia DR3 2209928594134139136 20260419.3487 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,14.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 20260419.3487 14.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.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
target 20260419.3487 13.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1052024,2461149.8487,13.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
DocumentRef: VOTx1052024 20260419.3487 13.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1051740,2461149.8487,14.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
DocumentRef: VOTx1051740 20260419.3487 14.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,14.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 20260419.3487 14.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,14.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 20260419.3487 14.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 19.3487* 00 41 17.73 +69 09 23.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,14.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 20260419.3487 14.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 14.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,14.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 20260419.3487 14.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,14.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 14.45CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,14.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 20260419.3487 14.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.3487* 23 49 13.12 +66 25 43.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1242076,2461149.8487,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
DocumentRef: VOTx1242076 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1243486,2461149.8487,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
DocumentRef: VOTx1243486 20260419.3487 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 19.3487* 00 34 27.31 +66 39 33.7 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1241841,2461149.8487,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
DocumentRef: VOTx1241841 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,11.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 20260419.3487 11.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 19.3487* 00 41 09.21 +67 22 38.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,11.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 11.92CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 12.45CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,13.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 13.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.3487* 00 48 47.80 +69 04 47.6 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J232017.97+680550.0,2461149.8487,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
ASASSN-V J232017.97+680550.0 20260419.3487 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 19.3487* 00 14 20.74 +66 22 58.1 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 528266683758045824,2461149.8487,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
Gaia DR3 528266683758045824 20260419.3487 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 19.3487* 00 43 57.77 +68 38 26.9 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
TCP 2026 04 19.3487* 00 29 09.35 +69 46 48.9 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 12.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J2337044+684351,2461149.8487,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
NSVS J2337044+684351 20260419.3487 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 19.3487* 00 39 31.51 +68 37 42.2 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.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
target 20260419.3487 12.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 19.3487* 00 39 19.63 +69 20 34.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 12.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.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 20260419.3487 12.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 19.3487* 00 30 13.22 +67 40 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 12.92CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.3487* 00 29 48.56 +69 19 54.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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
target 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.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 20260419.3487 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.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 20260419.3487 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 12.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.3487* 00 44 59.68 +68 02 44.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 529377534101809664,2461149.8487,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
Gaia DR3 529377534101809664 20260419.3487 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 19.3487* 00 39 22.33 +67 01 50.5 11.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,11.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.3487 11.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.3487* 00 46 04.89 +72 43 44.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 536737566154771072,2461149.8487,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 536737566154771072 20260419.3487 12.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 19.3487* 00 32 14.67 +68 57 54.2 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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
target 20260419.3487 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 19.3487* 00 36 10.77 +65 54 14.9 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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 19.3487* 00 18 12.64 +66 24 41.5 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,12.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 20260419.3487 12.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 19.3487* 00 27 56.55 +67 37 15.3 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,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 20260419.3487 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 19.3487* 00 40 25.84 +65 36 38.1 11.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,11.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 20260419.3487 11.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 19.3487* 00 44 11.17 +69 33 32.1 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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.8487,11.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 20260419.3487 11.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 537392286670030208,2461149.8487,12.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 537392286670030208 20260419.3487 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J2334044+691146,2461149.8487,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
NSVS J2334044+691146 20260419.3487 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1214273,2461149.8487,13.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1214273 20260419.3487 13.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.3487* 00 37 24.68 +69 50 52.7 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1219832,2461149.8487,12.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1219832 20260419.3487 12.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.3487* 00 30 57.49 +66 20 59.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.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 527808810183784704,2461149.8487,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
Gaia DR3 527808810183784704 20260419.3487 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
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461036.59057495 27.12.2025 02:10:15.676 /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
First image: 2461036.59057495 27.12.2025 02:10:15.676 /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
Last image: 2461149.84895525 19.04.2026 08:22:19.734 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.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.91
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: 8 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): 14824
Objects passed selection criteria: 14749
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: 10611.5
Average stars matched: 9605 (90.515 %)
Memory usage VmPeak: 118340 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Apr 16 15:05:05 CDT 2026
VaST build number 1.0rc89-19-g55e4b97d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sun Apr 19 03:29:47 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.59057495 27.12.2025 02:10:15.676 /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
First image: 2461036.59057495 27.12.2025 02:10:15.676 /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
Last image: 2461149.84895525 19.04.2026 08:22:19.734 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 280
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.56
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: 39 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): 98320
Objects passed selection criteria: 98078
Measurements per detected object (mean, median, min, max): 2.8 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.8 2.0 2 4
Average stars detected per image: 72559
Average stars matched: 65555.5 (90.3479 %)
Memory usage VmPeak: 1875812 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Apr 16 15:05:05 CDT 2026
VaST build number 1.0rc89-19-g55e4b97d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sun Apr 19 03:43:41 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/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
SExtractor catalog cache: saved Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat to cache
SExtractor catalog cache: saved Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.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/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
Checking WCS cache directory local_wcs_cache
Checking WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Found WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Checking WCS cache directory /home/NMW_web_upload/solved_reference_images
Checking WCS cache directory /dataX/kirx/NMW_NG_rt3_autumn2019/solved_reference_images
The reference JD(UT) for computing planet and comet positions: 2461149.84844492
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_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits exists and is non-empty
Saving wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits to local_wcs_cache/
'wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits' -> 'local_wcs_cache/wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits'
wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits exists and is non-empty
Saving wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits to local_wcs_cache/
'wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits' -> 'local_wcs_cache/wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits'
wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits exists and is non-empty
Saving wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits to local_wcs_cache/
'wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits' -> 'local_wcs_cache/wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits'
wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits exists and is non-empty
Saving wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits to local_wcs_cache/
'wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits' -> 'local_wcs_cache/wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits (1st reference image)
verification OK: wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
Image size: 941.6'x627.0' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:02.007 +69:59:50.87 J2000 4789.000 3195.000
###################################
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits (1st new image)
verification OK: wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
Image size: 924.4'x626.2' 15.4(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.79"/pix along the X axis and 5.88"/pix along the Y axis
Image center: 23:59:37.233 +70:01:08.36 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 00:00:02.007 +69:59:50.87
Second-epoch image center 23:59:37.233 +70:01:08.36
Angular distance between the image centers 0.0413 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits (2nd new image)
verification OK: wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
Image size: 924.4'x626.2' 15.4(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.79"/pix along the X axis and 5.88"/pix along the Y axis
Image center: 23:59:38.039 +70:01:00.88 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 00:00:02.007 +69:59:50.87
Second-epoch image center 23:59:38.039 +70:01:00.88
Angular distance between the image centers 0.0393 deg.
###################################
###################################
# Check the image center offset between the first and the second second-epoch image (shift should be applied between the second-epoch images)
Second-epoch first image center 23:59:37.233 +70:01:08.36
Second-epoch second image center 23:59:38.039 +70:01:00.88
Angular distance between the image centers 0.00237 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/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits &> /tmp/tmp.0IywvtyouZ
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits &> /tmp/tmp.AvGHtE9EHA
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits &> /tmp/tmp.K78wJFGRmO
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits &> /tmp/tmp.tEe6Q5fA7A
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
Calibrating the magnitude scale
Found non-empty wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.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_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits and wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.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_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits and wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat
Found non-empty wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits and wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat
The reference image (wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits) and catalog (wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat) found
'wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat' -> 'wcsmag.cat'
Read 16658 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0025 to 359.9970 deg, Dec +62.8658 to +75.5048 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.0025 to 359.9970 deg, Dec 62.8658 to 75.5048 deg
Loaded 84082 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): 8746 out of 9568 total matches.
Matched with Tycho-2 9568 out of 16658 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.942221
a=0.000000 b=1.000000 c=22.942221
From vast_summary.log: estimated ref. image limiting mag.: -7.91
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.03
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.03
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 10 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.5 pix Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
2.5 pix Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
2.8 pix fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
2.8 pix fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
Limiting magnitude estimates:
15.0 mag. Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
15.0 mag. Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
14.4 mag. fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
14.4 mag. fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
All-image limiting magnitude estimate: 14.4 (SNR ) 11.7 (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.0IywvtyouZ (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/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits' -> 'wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
WCS_IMAGE_NAME=wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
WCS-calibrated image found: wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
Checking if the catalog wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat corresponding to the image wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits alredy exist and is non-empty...
Catalog wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat corresponding to the image wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
WCS catalog name: wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1610, passed=16658
Got 16658 stars (including 15034 good ones) from the SExtractor catalog wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat
util/solve_plate_with_UCAC5 got 16658 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.6'
Seting catalog search parameters based on the expected field of view 941.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013078 (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.010462 (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 332.9470 through 0 to 28.4123, gap 28.4123 to 332.9470
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.9 to 75.5)
Done reading UCAC5 zone files...
Matched 968 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 968 matched stars entering correct_measured_positions(), 954 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.53"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 968 matched stars entering correct_measured_positions(), 16285 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 332.9477 through 0 to 28.4145, gap 28.4145 to 332.9477
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.9 to 75.5)
Done reading UCAC5 zone files...
Matched 968 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 968 matched stars entering correct_measured_positions(), 16286 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.51"
Accuracy estimation diagnostic: 968 matched stars entering correct_measured_positions(), 16286 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.53"
Excluding outliers - 968 stars left (next iteration limit 1064)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits -region wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.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.AvGHtE9EHA (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/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits 570.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits' -> 'wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
WCS_IMAGE_NAME=wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
WCS-calibrated image found: wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
Checking if the catalog wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat corresponding to the image wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits alredy exist and is non-empty...
Catalog wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat corresponding to the image wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
WCS catalog name: wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1667, passed=16773
Got 16773 stars (including 15086 good ones) from the SExtractor catalog wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat
util/solve_plate_with_UCAC5 got 16773 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.8'
Seting catalog search parameters based on the expected field of view 932.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012956 (46.6 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010364 (37.3 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 333.1738 through 0 to 27.8274, gap 27.8274 to 333.1738
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.9 to 75.5)
Done reading UCAC5 zone files...
Matched 338 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 286 matched stars entering correct_measured_positions(), 248 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.96"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 281 matched stars entering correct_measured_positions(), 4475 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.35"
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 333.1326 through 0 to 27.8046, gap 27.8046 to 333.1326
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.9 to 75.5)
Done reading UCAC5 zone files...
Matched 416 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 387 matched stars entering correct_measured_positions(), 4504 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.13"
Accuracy estimation diagnostic: 386 matched stars entering correct_measured_positions(), 5814 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.47"
Excluding outliers - 386 stars left (next iteration limit 309)
The image catalog is written to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits -region wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.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.K78wJFGRmO (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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
WCS_IMAGE_NAME=wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
WCS-calibrated image found: wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
Checking if the catalog wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat corresponding to the image wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits alredy exist and is non-empty...
Catalog wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat corresponding to the image wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
WCS catalog name: wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat
SExtractor catalog parsing summary: zero_flux=15, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=801, passed=10452
Got 10452 stars (including 9643 good ones) from the SExtractor catalog wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat
util/solve_plate_with_UCAC5 got 10452 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.4'
Seting catalog search parameters based on the expected field of view 924.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012839 (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.010271 (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 331.9487 through 0 to 26.8616, gap 26.8616 to 331.9487
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.6 to 75.2)
Done reading UCAC5 zone files...
Matched 268 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 203 matched stars entering correct_measured_positions(), 134 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.34"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 197 matched stars entering correct_measured_positions(), 2034 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.83"
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 331.9333 through 0 to 26.8549, gap 26.8549 to 331.9333
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.6 to 75.2)
Done reading UCAC5 zone files...
Matched 322 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 272 matched stars entering correct_measured_positions(), 2079 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.71"
Accuracy estimation diagnostic: 270 matched stars entering correct_measured_positions(), 2957 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.21"
Excluding outliers - 270 stars left (next iteration limit 216)
The image catalog is written to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits -region wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.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.tEe6Q5fA7A (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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
WCS_IMAGE_NAME=wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
WCS-calibrated image found: wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
Checking if the catalog wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat corresponding to the image wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits alredy exist and is non-empty...
Catalog wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat corresponding to the image wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
WCS catalog name: wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=749, passed=10582
Got 10582 stars (including 9826 good ones) from the SExtractor catalog wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat
util/solve_plate_with_UCAC5 got 10582 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.4'
Seting catalog search parameters based on the expected field of view 924.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012839 (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.010271 (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 331.9486 through 0 to 26.8601, gap 26.8601 to 331.9486
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.6 to 75.2)
Done reading UCAC5 zone files...
Matched 266 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 204 matched stars entering correct_measured_positions(), 135 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.41"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 196 matched stars entering correct_measured_positions(), 2067 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.78"
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 331.9347 through 0 to 26.8525, gap 26.8525 to 331.9347
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.6 to 75.2)
Done reading UCAC5 zone files...
Matched 320 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 271 matched stars entering correct_measured_positions(), 2113 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.48"
Accuracy estimation diagnostic: 270 matched stars entering correct_measured_positions(), 3045 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.85"
Excluding outliers - 270 stars left (next iteration limit 215)
The image catalog is written to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits -region wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.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_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits'
Saving fully-calibrated image wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits'
Saving fully-calibrated image wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits'
Saving fully-calibrated image wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits'
Preparing the HTML report for the field Cep-03-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Adding exclusion_list_local.txt__out02818.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out09685.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out20748.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out21839.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out22317.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out22775.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out23090.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out23308.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 118s
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: 6s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 20748_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 20748_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 20973_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 20973_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 00:12:22.09 +73:46:39.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21748_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 21748_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 00:24:03.95 +70:07:32.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21839_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 21839_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 22317_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 22317_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 22775_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 22775_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 23090_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 23090_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 23308_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 23308_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 09685_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 09685_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 02818_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 02818_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
make_report_in_HTML.sh Phase 2 (HTML assembly): 0s
make_report_in_HTML.sh TOTAL: 124s
Prepared the HTML report for the field Cep-03-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:52:29.40 +72:25:53.7
00:29:13.99 +68:43:26.0
23:12:06.20 +71:04:34.9
23:34:17.29 +72:51:34.9
23:40:13.45 +70:25:07.8
23:39:23.62 +66:57:49.1
00:33:49.24 +70:43:00.5
23:48:19.77 +68:50:10.7
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/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
SExtractor catalog cache: saved Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat to cache
SExtractor catalog cache: saved Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
Creating symlink local_wcs_cache/wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
Creating symlink local_wcs_cache/wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
Creating symlink local_wcs_cache/wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.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_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits exists and is non-empty
wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits exists and is non-empty
wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits exists and is non-empty
wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits exists and is non-empty
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits (1st reference image)
verification OK: wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
Image size: 941.6'x627.0' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:02.007 +69:59:50.87 J2000 4789.000 3195.000
###################################
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits (1st new image)
verification OK: wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
Image size: 924.4'x626.2' 15.4(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.79"/pix along the X axis and 5.88"/pix along the Y axis
Image center: 23:59:37.233 +70:01:08.36 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 00:00:02.007 +69:59:50.87
Second-epoch image center 23:59:37.233 +70:01:08.36
Angular distance between the image centers 0.0413 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits (2nd new image)
verification OK: wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
Image size: 924.4'x626.2' 15.4(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.79"/pix along the X axis and 5.88"/pix along the Y axis
Image center: 23:59:38.039 +70:01:00.88 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 00:00:02.007 +69:59:50.87
Second-epoch image center 23:59:38.039 +70:01:00.88
Angular distance between the image centers 0.0393 deg.
###################################
###################################
# Check the image center offset between the first and the second second-epoch image (shift should be applied between the second-epoch images)
Second-epoch first image center 23:59:37.233 +70:01:08.36
Second-epoch second image center 23:59:38.039 +70:01:00.88
Angular distance between the image centers 0.00237 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/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits &> /tmp/tmp.jE8UjSssqT
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits &> /tmp/tmp.w93XjdQ3LV
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits &> /tmp/tmp.Nek6DzxclB
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits &> /tmp/tmp.63JUko7RPS
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
Calibrating the magnitude scale
Found non-empty wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.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_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits and wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.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_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits and wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat
Found non-empty wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits and wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat
The reference image (wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits) and catalog (wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat) found
'wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat' -> 'wcsmag.cat'
Read 114234 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0012 to 359.9997 deg, Dec +62.7863 to +75.5048 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.0012 to 359.9997 deg, Dec 62.7863 to 75.5048 deg
Loaded 84921 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): 7448 out of 9832 total matches.
Matched with Tycho-2 9832 out of 114234 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.779293
a=0.000000 b=1.000000 c=22.779293
From vast_summary.log: estimated ref. image limiting mag.: -7.56
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.22
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.22
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 230 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.3 pix Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
2.3 pix Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
2.5 pix fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
2.5 pix fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
Limiting magnitude estimates:
15.2 mag. Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
15.2 mag. Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
14.5 mag. fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
14.5 mag. fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
All-image limiting magnitude estimate: 14.5 (SNR ) 14.0 (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.jE8UjSssqT (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/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits' -> 'wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
WCS_IMAGE_NAME=wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
WCS-calibrated image found: wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
Checking if the catalog wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat corresponding to the image wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits alredy exist and is non-empty...
Catalog wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat corresponding to the image wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
WCS catalog name: wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=42, blended=12405, passed=114192
Got 114192 stars (including 101585 good ones) from the SExtractor catalog wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat
util/solve_plate_with_UCAC5 got 114192 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.6'
Seting catalog search parameters based on the expected field of view 941.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013078 (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.010462 (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 332.6411 through 0 to 28.4717, gap 28.4717 to 332.6411
Reading UCAC5 zone files...
Searching UCAC5 zones 763 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 974 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 969 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.50"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 112172 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.49"
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 332.6416 through 0 to 28.4739, gap 28.4739 to 332.6416
Reading UCAC5 zone files...
Searching UCAC5 zones 763 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 974 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 112171 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.49"
Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 112171 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.50"
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_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits -region wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.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.w93XjdQ3LV (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/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits 570.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits' -> 'wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
WCS_IMAGE_NAME=wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
WCS-calibrated image found: wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
Checking if the catalog wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat corresponding to the image wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits alredy exist and is non-empty...
Catalog wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat corresponding to the image wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
WCS catalog name: wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat
SExtractor catalog parsing summary: zero_flux=2, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=43, blended=12319, passed=113226
Got 113226 stars (including 100709 good ones) from the SExtractor catalog wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat
util/solve_plate_with_UCAC5 got 113226 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.8'
Seting catalog search parameters based on the expected field of view 932.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012956 (46.6 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010364 (37.3 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 332.7589 through 0 to 27.9073, gap 27.9073 to 332.7589
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 349 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 300 matched stars entering correct_measured_positions(), 256 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.18"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 293 matched stars entering correct_measured_positions(), 27938 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.75"
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 332.7145 through 0 to 27.8794, gap 27.8794 to 332.7145
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 414 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 384 matched stars entering correct_measured_positions(), 27964 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.74"
Accuracy estimation diagnostic: 384 matched stars entering correct_measured_positions(), 35081 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.75"
Excluding outliers - 384 stars left (next iteration limit 322)
The image catalog is written to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits -region wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.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.Nek6DzxclB (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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
WCS_IMAGE_NAME=wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
WCS-calibrated image found: wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
Checking if the catalog wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat corresponding to the image wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits alredy exist and is non-empty...
Catalog wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat corresponding to the image wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
WCS catalog name: wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat
SExtractor catalog parsing summary: zero_flux=7, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=10, blended=5641, passed=65572
Got 65572 stars (including 59870 good ones) from the SExtractor catalog wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat
util/solve_plate_with_UCAC5 got 65572 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.4'
Seting catalog search parameters based on the expected field of view 924.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012839 (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.010271 (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 331.9272 through 0 to 27.1320, gap 27.1320 to 331.9272
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.5 to 75.2)
Done reading UCAC5 zone files...
Matched 259 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 207 matched stars entering correct_measured_positions(), 148 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.45"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 197 matched stars entering correct_measured_positions(), 12146 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.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 331.8971 through 0 to 27.1140, gap 27.1140 to 331.8971
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.5 to 75.2)
Done reading UCAC5 zone files...
Matched 347 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 311 matched stars entering correct_measured_positions(), 12207 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.94"
Accuracy estimation diagnostic: 307 matched stars entering correct_measured_positions(), 18670 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.36"
Excluding outliers - 307 stars left (next iteration limit 216)
The image catalog is written to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits -region wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.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.63JUko7RPS (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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
WCS_IMAGE_NAME=wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
WCS-calibrated image found: wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
Checking if the catalog wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat corresponding to the image wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits alredy exist and is non-empty...
Catalog wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat corresponding to the image wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
WCS catalog name: wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=8, blended=5527, passed=65287
Got 65287 stars (including 59686 good ones) from the SExtractor catalog wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat
util/solve_plate_with_UCAC5 got 65287 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.4'
Seting catalog search parameters based on the expected field of view 924.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012839 (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.010271 (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 331.9276 through 0 to 27.1285, gap 27.1285 to 331.9276
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.5 to 75.2)
Done reading UCAC5 zone files...
Matched 263 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 206 matched stars entering correct_measured_positions(), 139 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.09"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 196 matched stars entering correct_measured_positions(), 12105 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.01"
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 331.9032 through 0 to 27.1188, gap 27.1188 to 331.9032
Reading UCAC5 zone files...
Searching UCAC5 zones 767 to 828 (Dec 63.5 to 75.2)
Done reading UCAC5 zone files...
Matched 333 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 294 matched stars entering correct_measured_positions(), 12144 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.96"
Accuracy estimation diagnostic: 294 matched stars entering correct_measured_positions(), 18531 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.77"
Excluding outliers - 294 stars left (next iteration limit 215)
The image catalog is written to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits -region wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.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_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/wcs_Cep-03-Q2b1x1_2025-12-26_20-10-15_20.00sec_-15.00C_LIGHT_0065.fits
Saving fully-calibrated image wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/wcs_Cep-03-Q2b1x1_2025-12-26_20-10-55_20.00sec_-14.90C_LIGHT_0066.fits
Saving fully-calibrated image wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-21-35_20.00sec_-4.90C_LIGHT_0637.fits
Saving fully-calibrated image wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.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-19_CI_Cep-03-Q2b1x1_032305_TTUQ2b1x1_2962829_240p5kLR/wcs_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.fits
Preparing the HTML report for the field Cep-03-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__out132425.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out100627.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out100766.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out102382.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out103036.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out105084.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out106253.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out106959.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out107881.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out108399.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out109167.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out110569.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out111837.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out111976.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out124935.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out124936.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out125509.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out125557.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out132387.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out132389.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out132399.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out132401.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out132403.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out132415.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out132418.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out132419.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out136489.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out136935.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out136991.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out137563.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out137692.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out137707.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out138005.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out138427.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out138570.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out139069.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out139080.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out139413.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out139563.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out139622.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out139985.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out140300.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out140623.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out140682.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out140737.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out140965.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141247.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141270.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141308.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141310.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141317.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141393.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142194.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142281.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142396.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142562.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142786.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143481.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143646.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143687.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143717.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143758.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143808.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143972.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144273.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144279.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144289.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144543.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144629.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144871.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144894.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145133.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145305.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145374.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145444.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145542.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145565.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145592.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out145971.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out146259.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out146326.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out146354.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out146425.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out146503.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out146574.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out146722.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out147011.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out147071.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out147925.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out148078.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out148535.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out148794.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out148904.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out149417.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out149853.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out149898.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out150016.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out150076.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out150221.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out150234.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out17856.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out30532.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out54575.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out55137.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out56057.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out58267.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out58845.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out59911.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out60350.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out60798.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out62544.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out66618.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out66682.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out68091.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out68603.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out71681.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out72860.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out89550.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out92764.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out93485.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out94536.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out94577.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out97891.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out99110.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 512s
Pre-generating preview images in parallel...
Done pre-generating preview images.
Pre-generating finding charts in parallel...
Done pre-generating finding charts.
make_report_in_HTML.sh Pre-generation: 77s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132387_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 132387_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132389_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 132389_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132395_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 132395_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132399_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 132399_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132401_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 132401_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132403_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 132403_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132404_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 132404_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132406_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 132406_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (23.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132415_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 132415_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132418_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 132418_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132419_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 132419_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132424_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 132424_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 00:33:01.27 +66:44:45.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132425_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 132425_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 23:11:28.63 +67:30:52.0 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.04, MAG_FAINT_SEARCH_LIMIT=13.02)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 133598_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 133598_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 00:24:04.11 +70:07:31.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 133675_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 133675_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 23:34:17.03 +72:51:34.5 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 135763_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 135763_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 135797_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 135797_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 136082_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 136082_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 136489_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 136489_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 136560_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 136560_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 136690_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 136690_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 136935_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 136935_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 136991_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 136991_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137075_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 137075_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137157_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 137157_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137300_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 137300_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137534_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 137534_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137563_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 137563_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137634_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 137634_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (23.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137692_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 137692_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137707_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 137707_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137830_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 137830_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137907_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 137907_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137994_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 137994_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138003_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 138003_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138005_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 138005_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138427_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 138427_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138471_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 138471_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138532_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 138532_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138568_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 138568_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138570_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 138570_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138643_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 138643_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138759_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 138759_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138800_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 138800_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138861_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 138861_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 138880_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 138880_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139019_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 139019_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139069_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 139069_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139080_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 139080_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139413_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 139413_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139420_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 139420_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139473_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 139473_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 00:00:30.37 +70:55:07.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139563_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 139563_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139606_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 139606_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139622_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 139622_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139728_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 139728_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139734_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 139734_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139885_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 139885_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139985_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 139985_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140192_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 140192_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140300_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 140300_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140313_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 140313_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140457_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 140457_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140575_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 140575_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140623_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 140623_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140682_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 140682_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140737_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 140737_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140965_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 140965_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141066_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 141066_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141079_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 141079_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141247_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 141247_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141270_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 141270_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141308_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 141308_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141310_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 141310_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141317_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 141317_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141318_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 141318_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141393_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 141393_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141482_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 141482_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141711_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 141711_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142100_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 142100_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142194_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 142194_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142281_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 142281_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142396_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 142396_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142412_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 142412_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (18.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142562_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 142562_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142730_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 142730_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142786_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 142786_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142796_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 142796_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142932_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 142932_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142987_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 142987_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143042_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 143042_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143086_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 143086_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143383_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 143383_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143445_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 143445_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 23:58:35.40 +66:51:20.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143481_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 143481_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143645_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 143645_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (35.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143646_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 143646_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143687_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 143687_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143706_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 143706_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143717_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 143717_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143758_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 143758_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Successfully moved fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638.png to transient_report/143758_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638_discovery2.png
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143808_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 143808_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143817_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 143817_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143972_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 143972_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144248_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 144248_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 00:40:07.99 +65:57:32.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144273_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 144273_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144279_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 144279_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144289_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 144289_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144306_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 144306_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144543_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 144543_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144629_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 144629_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144771_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 144771_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144857_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 144857_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144871_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 144871_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144894_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 144894_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145133_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 145133_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145279_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 145279_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145305_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 145305_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145316_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 145316_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145374_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 145374_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145409_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 145409_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145444_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 145444_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145542_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 145542_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145565_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 145565_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145578_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 145578_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145587_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 145587_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 00:00:09.45 +71:30:28.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145592_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 145592_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145931_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 145931_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 145971_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 145971_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146096_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 146096_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146221_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 146221_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146259_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 146259_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146326_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 146326_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146354_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 146354_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146425_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 146425_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146491_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 146491_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146503_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 146503_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146560_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 146560_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146574_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 146574_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146596_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 146596_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146722_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 146722_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146755_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 146755_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146897_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 146897_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 147011_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 147011_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 147071_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 147071_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 147804_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 147804_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 147899_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 147899_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 147925_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 147925_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 148078_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 148078_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 148394_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 148394_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 148484_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 148484_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 148514_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 148514_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 148535_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 148535_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 148687_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 148687_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 148791_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 148791_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 148794_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 148794_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 148904_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 148904_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 148951_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 148951_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 149417_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 149417_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 149471_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 149471_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 149565_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 149565_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (17.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 149695_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 149695_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 149743_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 149743_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 149853_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 149853_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 149898_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 149898_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 149955_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 149955_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 149973_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 149973_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150016_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 150016_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150076_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 150076_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150137_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 150137_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150221_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 150221_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150234_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 150234_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150303_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 150303_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (21.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150338_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 150338_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150339_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 150339_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150453_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 150453_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (18.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150522_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 150522_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150526_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 150526_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (20.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150541_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 150541_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 150611_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 150611_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 112546_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 112546_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (23.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 89550_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 89550_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 68603_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 68603_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58845_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 58845_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 109167_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 109167_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 18477_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 18477_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 00:52:29.00 +72:25:53.4 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 102382_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 102382_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 54575_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 54575_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 111976_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 111976_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 103036_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 103036_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 106253_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 106253_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 59911_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 59911_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 106959_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 106959_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 91576_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 91576_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 93485_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 93485_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 66618_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 66618_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58267_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 58267_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 108399_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 108399_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 68091_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 68091_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 45630_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 45630_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 60350_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 60350_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 100766_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 100766_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 100627_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 100627_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 111837_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 111837_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 125557_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 125557_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 125509_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 125509_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 99110_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 99110_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 124936_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 124936_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 124935_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 124935_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 69434_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 69434_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 00:29:14.65 +68:43:22.3 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 110607_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 110607_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (23.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 59652_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 59652_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 105084_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 105084_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 62544_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 62544_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 71681_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 71681_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 13668_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 13668_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
**** FOUND 00:12:21.08 +73:46:42.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 107881_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 107881_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 17856_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 17856_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 66682_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 66682_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 94536_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 94536_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 94577_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 94577_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 110569_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 110569_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 62191_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
The candidate 62191_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 92764_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 92764_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 56057_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 56057_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 30532_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 30532_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 72860_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 72860_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 60798_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 60798_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 55137_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 55137_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 97891_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
Preparing report for the candidate 97891_fd_Cep-03-Q2b1x1_2026-04-19_03-22-19_20.00sec_-4.90C_LIGHT_0638
make_report_in_HTML.sh Phase 2 (HTML assembly): 6s
make_report_in_HTML.sh TOTAL: 595s
Prepared the HTML report for the field Cep-03-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
00:52:29.40 +72:25:53.7
00:29:13.99 +68:43:26.0
23:12:06.20 +71:04:34.9
23:34:17.29 +72:51:34.9
23:40:13.45 +70:25:07.8
23:39:23.62 +66:57:49.1
00:33:49.24 +70:43:00.5
23:48:19.77 +68:50:10.7
00:09:47.48 +67:04:04.9
00:03:02.04 +67:14:10.6
00:34:27.31 +66:39:33.7
23:58:03.26 +68:23:14.5
00:24:45.20 +67:11:24.7
23:53:21.67 +67:51:45.3
23:20:14.68 +68:05:51.9
00:39:22.33 +67:01:50.5
23:37:01.19 +68:43:53.2
00:16:14.36 +68:25:12.4
00:27:56.55 +67:37:15.3
00:30:13.22 +67:40:00.7
00:41:09.21 +67:22:38.7
00:22:40.46 +70:54:28.0
23:44:28.54 +70:44:43.0
23:46:30.01 +71:46:07.7
00:29:48.56 +69:19:54.4
23:30:28.12 +73:26:19.2
23:27:13.15 +70:39:46.2
00:42:07.12 +66:33:55.7
00:49:50.18 +70:45:20.0
00:03:31.47 +71:52:30.3
23:40:45.58 +70:22:21.7
23:40:21.22 +70:26:28.5
23:16:40.82 +66:55:22.7
23:18:14.04 +68:07:16.9
23:09:12.44 +73:13:18.2
00:19:26.19 +69:46:58.7
00:24:21.99 +71:46:06.3
23:49:27.02 +68:32:57.8
23:20:10.44 +73:52:30.6
00:19:51.70 +69:24:12.1
00:01:05.75 +73:33:46.4
00:36:22.59 +72:50:41.1
23:27:02.44 +65:39:09.9
23:36:37.05 +67:50:25.4
00:43:31.57 +71:35:03.9
23:27:20.51 +70:16:53.6
23:37:14.99 +68:45:05.4
23:16:02.46 +72:16:17.5
23:55:21.32 +72:45:19.3
23:33:44.18 +68:01:59.1
23:39:21.85 +70:45:33.2
00:21:10.65 +71:25:58.9
23:22:34.52 +71:47:18.5
00:43:48.14 +68:03:41.7
23:28:57.39 +72:12:38.4
23:38:57.92 +73:58:21.1
00:24:17.37 +73:48:35.4
23:56:57.17 +72:46:45.0
00:04:56.74 +73:01:03.5
00:05:44.29 +70:04:15.3
23:51:45.65 +72:42:20.4
23:12:40.53 +67:24:26.9
23:28:16.84 +72:47:41.8
00:33:18.03 +72:41:39.2
23:17:37.33 +71:01:12.1
23:38:17.38 +70:35:09.3
00:01:42.83 +67:24:15.5
00:18:16.60 +73:01:26.3
00:24:45.16 +71:46:25.6
23:51:42.21 +72:42:02.1
23:24:39.53 +69:56:59.3
00:21:21.70 +73:10:03.5
23:34:47.21 +72:38:19.4
23:45:59.56 +72:21:44.8
23:31:00.45 +69:03:49.5
23:17:21.27 +66:30:42.9
23:59:34.61 +66:56:30.7
00:57:13.72 +72:43:54.8
23:28:23.00 +72:48:08.0
23:52:54.03 +66:26:38.3
00:06:09.62 +73:52:27.6
00:26:55.04 +68:56:07.3
00:09:37.77 +67:18:49.7
23:11:57.01 +71:04:36.2
00:28:00.13 +68:15:13.4
00:03:54.91 +67:08:10.8
00:40:06.11 +66:56:02.5
00:18:10.84 +67:57:22.0
23:55:45.88 +66:53:05.2
23:58:47.62 +68:23:45.1
00:02:52.09 +68:31:16.8
23:13:08.22 +69:03:28.2
23:39:28.34 +66:08:37.2
23:47:22.74 +66:40:48.5
23:04:23.95 +73:34:47.8
00:18:36.18 +73:54:58.7
00:22:13.54 +67:48:43.6
23:47:39.45 +67:18:32.2
23:46:54.28 +67:33:51.3
23:29:04.86 +70:33:49.8
23:08:21.02 +71:05:57.1
00:41:17.73 +69:09:23.8
00:05:08.48 +73:52:07.6
23:35:54.73 +69:06:29.6
23:26:52.84 +73:20:04.0
00:18:19.77 +73:46:24.1
23:23:13.55 +70:54:30.8
00:46:04.89 +72:43:44.4
00:09:22.70 +72:24:46.3
23:20:26.67 +70:51:31.5
00:37:24.68 +69:50:52.7
00:44:11.17 +69:33:32.1
00:29:09.35 +69:46:48.9
00:04:44.78 +70:08:19.7
00:48:47.80 +69:04:47.6
00:39:19.63 +69:20:34.4
00:24:28.40 +69:41:34.5
00:15:04.16 +69:41:32.9
00:43:57.77 +68:38:26.9
00:32:14.67 +68:57:54.2
00:39:31.51 +68:37:42.2
23:55:18.60 +69:28:36.0
00:44:59.68 +68:02:44.6
23:34:02.09 +69:11:47.7
23:49:13.12 +66:25:43.1
00:40:25.84 +65:36:38.1
00:14:20.74 +66:22:58.1
00:36:10.77 +65:54:14.9
00:18:12.64 +66:24:41.5
00:30:57.49 +66:20:59.9
00:18:11.63 +66:47:16.0
########### Completed Cep-03-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:12:06.20 +71:04:34.9
23:34:17.29 +72:51:34.9
23:40:13.45 +70:25:07.8
23:39:23.62 +66:57:49.1
00:33:49.24 +70:43:00.5
23:48:19.77 +68:50:10.7
00:29:13.99 +68:43:26.0
00:52:29.40 +72:25:53.7
23:30:28.12 +73:26:19.2
23:27:13.15 +70:39:46.2
00:42:07.12 +66:33:55.7
00:49:50.18 +70:45:20.0
00:03:31.47 +71:52:30.3
23:40:45.58 +70:22:21.7
23:40:21.22 +70:26:28.5
23:16:40.82 +66:55:22.7
23:18:14.04 +68:07:16.9
23:09:12.44 +73:13:18.2
00:19:26.19 +69:46:58.7
00:24:21.99 +71:46:06.3
23:49:27.02 +68:32:57.8
23:20:10.44 +73:52:30.6
00:19:51.70 +69:24:12.1
00:01:05.75 +73:33:46.4
00:36:22.59 +72:50:41.1
23:27:02.44 +65:39:09.9
23:36:37.05 +67:50:25.4
00:43:31.57 +71:35:03.9
23:27:20.51 +70:16:53.6
23:37:14.99 +68:45:05.4
23:16:02.46 +72:16:17.5
23:55:21.32 +72:45:19.3
23:33:44.18 +68:01:59.1
23:39:21.85 +70:45:33.2
00:21:10.65 +71:25:58.9
23:22:34.52 +71:47:18.5
00:43:48.14 +68:03:41.7
23:28:57.39 +72:12:38.4
23:38:57.92 +73:58:21.1
00:24:17.37 +73:48:35.4
23:56:57.17 +72:46:45.0
00:04:56.74 +73:01:03.5
00:05:44.29 +70:04:15.3
23:51:45.65 +72:42:20.4
23:12:40.53 +67:24:26.9
23:28:16.84 +72:47:41.8
00:33:18.03 +72:41:39.2
23:17:37.33 +71:01:12.1
23:38:17.38 +70:35:09.3
00:01:42.83 +67:24:15.5
00:18:16.60 +73:01:26.3
00:24:45.16 +71:46:25.6
23:51:42.21 +72:42:02.1
23:24:39.53 +69:56:59.3
00:21:21.70 +73:10:03.5
23:34:47.21 +72:38:19.4
23:45:59.56 +72:21:44.8
23:31:00.45 +69:03:49.5
23:17:21.27 +66:30:42.9
23:59:34.61 +66:56:30.7
00:57:13.72 +72:43:54.8
23:28:23.00 +72:48:08.0
23:52:54.03 +66:26:38.3
00:06:09.62 +73:52:27.6
00:26:55.04 +68:56:07.3
00:09:37.77 +67:18:49.7
23:11:57.01 +71:04:36.2
00:28:00.13 +68:15:13.4
00:03:54.91 +67:08:10.8
00:40:06.11 +66:56:02.5
00:18:10.84 +67:57:22.0
23:55:45.88 +66:53:05.2
23:58:47.62 +68:23:45.1
00:02:52.09 +68:31:16.8
23:13:08.22 +69:03:28.2
23:39:28.34 +66:08:37.2
23:47:22.74 +66:40:48.5
23:04:23.95 +73:34:47.8
00:18:36.18 +73:54:58.7
00:22:13.54 +67:48:43.6
23:47:39.45 +67:18:32.2
23:46:54.28 +67:33:51.3
23:29:04.86 +70:33:49.8
23:08:21.02 +71:05:57.1
00:41:17.73 +69:09:23.8
00:05:08.48 +73:52:07.6
23:35:54.73 +69:06:29.6
23:26:52.84 +73:20:04.0
00:18:19.77 +73:46:24.1
23:23:13.55 +70:54:30.8
23:49:13.12 +66:25:43.1
23:55:18.60 +69:28:36.0
00:04:44.78 +70:08:19.7
00:16:14.36 +68:25:12.4
00:34:27.31 +66:39:33.7
23:20:26.67 +70:51:31.5
00:41:09.21 +67:22:38.7
23:58:03.26 +68:23:14.5
23:53:21.67 +67:51:45.3
00:48:47.80 +69:04:47.6
23:20:14.68 +68:05:51.9
00:14:20.74 +66:22:58.1
00:43:57.77 +68:38:26.9
00:29:09.35 +69:46:48.9
23:37:01.19 +68:43:53.2
00:39:31.51 +68:37:42.2
00:39:19.63 +69:20:34.4
00:03:02.04 +67:14:10.6
00:09:47.48 +67:04:04.9
00:30:13.22 +67:40:00.7
00:29:48.56 +69:19:54.4
23:46:30.01 +71:46:07.7
00:18:11.63 +66:47:16.0
23:44:28.54 +70:44:43.0
00:22:40.46 +70:54:28.0
00:24:45.20 +67:11:24.7
00:15:04.16 +69:41:32.9
00:44:59.68 +68:02:44.6
00:39:22.33 +67:01:50.5
00:46:04.89 +72:43:44.4
00:32:14.67 +68:57:54.2
00:36:10.77 +65:54:14.9
00:18:12.64 +66:24:41.5
00:27:56.55 +67:37:15.3
00:40:25.84 +65:36:38.1
00:44:11.17 +69:33:32.1
00:09:22.70 +72:24:46.3
23:34:02.09 +69:11:47.7
00:24:28.40 +69:41:34.5
00:37:24.68 +69:50:52.7
00:30:57.49 +66:20:59.9
###################################################################################
23:12:06.20 +71:04:34.9 -- not an asteroid (will add it to exclusion list)
23:34:17.29 +72:51:34.9 -- not an asteroid (will add it to exclusion list)
23:40:13.45 +70:25:07.8 -- not an asteroid (will add it to exclusion list)
23:39:23.62 +66:57:49.1 -- not an asteroid (will add it to exclusion list)
00:33:49.24 +70:43:00.5 -- not an asteroid (will add it to exclusion list)
23:48:19.77 +68:50:10.7 -- not an asteroid (will add it to exclusion list)
00:29:13.99 +68:43:26.0 -- not an asteroid (will add it to exclusion list)
00:52:29.40 +72:25:53.7 -- not an asteroid (will add it to exclusion list)
23:30:28.12 +73:26:19.2 -- not an asteroid (will add it to exclusion list)
23:27:13.15 +70:39:46.2 -- not an asteroid (will add it to exclusion list)
00:42:07.12 +66:33:55.7 -- not an asteroid (will add it to exclusion list)
00:49:50.18 +70:45:20.0 -- not an asteroid (will add it to exclusion list)
00:03:31.47 +71:52:30.3 -- not an asteroid (will add it to exclusion list)
23:40:45.58 +70:22:21.7 -- not an asteroid (will add it to exclusion list)
23:40:21.22 +70:26:28.5 -- not an asteroid (will add it to exclusion list)
23:16:40.82 +66:55:22.7 -- not an asteroid (will add it to exclusion list)
23:18:14.04 +68:07:16.9 -- not an asteroid (will add it to exclusion list)
23:09:12.44 +73:13:18.2 -- not an asteroid (will add it to exclusion list)
00:19:26.19 +69:46:58.7 -- not an asteroid (will add it to exclusion list)
00:24:21.99 +71:46:06.3 -- not an asteroid (will add it to exclusion list)
23:49:27.02 +68:32:57.8 -- not an asteroid (will add it to exclusion list)
23:20:10.44 +73:52:30.6 -- not an asteroid (will add it to exclusion list)
00:19:51.70 +69:24:12.1 -- not an asteroid (will add it to exclusion list)
00:01:05.75 +73:33:46.4 -- not an asteroid (will add it to exclusion list)
00:36:22.59 +72:50:41.1 -- not an asteroid (will add it to exclusion list)
23:27:02.44 +65:39:09.9 -- not an asteroid (will add it to exclusion list)
23:36:37.05 +67:50:25.4 -- not an asteroid (will add it to exclusion list)
00:43:31.57 +71:35:03.9 -- not an asteroid (will add it to exclusion list)
23:27:20.51 +70:16:53.6 -- not an asteroid (will add it to exclusion list)
23:37:14.99 +68:45:05.4 -- not an asteroid (will add it to exclusion list)
23:16:02.46 +72:16:17.5 -- not an asteroid (will add it to exclusion list)
23:55:21.32 +72:45:19.3 -- not an asteroid (will add it to exclusion list)
23:33:44.18 +68:01:59.1 -- not an asteroid (will add it to exclusion list)
23:39:21.85 +70:45:33.2 -- not an asteroid (will add it to exclusion list)
00:21:10.65 +71:25:58.9 -- not an asteroid (will add it to exclusion list)
23:22:34.52 +71:47:18.5 -- not an asteroid (will add it to exclusion list)
00:43:48.14 +68:03:41.7 -- not an asteroid (will add it to exclusion list)
23:28:57.39 +72:12:38.4 -- not an asteroid (will add it to exclusion list)
23:38:57.92 +73:58:21.1 -- not an asteroid (will add it to exclusion list)
00:24:17.37 +73:48:35.4 -- not an asteroid (will add it to exclusion list)
23:56:57.17 +72:46:45.0 -- not an asteroid (will add it to exclusion list)
00:04:56.74 +73:01:03.5 -- not an asteroid (will add it to exclusion list)
00:05:44.29 +70:04:15.3 -- not an asteroid (will add it to exclusion list)
23:51:45.65 +72:42:20.4 -- not an asteroid (will add it to exclusion list)
23:12:40.53 +67:24:26.9 -- not an asteroid (will add it to exclusion list)
23:28:16.84 +72:47:41.8 -- not an asteroid (will add it to exclusion list)
00:33:18.03 +72:41:39.2 -- not an asteroid (will add it to exclusion list)
23:17:37.33 +71:01:12.1 -- not an asteroid (will add it to exclusion list)
23:38:17.38 +70:35:09.3 -- not an asteroid (will add it to exclusion list)
00:01:42.83 +67:24:15.5 -- not an asteroid (will add it to exclusion list)
00:18:16.60 +73:01:26.3 -- not an asteroid (will add it to exclusion list)
00:24:45.16 +71:46:25.6 -- not an asteroid (will add it to exclusion list)
23:51:42.21 +72:42:02.1 -- not an asteroid (will add it to exclusion list)
23:24:39.53 +69:56:59.3 -- not an asteroid (will add it to exclusion list)
00:21:21.70 +73:10:03.5 -- not an asteroid (will add it to exclusion list)
23:34:47.21 +72:38:19.4 -- not an asteroid (will add it to exclusion list)
23:45:59.56 +72:21:44.8 -- not an asteroid (will add it to exclusion list)
23:31:00.45 +69:03:49.5 -- not an asteroid (will add it to exclusion list)
23:17:21.27 +66:30:42.9 -- not an asteroid (will add it to exclusion list)
23:59:34.61 +66:56:30.7 -- not an asteroid (will add it to exclusion list)
00:57:13.72 +72:43:54.8 -- not an asteroid (will add it to exclusion list)
23:28:23.00 +72:48:08.0 -- not an asteroid (will add it to exclusion list)
23:52:54.03 +66:26:38.3 -- not an asteroid (will add it to exclusion list)
00:06:09.62 +73:52:27.6 -- not an asteroid (will add it to exclusion list)
00:26:55.04 +68:56:07.3 -- not an asteroid (will add it to exclusion list)
00:09:37.77 +67:18:49.7 -- not an asteroid (will add it to exclusion list)
23:11:57.01 +71:04:36.2 -- not an asteroid (will add it to exclusion list)
00:28:00.13 +68:15:13.4 -- not an asteroid (will add it to exclusion list)
00:03:54.91 +67:08:10.8 -- not an asteroid (will add it to exclusion list)
00:40:06.11 +66:56:02.5 -- not an asteroid (will add it to exclusion list)
00:18:10.84 +67:57:22.0 -- not an asteroid (will add it to exclusion list)
23:55:45.88 +66:53:05.2 -- not an asteroid (will add it to exclusion list)
23:58:47.62 +68:23:45.1 -- not an asteroid (will add it to exclusion list)
00:02:52.09 +68:31:16.8 -- not an asteroid (will add it to exclusion list)
23:13:08.22 +69:03:28.2 -- not an asteroid (will add it to exclusion list)
23:39:28.34 +66:08:37.2 -- not an asteroid (will add it to exclusion list)
23:47:22.74 +66:40:48.5 -- not an asteroid (will add it to exclusion list)
23:04:23.95 +73:34:47.8 -- not an asteroid (will add it to exclusion list)
00:18:36.18 +73:54:58.7 -- not an asteroid (will add it to exclusion list)
00:22:13.54 +67:48:43.6 -- not an asteroid (will add it to exclusion list)
23:47:39.45 +67:18:32.2 -- not an asteroid (will add it to exclusion list)
23:46:54.28 +67:33:51.3 -- not an asteroid (will add it to exclusion list)
23:29:04.86 +70:33:49.8 -- not an asteroid (will add it to exclusion list)
23:08:21.02 +71:05:57.1 -- not an asteroid (will add it to exclusion list)
00:41:17.73 +69:09:23.8 -- not an asteroid (will add it to exclusion list)
00:05:08.48 +73:52:07.6 -- not an asteroid (will add it to exclusion list)
23:35:54.73 +69:06:29.6 -- not an asteroid (will add it to exclusion list)
23:26:52.84 +73:20:04.0 -- not an asteroid (will add it to exclusion list)
00:18:19.77 +73:46:24.1 -- not an asteroid (will add it to exclusion list)
23:23:13.55 +70:54:30.8 -- not an asteroid (will add it to exclusion list)
23:49:13.12 +66:25:43.1 -- not an asteroid (will add it to exclusion list)
23:55:18.60 +69:28:36.0 -- not an asteroid (will add it to exclusion list)
00:04:44.78 +70:08:19.7 -- not an asteroid (will add it to exclusion list)
00:16:14.36 +68:25:12.4 -- not an asteroid (will add it to exclusion list)
00:34:27.31 +66:39:33.7 -- not an asteroid (will add it to exclusion list)
23:20:26.67 +70:51:31.5 -- not an asteroid (will add it to exclusion list)
00:41:09.21 +67:22:38.7 -- not an asteroid (will add it to exclusion list)
23:58:03.26 +68:23:14.5 -- not an asteroid (will add it to exclusion list)
23:53:21.67 +67:51:45.3 -- not an asteroid (will add it to exclusion list)
00:48:47.80 +69:04:47.6 -- not an asteroid (will add it to exclusion list)
23:20:14.68 +68:05:51.9 -- not an asteroid (will add it to exclusion list)
00:14:20.74 +66:22:58.1 -- not an asteroid (will add it to exclusion list)
00:43:57.77 +68:38:26.9 -- not an asteroid (will add it to exclusion list)
00:29:09.35 +69:46:48.9 -- not an asteroid (will add it to exclusion list)
23:37:01.19 +68:43:53.2 -- not an asteroid (will add it to exclusion list)
00:39:31.51 +68:37:42.2 -- not an asteroid (will add it to exclusion list)
00:39:19.63 +69:20:34.4 -- not an asteroid (will add it to exclusion list)
00:03:02.04 +67:14:10.6 -- not an asteroid (will add it to exclusion list)
00:09:47.48 +67:04:04.9 -- not an asteroid (will add it to exclusion list)
00:30:13.22 +67:40:00.7 -- not an asteroid (will add it to exclusion list)
00:29:48.56 +69:19:54.4 -- not an asteroid (will add it to exclusion list)
23:46:30.01 +71:46:07.7 -- not an asteroid (will add it to exclusion list)
00:18:11.63 +66:47:16.0 -- not an asteroid (will add it to exclusion list)
23:44:28.54 +70:44:43.0 -- not an asteroid (will add it to exclusion list)
00:22:40.46 +70:54:28.0 -- not an asteroid (will add it to exclusion list)
00:24:45.20 +67:11:24.7 -- not an asteroid (will add it to exclusion list)
00:15:04.16 +69:41:32.9 -- not an asteroid (will add it to exclusion list)
00:44:59.68 +68:02:44.6 -- not an asteroid (will add it to exclusion list)
00:39:22.33 +67:01:50.5 -- not an asteroid (will add it to exclusion list)
00:46:04.89 +72:43:44.4 -- not an asteroid (will add it to exclusion list)
00:32:14.67 +68:57:54.2 -- not an asteroid (will add it to exclusion list)
00:36:10.77 +65:54:14.9 -- not an asteroid (will add it to exclusion list)
00:18:12.64 +66:24:41.5 -- not an asteroid (will add it to exclusion list)
00:27:56.55 +67:37:15.3 -- not an asteroid (will add it to exclusion list)
00:40:25.84 +65:36:38.1 -- not an asteroid (will add it to exclusion list)
00:44:11.17 +69:33:32.1 -- not an asteroid (will add it to exclusion list)
00:09:22.70 +72:24:46.3 -- not an asteroid (will add it to exclusion list)
23:34:02.09 +69:11:47.7 -- not an asteroid (will add it to exclusion list)
00:24:28.40 +69:41:34.5 -- not an asteroid (will add it to exclusion list)
00:37:24.68 +69:50:52.7 -- not an asteroid (will add it to exclusion list)
00:30:57.49 +66:20:59.9 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:01:05.75 +73:33:46.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:42.83 +67:24:15.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:52.09 +68:31:16.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:02.04 +67:14:10.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:31.47 +71:52:30.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:54.91 +67:08:10.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:44.78 +70:08:19.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:56.74 +73:01:03.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:08.48 +73:52:07.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:44.29 +70:04:15.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:09.62 +73:52:27.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:22.70 +72:24:46.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:37.77 +67:18:49.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:47.48 +67:04:04.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:20.74 +66:22:58.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:04.16 +69:41:32.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:14.36 +68:25:12.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:10.84 +67:57:22.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:11.63 +66:47:16.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:12.64 +66:24:41.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:16.60 +73:01:26.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:19.77 +73:46:24.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:36.18 +73:54:58.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:26.19 +69:46:58.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:51.70 +69:24:12.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:10.65 +71:25:58.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:21.70 +73:10:03.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:13.54 +67:48:43.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:40.46 +70:54:28.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:17.37 +73:48:35.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:21.99 +71:46:06.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:28.40 +69:41:34.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:45.16 +71:46:25.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:45.20 +67:11:24.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:55.04 +68:56:07.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:56.55 +67:37:15.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:00.13 +68:15:13.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:09.35 +69:46:48.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:13.99 +68:43:26.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:48.56 +69:19:54.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:13.22 +67:40:00.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:57.49 +66:20:59.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:14.67 +68:57:54.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:33:18.03 +72:41:39.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:33:49.24 +70:43:00.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:27.31 +66:39:33.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:10.77 +65:54:14.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:22.59 +72:50:41.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:24.68 +69:50:52.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:19.63 +69:20:34.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:22.33 +67:01:50.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:31.51 +68:37:42.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:40:06.11 +66:56:02.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:40:25.84 +65:36:38.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:41:09.21 +67:22:38.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:41:17.73 +69:09:23.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:42:07.12 +66:33:55.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:43:31.57 +71:35:03.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:43:48.14 +68:03:41.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:43:57.77 +68:38:26.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:44:11.17 +69:33:32.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:44:59.68 +68:02:44.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:46:04.89 +72:43:44.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:48:47.80 +69:04:47.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:49:50.18 +70:45:20.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:52:29.40 +72:25:53.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:57:13.72 +72:43:54.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:04:23.95 +73:34:47.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:08:21.02 +71:05:57.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:09:12.44 +73:13:18.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:11:57.01 +71:04:36.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:12:06.20 +71:04:34.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:12:40.53 +67:24:26.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:08.22 +69:03:28.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:02.46 +72:16:17.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:40.82 +66:55:22.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:21.27 +66:30:42.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:37.33 +71:01:12.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:14.04 +68:07:16.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:10.44 +73:52:30.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:14.68 +68:05:51.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:26.67 +70:51:31.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:34.52 +71:47:18.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:13.55 +70:54:30.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:39.53 +69:56:59.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:52.84 +73:20:04.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:02.44 +65:39:09.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:13.15 +70:39:46.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:20.51 +70:16:53.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:16.84 +72:47:41.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:23.00 +72:48:08.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:57.39 +72:12:38.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:04.86 +70:33:49.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:28.12 +73:26:19.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:00.45 +69:03:49.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:44.18 +68:01:59.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:02.09 +69:11:47.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:17.29 +72:51:34.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:47.21 +72:38:19.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:54.73 +69:06:29.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:37.05 +67:50:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:01.19 +68:43:53.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:14.99 +68:45:05.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:17.38 +70:35:09.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:57.92 +73:58:21.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:21.85 +70:45:33.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:23.62 +66:57:49.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:28.34 +66:08:37.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:13.45 +70:25:07.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:21.22 +70:26:28.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:45.58 +70:22:21.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:28.54 +70:44:43.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:59.56 +72:21:44.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:30.01 +71:46:07.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:54.28 +67:33:51.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:22.74 +66:40:48.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:39.45 +67:18:32.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:19.77 +68:50:10.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:13.12 +66:25:43.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:27.02 +68:32:57.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:42.21 +72:42:02.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:45.65 +72:42:20.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:54.03 +66:26:38.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:21.67 +67:51:45.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:18.60 +69:28:36.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:21.32 +72:45:19.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:45.88 +66:53:05.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:57.17 +72:46:45.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:03.26 +68:23:14.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:47.62 +68:23:45.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:34.61 +66:56:30.7 -- 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:01:05.75 +73:33:46.4 -- not a known variable star
00:01:42.83 +67:24:15.5 -- not a known variable star
00:02:52.09 +68:31:16.8 -- not a known variable star
00:03:02.04 +67:14:10.6 -- not a known variable star
00:03:31.47 +71:52:30.3 -- not a known variable star
00:03:54.91 +67:08:10.8 -- not a known variable star
00:04:44.78 +70:08:19.7 -- not a known variable star
00:04:56.74 +73:01:03.5 -- not a known variable star
00:05:08.48 +73:52:07.6 -- not a known variable star
00:05:44.29 +70:04:15.3 -- not a known variable star
00:06:09.62 +73:52:27.6 -- not a known variable star
00:09:22.70 +72:24:46.3 -- not a known variable star
00:09:37.77 +67:18:49.7 -- not a known variable star
00:09:47.48 +67:04:04.9 -- not a known variable star
00:14:20.74 +66:22:58.1 -- not a known variable star
00:15:04.16 +69:41:32.9 -- not a known variable star
00:16:14.36 +68:25:12.4 -- not a known variable star
00:18:10.84 +67:57:22.0 -- not a known variable star
00:18:11.63 +66:47:16.0 -- not a known variable star
00:18:12.64 +66:24:41.5 -- not a known variable star
00:18:16.60 +73:01:26.3 -- not a known variable star
00:18:19.77 +73:46:24.1 -- not a known variable star
00:18:36.18 +73:54:58.7 -- not a known variable star
00:19:26.19 +69:46:58.7 -- not a known variable star
00:19:51.70 +69:24:12.1 -- not a known variable star
00:21:10.65 +71:25:58.9 -- not a known variable star
00:21:21.70 +73:10:03.5 -- not a known variable star
00:22:13.54 +67:48:43.6 -- not a known variable star
00:22:40.46 +70:54:28.0 -- not a known variable star
00:24:17.37 +73:48:35.4 -- not a known variable star
00:24:21.99 +71:46:06.3 -- not a known variable star
00:24:28.40 +69:41:34.5 -- not a known variable star
00:24:45.16 +71:46:25.6 -- not a known variable star
00:24:45.20 +67:11:24.7 -- not a known variable star
00:26:55.04 +68:56:07.3 -- not a known variable star
00:27:56.55 +67:37:15.3 -- not a known variable star
00:28:00.13 +68:15:13.4 -- not a known variable star
00:29:09.35 +69:46:48.9 -- not a known variable star
00:29:13.99 +68:43:26.0 -- not a known variable star
00:29:48.56 +69:19:54.4 -- not a known variable star
00:30:13.22 +67:40:00.7 -- not a known variable star
00:30:57.49 +66:20:59.9 -- a known variable star
00:32:14.67 +68:57:54.2 -- not a known variable star
00:33:18.03 +72:41:39.2 -- not a known variable star
00:33:49.24 +70:43:00.5 -- not a known variable star
00:34:27.31 +66:39:33.7 -- not a known variable star
00:36:10.77 +65:54:14.9 -- not a known variable star
00:36:22.59 +72:50:41.1 -- not a known variable star
00:37:24.68 +69:50:52.7 -- not a known variable star
00:39:19.63 +69:20:34.4 -- not a known variable star
00:39:22.33 +67:01:50.5 -- not a known variable star
00:39:31.51 +68:37:42.2 -- not a known variable star
00:40:06.11 +66:56:02.5 -- not a known variable star
00:40:25.84 +65:36:38.1 -- not a known variable star
00:41:09.21 +67:22:38.7 -- not a known variable star
00:41:17.73 +69:09:23.8 -- not a known variable star
00:42:07.12 +66:33:55.7 -- not a known variable star
00:43:31.57 +71:35:03.9 -- not a known variable star
00:43:48.14 +68:03:41.7 -- not a known variable star
00:43:57.77 +68:38:26.9 -- not a known variable star
00:44:11.17 +69:33:32.1 -- not a known variable star
00:44:59.68 +68:02:44.6 -- not a known variable star
00:46:04.89 +72:43:44.4 -- not a known variable star
00:48:47.80 +69:04:47.6 -- not a known variable star
00:49:50.18 +70:45:20.0 -- a known variable star
00:52:29.40 +72:25:53.7 -- not a known variable star
00:57:13.72 +72:43:54.8 -- not a known variable star
23:04:23.95 +73:34:47.8 -- not a known variable star
23:08:21.02 +71:05:57.1 -- not a known variable star
23:09:12.44 +73:13:18.2 -- not a known variable star
23:11:57.01 +71:04:36.2 -- not a known variable star
23:12:06.20 +71:04:34.9 -- not a known variable star
23:12:40.53 +67:24:26.9 -- not a known variable star
23:13:08.22 +69:03:28.2 -- not a known variable star
23:16:02.46 +72:16:17.5 -- not a known variable star
23:16:40.82 +66:55:22.7 -- not a known variable star
23:17:21.27 +66:30:42.9 -- a known variable star
23:17:37.33 +71:01:12.1 -- not a known variable star
23:18:14.04 +68:07:16.9 -- a known variable star
23:20:10.44 +73:52:30.6 -- not a known variable star
23:20:14.68 +68:05:51.9 -- a known variable star
23:20:26.67 +70:51:31.5 -- not a known variable star
23:22:34.52 +71:47:18.5 -- not a known variable star
23:23:13.55 +70:54:30.8 -- not a known variable star
23:24:39.53 +69:56:59.3 -- not a known variable star
23:26:52.84 +73:20:04.0 -- not a known variable star
23:27:02.44 +65:39:09.9 -- not a known variable star
23:27:13.15 +70:39:46.2 -- not a known variable star
23:27:20.51 +70:16:53.6 -- not a known variable star
23:28:16.84 +72:47:41.8 -- not a known variable star
23:28:23.00 +72:48:08.0 -- not a known variable star
23:28:57.39 +72:12:38.4 -- a known variable star
23:29:04.86 +70:33:49.8 -- not a known variable star
23:30:28.12 +73:26:19.2 -- not a known variable star
23:31:00.45 +69:03:49.5 -- not a known variable star
23:33:44.18 +68:01:59.1 -- not a known variable star
23:34:02.09 +69:11:47.7 -- a known variable star
23:34:17.29 +72:51:34.9 -- not a known variable star
23:34:47.21 +72:38:19.4 -- not a known variable star
23:35:54.73 +69:06:29.6 -- not a known variable star
23:36:37.05 +67:50:25.4 -- not a known variable star
23:37:01.19 +68:43:53.2 -- a known variable star
23:37:14.99 +68:45:05.4 -- not a known variable star
23:38:17.38 +70:35:09.3 -- not a known variable star
23:38:57.92 +73:58:21.1 -- not a known variable star
23:39:21.85 +70:45:33.2 -- not a known variable star
23:39:23.62 +66:57:49.1 -- not a known variable star
23:39:28.34 +66:08:37.2 -- not a known variable star
23:40:13.45 +70:25:07.8 -- not a known variable star
23:40:21.22 +70:26:28.5 -- a known variable star
23:40:45.58 +70:22:21.7 -- not a known variable star
23:44:28.54 +70:44:43.0 -- not a known variable star
23:45:59.56 +72:21:44.8 -- not a known variable star
23:46:30.01 +71:46:07.7 -- not a known variable star
23:46:54.28 +67:33:51.3 -- not a known variable star
23:47:22.74 +66:40:48.5 -- not a known variable star
23:47:39.45 +67:18:32.2 -- not a known variable star
23:48:19.77 +68:50:10.7 -- not a known variable star
23:49:13.12 +66:25:43.1 -- not a known variable star
23:49:27.02 +68:32:57.8 -- not a known variable star
23:51:42.21 +72:42:02.1 -- not a known variable star
23:51:45.65 +72:42:20.4 -- not a known variable star
23:52:54.03 +66:26:38.3 -- not a known variable star
23:53:21.67 +67:51:45.3 -- not a known variable star
23:55:18.60 +69:28:36.0 -- not a known variable star
23:55:21.32 +72:45:19.3 -- not a known variable star
23:55:45.88 +66:53:05.2 -- not a known variable star
23:56:57.17 +72:46:45.0 -- not a known variable star
23:58:03.26 +68:23:14.5 -- not a known variable star
23:58:47.62 +68:23:45.1 -- not a known variable star
23:59:34.61 +66:56:30.7 -- not a known variable star
Found 122 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
131 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 131 (excluding asteroids and hot pixels, 122 new), not updating the exclusion list!
###################################################################################
Not allowed to update the exclusion list IS_THIS_TEST_RUN=NO ALLOW_EXCLUSION_LIST_UPDATE= NO
The observatory MPC code is V36
############################################################
Positions of planets computed with util/planet_finder/main.py for JD(UT)2461149.84844492 -observatory V36
00:25:31.44 -00:06:19.9 Mercury (-0.1mag)
03:25:07.66 +19:04:04.8 Venus (-3.9mag)
00:27:20.86 +01:54:30.2 Mars (1.2mag)
07:14:12.65 +22:43:35.5 Jupiter (-2.1mag)
00:30:39.93 +00:58:12.1 Saturn (0.9mag)
03:48:24.71 +19:49:45.4 Uranus (5.8mag)
00:11:16.43 -00:12:38.8 Neptune (7.8mag)
20:33:53.42 -22:52:47.6 Pluto (14.5mag)
03:23:52.99 +22:55:52.5 Moon (-8.7mag)
-rw-r--r-- 1 apache apache 362 Apr 19 03:29 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461149.84844492:
07:14:06.61 +22:43:49.5 Io (5.8mag)
07:14:11.28 +22:43:41.2 Europa (5.9mag)
07:13:53.95 +22:44:16.7 Ganymede (5.4mag)
07:14:26.11 +22:42:58.6 Callisto (6.6mag)
07:17:23.73 +22:29:42.4 Himalia (15.4mag)
07:14:15.93 +22:43:26.4 Thebe (16.2mag)
07:17:39.21 +23:00:02.2 Elara (17.3mag)
07:13:19.21 +23:21:50.6 Pasiphae (17.4mag)
07:22:27.76 +22:41:55.6 Carme (18.5mag)
00:30:30.79 +00:58:32.8 Titan (8.8mag)
00:30:38.08 +00:58:28.2 Rhea (10.1mag)
00:30:14.95 +00:57:49.3 Iapetus (11.5mag)
00:30:35.30 +00:58:40.0 Hyperion (14.8mag)
00:32:14.11 +01:06:38.2 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 19 03:29 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461149.84844492:
15:51:44.34 -18:32:56.9 JWST
16:39:16.58 +48:10:14.6 Chandra
18:59:52.30 -13:17:29.6 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 19 03:29 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461149.84844492 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:53:14.61 -28:58:49.4 13.9mag P/2010 H2 (Vales)
05:09:11.46 -69:30:24.2 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:33:12.12 +31:27:39.0 17.2mag C/2017 K2 (PANSTARRS)
17:30:02.65 +10:56:26.6 17.6mag C/2021 G2 (ATLAS)
23:11:04.38 +29:21:54.4 17.1mag C/2022 E2 (ATLAS)
04:33:09.80 +26:07:39.2 16.0mag C/2022 N2 (PANSTARRS)
09:04:12.98 +32:01:48.0 16.2mag C/2022 QE78 (ATLAS)
08:31:38.82 +00:11:40.7 17.4mag C/2022 R6 (PANSTARRS)
18:52:52.14 +18:48:36.8 17.6mag C/2023 A3 (Tsuchinshan-ATLAS)
15:39:32.68 -11:28:20.3 17.5mag P/2023 B1 (PANSTARRS)
09:06:10.81 -11:21:20.0 17.7mag C/2023 F3 (ATLAS)
21:57:26.63 +63:06:28.6 17.5mag C/2023 H5 (Lemmon)
19:16:06.49 -03:47:39.6 14.1mag C/2023 R1 (PANSTARRS)
21:23:46.91 +86:22:51.2 17.8mag C/2023 X2 (Lemmon)
06:19:37.21 +63:30:08.0 17.2mag C/2024 A1 (ATLAS)
05:20:19.28 +19:21:49.1 11.3mag C/2024 E1 (Wierzchos)
16:17:03.41 +06:56:12.7 17.4mag C/2024 G6 (ATLAS)
20:21:40.06 +16:11:39.4 14.6mag C/2024 J3 (ATLAS)
03:29:24.26 -21:52:58.5 16.3mag C/2024 T5 (ATLAS)
05:19:35.61 +44:28:29.3 17.7mag C/2025 J1 (Borisov)
13:25:03.18 +47:27:12.4 15.3mag C/2025 L1 (ATLAS)
03:30:39.65 -26:44:44.5 17.9mag C/2025 Q3 (ATLAS)
00:20:39.70 +16:53:00.2 8.1mag C/2025 R3 (PANSTARRS)
12:52:40.85 +03:12:40.5 17.4mag C/2025 Y1 (ATLAS)
03:52:39.50 +02:19:06.2 14.2mag C/2026 A1 (MAPS)
00:08:56.24 +37:48:46.3 14.7mag C/2026 B2 (Sun-Gao)
18:49:26.59 -09:32:15.6 11.6mag 10P/Tempel
14:55:43.75 +02:50:33.8 14.3mag 24P/Schaumasse
11:01:57.79 -01:25:20.2 15.7mag 29P/Schwassmann-Wachmann
10:37:33.77 -03:50:42.9 17.0mag 43P/Wolf-Harrington
01:53:52.08 +18:03:16.7 17.3mag 47P/Ashbrook-Jackson
07:17:02.09 +36:17:08.5 17.0mag 63P/Wild
23:33:17.38 -11:03:12.3 15.7mag 65P/Gunn
04:12:17.93 +22:22:52.2 15.9mag 76P/West-Kohoutek-Ikemura
01:13:00.74 +08:52:58.8 14.3mag 78P/Gehrels
23:13:01.86 -08:24:01.3 14.7mag 88P/Howell
02:19:57.82 +21:31:12.0 15.1mag 93P/Lovas
05:01:12.57 +32:27:33.1 16.2mag 123P/West-Hartley
08:32:26.97 +36:49:03.5 16.2mag 124P/Mrkos
02:38:25.05 +14:44:23.1 16.4mag 128P/Shoemaker-Holt
02:54:07.52 +14:53:38.4 17.5mag 131P/Mueller
01:43:55.44 +14:20:53.1 10.5mag 141P/Machholz
01:52:20.29 +06:07:20.5 10.5mag 141P-A/Machholz
00:36:08.34 +01:55:52.9 12.4mag 141P-D/Machholz
02:22:52.57 +07:52:38.2 17.9mag 141P-I/Machholz
01:11:44.97 +00:09:47.8 15.0mag 162P/SidingSpring
14:45:30.50 +00:15:20.7 17.8mag 210P/Christensen
21:48:18.38 -10:38:47.2 17.7mag 218P/LINEAR
17:17:10.61 -13:31:36.4 16.1mag 235P/LINEAR
05:41:46.05 +34:56:11.0 16.8mag 240P/NEAT
07:40:13.04 -04:48:51.7 17.8mag 242P/Spahr
22:25:17.32 -20:04:08.6 17.8mag 260P/McNaught
02:05:05.28 +21:17:54.4 18.0mag 295P/LINEAR
15:41:16.08 +07:12:14.8 17.5mag 391P/Kowalski
07:35:33.26 +21:22:20.8 17.7mag 450P/LONEOS
05:40:48.50 +44:50:12.5 17.5mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.8K Apr 19 03:29 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
14:49:14.13 -27:29:20.60 ASASSN-26cu 2026-04-16.06 14.03
17:21:59.44 -38:54:04.60 ASASSN-26ct 2026-04-14.4 15.15
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
14:49:14.13 -27:29:20.60 2026-04-16.06 14.03
12:23:20.40 +04:53:39.10 AT2026ixd 2026-04-12.14 17.65
17:46:09.76 -61:19:50.40 SN2026icy 2026-04-12.2 17.03
09:25:46.42 +02:13:46.30 SN2026gud 2026-04-11.98 16.49
16:52:15.46 -60:27:45.90 ASASSN-26cs 2026-04-12.4 15.5
04:20:55.37 -51:15:31.10 ASASSN-26cr 2026-04-12.01 15.37
22:25:39.35 +36:45:06.90 AT2026ihl 2026-04-10.48 14.21
19:40:44.94 +00:41:03.80 AT2026imw 2026-04-10.32 16.06
19:52:04.70 +05:53:33.50 ASASSN-26cq 2026-04-9.31 14.98
16:08:18.39 -64:11:08.80 ASASSN-26cp 2026-04-9.29 13.32
09:22:22.90 -61:02:43.70 SN2026idh 2026-04-7.97 16.34
05:06:54.12 -19:42:26.40 AT2026imr 2026-04-8 17.49
07:14:55.34 -36:03:21.40 AT2026hei 2026-04-8.12 16.7
21:35:33.14 -19:01:34.80 AT2026ihm 2026-04-8.36 16.7
04:28:24.08 -32:25:35.30 AT2026imo 2026-04-8.02 16.81
05:10:35.79 -39:38:40.80 SN 2026hnn 2026-04-7.04 17.07
09:54:32.04 -01:17:25.80 ASASSN-26cn 2026-04-7.01 15.58
07:46:24.43 -77:29:36.30 ASASSN-26co 2026-04-7.15 15.11
05:00:45.52 -29:51:06.20 AT2026hvw 2026-04-6.03 16.51
19:49:33.10 -23:37:11.00 ASASSN-26cl 2026-04-5.29 14.98
19:32:43.55 -22:39:33.40 ASASSN-26cm 2026-04-4.3 13.88
18:08:57.38 +76:48:23.60 ASASSN-26ck 2026-04-2.37 15.38
16:16:36.10 +44:52:30.20 AT2026hyy 2026-04-2.58 13.81
21:55:23.31 -34:48:53.90 ASASSN-26cj 2026-03-30.4 -1.47
11:19:50.81 -27:51:50.40 SN2026gvk 2026-03-30 15.28
11:53:57.02 -23:09:46.20 SN2026gzx 2026-03-28.75 15.27
07:13:46.14 -33:10:15.70 ASASSN-26ci 2026-03-28.15 15.14
09:03:36.09 -67:58:13.00 SN2026hkg 2026-03-28.19 15.82
07:03:00.72 +39:14:43.00 SN2026fin 2026-03-28.27 15.82
05:35:42.79 -63:44:05.60 ASASSN-26ch 2026-03-28.12 13.14
11:23:19.04 +34:22:38.00 SN2026fwt 2026-03-27.3 16.56
19:03:49.79 +37:04:05.20 ASASSN-26ce 2026-03-26.56 16.3
20:26:56.07 -52:54:06.50 AT2026hiy 2026-03-26.35 16.95
05:25:54.76 -30:15:35.80 ASASSN-26cg 2026-03-25.07 16.88
06:57:16.49 -26:54:37.20 SN2026fzb 2026-03-25.14 15.8
14:37:38.23 -43:00:52.30 ASASSN-26cd 2026-03-24.24 12.52
17:34:53.03 +06:04:29.70 AT2026gzl 2026-03-23.27 15.82
08:30:02.60 -35:12:47.50 ASASSN-26cf 2026-03-23.2 14.82
16:54:25.33 +37:49:56.60 SN 2026evz 2026-03-21.32 17.54
17:06:19.20 -18:54:19.50 ASASSN-26bx 2026-03-21.25 16.39
19:01:16.28 -29:29:23.10 ASASSN-26bw 2026-03-21.33 15.81
08:46:05.75 +10:47:39.80 ASASSN-26ca 2026-03-21.13 14.27
12:14:58.16 +63:47:16.20 SN 2026fvx 2026-03-21.12 15.6
18:02:55.90 -75:23:02.60 ASASSN-26bz 2026-03-21.32 16.16
12:16:02.87 -53:16:33.70 ASASSN-26cc 2026-03-20.08 3.93
13:08:21.85 +29:13:44.20 SN 2026fmh 2026-03-20.16 -0.33
19:56:38.48 -34:45:21.50 ASASSN-26cb 2026-03-20.35 -3.26
14:32:41.15 -41:38:48.50 ASASSN-26by 2026-03-20.15 -1.31
13:00:42.99 +37:18:34.60 SN2026fjc 2026-03-19.5 15.97
06:02:44.21 -04:11:06.20 ASASSN-26bv 2026-03-19.19 15.67
12:20:27.90 -45:55:38.40 ASASSN-26bt 2026-03-19.05 16.24
07:49:57.30 -56:14:35.10 ASASSN-26bu 2026-03-19.19 15.74
06:04:29.75 +53:23:34.00 SN 2026eza 2026-03-18.2 17.48
11:54:57.87 +69:19:28.90 AT2026fsf 2026-03-18.14 16.95
10:44:46.95 +58:27:29.30 SN 2026enn 2026-03-18.13 17.53
20:45:54.04 -73:26:43.00 AT 2026ezy 2026-03-18.13 16.83
06:53:18.10 -59:10:49.30 ASASSN-26bs 2026-03-18.02 16.93
07:45:09.29 -62:14:36.20 ASASSN-26br 2026-03-16.16 16.78
19:24:27.93 -52:04:36.40 AT 2023uk 2026-03-16.35 14.2
04:52:54.50 -15:20:57.10 AT2026fhw 2026-03-14.06 SDSS
11:10:34.24 +02:58:48.10 SN2026drr 2026-03-14.08 0.2
07:26:45.73 -27:45:13.90 ASASSN-26bo 2026-03-14.17 13.8
16:35:46.94 +58:12:28.40 SN2026ebt 2026-03-12.41 17.12
13:01:19.45 +15:42:15.00 SN2026ehe 2026-03-12.11 -0.29
09:15:55.41 +10:08:09.70 SN2026efq 2026-03-12.16 0.06
03:31:20.92 -35:29:29.00 SN2026evh 2026-03-12.05 17.29
06:26:19.15 -85:18:28.10 AT2026ffp 2026-03-12.16 0.37
14:16:42.30 -41:18:36.50 AT2026fij 2026-03-12.05 15.97
10:45:04.71 +00:06:13.10 SN 2026exe 2026-03-11.78 16.48
18:07:45.58 +69:43:01.00 SN2026ess 2026-03-12.37 17.37
13:11:03.58 +49:06:31.80 AT2026ewa 2026-03-12.42 16.77
15:03:25.23 -63:11:22.20 ASASSN-26bp 2026-03-11.92 13.33
13:09:37.25 -35:50:25.20 AT2024cmo 2026-03-11.12 16.29
13:06:01.97 -15:50:14.40 AT2026fdy 2026-03-10.33 16.68
11:30:09.67 -47:26:43.70 ASASSN-26bn 2026-03-10.12 15.2
05:03:25.25 -24:16:50.40 (= Gaia 2026-03-9.09 14.32
03:42:32.53 -04:17:53.70 ASASSN-26bm 2026-03-8.04 15.22
04:31:00.53 -68:29:50.20 ASASSN-26bl 2026-03-7.9 10.26
16:18:17.61 +41:25:11.40 SN 2026dkf 2026-03-6.31 16.7
13:45:00.35 +61:16:50.90 SN 2026ejl 2026-03-6.41 -0.66
09:27:45.48 -37:49:32.80 ASASSN-26bk 2026-03-2.3 13.11
20:22:01.20 +23:47:47.30 ASASSN-26bi 2026-02-28.51 15.86
11:16:22.10 +29:26:22.80 AT2026enm 2026-02-28.39 16.88
08:05:59.83 -48:39:35.60 ASASSN-26bh 2026-02-26.05 14.64
13:24:27.02 -45:57:01.40 ASASSN-26bg 2026-02-26.35 15.28
17:27:50.95 -68:28:46.40 ASASSN-26bf 2026-02-26.3 16.28
18:03:39.37 +19:58:46.70 ASASSN-26be 2026-02-25.58 14.8
17:40:18.19 +07:20:59.60 SN 2026crm 2026-02-24.34 16.9
18:38:36.11 -79:28:58.40 ASASSN-26bb 2026-02-24.36 16.11
17:43:29.75 +11:24:00.60 ASASSN-26bc 2026-02-23.37 -3.37
16:59:41.08 -80:01:51.20 ASASSN-26bd 2026-02-23.3 14.38
11:23:31.77 -08:39:15.40 SN2026cff 2026-02-23.15 -1.08
14:55:17.39 -05:56:05.30 SN2026dmk 2026-02-23.22 -0.76
12:28:15.19 +44:27:20.80 SN2026cjz 2026-02-23.47 15.62
12:12:29.55 -02:40:43.30 AT2026dsk 2026-02-23.4 17.21
09:21:05.29 +06:11:42.80 SN2026chr 2026-02-23.1 17.39
16:05:38.61 +18:06:07.40 SN 2026dsy 2026-02-23.36 17.15
-rw-r--r-- 1 apache apache 5.8K Apr 19 03:29 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
09:54:46.47 +69:06:31.7 PNV J09544647+6906317 2026-01-26.8081 19.3mag
18:08:51.99 -26:16:21.9 TCP J18085199-2616219 2026-01-31.8519 12.2mag
08:01:11.02 -03:43:14.1 TCP J08011102-0343141 2026-02-08.8090 15.10Cmag
05:19:15.40 -02:04:51.5 TCP J05191540-0204515 2026-02-13.4306 14.5mag
10:52:41.26 +36:40:08.9 TCP J10524126+3640089 2026-02-17.6065 17.4mag
05:50:50.81 +36:22:45.1 TCP J05505081+3622451 2026-02-17.5511 15.7mag
00:42:51.33 +41:13:49.1 PNV J00425133+4113491 2026-02-20.738 18.3mag
00:43:04.88 +41:29:41.4 PNV J00430488+4129414 2026-02-20.5923 18.84Cmag
17:43:29.74 +11:24:00.3 TCP J17432974+1124003 2026-02-22.3773 13.6mag
09:55:01.59 +69:08:42.7 PNV J09550159+6908427 2026-02-20.893 19.0mag
07:03:25.76 -12:41:40.1 TCP J07032576-1241401 2026-03-10.4268 15.4mag
00:42:36.82 +41:16:05.8 PNV J00423682+4116058 2026-03-12.5744 17.24Cmag
07:26:45.79 -27:45:14.1 TCP J07264579-2745141 2026-03-17.4417 14.8mag
17:57:19.56 -28:08:14.7 TCP J17571956-2808147 2026-03-19.7972 14.5mag
08:46:05.73 +10:47:39.7 TCP J08460573+1047397 2026-03-21.1936 14.5mag
09:55:38.83 +69:05:21.7 PNV J09553883+6905217 2026-04-01.893 19.4mag
19:32:43.67 -22:39:30.7 TCP J19324367-2239307 2026-04-05.4395 13.6mag
16:16:36.03 +44:52:28.9 TCP J16163603+4452289 2026-04-05.6655 14.2mag
00:43:38.36 +41:15:32.4 PNV J00433836+4115324 2026-04-08.079 17.2mag
15:41:11.68 +59:18:26.8 TCP J15411168+5918268 2026-04-12.9625 19.2mag
-rw-r--r-- 1 apache apache 188K Apr 19 03:29 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
16:35:21.390 +30:27:47.12 AT 2026jjg 2026-04-07.79 20.91
17:02:03.120 +41:30:38.89 AT 2026jjf 2026-04-03.89 21.38
17:08:30.580 +41:56:13.61 AT 2026jje 2026-04-03.89 21.47
16:48:25.780 +33:00:44.35 AT 2026jjd 2026-04-03.85 21.29
16:46:02.450 +30:55:42.15 AT 2026jjc 2026-04-03.80 19.57
16:51:04.120 +44:26:50.06 AT 2026jjb 2026-03-30.84 21.02
12:10:02.030 +43:26:37.06 AT 2026jja 2026-03-28.87 21.46
17:56:59.910 +48:20:04.31 AT 2026jiz 2026-03-27.87 20.99
15:23:12.550 +15:30:01.81 AT 2026jiy 2026-03-27.82 21.09
12:45:41.400 +53:52:15.13 AT 2026jix 2026-03-24.70 20.56
12:05:28.040 +47:18:05.03 AT 2026jiw 2026-03-24.69 20.17
12:49:49.680 +44:27:28.62 AT 2026jiv 2026-03-24.69 21.87
12:17:57.600 +45:03:04.77 AT 2026jiu 2026-03-24.69 20.4
11:39:16.940 +45:15:03.67 AT 2026jit 2026-03-24.66 21.06
14:17:33.100 +43:22:03.41 AT 2026jis 2026-03-22.80 20.74
14:45:33.130 +38:26:13.04 AT 2026jir 2026-03-22.80 21.14
14:42:55.800 +38:18:34.13 AT 2026jiq 2026-03-22.80 21.14
12:43:36.900 +28:13:26.06 AT 2026jip 2026-03-20.69 21.81
13:50:42.590 +38:45:33.09 AT 2026jio 2026-03-29.93 20.87
19:45:48.257 -49:40:35.86 AT 2026jin 2026-04-12.35 18.142
-rw-r--r-- 1 apache apache 30K Apr 19 03:29 tns_transients_list.txt
