Hubble Shows MilkyWay unavoidable Collision with Andromeda Galaxy


Recommended Posts

nasa.jpg

NASA astronomers announced Thursday they can now predict with certainty the next major cosmic event to affect our galaxy, Sun, and solar system: the titanic collision of our Milky Way galaxy with the neighboring Andromeda galaxy.

The Milky Way is destined to get a major makeover during the encounter, which is predicted to happen four billion years from now. It is likely the Sun will be flung into a new region of our galaxy, but our Earth and solar system are in no danger of being destroyed.

"Our findings are statistically consistent with a head-on collision between the Andromeda galaxy and our Milky Way galaxy," said Roeland van der Marel of the Space Telescope Science Institute (STScI) in Baltimore.

The solution came through painstaking NASA Hubble Space Telescope measurements of the motion of Andromeda, which also is known as M31. The galaxy is now 2.5 million light-years away, but it is inexorably falling toward the Milky Way under the mutual pull of gravity between the two galaxies and the invisible dark matter that surrounds them both.

"After nearly a century of speculation about the future destiny of Andromeda and our Milky Way, we at last have a clear picture of how events will unfold over the coming billions of years," said Sangmo Tony Sohn of STScI.

The scenario is like a baseball batter watching an oncoming fastball. Although Andromeda is approaching us more than two thousand times faster, it will take four billion years before the strike.

Computer simulations derived from Hubble's data show that it will take an additional two billion years after the encounter for the interacting galaxies to completely merge under the tug of gravity and reshape into a single elliptical galaxy similar to the kind commonly seen in the local universe.

Although the galaxies will plow into each other, stars inside each galaxy are so far apart that they will not collide with other stars during the encounter. However, the stars will be thrown into different orbits around the new galactic center. Simulations show that our solar system will probably be tossed much farther from the galactic core than it is today.

To make matters more complicated, M31's small companion, the Triangulum galaxy, M33, will join in the collision and perhaps later merge with the M31/Milky Way pair. There is a small chance that M33 will hit the Milky Way first.

The universe is expanding and accelerating, and collisions between galaxies in close proximity to each other still happen because they are bound by the gravity of the dark matter surrounding them. The Hubble Space Telescope's deep views of the universe show such encounters between galaxies were more common in the past when the universe was smaller.

A century ago astronomers did not realize that M31 was a separate galaxy far beyond the stars of the Milky Way. Edwin Hubble measured its vast distance by uncovering a variable star that served as a "milepost marker."

Edwin Hubble went on to discover the expanding universe where galaxies are rushing away from us, but it has long been known that M31 is moving toward the Milky Way at about 250,000 miles per hour. That is fast enough to travel from here to the Moon in one hour. The measurement was made using the Doppler Effect, which is a change in frequency and wavelength of waves produced by a moving source relative to an observer, to measure how starlight in the galaxy has been compressed by Andromeda's motion toward us.

Previously, it was unknown whether the far-future encounter will be a miss, glancing blow, or head-on smashup. This depends on M31's tangential motion. Until now, astronomers have not been able to measure M31's sideways motion in the sky, despite attempts dating back more than a century. The Hubble Space Telescope team, led by van der Marel, conducted extraordinarily precise observations of the sideways motion of M31 that remove any doubt that it is destined to collide and merge with the Milky Way.

"This was accomplished by repeatedly observing select regions of the galaxy over a five- to seven-year period," said Jay Anderson of STScI.

"In the 'worst-case-scenario' simulation, M31 slams into the Milky Way head-on and the stars are all scattered into different orbits," said team member Gurtina Besla of Columbia University in New York, N.Y. "The stellar populations of both galaxies are jostled, and the Milky Way loses its flattened pancake shape with most of the stars on nearly circular orbits. The galaxies' cores merge, and the stars settle into randomized orbits to create an elliptical-shaped galaxy."

The space shuttle servicing missions to Hubble upgraded it with ever more-powerful cameras, which have given astronomers a long-enough time baseline to make the critical measurements needed to nail down M31's motion. The Hubble observations and the consequences of the merger are reported in three papers that will appear in an upcoming issue of the Astrophysical Journal.

