David's Astronomy Pages
Notes - Session 1247 (2024-09-18)

 
Bullet Session Aims & Highlights
 - Observing Result
 - Night Summary Plot
 - Session Event Log
Bullet Operational Issues
  - Critical Issues (0),  Major Issues (0),  Minor Issues (3),  Small Defects (2),  Continuous Improvement (17)
Bullet Images from 2024-09-18 >>         
   
2024-09-22
Bullet SQLite 3.46.1
Bullet Transient Monitoring
   

Session Aims & Highlights (2024-09-18)

Main aims

  1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
  2. AstroMain.  Continue to check new 3.69.8 / 3.70 version of AstroMain to ensure new code in ObsManager for handling JobQueue/TheSky6 freezes has no negative effects or problems
  3. ImageLink/TheSky6.  Monitor session for any further incidents of the issue where the ImageLink process freezes for 5 minutes leading to Target Abort & Session Suspension.  Tracing was further extended in AstroMain 3.69.8 / 3.79. The new version also contains some statements tha might potentially resolve the ongoing issue.

 Equipment & Software

Highlights-

Notes:

Summary Plots & Logs

Observing Plan
Image
  
Observing Result
Image
   
Image
 
Dome & Scope Slewing Performance
Image
  
Slew/Centering Performance
Image
  
Guiding Performance
Image
  
Sky Conditions (Locate Frames)
Image 
  
Night Sky Summary Plot
Top axis: Sky Brightness at Zenith (in ADU/s)
Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs)
Image   
  
Actual Weather vs Pre-Session Weather Forecast
Image
Image
  
