ExoMars - Schiaparelli landing |
ExoMars - Schiaparelli landing |
Oct 21 2016, 07:25 PM
Post
#76
|
||
Member Group: Members Posts: 819 Joined: 3-June 04 From: Brittany, France Member No.: 79 |
I looked at Oppy's new images on Midnight Planets and spotted this pic I've not seen yesterday: http://www.midnightplanets.com/web/MERB/im...RP2857L6M1.html
Do you think the two bright spots above the horizon could be Schiaparelli and its parachute? I circled them: Time of acquisition seems too early (2:44:13 PM UTC) but Mike specifies that acquisition times are approximate. -------------------- |
|
|
||
Oct 21 2016, 07:30 PM
Post
#77
|
|
Senior Member Group: Members Posts: 2106 Joined: 13-February 10 From: Ontario Member No.: 5221 |
We know from the CTX images that it landed near the middle of the landing ellipses, way below the local horizon, so it can't be. I also withdraw my own speculation from earlier in the thread, given the ground truth.
|
|
|
Oct 21 2016, 07:43 PM
Post
#78
|
|
Senior Member Group: Members Posts: 4256 Joined: 17-January 05 Member No.: 152 |
On top of that, with the landing site over 50 km from Oppy, the pancam pixel scale would mean that those two specks were about 2.4 km apart! (So I guess theoretically possible if taken just after the parachute/backshell separated.)
|
|
|
Oct 21 2016, 08:39 PM
Post
#79
|
||
Senior Member Group: Members Posts: 4256 Joined: 17-January 05 Member No.: 152 |
I see a couple of possibly interesting features on the after CTX image. Marked with the black ellipse is some faint dark streaking that roughly aligns with the main lander splat. And circled is a small dark spot. Both weren't in the before image:
It's easiest to see them by flipping between the before and after images. Even though the image is very noisy, both features appear to rise above the noise fluctuations but still could be extreme fluctuations or other artifacts. Perhaps the streaks, being dark and so perhaps due to removed dust, are associated with the engine firing, and the dark spot the heat shield? |
|
|
||
Oct 21 2016, 09:49 PM
Post
#80
|
||
Member Group: Members Posts: 149 Joined: 18-June 08 Member No.: 4216 |
I see a couple of possibly interesting features on the after CTX image. Marked with the black ellipse is some faint dark streaking that roughly aligns with the main lander splat. And circled is a small dark spot. Both weren't in the before image: It's easiest to see them by flipping between the before and after images. Even though the image is very noisy, both features appear to rise above the noise fluctuations but still could be extreme fluctuations or other artifacts. Perhaps the streaks, being dark and so perhaps due to removed dust, are associated with the engine firing, and the dark spot the heat shield? Indeed, I pointed those two out here They appear to be downrange of the crash site. That's what you would expect for something that continues on ahead of the decelerating EDM. |
|
|
||
Oct 23 2016, 05:49 AM
Post
#81
|
|
Member Group: Members Posts: 507 Joined: 10-September 08 Member No.: 4338 |
|
|
|
Oct 23 2016, 06:35 PM
Post
#82
|
|
Member Group: Members Posts: 691 Joined: 21-December 07 From: Clatskanie, Oregon Member No.: 3988 |
When pancam auto-exposes images through each filter, it does so until it reaches a specified DN value. If I recall, that is about a DN of 3000. So Images taken with L2 or R2 would have a lower exposure time then say images taken with L6, L7 or R1. You can even see this in the raws as you approach the blue and UV end, the images start to get more noiser from CR hits and hot pixels since it takes more time to reach the specified DN. So I'd expect L6 images would be in the few second range and If schiaparelli went through the FOV (which is now extremely unlikely if not ruled out since we know where it landed), I would think it would leave a small streak. Images taken with R2 would be a fast exposure and would likely not show a streak at all.
|
|
|
Oct 23 2016, 08:23 PM
Post
#83
|
|
Senior Member Group: Members Posts: 2542 Joined: 13-September 05 Member No.: 497 |
These images were likely not autoexposed, but you're ignoring the fact that these are frame transfer cameras and would show artifacts with anything moving in the scene, which would probably lead to some kind of streaking for fast-moving objects regardless of exposure time. That said, the team looked at these images and said they saw nothing but cosmic-ray hits, so I'd say leave it at that.
-------------------- Disclaimer: This post is based on public information only. Any opinions are my own.
|
|
|
Oct 23 2016, 08:26 PM
Post
#84
|
|
Member Group: Members Posts: 965 Joined: 15-June 09 From: Lisbon, Portugal Member No.: 4824 |
A minuscule tribute to the ExoMars team. I have updated the kml file with the latest CTX images and also reviewed and extended the text of the several item's descriptions. Zoom in to see the "after" image. Enable (check) the "Hardware" to get small icons of Schiaparelli and its parachute.
Fernando Schiaparelli.kmz ( 408.86K ) Number of downloads: 425 |
|
|
Oct 24 2016, 01:20 AM
Post
#85
|
|
Member Group: Members Posts: 507 Joined: 10-September 08 Member No.: 4338 |
One way to rule out the streak in
http://qt.exploratorium.edu/mars/opportuni...ARP2857L6M1.JPG as being from Schiaparelli is to examine the times involved. From the filename, the above image was taken at 530160694 seconds in the epoch beginning on January 1, 2000 at 11:58:55.816 UTC. Using a J2000 calculator and subtracting the 64.2 seconds until 12:00:00 would put the image acquisition at 2016-10-19 14:50:29.799 UTC. However, the loss of signal from the Schiaparelli lander reportedly occurred about a minute before the scheduled landing time of 14:48 GMT (= UTC). Thus, the lander would have already crashed before the image was taken, unless I have made some error in my calculation. |
|
|
Oct 24 2016, 03:32 AM
Post
#86
|
|
Senior Member Group: Members Posts: 2542 Joined: 13-September 05 Member No.: 497 |
The time in the file name is an SCLK value and drifts around in a way tabulated by the NAIF group http://naif.jpl.nasa.gov/pub/naif/MER/kernels/sclk/mer1.tsc . According to the quick Python program I just wrote (below) this time corresponds to 2016 OCT 19 14:51:27. But your conclusion is right. I'm not sure how the imaging times for the MER imaging were commanded but this seems late.
CODE import math
import sys from spice import * furnsh("naif0001.tls") furnsh("mer1.tsc") t0 = scs2e(-253, sys.argv[1]) print "t0", t0, et2utc(t0, "c", 0), et2utc(t0, "isod", 0) -------------------- Disclaimer: This post is based on public information only. Any opinions are my own.
|
|
|
Oct 24 2016, 05:19 PM
Post
#87
|
|
Martian Photographer Group: Members Posts: 353 Joined: 3-March 05 Member No.: 183 |
The images were taken with fixed exposure times to minimize a streak. The contrast was expected to be low, even in the unlikely event the lander came to a part of the sky where Opportunity had a line of sight. So, spreading the sub-pixel feature over lots of pixels would just further reduce it.
The few red images were to mitigate against model error or tau change--the contrast was predicted to go through 0 within the Pancam bandpass. But they were few due to bits and to image timing. Pancam is slow; slower still in the rover's current operational mode. Tests ahead of time struggled to demonstrate a way to go fast--generally, when the images have gone fast, subframes were used. So, after the first 5 images (4 L, 1 R), there was no chance. I was expecting ~6 L images, and was betting the descent would be a little later and farther downrange (not having a better option--imaging from inside the crater was like looking for your keys under the streetlight, even if you thought you might have dropped them off in the dark spot off to the left). |
|
|
Oct 25 2016, 06:51 AM
Post
#88
|
|
Member Group: Members Posts: 149 Joined: 18-June 08 Member No.: 4216 |
Reported in Anatoly Zak's website:
"By October 24, engineers narrowed down a possible culprit to an error in the software of the Schiaparelli's Doppler radar altimeter, which misled the main computer into thinking that the spacecraft had already reached the landing altitude." That sounds like something you should catch during testing on the ground (Earth ground, that is) |
|
|
Oct 25 2016, 08:40 AM
Post
#89
|
|
Senior Member Group: Members Posts: 1276 Joined: 25-November 04 Member No.: 114 |
|
|
|
Oct 25 2016, 09:57 AM
Post
#90
|
|
Senior Member Group: Members Posts: 1089 Joined: 19-February 05 From: Close to Meudon Observatory in France Member No.: 172 |
Reported in Anatoly Zak's website: "By October 24, engineers narrowed down a possible culprit to an error in the software of the Schiaparelli's Doppler radar altimeter, which misled the main computer into thinking that the spacecraft had already reached the landing altitude." That sounds like something you should catch during testing on the ground (Earth ground, that is) Maybe the radar caught the heatshield flying down in its line of sight... |
|
|
Lo-Fi Version | Time is now: 21st September 2024 - 06:26 AM |
RULES AND GUIDELINES Please read the Forum Rules and Guidelines before posting. IMAGE COPYRIGHT |
OPINIONS AND MODERATION Opinions expressed on UnmannedSpaceflight.com are those of the individual posters and do not necessarily reflect the opinions of UnmannedSpaceflight.com or The Planetary Society. The all-volunteer UnmannedSpaceflight.com moderation team is wholly independent of The Planetary Society. The Planetary Society has no influence over decisions made by the UnmannedSpaceflight.com moderators. |
SUPPORT THE FORUM Unmannedspaceflight.com is funded by the Planetary Society. Please consider supporting our work and many other projects by donating to the Society or becoming a member. |