David's Astronomy - Notes 2021-08-27 (S0909)

David's Astronomy Pages
Notes - Session 909 (2021-08-27)

Notes
(S908)

Notes
Main

Home
Page

Notes
(S910)

	2021-08-28

	Session Aims & Highlights
	- Observing Result - Night Summary Plot - Session Event Log

	Operational Issues
	- Critical Issues (1), Major Issues (2), Minor Issues (12), Small Defects (2), Continuous Improvement (16)

	Images from 2021-08-27 >> [ Local Files >> ]

	Aurora Images/Video from 2021-08-27 >>

	Investigation - Target Position Failure (2 Pallas)
	SharpCap 4.0

	2021-08-30
	Review - Spectra Processing and Analysis

Session Aims & Highlights (2021-08-27)

Main aims

Targets. Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by time & conditions.
AstroMain. Test fixes, improvements and new features in AstroMain 3.41.4. Check for stability.

Equipment & Software

12" LX200 and ST-10XME
80mm APO and ZWO ASI 178MC
CCDApp2, TheSky6, CCDSoft5, PHD2 2.6.10, DeviceHub 6.5.1.4, MeadeGeneric 1.3.1.361, UPB 1.5, ASCOM 6.5 SP1
Pegasus UPB & Motor Focus, TCF-S
SharpCap 3.2, PHD2 2.6.10
AstroMain 3.41.4, AstroPlan 1.22.5, AstroShCap 1.3.11, AstroGuard 1.6.1, AstroVOE 1.7, AstroSN 1.5.1, AstroProtect 1.6
(AstroWeather 1.12.4, AstroAllSky 3.10.4, AstroObsCam 1.5.7)

Highlights

AstroMain.

Lowlights

User Errors. Two user errors with major impact to session.
1) Lens Cap on Main Scope was not removed prior to start of session.
2) Telescope was moved into a position where cables knocked the power button to off position.
Errors were eventually both corrected but at the cost of 2 visits to the observatory and 2 hours of good observing time.

Notes:

Summary Plots & Logs

Observing Plan

Observing Result

Dome & Scope Slewing Performance

Slew/Centering Performance

Guiding Performance

Sky Conditions (Locate Frames)

Night Sky Summary Plot
Top axis: Sky Brightness at Zenith (in ADU/s)
Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs)

Actual Weather vs Pre-Session Weather Forecast

Session Event Log