Session Event Log
Time     Event Detail
20:37:38 Session Monitoring AutoStart monitoring for Live Session opportunity between 20:37 & 04:42
20:37:39 Session AutoStarting Session autostarting (20:37)
20:38:03   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.)
20:38:31   Camera1 Connected SBIG Camera connected (Set point -10°C)
20:38:33 Session Created Session Created (Live, 2024-09-18 S01247, ImageSaveNum: 1247001)
20:38:38   Scope Switched On Telescope Power has been switched on via UPB Powerbox.
20:40:41   Services Started Observatory Services started
20:40:48 Observatory (Auto) Observatory placed in Fully-Automated Mode
20:40:50 Session Pending Session pending (2024-09-18)
20:40:52 Session Initiating Session initiating (2024-09-18)
20:41:01   Camera1 Connected SBIG Camera connected (Set point -10°C)
20:41:08   Plan Requested Observing Plan requested from AstroPlan (1.41)
20:42:05   Plan Loaded Observing Plan loaded to queue (Plan ID: 1022)
20:42:45   Telescope Connected Telescope connected (TheSky6)
20:43:09 Session Equilibration Session ready to Open Dome
20:43:54   Dome Opened Dome opened (Opening time 45s, Zigbee 39s)
20:44:09 Session Running Session running
20:44:11   Queue Started Observing Queue started (31 targets selected)
20:44:15     Target Started (NrZen) Target started (Focus Field 19, HIP 93376)
20:44:25       Dome Unparked Dome unparked
20:47:52       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
20:49:55       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide)
20:51:56       Focusing Completed Foc1 AutoFocus Completed (Profile No 1)
20:51:58       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap)
20:54:07       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide)
20:55:50       Focusing Completed Foc2 AutoFocus Completed (Profile No 2)
20:56:08     Target Completed (NrZen) Target completed (Focus Field 19, HIP 93376)
20:57:36     Target Started (1/31) Target started (1/31, GCVS T CrB)
21:01:34       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
21:03:49       Focusing Failed Foc1 focusing check failed
21:03:51       Focusing Completed Foc1 AutoFocus Completed (Profile No 3)
21:09:35     Target Completed Target completed (1/31, GCVS T CrB)
21:09:39     Target Started (2/31) Target started (2/31, AT2023guz)
21:12:53       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
21:15:26       Focusing Completed Foc1 AutoFocus Completed (Profile No 4)
21:31:32     Target Completed Target completed (2/31, AT2023guz)
21:31:36     Target Started (3/31) Target started (3/31, UGC 11315 w/AT2022aair)
21:34:55       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
21:37:08       Focusing Completed Foc1 AutoFocus Completed (Profile No 5)
21:53:03     Target Completed Target completed (3/31, UGC 11315 w/AT2022aair)
21:53:52     Target Started (4/31) Target started (4/31, AT2023tww (CV))
21:56:54       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
21:58:55       Focusing Completed Foc1 AutoFocus Completed (Profile No 6)
22:04:48     Target Completed Target completed (4/31, AT2023tww (CV))
22:05:52     Target Started (5/31) Target started (5/31, AT2022zkq (CV))
22:08:54       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
22:11:00       Focusing Completed Foc1 AutoFocus Completed (Profile No 7)
22:16:53     Target Completed Target completed (5/31, AT2022zkq (CV))
22:18:12     Target Started (6/31) Target started (6/31, Nova Vul 2024)
22:21:10       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
22:23:11       Focusing Completed Foc1 AutoFocus Completed (Profile No 8)
22:26:33     Target Completed Target completed (6/31, Nova Vul 2024)
22:28:02     Target Started (7/31) Target started (7/31, AT2024vla)
22:30:59       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
22:32:59       Focusing Completed Foc1 AutoFocus Completed (Profile No 9)
22:48:52     Target Completed Target completed (7/31, AT2024vla)
22:50:22     Target Started (8/31) Target started (8/31, AT2023abtp (CV))
22:53:14       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
22:55:50       Focusing Completed Foc1 AutoFocus Completed (Profile No 10)
22:58:21       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars)
23:01:58     Target Completed Target completed (8/31, AT2023abtp (CV))
23:02:00   Queue Paused Queue paused for Session Suspension
23:02:02 Session Suspending Session suspending
23:02:51   Dome Closed Dome closed (Closing time 50s, Zigbee 42s)
23:02:54 Session Suspended Session suspended
23:21:18     Target Cancelled Target cancelled (9/31, AT2023xev) due to cloud
23:39:48     Target Cancelled Target cancelled (10/31, GCVS CY AQR) due to cloud
23:51:18     Target Cancelled Target cancelled (11/31, AT2023ysf (CV)) due to cloud
00:03:19     Target Cancelled Target cancelled (12/31, AT2023csw (CV)) due to cloud
00:14:26     Target Cancelled Target cancelled (13/31, GCVS CI Cyg) due to cloud
00:33:41     Target Cancelled Target cancelled (14/31, AT2023mil) due to cloud
00:56:01     Target Cancelled Target cancelled (15/31, AT2024vhz) due to cloud
01:18:01     Target Cancelled Target cancelled (16/31, AT2023cgz) due to cloud
01:40:01     Target Cancelled Target cancelled (17/31, M31 w/AT2024rkz) due to cloud
01:52:21     Target Cancelled Target cancelled (18/31, MPL 532 Herculina) due to cloud
02:04:11     Target Cancelled Target cancelled (19/31, AT2021aesn (CV)) due to cloud
02:14:21     Target Cancelled Target cancelled (20/31, GCVS RX And) due to cloud
02:33:51     Target Cancelled Target cancelled (21/31, AT2024ugc) due to cloud
02:56:11     Target Cancelled Target cancelled (22/31, NGC 3206 w/SN2024bch) due to cloud
03:05:54 Session Resuming Session resuming
03:06:39   Dome Opened Dome opened (Opening time 45s, Zigbee 40s)
03:06:41 Session Running Session running
03:06:43   Queue Resumed Observing Queue resumed
03:06:46     Target Started (23/31) Target started (23/31, AT2023wfp)
03:23:12     Target Completed Target partially completed (23/31, AT2023wfp)
03:23:16     Target Started (24/31) Target started (24/31, AT2024vlc)
03:26:42       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
03:28:41       Focusing Completed Foc1 AutoFocus Completed (Profile No 11)
03:45:12     Target Completed Target completed (24/31, AT2024vlc)
03:45:17     Target Started (25/31) Target started (25/31, AT2023add (CV))
03:48:01       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
03:50:13       Focusing Completed Foc1 AutoFocus Completed (Profile No 12)
03:56:05     Target Completed Target completed (25/31, AT2023add (CV))
03:56:09     Target Started (26/31) Target started (26/31, GCVS BL Lac)
04:00:02       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
04:02:08       Focusing Completed Foc1 AutoFocus Completed (Profile No 13)
04:06:04     Target Completed Target completed (26/31, GCVS BL Lac)
04:06:08     Target Started (27/31) Target started (27/31, GCVS RR Tau)
04:09:56       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
04:12:04       Focusing Completed Foc1 AutoFocus Completed (Profile No 14)
04:18:51     Target Completed Target completed (27/31, GCVS RR Tau)
04:18:55     Target Started (28/31) Target started (28/31, GCVS GK Per)
04:21:44       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
04:24:03       Focusing Completed Foc1 AutoFocus Completed (Profile No 15)
04:27:49     Target Completed Target completed (28/31, GCVS GK Per)
04:28:18     Target Started (29/31) Target started (29/31, AT2023cmv (CV))
04:31:14       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
04:33:49       Focusing Completed Foc1 AutoFocus Completed (Profile No 16)
04:39:41     Target Completed Target completed (29/31, AT2023cmv (CV))
04:40:18     Target Started (30/31) Target started (30/31, GCVS GW Ori)
04:45:44       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
04:48:05       Focusing Completed Foc1 AutoFocus Completed (Profile No 17)
05:01:43     Target Completed Target completed (30/31, GCVS GW Ori)
05:01:47     Target Started (31/31) Target started (31/31, AT2024uzm)
05:04:49       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
05:07:07       Focusing Completed Foc1 AutoFocus Completed (Profile No 18)
05:23:11     Target Completed Target completed (31/31, AT2024uzm)
05:23:13   Queue Completed Job Queue completed
05:23:17 Session Closing Session closing
05:24:12   Dome Closed Dome closed (Closing time 50s, Zigbee 43s)
05:25:01   Dome Parked Dome parked (parking time 42s), Az: 90.0 deg
05:26:14   Telescope Parked Telescope parked (parking time 70s total)
05:26:29   Telescope State Handbox reads 'Scope parked Turn scope off.'
05:26:51   Telescope Switched Off Telescope Power has been switched off via UPB Switch.
05:28:14   Services Stopped Night Services stopped
05:28:17 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files)
05:28:39     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow)
05:29:38     Dome Find Park found (Best Park Az 90.3°)
05:29:44     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.3°)
05:29:46   Dome Parked Dome parked
05:30:07   Dome Charging Dome is parked and re-charging Ok (58mA)
05:30:09 Session Finished Session Finished

 
Session Alerts & Alarms
Time     Type       Name Detail
20:47:33 Red Alert Program Hung AstroMain UI appears to have stopped responding at 20:47
20:47:38 Green Clear Program Resumed AstroMain UI has resumed again after 14s
22:50:57 Yellow Alert Dome Discrepency Difference between Dome Az and Slave Az is > 1 deg (AT2023abtp)
05:30:07 Green Clear Dome Charging Dome is parked and re-charging Ok (58mA)
 

