<p><a href="https://i.sstatic.net/KSBxs.gif" rel="nofollow noreferrer"><img src="https://i.sstatic.net/KSBxs.gif" alt="enter image description here"></a></p>

<p>This GIF is made (via giphy.com) from the new NAASA Goddard video <a href="https://youtu.be/JG9x6tkf8mg" rel="nofollow noreferrer">Hubble's New Image of Interstellar Object</a>. It shows the comet moving at quite a clip!</p>

<p>This shouldn't be a surprise.</p>

<p>From the link in the question <a href="https://archive.stsci.edu/proposal_search.php?mission=hst&amp;id=16009" rel="nofollow noreferrer">https://archive.stsci.edu/proposal_search.php?mission=hst&amp;id=16009</a> the coordinates for the first and last exposure are:</p>

<pre><code>    RA             Dec            Time
09 47 45.181   +18 07 30.70    2019-10-12  13:44:39
09 48 17.077   +17 59 20.37    2019-10-12  20:42:23
</code></pre>

<p><strong>In 7 hours the comet moved roughly 0.2 degrees!</strong></p>

<p>From JPL's Horizons, the state vectors for the comet and Earth around the middle of the image sequence are:</p>

<pre><code>      JDTDB        Calendar Date (TDB)        X     (km)      Y               Z               VX   (km/s)     VY              VZ
comet 2458769.250, 2019-Oct-12 18:00:00, -1.9092457E+08,  2.9804744E+08,  3.2507629E+07, -1.3003446E+01, -2.9440986E+01, -2.7477326E+01
Earth 2458769.250, 2019-Oct-12 18:00:00,  1.4082817E+08,  4.9358841E+07, -1.4600024E+03, -1.0121471E+01,  2.8065445E+01, -7.7695706E-04
</code></pre>

<p>The comet is about 416 million km from Earth, moving at roughly 64 km/s relative to Earth and 42 km/s relative to the solar system barycenter.</p>

CC BY-SA 4.0
2019-10-17T00:12:29.910Z
2019-10-17T14:20:36.937Z
2019-10-17T14:20:36.937Z
uhoh
<blockquote>
  <p>Is that right?</p>
</blockquote>

<p>No.</p>

<p>The streaks are fast-moving objects in the view of the telescope -- Other satellites. Hubble is in a fairly low orbit <a href="https://www.nasa.gov/mission_pages/hubble/servicing/index.html" rel="nofollow noreferrer">(it can be visited)</a> and there are plenty of satellites around and above it, including in its field of view. (For obvious reasons, the streaks are not caused by aeroplanes, a usual contender for streaks). What gives it away are the differing lengths of the streaks, indicating different orbital heights, and the fact that there are streaks going in other directions, meaning other orbits.</p>

<p>The larger fuzzy object towards the bottom that you marked might be larger satellite that is closer by and is thus imagined as a fuzzy blob streaking across the image.</p>

<p>Further to this point, the image time here is 5 minutes, as indicated by the start and stop dates given on the proposal. 5 Minutes is much too short for a comet to move significantly against the background, causing streaks when tracked. For the five minutes of imaging, all objects are essentially fixed on the viewing frame.</p>

<p>Lastly, to your point of noise: The imaging qualities of Hubble are superb <a href="https://spacetelescope.org/about/history/aberration_problem/" rel="nofollow noreferrer">[citation needed]</a>. That amount of noise, even in raw data, would indicate an awful pixel sensor - on par to a cheap camera. </p>

