Proposal #377
| Proposer | (46778) David Gay (1983riceowl@gmail.com) obscode: GDAL |
|---|---|
| Assigned To | (3663) Dirk Terrell |
| Date Submitted | June 30, 2023 |
| Status | Allocated |
| Priority | Normal |
| Proposal | Weekly BSM monitoring of Blaze Stat T CrB in BVRI (3x each) through its forecast pre-eruption dip and eruption forecast as 2024.4 +/-0.3 from B. E. Schaefer (Louisiana State Univ.), B. Kloppenborg (AAVSO), E. O. Waagen (AAVSO). |
| Target | RA (H.HH) | Dec (D.DD) | Magnitude | Telescope | Observation Frequency | Expiration Date | Proprietary Term |
|---|---|---|---|---|---|---|---|
| T CrB | 15.991387 | 25.92230 | 12.0–9.0 | BSM_TX | 1 | Jan. 3, 2024 | No |
Comments
- (3663) Dirk Terrell — July 6, 2023, 3:05 p.m.
Same target as #376 but different filters. Ken to decide how to implement.
- (4726) Kenneth Menzies — July 7, 2023, 6:59 p.m.
Committed to TX with BVRI.
- (46778) David Gay — Jan. 30, 2024, 9:19 p.m.
I wondered why I was getting no more data just as T CrB was becoming observable again. I see now that it expired on Jan 3. I would like to request that this proposal be extended throughout the 2024 observability season (which is from Feb-Sep) so until Sep 30, 2024. Thank you.
- (3663) Dirk Terrell — Jan. 31, 2024, 3:30 p.m.
I wouldn't object to renewing this proposal.
- (4726) Kenneth Menzies — Feb. 3, 2024, 7:18 p.m.
It doesn't have an expire date in the actual plan!
- (46778) David Gay — Feb. 5, 2024, 5:55 a.m.
While there was not an explicit end date given in the proposal, given Dr. Schafer's eruption forecast of 2024.4 +/-0.3 that was mentioned in it, there was an implicit end date of 2024.4 +0.3 ~= Aug 15, 2024. If the observations can be extended through Sep 30, 2024, it would be great. Thank you.
- (4726) Kenneth Menzies — Feb. 5, 2024, 5:17 p.m.
I meant that when I created the plan for the TX scope, I did NOT enter an end date. It will continue forever! Until you tell me to stop and I archive the plan on the scope.
Ken
- (46778) David Gay — Feb. 5, 2024, 5:53 p.m.
OK, thank you! For some reason the last time that the target shows up on the bsm_tx scheduler log was on Jan 3, 2024, which corresponds to the expiration date shown above. Proposal #377 does not show up on the Jan 15, Jan 16, Jan 24 or Jan 28 scheduler logs for bsm_tx, although a couple of those runs ended with "**Too many failures to plate solve. The scope appears to be lost. Aborted." So it has been a month without an observation due to equipment issues, weather issues, or something (lower priority?) within the scheduling optimizer, which understandably may be struggling getting all observations in due to the limited uptime on bsm_tx during January.
Comments on this proposal are closed.