Time	Event	Detail
19:17:26	Session Monitoring	AutoStart monitoring for Live Session opportunity between 21:14 & 03:45
21:14:48	AutoStart Waiting	AutoStart waiting till earliest start time at 21:14
21:14:49	AutoStart Delayed	Session delayed due to too few stars
21:37:10	Session AutoStarting	Session autostarting (21:37)
21:37:39	Session Created	Live Session Created (2021-08-27 S00909, ImageSaveNum: 909001)
21:37:42	Scope Switched On	Telescope Power has been switched on via UPB Powerbox.
21:39:23	Services Started	Observatory Services started
21:39:30	Observatory (Auto)	Observatory placed in Fully-Automated Mode
21:39:35	Session Pending	Session pending (2021-08-27)
21:39:37	Session Initiating	Session initiating (2021-08-27)
21:39:39	Plan Requested	Observing Plan requested from AstroPlan (1.22.6)
21:41:13	Plan Loaded	Observing Plan loaded to queue (, Plan ID: 650)
21:41:27	Camera1 Connected	SBIG Camera Connected (set point -15°C)
21:41:33	Telescope Connected	Telescope Connected (TheSky6)
21:41:44	Session Equilibration	Session ready for dome & camera equilibration
21:42:30	Dome Opened	Dome opened (opening time 46s)
21:42:35	Session Running	Session running
21:42:37	Queue Started	Observing Queue started (26 targets selected)
21:42:39	Target Started (NrZen)	Target started (Focus Field 19, HIP 93376)
21:44:38	Focusing Skipped	Foc1 focusing skipped - unable to find a star (TCF-S)
21:44:41	Focusing Started-Foc2	Foc2 Focusing Started (Secondary Scope, using ShCap)
21:47:00	Focusing Completed	Foc2 AutoFocus Completed (Profile No 1, wide)
21:48:51	Focusing Completed	Foc2 AutoFocus Completed (Profile No 1)
21:49:11	Target Completed	Target completed (Focus Field 19, HIP 93376)
21:54:36	Target Started (1/26)	Target started (1/26, NGC 6500 w/SN2021wuf)
21:58:58	Focusing Skipped	Foc1 focusing skipped - star is lost (TCF-S)
22:16:45	Target Completed	Target completed (1/26, NGC 6500 w/SN2021wuf)
22:20:35	Target Started (2/26)	Target started (2/26, NGC 4896 w/SN2021wad)
22:40:42	Target Completed	Target partially completed (2/26, NGC 4896 w/SN2021wad)
22:40:44	Target Started (3/26)	Target started (3/26, 17P/Holmes)
22:46:12	Focusing Skipped	Foc1 focusing skipped - star is lost (TCF-S)
22:57:41	Target Completed	Target completed (3/26, 17P/Holmes)
22:57:43	Target Started (4/26)	Target started (4/26, UGC 4002 w/AT2021wvy)
22:59:00	User Intervention	User Intervention to take off lens cap
22:59:13	Target Failed	Target failed due to centering error (4/26, UGC 4002 w/AT2021wvy)
22:59:15	Queue Aborted	Job Queue aborted
23:12:37	Telescope Connected	Telescope Connected (TheSky6)
23:19:00	User Intervention	User Intervention to resync telescope following user error
23:37:31	Session Monitoring	AutoStart monitoring for Live Session opportunity between 23:37 & 03:45
23:37:33	Observatory (AutoStart)	Observatory placed in Auto-Start Mode
23:37:35	Session AutoStarting	Session autostarting (23:37)
23:37:57	Services Started	Observatory Services started
23:38:02	Observatory (Auto)	Observatory placed in Fully-Automated Mode
23:38:05	Session Pending	Session pending (2021-08-27)
23:38:07	Session Initiating	Session initiating (2021-08-27)
23:38:17	Plan Loaded	Observing Plan loaded to queue (, Plan ID: 650)
23:38:24	Camera1 Connected	SBIG Camera Connected (set point -15°C)
23:38:29	Telescope Connected	Telescope Connected (TheSky6)
23:38:44	Session Equilibration	Session ready for dome & camera equilibration
23:38:46	Session Running	Session running
23:38:48	Queue Started	Observing Queue started (22 targets selected)
23:38:50	Target Started (NrZen)	Target started (Focus Field 21, HIP 103850)
23:40:31	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
23:43:40	Focusing Completed	Foc1 AutoFocus Completed (Profile No 2, wide)
23:45:53	Focusing Completed	Foc1 AutoFocus Completed (Profile No 2)
23:45:55	Target Completed	Target completed (Focus Field 21, HIP 103850)
23:45:57	Target Missed (5/26)	Target's time slot was missed (5/26, 2019 L3 (ATLAS))
23:50:04	Target Started (6/26)	Target started (6/26, NGC 6184 w/SN2021wkv)
23:50:06	Target Failed	Target failed due to missed start time (6/26, NGC 6184 w/SN2021wkv)
23:52:42	Services Started	Observatory Services started
23:52:48	Target Started (7/26)	Target started (7/26, AT2021uoa (CV))
23:53:56	Focusing Started-Foc2	Foc2 Focusing Started (Secondary Scope, using ShCap)
23:56:18	Focusing Completed	Foc2 AutoFocus Completed (Profile No 3, wide)
23:58:10	Focusing Completed	Foc2 AutoFocus Completed (Profile No 3)
00:00:35	Critical Humidity Alert	Critical Humidity Alert (Obs.Manager will close the Shutter)
00:00:37	HardSuspend Called	Hard Suspend is called due to Critical Conditions (high humidity)
00:00:40	Target Aborted (7/26)	Target aborted (7/26, AT2021uoa (CV)) due to high humidity
00:00:42	Queue Paused	Queue paused for Session Suspension
00:00:45	Session Suspended	Session suspended
00:01:35	Dome Closed	Dome closed (closing time 50s)
00:03:40	Target Cancelled	Target cancelled (7/26, AT2021uoa (CV)) due to cloud
00:07:10	Session Resuming	Session resuming
00:07:55	Dome Opened	Dome opened (opening time 45s)
00:07:57	Session Running	Session running
00:07:59	Queue Resumed	Observing Queue resumed
00:08:01	Target Started (8/26)	Target started (8/26, GCVS SS Cyg)
00:11:03	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
00:12:43	Focusing Completed	Foc1 AutoFocus Completed (Profile No 4)
00:16:26	Target Completed	Target completed (8/26, GCVS SS Cyg)
00:19:51	Target Started (9/26)	Target started (9/26, GCVS CI Cyg)
00:23:58	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
00:25:41	Focusing Completed	Foc1 AutoFocus Completed (Profile No 5)
00:29:21	Target Completed	Target completed (9/26, GCVS CI Cyg)
00:29:23	Target Started (10/26)	Target started (10/26, GCVS BL Lac)
00:32:37	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
00:34:23	Focusing Completed	Foc1 AutoFocus Completed (Profile No 6)
00:37:56	Target Completed	Target completed (10/26, GCVS BL Lac)
00:38:52	Target Started (11/26)	Target started (11/26, Nova Cas 2021)
00:43:00	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
00:44:47	Focusing Completed	Foc1 AutoFocus Completed (Profile No 7)
00:54:59	Target Completed	Target completed (11/26, Nova Cas 2021)
00:55:01	Target Started (12/26)	Target started (12/26, GCVS HH And)
00:57:10	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
00:58:53	Focusing Completed	Foc1 AutoFocus Completed (Profile No 8)
01:00:38	Target Completed	Target completed (12/26, GCVS HH And)
01:03:08	Target Started (13/26)	Target started (13/26, NGC 7767 w/AT2021kni)
01:06:38	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
01:08:46	Focusing Completed	Foc1 AutoFocus Completed (Profile No 9)
01:24:27	Target Completed	Target completed (13/26, NGC 7767 w/AT2021kni)
01:25:30	Target Started (14/26)	Target started (14/26, GCVS DY Per)
01:29:04	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
01:30:57	Focusing Completed	Foc1 AutoFocus Completed (Profile No 10)
01:35:26	Target Completed	Target completed (14/26, GCVS DY Per)
01:35:38	Target Started (15/26)	Target started (15/26, Nova Per 2020)
01:39:23	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
01:41:05	Focusing Completed	Foc1 AutoFocus Completed (Profile No 11)
01:55:01	Target Completed	Target completed (15/26, Nova Per 2020)
01:55:52	Target Started (16/26)	Target started (16/26, 61 Cyg)
01:59:33	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
02:01:09	Focusing Completed	Foc1 AutoFocus Completed (Profile No 12)
02:02:25	Target Completed	Target completed (16/26, 61 Cyg)
02:02:56	Target Started (17/26)	Target started (17/26, 2 Pallas)
02:05:57	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
02:07:52	Focusing Completed	Foc1 AutoFocus Completed (Profile No 13)
02:10:11	Target Completed	Target completed (17/26, 2 Pallas)
02:11:58	Target Started (18/26)	Target started (18/26, UGC 505 w/SN2021ukt)
02:15:59	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
02:16:30	Focusing Failed	Foc1 focusing failed - star lost
02:33:15	Target Completed	Target completed (18/26, UGC 505 w/SN2021ukt)
02:38:09	Target Started (19/26)	Target started (19/26, 15P/Finlay)
02:42:58	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
02:44:53	Focusing Completed	Foc1 AutoFocus Completed (Profile No 15)
02:54:53	Target Completed	Target completed (19/26, 15P/Finlay)
02:54:56	Target Started (20/26)	Target started (20/26, GCVS EV Lac)
02:58:41	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
03:00:25	Focusing Completed	Foc1 AutoFocus Completed (Profile No 16)
03:02:42	Target Completed	Target completed (20/26, GCVS EV Lac)
03:02:44	Target Started (21/26)	Target started (21/26, GCVS Z And)
03:06:13	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
03:07:54	Focusing Completed	Foc1 AutoFocus Completed (Profile No 17)
03:11:40	Target Completed	Target completed (21/26, GCVS Z And)
03:11:42	Target Started (22/26)	Target started (22/26, WDS GRB 34)
03:14:27	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
03:15:55	Focusing Completed	Foc1 AutoFocus Completed (Profile No 18)
03:17:44	Target Completed	Target completed (22/26, WDS GRB 34)
03:17:46	Target Started (23/26)	Target started (23/26, GCVS U And)
03:20:44	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
03:22:18	Focusing Completed	Foc1 AutoFocus Completed (Profile No 19)
03:32:11	Target Completed	Target completed (23/26, GCVS U And)
03:32:13	Target Started (24/26)	Target started (24/26, UGC 2605 w/SN2021wvw)
03:34:49	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
03:36:58	Focusing Completed	Foc1 AutoFocus Completed (Profile No 20)
03:52:44	Target Completed	Target completed (24/26, UGC 2605 w/SN2021wvw)
03:52:46	Target Started (25/26)	Target started (25/26, UGC 3240 w/AT2021vau)
03:56:43	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
03:57:57	Focusing Failed	Foc1 focusing failed - star lost
04:13:37	Target Completed	Target completed (25/26, UGC 3240 w/AT2021vau)
04:14:04	Target Started (26/26)	Target started (26/26, GCVS RX And)
04:17:33	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
04:19:13	Focusing Completed	Foc1 AutoFocus Completed (Profile No 22)
04:21:50	Target Completed	Target completed (26/26, GCVS RX And)
04:21:53	Queue Completed	Job Queue completed
04:21:55	Session Closing	Session closing
04:22:49	Dome Closed	Dome closed (closing time 50s)
04:23:49	Dome Parked	Dome parked (parking time 53s), Az: 90.0 deg
04:25:14	Telescope Parked	Telescope parked (parking time 77s)
04:25:29	Telescope State	Scope parked Turn scope off. (Handbox)
04:25:50	Telescope Switched Off	Telescope Power has been switched off via UPB Switch.
04:26:41	Services Stopped	Night Services stopped
04:26:43	Session Housekeeping	Housekeeping Started (Cleanup FITS, Create Fits Summary, Transfer Files)
04:26:59	Session Finished	Session Finished

