A google search for "osiris instrument rosetta pdf"

Reveals this paper http://pdssbn.astro.umd.edu/holdings/ro-a-.../osiris_ssr.pdf

Which states....



It later states

The math for figuring it out is very very simple. You don't even need to use trig.

Take any image for which there is a quoted range and resolution
http://www.esa.int/spaceinimages/Images/20...te_from_30_km_a

Which states
[quoteThe image was taken by Rosetta’s OSIRIS narrow-angle camera at 07:04 GMT on 12 September 2014 from a distance of about 30 km. The image scale is 0.5 m/pixel and the image covers about 1 km square.[/quote]

30km -> 50cm/pixel

So 15km would be 25cm/pixel

3km (closer than they plan to get with Rosetta) would be 5cm/pixel

So no - the 2cm figure is probably optimistic.

I see a couple of entries ( 4 in total ) in the long range DSN schedule for the first two weeks in January 2015 ( DOY 6, 11, 12 and 13 ) for VEX - but the DSN schedule isn't particularly reliable that far out.

I took the Photojournal image ( http://photojournal.jpl.nasa.gov/catalog/PIA19038 ) and attempted to crudely turn it into a comparative graph.

I took a 10 pixel wide vertical slice from each of the two images, turned it to greyscale, reduced to 1 pixel wide, extracted raw values via ImageJ and then plotted with Excel. Very much a qualitative comparison and shouldn't be considered in any way quantitative.

The hematite spike is obvious - but there's also a double bump in the Confidence Hills sample (just left of center in this image) whereas Cumberland has a single bump.

I think some would benefit from reading the documentation regarding the design and testing of Philae....

http://www.simpack.com/fileadmin/simpack/d...lanck_hilch.pdf

http://elib.dlr.de/87802/1/Poster_DLR_Land...zeA4_IPPW10.pdf

http://www.lpi.usra.edu/meetings/lpsc2013/pdf/1392.pdf
from which this paragraph is particularly important....


And finally
http://issfd.org/ISSFD_2012/ISSFD23_GC_2.pdf

It's not surface 'weight' that's the problem ( about 11 grams by my rough calculations - 0.01 Newtons )

It's the impact of landing. 1m/sec to a dead stop in, say, 20cm..... is a 5m/sec/sec deceleration - which is 500N of deceleration force for the 100kg Philae: 50,000x higher than the resting surface weight.

Whilst the lower frequencies are less fussy regarding pointing - the predominant factor in required pointing accuracy is antenna design - NOT frequency.

The S-Band relay from Huygens to Cassini had a beamwidth of only 2.3-2.4 degrees because it used Cassini's HGA.
http://descanso.jpl.nasa.gov/DPSummary/Des...3--Cassini2.pdf ( page 8 )

Whereas Deep Impact's probe-flyby relay used S-Band but patch-antennas that were in essence omnidirectional and managed 64kbps downlink at 8,000km range.

Arkyd 3 wasn't their first telescope - it was a technology demonstration 3U cubesat. Still a tragic loss along with RACE, another 28 satellite flock from PLanet Labs and all the other ISS resupply hardware.

http://www.geekwire.com/2014/arkyd-3/
"On board are Planetary Resources’ initial designs for a computer system, a power system, a communications system, an attitude determination system (determining the direction the satellite is pointing relative to the stars) and many other technologies that Planetary Resources plans to continue working on as it develops future versions of spacecraft in the Arkyd line."

There's a few issues with what you're saying. Firstly - Rosetta is taking a lot lot more than 1 frame per day..... that's simply what's being released at the moment. Once all this data is delivered to ESA's PSA - there will be hundreds of image of 67P that people will be able to turn into pretty amazing animations.


And who cares how long it might take to downlink an HD video? Well actually - all the scientists and engineers entrusted with operating Rosetta and doing science with it. The amount of data it's possible to return from the somewhere as far as 67P is a massive constraint on operations. It's not a question of taking an HD camera, or processing it's data...it's getting it back to Earth.

A rough calculation: 90 second of highly compressed 720p video is around 170 Megabytes. At typical data rates from Rosetta - that would take 8 HOURS to download from the spacecraft. That represents pretty much an entire day's downlink from a typical deep space spacecraft. And for what? An HD video 90 seconds long that, to be honest, would be better represented by a few 2k x 2k still images anyway - and you would have given up all the other scientific measurements Rosetta could take that day. These spacecraft do not last for ever. It's wrong to assume data will somehow magically make it to Earth eventually.


Curiosity is capable of, and indeed has taken HD video from the surface of Mars - but only on a few very specific, very select and very rare occasions, for the same reasons - the quantity of data it's possible to return from deep space is a massive, massive constraint. Kaguya at lunar distances was capable of, and indeed did return many HD movies of the moon where the data rate doesn't represent such a constraint ( typical downlink from lunar orbit is more than 2,000 times faster than Rosetta right now.

They do. The challenge is offloading the data thru the flight computer to be transmitted back up to Rosetta and from there on to Earth - all whilst the flight computer is trying to land.

For those who want to read tens of thousands of words by Don on that issue - read this thread http://www.unmannedspaceflight.com/index.php?showtopic=4308

I'd certainly like to have a look at the model, Sittingduck ( specifically with a view to 3d printing )

This is data I've looked at myself - ( from here - http://pds-geosciences.wustl.edu/mpf/mpfl-...im_2xxx/extras/ ) - and making a nice coherent mesh without holes is a huge HUGE creative task.

It'll be a brave person to take it on

Oct 18th Navcam 4 frames from http://blogs.esa.int/rosetta/2014/10/22/co...ops-neighbours/

It's the same HiRISE imagery we've been talking about here since yesterday
http://www.jpl.nasa.gov/spaceimages/details.php?id=PIA18618

A model of that size is going to be about that much. And you don't need to 'hollow' the model - the middleware between an STL file and the printer will do that for you autonomously to suit the requirements of the printer whilst using no more material than necessary.

I know that. But it's still SPICE that's driving HORIZONS. The same SPICE driving 'Eyes..' and telling the DSN where to point.

Let me put it another way. The DSN is using SPICE data generated by JPL nav team. We use the exact same SPICE data in Eyes on the Solar System. That same SPICE data is driving anything people get from HORIZONS.

It does. If you're being talked to by the DSN and JPL is helping with navigation - believe me - there's SPICE involved. It might not be publicly available - but there IS SPICE data.

If you go into HORIZONS Telnet and ping for MOM - you will see this



That's all filenames of SPICE BSPs

Doug

That's one of ours - it's from the Eyes on the Solar System team. Word of warning - as with almost every spacecraft we make - we had nothing in terms of good reference material. Infact, less than ususal because it's an ESA mission. It looks OK - but do not expect it to be especially accurate. We did our best, but we really had little to go on.

This thread. The post before yours.

Not a hard seartch to do....finding this took less time than typing it up.

http://lmgtfy.com/?q=mro+siding+spring

Third hit

http://cometcampaign.org/files/docs/sessio...CSS_CIOC_v3.pdf
Mars Reconnaissance Orbiter Observation Plan for Comet Siding Spring Encounter

Page 5 of which states....

Probably the best way is to let people download two separate movies - a left and right eye - and then people can use something like Stereoscopic player ( http://www.3dtv.at/Index_en.aspx ) to play it in any format they choose - Anaglyph - X-Eye - Over and Under etc etc. If hosting them's a problem, I'm sure UMSF and/or TPS can help

Very very very subjective.

Currently scheduled for Jan 19th.
http://spaceflightnow.com/tracking/index.html