5 ms·

The most exciting part is the following: "The close-up image was taken about 1.5 hours before New Horizons closest approach to Pluto, when the craft was 47,800

The most exciting part is the following: "The close-up image was taken about 1.5 hours before New Horizons closest approach to Pluto, when the craft was 47,800 miles (77,000 kilometers) from the surface of the planet. The image easily resolves structures smaller than a mile across." At its closest, the probe was 7,800 miles away, so we're going to get images way clearer than this in the following days, and even this is amazing to look at.

draugadrotten 11y ago
It will take approx 16 months to transfer all the pictures it took, because it is transmitting at only 1 kbit/second. http://www.planetary.org/blogs/emily-lakdawalla/2015/01300800-talking-to-pluto-is-hard.html?referrer=https://www.google.se/ http://www.planetary.org/blogs/emily-lakdawalla/2015/0130080...
- brock_r 11y ago
  Your linked article says 2 weeks, not 16 months. 11 photos a day.
  - rootbear 11y ago
    I don't know why that article quotes two weeks. I've read the 16 months figure in several places and it was mentioned in the press briefings yesterday. There might be a specific subset of data that will take two weeks to get. Perhaps the low-res JPGs of all of the planet imagery.
    - dEnigma 11y ago
      That article says two weeks because it's talking about a different set of images, from January. The uncompressed images from the fly-by will take the roughly 16 months you mentioned, but there will be smaller, compressed images before that.
    - deleted 11y ago
      [deleted]
    - UberMouse 11y ago
      I think it's 16 months to transfer every piece of sensor and imaging data back. The article says it takes ~40 minutes to transfer back a losslessly compressed full resolution image from the LORRI scanner
      - firebones 11y ago
        Anyone got info on the software/hardware specs and how they approach prioritizing and storage management? We waited a long time for the Apollo code to make it to Github--what better way to rope in the interest of one segment of humanity than getting more eyes on the code? I imagine that there wasn't time or power to do patches...but if there was, even the mechanics of that would be fascinating. Has anyone ran across a good discussion around the computational aspects of New Horizons?
        Dylan16807 11y ago
        http://www.planetary.org/blogs/emily-lakdawalla/2015/06240556-what-to-expect-new-horizons-pluto.html http://www.planetary.org/blogs/emily-lakdawalla/2015/0624055... http://www.planetary.org/blogs/emily-lakdawalla/2015/01300800-talking-to-pluto-is-hard.html http://www.planetary.org/blogs/emily-lakdawalla/2015/0130080... Some basic info on communication. The wikipedia page has a lot of info. The most important parts are that it has a redundant pair of 8GB flash drives and they actually upgraded the code in-flight to use both transmitters at once and nearly double the data rate. I'm not sure how priorities are arranged but it's all going to be sent back relatively quickly in terms of mission lifetime, and I think they managed storage use mostly by putting in plenty.
        hga 11y ago
        they actually upgraded the code in-flight to use both transmitters at once and nearly double the data rate It was anticipated this would be possible, depending on how the energy budget for the whole craft worked out.
      - mikeash 11y ago
        One of the early things I did when I obtained a computer modem was dial into a NASA BBS and download images of planets taken by Voyager. I believe it was at 300bps, although we may have had our 2400bps modem by then. Fortunately I didn't spend 16 months at it, since we were paying long distance charges and just a couple of pictures of Neptune downloaded over the course of an hour or so cost a relatively ridiculous amount of money. Still, it makes me feel a kinship with these folks, even if just barely.
  - deleted 11y ago
    [deleted]
  - InclinedPlane 11y ago
    That's the delay in getting a single batch of images back during the approach phase, not how long it'll take to get all of the images from the flyby back.
- orthecreedence 11y ago
  Reminds me of RealPlayer.
