<p>First, I'll talk a little bit about <strong>the state of what is being done:</strong> (according to my knowledge)  </p>

<p>In Astronomy on-board processing is usually avoided if possible.  </p>

<p>The reason for this is to have the pure data as unspoiled as possible, because instrument effects, cosmic rays, the light from Earth's corona, etc. can introduce many systematic errors into the data. If that would be removed on-board and then sent to Earth, then there would be no control later on what the actual, original data was.<br>
This became relevant e.e. for the exoplanet-finding <a href="https://kepler.nasa.gov/Mission/faq/" rel="nofollow noreferrer">Kepler</a>(see also the technical data there) space telescope where the photometric data was showing very unexpected behaviour at first, before the reasons for it were realized, obviously long after the spacecraft was designed and built.  </p>

<p>Thus, the image processing challenges are usually resolved on the ground stations and with the astronomers on their big computers. Also the interpretation of the data, after being cleaned, debiased, etc. is non-trivial.</p>

<p>As however the downlink speed depends on the distance $d$ to Earth like $\sim \frac{1}{d^3}$ so satellites that orbit far away do have to apply some clever ways to reduce data sometimes. The Hubble is not a candidate for this, as it orbits Earth at only some 500 km a.s.l, its data can be transferred to Earth without problems.</p>

<p>The <a href="http://www.sea-astronomia.es/drupal/sites/default/files/archivos/proceedings11/instrumentacion/portellj/portellj.pdf" rel="nofollow noreferrer">Gaia</a> satellite however, orbits the second Earth-Sun Lagrange point and is thus farther away from Earth, 1.5 million km. This mission is an astrometric mission, meaning it's there to measure positions and velocities of stars to extreme precision. If all the pixels of all onboard systems would continuously be read out and produce data, that would be too much to handle and some would be lost. So Gaia has a pre-detector that tells the main detector "Hey a star is coming". The main CCD then creates a moving window of 12x12 pixels from which all electrons are read-out and accepted as data. So that's some limited processing there.</p>

<p>In terms of data transfer, missions like <a href="http://pluto.jhuapl.edu/" rel="nofollow noreferrer">New Horizons</a> (Pluto encounter last year) or the Voyagers, are too far out to simply send their data over. Therefore the <a href="https://eyes.nasa.gov/dsn/dsn.html" rel="nofollow noreferrer">Deep Space Network</a> exists, to look out for radio signals from those probes and actively amplify them.</p>

<p><strong>What you could do:</strong><br>
So now that I've spent time explaining that on real spacecraft it's not being done what you want to do, we can bend the rules and just try to think about what's being done on the ground (if you want to):</p>

<ul>
<li>Image calibration: A detector taking an image wants to be very well understood, before claiming any interesting discoveries or measurments. Part of this process is taking a dark image to characterize what your CCD is doing when nothing is measured. Then a flatfield image is done, an image of an ideally uniformly white surface, in order to characterize pixel-to-pixel variations. <a href="http://www.astrofriend.eu/astronomy/tutorials/tutorial-pre-calibration-flat-dark/tutorial-pre-calibration-flat-dark.html" rel="nofollow noreferrer">More</a>. For the measured image then, the dark image is substracted and divided through the flatfield image.</li>
<li>Cosmic ray removal: Cosmic rays fly through your camera in a random direction at random times (in space as well as on the ground). They produce streaks in CCD cameras, and can be automatically removed by taking the same image three times, and discarding one of them or only a pixel-region if a dramatic intensity streak somewhere is measured.</li>
<li>Measuring a point-spread function:  Stars are so far away, that they appear as point sources. However through instrumental effects this ideal point will always be spread out into a finite shape, called the <a href="https://en.wikipedia.org/wiki/Point_spread_function" rel="nofollow noreferrer">PSF</a>. Because this function can be easily a few pixels wide, it is very important to know the shape of the PSF to be able to assign photons to a star that have been measured in off-center pixels. Knowing then a star's photon output and it's distance one can calculate the luminosity. But even that can't be done on an on-board chip. What you could to is to try to automatically fit an Airy-function to the PSF.</li>
</ul>

<p>Ok so that was just a few ideas, but I'm not an observer, there may be better ones out there. Also you got keywords not to google further.</p>

CC BY-SA 3.0
2016-11-16T13:07:20.967Z
2016-11-16T13:25:58.647Z
2016-11-16T13:25:58.647Z
AtmosphericPrisonEscape
<p>Based on the original question... </p>

