<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[Skyhound Forums - Minor Planet and Comet Astrometry]]></title>
		<link>https://skyhound.com/forums/</link>
		<description><![CDATA[Skyhound Forums - https://skyhound.com/forums]]></description>
		<pubDate>Fri, 03 Apr 2026 22:20:33 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Alert - Minor Planet Appulse]]></title>
			<link>https://skyhound.com/forums/showthread.php?tid=2530</link>
			<pubDate>Thu, 12 May 2022 18:07:28 -0400</pubDate>
			<dc:creator><![CDATA[<a href="https://skyhound.com/forums/member.php?action=profile&uid=1306">bigmasterdrago</a>]]></dc:creator>
			<guid isPermaLink="false">https://skyhound.com/forums/showthread.php?tid=2530</guid>
			<description><![CDATA[A very close approach of two bright asteroids begins in several hours. Although not visible from North America, others will have better luck. Namely, South America, UK and Europe. Best at 00:00 UT, asteroids 240 Vanadis and 233 Asterope may be seen to nearly merge.<br />
<br />
Tom Polakis has been imaging these 12th and 13th magnitude rocks for several nights. <a href="https://pbase.com/polakis/image/172595509" target="_blank" rel="noopener" class="mycode_url">https://pbase.com/polakis/image/172595509</a><br />
<br />
From my location the minimum separation of these two rocks would be 4.3 arc seconds at 6:04UT on the 13th. But 30+° below my SW horizon.]]></description>
			<content:encoded><![CDATA[A very close approach of two bright asteroids begins in several hours. Although not visible from North America, others will have better luck. Namely, South America, UK and Europe. Best at 00:00 UT, asteroids 240 Vanadis and 233 Asterope may be seen to nearly merge.<br />
<br />
Tom Polakis has been imaging these 12th and 13th magnitude rocks for several nights. <a href="https://pbase.com/polakis/image/172595509" target="_blank" rel="noopener" class="mycode_url">https://pbase.com/polakis/image/172595509</a><br />
<br />
From my location the minimum separation of these two rocks would be 4.3 arc seconds at 6:04UT on the 13th. But 30+° below my SW horizon.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[C/2019 Q4 (Borisov) - First Interstellar Comet!]]></title>
			<link>https://skyhound.com/forums/showthread.php?tid=611</link>
			<pubDate>Wed, 11 Sep 2019 17:17:08 -0400</pubDate>
			<dc:creator><![CDATA[<a href="https://skyhound.com/forums/member.php?action=profile&uid=1">theskyhound</a>]]></dc:creator>
			<guid isPermaLink="false">https://skyhound.com/forums/showthread.php?tid=611</guid>
			<description><![CDATA[The Minor Planet Center just released an orbit for C/2019 Q4 (Borisov) and I have added it to the current comets target list. <br />
<br />
This comet was only recognized yesterday as being of interstellar origin (a first). It is currently brighter than 19th mag.]]></description>
			<content:encoded><![CDATA[The Minor Planet Center just released an orbit for C/2019 Q4 (Borisov) and I have added it to the current comets target list. <br />
<br />
This comet was only recognized yesterday as being of interstellar origin (a first). It is currently brighter than 19th mag.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Will not update new objects]]></title>
			<link>https://skyhound.com/forums/showthread.php?tid=157</link>
			<pubDate>Tue, 27 Feb 2018 15:52:54 -0500</pubDate>
			<dc:creator><![CDATA[<a href="https://skyhound.com/forums/member.php?action=profile&uid=183">ncwolfie</a>]]></dc:creator>
			<guid isPermaLink="false">https://skyhound.com/forums/showthread.php?tid=157</guid>
			<description><![CDATA[Why can or I not update the database to include new minor planets, namely NEO's? <br />
I have downloaded the MPCOrb.dat file, then tried update by the to read option but nothing gets updated. <img src="https://skyhound.com/forums/images/smilies/huh.png" alt="Huh" title="Huh" class="smilie smilie_17" /> <br />
<br />
<br />
Thanks<br />
Randy]]></description>
			<content:encoded><![CDATA[Why can or I not update the database to include new minor planets, namely NEO's? <br />
I have downloaded the MPCOrb.dat file, then tried update by the to read option but nothing gets updated. <img src="https://skyhound.com/forums/images/smilies/huh.png" alt="Huh" title="Huh" class="smilie smilie_17" /> <br />
<br />
<br />
Thanks<br />
Randy]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Minor Planet List type ID request]]></title>
			<link>https://skyhound.com/forums/showthread.php?tid=35</link>
			<pubDate>Tue, 02 Jan 2018 13:06:52 -0500</pubDate>
			<dc:creator><![CDATA[<a href="https://skyhound.com/forums/member.php?action=profile&uid=183">ncwolfie</a>]]></dc:creator>
			<guid isPermaLink="false">https://skyhound.com/forums/showthread.php?tid=35</guid>
			<description><![CDATA[Doing minor planet astrometric work, I will often use SkyTools3 to generate an observing list of minor planets (alongside of the Minor Planet Centers list generator). I concentrate mainly on NEO's and use the database search tool to put my list together, I am able to single out what particular type asteroids are, Aten's, Apollo's etc. However when I generate my list, the only ID shown of the minor planets selected is the name and or number ID. Is there a way to also list what type of asteroid it is? For example, I print out a list of asteroids visible for the night. While I could see what type of each was in the database search, once I create the list and print it, I only have names and numbers, nothing to tell me the types. It would be great if the types were also listed. Maybe I am overlooking something.<br />
<br />
Thanks and best regards,<br />
Randy]]></description>
			<content:encoded><![CDATA[Doing minor planet astrometric work, I will often use SkyTools3 to generate an observing list of minor planets (alongside of the Minor Planet Centers list generator). I concentrate mainly on NEO's and use the database search tool to put my list together, I am able to single out what particular type asteroids are, Aten's, Apollo's etc. However when I generate my list, the only ID shown of the minor planets selected is the name and or number ID. Is there a way to also list what type of asteroid it is? For example, I print out a list of asteroids visible for the night. While I could see what type of each was in the database search, once I create the list and print it, I only have names and numbers, nothing to tell me the types. It would be great if the types were also listed. Maybe I am overlooking something.<br />
<br />
Thanks and best regards,<br />
Randy]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[A Very Marginal Image of a Comet]]></title>
			<link>https://skyhound.com/forums/showthread.php?tid=15</link>
			<pubDate>Thu, 16 Nov 2017 20:13:58 -0500</pubDate>
			<dc:creator><![CDATA[<a href="https://skyhound.com/forums/member.php?action=profile&uid=1">theskyhound</a>]]></dc:creator>
			<guid isPermaLink="false">https://skyhound.com/forums/showthread.php?tid=15</guid>
			<description><![CDATA[So this is likely one of the worst images of a comet you are going to see. But that was sort of the point. This is a Track &amp; Stack in Astrometrica of three 4-min exposures from last night. The remote imaging system used was T21, located just a few miles down the road in Mayhill, NM, via iTelescope.com. It is a Planewave 17" CDK with an FLI-PL6303E camera. <br />
<br />
As with most of my imaging these days, this was a SkyTools 4 test. A little backstory first: stellar and diffuse objects are modeled differently. A diffuse object, such as a nebula or galaxy, is modeled as one typical image pixel sampling a continuous surface brightness. A stellar object is modeled as a Gaussian Point Spread function. The details aren't really important-what matters is that comets are both of these things, and to varying degrees depending on the comet. Some comets look like stars with no visible coma, while others are completely diffuse, with no central bright spot. Most lie somewhere in between. This makes comets really difficult to model.<br />
<br />
SkyTools 4 told me that comet 250P/Larsen would be high in the sky at around 3 AM, and with an integrated magnitude of 19.1, SkyTools predicted that it would be a difficult target. In fact, SkyTools predicted that even once I stacked three 4-min exposures the Signal to Noise Ratio (SNR) would only be 8. An SNR of at least 5 is typically required to do fairly accurate astrometry. So SkyTools was predicting that this would be a marginal observation. <br />
<br />
And indeed it was! The SNR measured by Astrometrica was 6, which is quite close. This relatively small difference is actually quite remarkable, given how difficult comets are to model. Being able to fairly accurately predict how long of an exposure is required to obtain good astrometry is a rather useful thing! <br />
<br />
Incidentally, SkyTools 4 also told me that the comet would only move by 3 pixels over the course of the three exposures, and that it would move by 1 pixel during each of them.<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://skyhound.com/forums/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=4" target="_blank" title="">Astrometrica.png</a> (Size: 245.62 KB / Downloads: 35)
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[So this is likely one of the worst images of a comet you are going to see. But that was sort of the point. This is a Track &amp; Stack in Astrometrica of three 4-min exposures from last night. The remote imaging system used was T21, located just a few miles down the road in Mayhill, NM, via iTelescope.com. It is a Planewave 17" CDK with an FLI-PL6303E camera. <br />
<br />
As with most of my imaging these days, this was a SkyTools 4 test. A little backstory first: stellar and diffuse objects are modeled differently. A diffuse object, such as a nebula or galaxy, is modeled as one typical image pixel sampling a continuous surface brightness. A stellar object is modeled as a Gaussian Point Spread function. The details aren't really important-what matters is that comets are both of these things, and to varying degrees depending on the comet. Some comets look like stars with no visible coma, while others are completely diffuse, with no central bright spot. Most lie somewhere in between. This makes comets really difficult to model.<br />
<br />
SkyTools 4 told me that comet 250P/Larsen would be high in the sky at around 3 AM, and with an integrated magnitude of 19.1, SkyTools predicted that it would be a difficult target. In fact, SkyTools predicted that even once I stacked three 4-min exposures the Signal to Noise Ratio (SNR) would only be 8. An SNR of at least 5 is typically required to do fairly accurate astrometry. So SkyTools was predicting that this would be a marginal observation. <br />
<br />
And indeed it was! The SNR measured by Astrometrica was 6, which is quite close. This relatively small difference is actually quite remarkable, given how difficult comets are to model. Being able to fairly accurately predict how long of an exposure is required to obtain good astrometry is a rather useful thing! <br />
<br />
Incidentally, SkyTools 4 also told me that the comet would only move by 3 pixels over the course of the three exposures, and that it would move by 1 pixel during each of them.<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://skyhound.com/forums/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=4" target="_blank" title="">Astrometrica.png</a> (Size: 245.62 KB / Downloads: 35)
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
	</channel>
</rss>