Jump to content

Featured Replies

Solved by Jesterface23

Go to solution
  • Popular Post
51 minutes ago, Jay-B said:

What is causing these reverse or negative readings on the solar flares page?

 

 

Screenshot 2024-02-28 092946.png

Every six months near the equinoxes, the satellite is eclipsed by the Earth about month, and this causes such gaps in the graphs 

13 minutes ago, tniickck said:

Every six months near the equinoxes, the satellite is eclipsed by the Earth about month, and this causes such gaps in the graphs 

Sometimes this situation can happen during a solar eclipse. I'm telling the truth?

No such thing as a reverse flare.

This was not in this case the GOES satellites being eclipsed.  No eclipse is seen in the SDO imagery for these dip timeframes.

This is a data dropout where flux was reported as 0.0 for some reason for the periods of the dips, as seen in the reported numeric data available at services.swpc.noaa.gov/json/goes/primary/

{"time_tag": "2024-02-28T05:06:00Z", "satellite": 16, "flux": 9.999999717180685e-10, "observed_flux": 3.015147953533415e-08, "electron_correction": 3.3437931534763266e-08, "electron_contaminaton": true, "energy": "0.1-0.8nm"}, {"time_tag": "2024-02-28T05:07:00Z", "satellite": 16, "flux": 0.0, "observed_flux": 0.0, "electron_correction": 1.2745965172200613e-08, "electron_contaminaton": true, "energy": "0.05-0.4nm"}, {"time_tag": "2024-02-28T05:07:00Z", "satellite": 16, "flux": 0.0, "observed_flux": 0.0, "electron_correction": 3.395538072936688e-08, "electron_contaminaton": true, "energy": "0.1-0.8nm"}, 

Hi, there were such failures in 2021, 2022, 2023, at the same time. In 2022, the failure was also on February 27. It doesn't look like a glitch, while other graphs show magnetic fluctuations.Screenshot_2024-02-28-23-22-01-426_org.telegram.messenger.thumb.jpg.3d0f1eb6e74ae249738764d3a273c079.jpg

  • Popular Post
1 uur geleden, Drax Spacex zei:

This was not in this case the GOES satellites being eclipsed.  No eclipse is seen in the SDO imagery for these dip timeframes.

SDO is in an inclined geosynchronous orbit and GOES is in a geostationary orbit. So when GOES eclipses you'll not see it on SDO as it is in a different orbit.

1 uur terug, Gerasev22 zei:

there were such failures in 2021, 2022, 2023, at the same time

Not failures, just eclipse season that has started just like @Jesterface23 has pointed out. Luckily we have a secondary satellite as a backup when one GOES is in eclipse. 

But why would the flux suddenly drop to 0.0?  The answer is in the text of the above GOES link:

"There is a significant risk of light from the sun directly entering the scanners on GOES-16/17/18 and causing degraded products as the spacecraft enters and leaves the Earth's shadow. To minimize this risk, a special algorithm is applied to the imager products. In some instances, shifting, canceling, or truncating the frame is necessary."

57 minuten geleden, Jesterface23 zei:

It is due to an eclipse from when the Earth gets in the way of the Sun and GOES satellites. Double checking the orbits and it is the case in this situation.

https://www.ospo.noaa.gov/Operations/GOES/eclipse.html

Exactly. This. It happens to SDO as well. SDO and GOES eclipses do not occur at the same time because these satellites are in different orbits and points in space.

2 hours ago, Drax Spacex said:

This was not in this case the GOES satellites being eclipsed.  No eclipse is seen in the SDO imagery for these dip timeframes.

This is a data dropout where flux was reported as 0.0 for some reason for the periods of the dips, as seen in the reported numeric data available at services.swpc.noaa.gov/json/goes/primary/

{"time_tag": "2024-02-28T05:06:00Z", "satellite": 16, "flux": 9.999999717180685e-10, "observed_flux": 3.015147953533415e-08, "electron_correction": 3.3437931534763266e-08, "electron_contaminaton": true, "energy": "0.1-0.8nm"}, {"time_tag": "2024-02-28T05:07:00Z", "satellite": 16, "flux": 0.0, "observed_flux": 0.0, "electron_correction": 1.2745965172200613e-08, "electron_contaminaton": true, "energy": "0.05-0.4nm"}, {"time_tag": "2024-02-28T05:07:00Z", "satellite": 16, "flux": 0.0, "observed_flux": 0.0, "electron_correction": 3.395538072936688e-08, "electron_contaminaton": true, "energy": "0.1-0.8nm"}, 

It was definitely a case of being eclipsed. You can check the schedule for GOES-16 here; the drop to 0 occurred exactly when expected, as GOES-16 entered the umbra.

Welp, didn't read the other comments until now; I guess this point has been hammered home enough already by now.

37 minutes ago, Vancanneyt Sander said:

So when GOES eclipses you'll not see it on SDO as it is in a different orbit.

Yep, and the times are also different for GOES-16 and GOES-18, due to being located at different geostationary points, in case anyone wonders why the data drops out at different times for the two in the NOAA X-ray flux.

2 hours ago, Adrian Kobyłecki said:

Sometimes this situation can happen during a solar eclipse. I'm telling the truth?

It could, but it would be quite rare, since our moon orbits in a different plane than the satellites; due to that, Solar eclipses can occur at any part of the year, but the satellite eclipse seasons will always be around the equinoctes. What's more common is for the moon to eclipse the satellites when they're above or below the ecliptic, so that there's no Solar eclipse visible from Earth at the same time.

But occasionally both happen at the same time, which is only possible when a Solar eclipse happens near one of the equinoctes; on September 1 of 2016, which is indeed close enough to the equinox, there was precisely an event like that, where SDO witnessed such a double eclipse:

 

18 hours ago, Gerasev22 said:

Привет, такие сбои были в 2021, 2022, 2023 годах, в одно и то же время. В 2022 году сбой был также 27 февраля. Это не похоже на сбой, в то время как другие графики показывают магнитные колебания.Screenshot_2024-02-28-23-22-01-426_org.telegram.messenger.thumb.jpg.3d0f1eb6e74ae249738764d3a273c079.jpg

  My dear friend, i am  at least partly reassured. I decided that the sun was eating itself! Thank you, my friend. Flower for you.

24ee08a63cd1a910e728430f7c17b052.jpg

Create an account or sign in to comment

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.