Session Alerts

Time	Alert	Detail
00:41:25	Dome Discrepency	Difference between Telescope Az and Dome Az is > 8 deg (Nova Cas 2021)
00:51:24	Dome	Dome has been stationary for more than 10 mins
00:55:05	Dome	Dome Movements have begun again (outage 14.3 mins)

Operational Issues (2021-08-27, S909)

Critical Issues (1)
Major Issues (2)
Minor Issues (12)
Small Defects (2)
Continuous Improvement (16)

[ Prev | Next ]

Critical Issues

AstroGuard intervened inappropriately when the scope entered Az 350-360° and it proceeded to move the scope to Az 312° thereby wrapping cables around pier/mount base with potential for causing damage to equipment. After visiting the observatory to remove lens cap that hadn't been removed prior to session the scope was found to be pointing due north. Due to user misunderstanding of the telescope situation the telescope was moved pass the north line using the hand controller. AstroGuard recognised that the Telescope has moved beyond Az 350° (ie in region 350 to 360 deg) and intervened to move the telescope to what it considered to be a 'safe position', but this caused cables to wrap around the fork base. Code indicates that AstroGuard will attempt to slew to Az 180/Alt 5 (objScope.SlewToAltAzAsync(180, 5) ). It is possible that user intervened to stop the slew with the handset or Az 312 was that last azimuth read before the telescope power button became set to off. Fortunately (in a way) cables impact on the telescope's power button and move power switch to the off position. This issue is judged to be a critical issue, since rather than moving the telescope to a 'safe position' the automated operation actually placed the telescope into a situation with a great risk of causing damage to the telescope equipment. AstroGuard failed to recognise how the scope had arrive at the position it did (this was not dissimilar way to the issue that user failed to understand the scope's position/true status). Design of AstroGuard's AI Code didn't allow for the user doing extreme / inappropriate things ! Temporary Fix implemented in AstroGuard 1.6.2 that Aborts Current Slew and Turns off Tracking if the scope is found to have moved into the Az. region 350 to 360° (at Altitude < 65° ) instead of moving the scope to Az 180° in previous versions.
Temporary Fix implemented (AstroGuard 1.6.2)

Major Issues

LX200 Lens Cap accidently left on after taking dark frames during previous 2 days. Although Session proceeded to start ok (autostart has no current way of knowing whether lens cap is on or not) the session started and Near Zenith Focusing and first few targets were acquired, but obviously no useful image data was taken. Monitoring failed to recognise the issue for at least an hour. Monitoring indicated that autoguiding was functioning ok and it was assumed wrongly that main scope was imaging ok when it in fact wasn't.
User Error. Resolved in session (Session)
LX200 was accidently moved (via hand-controller) to a position which ended up in causing telescope cables to turn off the telescope power by making contact with its Power Button. After visiting the observatory to remove lens cap the scope was found to be pointing due north. At the time its was believed that scope had been at a target 2 (NGC 4896) in NNW sky (not NNW Sky but actually at Az 293°) and had somehow tracked to a north directed position (when it fact the scope had moved from Target 3 (17P/Holmes) at Az 34 to Target 4 (UGC 4002) at Az 4.8°) Insufficient care was taken to note the precise position of cables and understand the precise way the scope had reached this position and thus the correct direction to move the scope to return the scope to a normal position to continue the session after removal of the lens cap. Unfortunately the hand-controller was moved in the wrong direction and led to cables hitting the scope's power button with the consquence that Scope was powered off. At least 1 hour was lost as the scope had to be returned close to Meridian/Dec0, restarted & resynced (including a short mapping run). ObsCam pictures could (SHOULD) have been used to understand how the scope had moved into its position pointing roughly North and from which direction. ( Note: As a complication to the issue once the scope was moved past the North Line, AstroGuard recognised that Telescope has moved beyond Az 350° (ie in region 350 to 360°) and intervened to move the telescope to a 'safe position'. Telescope slewed to Az 312.3°, Alt 21.3° (47s) . This is entered as a separate critical issue, since rather than move the telescope to a 'safe position' the automated operation placed the telescope into a position of greater potential damage to equipment.)
User Error. Resolved in session (Session)

Minor Issues

Query: Problems with SharpCap Focusing. There was a suspicion that there was some issue with SharpCap focusing. Although Lens Cap had been left on the LX200 scope at start of session, this shouldn't have affected focusing using the TS80 GuideScope. There were problems in activating the SharpCap program window when tried at c 23:45. This seems to be related to an unexpected modal dialog asking whether to update SharpCap to latest version. This doesn't seem to have stopped the acquistion of SharpCap images at 21:44, and 23:54.. Profile shows focusing at 21:44 (Focus Field 19) was well defined with peak FWHM of 2.8 arc sec. Focusing at 23:54 (AT2021uoa) shows a poor FWHM of 8.8 arc sec. It is assumed that the star field didn't contain a sufficiently bright star.
Closed (Session)
LX200 moved to a position pointing approximately due North (22:57). When visiting the Observatory to remove the lens cap that had accidently been left on the LX200 Scope, it was noticed that the telescope was unexpectedly pointing in roughly due north position (safeguards should have operated to prevent the scope moving into this position due to dangers of cable wrap/equipment damage). Investigating showed that the scope had moved from Target 3 (NE Sky to Target 4 (UGC 4002) at Az 4.8 and its position was perfectly safe. Whilst initially graded as a Major Issue, the issue is downgraded to Minor Issue. Problem was a failure to recognise the scope's position part because of dim lighting. When a unexpected situation arises it is important to 'Stop' and understand the situtation before taking action which may prove to be incorrect or cause damage to equipment !
Closed 2021-08-28 (Session)
Duplicate Session Monitoring & Session Autostarting Events sent to database after restarting Session Run using AutoStart. One event is from the actual event, the duplicate event is due to saving of retrospective event. This happens normally, but because the first event is not saved to the prior general session but is saved to the live session the duplication becomes evident. Code modified to only write Retrospective Events if bAddRetrospectiveEvents is raised.
Fixed 2021-08-28 (AstroMain 3.41.5)
"Build Heading" button routine on the Analysis/ImageSets tab sometimes give a string in which the string 'with Type Ia Supernova' is duplicated. For example "UGC 505 - Spiral Galaxy with Type Ia Supernova with Type Ia Supernova 2021ukt". Problem is caused when Object Type includes ".. with Type Ia Supernova". This is writen out after which the string "with Type Ia Supernova 2021ukt" is built up and written from TNS details.
Fixed 2021-08-28 (AstroMain 3.41.5)
Transient details, Type Unk to SN Type Ia not updated for AT2021vau in UGC 3240. During compilation of images of UGC 3240 w/ AT2021vau (discovery date 2021-08-04.610) it was noted that transient details from Targets database showed in to be of Unknown whilst Rochester Supernova Site showed it has subsequently confirmed as Type Ia Supernova. AstroSN was run earlier in the day (at T+25d) and should have updated the database with transient's latest details. However there is an arbitary limit in AstroSN such that details are only updated for transients that are less than 14d or so. This limit needs to be raised to 90d.
Fixed 2021-08-30 (AstroSN 1.5.3)
AstroMain on Development Computer crashes when trying to connect to or take picture with SBIG ST10 camera which isn't present. Exception needs to be trapped, and the issue gracefully handled. Issue doesn't occur when CCDSoft Camera is set to 'Simulator'. The issue doesn't occur on the Observatory Computer (as SBIG ST10 Camera is normally always attached). In this instance the program crashes in TakeMainImage() routine with System.NullReferenceException: 'Object variable or With block variable not set.' on the code line "If Image.Path = "" Then", but a similar issue could occur anywhere else that Image tries to be accessed, such as ImageAndLink() routine. Fixed using Try, Catch End Try blocks.
Fixed 2021-08-29 (AstroMain 3.41.5 , Development Computer)
AstroMain on Development Computer crashes when trying to combine images taken with Simulater Camera. Exception needs to be trapped, and the issue gracefully handled. Issue doesn't occur with images taken with SBIG ST10 camera. Program crashes in GetCombinedName() routine with System.ArgumentException (Argument 'Start' must be greater than zero.) on the code line "If Microsoft.VisualBasic.Mid(MinS, Len(MinS) - 2, 1) = Microsoft.VisualBasic.Mid(MaxS, Len(MinS) - 2, 1) Then". The exception occurs when files have Image Numbers <100 (specifically less than 3 chars) which isn't normally a problem with images collected from live sessions, but obviously can for images during a test session.
Fixed 2021-08-29 (AstroMain 3.41.5 , Development Computer)
AstroMain on Development Computer producing incorrectly named combined file names when trying to saved combine images taken with Simulater Camera. With images named '2004_DV4.20210829.im1.2s.CFIT' to '2004_DV4.20210829.im3.2s.CFIT' the GetCombinedName() routine produces the name 2004_DV4.2021-3.av3x829.im1.2s.C.FIT. Problem is due to the routine searching for first instance of '1' in '2004_DV4.20210829.im1.2s.CFIT and extracting '2004_DV4.2021' instead of extracting 2004_DV4.20210829.im1. This isn't normally a problem with images from live session which are named like '2004_DV4.20210829.im909244.2s.CFIT' where the routine will be searching for first instance of '909244'. Code modified so that it searches for the first instance of 'im1'.
Fixed 2021-08-29 (AstroMain 3.41.5 , Development Computer)
Telrad's red reticle is badly out of focus. This has been an issue ever since the wiring connections in the Telrad were repaired. It would seem that the position of the light had somehow been affected during the repair . The Telrad's broad reticle was just about usable for aligning the scope onto the bright star Altair, but if star had been any dimmer or sky transparency was poor it may have been difficult to align the scope. Need to remove and open the Telrad to see if it is repairable and if not to purchase a new one. Problem was eventually diagnosed to be due to a small (1cmx1cm) plastic square with 'engaved' reticle that is normally located in the front of the Telrad's red light source becoming dislodged and temporarily lost. This plastic square is critical to getting a sharp red reticle in the Telrad FOV. The plastic square was eventually found stuck on the inside of the Telrad and will be stuck back in its correct position in due course. In the mean time an old red-dot finder has been pulled out of my astronomical 'odd n' ends' box and fixed to the LX200 scope in place of the Telrad.
Done 2021-10-27 (Observatory/Telrad)
TheSky6/ TeleAPI on Development Computer occasionally tries to connect to older POTH.Telecope instead of DeviceHub.Telescope. After failing to connect TeleApi settings have to manually rechanged to point to DeviceHub.Telescope. This issue only occurs on Development Computer. Problem can reoccur even after saving TheSky6 document in which TeleApi points to DeviceHub.Telescope. Unable to determine origin of the problem. Even after changing TeleApi Setting it seems to revert to an older historic setting. Proposal to monitor situation for time being. The Scope attached to TeleAPI is reported when starting the ConnectTheSky6Telescope() routine. Issue happened again ahead of session S819, 2021-10-03 (see details). ASCOM Profile. In an attempt to fix issue POTH.Hub key has been deleted from the ASCOM Profile Explorer (POTH had already be uninstalled fom the computer). There is suspicion (2022-05-16, See Session DH 6.6.0.8 Upgrade, S1010) that the issue occurs after recently updating DeviceHub (which uninstalls old DH version / installs new version). However the issue didn't arise after upgrading DH to 6.6.0.10 on 2022-06-02. Important to point out that the issue does not occur on the Observatory Computer (it is restricted to Development Computer). The issue shares some similarity to a problem seen around 2022-07-14 (S1022A) when TeleApi Settings began showing blank Telescope field and not saving a fresh selection following a Windows Update which was resolved by starting TheSky6 one-time as adminstrator (see Investigation - Can't Connect TheSky6 Scope (Blank TeleAPI, following Win Update), 2022-07-14).
Closed after review, 2022-07-14 (TheSky6 / ASCOM / DeviceHub)
Collection of AllSky Meas for Focus Field 19 timed out waiting for information from AllSky Computer (21:42). Fix attempted in AstroMain 3.41.4 but hasn't worked. Logs show that AstroAllSky recognised NextTarget(1) to (3) but not NextTarget(0) which should have had the name 'Focus Field 19' but was presumably set to blank string and therefore no sky measurement was taken. It is presumed that the process of calling UpdateTpnNextTargets(1) might have blanked NextTarget(0). AstroAllSky reventually recognises NextTarget(0) as being Focus Field 19, but this is not until 21:45 which was after telescope had slewed to Focus Field 19 position and had begun autofocusing. Fix attempted 2021-08-28 (AstroMain 3.41.5) but didn't work. Extra Trace message added to AstroMain 3.41.6 (controlled via cboxTraceCloudInformation checkbox on More/Backdoor Tab) to help understand this issue. Examining Annotated AllSky images
'Scope' first appears at 21:38:59. [Scope Connection was made at 21:38:49]
Target 1 (NGC 6500 w/SN), along with Target 2 & Target 3, first appears at 21:41. [TheSky6 scope connection was made at 21:41:30]
Focus Field 19 first appears at 21:45:42 (where it appears along with Targets 1 to 3). [ Focusing began at 21:44:15 ]
Target 0 (NGC 6500 w/SN) first appears at 21:48:49 (where it appears with 'Scope' still at the Focus Field 19 position). [ NGC 6500 w/SN started at 21:49:12]
Note: Although Target 0 (NGC 6500 w/SN) seems to appear on AllSky image before it was notified, the image is prepared some 30s+ after the time drawn on the annotated AllSky Image and can explain the apparet time discrepency. Review (2022-05-16) indicates that issue hasn't not been resolved despite multiple atttempts in 2021. Issue closed 2022-06-03 as the issue can't be readily fixed and it has been decided to remove the reporting of AllSky Measurement from Near Zenith Focusing in order to avoid waiting for a 30s time-out.
Closed 2022-06-03 (AstroMain 3.51.13)

Small Defects

Blue circle not drawn on realtime JPG pictures for minor planet target '2 Pallas' . Locate images plate solved ok and the target was centered ok. Asteroids (ProgramID=49) added to list of projects that set T.CircleRadiusMins to 0.5.
Fixed 2021-08-28 (AstroMain 3.41.5)
AstroMain log not showing a line break at start of Target 1/26 (NGC 6500). No line break (---------) between message lines from Focus Field 19 and message lines from NGC 6500. Earlier logs not showing line breaks between Targets cancelled due to weather conditions.
Fixed 2021-08-28 (AstroMain 3.41.5)

Continuous Improvement

Add 'M31 Nova' as a special case for Open Store Folder. Where Object is M31 and Transient = True (ie TNS_ID <> "") then the 'M31 Nova' folder should be opened instead of the 'M31' folder.
Notes: AstroPlan needs to be updated to handle this special case.
Should special case be extended to handle 'M33 Nova').
Should folder be called 'M31 Transients' instead of M31 Nova ?
Done 2021-08-28 (AstroMain 3.41.5)
Add 'M31_AT2021abc' as a special case for building FileNames. Where Object is M31 and Transient = True (ie TNS_ID <> "") then the file name should be in the format 'M31_AT2021abc.20210313.....gif' instead of 'M31.20210313.....gif'.
Done 2021-08-28 (AstroMain 3.41.5)
Modify Guide Summ Table to widen line breaks and ensure a space line is always present between Guide Runs. Line breaks (---------) between guide runs should be widened c 'Wind' column. When guiding is aborted (as in case of Guide Run 4) the code for writing the next Guide Run should ensure a space line is always present. The current table has Guide Run 5, continuing directly after Guide Run 6.
Done 2021-08-28 (AstroMain 3.41.5)
Modify Guide Summ Table to include AllSky Meas (excess sky brightness value). Sky Meas Column should be added to table. Line breaks (---------) between guide runs should be widened to be widened to include the new SkyMeas column.
Done 2021-08-28 (AstroMain 3.41.5)
Collect 1x1 -10deg C Master Dark frames for missing exposures, 30s in particular. 1x1 master darks frames are missing for the -10degC set temperature setting. New darks frames were collected in evening of 2021-08-28 (bias, 5s, 10s, 15s, 20s, 30s, 45s) and compiled into master darks on 2021-08-29.
Done 2021-08-28 (Session S909 Darks)
Create routines/workflow to send Spectra Images to RSpec for onwards processing and analysis
Done 2021-08-30 (AstroMain 3.41.5)
Create button routine for creating a Synthetic Flat (master flat frame with a constant value). Whilst a Dusk/Dawn Flat can be taken through a SA200 Filter, it's use for reduction of raw Spectral images is question. A flat normally a combination of the vignetting, defects/dusk on the filter and defect/dusk on the surface of the CCD Chip and variations between photosites themselves. Defect/dusk on the surface of the CCD Chip and photosites are relevant to correcting a first order spectra in an spectral image, but the x,y positions that the 1st order spectra photons falls on the CCD chip, are not the same as the x,y positions that light passed through the filter/grating. Correcting the raw spectral image pixels with the variations in light passage through the grating is potentially adding noise/defects to the image, rather than component /y positions defects/dusk on the filter are irre It is possible that no flat Aim is to create a synthetic Button routine currently placed on Analysis/ImageSets/Spectra tab, and builds a flat frame based on the current Active Image with constant value of 1000, appends SYNFLAT to file name and shows it with a histogram range 800 to 1050.
Done 2021-08-30 (AstroMain 3.41.5)
Modify Fits_Summary's 'X2_Modify_Object_Names' macro to insert 'MPL_' ahead of Minor Planets. Minor planets recognised as starting with "(" or starting with "19" or "20" provided that the first 4 characters of string is Numeric .
Done 2021-08-29 (Fits Summary)
Modify Fits_Summary's 'X2_Modify_Object_Names' macro to change particular star name formats. Change names like '27 Ser' to 'Ser_27'. Changes names like 'Alpha Ori' t0 'Ori_Alpha' names like .
Done 2021-08-29 (Fits Summary)
Modify Fits_Summary's 'X2_Modify_Object_Names' macro to simply code for dealing with C/19xx and C20xx comet names.
Done 2021-08-29 (Fits Summary)
Add 'Store' folder name field to AstroMain's Analysis/ImageSets tab which is automatically filled in when the imageset changes.
Done 2021-08-29 (Fits Summary)
Update GetObjectStoreFolder() routine in AstroMain and AstroPlan to reflect changes and enhancements to Store naming.
Done 2021-08-29 (AstroMain 3.41.5, AstroPlan 1.22.6)
Add 'Save Fix', 'Load Fix' button routine to Analysis/ImageSets Tab. Add buttons and routines to support the use of a FIX file to flat field correct a target FITS image.
Done 2021-08-30 (AstroMain 3.41.5)
Automatically 'Show Less' after running 'Kill Stranded Processes' routine (AstroLaunch). Additional menu items (including Kill Stranded Processes) to be hidden have routine has run.
Done 2021-09-01 (AstroLaunch 1.6.3)
Query: Is there any way to determine what the LX200 Scope has as it's Park Position setting without commanding a Park and observing where the scope moves to. At the moment if there is a doubt about Scope's Park Position because Scope was restarted from the Meridian/Dec 0 position and then re-synced/short mapping job, the scope has to be moved to its normal park position and the current position Set as Park Position from Scope's Controller. (Park Position can not be set via DeviceHub). It's unlikely that the coordinates currently set for the LX200's Park Position can be determined. However it is potentially feasible to slew to intended Park Position and use MeadeGeneric driver's handbox extension to manipulate the AutoStar II handbox to Set Park Position using 'Use Current'. To investigate. Handbox actions are "readdisplay"', "enter", "mode", "longmode", "goto", "0" to "9", "up", "down", "forward", "back", "?". Probably best to start with a virtual handbox and then consider a fully implemented 'SetParkPosition() routine : (with Slew to Az180/Alt 3, Set Park, UseCurrent). Tickets to create a virtual handbox and add a button routine to move scope to normal park position and then Set Park Position have been added to session S812 (2021-09-07)
Closed 2021-09-06 (LX200 / MeadeGeneric Driver)
Query: Is there any way for Job Executor/Obs.manager to determine that the lens cap has possibly been accidently left on front of the telescope. It would be helpful if the Obs.Manager could use some AI to determine that there was not only an absence of stars in images (which could be due to cloud), but that the nature of its background was likely to mean that there was an issue with either a) the CCD Shutter being closed, b) view of sky occuluded by Lens Cap or c) view of sky occuluded by the dome's roof and to raise a red alert and abort the session. It should be feasible to identify occulsion of light from reaching the camera attached to the telescope by consideration of the sky brightness measurements in ADU/arc sec^2/sec from images taken through the C Filter.
To Do 2021-08-28 (AstroMain 3.41.5)