CC BY-SA 4.0
2019-10-15T18:20:42.820Z
I agree.  If every sharp dot in that image was noise from a 5 min exposure, the Hubble camera would be useless.  I get less noise in a 5 minute exposure from my DSLR.
Dan Hanson
CC BY-SA 4.0
2019-10-15T19:35:57.550Z
@DanHanson -- Your DSL is sitting at the bottom of the Earth's atmosphere, which protects it from the cosmic rays that afflict Hubble.
Peter Erwin
CC BY-SA 4.0
2019-10-15T19:36:51.547Z
I have been working with HST images for over twenty years. That *is* the standard kind of noise you get in HST images.
Peter Erwin
CC BY-SA 4.0
2019-10-15T19:51:36.873Z
"5 Minutes is much too short for a comet to move significantly against the background" -- This is wrong. Per the linked article, the comet's apparent motion was 75 arcsec/hour, which means 5.4 arcsec in a 260 sec exposure. That's over 130 pixels on the detector they were using. They absolute *had* to move the telescope in order to track the comet.
Peter Erwin
CC BY-SA 4.0
2019-10-15T20:04:51.637Z
See [this page](http://spiff.rit.edu/classes/phys373/lectures/cosmic_rays/cosmic_rays.html) for a demonstration of how noisy genuine *single-exposure* *HST* images are, and how well combining multiple exposures can clean them up.
Peter Erwin
CC BY-SA 4.0
2019-10-15T20:30:53.953Z
@PeterErwin You're right, I'm wrong.  I'm an amateur astronomer and use stacking all the time to improve S/N ratio in my images, but I had no idea there were that many cosmic rays in a hubble frame.  Your link was very educational.  Thanks!
Dan Hanson
CC BY-SA 4.0
2019-10-16T12:33:30.847Z
@PeterErwin the streaks are ~86pixels in length, if that helps.  Seems that maybe they didn't take the entire capture to create this image?
Baldrickk
CC BY-SA 4.0
2019-10-16T13:47:46.467Z
@Baldrickk I was using the mean raw pixel size of the WFC3-UVIS detector (0.039") for that estimate. The JPEG image uhoh posted has probably been resampled to some coarser scale (it's only 960 pixels wide, while the full width of the aperture they used is closer to 2100 pixels).
Peter Erwin
CC BY-SA 4.0
2019-10-16T13:53:57.550Z
For those who are curious as to what an actual satellite trail might look like, there's one in another of the *HST* images of this comet, taken about an hour and a half earlier, [here](https://archive.stsci.edu/cgi-bin/mastpreview?mission=hst&dataid=IE6K01U5Q). (It's the diagonal streak from upper left to lower right, from an object moving so fast that it crossed the camera's field of view before the telescope had moved far enough to produce visible curvature.)
Peter Erwin
CC BY-SA 4.0
2019-10-17T00:33:12.267Z
@PeterErwin that's excellent, thanks! Unless of course all those things we call "artificial satellites" are actually other, even faster interstellar objects (humor)
uhoh
CC BY-SA 4.0
2019-10-17T10:04:14.673Z
@PeterErwin thanks for that. a lot clearer now.
Baldrickk
CC BY-SA 4.0
2019-10-17T14:04:12.020Z
Hi @Urhen have a look at the GIF and video in [this answer](https://astronomy.stackexchange.com/a/33695/7982). I think it turns out that those streaks are indeed stars. All streaks are exactly the same length, which makes sense because [all of the exposures](https://archive.stsci.edu/proposal_search.php?mission=hst&id=16009) were the same duration, and tracking the comet.
uhoh
CC BY-SA 4.0
2019-10-15T17:15:45.527Z
2019-10-15T17:15:45.527Z
Urhen
<blockquote>
  <p>Is that right?</p>
</blockquote>

<p>I guess not. </p>

<p>It is easy to correct for biases in pixel sensitivity, these objects are stars and the telescope tracks them such that their light is collected into the same photon bin over time. Correction for pixel sensitivity is generally done (own experience) by taking images completely out of focus in faint light conditions. In this way one assures that the incoming number of photons is the same for each bin (in a statistical sense) and one can calculate the relative sensitivity of each pixel. I do not know if this is the way this is done for the Hubble telescope as well. </p>

CC BY-SA 4.0
2019-10-15T18:26:10.360Z
2019-10-16T06:30:47.993Z
2019-10-16T06:30:47.993Z
Basileios
<blockquote>
  <ol>
  <li>Is that right?</li>
  </ol>
</blockquote>

<p>Yes.</p>

<blockquote>
  <ol start="2">
  <li>Is the fuzzy one an extended object?</li>
  </ol>
</blockquote>

<p>That would certainly be my guess (probably a distant galaxy).</p>

<blockquote>
  <ol start="3">
  <li>What causes so many isolated pixels to be so much brighter than the background? Is this just the tail of a statistical distribution of
  shot noise, or are there other mechanisms that can produce single
  pixel noise many standard deviations above the statistical shot noise
  distribution?</li>
  </ol>
</blockquote>

<p>Some of those might be "hot pixels", which are manufacturing defects that cause individual pixels to overproduce electrons. Most of them are due to so-called "cosmic rays", a generic term used in astronomical imaging to refer to the effects of energetic charged particles hitting the detector. In <a href="https://www.eso.org/~ohainaut/ccd/CCD_artifacts.html" rel="noreferrer">ground-based images</a>, these are often not actual cosmic rays, but instead are particles from the decay of radioactive isotopes in or near the detector. In the case of space-based images like these, they more often <em>are</em> proper cosmic rays, though many of them are really charged particles trapped in the Earth's magnetosphere. (There is a part of <em>Hubble</em>'s orbit which takes it within the <a href="https://en.wikipedia.org/wiki/South_Atlantic_Anomaly" rel="noreferrer">South Atlantic Anomaly</a>, where the Van Allen belt dips down toward the Earth's surface; observations are not scheduled during those periods, because of all the extra cosmic-ray hits the detectors receive.)</p>

<p>For example, <a href="https://archive.stsci.edu/missions/hst/public/ie6k/ie6k04voq/ie6k04voq_drc.jpg" rel="noreferrer">here</a> is a preview image from one of the other exposures in the sequence of observations. If you look closely, you can see that many of the cosmic-ray hits are slightly elongated, because the particle was traveling at an intermediate angle and passed through two or more adjacent pixels. The bright linear streak right next to the comet is an extreme example of this, where the particle was traveling almost parallel to the detector and so passed through an extended sequence of pixels.</p>

<p>The usual approach to dealing with this is to take several short exposures, one right after another, and combine them afterwards by rejecting extreme outlying pixel values from a single exposure (stars and other genuine objects will have similar pixel values from one exposure to the next, while cosmic rays are randomly located and do not repeat). This is why the <em>HST</em> images you see usually don't have cosmic-ray artifacts: they are the result of combining multiple exposures. (See <a href="http://spiff.rit.edu/classes/phys373/lectures/cosmic_rays/cosmic_rays.html" rel="noreferrer">here</a> for a discussion and an example.) There are also statistical analysis tricks one can use to try to clean up individual exposures, though this necessarily involves interpolating data.</p>

CC BY-SA 4.0
2019-10-15T07:59:50.410Z
I see, so there's probably some simple formula for the length distribution of randomly oriented minimum ionizing particles for a given pixel sensitive depth/width ratio (not that these have to be minimum ionizing) such that most are one or a few adjacent pixels, and only a few can cover tens or hundreds of pixels. Thanks for the great answer!
uhoh
CC BY-SA 4.0
2019-10-15T07:54:38.917Z
2019-10-15T19:42:59.737Z
2019-10-15T19:42:59.737Z
Peter Erwin
<p>The Forbes news article <a href="https://www.forbes.com/sites/jonathanocallaghan/2019/10/14/nasas-hubble-telescope-snaps-best-images-yet-of-our-first-interstellar-comet/#6740b20a26cb" rel="noreferrer">NASA's Hubble Telescope Snaps Best Images Yet Of Our First Interstellar Comet</a> shows the image below (which I have since annotated) of comet 2I/Borisov (C/2019 Q4) and links to this series of Hubble images: <a href="https://archive.stsci.edu/proposal_search.php?mission=hst&amp;id=16009" rel="noreferrer">https://archive.stsci.edu/proposal_search.php?mission=hst&amp;id=16009</a></p>

<p>Looking through the previews of those images, they all seem to have streaks of similar length and direction, so I am assuming that the telescope is tracking the comet's motion in each exposure and the streaks are stars, suggesting that all the small dots are noise and not stars.</p>

<ol>
<li>Is that right?</li>
<li>Is the fuzzy one an extended object?</li>
<li>What causes so many isolated pixels to be so much brighter than the background? Is this just the tail of a statistical distribution of shot noise, or are there other mechanisms that can produce single pixel noise many standard deviations above  the statistical shot noise distribution?</li>
</ol>

<p><a href="https://i.sstatic.net/JI0RH.jpg" rel="noreferrer"><img src="https://i.sstatic.net/JI0RH.jpg" alt="enter image description here"></a></p>

CC BY-SA 4.0
2019-10-16T10:13:13.760Z
To what you refer by the fuzzy extended object? I do only see the comet (and of course strikes, stars and the noise).
Alchimista
CC BY-SA 4.0
2019-10-17T00:36:43.667Z
@Alchimista there are five annotated tracks, the bottom one is fuzzy. There's another fuzzy one not annotated at the top of the image (above the comet). I'm calling these two fuzzy tracks "extended".
uhoh
CC BY-SA 4.0
2019-10-17T09:23:00.547Z
Ah ok now I see them
Alchimista
CC BY-SA 4.0
2019-10-17T14:30:31.623Z
related: [Questions about Hubble's brand new view of an interstellar comet (video)](https://astronomy.stackexchange.com/q/33699/7982)
uhoh
<photography><hubble-telescope><image-processing>
Which are stars and which are noise in this comet photo?
uhoh
# Which are stars and which are noise in this comet photo?

(Asked by: username_0 on 2019-10-15)

The Forbes news article [NASA's Hubble Telescope Snaps Best Images Yet Of Our First Interstellar Comet](https://www.forbes.com/sites/jonathanocallaghan/2019/10/14/nasas-hubble-telescope-snaps-best-images-yet-of-our-first-interstellar-comet/#6740b20a26cb) shows the image below (which I have since annotated) of comet 2I/Borisov (C/2019 Q4) and links to this series of Hubble images: <https://archive.stsci.edu/proposal_search.php?mission=hst&id=16009>

Looking through the previews of those images, they all seem to have streaks of similar length and direction, so I am assuming that the telescope is tracking the comet's motion in each exposure and the streaks are stars, suggesting that all the small dots are noise and not stars.

1. Is that right?
2. Is the fuzzy one an extended object?
3. What causes so many isolated pixels to be so much brighter than the background? Is this just the tail of a statistical distribution of shot noise, or are there other mechanisms that can produce single pixel noise many standard deviations above the statistical shot noise distribution?

[![enter image description here](https://i.sstatic.net/JI0RH.jpg)](https://i.sstatic.net/JI0RH.jpg)

**Tags:** photography, hubble-telescope, image-processing

> **Comments:**
> **username_1**: To what you refer by the fuzzy extended object? I do only see the comet (and of course strikes, stars and the noise).  
> **username_0**: @username_1 there are five annotated tracks, the bottom one is fuzzy. There's another fuzzy one not annotated at the top of the image (above the comet). I'm calling these two fuzzy tracks "extended".  
> **username_1**: Ah ok now I see them  
> **username_0**: related: [Questions about Hubble's brand new view of an interstellar comet (video)](https://astronomy.stackexchange.com/q/33699/7982)  

---

## 4 answers

### Answer by username_4 on 2019-10-15. Score: 18 | Accepted answer

> 1. Is that right?

Yes.

> 2. Is the fuzzy one an extended object?

That would certainly be my guess (probably a distant galaxy).

> 3. What causes so many isolated pixels to be so much brighter than the background? Is this just the tail of a statistical distribution of
>    shot noise, or are there other mechanisms that can produce single
>    pixel noise many standard deviations above the statistical shot noise
>    distribution?

Some of those might be "hot pixels", which are manufacturing defects that cause individual pixels to overproduce electrons. Most of them are due to so-called "cosmic rays", a generic term used in astronomical imaging to refer to the effects of energetic charged particles hitting the detector. In [ground-based images](https://www.eso.org/~ohainaut/ccd/CCD_artifacts.html), these are often not actual cosmic rays, but instead are particles from the decay of radioactive isotopes in or near the detector. In the case of space-based images like these, they more often *are* proper cosmic rays, though many of them are really charged particles trapped in the Earth's magnetosphere. (There is a part of *Hubble*'s orbit which takes it within the [South Atlantic Anomaly](https://en.wikipedia.org/wiki/South_Atlantic_Anomaly), where the Van Allen belt dips down toward the Earth's surface; observations are not scheduled during those periods, because of all the extra cosmic-ray hits the detectors receive.)

For example, [here](https://archive.stsci.edu/missions/hst/public/ie6k/ie6k04voq/ie6k04voq_drc.jpg) is a preview image from one of the other exposures in the sequence of observations. If you look closely, you can see that many of the cosmic-ray hits are slightly elongated, because the particle was traveling at an intermediate angle and passed through two or more adjacent pixels. The bright linear streak right next to the comet is an extreme example of this, where the particle was traveling almost parallel to the detector and so passed through an extended sequence of pixels.

The usual approach to dealing with this is to take several short exposures, one right after another, and combine them afterwards by rejecting extreme outlying pixel values from a single exposure (stars and other genuine objects will have similar pixel values from one exposure to the next, while cosmic rays are randomly located and do not repeat). This is why the *HST* images you see usually don't have cosmic-ray artifacts: they are the result of combining multiple exposures. (See [here](http://spiff.rit.edu/classes/phys373/lectures/cosmic_rays/cosmic_rays.html) for a discussion and an example.) There are also statistical analysis tricks one can use to try to clean up individual exposures, though this necessarily involves interpolating data.

> **Comments:**
> **username_0**: I see, so there's probably some simple formula for the length distribution of randomly oriented minimum ionizing particles for a given pixel sensitive depth/width ratio (not that these have to be minimum ionizing) such that most are one or a few adjacent pixels, and only a few can cover tens or hundreds of pixels. Thanks for the great answer!  

---

### Answer by username_0 on 2019-10-17. Score: 3

This GIF is made (via giphy.com) from the new NAASA Goddard video Hubble's New Image of Interstellar Object. It shows the comet moving at quite a clip!
This shouldn't be a surprise.
From the link in the question https://archive.stsci.edu/proposal_search.php?mission=hst&id=16009 the coordinates for the first and last exposure are:
    RA             Dec            Time
09 47 45.181   +18 07 30.70    2019-10-12  13:44:39
09 48 17.077   +17 59 20.37    2019-10-12  20:42:23

In 7 hours the comet moved roughly 0.2 degrees!
From JPL's Horizons, the state vectors for the comet and Earth around the middle of the image sequence are:
      JDTDB        Calendar Date (TDB)        X     (km)      Y               Z               VX   (km/s)     VY              VZ
comet 2458769.250, 2019-Oct-12 18:00:00, -1.9092457E+08,  2.9804744E+08,  3.2507629E+07, -1.3003446E+01, -2.9440986E+01, -2.7477326E+01
Earth 2458769.250, 2019-Oct-12 18:00:00,  1.4082817E+08,  4.9358841E+07, -1.4600024E+03, -1.0121471E+01,  2.8065445E+01, -7.7695706E-04

The comet is about 416 million km from Earth, moving at roughly 64 km/s relative to Earth and 42 km/s relative to the solar system barycenter.


---

### Answer by username_2 on 2019-10-15. Score: 1

> Is that right?

No.

The streaks are fast-moving objects in the view of the telescope -- Other satellites. Hubble is in a fairly low orbit [(it can be visited)](https://www.nasa.gov/mission_pages/hubble/servicing/index.html) and there are plenty of satellites around and above it, including in its field of view. (For obvious reasons, the streaks are not caused by aeroplanes, a usual contender for streaks). What gives it away are the differing lengths of the streaks, indicating different orbital heights, and the fact that there are streaks going in other directions, meaning other orbits.

The larger fuzzy object towards the bottom that you marked might be larger satellite that is closer by and is thus imagined as a fuzzy blob streaking across the image.

Further to this point, the image time here is 5 minutes, as indicated by the start and stop dates given on the proposal. 5 Minutes is much too short for a comet to move significantly against the background, causing streaks when tracked. For the five minutes of imaging, all objects are essentially fixed on the viewing frame.

Lastly, to your point of noise: The imaging qualities of Hubble are superb [[citation needed]](https://spacetelescope.org/about/history/aberration_problem/). That amount of noise, even in raw data, would indicate an awful pixel sensor - on par to a cheap camera.

> **Comments:**
> **username_3**: I agree.  If every sharp dot in that image was noise from a 5 min exposure, the Hubble camera would be useless.  I get less noise in a 5 minute exposure from my DSLR.  
> **username_4**: @DanHanson -- Your DSL is sitting at the bottom of the Earth's atmosphere, which protects it from the cosmic rays that afflict Hubble.  
> **username_4**: I have been working with HST images for over twenty years. That *is* the standard kind of noise you get in HST images.  
> **username_4**: "5 Minutes is much too short for a comet to move significantly against the background" -- This is wrong. Per the linked article, the comet's apparent motion was 75 arcsec/hour, which means 5.4 arcsec in a 260 sec exposure. That's over 130 pixels on the detector they were using. They absolute *had* to move the telescope in order to track the comet.  
> **username_4**: See [this page](http://spiff.rit.edu/classes/phys373/lectures/cosmic_rays/cosmic_rays.html) for a demonstration of how noisy genuine *single-exposure* *HST* images are, and how well combining multiple exposures can clean them up.  
> **username_3**: @PeterErwin You're right, I'm wrong.  I'm an amateur astronomer and use stacking all the time to improve S/N ratio in my images, but I had no idea there were that many cosmic rays in a hubble frame.  Your link was very educational.  Thanks!  
> **username_5**: @PeterErwin the streaks are ~86pixels in length, if that helps.  Seems that maybe they didn't take the entire capture to create this image?  
> **username_4**: @username_5 I was using the mean raw pixel size of the WFC3-UVIS detector (0.039") for that estimate. The JPEG image username_0 posted has probably been resampled to some coarser scale (it's only 960 pixels wide, while the full width of the aperture they used is closer to 2100 pixels).  
> **username_4**: For those who are curious as to what an actual satellite trail might look like, there's one in another of the *HST* images of this comet, taken about an hour and a half earlier, [here](https://archive.stsci.edu/cgi-bin/mastpreview?mission=hst&dataid=IE6K01U5Q). (It's the diagonal streak from upper left to lower right, from an object moving so fast that it crossed the camera's field of view before the telescope had moved far enough to produce visible curvature.)  
> **username_0**: @PeterErwin that's excellent, thanks! Unless of course all those things we call "artificial satellites" are actually other, even faster interstellar objects (humor)  
> **username_5**: @PeterErwin thanks for that. a lot clearer now.  
> **username_0**: Hi @username_2 have a look at the GIF and video in [this answer](https://astronomy.stackexchange.com/a/33695/7982). I think it turns out that those streaks are indeed stars. All streaks are exactly the same length, which makes sense because [all of the exposures](https://archive.stsci.edu/proposal_search.php?mission=hst&id=16009) were the same duration, and tracking the comet.  

---

### Answer by username_6 on 2019-10-15. Score: 0

> Is that right?

I guess not.

It is easy to correct for biases in pixel sensitivity, these objects are stars and the telescope tracks them such that their light is collected into the same photon bin over time. Correction for pixel sensitivity is generally done (own experience) by taking images completely out of focus in faint light conditions. In this way one assures that the incoming number of photons is the same for each bin (in a statistical sense) and one can calculate the relative sensitivity of each pixel. I do not know if this is the way this is done for the Hubble telescope as well.


---

