Jump to content

Featured Replies

It was a filament eruption that resulted in a nice CME. But it appears to be headed southwest for the most part. We might receive a glancing blow at best

B4D7C5BC-6D1D-4E20-A515-CF765FE98A4D.jpeg

  • Replies 755
  • Views 96.6k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Marcel de Bont
    Marcel de Bont

    The user Sunlive123 received a ban after a grossly out of line post in this topic combined with a history of previous problematic posts. In case you read this Sunlive, our ads are needed to keep SWL r

  • MinYoongi
    MinYoongi

    Oh my God, would you please be so kind and stop saying such nonsense all the time? A filament is definitely not to blame for Goes' data problems and that alone doesn't fit in terms of time. You alone

  • dayum whatever just happened was so powerful a f***ing minecraft block flew out of the sun

Posted Images

23 minutes ago, Isatsuki San said:

@Jesterface23What do you think about this being quite slow or normal?

I came into this topic a minute before the mention Heh

 

The initial filament release everyone is looking at around 01:00Z I think can be put to the side, it is too slow.

STEREO A seems to have captured a possible 2nd CME release slightly east of the above filament eruption at around 03:00Z. This one is still somewhat slow, but may have the chance to impact L1 if the ambient solar wind velocities aren't too high. Will wait for more imagery.

Edited by Jesterface23

I wish we had Solar Demon right now so we could see the shock wave better because on SUVI 195 it looks like material released almost all the way to center disc.

The areas above and below ar 3924 look like they open up and let go straight ahead. This was a pretty interesting series of events for sure.

Edited by Cokelley

All I can say is the CME could arrive on the 18th or 19th. A C3 data feed is down and there isn't much for me to work with. We've entered a CH HSS and it probably wont survive the transit if the solar wind velocities remain elevated.

6 hours ago, Jesterface23 said:

All I can say is the CME could arrive on the 18th or 19th. A C3 data feed is down and there isn't much for me to work with. We've entered a CH HSS and it probably wont survive the transit if the solar wind velocities remain elevated.

Ah, is it because of the crown hole that EPAM is elevated?

10 minutes ago, Isatsuki San said:

Ah, is it because of the crown hole that EPAM is elevated?

We went through some sort of solar wind transition along with all the solar eruptions happening. We are either in a CIR/HSS mix or flux rope currently with how low the temperatures are right now. Time may tell.

Something interesting happened inside of this filament over the last few hours, does someone perhaps know what exactly happened there?
image.png?ex=67619191&is=67604011&hm=254c1ecb05e446547eb3a6433438b2f2bccfb7a149fbba806e9a3e3f8d7fcbd4&

2 hours ago, Luca Remenji said:

Something interesting happened inside of this filament over the last few hours, does someone perhaps know what exactly happened there?
image.png?ex=67619191&is=67604011&hm=254c1ecb05e446547eb3a6433438b2f2bccfb7a149fbba806e9a3e3f8d7fcbd4&

Edit: there wasn’t a cme associated I think it was reabsorbed

Edited by yahya
Updated info

Is that a filament breaking off on the SW limb? Starting at about 12:33UTC, and still going (current last image on SUVI 304A 14:21UTC).

Looks like there’s a weak proton event (10mev reached S0) I’m assuming a filament eruption is behind it given the low X-ray flux ? 

8 hours ago, Jay said:

Looks like there’s a weak proton event (10mev reached S0) I’m assuming a filament eruption is behind it given the low X-ray flux ? 

@NightSky

There's a data gap in lasco c2 and c3 imagery around the time of the possible filament release ejection so it is hard to say if that is responsible because I can't make out any ejections that may or may not have happened. It does look like the filament moved in SUVI 195 but I can't make out any dimming to be sure of a release. maybe @MinYoongi @Parabolic or @Jesterface23 has some more info on that?

That being said, a big prominence did just lift off from the north west limb area recently, around 11utc. It is a big one ! Thanks to Solarham.com for the heads up!

Edited by Cokelley

Filament lift near 3939 around 19:30 UTC - staying just below M-flare.

1 hour ago, NightSky said:

Filament lift near 3939 around 19:30 UTC - staying just below M-flare.

Good catch ! I just noticed that on SUVI 195. It looks like it is still lifting possibly !

Something is brewing just under the surface, keeping the baseline just a hair below the M-line.

 

There's a neat looking "circle of fire" near the 3939, slowly expanding outwards. Visible on 304A. I don't remember seeing one before, so those of you who have seen it all - is that something that happens all the time?

 

 

10 minutes ago, NightSky said:

Something is brewing just under the surface, keeping the baseline just a hair below the M-line.

 

There's a neat looking "circle of fire" near the 3939, slowly expanding outwards. Visible on 304A. I don't remember seeing one before, so those of you who have seen it all - is that something that happens all the time?

 

 

The same happened before the X9 from 3842

20 minutes ago, Ukrspotter said:

The same happened before the X9 from 3842

REALLY? 😲

Anyone have a link to that? I assume the animations are available somewhere?

 

 

1 hour ago, Ukrspotter said:

The same happened before the X9 from 3842

We have m baseline 🥲 this brings a tear to my eye it’s so amazing 

An m Baseline is rough on the skin for a sunburn, if you follow my drift. Aussies will need some sunscreen for now.

It’s like every active region on the earth facing disk wants to flare right now 😂

The whole sun is an mflare at rest. One sneezE and it will go straight into x land. At this point I don't think earth direction is an issue. The question is how long does the burn continue.? Solar winds are starting to pick up, too.

Guest
This topic is now closed to further replies.

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you also agree to our Terms of Use and our Privacy Policy.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.