summaryrefslogtreecommitdiff
path: root/aurora_in_mielno_may_2024.html
diff options
context:
space:
mode:
authorAki <please@ignore.pl>2024-07-08 21:25:40 +0200
committerAki <please@ignore.pl>2024-07-08 21:25:40 +0200
commit899ea7ddd0fb1f976996c0c0678c387b61ff3f63 (patch)
treeb2dd6f08518747df2f7fa9b89c1e7a7112eee026 /aurora_in_mielno_may_2024.html
parent4fa63db65a32d7a8b819e7aca818a0688b0e60b6 (diff)
downloadignore.pl-899ea7ddd0fb1f976996c0c0678c387b61ff3f63.zip
ignore.pl-899ea7ddd0fb1f976996c0c0678c387b61ff3f63.tar.gz
ignore.pl-899ea7ddd0fb1f976996c0c0678c387b61ff3f63.tar.bz2
Added reference to SWPC article on 3664 region
Diffstat (limited to 'aurora_in_mielno_may_2024.html')
-rw-r--r--aurora_in_mielno_may_2024.html4
1 files changed, 3 insertions, 1 deletions
diff --git a/aurora_in_mielno_may_2024.html b/aurora_in_mielno_may_2024.html
index 6c125d6..284cde8 100644
--- a/aurora_in_mielno_may_2024.html
+++ b/aurora_in_mielno_may_2024.html
@@ -58,6 +58,8 @@ enough. Luckily, I am persistent and managed to get some photos despite that:</p
<p>Stormwatch persisted through the Sunday as another CMEs were expected to reach Earth. Sadly, the activity started
going up only after local midnight and having a working day on Monday I decided to not gamble. It was the correct
decision as it reached only G2 and a G3 warning persisted through to the Monday.
-<p>Later that week the region 3664 rotated out of the view.
+<p>Later that week the region 3664 rotated out of the view. It came back as 3697 and 3723.
+<p>For detailed story, check out <a href="https://storymaps.arcgis.com/stories/0c501560633549b69dbd01c4c725b2b3">The
+Evolution and Impact of Active Region 13664</a> by Briana Muhlestein, Senior Weather Forecaster.
</article>
<script src="https://stats.ignore.pl/track.js"></script>