MEX VMC - Back on, and online! Options

[djellison]

I heard about this 24 hours ago, and couldn't believe it - this is EXACTLY what has been missing from ESA. MASSIVE kudos to the ESOC MEX flight ops team for doing it

http://www.esa.int/SPECIALS/VMC/index.html

The last time I wrote a post and hit 'submit' at UMSF with a smile this big on my face, was when Oppy successfully got out of Purgatory.

[Paolo Amoroso]

Are you able to use the Celestia scripts? I downloaded a ZIP file with images and the corresponding script, placed them in the same folder and run the script with Celestia 1.4.1 under MacOS X. But nothing happens.


Paolo Amoroso

[Astro0]

..placed them in the same folder and run the script with Celestia 1.4.1 under MacOS X. But nothing happens.

Paolo,

I think that the intention with the Celestia script is just to show where MEX was at the time that the image was taken. Reading from their website it says that this will help users determine what surface features are visible and the timing of the images available. While the images are available in a folder of the same name as the script, I don't see that they are related beyond that. Simply a way to compare the Mars Webcam images to a visualisation of the same region using Celestia.

Astro0

[Paolo Amoroso]

I think that the intention with the Celestia script is just to show where MEX was at the time that the image was taken.

For each image, the script calls functions for selecting Mars and tracking it, which are supposed to bring the planet in the field of view. But I see only an empty star field. Also according to the script, the "M" and "N" should move to the next or previous image location, but this doesn't work. I don't see the instructions that the script should display, either.

Hmmm... I'd better check whether the version of Celestia I am using was compiled with support for the Lua language required by the VMC scripts.


Paolo Amoroso

[ugordan]

A dodgy first version of the tool:
 vmc2rgb_v01.zip ( 37.97K ) Number of downloads: 1760

It takes an input RAW file and writes out a PNG with the same filename and adds a "_rgb.png" suffix. For example:

CODE

VMC2RGB "08-183 12.23.52 VMC Img No 6.raw"

will produce "08-183 12.23.52 VMC Img No 6_rgb.png". Note that in windows command line prompt you need to use double quotes for filenames containing spaces such as these. The end qoute is not strictly necessary. If you associate the *.RAW file extension to the program (or if you just drag-n-drop the image on the program icon) you don't have to worry about this.

Also, the tool is dumb in that it will interpret any file you feed it as a 640x480 raw stream. I suppose I could make it grab PNGs as well sometime.

I'll consider adding an improved interpolation as slinted suggested later. I've done some reading and apparently the Bayer filter outputs have a fair amount of inter-channel "crosstalk" that causes saturation to go down which might explain the low saturation in these images. This is usually automatically handled by digital cameras with internal saturation boosting, in this particular case Photoshop's your friend.