I have a personal spectroscopy project I want to conduct using objects (stars) from GAIA DR3. I can create a CSV file with my selected stars that includes the GAIA source_id, ra, dec, and magnitude. Is there a simple way to create an observing list from a csv file. I know that I can import object designations and that ST4 will attempt to match them with the included catalogs, but that seems to be a one-at-a-time process and I don't think it is posible to match GAIA source_id's. And I don't need to match these stars with other catalogs. I can work with the GAIA source_id as the ST4 Primary ID in the list. Is my objective clear? Am I phrasing this question correctly?

Antone

Is there a way auto-create observations by scanning a directory-tree of .FITS files?  I would like to track projects that I have started years ago but are not complete.  It will be quite tedious to manually enter each night's observations to determine the total data I have collected over the years.  I use ACP and Scheduler gives me a good feel for my progress but sometimes I'll modify plans in Scheduler which would skew its description of progress.  And in some cases some data were collected without ACP.  I use PixInsight's batch-preprocessing script to quickly read a directory-tree of my light frames taken on a given target over the years and it will conveniently compute total exposure for each filter for the entire tree of files.  It would be great to have something similar in SkyTools so I can save this and track progress over time.  Going a bit further... getting PixInsight to compute quality statistics on the observations and store that in the project would be fantastic as well.

CNEOS predicts that the NEO 2022 TN1 will make a close approach on 2024-Apr-30 23:57 ± < 00:01 UT at a distance of 0.04766 AU. It's already 15.2 magnitude in Virgo.

I'll try to provide more information later today.

Good hunting,

Phil S.

I used ST V2 for years and finally decided to try V4.1.  I run a ASA600 scope in Chile and I have correctly entered the lat/long of the telescope and no matter what I do, the object list only shows objects visible in the N. Hemisphere.  That is completely useless to me.  How to I get the software to correctly display object visible from the telescope location?

Thanks,
John

Hi Greg,

Searching for objects in ST is something I do very often, it's perhaps the most often used function for me. AFAIK, currently it involves using the mouse twice so it's less efficient than I'd wish it were. 

To open the search dialog, I need to click on Tools then Designation Search. There is no accelerator key for either (otherwise, Alt-T then S would have been acceptable; a single global shortcut like F3 ideal).

I then can perform the search by typing the criterion than hit Enter. This is fine.

But to open the first result of the search (which most often is the desired one), I have to use the mouse again. I cannot move the focus out of the search textbox by pressing Tab (if I do, it types that special character in which replaces what I searched for). If Tab moved the focus to the Search button then to the results, pressing Tab twice and enter on the first result (or going down in the list with the down arrow key) would have been very fine.

In the field, with the laptop, I miss the keyboard even more because using the touchpad is not as fast or precise than a mouse and if I have a glove, it may not work at all. Sometimes I carry a Bluetooth mouse, but it requires a surface and it's an extra object.

Is there a way to achieve the above? If not, could it be in the future?

Thanks,
Razvan

Hi all

Firstly I apologies if this is a constant question, but I am baffled by databases at the best of times.

I have an understanding of the basics of planning a night session, what I am having issues with are the types etc.

I want to create an evenings viewing by being able to see what stars are about, where my issue lay is where in the database do I click to give me just stars, SAO, Hip etc. I can see Messier and the like but nothing singular for a star.

I would welcome any feedback and again apologies if this question has been raised but I dont know what to ask in search.

Many thanks and good to meet you all.

Terry

CNEOS predicts that the newly discovered NEO, 2024 HK1, will make a close approach on  2024-May-04 19:20±03:36 UT at a distance of 0.00460 AU moving with V Relative=8.67 km/sec. H=25.4 magnitude, diameter 22 m - 49 m and 'Rarity'=1. There is a  2 day observation arc, the Condition Code=8 and the Earth MOID=0.00459959 AU. The solution date was 2024-Apr-24 18:12:02 PDT. The initial reported observation was by Pan-STARRS 2, Haleakala on 2024-04-21. This object's orbit will be refined over the next few days to provide more accurate predictions of its position.

I'll provide another update after the orbit is refined further. This object will probably be best from the southern hemisphere.

Phil S.

Hello Everyone,

Please perform a full backup before you download and apply the update to version 4.x.11.06. I had two reports about problems with log entries right after I released this update, so I pulled it out of an abundance of caution. But the problems seem unrelated to each other and unrelated to the update. Therefore I am going to make the update available once again. Just in case there is a problem with the update after all, making a backup via the Tools menu before applying it will ensure your data is safe.

CNEOS predicts that the newly discovered NEO, 2024 HY, will make a close approach on 2024-Apr-22 17:50±<00:01 UT at a distance of 0.01471 AU moving with V Realative=9.22 km/sec, H=23.3 magnitude, diameter 57 m - 130 m and 'Rarity'=1. There is a 1 day observation arc, the Condition Code=7 and the Earth MOID=0.00745199 AU. The solution date is 2024-Apr-22 05:48:07 PDT. The initial reported observation was by ATLAS Chile, Rio Hurtado on 2024-04-20. CNEOS predicts that it will pass within 0.00832 AU on 2036 Apr 23, so it will probably make it on MPC's list of Potentially Hazardous Asteroids (PHAs).

Using MPC's elements downloaded on 2024 Apr 22 0000 UT, ST4Visual predicts that this NEO reached a maximum brightness of 15.6 magnitude on April 21 ~2300 EDT while travelling through Crater at 50"/minute. This object should be visible in a 13" telescope on April 22 at 2200 EDT moving through Leo at 15.9 magnitude and 0.01 AU distant with apparent motion of 52.1"/minute. Close approach is predicted (to the nearest hour) on 2024 Apr 22 1400 EDT when the NEO is predicted to be 15.8 magnitude moving through Leo at 52.1"/minute, but in daylight and below the horizon as seen from Columbus, Ohio.

Here's the Object Info dialog for this NEO: [attachment=3078]

Good hunting,

Phil S.

CNEOS predicts that the newly discovered NEO, 2024 GN2, will make a close approach on 2024-Apr-16 14:20±00:01 UT at a distance of 0.00312 AU moving with V Relative=18.51 km/sec, H=26.4 magnitude, diameter 14 m - 31 m and 'Rarity'=1. The orbit has been refined over a 5 day observation arc. The Condition Code=8 and the Earth MOID=0.00303177 AU. The solution date is 2024-Apr-14 06:17:36 PDT. The orbit has been refined since it first appeared on the MPC's list of NEAs at Today's Epoch downloaded by SkyTools on April 11. The initial reported observation was by Pan-STARRS 2, Haleakala on 2024-04-09. This NEO will probably be added to MPC's list of Potentially Hazardous Asteroids due to the small MOID value.

Using MPC's orbital elements for 2024 Apr 14 0000 UT, ST4v predicts that this NEO will reach a maximum brightness of 16.3 magnitude on (to the nearest hour) 2024 Apr 16 0500 EDT at 556.5k km distance moving through Crux at 300"/minute, below the horizon as seen from Columbus, Ohio. Close approach (to the nearest hour) is predicted on 2024 Apr 16 1000 EDT at 468.5k km distance and 17.0 magnitude moving through Mensa at 476"/minute, still below the horizon  and in daylight as seen from Columbus, Ohio. This object will be best seen from the southern hemisphere.

Here's the Object Info dialog for this NEO: [attachment=3077]

Anyone wishing to observe this object should download orbital elements from the MPC's NEAs at Today's Epoch datafile or JPL's HORIZON website near the time of the close approach, since parallax will affect the apparent position of the nearby NEO relative to the stars.

Good hunting,

Phil S.