The science team that did the investigation is led by Principal Investigator R.P. van der Marel (Space Telescope Science Institute [sTScI], Baltimore, Md.), and further consists of S.T. Sohn and J. Anderson (STScI), G. Besla (Columbia University, New York, N.Y.), M. Fardal (University of Massachusetts, Amherst, Mass.), R.L. Beaton (University of Virginia, Charlottesville, Va.), Thomas M. Brown (STScI), P. Guhathakurta (UCO/Lick Observatory, University of California, Santa Cruz, Calif.), and T.J. Cox (Carnegie Observatories, Pasadena, Calif).

http://hubblesite.org/newscenter/archive/releases/2012/20/full/

It's a shame I'm not going to be alive to witness any of this because by all accounts it's going to be spectacular.

And really, some people seem to be under the impression that it's going to mean certain doom for organic life, which isn't necessarily true. Apart from the fact that the stars in galaxies are so widely spaced apart making a collision unlikely, the general consensus is that the position of the sun and solar system may shift compared to the rest of the galaxy the chances are the actual impact on the solar system won't be that big.

Estimates of the sun's remaining lifespan range from 5-7 billion years so it's still possible there may be some life left on earth when this event starts to occur but whether humans will still be here remains to be seen. Nonetheless still pretty cool and interesting

Doesn't matter, the Reapers will wipe us out before then.

:laugh:

^ Why are you not planning to be alive ? ;)

Unfortunately, death isn't something I can mitigate with planning. I could extend my life by eating healthy and exercising but I still think 4 billion years is a bit of a stretch :p

Doesn't matter, the Reapers will wipe us out before then.

We should immediately go back to caves, licking our own eyes (trying to, whatsoever) and eating flies, so perhaps the reaptards won't trouble us until we quit doing so.

Stupid telomeres, though... safeguard against cancer that leads to cell death, anyway. Dumbass circular logic! Living forever isn't quite what it used to be, but human lifetime indeed seems too short to me.

Well ... that or a Stargate ... quick, lets move to Egypt ... clearly if we get the pyramyids to work, we'll travel the stars in a Destiny like ship (hell the Enterprise will be build before that, so i think we'll be safe no matter what)

I'm not going to wait around for it to happen, I've got better things to do. Like install Windows 180,756,465,5764,465,576, service pack 75,648,493. Hey look, they finnaly brought Aero back!

  • Like 3

Damn it Apple! iCal won't let me make a new appointment for June 1, 4.000.002.012? :crazy:

Be wary, even if it one day lets you do so, you could just oversleep it :shiftyninja:

https://www.neowin.net/news/alarm-clock-bug-hits-iphones-ipads-and-ipods (etc.)

uh...didn't we already know this? I'm pretty sure I read a long, long time ago that scientists already extrapolated the two galaxy's trajectories and found out they will collide eventually. Did I miss something?

uh...didn't we already know this? I'm pretty sure I read a long, long time ago that scientists already extrapolated the two galaxy's trajectories and found out they will collide eventually. Did I miss something?