<pre><code>which I feel like is a little late now, as most universities are finished until next year. 
</code></pre>

<p>isn't as involved or difficult as it has been presented. </p>

<p>If all you're looking for are image processing problems, then you're going to need to look into the following:</p>

<ol>
<li>Bias levels</li>
<li>Dark levels</li>
<li>Background levels</li>
<li>Cosmic Rays</li>
</ol>

<p>Anything else regarding the images ie: stacking of filter combinations, are secondary and rarely required for any science case.</p>

<p>The funny thing is, these are common for any CCD image with a long exposure, so the space telescopes bit only adds more chance for cosmic ray interactions.</p>

<p>Enjoy</p>

CC BY-SA 3.0
2016-12-16T17:06:34.433Z
2016-12-16T17:06:34.433Z
LaserYeti
<p>For a computer science project  in University; </p>

<p>I need to find image processing problems on space exploration and Space Telescopes, only related to the image itself. </p>

<p>I have wrote a computer program that is able to separate every pixel of an image according to its pixel intensity (the whitest to the darkest) in 3 (or even more) big groups.</p>

<p>I was thinking that this might be somehow useful in a space image processing situation in a well known challenge of the technology in the Telescopes or machine vision devices around space.</p>

<p>Situation can be very specific, just as an example calculating the mass of a star by the look of the pixels which compose it, or something like this.</p>

CC BY-SA 3.0
2016-11-16T09:55:24.103Z
Are you asking for problems related to the real problems in modern research, or just more general processing things that you could do with an image? (At the moment it's not clear if you need a "Hubble type" pro application or you're just looking for any interesting image processing exercise to do.)
Andy
CC BY-SA 3.0
2016-11-16T11:03:42.723Z
Please specify if you're asking about  data processing challenges onboard of a satellite, due to limited downlink, or something else.
AtmosphericPrisonEscape
CC BY-SA 3.0
2016-11-16T11:40:18.143Z
Many thanks, @Andy yes, I'm looking for a real problem to serve as material for a research, if you can mention them this will help me to orientate my searching on internet. If it's a real issue present not only in the Hubble but in other "astronomic"  and space exploration imaging, it'd be great.
sujeto1
CC BY-SA 3.0
2016-11-16T11:40:25.200Z
@AtmosphericPrisonEscape you quite aimed what I'm intending to do, in fact it's a digital design (a chip?) that can achieve a function on computer vision or image processing Onboard the satellite. My design perform "image segmentation" of a picture, processing pixel by pixel.
sujeto1
CC BY-SA 3.0
2016-11-16T13:45:03.503Z
You might want to look at ImageJ , https://imagej.nih.gov/ij/ ,for general feature extraction,  and the many NASA tools available at https://software.nasa.gov/data_and_image_processing
Carl Witthoft
<star-systems><hubble-telescope><artificial-satellite>
Do you know about any Image Processing Challenges known in Space Telescope like Hubble?
sujeto1
# Do you know about any Image Processing Challenges known in Space Telescope like Hubble?

(Asked by: username_0 on 2016-11-16)

For a computer science project in University;

I need to find image processing problems on space exploration and Space Telescopes, only related to the image itself.

I have wrote a computer program that is able to separate every pixel of an image according to its pixel intensity (the whitest to the darkest) in 3 (or even more) big groups.

I was thinking that this might be somehow useful in a space image processing situation in a well known challenge of the technology in the Telescopes or machine vision devices around space.

Situation can be very specific, just as an example calculating the mass of a star by the look of the pixels which compose it, or something like this.

**Tags:** star-systems, hubble-telescope, artificial-satellite

> **Comments:**
> **username_1**: Are you asking for problems related to the real problems in modern research, or just more general processing things that you could do with an image? (At the moment it's not clear if you need a "Hubble type" pro application or you're just looking for any interesting image processing exercise to do.)  
> **username_2**: Please specify if you're asking about  data processing challenges onboard of a satellite, due to limited downlink, or something else.  
> **username_0**: Many thanks, @username_1 yes, I'm looking for a real problem to serve as material for a research, if you can mention them this will help me to orientate my searching on internet. If it's a real issue present not only in the Hubble but in other "astronomic"  and space exploration imaging, it'd be great.  
> **username_0**: @username_2 you quite aimed what I'm intending to do, in fact it's a digital design (a chip?) that can achieve a function on computer vision or image processing Onboard the satellite. My design perform "image segmentation" of a picture, processing pixel by pixel.  
> **username_3**: You might want to look at ImageJ , https://imagej.nih.gov/ij/ ,for general feature extraction,  and the many NASA tools available at https://software.nasa.gov/data_and_image_processing  

