This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH
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 19.2377* 08 40 56.62 +50 10 04.2 9.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,2461149.7377,9.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 9.95CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,10.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 10.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.07CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,9.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 9.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,11.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 11.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,11.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 11.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,12.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 12.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,12.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 12.10CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,12.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 12.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,12.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 12.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,12.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 12.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,12.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 12.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,12.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 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 19.2377* 09 17 21.38 +56 27 13.0 13.2 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,2461149.7377,13.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,12.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 12.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.01CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.2377* 08 40 00.77 +56 09 18.5 13.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
target,2461149.7377,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1034059388497539712,2461149.7377,13.17,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1034059388497539712 20260419.2377 13.17CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.2377* 09 16 34.24 +56 00 15.0 13.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,2461149.7377,13.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.2377* 08 47 19.03 +55 11 00.3 13.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,2461149.7377,13.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.92CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.2377* 08 51 44.76 +55 58 46.2 14.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
ATO J132.9231+55.9801,2461149.7377,14.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J132.9231+55.9801 20260419.2377 14.26CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 19.2377 2461149.7377 14.16 08:59:49.81 +50:48:56.0
167.85079 40.71037 galactic UMa Second-epoch detections are separated by 5.4" and 4.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Large-amplitude variable Gaia DR2 1016098007063555200 | 08:59:51.66 +50:48:29.7 (Gaia DR3) | 2021A&A...648A..44M | | Gaia3var=NOT_AVAILABLE (the VSX policy as of May 2022 seems to be NOT to regard variables from 2021A&A...648A..44M as 'known' for the lack of classification) SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.2377* 08 59 49.81 +50 48 56.0 14.2 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
Large-amplitude variable Gaia DR2 1016098007063555200,2461149.7377,14.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Large-amplitude variable Gaia DR2 1016098007063555200 20260419.2377 14.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 13.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.2377* 09 08 03.43 +50 22 54.1 14.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,2461149.7377,14.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 14.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,14.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 14.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,14.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 14.26CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.7377,10.25,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.2377 10.25CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461058.81301528 18.01.2026 07:30:34.520 /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
First image: 2461058.81301528 18.01.2026 07:30:34.520 /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
Last image: 2461149.73799494 19.04.2026 05:42:32.763 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 4
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.42
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: 4 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): 10242
Objects passed selection criteria: 10232
Measurements per detected object (mean, median, min, max): 3.6 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.6 4.0 2 4
Average stars detected per image: 9498
Average stars matched: 9355.5 (98.4997 %)
Memory usage VmPeak: 115640 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Apr 16 15:05:05 CDT 2026
VaST build number 1.0rc89-19-g55e4b97d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sun Apr 19 00:45:17 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: 2461058.81301528 18.01.2026 07:30:34.520 /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
First image: 2461058.81301528 18.01.2026 07:30:34.520 /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
Last image: 2461149.73799494 19.04.2026 05:42:32.763 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 91
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.20
Magnitude-Size filter: Disabled
For each source choose aperture with the smallest scatter: YES
Photometric errors rescaling: NO
Number of identified bad images: 0
Number of SysRem iterations: 0
User-specified moving object: none
Computation time: 22 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): 59113
Objects passed selection criteria: 58959
Measurements per detected object (mean, median, min, max): 3.7 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.7 4.0 2 4
Average stars detected per image: 56902.8
Average stars matched: 55337.8 (97.2497 %)
Memory usage VmPeak: 160056 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Apr 16 15:05:05 CDT 2026
VaST build number 1.0rc89-19-g55e4b97d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sun Apr 19 00:55:39 CDT 2026
Host name: tau
############################################################
Updating neverexclude_list.txt
'/var/www/nmw_calibration/neverexclude_list.txt' -> './neverexclude_list.txt'
Choosing bad regions list
'/var/www/nmw_calibration/TTUQ1b1x1/TTUQ1_bad_region.lst' -> 'bad_region.lst'
wait
*------ default.sex.telephoto_lens_onlybrightstars_v1 ------*
'default.sex.telephoto_lens_onlybrightstars_v1' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_onlybrightstars_v1
./vast --norotation --noflagimage --starmatchraius 3.5 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
SExtractor catalog cache: saved Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat to cache
SExtractor catalog cache: saved Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.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/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
Checking WCS cache directory local_wcs_cache
Checking WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Found WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Checking WCS cache directory /home/NMW_web_upload/solved_reference_images
Checking WCS cache directory /dataX/kirx/NMW_NG_rt3_autumn2019/solved_reference_images
The reference JD(UT) for computing planet and comet positions: 2461149.73732584
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_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits exists and is non-empty
Saving wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits to local_wcs_cache/
'wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits' -> 'local_wcs_cache/wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits'
wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits exists and is non-empty
Saving wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits to local_wcs_cache/
'wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits' -> 'local_wcs_cache/wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits'
wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits exists and is non-empty
Saving wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits to local_wcs_cache/
'wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits' -> 'local_wcs_cache/wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits'
wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits exists and is non-empty
Saving wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits to local_wcs_cache/
'wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits' -> 'local_wcs_cache/wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits (1st reference image)
verification OK: wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
Image size: 927.4'x629.8' 15.5(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.92"/pix along the Y axis
Image center: 08:28:35.075 +53:59:05.09 J2000 4789.000 3195.000
###################################
The image scale is 5.81"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.8" and 8.7"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits (1st new image)
verification OK: wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
Image size: 927.1'x629.4' 15.5(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.91"/pix along the Y axis
Image center: 08:28:50.750 +53:58:35.07 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 08:28:35.075 +53:59:05.09
Second-epoch image center 08:28:50.750 +53:58:35.07
Angular distance between the image centers 0.0393 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits (2nd new image)
verification OK: wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
Image size: 927.1'x629.5' 15.5(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.91"/pix along the Y axis
Image center: 08:28:52.791 +53:58:50.43 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 08:28:35.075 +53:59:05.09
Second-epoch image center 08:28:52.791 +53:58:50.43
Angular distance between the image centers 0.0436 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 08:28:50.750 +53:58:35.07
Second-epoch second image center 08:28:52.791 +53:58:50.43
Angular distance between the image centers 0.00657 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/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits &> /tmp/tmp.StHNjCpmZa
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits &> /tmp/tmp.ffsOAEBMPj
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits &> /tmp/tmp.t0OMraI5Q4
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits &> /tmp/tmp.A61cXctnD8
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
Calibrating the magnitude scale
Found non-empty wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.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_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits and wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.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_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits and wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat
Found non-empty wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits and wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat
The reference image (wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits) and catalog (wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat) found
'wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat' -> 'wcsmag.cat'
Read 10732 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 113.1029 to 142.4921 deg, Dec +47.7241 to +59.2635 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 113.1029 to 142.4921 deg, Dec 47.7241 to 59.2635 deg
Loaded 7241 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): 20 out of 20 total matches.
Matched with Tycho-2 20 out of 10732 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.854505
a=0.000000 b=1.000000 c=22.854505
From vast_summary.log: estimated ref. image limiting mag.: -7.42
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.43
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.43
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 2 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.1 pix Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
2.1 pix Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
2.1 pix fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
2.1 pix fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
Limiting magnitude estimates:
15.4 mag. Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
15.4 mag. Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
15.2 mag. fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
15.1 mag. fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
All-image limiting magnitude estimate: 15.1 (SNR ) 12.1 (80% of stars) with default.sex.telephoto_lens_onlybrightstars_v1
The first estimate is the magnitude of a star detected with a signal-to-noise ratio of following Karpov (2025, Acta Polytechnica, 65, 50).
This value should be representative of the faintest stars clearly visible in the image.
The brighter of the limiting magnitude estimates for the two second-epoch images is reported here.
The second estimate is the 80th percentile of the magnitude distribution of stars detected on all four images.
This value is representative of the faintest object that may enter the candidate transients list.
The hard cut-off for the candidate transients is 15.0 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.StHNjCpmZa (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits 569.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits' -> 'wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
WCS_IMAGE_NAME=wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
WCS-calibrated image found: wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
Checking if the catalog wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat corresponding to the image wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits alredy exist and is non-empty...
Catalog wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat corresponding to the image wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
WCS catalog name: wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=751, passed=10732
Got 10732 stars (including 9968 good ones) from the SExtractor catalog wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat
util/solve_plate_with_UCAC5 got 10732 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 927.4'
Seting catalog search parameters based on the expected field of view 927.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012881 (46.4 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010304 (37.1 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 178 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 147 matched stars entering correct_measured_positions(), 124 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.17"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 141 matched stars entering correct_measured_positions(), 1637 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.63"
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 223 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 205 matched stars entering correct_measured_positions(), 1671 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.34"
Accuracy estimation diagnostic: 202 matched stars entering correct_measured_positions(), 2144 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.08"
Excluding outliers - 202 stars left (next iteration limit 155)
The image catalog is written to wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits -region wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.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.ffsOAEBMPj (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits 569.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits' -> 'wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
WCS_IMAGE_NAME=wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
WCS-calibrated image found: wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
Checking if the catalog wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat corresponding to the image wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits alredy exist and is non-empty...
Catalog wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat corresponding to the image wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
WCS catalog name: wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=785, passed=10668
Got 10668 stars (including 9872 good ones) from the SExtractor catalog wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat
util/solve_plate_with_UCAC5 got 10668 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 927.5'
Seting catalog search parameters based on the expected field of view 927.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012882 (46.4 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010306 (37.1 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 172 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 142 matched stars entering correct_measured_positions(), 117 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.19"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 137 matched stars entering correct_measured_positions(), 1584 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.80"
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 219 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 199 matched stars entering correct_measured_positions(), 1618 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.56"
Accuracy estimation diagnostic: 198 matched stars entering correct_measured_positions(), 2106 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.06"
Excluding outliers - 198 stars left (next iteration limit 150)
The image catalog is written to wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits -region wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.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.t0OMraI5Q4 (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
WCS_IMAGE_NAME=wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
WCS-calibrated image found: wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
Checking if the catalog wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat corresponding to the image wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits alredy exist and is non-empty...
Catalog wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat corresponding to the image wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
WCS catalog name: wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=551, passed=8446
Got 8446 stars (including 7887 good ones) from the SExtractor catalog wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat
util/solve_plate_with_UCAC5 got 8446 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 927.1'
Seting catalog search parameters based on the expected field of view 927.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012876 (46.4 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010301 (37.1 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 204 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 174 matched stars entering correct_measured_positions(), 139 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.64"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 173 matched stars entering correct_measured_positions(), 1529 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.85"
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 257 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 236 matched stars entering correct_measured_positions(), 1563 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.45"
Accuracy estimation diagnostic: 236 matched stars entering correct_measured_positions(), 2016 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.79"
Excluding outliers - 236 stars left (next iteration limit 190)
The image catalog is written to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits -region wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.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.A61cXctnD8 (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
WCS_IMAGE_NAME=wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
WCS-calibrated image found: wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
Checking if the catalog wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat corresponding to the image wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits alredy exist and is non-empty...
Catalog wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat corresponding to the image wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
WCS catalog name: wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=540, passed=8368
Got 8368 stars (including 7816 good ones) from the SExtractor catalog wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat
util/solve_plate_with_UCAC5 got 8368 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 927.1'
Seting catalog search parameters based on the expected field of view 927.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012876 (46.4 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010301 (37.1 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 202 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 172 matched stars entering correct_measured_positions(), 141 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.74"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 170 matched stars entering correct_measured_positions(), 1523 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.61"
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 255 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 235 matched stars entering correct_measured_positions(), 1560 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.48"
Accuracy estimation diagnostic: 234 matched stars entering correct_measured_positions(), 2039 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.04"
Excluding outliers - 234 stars left (next iteration limit 187)
The image catalog is written to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits -region wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.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_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits'
Saving fully-calibrated image wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits'
Saving fully-calibrated image wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits'
Saving fully-calibrated image wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits'
Preparing the HTML report for the field Lyn-02-Q1b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Adding exclusion_list_local.txt__out02150.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out20507.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 15s
Pre-generating preview images in parallel...
Done pre-generating preview images.
Pre-generating finding charts in parallel...
Done pre-generating finding charts.
make_report_in_HTML.sh Pre-generation: 2s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 20507_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 20507_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 02150_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 02150_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
make_report_in_HTML.sh Phase 2 (HTML assembly): 0s
make_report_in_HTML.sh TOTAL: 17s
Prepared the HTML report for the field Lyn-02-Q1b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
*------ done with default.sex.telephoto_lens_onlybrightstars_v1 ------*
#### The local exclusion list is exclusion_list_local.txt ####
07:57:11.43 +57:08:01.4
08:40:56.62 +50:10:04.2
wait
*------ default.sex.telephoto_lens_vSTL ------*
'default.sex.telephoto_lens_vSTL' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_vSTL
./vast --norotation --noflagimage --starmatchraius 3.5 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
SExtractor catalog cache: saved Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat to cache
SExtractor catalog cache: saved Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
Creating symlink local_wcs_cache/wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
Creating symlink local_wcs_cache/wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
Creating symlink local_wcs_cache/wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.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_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits exists and is non-empty
wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits exists and is non-empty
wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits exists and is non-empty
wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits exists and is non-empty
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits (1st reference image)
verification OK: wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
Image size: 927.4'x629.8' 15.5(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.92"/pix along the Y axis
Image center: 08:28:35.075 +53:59:05.09 J2000 4789.000 3195.000
###################################
The image scale is 5.81"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.8" and 8.7"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits (1st new image)
verification OK: wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
Image size: 927.1'x629.4' 15.5(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.91"/pix along the Y axis
Image center: 08:28:50.750 +53:58:35.07 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 08:28:35.075 +53:59:05.09
Second-epoch image center 08:28:50.750 +53:58:35.07
Angular distance between the image centers 0.0393 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits (2nd new image)
verification OK: wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
Image size: 927.1'x629.5' 15.5(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.91"/pix along the Y axis
Image center: 08:28:52.791 +53:58:50.43 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 08:28:35.075 +53:59:05.09
Second-epoch image center 08:28:52.791 +53:58:50.43
Angular distance between the image centers 0.0436 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 08:28:50.750 +53:58:35.07
Second-epoch second image center 08:28:52.791 +53:58:50.43
Angular distance between the image centers 0.00657 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/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits &> /tmp/tmp.o8dGpw1i2L
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits &> /tmp/tmp.C3Jv6YVrCq
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits &> /tmp/tmp.VWWpMmGuxb
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits &> /tmp/tmp.ysDADufoPc
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
Calibrating the magnitude scale
Found non-empty wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.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_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits and wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.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_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits and wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat
Found non-empty wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits and wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat
The reference image (wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits) and catalog (wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat) found
'wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat' -> 'wcsmag.cat'
Read 60990 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 113.0237 to 142.6172 deg, Dec +47.6792 to +59.2703 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 113.0237 to 142.6172 deg, Dec 47.6792 to 59.2703 deg
Loaded 7317 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): 20 out of 25 total matches.
Matched with Tycho-2 25 out of 60990 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.056610
a=0.000000 b=1.000000 c=22.056610
From vast_summary.log: estimated ref. image limiting mag.: -7.20
Updating vast_summary.log: Estimated ref. image limiting mag.: 14.86
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 14.86
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 85 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.0 pix Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
2.0 pix Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
2.0 pix fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
2.0 pix fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
Limiting magnitude estimates:
14.9 mag. Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
14.9 mag. Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
14.6 mag. fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
14.6 mag. fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
All-image limiting magnitude estimate: 14.6 (SNR ) 14.0 (80% of stars) with default.sex.telephoto_lens_vSTL
The first estimate is the magnitude of a star detected with a signal-to-noise ratio of following Karpov (2025, Acta Polytechnica, 65, 50).
This value should be representative of the faintest stars clearly visible in the image.
The brighter of the limiting magnitude estimates for the two second-epoch images is reported here.
The second estimate is the 80th percentile of the magnitude distribution of stars detected on all four images.
This value is representative of the faintest object that may enter the candidate transients list.
The hard cut-off for the candidate transients is 15.0 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.o8dGpw1i2L (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits 569.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits' -> 'wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
WCS_IMAGE_NAME=wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
WCS-calibrated image found: wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
Checking if the catalog wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat corresponding to the image wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits alredy exist and is non-empty...
Catalog wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat corresponding to the image wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
WCS catalog name: wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=19, blended=3457, passed=60971
Got 60971 stars (including 57409 good ones) from the SExtractor catalog wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat
util/solve_plate_with_UCAC5 got 60971 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 927.4'
Seting catalog search parameters based on the expected field of view 927.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012881 (46.4 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010304 (37.1 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 172 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 142 matched stars entering correct_measured_positions(), 118 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.89"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 135 matched stars entering correct_measured_positions(), 9052 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.46"
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 218 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 192 matched stars entering correct_measured_positions(), 9088 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.40"
Accuracy estimation diagnostic: 189 matched stars entering correct_measured_positions(), 12156 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.55"
Excluding outliers - 189 stars left (next iteration limit 148)
The image catalog is written to wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits -region wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.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.C3Jv6YVrCq (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits 569.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits' -> 'wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
WCS_IMAGE_NAME=wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
WCS-calibrated image found: wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
Checking if the catalog wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat corresponding to the image wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits alredy exist and is non-empty...
Catalog wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat corresponding to the image wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
WCS catalog name: wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=24, blended=3501, passed=61060
Got 61060 stars (including 57445 good ones) from the SExtractor catalog wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat
util/solve_plate_with_UCAC5 got 61060 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 927.5'
Seting catalog search parameters based on the expected field of view 927.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012882 (46.4 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010306 (37.1 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 172 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 140 matched stars entering correct_measured_positions(), 117 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.18"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 133 matched stars entering correct_measured_positions(), 8718 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.40"
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 219 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 189 matched stars entering correct_measured_positions(), 8757 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.37"
Accuracy estimation diagnostic: 188 matched stars entering correct_measured_positions(), 12273 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.11"
Excluding outliers - 188 stars left (next iteration limit 146)
The image catalog is written to wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits -region wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.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.VWWpMmGuxb (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
WCS_IMAGE_NAME=wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
WCS-calibrated image found: wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
Checking if the catalog wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat corresponding to the image wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits alredy exist and is non-empty...
Catalog wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat corresponding to the image wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
WCS catalog name: wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=13, blended=2394, passed=53595
Got 53595 stars (including 51101 good ones) from the SExtractor catalog wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat
util/solve_plate_with_UCAC5 got 53595 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 927.1'
Seting catalog search parameters based on the expected field of view 927.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012876 (46.4 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010301 (37.1 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 202 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 172 matched stars entering correct_measured_positions(), 136 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.90"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 169 matched stars entering correct_measured_positions(), 8259 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.05"
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.3)
Done reading UCAC5 zone files...
Matched 251 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 234 matched stars entering correct_measured_positions(), 8297 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.00"
Accuracy estimation diagnostic: 230 matched stars entering correct_measured_positions(), 11039 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.24"
Excluding outliers - 230 stars left (next iteration limit 185)
The image catalog is written to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits -region wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.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.ysDADufoPc (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
WCS_IMAGE_NAME=wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
WCS-calibrated image found: wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
Checking if the catalog wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat corresponding to the image wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits alredy exist and is non-empty...
Catalog wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat corresponding to the image wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
WCS catalog name: wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=14, blended=2369, passed=53508
Got 53508 stars (including 51027 good ones) from the SExtractor catalog wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat
util/solve_plate_with_UCAC5 got 53508 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 927.1'
Seting catalog search parameters based on the expected field of view 927.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012876 (46.4 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010301 (37.1 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 198 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 166 matched stars entering correct_measured_positions(), 140 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.62"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 164 matched stars entering correct_measured_positions(), 8391 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.02"
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.3)
Done reading UCAC5 zone files...
Matched 251 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 229 matched stars entering correct_measured_positions(), 8427 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.96"
Accuracy estimation diagnostic: 227 matched stars entering correct_measured_positions(), 11189 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.09"
Excluding outliers - 227 stars left (next iteration limit 180)
The image catalog is written to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits -region wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.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_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/wcs_Lyn-02-Q1b1x1_2026-01-18_01-30-34_20.00sec_-15.00C_LIGHT_0318.fits
Saving fully-calibrated image wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/wcs_Lyn-02-Q1b1x1_2026-01-18_01-31-17_20.00sec_-15.00C_LIGHT_0319.fits
Saving fully-calibrated image wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-41-34_20.00sec_-5.00C_LIGHTs_0384.fits
Saving fully-calibrated image wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Lyn-02-Q1b1x1_004336_TTUQ1b1x1_1191510_gAdGJKZH/wcs_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385.fits
Preparing the HTML report for the field Lyn-02-Q1b1x1 with default.sex.telephoto_lens_vSTL
Adding exclusion_list_local.txt__out11108.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75415.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75419.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75422.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75428.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75441.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75461.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75474.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75475.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75480.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75496.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75506.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75522.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75561.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75562.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75572.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75573.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75581.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75599.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75601.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75615.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75633.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75636.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75641.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75676.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75691.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75750.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75755.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75756.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75773.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75774.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75782.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75841.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75860.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75872.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75884.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75904.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75932.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 63s
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: 25s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75393_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75393_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75394_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75394_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75407_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75407_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75415_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75415_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75417_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75417_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75418_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75418_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75419_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75419_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75422_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75422_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75428_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75428_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75441_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75441_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75461_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75461_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75468_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75468_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75474_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75474_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75475_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75475_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75476_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75476_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (27.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75480_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75480_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75489_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75489_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75496_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75496_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75506_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75506_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75522_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75522_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75550_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75550_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75561_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75561_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75562_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75562_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75568_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75568_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75572_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75572_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75573_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75573_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75581_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75581_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75583_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75583_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75590_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75590_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75599_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75599_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75601_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75601_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75608_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75608_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75615_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75615_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75633_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75633_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75636_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75636_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75641_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75641_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75661_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75661_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75676_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75676_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75677_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75677_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75691_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75691_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75698_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75698_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75703_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75703_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (8.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75734_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75734_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75738_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75738_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75750_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75750_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75752_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75752_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75755_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75755_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75756_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75756_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75773_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75773_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75774_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75774_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75775_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75775_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75782_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75782_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75783_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75783_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75798_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75798_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75800_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75800_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75806_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75806_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75824_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75824_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75828_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75828_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75835_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75835_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75836_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75836_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (27.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75838_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75838_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75841_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75841_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75842_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75842_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75850_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75850_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75860_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75860_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75872_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75872_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75876_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75876_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75884_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75884_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75887_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75887_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75898_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75898_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75903_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75903_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75904_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75904_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75910_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75910_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75922_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75922_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75929_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75929_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75932_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 75932_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75939_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75939_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75945_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75945_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75950_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75950_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75958_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75958_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75970_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75970_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75972_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75972_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75980_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 75980_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 48804_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
The candidate 48804_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385 did not pass the final checks
**** FOUND 08:40:56.70 +50:10:01.8 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 11108_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
Preparing report for the candidate 11108_fd_Lyn-02-Q1b1x1_2026-04-19_00-42-32_20.00sec_-4.90C_LIGHTs_0385
make_report_in_HTML.sh Phase 2 (HTML assembly): 3s
make_report_in_HTML.sh TOTAL: 91s
Prepared the HTML report for the field Lyn-02-Q1b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
07:57:11.43 +57:08:01.4
08:40:56.62 +50:10:04.2
07:57:12.13 +57:07:54.5
08:13:53.74 +53:09:19.3
08:34:08.68 +56:21:25.9
07:53:10.71 +49:29:37.8
07:42:29.44 +49:38:02.3
08:14:45.73 +49:29:04.1
08:11:03.22 +55:44:38.5
08:09:31.32 +51:34:29.7
08:16:37.78 +50:49:31.6
08:10:27.68 +55:08:17.2
08:09:25.03 +49:07:06.4
08:02:28.87 +54:25:44.1
07:56:41.62 +53:33:42.0
08:25:38.54 +54:29:02.1
09:17:21.38 +56:27:13.0
08:19:32.18 +54:39:13.0
08:14:08.25 +52:33:51.4
08:05:48.33 +53:40:22.6
08:40:00.77 +56:09:18.5
08:28:55.35 +56:45:53.3
08:17:58.52 +58:54:22.9
09:16:34.24 +56:00:15.0
07:43:23.34 +51:22:53.7
08:28:27.06 +58:40:09.3
08:47:19.03 +55:11:00.3
08:27:30.95 +49:37:26.4
08:15:51.77 +54:58:19.3
08:30:39.11 +54:27:34.7
08:26:17.15 +57:54:41.4
08:07:43.16 +54:20:07.5
08:01:15.75 +53:13:42.1
08:23:27.30 +53:03:44.6
08:51:44.76 +55:58:46.2
08:59:49.81 +50:48:56.0
07:45:56.90 +51:43:44.7
09:08:03.43 +50:22:54.1
08:31:33.27 +58:51:50.5
08:28:40.11 +54:41:25.4
########### Completed Lyn-02-Q1b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ1.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
08:40:56.62 +50:10:04.2
07:57:11.43 +57:08:01.4
08:13:53.74 +53:09:19.3
08:34:08.68 +56:21:25.9
07:53:10.71 +49:29:37.8
07:42:29.44 +49:38:02.3
08:14:45.73 +49:29:04.1
08:11:03.22 +55:44:38.5
08:09:31.32 +51:34:29.7
08:16:37.78 +50:49:31.6
08:10:27.68 +55:08:17.2
08:09:25.03 +49:07:06.4
08:02:28.87 +54:25:44.1
07:56:41.62 +53:33:42.0
08:25:38.54 +54:29:02.1
09:17:21.38 +56:27:13.0
08:19:32.18 +54:39:13.0
08:14:08.25 +52:33:51.4
08:05:48.33 +53:40:22.6
08:40:00.77 +56:09:18.5
08:28:55.35 +56:45:53.3
08:17:58.52 +58:54:22.9
09:16:34.24 +56:00:15.0
07:43:23.34 +51:22:53.7
08:28:27.06 +58:40:09.3
08:47:19.03 +55:11:00.3
08:27:30.95 +49:37:26.4
08:15:51.77 +54:58:19.3
08:30:39.11 +54:27:34.7
08:26:17.15 +57:54:41.4
08:07:43.16 +54:20:07.5
08:01:15.75 +53:13:42.1
08:23:27.30 +53:03:44.6
08:51:44.76 +55:58:46.2
08:59:49.81 +50:48:56.0
07:45:56.90 +51:43:44.7
09:08:03.43 +50:22:54.1
08:31:33.27 +58:51:50.5
08:28:40.11 +54:41:25.4
07:57:12.13 +57:07:54.5
###################################################################################
08:40:56.62 +50:10:04.2 -- not an asteroid (will add it to exclusion list)
07:57:11.43 +57:08:01.4 -- not an asteroid (will add it to exclusion list)
08:13:53.74 +53:09:19.3 -- not an asteroid (will add it to exclusion list)
08:34:08.68 +56:21:25.9 -- not an asteroid (will add it to exclusion list)
07:53:10.71 +49:29:37.8 -- not an asteroid (will add it to exclusion list)
07:42:29.44 +49:38:02.3 -- not an asteroid (will add it to exclusion list)
08:14:45.73 +49:29:04.1 -- not an asteroid (will add it to exclusion list)
08:11:03.22 +55:44:38.5 -- not an asteroid (will add it to exclusion list)
08:09:31.32 +51:34:29.7 -- not an asteroid (will add it to exclusion list)
08:16:37.78 +50:49:31.6 -- not an asteroid (will add it to exclusion list)
08:10:27.68 +55:08:17.2 -- not an asteroid (will add it to exclusion list)
08:09:25.03 +49:07:06.4 -- not an asteroid (will add it to exclusion list)
08:02:28.87 +54:25:44.1 -- not an asteroid (will add it to exclusion list)
07:56:41.62 +53:33:42.0 -- not an asteroid (will add it to exclusion list)
08:25:38.54 +54:29:02.1 -- not an asteroid (will add it to exclusion list)
09:17:21.38 +56:27:13.0 -- not an asteroid (will add it to exclusion list)
08:19:32.18 +54:39:13.0 -- not an asteroid (will add it to exclusion list)
08:14:08.25 +52:33:51.4 -- not an asteroid (will add it to exclusion list)
08:05:48.33 +53:40:22.6 -- not an asteroid (will add it to exclusion list)
08:40:00.77 +56:09:18.5 -- not an asteroid (will add it to exclusion list)
08:28:55.35 +56:45:53.3 -- not an asteroid (will add it to exclusion list)
08:17:58.52 +58:54:22.9 -- not an asteroid (will add it to exclusion list)
09:16:34.24 +56:00:15.0 -- not an asteroid (will add it to exclusion list)
07:43:23.34 +51:22:53.7 -- not an asteroid (will add it to exclusion list)
08:28:27.06 +58:40:09.3 -- not an asteroid (will add it to exclusion list)
08:47:19.03 +55:11:00.3 -- not an asteroid (will add it to exclusion list)
08:27:30.95 +49:37:26.4 -- not an asteroid (will add it to exclusion list)
08:15:51.77 +54:58:19.3 -- not an asteroid (will add it to exclusion list)
08:30:39.11 +54:27:34.7 -- not an asteroid (will add it to exclusion list)
08:26:17.15 +57:54:41.4 -- not an asteroid (will add it to exclusion list)
08:07:43.16 +54:20:07.5 -- not an asteroid (will add it to exclusion list)
08:01:15.75 +53:13:42.1 -- not an asteroid (will add it to exclusion list)
08:23:27.30 +53:03:44.6 -- not an asteroid (will add it to exclusion list)
08:51:44.76 +55:58:46.2 -- not an asteroid (will add it to exclusion list)
08:59:49.81 +50:48:56.0 -- not an asteroid (will add it to exclusion list)
07:45:56.90 +51:43:44.7 -- not an asteroid (will add it to exclusion list)
09:08:03.43 +50:22:54.1 -- not an asteroid (will add it to exclusion list)
08:31:33.27 +58:51:50.5 -- not an asteroid (will add it to exclusion list)
08:28:40.11 +54:41:25.4 -- not an asteroid (will add it to exclusion list)
07:57:12.13 +57:07:54.5 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
07:42:29.44 +49:38:02.3 -- does not seem to be a hot pixel (will add it to exclusion list)
07:43:23.34 +51:22:53.7 -- does not seem to be a hot pixel (will add it to exclusion list)
07:45:56.90 +51:43:44.7 -- does not seem to be a hot pixel (will add it to exclusion list)
07:53:10.71 +49:29:37.8 -- does not seem to be a hot pixel (will add it to exclusion list)
07:56:41.62 +53:33:42.0 -- does not seem to be a hot pixel (will add it to exclusion list)
07:57:11.43 +57:08:01.4 -- does not seem to be a hot pixel (will add it to exclusion list)
07:57:12.13 +57:07:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
08:01:15.75 +53:13:42.1 -- does not seem to be a hot pixel (will add it to exclusion list)
08:02:28.87 +54:25:44.1 -- does not seem to be a hot pixel (will add it to exclusion list)
08:05:48.33 +53:40:22.6 -- does not seem to be a hot pixel (will add it to exclusion list)
08:07:43.16 +54:20:07.5 -- does not seem to be a hot pixel (will add it to exclusion list)
08:09:25.03 +49:07:06.4 -- does not seem to be a hot pixel (will add it to exclusion list)
08:09:31.32 +51:34:29.7 -- does not seem to be a hot pixel (will add it to exclusion list)
08:10:27.68 +55:08:17.2 -- does not seem to be a hot pixel (will add it to exclusion list)
08:11:03.22 +55:44:38.5 -- does not seem to be a hot pixel (will add it to exclusion list)
08:13:53.74 +53:09:19.3 -- does not seem to be a hot pixel (will add it to exclusion list)
08:14:08.25 +52:33:51.4 -- does not seem to be a hot pixel (will add it to exclusion list)
08:14:45.73 +49:29:04.1 -- does not seem to be a hot pixel (will add it to exclusion list)
08:15:51.77 +54:58:19.3 -- does not seem to be a hot pixel (will add it to exclusion list)
08:16:37.78 +50:49:31.6 -- does not seem to be a hot pixel (will add it to exclusion list)
08:17:58.52 +58:54:22.9 -- does not seem to be a hot pixel (will add it to exclusion list)
08:19:32.18 +54:39:13.0 -- does not seem to be a hot pixel (will add it to exclusion list)
08:23:27.30 +53:03:44.6 -- does not seem to be a hot pixel (will add it to exclusion list)
08:25:38.54 +54:29:02.1 -- does not seem to be a hot pixel (will add it to exclusion list)
08:26:17.15 +57:54:41.4 -- does not seem to be a hot pixel (will add it to exclusion list)
08:27:30.95 +49:37:26.4 -- does not seem to be a hot pixel (will add it to exclusion list)
08:28:27.06 +58:40:09.3 -- does not seem to be a hot pixel (will add it to exclusion list)
08:28:40.11 +54:41:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
08:28:55.35 +56:45:53.3 -- does not seem to be a hot pixel (will add it to exclusion list)
08:30:39.11 +54:27:34.7 -- does not seem to be a hot pixel (will add it to exclusion list)
08:31:33.27 +58:51:50.5 -- does not seem to be a hot pixel (will add it to exclusion list)
08:34:08.68 +56:21:25.9 -- does not seem to be a hot pixel (will add it to exclusion list)
08:40:00.77 +56:09:18.5 -- does not seem to be a hot pixel (will add it to exclusion list)
08:40:56.62 +50:10:04.2 -- does not seem to be a hot pixel (will add it to exclusion list)
08:47:19.03 +55:11:00.3 -- does not seem to be a hot pixel (will add it to exclusion list)
08:51:44.76 +55:58:46.2 -- does not seem to be a hot pixel (will add it to exclusion list)
08:59:49.81 +50:48:56.0 -- does not seem to be a hot pixel (will add it to exclusion list)
09:08:03.43 +50:22:54.1 -- does not seem to be a hot pixel (will add it to exclusion list)
09:16:34.24 +56:00:15.0 -- does not seem to be a hot pixel (will add it to exclusion list)
09:17:21.38 +56:27:13.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)
07:42:29.44 +49:38:02.3 -- not a known variable star
07:43:23.34 +51:22:53.7 -- not a known variable star
07:45:56.90 +51:43:44.7 -- not a known variable star
07:53:10.71 +49:29:37.8 -- not a known variable star
07:56:41.62 +53:33:42.0 -- not a known variable star
07:57:11.43 +57:08:01.4 -- not a known variable star
07:57:12.13 +57:07:54.5 -- not a known variable star
08:01:15.75 +53:13:42.1 -- not a known variable star
08:02:28.87 +54:25:44.1 -- not a known variable star
08:05:48.33 +53:40:22.6 -- not a known variable star
08:07:43.16 +54:20:07.5 -- not a known variable star
08:09:25.03 +49:07:06.4 -- not a known variable star
08:09:31.32 +51:34:29.7 -- not a known variable star
08:10:27.68 +55:08:17.2 -- not a known variable star
08:11:03.22 +55:44:38.5 -- not a known variable star
08:13:53.74 +53:09:19.3 -- not a known variable star
08:14:08.25 +52:33:51.4 -- not a known variable star
08:14:45.73 +49:29:04.1 -- not a known variable star
08:15:51.77 +54:58:19.3 -- not a known variable star
08:16:37.78 +50:49:31.6 -- not a known variable star
08:17:58.52 +58:54:22.9 -- not a known variable star
08:19:32.18 +54:39:13.0 -- not a known variable star
08:23:27.30 +53:03:44.6 -- not a known variable star
08:25:38.54 +54:29:02.1 -- not a known variable star
08:26:17.15 +57:54:41.4 -- not a known variable star
08:27:30.95 +49:37:26.4 -- not a known variable star
08:28:27.06 +58:40:09.3 -- not a known variable star
08:28:40.11 +54:41:25.4 -- not a known variable star
08:28:55.35 +56:45:53.3 -- not a known variable star
08:30:39.11 +54:27:34.7 -- not a known variable star
08:31:33.27 +58:51:50.5 -- not a known variable star
08:34:08.68 +56:21:25.9 -- not a known variable star
08:40:00.77 +56:09:18.5 -- not a known variable star
08:40:56.62 +50:10:04.2 -- not a known variable star
08:47:19.03 +55:11:00.3 -- not a known variable star
08:51:44.76 +55:58:46.2 -- not a known variable star
08:59:49.81 +50:48:56.0 -- not a known variable star
09:08:03.43 +50:22:54.1 -- not a known variable star
09:16:34.24 +56:00:15.0 -- not a known variable star
09:17:21.38 +56:27:13.0 -- not a known variable star
Found 40 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
40 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
###################################################################################
exclusion_list_gaiadr2.txt NOT FOUND
exclusion_list_apass.txt NOT FOUND
IS_THIS_TEST_RUN= NO ALLOW_EXCLUSION_LIST_UPDATE= YES
#### Adding the following to the exclusion list ####
07:42:29.44 +49:38:02.3
07:43:23.34 +51:22:53.7
07:45:56.90 +51:43:44.7
07:53:10.71 +49:29:37.8
07:56:41.62 +53:33:42.0
07:57:11.43 +57:08:01.4
07:57:12.13 +57:07:54.5
08:01:15.75 +53:13:42.1
08:02:28.87 +54:25:44.1
08:05:48.33 +53:40:22.6
08:07:43.16 +54:20:07.5
08:09:25.03 +49:07:06.4
08:09:31.32 +51:34:29.7
08:10:27.68 +55:08:17.2
08:11:03.22 +55:44:38.5
08:13:53.74 +53:09:19.3
08:14:08.25 +52:33:51.4
08:14:45.73 +49:29:04.1
08:15:51.77 +54:58:19.3
08:16:37.78 +50:49:31.6
08:17:58.52 +58:54:22.9
08:19:32.18 +54:39:13.0
08:23:27.30 +53:03:44.6
08:25:38.54 +54:29:02.1
08:26:17.15 +57:54:41.4
08:27:30.95 +49:37:26.4
08:28:27.06 +58:40:09.3
08:28:40.11 +54:41:25.4
08:28:55.35 +56:45:53.3
08:30:39.11 +54:27:34.7
08:31:33.27 +58:51:50.5
08:34:08.68 +56:21:25.9
08:40:00.77 +56:09:18.5
08:40:56.62 +50:10:04.2
08:47:19.03 +55:11:00.3
08:51:44.76 +55:58:46.2
08:59:49.81 +50:48:56.0
09:08:03.43 +50:22:54.1
09:16:34.24 +56:00:15.0
09:17:21.38 +56:27:13.0
####################################################
The observatory MPC code is V36
############################################################
Positions of planets computed with util/planet_finder/main.py for JD(UT)2461149.73732584 -observatory V36
00:24:53.83 -00:10:25.3 Mercury (-0.1mag)
03:24:34.44 +19:01:45.9 Venus (-3.9mag)
00:27:01.81 +01:52:25.8 Mars (1.2mag)
07:14:09.39 +22:43:41.3 Jupiter (-2.1mag)
00:30:36.96 +00:57:53.9 Saturn (0.9mag)
03:48:23.26 +19:49:40.9 Uranus (5.8mag)
00:11:15.56 -00:12:44.2 Neptune (7.8mag)
20:33:53.15 -22:52:47.1 Pluto (14.5mag)
03:14:42.49 +22:33:26.5 Moon (-8.7mag)
-rw-r--r-- 1 apache apache 362 Apr 19 00:45 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461149.73732584:
07:14:02.09 +22:43:57.1 Io (5.8mag)
07:14:05.67 +22:43:52.0 Europa (5.9mag)
07:13:50.27 +22:44:22.7 Ganymede (5.4mag)
07:14:24.17 +22:43:01.8 Callisto (6.6mag)
07:17:20.77 +22:29:51.2 Himalia (15.4mag)
07:14:13.68 +22:43:32.1 Thebe (16.2mag)
07:17:36.13 +23:00:10.9 Elara (17.3mag)
07:13:15.49 +23:22:00.0 Pasiphae (17.4mag)
07:22:24.65 +22:42:00.8 Carme (18.5mag)
00:30:27.95 +00:58:15.3 Titan (8.8mag)
00:30:35.69 +00:58:10.1 Rhea (10.1mag)
00:30:12.12 +00:57:32.1 Iapetus (11.5mag)
00:30:32.74 +00:58:21.9 Hyperion (14.8mag)
00:32:11.23 +01:06:20.8 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 19 00:45 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461149.73732584:
15:51:48.95 -18:27:20.1 JWST
16:27:32.04 +49:26:02.1 Chandra
18:03:55.30 -37:04:54.7 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 19 00:45 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461149.73732584 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:53:12.39 -28:58:24.1 13.9mag P/2010 H2 (Vales)
05:09:06.44 -69:30:42.6 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:33:10.54 +31:27:36.3 17.2mag C/2017 K2 (PANSTARRS)
17:30:03.57 +10:55:39.9 17.6mag C/2021 G2 (ATLAS)
23:11:02.73 +29:21:37.6 17.1mag C/2022 E2 (ATLAS)
04:33:01.89 +26:07:29.0 16.0mag C/2022 N2 (PANSTARRS)
09:04:11.28 +32:01:47.7 16.2mag C/2022 QE78 (ATLAS)
08:31:37.58 +00:10:59.8 17.4mag C/2022 R6 (PANSTARRS)
18:52:53.98 +18:48:03.8 17.6mag C/2023 A3 (Tsuchinshan-ATLAS)
15:39:35.05 -11:28:26.2 17.5mag P/2023 B1 (PANSTARRS)
09:06:13.57 -11:22:22.3 17.7mag C/2023 F3 (ATLAS)
21:57:20.36 +63:06:03.3 17.5mag C/2023 H5 (Lemmon)
19:16:13.00 -03:47:31.4 14.1mag C/2023 R1 (PANSTARRS)
21:24:08.06 +86:21:54.0 17.8mag C/2023 X2 (Lemmon)
06:19:33.45 +63:30:09.6 17.2mag C/2024 A1 (ATLAS)
05:20:05.38 +19:19:49.3 11.3mag C/2024 E1 (Wierzchos)
16:17:07.98 +06:55:07.6 17.4mag C/2024 G6 (ATLAS)
20:21:38.49 +16:09:48.2 14.6mag C/2024 J3 (ATLAS)
03:29:18.12 -21:53:58.0 16.3mag C/2024 T5 (ATLAS)
05:19:29.74 +44:30:06.0 17.7mag C/2025 J1 (Borisov)
13:25:30.66 +47:23:40.4 15.3mag C/2025 L1 (ATLAS)
03:30:28.65 -26:43:39.9 17.9mag C/2025 Q3 (ATLAS)
00:19:09.85 +16:57:42.5 8.1mag C/2025 R3 (PANSTARRS)
12:52:43.75 +03:12:17.3 17.4mag C/2025 Y1 (ATLAS)
03:51:54.52 +02:19:36.9 14.2mag C/2026 A1 (MAPS)
00:08:37.71 +37:47:37.2 14.7mag C/2026 B2 (Sun-Gao)
18:49:13.73 -09:32:36.8 11.6mag 10P/Tempel
14:55:53.30 +02:51:19.3 14.3mag 24P/Schaumasse
11:01:59.41 -01:25:32.2 15.7mag 29P/Schwassmann-Wachmann
10:37:33.64 -03:51:12.1 17.0mag 43P/Wolf-Harrington
01:53:41.64 +18:02:09.3 17.3mag 47P/Ashbrook-Jackson
07:16:49.43 +36:18:37.4 17.0mag 63P/Wild
23:33:08.95 -11:03:59.1 15.7mag 65P/Gunn
04:11:59.63 +22:20:40.5 15.9mag 76P/West-Kohoutek-Ikemura
01:12:45.78 +08:51:41.0 14.3mag 78P/Gehrels
23:12:41.95 -08:25:59.4 14.7mag 88P/Howell
02:19:38.51 +21:29:28.7 15.1mag 93P/Lovas
05:00:59.58 +32:27:13.9 16.2mag 123P/West-Hartley
08:32:18.64 +36:52:09.6 16.2mag 124P/Mrkos
02:38:14.57 +14:43:39.4 16.4mag 128P/Shoemaker-Holt
02:53:54.28 +14:52:51.3 17.5mag 131P/Mueller
01:43:19.67 +14:18:45.3 10.5mag 141P/Machholz
01:51:45.61 +06:04:52.3 10.5mag 141P-A/Machholz
00:35:36.45 +01:53:34.6 12.4mag 141P-D/Machholz
02:22:17.58 +07:50:11.7 17.9mag 141P-I/Machholz
01:11:26.13 +00:06:25.7 15.0mag 162P/SidingSpring
14:45:42.46 +00:14:44.2 17.7mag 210P/Christensen
21:47:59.80 -10:40:21.9 17.7mag 218P/LINEAR
17:17:09.92 -13:32:24.6 16.1mag 235P/LINEAR
05:41:31.39 +34:55:45.0 16.8mag 240P/NEAT
07:40:09.48 -04:49:33.0 17.8mag 242P/Spahr
22:25:00.53 -20:05:58.9 17.8mag 260P/McNaught
02:04:51.31 +21:16:14.6 18.0mag 295P/LINEAR
15:41:19.01 +07:11:50.0 17.5mag 391P/Kowalski
07:35:30.44 +21:22:20.7 17.7mag 450P/LONEOS
05:40:38.53 +44:50:36.5 17.5mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.8K Apr 19 00:45 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
14:49:14.13 -27:29:20.60 ASASSN-26cu 2026-04-16.06 14.03
17:21:59.44 -38:54:04.60 ASASSN-26ct 2026-04-14.4 15.15
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
14:49:14.13 -27:29:20.60 2026-04-16.06 14.03
12:23:20.40 +04:53:39.10 AT2026ixd 2026-04-12.14 17.65
17:46:09.76 -61:19:50.40 SN2026icy 2026-04-12.2 17.03
09:25:46.42 +02:13:46.30 SN2026gud 2026-04-11.98 16.49
16:52:15.46 -60:27:45.90 ASASSN-26cs 2026-04-12.4 15.5
04:20:55.37 -51:15:31.10 ASASSN-26cr 2026-04-12.01 15.37
22:25:39.35 +36:45:06.90 AT2026ihl 2026-04-10.48 14.21
19:40:44.94 +00:41:03.80 AT2026imw 2026-04-10.32 16.06
19:52:04.70 +05:53:33.50 ASASSN-26cq 2026-04-9.31 14.98
16:08:18.39 -64:11:08.80 ASASSN-26cp 2026-04-9.29 13.32
09:22:22.90 -61:02:43.70 SN2026idh 2026-04-7.97 16.34
05:06:54.12 -19:42:26.40 AT2026imr 2026-04-8 17.49
07:14:55.34 -36:03:21.40 AT2026hei 2026-04-8.12 16.7
21:35:33.14 -19:01:34.80 AT2026ihm 2026-04-8.36 16.7
04:28:24.08 -32:25:35.30 AT2026imo 2026-04-8.02 16.81
05:10:35.79 -39:38:40.80 SN 2026hnn 2026-04-7.04 17.07
09:54:32.04 -01:17:25.80 ASASSN-26cn 2026-04-7.01 15.58
07:46:24.43 -77:29:36.30 ASASSN-26co 2026-04-7.15 15.11
05:00:45.52 -29:51:06.20 AT2026hvw 2026-04-6.03 16.51
19:49:33.10 -23:37:11.00 ASASSN-26cl 2026-04-5.29 14.98
19:32:43.55 -22:39:33.40 ASASSN-26cm 2026-04-4.3 13.88
18:08:57.38 +76:48:23.60 ASASSN-26ck 2026-04-2.37 15.38
16:16:36.10 +44:52:30.20 AT2026hyy 2026-04-2.58 13.81
21:55:23.31 -34:48:53.90 ASASSN-26cj 2026-03-30.4 -1.47
11:19:50.81 -27:51:50.40 SN2026gvk 2026-03-30 15.28
11:53:57.02 -23:09:46.20 SN2026gzx 2026-03-28.75 15.27
07:13:46.14 -33:10:15.70 ASASSN-26ci 2026-03-28.15 15.14
09:03:36.09 -67:58:13.00 SN2026hkg 2026-03-28.19 15.82
07:03:00.72 +39:14:43.00 SN2026fin 2026-03-28.27 15.82
05:35:42.79 -63:44:05.60 ASASSN-26ch 2026-03-28.12 13.14
11:23:19.04 +34:22:38.00 SN2026fwt 2026-03-27.3 16.56
19:03:49.79 +37:04:05.20 ASASSN-26ce 2026-03-26.56 16.3
20:26:56.07 -52:54:06.50 AT2026hiy 2026-03-26.35 16.95
05:25:54.76 -30:15:35.80 ASASSN-26cg 2026-03-25.07 16.88
06:57:16.49 -26:54:37.20 SN2026fzb 2026-03-25.14 15.8
14:37:38.23 -43:00:52.30 ASASSN-26cd 2026-03-24.24 12.52
17:34:53.03 +06:04:29.70 AT2026gzl 2026-03-23.27 15.82
08:30:02.60 -35:12:47.50 ASASSN-26cf 2026-03-23.2 14.82
16:54:25.33 +37:49:56.60 SN 2026evz 2026-03-21.32 17.54
17:06:19.20 -18:54:19.50 ASASSN-26bx 2026-03-21.25 16.39
19:01:16.28 -29:29:23.10 ASASSN-26bw 2026-03-21.33 15.81
08:46:05.75 +10:47:39.80 ASASSN-26ca 2026-03-21.13 14.27
12:14:58.16 +63:47:16.20 SN 2026fvx 2026-03-21.12 15.6
18:02:55.90 -75:23:02.60 ASASSN-26bz 2026-03-21.32 16.16
12:16:02.87 -53:16:33.70 ASASSN-26cc 2026-03-20.08 3.93
13:08:21.85 +29:13:44.20 SN 2026fmh 2026-03-20.16 -0.33
19:56:38.48 -34:45:21.50 ASASSN-26cb 2026-03-20.35 -3.26
14:32:41.15 -41:38:48.50 ASASSN-26by 2026-03-20.15 -1.31
13:00:42.99 +37:18:34.60 SN2026fjc 2026-03-19.5 15.97
06:02:44.21 -04:11:06.20 ASASSN-26bv 2026-03-19.19 15.67
12:20:27.90 -45:55:38.40 ASASSN-26bt 2026-03-19.05 16.24
07:49:57.30 -56:14:35.10 ASASSN-26bu 2026-03-19.19 15.74
06:04:29.75 +53:23:34.00 SN 2026eza 2026-03-18.2 17.48
11:54:57.87 +69:19:28.90 AT2026fsf 2026-03-18.14 16.95
10:44:46.95 +58:27:29.30 SN 2026enn 2026-03-18.13 17.53
20:45:54.04 -73:26:43.00 AT 2026ezy 2026-03-18.13 16.83
06:53:18.10 -59:10:49.30 ASASSN-26bs 2026-03-18.02 16.93
07:45:09.29 -62:14:36.20 ASASSN-26br 2026-03-16.16 16.78
19:24:27.93 -52:04:36.40 AT 2023uk 2026-03-16.35 14.2
04:52:54.50 -15:20:57.10 AT2026fhw 2026-03-14.06 SDSS
11:10:34.24 +02:58:48.10 SN2026drr 2026-03-14.08 0.2
07:26:45.73 -27:45:13.90 ASASSN-26bo 2026-03-14.17 13.8
16:35:46.94 +58:12:28.40 SN2026ebt 2026-03-12.41 17.12
13:01:19.45 +15:42:15.00 SN2026ehe 2026-03-12.11 -0.29
09:15:55.41 +10:08:09.70 SN2026efq 2026-03-12.16 0.06
03:31:20.92 -35:29:29.00 SN2026evh 2026-03-12.05 17.29
06:26:19.15 -85:18:28.10 AT2026ffp 2026-03-12.16 0.37
14:16:42.30 -41:18:36.50 AT2026fij 2026-03-12.05 15.97
10:45:04.71 +00:06:13.10 SN 2026exe 2026-03-11.78 16.48
18:07:45.58 +69:43:01.00 SN2026ess 2026-03-12.37 17.37
13:11:03.58 +49:06:31.80 AT2026ewa 2026-03-12.42 16.77
15:03:25.23 -63:11:22.20 ASASSN-26bp 2026-03-11.92 13.33
13:09:37.25 -35:50:25.20 AT2024cmo 2026-03-11.12 16.29
13:06:01.97 -15:50:14.40 AT2026fdy 2026-03-10.33 16.68
11:30:09.67 -47:26:43.70 ASASSN-26bn 2026-03-10.12 15.2
05:03:25.25 -24:16:50.40 (= Gaia 2026-03-9.09 14.32
03:42:32.53 -04:17:53.70 ASASSN-26bm 2026-03-8.04 15.22
04:31:00.53 -68:29:50.20 ASASSN-26bl 2026-03-7.9 10.26
16:18:17.61 +41:25:11.40 SN 2026dkf 2026-03-6.31 16.7
13:45:00.35 +61:16:50.90 SN 2026ejl 2026-03-6.41 -0.66
09:27:45.48 -37:49:32.80 ASASSN-26bk 2026-03-2.3 13.11
20:22:01.20 +23:47:47.30 ASASSN-26bi 2026-02-28.51 15.86
11:16:22.10 +29:26:22.80 AT2026enm 2026-02-28.39 16.88
08:05:59.83 -48:39:35.60 ASASSN-26bh 2026-02-26.05 14.64
13:24:27.02 -45:57:01.40 ASASSN-26bg 2026-02-26.35 15.28
17:27:50.95 -68:28:46.40 ASASSN-26bf 2026-02-26.3 16.28
18:03:39.37 +19:58:46.70 ASASSN-26be 2026-02-25.58 14.8
17:40:18.19 +07:20:59.60 SN 2026crm 2026-02-24.34 16.9
18:38:36.11 -79:28:58.40 ASASSN-26bb 2026-02-24.36 16.11
17:43:29.75 +11:24:00.60 ASASSN-26bc 2026-02-23.37 -3.37
16:59:41.08 -80:01:51.20 ASASSN-26bd 2026-02-23.3 14.38
11:23:31.77 -08:39:15.40 SN2026cff 2026-02-23.15 -1.08
14:55:17.39 -05:56:05.30 SN2026dmk 2026-02-23.22 -0.76
12:28:15.19 +44:27:20.80 SN2026cjz 2026-02-23.47 15.62
12:12:29.55 -02:40:43.30 AT2026dsk 2026-02-23.4 17.21
09:21:05.29 +06:11:42.80 SN2026chr 2026-02-23.1 17.39
16:05:38.61 +18:06:07.40 SN 2026dsy 2026-02-23.36 17.15
-rw-r--r-- 1 apache apache 5.8K Apr 19 00:45 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
09:54:46.47 +69:06:31.7 PNV J09544647+6906317 2026-01-26.8081 19.3mag
18:08:51.99 -26:16:21.9 TCP J18085199-2616219 2026-01-31.8519 12.2mag
08:01:11.02 -03:43:14.1 TCP J08011102-0343141 2026-02-08.8090 15.10Cmag
05:19:15.40 -02:04:51.5 TCP J05191540-0204515 2026-02-13.4306 14.5mag
10:52:41.26 +36:40:08.9 TCP J10524126+3640089 2026-02-17.6065 17.4mag
05:50:50.81 +36:22:45.1 TCP J05505081+3622451 2026-02-17.5511 15.7mag
00:42:51.33 +41:13:49.1 PNV J00425133+4113491 2026-02-20.738 18.3mag
00:43:04.88 +41:29:41.4 PNV J00430488+4129414 2026-02-20.5923 18.84Cmag
17:43:29.74 +11:24:00.3 TCP J17432974+1124003 2026-02-22.3773 13.6mag
09:55:01.59 +69:08:42.7 PNV J09550159+6908427 2026-02-20.893 19.0mag
07:03:25.76 -12:41:40.1 TCP J07032576-1241401 2026-03-10.4268 15.4mag
00:42:36.82 +41:16:05.8 PNV J00423682+4116058 2026-03-12.5744 17.24Cmag
07:26:45.79 -27:45:14.1 TCP J07264579-2745141 2026-03-17.4417 14.8mag
17:57:19.56 -28:08:14.7 TCP J17571956-2808147 2026-03-19.7972 14.5mag
08:46:05.73 +10:47:39.7 TCP J08460573+1047397 2026-03-21.1936 14.5mag
09:55:38.83 +69:05:21.7 PNV J09553883+6905217 2026-04-01.893 19.4mag
19:32:43.67 -22:39:30.7 TCP J19324367-2239307 2026-04-05.4395 13.6mag
16:16:36.03 +44:52:28.9 TCP J16163603+4452289 2026-04-05.6655 14.2mag
00:43:38.36 +41:15:32.4 PNV J00433836+4115324 2026-04-08.079 17.2mag
15:41:11.68 +59:18:26.8 TCP J15411168+5918268 2026-04-12.9625 19.2mag
-rw-r--r-- 1 apache apache 188K Apr 19 00:45 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
17:08:30.580 +41:56:13.61 AT 2026jje 2026-04-03.89 21.47
16:48:25.780 +33:00:44.35 AT 2026jjd 2026-04-03.85 21.29
16:46:02.450 +30:55:42.15 AT 2026jjc 2026-04-03.80 19.57
16:51:04.120 +44:26:50.06 AT 2026jjb 2026-03-30.84 21.02
12:10:02.030 +43:26:37.06 AT 2026jja 2026-03-28.87 21.46
17:56:59.910 +48:20:04.31 AT 2026jiz 2026-03-27.87 20.99
15:23:12.550 +15:30:01.81 AT 2026jiy 2026-03-27.82 21.09
12:45:41.400 +53:52:15.13 AT 2026jix 2026-03-24.70 20.56
12:05:28.040 +47:18:05.03 AT 2026jiw 2026-03-24.69 20.17
12:49:49.680 +44:27:28.62 AT 2026jiv 2026-03-24.69 21.87
12:17:57.600 +45:03:04.77 AT 2026jiu 2026-03-24.69 20.4
11:39:16.940 +45:15:03.67 AT 2026jit 2026-03-24.66 21.06
14:17:33.100 +43:22:03.41 AT 2026jis 2026-03-22.80 20.74
14:45:33.130 +38:26:13.04 AT 2026jir 2026-03-22.80 21.14
14:42:55.800 +38:18:34.13 AT 2026jiq 2026-03-22.80 21.14
12:43:36.900 +28:13:26.06 AT 2026jip 2026-03-20.69 21.81
13:50:42.590 +38:45:33.09 AT 2026jio 2026-03-29.93 20.87
19:45:48.257 -49:40:35.86 AT 2026jin 2026-04-12.35 18.142
23:14:08.648 +35:53:12.54 AT 2026jim 2026-03-28.53 17.909
07:22:52.030 +11:04:39.45 AT 2026jil 2026-04-11.54 18.4
-rw-r--r-- 1 apache apache 30K Apr 19 00:45 tns_transients_list.txt
