This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr
The list of candidates will appear below. Please manually reload the page every few minutes untill the 'Processing complete' message appears.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 14 18.29 +55 04 58.2 12.9 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 12 36.74 +53 02 56.2 13.0 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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 23.3726* 10 07 11.39 +53 52 25.3 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 08 37.19 +51 34 47.4 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.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 20260423.3726 12.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 23.3726* 10 11 12.71 +52 23 53.4 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 09 40 10.64 +52 18 09.1 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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 23.3726* 10 11 31.00 +57 18 37.6 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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 23.3726* 10 08 57.01 +55 15 41.8 13.1 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,13.14,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 13.14CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 12 07.97 +53 42 00.7 13.1 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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!
TCP 2026 04 23.3726* 10 06 31.99 +56 13 09.4 13.0 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 05 32.05 +56 26 37.6 13.0 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,13.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 13.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 06 40.43 +52 11 55.5 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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!
TCP 2026 04 23.3726* 10 07 11.95 +50 24 03.5 12.9 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 824097949431657344,2461153.8726,12.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 824097949431657344 20260423.3726 12.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 06 14.57 +49 46 54.3 12.9 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 13 19.82 +54 03 53.1 13.0 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 851733800534787968,2461153.8726,13.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 851733800534787968 20260423.3726 13.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 14 16.14 +55 26 49.0 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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!
TCP 2026 04 23.3726* 10 05 49.39 +49 47 34.3 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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 23.3726* 10 09 06.70 +55 54 18.3 12.9 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 06 30.85 +57 17 00.5 12.9 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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!
TCP 2026 04 23.3726* 10 10 09.58 +53 10 35.4 12.9 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J152.5398+53.1752,2461153.8726,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
ATO J152.5398+53.1752 20260423.3726 12.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 09 14.94 +55 12 38.8 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 12 24.81 +50 28 52.8 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 13 59.74 +53 58 38.4 13.1 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 13.11CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 07 12.28 +50 16 37.0 12.4 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.41CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 11 44.04 +54 28 08.9 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.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 20260423.3726 12.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 09 09.27 +53 54 35.3 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.75,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 06 40.89 +50 51 29.4 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.75,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 12 49.00 +56 14 31.9 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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!
TCP 2026 04 23.3726* 10 05 25.08 +56 49 17.7 12.9 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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!
TCP 2026 04 23.3726* 10 09 57.84 +53 03 02.1 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J152.4900+53.0545,2461153.8726,12.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J152.4900+53.0545 20260423.3726 12.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 10 25.38 +54 09 47.4 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 09 28.61 +51 16 58.4 12.3 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 848178083009862656,2461153.8726,12.34,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 848178083009862656 20260423.3726 12.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 23.3726* 10 06 58.29 +54 30 30.4 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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 23.3726* 10 09 19.49 +51 31 21.0 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 13 22.32 +51 28 10.0 13.0 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J153.3410+51.4728,2461153.8726,13.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J153.3410+51.4728 20260423.3726 13.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 09 44 31.69 +50 13 45.5 12.6 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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!
TCP 2026 04 23.3726* 10 12 01.33 +56 09 56.9 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 05 31.71 +52 34 08.2 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.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 20260423.3726 12.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 23.3726* 10 09 27.44 +53 33 36.2 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.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 20260423.3726 12.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 23.3726* 10 15 37.79 +54 45 23.0 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J153.9072+54.7587,2461153.8726,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
ATO J153.9072+54.7587 20260423.3726 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 23.3726* 10 14 05.49 +52 33 11.5 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 12.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 09 56.26 +54 35 19.3 12.9 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.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 20260423.3726 12.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!
TCP 2026 04 23.3726* 10 06 51.19 +50 34 20.6 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 09 10.30 +57 27 56.9 12.8 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 10 01.10 +50 20 36.4 12.5 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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
target 20260423.3726 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!
TCP 2026 04 23.3726* 10 12 19.79 +56 46 26.1 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 1045505682499768704,2461153.8726,12.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1045505682499768704 20260423.3726 12.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 07 04.45 +49 48 32.7 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 07 35.55 +55 25 06.5 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 08 07.33 +55 16 48.8 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 09 08.25 +57 27 19.9 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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 23.3726* 10 12 23.04 +50 13 09.3 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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 23.3726* 10 11 08.52 +55 39 37.0 13.1 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 12 29.48 +53 19 10.4 13.1 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 851633435739119744,2461153.8726,13.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 851633435739119744 20260423.3726 13.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 10 25.93 +52 56 28.6 13.0 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 09 16.99 +50 59 46.2 12.6 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 824152173395202816,2461153.8726,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
Gaia DR3 824152173395202816 20260423.3726 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!
TCP 2026 04 23.3726* 10 10 21.87 +51 06 00.6 12.7 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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 23.3726* 10 10 56.81 +50 07 45.6 12.4 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 12.45CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 05 50.98 +50 22 08.4 12.6 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 12.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 09 16.45 +50 38 06.3 12.5 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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
target 20260423.3726 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!
TCP 2026 04 23.3726* 10 12 35.90 +54 26 01.0 12.9 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 13 03.38 +54 28 35.3 12.6 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,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 20260423.3726 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!
TCP 2026 04 23.3726* 10 07 51.28 +56 26 34.9 13.0 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 1045111198343578240,2461153.8726,13.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1045111198343578240 20260423.3726 13.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 08 32.62 +55 56 57.8 12.5 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 23.3726* 10 13 17.84 +54 18 22.5 12.9 U UMa 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461153.8726,12.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260423.3726 12.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461093.77794983 22.02.2026 06:40:04.865 /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
First image: 2461093.77794983 22.02.2026 06:40:04.865 /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
Last image: 2461153.87289255 23.04.2026 08:56:47.916 /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
JD time system (TT/UTC/UNKNOWN): UTC
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.46
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: 2 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): 5924
Objects passed selection criteria: 5900
Measurements per detected object (mean, median, min, max): 2.5 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.5 2.0 2 4
Average stars detected per image: 3888.25
Average stars matched: 3785.5 (97.3574 %)
Memory usage VmPeak: 112508 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Tue Apr 21 18:08:25 CDT 2026
VaST build number 1.0rc89-27-g1ba0f777
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-21)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Thu Apr 23 04:02:43 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: 2461093.77794983 22.02.2026 06:40:04.865 /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
First image: 2461093.77794983 22.02.2026 06:40:04.865 /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
Last image: 2461153.87289255 23.04.2026 08:56:47.916 /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 135
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.16
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: 11 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): 31412
Objects passed selection criteria: 31293
Measurements per detected object (mean, median, min, max): 2.6 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.6 2.0 2 4
Average stars detected per image: 21772
Average stars matched: 21097 (96.8997 %)
Memory usage VmPeak: 137092 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Tue Apr 21 18:08:25 CDT 2026
VaST build number 1.0rc89-27-g1ba0f777
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-21)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Thu Apr 23 04:03:56 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/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
SExtractor catalog cache: saved UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat to cache
SExtractor catalog cache: saved UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.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/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.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: 2461153.87239231
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_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits exists and is non-empty
Saving wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits to local_wcs_cache/
'wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits' -> 'local_wcs_cache/wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits'
wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits exists and is non-empty
Saving wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits to local_wcs_cache/
'wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits' -> 'local_wcs_cache/wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits'
wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits exists and is non-empty
Saving wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits to local_wcs_cache/
'wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits' -> 'local_wcs_cache/wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits'
wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits exists and is non-empty
Saving wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits to local_wcs_cache/
'wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits' -> 'local_wcs_cache/wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits (1st reference image)
verification OK: wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
Image size: 941.6'x627.1' 15.7(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 09:52:59.725 +53:58:44.63 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_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits (1st new image)
verification OK: wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
Image size: 938.0'x624.2' 15.6(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.88"/pix along the X axis and 5.86"/pix along the Y axis
Image center: 09:53:11.031 +54:00:03.44 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 09:52:59.725 +53:58:44.63
Second-epoch image center 09:53:11.031 +54:00:03.44
Angular distance between the image centers 0.0353 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits (2nd new image)
verification OK: wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
Image size: 938.0'x624.2' 15.6(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.88"/pix along the X axis and 5.86"/pix along the Y axis
Image center: 09:53:10.870 +54:00:12.45 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 09:52:59.725 +53:58:44.63
Second-epoch image center 09:53:10.870 +54:00:12.45
Angular distance between the image centers 0.0366 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 09:53:11.031 +54:00:03.44
Second-epoch second image center 09:53:10.870 +54:00:12.45
Angular distance between the image centers 0.00253 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/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits &> /tmp/tmp.ILGqWanNw1
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits &> /tmp/tmp.0oPhcQdsfP
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits &> /tmp/tmp.P4c6bs4OoU
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits &> /tmp/tmp.NaebEGF9YK
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
Calibrating the magnitude scale
Found non-empty wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.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_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits and wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.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_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits and wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat
Found non-empty wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits and wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat
The reference image (wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits) and catalog (wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat) found
'wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat' -> 'wcsmag.cat'
Read 8427 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 133.8964 to 163.5531 deg, Dec +47.6713 to +59.3564 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 133.8964 to 163.5531 deg, Dec 47.6713 to 59.3564 deg
Loaded 6206 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): 4180 out of 4401 total matches.
Matched with Tycho-2 4401 out of 8427 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.919328
a=0.000000 b=1.000000 c=22.919328
From vast_summary.log: estimated ref. image limiting mag.: -7.46
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.46
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.46
Magnitude calibration plot:
Preparing per-reference-image forced-photometry calibration (method=tycho2 band=V)
Read 8427 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 133.8964 to 163.5531 deg, Dec +47.6713 to +59.3564 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 133.8964 to 163.5531 deg, Dec 47.6713 to 59.3564 deg
Loaded 6206 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): 4180 out of 4401 total matches.
Matched with Tycho-2 4401 out of 8427 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits via Tycho-2
Forced-photometry filter: calibrated wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits -> calib.txt_param_ref_wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits (aperture=6.3)
Read 8505 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 133.8811 to 163.5531 deg, Dec +47.6713 to +59.3308 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 133.8811 to 163.5531 deg, Dec 47.6713 to 59.3308 deg
Loaded 6196 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): 4177 out of 4397 total matches.
Matched with Tycho-2 4397 out of 8505 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits via Tycho-2
Forced-photometry filter: calibrated wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits -> calib.txt_param_ref_wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits (aperture=6.3)
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 0 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.2 pix UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
2.2 pix UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
2.8 pix fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
2.7 pix fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
2.2 pix wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
2.2 pix wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
Limiting magnitude estimates:
15.5 mag. UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
15.5 mag. UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
13.0 mag. fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
12.9 mag. fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
All-image limiting magnitude estimate: 12.9 (SNR ) 10.8 (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.ILGqWanNw1 (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/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits' -> 'wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
WCS_IMAGE_NAME=wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
WCS-calibrated image found: wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
Checking if the catalog wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat corresponding to the image wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits alredy exist and is non-empty...
Catalog wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat corresponding to the image wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
WCS catalog name: wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=549, passed=8427
Got 8427 stars (including 7865 good ones) from the SExtractor catalog wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat
util/solve_plate_with_UCAC5 got 8427 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
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.7 to 59.4)
Done reading UCAC5 zone files...
Matched 977 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 973 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.37"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 8334 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.36"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.7 to 59.4)
Done reading UCAC5 zone files...
Matched 977 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 8335 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.36"
Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 8335 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.35"
Excluding outliers - 977 stars left (next iteration limit 1074)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits -region wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.0oPhcQdsfP (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/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits' -> 'wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
WCS_IMAGE_NAME=wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
WCS-calibrated image found: wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
Checking if the catalog wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat corresponding to the image wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits alredy exist and is non-empty...
Catalog wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat corresponding to the image wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
WCS catalog name: wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=566, passed=8505
Got 8505 stars (including 7931 good ones) from the SExtractor catalog wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat
util/solve_plate_with_UCAC5 got 8505 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
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.7 to 59.3)
Done reading UCAC5 zone files...
Matched 977 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 974 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.37"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 8410 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.36"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.7 to 59.3)
Done reading UCAC5 zone files...
Matched 977 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 8410 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.36"
Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 8410 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.36"
Excluding outliers - 977 stars left (next iteration limit 1074)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits -region wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.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.P4c6bs4OoU (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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
WCS_IMAGE_NAME=wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
WCS-calibrated image found: wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
Checking if the catalog wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat corresponding to the image wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits alredy exist and is non-empty...
Catalog wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat corresponding to the image wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
WCS catalog name: wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=101, passed=1911
Got 1911 stars (including 1806 good ones) from the SExtractor catalog wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat
util/solve_plate_with_UCAC5 got 1911 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 938.0'
Seting catalog search parameters based on the expected field of view 938.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013028 (46.9 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010422 (37.5 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.1 to 59.2)
Done reading UCAC5 zone files...
Matched 970 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 942 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.42"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 1854 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.43"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.1 to 59.2)
Done reading UCAC5 zone files...
Matched 970 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 1854 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.42"
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 1854 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.40"
Excluding outliers - 970 stars left (next iteration limit 1067)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits -region wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.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.NaebEGF9YK (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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
WCS_IMAGE_NAME=wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
WCS-calibrated image found: wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
Checking if the catalog wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat corresponding to the image wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits alredy exist and is non-empty...
Catalog wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat corresponding to the image wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
WCS catalog name: wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=105, passed=1981
Got 1981 stars (including 1875 good ones) from the SExtractor catalog wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat
util/solve_plate_with_UCAC5 got 1981 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 938.0'
Seting catalog search parameters based on the expected field of view 938.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013028 (46.9 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010422 (37.5 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.2 to 59.2)
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(), 940 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.41"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 968 matched stars entering correct_measured_positions(), 1900 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.42"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.2 to 59.2)
Done reading UCAC5 zone files...
Matched 967 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 967 matched stars entering correct_measured_positions(), 1903 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.41"
Accuracy estimation diagnostic: 967 matched stars entering correct_measured_positions(), 1903 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.39"
Excluding outliers - 967 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_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits -region wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.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_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits'
Saving fully-calibrated image wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits'
Preparing the HTML report for the field UMa-06-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
No candidates found here
Prepared the HTML report for the field UMa-06-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
*------ done with default.sex.telephoto_lens_onlybrightstars_v1 ------*
#### The local exclusion list is exclusion_list_local.txt ####
wait
*------ default.sex.telephoto_lens_vSTL ------*
'default.sex.telephoto_lens_vSTL' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_vSTL
./vast --norotation --noflagimage --starmatchraius 4 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
SExtractor catalog cache: saved UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat to cache
SExtractor catalog cache: saved UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
Creating symlink local_wcs_cache/wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
Creating symlink local_wcs_cache/wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
Creating symlink local_wcs_cache/wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.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_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits exists and is non-empty
wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits exists and is non-empty
wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits exists and is non-empty
wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits exists and is non-empty
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits (1st reference image)
verification OK: wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
Image size: 941.6'x627.1' 15.7(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 09:52:59.725 +53:58:44.63 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_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits (1st new image)
verification OK: wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
Image size: 938.0'x624.2' 15.6(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.88"/pix along the X axis and 5.86"/pix along the Y axis
Image center: 09:53:11.031 +54:00:03.44 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 09:52:59.725 +53:58:44.63
Second-epoch image center 09:53:11.031 +54:00:03.44
Angular distance between the image centers 0.0353 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits (2nd new image)
verification OK: wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
Image size: 938.0'x624.2' 15.6(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.88"/pix along the X axis and 5.86"/pix along the Y axis
Image center: 09:53:10.870 +54:00:12.45 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 09:52:59.725 +53:58:44.63
Second-epoch image center 09:53:10.870 +54:00:12.45
Angular distance between the image centers 0.0366 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 09:53:11.031 +54:00:03.44
Second-epoch second image center 09:53:10.870 +54:00:12.45
Angular distance between the image centers 0.00253 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/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits &> /tmp/tmp.0leK6EMF9T
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits &> /tmp/tmp.bsV7OaClUi
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits &> /tmp/tmp.4LuXmb5UOH
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits &> /tmp/tmp.fmWiYDlb2p
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
Calibrating the magnitude scale
Found non-empty wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.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_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits and wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.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_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits and wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat
Found non-empty wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits and wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat
The reference image (wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits) and catalog (wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat) found
'wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat' -> 'wcsmag.cat'
Read 43398 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 133.7317 to 163.6362 deg, Dec +47.6486 to +59.3564 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 133.7317 to 163.6362 deg, Dec 47.6486 to 59.3564 deg
Loaded 6260 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): 3922 out of 4423 total matches.
Matched with Tycho-2 4423 out of 43398 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.805739
a=0.000000 b=1.000000 c=22.805739
From vast_summary.log: estimated ref. image limiting mag.: -7.16
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.65
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.65
Magnitude calibration plot:
Preparing per-reference-image forced-photometry calibration (method=tycho2 band=V)
Read 43398 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 133.7317 to 163.6362 deg, Dec +47.6486 to +59.3564 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 133.7317 to 163.6362 deg, Dec 47.6486 to 59.3564 deg
Loaded 6260 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): 3922 out of 4423 total matches.
Matched with Tycho-2 4423 out of 43398 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits via Tycho-2
Forced-photometry filter: calibrated wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits -> calib.txt_param_ref_wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits (aperture=4.9)
Read 43456 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 133.7322 to 163.6360 deg, Dec +47.6713 to +59.3422 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 133.7322 to 163.6360 deg, Dec 47.6713 to 59.3422 deg
Loaded 6242 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): 3916 out of 4421 total matches.
Matched with Tycho-2 4421 out of 43456 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits via Tycho-2
Forced-photometry filter: calibrated wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits -> calib.txt_param_ref_wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits (aperture=4.9)
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 83 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.1 pix UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
2.1 pix UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
2.4 pix fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
2.3 pix fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
2.1 pix wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
2.1 pix wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
Limiting magnitude estimates:
15.6 mag. UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
15.6 mag. UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
13.4 mag. fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
13.4 mag. fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
All-image limiting magnitude estimate: 13.4 (SNR ) 13.1 (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.0leK6EMF9T (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/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits' -> 'wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
WCS_IMAGE_NAME=wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
WCS-calibrated image found: wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
Checking if the catalog wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat corresponding to the image wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits alredy exist and is non-empty...
Catalog wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat corresponding to the image wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits
WCS catalog name: wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=23, blended=2121, passed=43375
Got 43375 stars (including 41181 good ones) from the SExtractor catalog wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat
util/solve_plate_with_UCAC5 got 43375 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
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.6 to 59.4)
Done reading UCAC5 zone files...
Matched 975 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 975 matched stars entering correct_measured_positions(), 968 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.39"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 975 matched stars entering correct_measured_positions(), 42813 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.37"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.6 to 59.4)
Done reading UCAC5 zone files...
Matched 975 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 975 matched stars entering correct_measured_positions(), 42815 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.37"
Accuracy estimation diagnostic: 975 matched stars entering correct_measured_positions(), 42815 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.37"
Excluding outliers - 975 stars left (next iteration limit 1072)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits -region wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-04_20.00sec_-14.90C_LIGHT_0286.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.bsV7OaClUi (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/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits' -> 'wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
WCS_IMAGE_NAME=wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
WCS-calibrated image found: wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
Checking if the catalog wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat corresponding to the image wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits alredy exist and is non-empty...
Catalog wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat corresponding to the image wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits
WCS catalog name: wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=26, blended=2172, passed=43430
Got 43430 stars (including 41175 good ones) from the SExtractor catalog wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat
util/solve_plate_with_UCAC5 got 43430 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
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.7 to 59.3)
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(), 971 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.38"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 42978 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.39"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.7 to 59.3)
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(), 42978 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.39"
Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 42978 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.37"
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_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits -region wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_UMa-06-Q2b1x1_2026-02-22_00-40-50_20.00sec_-15.00C_LIGHT_0287.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.4LuXmb5UOH (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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
WCS_IMAGE_NAME=wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
WCS-calibrated image found: wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
Checking if the catalog wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat corresponding to the image wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits alredy exist and is non-empty...
Catalog wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat corresponding to the image wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
WCS catalog name: wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=2, blended=285, passed=11708
Got 11708 stars (including 11398 good ones) from the SExtractor catalog wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat
util/solve_plate_with_UCAC5 got 11708 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 938.0'
Seting catalog search parameters based on the expected field of view 938.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013028 (46.9 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010422 (37.5 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.1 to 59.3)
Done reading UCAC5 zone files...
Matched 967 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 967 matched stars entering correct_measured_positions(), 944 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.43"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 967 matched stars entering correct_measured_positions(), 11300 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.44"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.1 to 59.3)
Done reading UCAC5 zone files...
Matched 967 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 967 matched stars entering correct_measured_positions(), 11300 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.43"
Accuracy estimation diagnostic: 967 matched stars entering correct_measured_positions(), 11299 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.40"
Excluding outliers - 967 stars left (next iteration limit 1063)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits -region wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.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.fmWiYDlb2p (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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
WCS_IMAGE_NAME=wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
WCS-calibrated image found: wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
Checking if the catalog wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat corresponding to the image wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits alredy exist and is non-empty...
Catalog wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat corresponding to the image wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
WCS catalog name: wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=6, blended=292, passed=12203
Got 12203 stars (including 11887 good ones) from the SExtractor catalog wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat
util/solve_plate_with_UCAC5 got 12203 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 938.0'
Seting catalog search parameters based on the expected field of view 938.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013028 (46.9 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010422 (37.5 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.1 to 59.3)
Done reading UCAC5 zone files...
Matched 962 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 962 matched stars entering correct_measured_positions(), 937 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.42"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 962 matched stars entering correct_measured_positions(), 11681 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.43"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.1 to 59.3)
Done reading UCAC5 zone files...
Matched 962 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 962 matched stars entering correct_measured_positions(), 11680 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.43"
Accuracy estimation diagnostic: 962 matched stars entering correct_measured_positions(), 11680 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.40"
Excluding outliers - 962 stars left (next iteration limit 1058)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits -region wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.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_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-04_20.00sec_-5.00C_LIGHT_0234.fits
Saving fully-calibrated image wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.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-23_CI_UMa-06-Q2b1x1_040025_TTUQ2b1x1_1644174_oNK3BFsr/wcs_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235.fits
Preparing the HTML report for the field UMa-06-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
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
Adding exclusion_list_local.txt__out06522.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out06535.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out06936.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out07394.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out09051.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out09399.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out10770.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out10930.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out11206.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out11566.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out11744.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out12752.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out12905.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out13788.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out14415.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out15039.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out15602.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out15625.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out15837.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out15959.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out17214.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out18459.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out18650.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out18822.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out18901.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out18997.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out19319.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out20156.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out20346.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out20653.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out21368.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out21699.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out22052.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out22888.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out23618.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out24431.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out24780.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out24971.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out25412.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out30231.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out30513.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31089.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out33033.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out33045.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out33217.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out33585.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out34723.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35235.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35404.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35453.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35634.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35699.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36291.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36443.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36785.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out37384.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out38255.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out38608.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out39507.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out40312.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out40569.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out40575.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out41974.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out42896.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 90s
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: 31s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52324_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52324_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 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 52338_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52338_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52359_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52359_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52381_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52381_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52464_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52464_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52469_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52469_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52478_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52478_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
**** FOUND 09:59:37.81 +56:47:42.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52479_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52479_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52491_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52491_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52497_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52497_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52541_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52541_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52554_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52554_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
**** FOUND 09:39:03.71 +52:19:13.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52579_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52579_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52581_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52581_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
**** FOUND 09:38:30.93 +55:52:36.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52584_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52584_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 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 52605_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52605_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52617_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52617_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52625_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52625_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52639_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
The candidate 52639_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 15959_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 15959_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 24780_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 24780_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21699_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 21699_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 40569_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 40569_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 30231_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 30231_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 41974_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 41974_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 06936_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 06936_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 15625_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 15625_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 22052_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 22052_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 11744_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 11744_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 10930_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 10930_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 42896_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 42896_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35699_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 35699_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33033_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 33033_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 20346_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 20346_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 14415_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 14415_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33045_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 33045_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 12905_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 12905_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 07394_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 07394_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 24431_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 24431_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 15837_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 15837_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36443_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 36443_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 20653_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 20653_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35235_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 35235_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 18822_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 18822_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21368_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 21368_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 37384_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 37384_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 11206_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 11206_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 09399_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 09399_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 24971_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 24971_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 20156_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 20156_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 39507_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 39507_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 18997_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 18997_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 40312_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 40312_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 40575_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 40575_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33585_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 33585_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 11566_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 11566_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 30513_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 30513_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 22888_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 22888_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 17214_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 17214_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31089_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 31089_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 18459_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 18459_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36291_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 36291_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 06522_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 06522_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35634_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 35634_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 09051_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 09051_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33217_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 33217_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 15039_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 15039_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 15602_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 15602_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 06535_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 06535_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35404_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 35404_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 13788_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 13788_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 23618_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 23618_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 25412_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 25412_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 38255_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 38255_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 38608_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 38608_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34723_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 34723_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35453_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 35453_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36785_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 36785_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 18901_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 18901_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 18650_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 18650_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 10770_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 10770_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 12752_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 12752_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 19319_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
Preparing report for the candidate 19319_fd_UMa-06-Q2b1x1_2026-04-23_03-56-47_20.00sec_-4.90C_LIGHT_0235
make_report_in_HTML.sh Phase 2 (HTML assembly): 4s
make_report_in_HTML.sh TOTAL: 125s
Prepared the HTML report for the field UMa-06-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
10:09:10.30 +57:27:56.9
10:09:08.25 +57:27:19.9
10:11:31.00 +57:18:37.6
10:06:30.85 +57:17:00.5
10:12:19.79 +56:46:26.1
10:05:25.08 +56:49:17.7
10:07:51.28 +56:26:34.9
10:05:32.05 +56:26:37.6
10:12:49.00 +56:14:31.9
10:12:01.33 +56:09:56.9
10:06:31.99 +56:13:09.4
10:08:32.62 +55:56:57.8
10:09:06.70 +55:54:18.3
10:11:08.52 +55:39:37.0
10:14:16.14 +55:26:49.0
10:07:35.55 +55:25:06.5
10:08:07.33 +55:16:48.8
10:08:57.01 +55:15:41.8
10:09:14.94 +55:12:38.8
10:14:18.29 +55:04:58.2
10:15:37.79 +54:45:23.0
10:09:56.26 +54:35:19.3
10:13:03.38 +54:28:35.3
10:11:44.04 +54:28:08.9
10:12:35.90 +54:26:01.0
10:06:58.29 +54:30:30.4
10:13:17.84 +54:18:22.5
10:10:25.38 +54:09:47.4
10:13:19.82 +54:03:53.1
10:13:59.74 +53:58:38.4
10:09:09.27 +53:54:35.3
10:07:11.39 +53:52:25.3
10:12:07.97 +53:42:00.7
10:09:27.44 +53:33:36.2
10:12:29.48 +53:19:10.4
10:10:09.58 +53:10:35.4
10:12:36.74 +53:02:56.2
10:09:57.84 +53:03:02.1
10:10:25.93 +52:56:28.6
10:11:12.71 +52:23:53.4
10:05:31.71 +52:34:08.2
10:14:05.49 +52:33:11.5
10:06:14.57 +49:46:54.3
10:05:49.39 +49:47:34.3
10:07:04.45 +49:48:32.7
09:44:31.69 +50:13:45.5
10:10:56.81 +50:07:45.6
10:07:12.28 +50:16:37.0
10:12:23.04 +50:13:09.3
10:05:50.98 +50:22:08.4
10:10:01.10 +50:20:36.4
10:07:11.95 +50:24:03.5
10:06:51.19 +50:34:20.6
10:12:24.81 +50:28:52.8
10:09:16.45 +50:38:06.3
10:06:40.89 +50:51:29.4
10:09:16.99 +50:59:46.2
10:10:21.87 +51:06:00.6
10:09:28.61 +51:16:58.4
10:09:19.49 +51:31:21.0
10:08:37.19 +51:34:47.4
10:13:22.32 +51:28:10.0
09:40:10.64 +52:18:09.1
10:06:40.43 +52:11:55.5
########### Completed UMa-06-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 ####
10:14:18.29 +55:04:58.2
10:12:36.74 +53:02:56.2
10:07:11.39 +53:52:25.3
10:08:37.19 +51:34:47.4
10:11:12.71 +52:23:53.4
09:40:10.64 +52:18:09.1
10:11:31.00 +57:18:37.6
10:08:57.01 +55:15:41.8
10:12:07.97 +53:42:00.7
10:06:31.99 +56:13:09.4
10:05:32.05 +56:26:37.6
10:06:40.43 +52:11:55.5
10:07:11.95 +50:24:03.5
10:06:14.57 +49:46:54.3
10:13:19.82 +54:03:53.1
10:14:16.14 +55:26:49.0
10:05:49.39 +49:47:34.3
10:09:06.70 +55:54:18.3
10:06:30.85 +57:17:00.5
10:10:09.58 +53:10:35.4
10:09:14.94 +55:12:38.8
10:12:24.81 +50:28:52.8
10:13:59.74 +53:58:38.4
10:07:12.28 +50:16:37.0
10:11:44.04 +54:28:08.9
10:09:09.27 +53:54:35.3
10:06:40.89 +50:51:29.4
10:12:49.00 +56:14:31.9
10:05:25.08 +56:49:17.7
10:09:57.84 +53:03:02.1
10:10:25.38 +54:09:47.4
10:09:28.61 +51:16:58.4
10:06:58.29 +54:30:30.4
10:09:19.49 +51:31:21.0
10:13:22.32 +51:28:10.0
09:44:31.69 +50:13:45.5
10:12:01.33 +56:09:56.9
10:05:31.71 +52:34:08.2
10:09:27.44 +53:33:36.2
10:15:37.79 +54:45:23.0
10:14:05.49 +52:33:11.5
10:09:56.26 +54:35:19.3
10:06:51.19 +50:34:20.6
10:09:10.30 +57:27:56.9
10:10:01.10 +50:20:36.4
10:12:19.79 +56:46:26.1
10:07:04.45 +49:48:32.7
10:07:35.55 +55:25:06.5
10:08:07.33 +55:16:48.8
10:09:08.25 +57:27:19.9
10:12:23.04 +50:13:09.3
10:11:08.52 +55:39:37.0
10:12:29.48 +53:19:10.4
10:10:25.93 +52:56:28.6
10:09:16.99 +50:59:46.2
10:10:21.87 +51:06:00.6
10:10:56.81 +50:07:45.6
10:05:50.98 +50:22:08.4
10:09:16.45 +50:38:06.3
10:12:35.90 +54:26:01.0
10:13:03.38 +54:28:35.3
10:07:51.28 +56:26:34.9
10:08:32.62 +55:56:57.8
10:13:17.84 +54:18:22.5
###################################################################################
10:14:18.29 +55:04:58.2 -- not an asteroid (will add it to exclusion list)
10:12:36.74 +53:02:56.2 -- not an asteroid (will add it to exclusion list)
10:07:11.39 +53:52:25.3 -- not an asteroid (will add it to exclusion list)
10:08:37.19 +51:34:47.4 -- not an asteroid (will add it to exclusion list)
10:11:12.71 +52:23:53.4 -- not an asteroid (will add it to exclusion list)
09:40:10.64 +52:18:09.1 -- not an asteroid (will add it to exclusion list)
10:11:31.00 +57:18:37.6 -- not an asteroid (will add it to exclusion list)
10:08:57.01 +55:15:41.8 -- not an asteroid (will add it to exclusion list)
10:12:07.97 +53:42:00.7 -- not an asteroid (will add it to exclusion list)
10:06:31.99 +56:13:09.4 -- not an asteroid (will add it to exclusion list)
10:05:32.05 +56:26:37.6 -- not an asteroid (will add it to exclusion list)
10:06:40.43 +52:11:55.5 -- not an asteroid (will add it to exclusion list)
10:07:11.95 +50:24:03.5 -- not an asteroid (will add it to exclusion list)
10:06:14.57 +49:46:54.3 -- not an asteroid (will add it to exclusion list)
10:13:19.82 +54:03:53.1 -- not an asteroid (will add it to exclusion list)
10:14:16.14 +55:26:49.0 -- not an asteroid (will add it to exclusion list)
10:05:49.39 +49:47:34.3 -- not an asteroid (will add it to exclusion list)
10:09:06.70 +55:54:18.3 -- not an asteroid (will add it to exclusion list)
10:06:30.85 +57:17:00.5 -- not an asteroid (will add it to exclusion list)
10:10:09.58 +53:10:35.4 -- not an asteroid (will add it to exclusion list)
10:09:14.94 +55:12:38.8 -- not an asteroid (will add it to exclusion list)
10:12:24.81 +50:28:52.8 -- not an asteroid (will add it to exclusion list)
10:13:59.74 +53:58:38.4 -- not an asteroid (will add it to exclusion list)
10:07:12.28 +50:16:37.0 -- not an asteroid (will add it to exclusion list)
10:11:44.04 +54:28:08.9 -- not an asteroid (will add it to exclusion list)
10:09:09.27 +53:54:35.3 -- not an asteroid (will add it to exclusion list)
10:06:40.89 +50:51:29.4 -- not an asteroid (will add it to exclusion list)
10:12:49.00 +56:14:31.9 -- not an asteroid (will add it to exclusion list)
10:05:25.08 +56:49:17.7 -- not an asteroid (will add it to exclusion list)
10:09:57.84 +53:03:02.1 -- not an asteroid (will add it to exclusion list)
10:10:25.38 +54:09:47.4 -- not an asteroid (will add it to exclusion list)
10:09:28.61 +51:16:58.4 -- not an asteroid (will add it to exclusion list)
10:06:58.29 +54:30:30.4 -- not an asteroid (will add it to exclusion list)
10:09:19.49 +51:31:21.0 -- not an asteroid (will add it to exclusion list)
10:13:22.32 +51:28:10.0 -- not an asteroid (will add it to exclusion list)
09:44:31.69 +50:13:45.5 -- not an asteroid (will add it to exclusion list)
10:12:01.33 +56:09:56.9 -- not an asteroid (will add it to exclusion list)
10:05:31.71 +52:34:08.2 -- not an asteroid (will add it to exclusion list)
10:09:27.44 +53:33:36.2 -- not an asteroid (will add it to exclusion list)
10:15:37.79 +54:45:23.0 -- not an asteroid (will add it to exclusion list)
10:14:05.49 +52:33:11.5 -- not an asteroid (will add it to exclusion list)
10:09:56.26 +54:35:19.3 -- not an asteroid (will add it to exclusion list)
10:06:51.19 +50:34:20.6 -- not an asteroid (will add it to exclusion list)
10:09:10.30 +57:27:56.9 -- not an asteroid (will add it to exclusion list)
10:10:01.10 +50:20:36.4 -- not an asteroid (will add it to exclusion list)
10:12:19.79 +56:46:26.1 -- not an asteroid (will add it to exclusion list)
10:07:04.45 +49:48:32.7 -- not an asteroid (will add it to exclusion list)
10:07:35.55 +55:25:06.5 -- not an asteroid (will add it to exclusion list)
10:08:07.33 +55:16:48.8 -- not an asteroid (will add it to exclusion list)
10:09:08.25 +57:27:19.9 -- not an asteroid (will add it to exclusion list)
10:12:23.04 +50:13:09.3 -- not an asteroid (will add it to exclusion list)
10:11:08.52 +55:39:37.0 -- not an asteroid (will add it to exclusion list)
10:12:29.48 +53:19:10.4 -- not an asteroid (will add it to exclusion list)
10:10:25.93 +52:56:28.6 -- not an asteroid (will add it to exclusion list)
10:09:16.99 +50:59:46.2 -- not an asteroid (will add it to exclusion list)
10:10:21.87 +51:06:00.6 -- not an asteroid (will add it to exclusion list)
10:10:56.81 +50:07:45.6 -- not an asteroid (will add it to exclusion list)
10:05:50.98 +50:22:08.4 -- not an asteroid (will add it to exclusion list)
10:09:16.45 +50:38:06.3 -- not an asteroid (will add it to exclusion list)
10:12:35.90 +54:26:01.0 -- not an asteroid (will add it to exclusion list)
10:13:03.38 +54:28:35.3 -- not an asteroid (will add it to exclusion list)
10:07:51.28 +56:26:34.9 -- not an asteroid (will add it to exclusion list)
10:08:32.62 +55:56:57.8 -- not an asteroid (will add it to exclusion list)
10:13:17.84 +54:18:22.5 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
09:40:10.64 +52:18:09.1 -- does not seem to be a hot pixel (will add it to exclusion list)
09:44:31.69 +50:13:45.5 -- does not seem to be a hot pixel (will add it to exclusion list)
10:05:25.08 +56:49:17.7 -- does not seem to be a hot pixel (will add it to exclusion list)
10:05:31.71 +52:34:08.2 -- does not seem to be a hot pixel (will add it to exclusion list)
10:05:32.05 +56:26:37.6 -- does not seem to be a hot pixel (will add it to exclusion list)
10:05:49.39 +49:47:34.3 -- does not seem to be a hot pixel (will add it to exclusion list)
10:05:50.98 +50:22:08.4 -- does not seem to be a hot pixel (will add it to exclusion list)
10:06:14.57 +49:46:54.3 -- does not seem to be a hot pixel (will add it to exclusion list)
10:06:30.85 +57:17:00.5 -- does not seem to be a hot pixel (will add it to exclusion list)
10:06:31.99 +56:13:09.4 -- does not seem to be a hot pixel (will add it to exclusion list)
10:06:40.43 +52:11:55.5 -- does not seem to be a hot pixel (will add it to exclusion list)
10:06:40.89 +50:51:29.4 -- does not seem to be a hot pixel (will add it to exclusion list)
10:06:51.19 +50:34:20.6 -- does not seem to be a hot pixel (will add it to exclusion list)
10:06:58.29 +54:30:30.4 -- does not seem to be a hot pixel (will add it to exclusion list)
10:07:04.45 +49:48:32.7 -- does not seem to be a hot pixel (will add it to exclusion list)
10:07:11.39 +53:52:25.3 -- does not seem to be a hot pixel (will add it to exclusion list)
10:07:11.95 +50:24:03.5 -- does not seem to be a hot pixel (will add it to exclusion list)
10:07:12.28 +50:16:37.0 -- does not seem to be a hot pixel (will add it to exclusion list)
10:07:35.55 +55:25:06.5 -- does not seem to be a hot pixel (will add it to exclusion list)
10:07:51.28 +56:26:34.9 -- does not seem to be a hot pixel (will add it to exclusion list)
10:08:07.33 +55:16:48.8 -- does not seem to be a hot pixel (will add it to exclusion list)
10:08:32.62 +55:56:57.8 -- does not seem to be a hot pixel (will add it to exclusion list)
10:08:37.19 +51:34:47.4 -- does not seem to be a hot pixel (will add it to exclusion list)
10:08:57.01 +55:15:41.8 -- does not seem to be a hot pixel (will add it to exclusion list)
10:09:06.70 +55:54:18.3 -- does not seem to be a hot pixel (will add it to exclusion list)
10:09:08.25 +57:27:19.9 -- does not seem to be a hot pixel (will add it to exclusion list)
10:09:09.27 +53:54:35.3 -- does not seem to be a hot pixel (will add it to exclusion list)
10:09:10.30 +57:27:56.9 -- does not seem to be a hot pixel (will add it to exclusion list)
10:09:14.94 +55:12:38.8 -- does not seem to be a hot pixel (will add it to exclusion list)
10:09:16.45 +50:38:06.3 -- does not seem to be a hot pixel (will add it to exclusion list)
10:09:16.99 +50:59:46.2 -- does not seem to be a hot pixel (will add it to exclusion list)
10:09:19.49 +51:31:21.0 -- does not seem to be a hot pixel (will add it to exclusion list)
10:09:27.44 +53:33:36.2 -- does not seem to be a hot pixel (will add it to exclusion list)
10:09:28.61 +51:16:58.4 -- does not seem to be a hot pixel (will add it to exclusion list)
10:09:56.26 +54:35:19.3 -- does not seem to be a hot pixel (will add it to exclusion list)
10:09:57.84 +53:03:02.1 -- does not seem to be a hot pixel (will add it to exclusion list)
10:10:01.10 +50:20:36.4 -- does not seem to be a hot pixel (will add it to exclusion list)
10:10:09.58 +53:10:35.4 -- does not seem to be a hot pixel (will add it to exclusion list)
10:10:21.87 +51:06:00.6 -- does not seem to be a hot pixel (will add it to exclusion list)
10:10:25.38 +54:09:47.4 -- does not seem to be a hot pixel (will add it to exclusion list)
10:10:25.93 +52:56:28.6 -- does not seem to be a hot pixel (will add it to exclusion list)
10:10:56.81 +50:07:45.6 -- does not seem to be a hot pixel (will add it to exclusion list)
10:11:08.52 +55:39:37.0 -- does not seem to be a hot pixel (will add it to exclusion list)
10:11:12.71 +52:23:53.4 -- does not seem to be a hot pixel (will add it to exclusion list)
10:11:31.00 +57:18:37.6 -- does not seem to be a hot pixel (will add it to exclusion list)
10:11:44.04 +54:28:08.9 -- does not seem to be a hot pixel (will add it to exclusion list)
10:12:01.33 +56:09:56.9 -- does not seem to be a hot pixel (will add it to exclusion list)
10:12:07.97 +53:42:00.7 -- does not seem to be a hot pixel (will add it to exclusion list)
10:12:19.79 +56:46:26.1 -- does not seem to be a hot pixel (will add it to exclusion list)
10:12:23.04 +50:13:09.3 -- does not seem to be a hot pixel (will add it to exclusion list)
10:12:24.81 +50:28:52.8 -- does not seem to be a hot pixel (will add it to exclusion list)
10:12:29.48 +53:19:10.4 -- does not seem to be a hot pixel (will add it to exclusion list)
10:12:35.90 +54:26:01.0 -- does not seem to be a hot pixel (will add it to exclusion list)
10:12:36.74 +53:02:56.2 -- does not seem to be a hot pixel (will add it to exclusion list)
10:12:49.00 +56:14:31.9 -- does not seem to be a hot pixel (will add it to exclusion list)
10:13:03.38 +54:28:35.3 -- does not seem to be a hot pixel (will add it to exclusion list)
10:13:17.84 +54:18:22.5 -- does not seem to be a hot pixel (will add it to exclusion list)
10:13:19.82 +54:03:53.1 -- does not seem to be a hot pixel (will add it to exclusion list)
10:13:22.32 +51:28:10.0 -- does not seem to be a hot pixel (will add it to exclusion list)
10:13:59.74 +53:58:38.4 -- does not seem to be a hot pixel (will add it to exclusion list)
10:14:05.49 +52:33:11.5 -- does not seem to be a hot pixel (will add it to exclusion list)
10:14:16.14 +55:26:49.0 -- does not seem to be a hot pixel (will add it to exclusion list)
10:14:18.29 +55:04:58.2 -- does not seem to be a hot pixel (will add it to exclusion list)
10:15:37.79 +54:45:23.0 -- does not seem to be a hot pixel (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_nohotpixels' -> 'exclusion_list_index_html.txt'
# Count candidates with no identification (that also don't look like hot pix)
09:40:10.64 +52:18:09.1 -- not a known variable star
09:44:31.69 +50:13:45.5 -- not a known variable star
10:05:25.08 +56:49:17.7 -- not a known variable star
10:05:31.71 +52:34:08.2 -- not a known variable star
10:05:32.05 +56:26:37.6 -- not a known variable star
10:05:49.39 +49:47:34.3 -- not a known variable star
10:05:50.98 +50:22:08.4 -- not a known variable star
10:06:14.57 +49:46:54.3 -- not a known variable star
10:06:30.85 +57:17:00.5 -- not a known variable star
10:06:31.99 +56:13:09.4 -- not a known variable star
10:06:40.43 +52:11:55.5 -- not a known variable star
10:06:40.89 +50:51:29.4 -- not a known variable star
10:06:51.19 +50:34:20.6 -- not a known variable star
10:06:58.29 +54:30:30.4 -- not a known variable star
10:07:04.45 +49:48:32.7 -- not a known variable star
10:07:11.39 +53:52:25.3 -- not a known variable star
10:07:11.95 +50:24:03.5 -- not a known variable star
10:07:12.28 +50:16:37.0 -- not a known variable star
10:07:35.55 +55:25:06.5 -- not a known variable star
10:07:51.28 +56:26:34.9 -- a known variable star
10:08:07.33 +55:16:48.8 -- not a known variable star
10:08:32.62 +55:56:57.8 -- not a known variable star
10:08:37.19 +51:34:47.4 -- not a known variable star
10:08:57.01 +55:15:41.8 -- not a known variable star
10:09:06.70 +55:54:18.3 -- not a known variable star
10:09:08.25 +57:27:19.9 -- not a known variable star
10:09:09.27 +53:54:35.3 -- not a known variable star
10:09:10.30 +57:27:56.9 -- not a known variable star
10:09:14.94 +55:12:38.8 -- not a known variable star
10:09:16.45 +50:38:06.3 -- not a known variable star
10:09:16.99 +50:59:46.2 -- a known variable star
10:09:19.49 +51:31:21.0 -- not a known variable star
10:09:27.44 +53:33:36.2 -- not a known variable star
10:09:28.61 +51:16:58.4 -- not a known variable star
10:09:56.26 +54:35:19.3 -- not a known variable star
10:09:57.84 +53:03:02.1 -- not a known variable star
10:10:01.10 +50:20:36.4 -- not a known variable star
10:10:09.58 +53:10:35.4 -- not a known variable star
10:10:21.87 +51:06:00.6 -- not a known variable star
10:10:25.38 +54:09:47.4 -- not a known variable star
10:10:25.93 +52:56:28.6 -- not a known variable star
10:10:56.81 +50:07:45.6 -- not a known variable star
10:11:08.52 +55:39:37.0 -- not a known variable star
10:11:12.71 +52:23:53.4 -- not a known variable star
10:11:31.00 +57:18:37.6 -- not a known variable star
10:11:44.04 +54:28:08.9 -- not a known variable star
10:12:01.33 +56:09:56.9 -- not a known variable star
10:12:07.97 +53:42:00.7 -- not a known variable star
10:12:19.79 +56:46:26.1 -- not a known variable star
10:12:23.04 +50:13:09.3 -- not a known variable star
10:12:24.81 +50:28:52.8 -- not a known variable star
10:12:29.48 +53:19:10.4 -- a known variable star
10:12:35.90 +54:26:01.0 -- not a known variable star
10:12:36.74 +53:02:56.2 -- not a known variable star
10:12:49.00 +56:14:31.9 -- not a known variable star
10:13:03.38 +54:28:35.3 -- not a known variable star
10:13:17.84 +54:18:22.5 -- not a known variable star
10:13:19.82 +54:03:53.1 -- a known variable star
10:13:22.32 +51:28:10.0 -- not a known variable star
10:13:59.74 +53:58:38.4 -- not a known variable star
10:14:05.49 +52:33:11.5 -- not a known variable star
10:14:16.14 +55:26:49.0 -- not a known variable star
10:14:18.29 +55:04:58.2 -- not a known variable star
10:15:37.79 +54:45:23.0 -- not a known variable star
Found 60 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
64 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 64 (excluding asteroids and hot pixels, 60 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)2461153.87239231 -observatory V36
00:48:51.34 +02:30:20.3 Mercury (-0.3mag)
03:45:11.63 +20:23:57.2 Venus (-3.9mag)
00:38:45.11 +03:09:12.6 Mars (1.2mag)
07:16:15.70 +22:40:04.4 Jupiter (-2.1mag)
00:32:25.47 +01:09:04.2 Saturn (0.9mag)
03:49:17.66 +19:52:33.2 Uranus (5.8mag)
00:11:46.94 -00:09:27.8 Neptune (7.8mag)
20:34:01.44 -22:53:08.3 Pluto (14.5mag)
07:40:39.98 +24:12:13.8 Moon (-10.1mag)
-rw-r--r-- 1 apache apache 363 Apr 23 04:02 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461153.87239231:
07:16:21.38 +22:39:53.9 Io (5.8mag)
07:16:23.78 +22:39:48.6 Europa (6.0mag)
07:16:31.70 +22:39:25.4 Ganymede (5.4mag)
07:15:45.41 +22:41:04.6 Callisto (6.6mag)
07:19:14.98 +22:24:29.7 Himalia (15.4mag)
07:16:19.58 +22:39:54.2 Thebe (16.3mag)
07:19:34.79 +22:54:45.0 Elara (17.3mag)
07:15:38.59 +23:16:13.2 Pasiphae (17.5mag)
07:24:24.95 +22:38:45.2 Carme (18.6mag)
00:32:24.51 +01:08:54.9 Titan (8.8mag)
00:32:26.54 +01:09:19.2 Rhea (10.1mag)
00:31:56.67 +01:08:04.5 Iapetus (11.5mag)
00:32:15.06 +01:09:11.9 Hyperion (14.8mag)
00:33:56.24 +01:17:02.9 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 23 04:02 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461153.87239231:
16:06:38.00 -21:00:26.3 JWST
19:11:06.64 +16:08:34.2 Chandra
19:20:53.86 -01:39:54.1 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 23 04:02 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461153.87239231 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
05:37:37.44 +30:47:57.0 18.0mag P/2009 WX51 (Catalina)
18:54:25.71 -29:13:59.1 13.8mag P/2010 H2 (Vales)
05:12:15.45 -69:19:43.5 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:34:10.92 +31:29:27.6 17.3mag C/2017 K2 (PANSTARRS)
17:29:26.02 +11:24:13.5 17.7mag C/2021 G2 (ATLAS)
23:11:59.43 +29:32:09.0 17.1mag C/2022 E2 (ATLAS)
04:37:55.93 +26:13:51.6 16.1mag C/2022 N2 (PANSTARRS)
09:05:21.14 +32:01:44.3 16.3mag C/2022 QE78 (ATLAS)
08:32:28.36 +00:35:49.8 17.4mag C/2022 R6 (PANSTARRS)
18:51:40.65 +19:08:08.3 17.6mag C/2023 A3 (Tsuchinshan-ATLAS)
15:38:05.71 -11:24:46.3 17.5mag P/2023 B1 (PANSTARRS)
09:04:38.69 -10:44:30.6 17.7mag C/2023 F3 (ATLAS)
22:01:00.50 +63:21:39.4 17.6mag C/2023 H5 (Lemmon)
19:11:55.54 -03:53:06.3 14.1mag C/2023 R1 (PANSTARRS)
21:06:33.51 +86:56:49.4 17.8mag C/2023 X2 (Lemmon)
06:22:02.71 +63:30:00.9 17.2mag C/2024 A1 (ATLAS)
05:28:29.55 +20:30:28.1 11.5mag C/2024 E1 (Wierzchos)
16:14:14.99 +07:35:10.3 17.3mag C/2024 G6 (ATLAS)
20:22:30.05 +17:19:20.3 14.5mag C/2024 J3 (ATLAS)
03:33:06.65 -21:17:43.1 16.3mag C/2024 T5 (ATLAS)
05:23:08.02 +43:31:36.1 17.7mag C/2025 J1 (Borisov)
13:09:03.08 +49:19:45.7 15.5mag C/2025 L1 (ATLAS)
03:37:20.06 -27:24:54.0 17.9mag C/2025 Q3 (ATLAS)
01:26:43.17 +12:42:36.5 7.8mag C/2025 R3 (PANSTARRS)
12:50:59.72 +03:26:16.4 17.4mag C/2025 Y1 (ATLAS)
04:16:54.06 +02:03:33.1 15.1mag C/2026 A1 (MAPS)
00:19:51.39 +38:28:36.9 14.8mag C/2026 B2 (Sun-Gao)
18:57:14.30 -09:19:01.5 11.4mag 10P/Tempel
14:50:15.12 +02:21:44.7 14.6mag 24P/Schaumasse
11:01:05.33 -01:18:26.1 15.7mag 29P/Schwassmann-Wachmann
10:37:52.26 -03:34:08.9 17.1mag 43P/Wolf-Harrington
02:00:07.51 +18:43:41.2 17.3mag 47P/Ashbrook-Jackson
07:24:45.36 +35:23:47.1 17.0mag 63P/Wild
23:38:17.09 -10:35:11.2 15.7mag 65P/Gunn
04:23:23.28 +23:40:46.8 15.9mag 76P/West-Kohoutek-Ikemura
01:22:00.80 +09:39:37.2 14.2mag 78P/Gehrels
23:24:49.32 -07:12:44.8 14.7mag 88P/Howell
02:31:37.79 +22:32:24.0 15.0mag 93P/Lovas
05:09:06.07 +32:38:58.5 16.1mag 123P/West-Hartley
08:37:39.89 +34:58:09.5 16.2mag 124P/Mrkos
02:44:42.97 +15:10:33.0 16.4mag 128P/Shoemaker-Holt
03:02:04.24 +15:21:31.7 17.5mag 131P/Mueller
02:05:32.78 +15:33:55.6 10.5mag 141P/Machholz
02:13:15.49 +07:35:39.0 10.5mag 141P-A/Machholz
00:55:32.43 +03:19:59.8 12.0mag 141P-D/Machholz
02:43:53.75 +09:19:06.7 17.9mag 141P-I/Machholz
01:23:04.30 +02:11:54.4 15.0mag 162P/SidingSpring
14:38:31.85 +00:35:38.7 17.9mag 210P/Christensen
21:59:10.05 -09:41:45.8 17.8mag 218P/LINEAR
17:17:24.33 -13:01:53.5 16.1mag 235P/LINEAR
05:50:37.38 +35:11:16.8 16.9mag 240P/NEAT
07:42:27.27 -04:24:42.7 17.8mag 242P/Spahr
22:35:22.16 -18:55:43.6 17.7mag 260P/McNaught
02:13:32.83 +22:17:56.7 17.9mag 295P/LINEAR
15:39:27.84 +07:26:35.7 17.5mag 391P/Kowalski
07:37:20.63 +21:22:19.1 17.7mag 450P/LONEOS
05:46:50.62 +44:36:06.2 17.6mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.9K Apr 23 04:02 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 23 04:02 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 23 04:02 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
14:39:35.385 +13:27:11.96 AT 2026jrd 2026-04-15.44 20.14
04:02:17.791 +25:48:48.21 AT 2026jrc 2026-04-15.13 17.3477
17:13:00.934 -11:35:38.06 AT 2026jrb 2026-04-09.42 18.3562
16:22:35.208 -07:41:50.91 AT 2026jra 2026-04-15.42 18.678
14:38:49.756 +05:59:17.55 AT 2026jqz 2026-04-10.33 20.5079
17:37:46.128 -00:10:27.29 AT 2026jqy 2026-04-15.44 19.9423
21:22:43.135 +01:34:03.91 AT 2026jqx 2026-04-15.50 19.506
20:20:49.879 -54:50:37.33 AT 2026jqw 2026-04-15.38 18.428
14:18:06.700 +18:27:11.82 AT 2026jqv 2026-04-15.09 18.593
05:54:56.359 -64:02:05.45 AT 2026jqu 2026-04-15.74 19.448
23:56:40.308 -79:35:41.95 AT 2026jqt 2026-04-15.38 18.924
04:07:29.216 -53:22:08.08 AT 2026jqs 2026-04-15.75 18.414
15:43:49.348 +30:31:32.85 AT 2026jqr 2026-04-15.07 19.396
10:01:06.186 +12:53:37.52 AT 2026jqq 2026-04-14.00 19.168
21:41:55.797 +08:42:01.92 AT 2026jqp 2026-04-15.51 19.6758
20:30:05.017 +14:09:09.48 AT 2026jqo 2026-04-13.20 19.78
18:56:45.384 +43:09:18.15 AT 2026jqn 2026-04-14.23 18.62
12:34:36.583 +07:30:35.59 AT 2026jqm 2026-04-15.29 22.3871
21:15:43.547 +02:04:36.79 AT 2026jql 2026-04-10.51 18.5787
21:17:35.104 -09:31:48.68 AT 2026jqk 2026-04-08.51 19.2234
-rw-r--r-- 1 apache apache 30K Apr 23 04:02 tns_transients_list.txt