---

## 2 answers

### Answer by username_2 on 2016-11-16. Score: 2

First, I'll talk a little bit about **the state of what is being done:** (according to my knowledge)

In Astronomy on-board processing is usually avoided if possible.

The reason for this is to have the pure data as unspoiled as possible, because instrument effects, cosmic rays, the light from Earth's corona, etc. can introduce many systematic errors into the data. If that would be removed on-board and then sent to Earth, then there would be no control later on what the actual, original data was.  
This became relevant e.e. for the exoplanet-finding [Kepler](https://kepler.nasa.gov/Mission/faq/)(see also the technical data there) space telescope where the photometric data was showing very unexpected behaviour at first, before the reasons for it were realized, obviously long after the spacecraft was designed and built.

Thus, the image processing challenges are usually resolved on the ground stations and with the astronomers on their big computers. Also the interpretation of the data, after being cleaned, debiased, etc. is non-trivial.

As however the downlink speed depends on the distance $d$ to Earth like $\sim \frac{1}{d^3}$ so satellites that orbit far away do have to apply some clever ways to reduce data sometimes. The Hubble is not a candidate for this, as it orbits Earth at only some 500 km a.s.l, its data can be transferred to Earth without problems.

The [Gaia](http://www.sea-astronomia.es/drupal/sites/default/files/archivos/proceedings11/instrumentacion/portellj/portellj.pdf) satellite however, orbits the second Earth-Sun Lagrange point and is thus farther away from Earth, 1.5 million km. This mission is an astrometric mission, meaning it's there to measure positions and velocities of stars to extreme precision. If all the pixels of all onboard systems would continuously be read out and produce data, that would be too much to handle and some would be lost. So Gaia has a pre-detector that tells the main detector "Hey a star is coming". The main CCD then creates a moving window of 12x12 pixels from which all electrons are read-out and accepted as data. So that's some limited processing there.

In terms of data transfer, missions like [New Horizons](http://pluto.jhuapl.edu/) (Pluto encounter last year) or the Voyagers, are too far out to simply send their data over. Therefore the [Deep Space Network](https://eyes.nasa.gov/dsn/dsn.html) exists, to look out for radio signals from those probes and actively amplify them.

**What you could do:**  
So now that I've spent time explaining that on real spacecraft it's not being done what you want to do, we can bend the rules and just try to think about what's being done on the ground (if you want to):

* Image calibration: A detector taking an image wants to be very well understood, before claiming any interesting discoveries or measurments. Part of this process is taking a dark image to characterize what your CCD is doing when nothing is measured. Then a flatfield image is done, an image of an ideally uniformly white surface, in order to characterize pixel-to-pixel variations. [More](http://www.astrofriend.eu/astronomy/tutorials/tutorial-pre-calibration-flat-dark/tutorial-pre-calibration-flat-dark.html). For the measured image then, the dark image is substracted and divided through the flatfield image.
* Cosmic ray removal: Cosmic rays fly through your camera in a random direction at random times (in space as well as on the ground). They produce streaks in CCD cameras, and can be automatically removed by taking the same image three times, and discarding one of them or only a pixel-region if a dramatic intensity streak somewhere is measured.
* Measuring a point-spread function: Stars are so far away, that they appear as point sources. However through instrumental effects this ideal point will always be spread out into a finite shape, called the [PSF](https://en.wikipedia.org/wiki/Point_spread_function). Because this function can be easily a few pixels wide, it is very important to know the shape of the PSF to be able to assign photons to a star that have been measured in off-center pixels. Knowing then a star's photon output and it's distance one can calculate the luminosity. But even that can't be done on an on-board chip. What you could to is to try to automatically fit an Airy-function to the PSF.

Ok so that was just a few ideas, but I'm not an observer, there may be better ones out there. Also you got keywords not to google further.


---

### Answer by username_4 on 2016-12-16. Score: 0

Based on the original question... 
which I feel like is a little late now, as most universities are finished until next year. 

isn't as involved or difficult as it has been presented. 
If all you're looking for are image processing problems, then you're going to need to look into the following:

Bias levels
Dark levels
Background levels
Cosmic Rays

Anything else regarding the images ie: stacking of filter combinations, are secondary and rarely required for any science case.
The funny thing is, these are common for any CCD image with a long exposure, so the space telescopes bit only adds more chance for cosmic ray interactions.
Enjoy


---

