|Proposer||(18587) Daniel Zaharevitz (email@example.com) obscode: ZDAB|
|Assigned To||(3663) Dirk Terrell|
|Date Submitted||Jan. 16, 2023|
Monitor the faint stars in the Super Nova Candidate list
This proposal is complementary to Proposal #242. That proposal uses AAVSONet Bright Star Monitor stations to monitor stars in the AAVSO SNEWS Campaign (https://www.aavso.org/snews-campaign). This is a list developed in a collaboration with SNEWS (Super Nova Early Warning System. see https://snews2.org/ ) It was created in December 2021 with an emphasis on brighter stars and thus Proposal #242 was assigned to AAVSONet BSM stations. This has been quite successful, providing almost 3000 observations and playing a major role in reducing the number of stars with zero observations in AID from 57 at the start of the campaign to 6 (as of 01/15/2023). The present proposal looks to extend the monitoring to the FSM stations. There are three main goals:
1) monitor the stars in the SNEWS Campaign list with V magnitude > 10
2) support the efforts of the SNEWS team to extend the list of candidate stars by monitoring potential additions to the list with V magnitude > 10. For this pilot effort, we choose stars on the SNEWS extended list that are already in VSX with an AUID.
3) support the efforts of AAVSO to bring full support for data with Sloan filters to the AAVSO software and databases by providing an ongoing source of data, analysis, and feedback for using Sloan filter data in AAVSO software.
Details would be as in Proposal #242; priorities set to just above survey level, images routed to Daniel Zaharevitz (ZDAB), plan sent to two FSM's one north, one south. The goal for initial cadence is 10 days. The multi filter photometry is requested, most likely B V SG SR SI, but whatever is available on the assigned telescope.
StarName,RA2000,RA(H.HHHHH),Dec2000,AUID,DataCount,VarType,Constellation,MaxMag,LatestObservation,Lapse (days since last observation),LastResult
|Target||RA (H.HH)||Dec (D.DD)||Magnitude||Telescope||Observation Frequency||Expiration Date||Proprietary Term|
|NSV 18823||11.635730||-63.21978||11.27–11.08||MPO61||10||July 17, 2023||No|
|V0397 Cen||13.295600||-62.68917||13.0–10.4||MPO61||10||July 17, 2023||No|
|ASAS J143217-6106.4||14.538090||-61.10672||12.17–11.67||MPO61||10||July 17, 2023||No|
|ASAS J152507-5938.6||15.418610||-59.64403||11.22–10.84||MPO61||10||July 17, 2023||No|
|[HHR2012] J162126.1-492352||16.357240||-49.39794||10.13–9.82||MPO61||10||July 17, 2023||No|
|CX Mon||6.621800||0.92119||10.52–10.03||MPO61||10||July 17, 2023||No|
|V0492 Aql||18.990900||5.37783||10.67–10.17||MPO61||10||July 17, 2023||No|
|KY Cyg||20.432790||38.35214||11.8–10.5||MPO61||10||July 17, 2023||No|
|V1489 Cyg||20.773760||40.11653||18.0–16.0||MPO61||10||July 17, 2023||No|
|IO Per||3.113130||55.73317||12.3–10.8||MPO61||10||July 17, 2023||No|
|TYC 3973-145-1||22.172210||56.19692||11.15–10.89||MPO61||10||July 17, 2023||No|
|V0354 Cep||22.559620||58.89642||11.74–10.67||MPO61||10||July 17, 2023||No|
|V0674 Cep||22.471510||59.23447||11.7–10.2||MPO61||10||July 17, 2023||No|
|V0355 Cep||22.819580||59.30361||11.4–10.55||MPO61||10||July 17, 2023||No|
|V0582 Cas||23.503120||60.27928||12.8–11.7||MPO61||10||July 17, 2023||No|
|V0703 Cas||2.456660||60.67995||12.52–10.77||MPO61||10||July 17, 2023||No|
|NADA-V14||23.243830||60.92133||11.1–10.9||MPO61||10||July 17, 2023||No|
|NSV 14333||22.848110||61.76607||12.0–11.1||MPO61||10||July 17, 2023||No|
|IRAS 00408+6200||0.730740||62.28067||10.85–10.72||MPO61||10||July 17, 2023||No|
|V0902 Cas||1.432880||63.49225||11.8–10.9||MPO61||10||July 17, 2023||No|
|V0634 Cas||0.825970||64.78312||11.2–10.6||MPO61||10||July 17, 2023||No|
Committed to OC61 and MPO61
Most of these would have worked on BSMs. Not sure why you needed FSMs?
My assumption was that it would be implemented on the BSMs for the most part. I don't think it is appropriate to overload the FSMs with this.
Comments on this proposal are closed.