- hackuser 11y ago
  > because it is transmitting at only 1 kbit/second. I read elsewhere that it's also because other projects need to use the Deep Space Network, and bandwidth is a little constrained.
  - InclinedPlane 11y ago
    This is true. Communicating with New Horizons requires using the 70m DSN dishes. Of which human civilization has built ... 3. So monopolizing that resource for an entire year would be problematic. Instead the probe will send back highly compressed gallery sheets of all the images it has as well as a few pre-selected shots (some of which we've seen) which the science team will use to prioritize the data the gets sent back. Then the highest priority images will be transmitted using loss-less compression and the remainder will get sent over the remaining months off and one when the 70m DSN dishes aren't needed elsewhere.
    - rohit89 11y ago
      Maybe its time to build more then. It seems silly to be bottle-necked on things like this.
      - hga 11y ago
        Lots of missions and mission phases don't require bigger antennas. Look at http://eyes.nasa.gov/dsn/dsn.html http://eyes.nasa.gov/dsn/dsn.html for current usage of the Deep Space Network. As I type this, 3 smaller dishes in Goldstone are handling 4 Mars missions, all solar powered, Odyssey at 14.22 kb/s. At Canberra, the only active dish is a small one, receiving data at 159 b/s from Voyager 2 (!). Which, I grant, doesn't have a lot to say right now. 3 sites, 1 big dish and 3 smaller ones at each, except for a 4th smaller one at Goldstone, that's a serious investment and I gather enough for now, especially since satellite technology now allows storing massive amounts of data (8 GB for New Horizons) for download as the mission and ground stations allow. Note also that after New Horizons finishes downloading the data from its flyby in November 2016, it won't have a lot to say unless and until its Kuiper belt object flyby.
soheil 11y ago
Also "planet"!?

draugadrotten 11y ago

It will take approx 16 months to transfer all the pictures it took, because it is transmitting at only 1 kbit/second. http://www.planetary.org/blogs/emily-lakdawalla/2015/01300800-talking-to-pluto-is-hard.html?referrer=https://www.google.se/ http://www.planetary.org/blogs/emily-lakdawalla/2015/0130080...

brock_r 11y ago
Your linked article says 2 weeks, not 16 months. 11 photos a day.
- rootbear 11y ago
  I don't know why that article quotes two weeks. I've read the 16 months figure in several places and it was mentioned in the press briefings yesterday. There might be a specific subset of data that will take two weeks to get. Perhaps the low-res JPGs of all of the planet imagery.
  - dEnigma 11y ago
    That article says two weeks because it's talking about a different set of images, from January. The uncompressed images from the fly-by will take the roughly 16 months you mentioned, but there will be smaller, compressed images before that.
  - deleted 11y ago
    [deleted]
  - UberMouse 11y ago
    I think it's 16 months to transfer every piece of sensor and imaging data back. The article says it takes ~40 minutes to transfer back a losslessly compressed full resolution image from the LORRI scanner
    - firebones 11y ago
      Anyone got info on the software/hardware specs and how they approach prioritizing and storage management? We waited a long time for the Apollo code to make it to Github--what better way to rope in the interest of one segment of humanity than getting more eyes on the code? I imagine that there wasn't time or power to do patches...but if there was, even the mechanics of that would be fascinating. Has anyone ran across a good discussion around the computational aspects of New Horizons?
      - Dylan16807 11y ago
        http://www.planetary.org/blogs/emily-lakdawalla/2015/06240556-what-to-expect-new-horizons-pluto.html http://www.planetary.org/blogs/emily-lakdawalla/2015/0624055... http://www.planetary.org/blogs/emily-lakdawalla/2015/01300800-talking-to-pluto-is-hard.html http://www.planetary.org/blogs/emily-lakdawalla/2015/0130080... Some basic info on communication. The wikipedia page has a lot of info. The most important parts are that it has a redundant pair of 8GB flash drives and they actually upgraded the code in-flight to use both transmitters at once and nearly double the data rate. I'm not sure how priorities are arranged but it's all going to be sent back relatively quickly in terms of mission lifetime, and I think they managed storage use mostly by putting in plenty.
        hga 11y ago
        they actually upgraded the code in-flight to use both transmitters at once and nearly double the data rate It was anticipated this would be possible, depending on how the energy budget for the whole craft worked out.
    - mikeash 11y ago
      One of the early things I did when I obtained a computer modem was dial into a NASA BBS and download images of planets taken by Voyager. I believe it was at 300bps, although we may have had our 2400bps modem by then. Fortunately I didn't spend 16 months at it, since we were paying long distance charges and just a couple of pictures of Neptune downloaded over the course of an hour or so cost a relatively ridiculous amount of money. Still, it makes me feel a kinship with these folks, even if just barely.
- deleted 11y ago
  [deleted]
- InclinedPlane 11y ago
  That's the delay in getting a single batch of images back during the approach phase, not how long it'll take to get all of the images from the flyby back.
orthecreedence 11y ago
Reminds me of RealPlayer.
hackuser 11y ago
> because it is transmitting at only 1 kbit/second. I read elsewhere that it's also because other projects need to use the Deep Space Network, and bandwidth is a little constrained.
- InclinedPlane 11y ago
  This is true. Communicating with New Horizons requires using the 70m DSN dishes. Of which human civilization has built ... 3. So monopolizing that resource for an entire year would be problematic. Instead the probe will send back highly compressed gallery sheets of all the images it has as well as a few pre-selected shots (some of which we've seen) which the science team will use to prioritize the data the gets sent back. Then the highest priority images will be transmitted using loss-less compression and the remainder will get sent over the remaining months off and one when the 70m DSN dishes aren't needed elsewhere.
  - rohit89 11y ago
    Maybe its time to build more then. It seems silly to be bottle-necked on things like this.
    - hga 11y ago
      Lots of missions and mission phases don't require bigger antennas. Look at http://eyes.nasa.gov/dsn/dsn.html http://eyes.nasa.gov/dsn/dsn.html for current usage of the Deep Space Network. As I type this, 3 smaller dishes in Goldstone are handling 4 Mars missions, all solar powered, Odyssey at 14.22 kb/s. At Canberra, the only active dish is a small one, receiving data at 159 b/s from Voyager 2 (!). Which, I grant, doesn't have a lot to say right now. 3 sites, 1 big dish and 3 smaller ones at each, except for a 4th smaller one at Goldstone, that's a serious investment and I gather enough for now, especially since satellite technology now allows storing massive amounts of data (8 GB for New Horizons) for download as the mission and ground stations allow. Note also that after New Horizons finishes downloading the data from its flyby in November 2016, it won't have a lot to say unless and until its Kuiper belt object flyby.

soheil 11y ago

Also "planet"!?