IPB

Welcome Guest ( Log In | Register )

17 Pages V  < 1 2 3 4 > »   
Reply to this topicStart new topic
Stardust-NExT, Revisiting Tempel 1
Decepticon
post Dec 30 2010, 03:04 AM
Post #16


Senior Member
****

Group: Members
Posts: 1276
Joined: 25-November 04
Member No.: 114



QUOTE (volcanopele @ Dec 29 2010, 09:58 PM) *
Quick question: is the rotation of Temple 1 understood well enough that the mission planners can ensure that the DI impact site will be on the comet's sunlit side when Stardust-NExT flies by?



According to this yes. http://www.sdnext.org/mission/pdfs/SD_NEXT_Fctsht.pdf
Go to the top of the page
 
+Quote Post
stevesliva
post Dec 30 2010, 03:30 AM
Post #17


Senior Member
****

Group: Members
Posts: 1576
Joined: 14-October 05
From: Vermont
Member No.: 530



QUOTE (nprev @ Dec 29 2010, 08:32 PM) *
On the plus side this sounds like a well-understood fault state (esp. because it appears that there is some heritage with this system), and they are taking preventative actions well before the flyby.


Yeah, just a bit flip. Somewhat amusing that it was an error with the error-checking, if I read that right.
Go to the top of the page
 
+Quote Post
djellison
post Dec 30 2010, 03:46 AM
Post #18


Founder
****

Group: Chairman
Posts: 14431
Joined: 8-February 04
Member No.: 1



Actually - I would urge caution on the crater observation. It's a goal, but it's not a certainty. The mag-curve of the nucleus is double bumped, and using the shape model you can match it very well in both bumps - so basically, we may get the crater, or we may not.

If we get it - awesome. If we don't - we get to map the other side of the Nucleus which is also awesome.
Go to the top of the page
 
+Quote Post
JohnVV
post Dec 30 2010, 05:35 AM
Post #19


Member
***

Group: Members
Posts: 890
Joined: 18-November 08
Member No.: 4489



QUOTE
somewhat worrying mission status update

?? i would not use "somewhat worrying" it looks like a normal everyday address allocation bug

At least it is not a BSOD

QUOTE
It is caused by a latch-up of a redundant memory address register

sounds like a raid 1 set up
Go to the top of the page
 
+Quote Post
stevesliva
post Dec 30 2010, 05:50 AM
Post #20


Senior Member
****

Group: Members
Posts: 1576
Joined: 14-October 05
From: Vermont
Member No.: 530



QUOTE (JohnVV @ Dec 30 2010, 12:35 AM) *
sounds like a raid 1 set up


Yeah, pretty much. Sounds like they're comparing addresses with completely redundant memory words. Sucks when one of the address registers goes haywire.
Go to the top of the page
 
+Quote Post
Phil Stooke
post Jan 3 2011, 05:38 AM
Post #21


Solar System Cartographer
****

Group: Members
Posts: 10122
Joined: 5-April 05
From: Canada
Member No.: 227



"It's a small team and everybody who's involved in Stardust was also involved in Deep Impact/Hartley 2 -- same science team, same outreach folks."

That's where UMSF comes in...

Phil


--------------------
... because the Solar System ain't gonna map itself.

Also to be found posting similar content on https://mastodon.social/@PhilStooke
NOTE: everything created by me which I post on UMSF is considered to be in the public domain (NOT CC, public domain)
Go to the top of the page
 
+Quote Post
Astro0
post Jan 3 2011, 10:00 AM
Post #22


Senior Member
****

Group: Admin
Posts: 3108
Joined: 21-December 05
From: Canberra, Australia
Member No.: 615



That's where UMSF comes in...
Hey, anything we can do to help smile.gif They know we're watching, ready and willing to lend a hand.

Just thought about the fact that it was 7 years ago today that Stardust encountered comet Wild2 and now here we are, 42 days from the encounter with Tempel1. I remember it as a hectic time at the Canberra DSN, we were prime for the comet encounter and 24 hours later, prime for MER Spirit's landing. smile.gif
Go to the top of the page
 
+Quote Post
Paolo
post Jan 7 2011, 12:49 PM
Post #23


Senior Member
****

Group: Members
Posts: 1729
Joined: 3-August 06
From: 43° 35' 53" N 1° 26' 35" E
Member No.: 1004