Back to Top


Operational Issues (2024-09-18 S1247)

[ Prev | Next ]

Critical Issues

Major Issues

Minor Issues

Small Defects

Continuous Improvement

[ Prev | Next ]


Fig 1.   New Target String Utility
New Target String Utility added to AstroMain 3.71.1 allows the Target List from the contents section of a session's web page to be pasted into the utility (top picture) and quickly processed to create a comma delineated string representation (bottom picture) that can be inserted into session's image link description on the Session Images index page
 
(example below is from Session 1240 (2024-09-10).

Image
 
Image
 
Saturn, Nova Per 2020, Nova Vul 2024, T CrB, AT2022jsu, AT2022snh, AT2022vqv, AT2022wxa, AT2023abqc, AT2023abtv, AT2024ed, AT2024rrb, M33 w/Nova 2024-08a?, NGC 797 w/SN2024jjc, NGC 3073 w/AT2024unf, NGC 3079 (H V-47), NGC 3206 w/SN2024bch, NGC 7253B w/SN2023wuk, SN 2023reh (S01240)

Fig 2.   Main Mirror Refocusing (2024-09-26)
Focus Profile from end of S1247 session (top picture) compared with Focus Profile after Primary Mirror Refocusing on 2024-09-26 (bottom picture)

a) Focus Profile, End of Session S1247,  Best Focus at 497 which is close to lower end of TCF-S' focusing range (0-7000)
Image