[ Prev | Next ]

2021-08-28

Investigation - Target Position Failure (MPL 2 Pallas)

An attempt to image the minor planet 2 Pallas (forecast magnitude +8.9) was made at 2021-08-28 01:09 UT. Whilst basic acquisition was successful in that resulting image showed a starfield of focused stars positioned only 0.2 arc min from the planned RA/Dec coordinates that corresponded with the calculated position of TheSky6 minor planet '2 Pallas', the field proved to be located 3.81 degrees from the calculated position of TheSky6 extended minor planet MLP 2 Pallas derived from latest MPCORB.dat file.

Since computed positions of Extended Minor Planets are only valid for a 24 hour period, it is not practical to always restart TheSky6 to compute positions at start-up or manually click on Extended Minor Planets 'Compute' button to get positions corresponding to earlier Images. The compute process is slow (taking around 30s to compute the positions for some 1,120,272 minor planets (2021-08-28). This can be got around by copying specific minor planet details from 'Extended Minor Planets' to the Local 'Minor Planets', where the minor planet position can be readily obtained for any date/time.

Foward Actions
Delete minor planets in TheSky6 Minor Planets including '2 Pallas'

Open extended minor planet 'MPL 2 Pallas' in TheSky6 and click 'Copy to Local' from Object Information/Utility Tab
(details sent to ./User/Documents/Software Bisque/TheSky6/Minor planets/MinorPl.dat)

Access local minor planet as '(2) Pallas'
-it can also be accessed as 'Pallas'

Update '2 Pallas' target in AstroPlan and change name to '(2) Pallas'

Understand implications of object names using '( )' in names
   - AstroPlan is ok with Target Name '(2) Pallas'.
     - Historic and new Observing Plan charts show '(2) Pallas'. Historic Observing Results chart show '2 Pallas' if session predates name change.
     - Historic Sessions that acquired 2 Pallas images can still be picked up as reference is made via TargetID which is unchanged by name change.
     - If Object Name is (2) Pallas in 'Fit Summary.dat' then it is converted to 2_Pallas by the 'X2_Modify_Object_Names' macro
      when creating the session's Fits_Summary file
    - If Object Name were to be left as (2) Pallas (by editing the 'X2_Modify_Object_Names' macro) , then the A5_Group_Reduced_Fits' macro
       will create a folder with name like '(2)_Pallas 3x3 20s C' and copy reduced images to names like '(2)_Pallas.20210828.im909144.20s.C.FIT'
    - Image Sets can see/use folder like '(2)_Pallas 3x3 20s C' and show object name '(2) Pallas'
    - Store will try to access/create the store folder '(2) Pallas'

Understand if MinorPl.dat can be copied to Observatory Computer and immediately picked or it requires TheSky6 to be restarted
      - File can be copied to Observatory Computer ok with affecting an open TheSky6 program
      - Newly added minor planet is not immediately accessible in TheSky6
      - Newly added minor planets are accessible after restarting TheSky6 or individually going to Minor Planets,
        selecting the new minor planet, and then going to 'edit' & then clicking on 'Compute'

Understand the variations in Minor Planet naming
      - for the minor planet '2013 GB80' it is accessed using the name 'MPL 2013 GB80'. When it is copied to local it takes on the name '2013 GB80'
     - for the older minor planet '2003 EL61' it can no longer be accessed using the name 'MPL 2003 EL61', instead it is
       accessed as 'MPL 136108 Haumea'. which when copied to local takes on the name '136108 Haumea'.
       (this minor planet was officially named as dwarf planet 'Haumea' and is no longer referrable as '2003 EL61')
     - for the older minor planet '2004 DW, it is accessed using either the name 'MPL 2004 DW' or 'MPL 90491 2004 DW22'.
       when copied to local it takes the name '(90491) 2004 DW22'
     where is can be accessed by the name '90491', '2004 DW22' or '(90491) 2004 DW22'
     (note that accessing MPL 2004 DV4 isn't unique and returns 7 objects in TheSky,
      one of which is (144302) 2004 DV4, but others include 2004 DV41, 2004 DV42, 2004 DV47 etc
     MPL 2004 DV4 can't be accessed from AstroPlan but 2004 DV4 can
     after copying '2004 DV4' and '2004 DV47' to local   then either can be uniquely accessed using '2004 DV4' or '2004 DV47' as appropriate
- where target is named '2004 DV4' the FITS image have OBJCT = "2004 DV4", initially FITS files are named like '00000001._144302__2004_DV4.FIT
(but this is later cleaned up to become "00000001.FIT".   Fits Summary.dat shows files with object name '2004 DV4' which is modified to '2004_DV4' after importing to session Fits Summary .xls file.

Modify '>> Store' buttons to open up 'MPL 2 Pallas' folder

Modify Excel macro 'Modify Object Names' to change names in format '(2) Pallas' to 'MPL_2_Pallas'

Open other extended minor planets as required and Copy to Local.

SharpCap 4.0

The 4.0 version of SharpCap (4.0.81150.0, 64 bit, dated 2021-08-23) was downloaded and installed on Observatory Computer today (2021-08-28), but is not yet ready to use for live sessons. This is the first 4.0 version downloaded and installed since the first 4.0 build was first issued in June 2021

SharpCap Downloads: https://www.sharpcap.co.uk/sharpcap/downloads

4.0 Features

New features of version 4.0 that are most relevant to me are:

- New Sequencer (Sequence Planner)
- Still Mode
- Focuser position and mount co-ordinates added to capture settings file
- Fix FITS writing issue on ZWO cameras
- Bug Fixes
- Updated User Manual

SharpCap 3.2 - Remains live

The previous 3.2 version is still installed on the computer, which is useful since AstroLaunch and AstroMain are still currently still set up to start the 3.2 version, and there is a critical issue that is currently preventing the running of my AstroShCap.py script which provides a communication interface between AstroMain and SharpCap.

Critical Issue - Unable to run AstroShCap.py script in SharpCap 4.0

AstroShCap is a script which provides communication between AstroMain and SharpCap, and successful operation of the script is critical to live Observatory operations.
At the moment there is a showstopping issue.

Running script from C:\Data\ZWO Imaging\SharpCap\_Scripts\AstroShCap.py
C:/Data/ZWO Imaging/SharpCap/_Scripts/AstroShCap_version.py
Version: Point
VersionNo 1.3.11
Traceback (most recent call last):
File "<string>", line 4672, in <module>
File "<string>", line 129, in __init__
AttributeError: 'WindowProxy' object has no attribute 'Location'

Foward Actions

Check settings in 4.0 vs those in 3.2
Get AstroShCap.py to successfully run in 4.0
Check ZWO 178MC camera functionality via 4.0
Get AstroLaunch and AstroMain to point to SharpCap 4.0 instead of 3.2

3.2 settings:
Automatically restore camera settings
Save capture settings file alongside each capture
Start camera with 'Auto' output format

Preferred Video Format: SER
Preferred Image format: FITS
Startup Scripts :   C:\Data\ZWO Imaging\SharpCap\_Scripts\AstroShCap.py
Focuser:   ASCOM Pegasus UPB Focuser
    Connect hardware automatically when opening camera

Filenames Tab
Save captured files to : C:\Data\ZWO Imaging\SharpCap

Filename Templates:

Single File (Video): {TargetName}\{Time:Z}
Sequence Stills: {TargetName}\{Time:Z}\{TargetName}_{Index}
Live Stack: {TargetName}\LiveStack\{AutoSave}\Stack_{BitDepth}bits_{StackedFrames}frames_{TotalExposure}
Live Stack (Raw Frames): {TargetName}\LiveStack\rawframes\frame_{StackedFrames}
Live Stack (Processed): {TargetName}\LiveStack\processed\Stack_{StackedFrames}frames_{TotalExposure}

2021-08-30

Review - Spectra Processing and Analysis

A review of Spectra Processing And Analysis Workflows was conducted as part of a renewed initiative to improve skills in collection, processing and analysis of low resolution spectral data taken at my Observatory.

The Observatory's telescope (12" LX200GPS/R) is capable of collecting low resolution slitless spectral data using a Star Analyser 200. The SA 200 is a high quality transmission diffraction grating held in a 1.25" filter cell and is mounted into one of the positions in a SBIG CFW-10 filter wheel attached to a SBIG ST-10XME CCD Camera (KAF-401E) . This setup allows spectral imaging to be easily intermixed with general imaging (C), photometric imaging (BVRI) and special imaging (VR, Moon, Ha, L-Enhance) without changing equipment. A computer controlled focuser allows the telescope to be automatically focused according to filter. The SA 200's grating with 200 lines/mm, a constrained distance of 26.4mm from the CCD and 6.8 x 6.8 mm size photosites, combine to produce spectral images with a dispersion of 25.5 A/pixel (at 2x2 binning) or 12.25 A/pixel (at 1x1 binning). Images taken through the SA 200 grating are referred to having used the 'S' Filter. Telescope mount is autoguided during imaging using a CMOS camera on a guidescope that is securely attached to the main scope.

Overall Process

Setup :

SA-200 (S Filter) is installed in Filter Wheel with an orientation that produces spectra exactly aligning with horizontal rows on CCD
(currently orientation is ~ 3 deg from being horizontal)
Focus Position offset between S Filter and C (Main) Filter is determined (e.g -129 steps with TCF-S focuser)
Focus Position offset between zero order star and the middle of 1st order spectra is determined (best focus for spectra is different to best focus on the star itself)

Pre-Session :

Potential spectra targets are identified. These might include stars or other astronomical transients in outburst
A target is set up in the Targets Database including a one or more sets of S Filter images (e.g. 5 frames, full area, 2x2 binning, 30s)

Session

A schedular runs and targets (including spectral targets) are placed in the night's Observing Plan
A session is opened and the Observing Plan is executed autonomously (eg. 2021-08-27 S00909).
Targets are autonomously slewed to, centred, focused, autoguided and imaged,

Post-Session :

Image files are collated by CCD temperature, exposure, binning and filter (e.g "-10c 2x2 30s S")
Image files and images are reduced (i.e. pre-processing using master darks and master flats)
Reduced image files are grouped by target and imageset (e.g. "Nova_Cas_2021 2x2 30s S")
Spectral Image sets are opened/analysed
- Individual frames examined, bad frames rejected
- Frames aligned, and averaged to create spectral image (e.g. "Nova_Cas_2021.20210827.im909086-90.av5x30s.S.FIT")
- Spectral Image is plate solved if required. Target zero order star and first order spectra are identified.
- Spectral Image is 'sent' to RSpec (at the same time a folder for holding the target's spectra data is created or re-opened)
Spectral Image is processed in RSpec to get a raw spectra (in pixels)
- Spectral image is reviewed in left hand pane
- Image Histogram is adjusted (using either autostretch or manual controls)
- Image is rotated (typically this is a 183 deg rotation on order to get zero order star on left, and spectra directly to its right)
- Image area is cropped to exclude unnecessary image area to left and right of the object of interest
- 'Orange' Box is placed to include the target objects & its spectra (but avoid other stars & their spectra)
- Subtract background (typically a custom region above/below box) is used
- Raw spectra is reviewed in right hand pane
Raw spectra is calibrated in RSpec to get a Calibrated Spectra (in angstroms)
- One point or two point calibration can be used
- One point : involves defining the pixel position (barycenter) of the zero order star image and
calibrating using previously determined dispersion (e.g. 25.48 A/pixel for a 2x2 binned image).
- Two Point : involves defining the pixel position of the zero order star (0 Angstroms)
and the pixel position and wavelength of a readily identified emission or absoption line (eg. H alpha line at 6563 A)
- Calibrated Spectra Profile is saved to a .dat file (e.g Nova_Cas_2021.20210827.im909086-90.av5x30s.S.dat)
Calibrated spectra is corrected in RSpec to get a Corrected Spectra (in angstroms)
- New or Previously determined Instrumental Response appropriate for the setup, sky conditions and altitude of the target is loaded as as Reference Curve
- Calibrated Spectra (Profile) is divided by Instumental Response (Reference) to create Corrected Spectra result
- Corrected Spectra is 'moved' to Profile
- Corrected Spectra (Profile) is normalised by divided it by a constant to create a Corrected & Normalised Spectra result,
    where the constant is the Y value of Corrected Spectra at a specific wavelength
    (e.g 3.4 at 5400 A, such that when divided by 3.4 the result is normalised and has the value 1.0 at 5400 A)
   Note: To identify Y value associated with a specific wavelength hover the house over the spectra profile to see both Wavelength and Y Intensity. However to get this Y value to show, it is necessary to have the Measure lines visible (but not the Elements window).
Note: unless modified the Y value is a unitless relative intensity that is the sum between the orange lines of one column in the image)

- Corrected & Normalised Spectra result is 'moved' to Profile
- Delete any invalid parts of the spectra (between threshold lines or crop to current zoom)
- Corrected & Normalised Spectra is saved (e.g. "Nova_Cas_2021.20210827.spectra.dat")
- Relevant Lines are added to the Spectra Profile and the image saved (e.g 'Nova_Cas_2021.20210827.spectra.png')
Finished Spectra can be loaded into RSpec's Presentation Manager for further analysis
- Previous or newly created Presentation is loaded/prepared.
- New spectra is loaded as a new row, and compared with previous spectra or with reference curves etc.
- Add .dat file from new spectra to a new row
- Add legend for new row
- Adjust Offset to space out spectra (if/as required)
- Check/add Line as required
- Save Presentation (e.g. "Nova_Cas_2021.Spectra.xml" )
- Save Image (e.g. "Nova_Cas_2021.Spectra.png" )

Notes:
- RSpec SaveTo Dialog can accept clicking on shortcuts to one folder to directly move to another
- RSpec SaveTo Dialog can accept file names like "Spectra\Test.dat" which saves file in the current folder's subfolder 'Spectra'
(this saves needing to click on subfolder)
- RSpec doesn't like Saving Profile (.dat) to a current actively monitored folder.
Whilst .dat file is saved ok , the process also saves an .ini file which leads to a RSpec error dialog popping up "Error opening file .ini Invalid stream format..."

Instrumental Response :

Foward Actions

This Web Page:	Notes - Session 909 (2021-08-27)
Last Updated :	2024-03-23
Site Owner :	David Richards
Home Page :	David's Astronomy Web Site

David's Astronomy Pages Notes - Session 909 (2021-08-27)