a new status update. stardustnext.jpl.nasa.gov/mission/mission_status11_q1.html
it turns out the comet is still too faint to be visible in OpNav images
Go to the top of the page
 
+Quote Post
CJSF
post Jan 7 2011, 04:45 PM
Post #24


Newbie
*

Group: Members
Posts: 2
Joined: 16-June 10
Member No.: 5375



QUOTE (Paolo @ Jan 7 2011, 07:49 AM) *
a new status update. stardustnext.jpl.nasa.gov/mission/mission_status11_q1.html
it turns out the comet is still too faint to be visible in OpNav images


And it says they have lower fuel reserves than expected. I'm really excited about this encounter. It also mentioned the cold boot due to the "MEEB" restored the memory to its factory default. Does this mean they lost any patches or updates to the memory or memory management that were uploaded to the craft since launch?

CJSF


--------------------
Two years ago moved from my town
I was looking up past the city lights
But the city lights got in my way

See the constellation ride across the sky
No cigar, no lady on his arm
Just a guy made of dots and lines

-from "See The Constellation"
by They Might Be Giants
Go to the top of the page
 
+Quote Post
stevesliva
post Jan 19 2011, 10:53 PM
Post #25


Senior Member
****

Group: Members
Posts: 1576
Joined: 14-October 05
From: Vermont
Member No.: 530



No updates for awhile, but this RSS feed may point to updates in that status page:
http://feedity.com/rss.aspx/nasa-gov/UVRWW1ZV
Go to the top of the page
 
+Quote Post
Paolo
post Jan 22 2011, 08:42 AM
Post #26


Senior Member
****

Group: Members
Posts: 1729
Joined: 3-August 06
From: 43° 35' 53" N 1° 26' 35" E
Member No.: 1004



a new status update http://stardustnext.jpl.nasa.gov/mission/m...tatus11_q1.html
comet still not in sight

QUOTE
January 19, 2011
The spacecraft continues to operate as expected and all subsystems are healthy on approach to comet Tempel 1. This week the spacecraft started to tip back and forth to the imaging attitude in order to fix the Navcam mirror in a position that results in less scattered light reaching the CCD. This strategy has resulted in much lower background noise. The comet has not yet been detected in the images, and may not be detected for another week yet. The team continues to prepare for the Tempel 1 flyby by completing the tests of the encounter sequences.
Go to the top of the page
 
+Quote Post
elakdawalla
post Jan 22 2011, 10:14 PM
Post #27


Administrator
****

Group: Admin
Posts: 5172
Joined: 4-August 05
From: Pasadena, CA, USA, Earth
Member No.: 454



Thanks for keeping an eye on that site, Paolo!


--------------------
My website - My Patreon - @elakdawalla on Twitter - Please support unmannedspaceflight.com by donating here.
Go to the top of the page
 
+Quote Post
Hungry4info
post Jan 27 2011, 02:39 PM
Post #28


Senior Member
****

Group: Members
Posts: 1413
Joined: 26-July 08
Member No.: 4270



Stardust has located Tempel 1.
http://www.jpl.nasa.gov/news/news.cfm?rele...elease_2011-029


--------------------
-- Hungry4info (Sirius_Alpha)
Go to the top of the page
 
+Quote Post
ZLD
post Jan 27 2011, 08:49 PM
Post #29


Member
***

Group: Members
Posts: 555
Joined: 27-September 10
Member No.: 5458



Heres a slightly cleaned up version:
Attached Image


You can just barely make out a slight crescent and the shape of Tempel 1.


--------------------
Go to the top of the page
 
+Quote Post
djellison
post Jan 27 2011, 09:19 PM
Post #30


Founder
****

Group: Chairman
Posts: 14431
Joined: 8-February 04
Member No.: 1



That's just the coma - not the nucleus itself. Stardust's Navcam is 3.5 deg FOV, so we wont resolve the nucleus until very near close approach.
Go to the top of the page
 
+Quote Post

17 Pages V  < 1 2 3 4 > » 
Reply to this topicStart new topic

 



RSS Lo-Fi Version Time is now: 19th March 2024 - 04:11 AM
RULES AND GUIDELINES
Please read the Forum Rules and Guidelines before posting.

IMAGE COPYRIGHT
Images posted on UnmannedSpaceflight.com may be copyrighted. Do not reproduce without permission. Read here for further information on space images and 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.