b) Focus Profile after Primary Mirror Refocusing ,  Best Focus at 3554 which is close to the center of TCF-S' focusing range (0-7000)
Image


Fig 3.   Night Summary Plot covering period of Telescope Refocusing (2024-09-26)
The period when the refocusing was taking place (when the Dome was open) doesn't show any Dome Shutter flags on the chart. This most-likely doesn't hape However the design needs The log doesn't show the period when the dome was open, .  This should be shown even though this took place during a General Session (rather than during a Live Session).  As this wasn't a live session the periods when the dome was operating but closed it is correct not to show a 'dome closed' flag, however

Image

Fig 4.   Aladin Lite embedded below centred on NGC 3683
(see  https://aladin.cds.unistra.fr/AladinLite/doc/#embedding for details on how this is done )


This uses the following embedded code

 <!-- insert this snippet where you want Aladin Lite viewer to appear -->
<div id="aladin-lite-div" style="width:800px;height:500px;">
</div>
<script type="text/javascript" src="https://aladin.cds.unistra.fr/AladinLite/api/v3/latest/aladin.js" charset="utf-8"></script>
<script type="text/javascript">
  let aladin;
  A.init.then(() => {
    aladin = A.aladin('#aladin-lite-div', {target: "NGC 3683", survey: "P/DSS2/color", fov:0.20});
  });
</script>

(see  https://aladin.cds.unistra.fr/AladinLite/doc/#embedding for more details on how this is done )

[ Prev | Next ]

Back to Top


2024-09-22


SQLite 3.46.1

 SQLite is used for the Observatory Databases.  Database locations are shown below

Database Location

Databases :   "C:\Data\CCD Imaging\Targets Database"
BackUps :      "C:\Data\CCD Imaging\Targets Database Backups"   (with timestamped subfolders with names like  "../Targets Database (2024-09-20 2018)"

SQLite Update
Currently databases are read/changed from AstroSuite's VB.Net programs (AstroPlan, AstroMain, AstroSN, AstroVOE) using library assembly System.Data.SQLite.dll"  ( ..\packages\System.Data.SQLite.Core.1.0.108.0\lib\net40\System.Data.SQLite.dll  )

The latest version of Sqlite3 give access to new commands "Alter table .. rename column .."  and "Alter table .. drop column .." which are useful functionality, but likely not available in the currently employed SQLite.dll  

( The facility to 'DROP COLUMN'  from a table only appeared in 3.35.0 )

 It may be easier to install the latest Command Line version of Sqlite3 in order to manually make changes to table schema, as such changes are just an occassional ad-hoc requirement.  This also reduces the risk associate with updating sqlite across several projects (AstroPlan, AstroMain, AstroSN, AstroVOE).

SQLite 3.46.1 was download and installed today (2024-09-22).

Download & Installation of SQLite onto Windows

  1. Go to SQLite Download Page (from SQLite Site,  https://www.sqlite.org/ )
     
  2.  Goto the "Precompiled Binaries for Windows" section and download  "sqlite-dll-win-x64-*.zip"  and "sqlite-tools-win-x64-*.zip
     
  3. Unzip downloaded files and move contents to a program folder of user's choice   "C:\More Programs\Sqlite"
    - The Command Line Shell is "sqlite3.exe"
    - The DLL file is  "sqlite3.dll"
    - Other tools are "sqldiff.exe" & "sqlite3_analyzer.exe"
     
  4.  Add the program folder path to system PATH

Adding to Windows system PATH

  1. Right-click on the Start Button.
  2. Select “System” from the context menu.
  3. Click “Advanced system settings”
  4. Go to the “Advanced” tab.
  5. Click “Environment Variables…”
  6. Click variable called “Path” and click “Edit…”
  7. Click “New”
  8. Enter the path to the folder containing the binary you want on your PATH.
    "C:\More Programs\Sqlite"
  9. May need to restart computer for executables on new path to be used via
    > sqlite3

Back to Top


Transient Monitoring

 'Monitor Target' was as original intended capability when the Observatory Target Database & AstroPlan designed and built.   It was intended to make observations of a given target occur at a semi regular frequency expressed in days.   However it hasn't really been used, with the consequence that a ongoing active Target with StatusType  "Regular Target" has to be manually set to Must-Include Tier3 (Standby) to explicitly delay Target Observation and then later on manually turned off Tier 3 (Standby) or set Must Include Tier 1 or Tier 2. This is labourious when there should be a automated way of spacing observations, and can lead to multiple observations over just a few nights when this isn't necessary, or a failure to make Observations for an extended period.

Targets like short-medium period variables stars might need observations every available night, whilst  targets like long period variables and nearby star might only need observations every 14 days or so.   Targets like Supernova may need observations every 1-2 nights to begin with, becoming every 3-4 nights after that and then declining in frequency becoming every 30 days of so later on.   Some long term monitoring of a Nova might eventually require observations every 100 nights or so.

Current Design
As originally designed,  monitoring was specified by setting Observation Type to "Monitor" on the Target Form, which would lead to 4 other fields to be shown.
Req'd Obs  (the number of observations to be made), Obs.Done (the number of observations made), Req'd Frequency (the required frequency in observations, in days). & Time of Last Obs. (the Date/Time when the Last Observation was made). The design was intended to make the Target available for the Observing Plan when "Now > Time of Last Obs.AddDays(Req'd Frequency)".  The design also had the intention that when the value of Obs.Done reached the value of Req'd Done, the status of the target would be automatically set to "Completed".

The database's target table has the following columns to support this

   ObservationType  integer
   MonitorNumObsRequired  integer
   MonitorNumObsCompleted  integer
   MonitorLastObservation  varchar(20)
   MonitorRequiredFrequency  real

The TargetRecord structure (T) has the following fields to support this :

   ObservationType  (ObservationType,  Integer)          
   MonitorNumObsRequired  (integer)
   MonitorNumObsRequired  (integer)
   MonitorLastObservation (string)
   MonitorRequiredFrequency (double)

   MonitorLastObservation has default (blank)  value 1999-09-09 (00:00:00)  whilst other fields have default values of 0.
   Enum ObservationType     Monitor = 2

For regular monitoring the Req's Frequency is set when the Target is originally created/setup.  If the frequency needs to be changed to be appropriate to a supernova or nova decay this would need to be manually changed by the user.

New Design
In practice the deactivation (Completion) of a Target is performed by the user manually setting TargetStatus to "Completed", and the "Req's Obs" and "Obs Done" are not required.

For regular monitoring it is appropriate to continue with the  Req'd Frequency that was set up by the user when the Target was created/set-up but for certain targets like a supernova or nova it would be helpful to have the Req'd Frequency to be automatically adjusted to have a nightly observation during build-up and early decline, progressively lengthening to prehaps a frequency of 100 days or more.

The 'Time of Last Obs' can be obtained by a query on the session observation table and doesn't need to be a database field.
Of more value is a new database field called 'Night Due' (the Night Date of the night that a new observation becomes due).

If an observation is made but upon review/analysis its images are then rejected (due to cloud, bad guiding or any other reason), there needs to be a process to allow its Night Due to be set as the upcoming night so that a replacement observation can be made as soon as possible.

The target table columns needs the following fields to be added :

    MonitorNightDateDue  varchar(20)
    MonitorRequiredFrequency  real
    MonitorAutoFrequency  varchar(10)

The TargetRecord structure (T)
  

Actions required
  

Auto Frequency

A way of automatically adjusting the Observational Frequency with according to number of days since discovery of a transient object (TDays) has been devised using the following equation

  Frequency (in days) = Maximum(1,10^(LOG10( TDays)- FrequencyFactor)  )
 
 where FrequencyFactor is a number between 0.3 and 1.2

The following charts illustrate the transients observations for first 100 days in two ways :
    i) vs Frequency  
   ii) vs No. of Observations

Image

Image
 

The following charts are similar to those above but extend out to 1500 days.

Image

Image

Ideally the Frequency Factor curves might be reduced in number from 10 to to say just 4 and to take on some user-friendly names, such as "Slow", "Medium", "Medium-Fast" & "Fast", but the decision of what to take and their best names has not been decided.  So instead might be best to simply go with "1.2", "1.1", "1.0" and so on down to "0.3".

All the curves start out with an Obs.Frequency of 1 (i.e. Nightly Observations) and after a varying amount of time (from 3 to 22 days ) the frequency of observations then reduces at varying rates.

Unless the appropriate Factor to select can be gleaned from the information about the reported Transient it may be appropriate to simply set a middle-of-the-road factor (eg. "0.8"), and then if it is appropriate to continue nightly observations for longer the Factor can be manually increased to between "0.9" & "1.2", but if instead it is appropriate to space out observations the Factor can be manually decreased to between "0.7" and "0.3".

Depending on the relative interest in the Transient Object and its behaviour,  it may be appropriate to have a lot of nightly observations to begin (covering say the first 3 months), but change to a lower frequency later on (covering 2-3 years).  Nova Cas 2021 would fall into this category of a particularly interesting object.

Whilst the graphs suggest a high number of observations (e.g. between 12 and 65 observations in the 300 days period post discovery) the actual number of observations will inevitably be less than this for a number of reasons:

This effect can be mitigated in part by allowing a Transient Observation if it is close to being due, where Tolerance is set according to the RequiredFrequency as follows:

 ' Get Allowed Tolerance
' ---------------------
If .MonitorRequiredFrequency > 50 Then
  Tolerance = 5
ElseIf .MonitorRequiredFrequency > 25 Then
  Tolerance = 4
ElseIf .MonitorRequiredFrequency > 12 Then
  Tolerance = 3
ElseIf .MonitorRequiredFrequency > 7 Then
  Tolerance = 2
ElseIf .MonitorRequiredFrequency > 4 Then
  Tolerance = 1
Else
  Tolerance = 0
End If

' Exclude Target if Observation not due (or not close to being due) ' added 2024-09-22 (CI S1247)
' ----------------------------------------------------------------
If DateTime.Parse(GetNightDateNow()).Subtract(DateTime.Parse(.MonitorNightDateDue)).TotalDays + Tolerance < 0 Then
  bRollBack = True
  .ExclusionReason = "Observation not due till " + .MonitorNightDateDue
End If

If an Observation is only Part Completed, the NightDateDue is based on taking 30% of the RequiredFrequency.

 DueDays = Math.Max(1, Int(T.MonitorRequiredFrequency * 0.3))
 
 D = DateTime.Parse(GetNightDateNow).AddDays(DueDays)
 T.MonitorNightDateDue = D.ToString("yyyy-MM-dd") )

If user accepts the part-completed Observation the NightDateDue can be set using the 'Due From Last' button facility on the Target's target form.

If user declines to accept a Completed or Part Completion Observation, that Observation can be marked a Rejected on Session's Observations form and
the NightDateDue can be reset on the Target's target form using either 'Due From Last' or 'Due Now' buttons.

Back to Top