From what I'm gathering, whilst it's been suggested for a while that the 2 had a chance of colliding, I think this is the first time that scientists have managed to get a clearer extrapolation of the dynamics of what will happen when they do. I like Hubble simply because it takes some stunning pictures but things like this always hold an interest for me.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Thanks
    • I actually got to use one of those so called "backup codes" once. It was for a customer, I choose the backup code option, and by the grace of god, they actually hade them printed out. Imagine my surprise, when after using the backup code, Google then told use we had to enter a code they just sent to the gmail address we currently did not have access to. I was not amused, Google backup codes should be the end all get out of jail free card, because you had to have access to the account to even get them.
    • On the topic of being locked out of a service. Recently two different friends of mine got locked out of their Google accounts. Both were hack attempts and one of them is waiting 30 days before he can get back in. He had backup codes and MFA but not a passkey. It was a browser token hack. Anyhow he has to wait 30 days for the dispute or whatever to end. The other person only had a password and is screwed losing all of the email, docs and years of photos. Google won’t help her at all. Her fault because she had no backup/recovery setup. Enable passkeys if possible. Also do NOT use browser based password managers. If using a cloud service make sure it is one you can fully sync to one of your devices so you can back it up. Like a PC or Mac with some backup drive plugged into it. Google is the worst to use IMHO. You can’t sync your photos at all. You have to use the “Take Out” service which is manual and takes days. That service strips the meta data from your photos. Also Google Docs synced to a device are useless without a Google accounts. MS Office/Libre Office is not going to open a link to a Google doc to a dead account.
    • Why you need to take back control of your synced passwords and how to go about doing that by Paul Hill Credit: Pixabay Last month, when Google decided to introduce daily and weekly caps for Gemini, it reignited an anxiety of mine, that you can’t really depend on service providers to maintain features forever, and it got me looking into free software (as in freedom) in other areas too. One app I quickly came across was KeePassXC on desktop and KeePassDX on Android as an alternative to password manager lock-in within the Chrome or Firefox ecosystems. I personally like to switch around with browsers, and using either password manager is inconvenient, so something like KeePassXC was interesting to me. The main issue with it now is syncing; I was not sure how to do that. After a bit of research, I came across Syncthing, a tool I was vaguely familiar with but had never used because it seemed complicated. However, I was completely wrong, and honestly, I think everyone should use it if they use multiple devices. It essentially lets you share folders peer to peer across all of your devices, no cloud services that you don’t control necessary! And it was fairly simple to set up, if not a bit clunky. Since setting it up, I’ve also started using Syncthing to back up other apps too, so don’t think it’s limited to just saving password databases. You can use it for pretty much anything you use Dropbox or Google Drive for. Before continuing to talk about those apps a bit more, let’s walk back a bit and talk about browser sync. Ever since the late 2000s and early 2010s, really, since we have been using smartphones, browser sync has been a necessity of life. I don’t know about you, but I have hundreds of passwords saved. For the most part, they’re all unique, so I don’t remember them and rely on software to manage them for me. Until recently, I’ve relied on password managers in Chrome and Firefox, but what I always found annoying was that it can be hard to transfer them between browsers. Sure, on Windows it is simple enough, but on Linux, exporting bookmarks has been temperamental. It works OK nowadays, but not too long ago, Chrome required you to enable exporting passwords in chrome://flags. The situation is even worse on mobile; there is no exporting or importing of passwords of any kind. You literally have to do it on a desktop, which is incredibly annoying in our mobile-first world. Sync also lets us take out bookmarks, history, tabs, and autofill data easily. To enable sync, it’s just a matter of signing into the browser once, and it handles the rest. It’s nice and easy. Obviously, all this has some issues, including those I’ve outlined above about it being hard to transfer data between browsers, but also things such as account suspension, lost account passwords, and other lock-in mechanisms, such as passkeys, being tied to a specific browser. On a sidenote, I have just removed all of my passkeys because they can make it harder to move browsers. I think the biggest threat to your synced passwords, especially if doing this with Google, is having your account suspended. I don’t ever expect mine to be suspended, but you do hear horror stories on Reddit where people lose access to their Google accounts. Imagine if you have hundreds of passwords, then suddenly lose access to them because Google froze your account, what would you do? So yes, it can be nice to use these syncing services for their convenience, but they also have risks. You may have seen me going on about free software quite a bit in my editorials. It’s essentially a concept championed by the Free Software Foundation. It’s software under particular licenses that grant you four freedoms: run the program for any purpose (0), study and change the source code (1), redistribute copies to others (2), and the freedom to distribute modified copies to others (3). For example, if there is an app I use and one day it gets abandoned by the developer, I can keep running it or even clone the software and continue developing it. Look at the myriad of cool services Google has run over the years before killing them. You can’t take the source code for those because they are proprietary, for the most part. Both KeePassXC and Syncthing are free software, so I get the freedoms listed above. In my use case where I’m syncing a database full of my passwords, I also get proper ownership over my data, there is no losing access to the database due to a frozen account, I can access the code of the tools I’m using, and I can get support from real people online if I run into issues, rather than having to consult a vague help page from an opaque company. With the KeePassXC password manager, you create a .kdbx file, which is what will be synced between devices. KeePassXC has cross-platform apps and also has browser extensions so that the browser can fetch passwords from the database once it is unlocked. Meanwhile, Syncthing is a peer-to-peer file sync tool where you can select folders to sync between your devices. Just pop files in the folders you choose, and then they will be available across your other devices whenever they come online. Syncthing is resilient as it works over both LAN and the internet and only ever sends content between your devices, never to a third-party server somewhere else. By combining these two pieces of software, you can essentially replicate the browser sync functionality. I have had a weird, conflicting issue where a new file is appearing, but it doesn’t seem to be impacting my main password database, which is updating between devices just fine. If you want to get a setup similar to what I have, you will need to go here to download KeePassXC for your computer. Once you have that, you will need to download your passwords from your web browser to a CSV file. In Chrome, you can type chrome://password-manager/settings into the URL bar, and you should see an option to download your passwords under Export Passwords. This will give you the CSV file you need for importing into KeePassXC. If you use a different browser, just use a search engine and type “browser-name export passwords” and muddle along. In KeePassXC, you’ll want to press Import File from the home screen, select the CSV file, and create a new database from it. On one of the screens of the wizard, there will be a Title field with a drop-down selected to none. Change this to Title and continue. You’ll select a name for the database, the encryption level (the defaults are fine), and then you will pick a password. I would choose four unrelated words that are easy for you to remember, as you’ll be typing them fairly often to access your passwords. When you have all your passwords in your new database, you will want to set up the browser extension so that your browser can fetch passwords from KeePassXC. Rather than explain how to do that here, refer to KeePassXC’s guide on how to set it up properly. Once you’ve got that set up, you want to install KeePassDX on Android. You can grab it on the F-Droid store and the Google Play Store. For iPhone users, there are other .kdbx-supporting apps, but I haven’t tried any of them, so have a look around and use what suits you. Once you have that done, you will want to install Syncthing on your computer and find a third-party app for your mobile device. On Android, I use an app called BasicSync; there are also options for iOS, but again, I’ve not tried these. Once you’ve got SyncThing, you’ll want to set it up and connect all of your devices together and share a folder between your gadgets. PCWorld has a good tutorial on setting up a synchronized file between your devices using SyncThing. Once you’ve set it up, congrats, you’ll never have to touch that stuff again except for adding or removing devices. I’ll be honest, I didn’t particularly like setting up Syncthing. It didn’t take me a massive amount of time, but I think I had to check online because I found it a bit confusing. That said, I’ve had it running for several weeks now and never need to touch the Syncthing settings, so that’s very nice. I also mentioned a conflicting file. I’m not sure why this is appearing, but the main .kdbx file seems to be updating and syncing just fine. What’s nice is that both KeePassXC and Syncthing are free software, so they won’t just vanish one day; you can take the code and fork the project or use a range of alternative implementations that others have made. It’s also nice that it works over LAN, so even if your ISP is having problems, your passwords will still sync. One area where you will want to be a bit more careful with this setup is if you only have one device. I am OK because I have a computer and two phones, all synced up. If you just have one device, you will probably want to store a backup of your .kdbx file somewhere else. Obviously, you’ll also want to remember your password really well, too. If you get locked out, it's game over. Overall, if you want to take back control of your computing from big tech, taking control of your passwords is an important part of this. You don’t need to immediately clear out your browser’s password manager; try running KeePassXC and the password manager concurrently for a while to see if you run into any problems. If you do try this out, let us know some other creative ways to use Syncthing. I haven’t really come up with a solution about what to do with my bookmarks, for example.
    • If the price was a dollar, someone would complain "Why isn't it free?" If it was free, someone would complain they weren't being paid to play it.
  • Recent Achievements

    • Week One Done
      Supreme Spray LV earned a badge
      Week One Done
    • One Month Later
      Genuinetonerink- Dubai earned a badge
      One Month Later
    • Week One Done
      Genuinetonerink- Dubai earned a badge
      Week One Done
    • One Year In
      hhgygy earned a badge
      One Year In
    • Week One Done
      AMV earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      513
    2. 2
      +Edouard
      163
    3. 3
      PsYcHoKiLLa
      88
    4. 4
      Steven P.
      74
    5. 5
      Michael Scrip
      73
  • Tell a friend

    Love Neowin? Tell a friend!