<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>What's new on DeepSkyLog</title><link>https://deepskylog.space/whats-new/</link><description>Recent content in What's new on DeepSkyLog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://deepskylog.space/whats-new/index.xml" rel="self" type="application/rss+xml"/><item><title>The DeepSkyLog Uploader: bring your FITS archive into DeepSkyLog</title><link>https://deepskylog.space/whats-new/deepskylog-uploader/</link><pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate><guid>https://deepskylog.space/whats-new/deepskylog-uploader/</guid><description>&lt;p&gt;Years of captures sit in folders on a disk or a NAS, and until now bringing them into DeepSkyLog meant the browser import or the command-line tool. The DeepSkyLog Uploader is a desktop app for exactly that, and it works on every plan.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://deepskylog.space/images/screenshots/uploader-sessions.jpg" alt="The DeepSkyLog Uploader after a scan: one line per target, night and filter, with frames, integration time and star size"&gt;&lt;/p&gt;
&lt;h2 id="what-it-does"&gt;What it does&lt;/h2&gt;
&lt;p&gt;Point it at your session folders and press &lt;strong&gt;Scan&lt;/strong&gt;. It reads every FITS and XISF light frame, skips darks, flats, bias frames and stacked files, and shows what it found as sessions: one line per target, night and filter, with the frame count, the integration time and the star size.&lt;/p&gt;</description></item><item><title>Add your local horizon to improve planning</title><link>https://deepskylog.space/whats-new/local-horizon-and-planning/</link><pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate><guid>https://deepskylog.space/whats-new/local-horizon-and-planning/</guid><description>&lt;p&gt;A target at 40 degrees is no use if it&amp;rsquo;s behind your neighbor&amp;rsquo;s roof. Until now planning only knew a flat minimum altitude. Locations can now carry a local horizon, and every planning view uses it.&lt;/p&gt;
&lt;h2 id="the-rule"&gt;The rule&lt;/h2&gt;
&lt;p&gt;A target counts as usable when its altitude is above both:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the horizon at its current azimuth, and&lt;/li&gt;
&lt;li&gt;your minimum altitude setting.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The minimum altitude keeps its job (seeing, airmass). The horizon only adds the obstructions. A location without a horizon behaves exactly as before.&lt;/p&gt;</description></item><item><title>Planning around the moon: which filter tonight?</title><link>https://deepskylog.space/whats-new/planning-around-the-moon/</link><pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate><guid>https://deepskylog.space/whats-new/planning-around-the-moon/</guid><description>&lt;p&gt;A bright moon doesn&amp;rsquo;t have to mean a lost night. It only rules out some filters. Plan Ahead now works out which ones.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://deepskylog.space/images/screenshots/plan-ahead.jpg" alt="Plan Ahead with the moon row, the altitude chart and ranked projects"&gt;&lt;/p&gt;
&lt;h2 id="why-the-moon-matters-more-to-some-filters"&gt;Why the moon matters more to some filters&lt;/h2&gt;
&lt;p&gt;Moonlight is scattered sunlight, spread across the whole visible spectrum. A broadband filter (L, R, G, B) collects all of it, so LRGB wants the moon below the horizon.&lt;/p&gt;</description></item></channel></rss>