IPB

Welcome Guest ( Log In | Register )


zeBeamer
Posted on: Apr 1 2011, 08:57 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830



new and unexpected images from MESSENGER arrived today !
http://messenger.jhuapl.edu/gallery/scienc...mp;image_id=448

Erwan
  Forum: Messenger · Post Preview: #172082 · Replies: 116 · Views: 223182

zeBeamer
Posted on: Mar 17 2011, 07:35 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


Rick,

see the code below.
The files produced are very large, but I guess that the way it is with the STL format. For such well-defined uniform grids, it seems quite overkill though. A 2400x2400 grid converts to 11,520,000 facets and ~550MB.

Erwan

CODE
%%
clear

IMGfile='ldem_875S_20m.img';
STLfile='ldem_875S_20m.stl';

%% read IMG file
fidbin=fopen(IMGfile,'rb');
tmpbin=single(fread(fidbin,inf,'int16','ieee-le')/2000.0);
fclose(fidbin);

%% construct x/y vectors
dxy=0.02;
xymax=75.84;

xps=single((-xymax+dxy/2):dxy:(xymax-dxy/2));
yps=single((xymax-dxy/2):-dxy:(-xymax+dxy/2));

%% construct x/y arrays
[xps_,yps_]=meshgrid(xps,yps);

%%
zp=reshape(tmpbin,length(yps),length(xps))';
clear tmpbin

%% select subset to plot/convert
kx=3792+(-1200:1200);
ky=3792+(-1200:1200);

%% plot to check correct orientation
clf; hold on; box on; set(gca,'FontSize',13);
pcolor(xps_(ky,kx),yps_(ky,kx),zp(ky,kx));
shading flat;
axis equal; axis image;
xlabel('Stereographic X [km]   ');
ylabel('Stereographic Y [km]   ');

%% write STL file
surf2stl(STLfile,xps_(ky,kx),yps_(ky,kx),zp(ky,kx),'binary');
  Forum: LRO & LCROSS · Post Preview: #171621 · Replies: 4 · Views: 22018

zeBeamer
Posted on: Mar 17 2011, 03:49 AM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


Rick,

The IMG file is probably the best to use.
I could do that pretty easily with Matlab (and probably the open-source Octave can do it similarly).
Basically, I read the IMG as an int16 array, divided the values by 2000 to scale to km, created X/Y arrays (see the LBL files for the relevant info). Then, I used a script on the Matlab File Exchange (http://www.mathworks.com/matlabcentral/fileexchange/4512-surf2stl) to convert those 3 arrays (x,y,z) to a binary STL file (it can also do ascii).
That last step is pretty slow, so I actually created a STL from a small subset region of the IMG file I was trying out (LDEM_75N_240M.IMG).
I tested it out with MeshLab (http://meshlab.sourceforge.net), and it seems to be working fine.

Erwan
(I'm not including the (short) code I wrote because you might not be using Matlab, but let me know if you're interested.)
  Forum: LRO & LCROSS · Post Preview: #171599 · Replies: 4 · Views: 22018

zeBeamer
Posted on: Feb 25 2011, 08:37 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830



QUOTE (Phil Stooke @ Feb 25 2011, 03:19 PM) *
Could b/w shaded relief versions be added to that?

I added shaded-relief images from 4 different lighting azimuths.

QUOTE (djellison @ Feb 25 2011, 03:24 PM) *
And simple unshaded greyscale 16 bit images (png/tif or similar?)

That's very close to the raw IMG files, no? I added grayscale images (PNG, JPG).


Erwan

  Forum: LRO & LCROSS · Post Preview: #171070 · Replies: 24 · Views: 70247

zeBeamer
Posted on: Feb 25 2011, 06:50 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


Hi All,

Some LOLA products for the PDS release (#5), which will be officially out on March 15, 2011, are now available on the LOLA PDS node !
Label files and documentation are still being worked out, but I thought it'd be good to post (and some of you know we usually put those products online a bit early)

The data released are from July 13, 2009 to January 31, 2011.
There are EDRs/RDRs (individual profiles) for the courageous ones. But most of you will prefer the map products ( http://imbrium.mit.edu/DATA/LOLA_GDR/ ).
In addition to IMG products (int16), there are JP2 files (GeoJPEG2000) which are compressed (lossless) and contain projection information. If you use a GIS programs, that should be helpful. The attached XML files contain the statistics already, which could save you 10+ minutes for the bigger grids upon loading. (Due to PDS filenaming conventions, you need to rename them to file.JP2.aux.xml for that to work properly; tested on ArcGIS).
And keep in mind that in both those formats, the data were digitized at a 0.5m granularity, so you will need to divide the values by 2 to get the actual heights (in meters).

Also of interest for visualization are the updated LOLA texture packages for Celestia.
ZIP files here: http://imbrium.mit.edu/EXTRAS/CELESTIA/
and a few screenshots:







It'd be great also to know how this community is using the LOLA data, so please reply if you do:
1- Experimental Data Records (EDR) [raw telemetry]
2 - Reduced Data Records (RDR) [altimetric profiles]
3 - IMG Gridded Data Records (GDR) [maps]
4 - JP2 Gridded Data Records (GDR) [maps]
5 - Celestia Virtual Textures


Enjoy !!

Erwan

EDIT 2011.02.25 08:30pm EST
I realized there was a mistake in the level 0 normal map. (The files were the same as the topography texture...)
The ZIP files have been updated. In case you downloaded the "old" version, you can download the two level 0 files here instead of re-downloading the ZIP.
  Forum: LRO & LCROSS · Post Preview: #171065 · Replies: 24 · Views: 70247

zeBeamer
Posted on: Jan 13 2011, 02:45 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


Current orbits are good to 15-20m, so I am not surprised that the orbit errors show up at 5m resolution. We're working on it (for example, by developping new gravity field models), but 5m is currently not achievable. (For reference, the original requirement was 50m). Maybe after GRAIL gives us a perfect gravity field!
Also, keep in mind that each laser footprint is ~5m in diameter, so your maps will have very sparse coverage at those resolutions.
  Forum: LRO & LCROSS · Post Preview: #169522 · Replies: 17 · Views: 29129

zeBeamer
Posted on: Sep 12 2010, 01:03 AM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


QUOTE (Rick Sternbach @ Sep 9 2010, 07:31 PM) *
Oh, and I just noticed a lot of file names *missing*, like all the JPG2000 files. With my limited Mac software here, those were the only files I could get to look at and use in Terragen. I can get a file like LDEM_64.img to open in MacDEM as I did with the MOLA files, but now MacDEM can't figure out the height range (I think). Image comes out where I can see the terrain with directional lighting turned on, but the shades are all super contrasty and black-white splotchy. Probably time to get a new machine and better terrain software. sad.gif


GeoJPEG2000 are forthcoming. We want to make sure they're correct, and we found some strange things happening with the programs used to make the conversion.
Anyway, release date has always been the 15th, if you can wait that long wink.gif

As for the 128ppd being too large, we did not plan on splitting those up, but that could potentially be done in the next release, if enough people think it's worthwhile. The problem is that when we eventually release a 1024ppd, we don't want to break them up 256 tiles (each equivalent to a 64ppd global). 64 "128ppd" tiles will be quite enough already!

Erwan

  Forum: LRO & LCROSS · Post Preview: #164025 · Replies: 70 · Views: 108499

zeBeamer
Posted on: Sep 3 2010, 09:20 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


Here is one image of the South Pole region as shown by Maria Zuber in the Ames meeting about a month ago. Click for higher resolution.

It's a 25-m DEM constructed from ~4000 profiles. The axis labels are in kilometers (stereographic projection around 0,-90).
Still a few blemishes, but impressive enough I hope wink.gif

Erwan
  Forum: LRO & LCROSS · Post Preview: #163781 · Replies: 70 · Views: 108499

zeBeamer
Posted on: Sep 2 2010, 07:56 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


QUOTE (Rick Sternbach @ Sep 2 2010, 11:42 AM) *
Quick noob question; what's the difference between an LDEM file and a CDEM file? Just noticed all the new file names added.


CDEM contains the counts. LDEM contains the altitude (discretized in half-meter levels).

Erwan

  Forum: LRO & LCROSS · Post Preview: #163735 · Replies: 70 · Views: 108499

zeBeamer
Posted on: Sep 1 2010, 10:57 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


QUOTE (James Fincannon @ Aug 14 2010, 12:51 PM) *
Thus the magic of creating the DEM (i.e. sausage making) has alot of aspects that people need to realize and see if it applies to their usage. I have been stymied from doing illumination analysis because of these concerns. Sure I can do it and have done it with my analysis tools and use either the DEMs or the actual laser points, but I cannot create an error bar, so I have to reassess this laser data DEM.


James,
we discussed that offline, but I do not agree that we need to paint the whole Moon to have a realistic map at say 25m resolution. Indeed the current filling ratio of the 25x25m near the poles was 72% when we discussed that in June, but it will keep on improving.
The September release in a couple of weeks will have side products for each of the DEMs containing the counts of laser shots in each pixel. People can use that as a mask to see where you can be more or less confident in the measurement averaging (actually a median).
But I am not sure that is what will capture the interest of most people here. And having "gaps" in the DEMs to reflect the actual sampling would not necessarily make it better; I would expect most people want a full map, and do not want to do their own interpolation (they may not be familiar with the tools to do so) when they want to render a given region.
To reassure you, the data is not put through magic black boxes, and the workflow is actually pretty straightforward. It just gets messy to deal with when you have billions of points and those high resolutions.

QUOTE (James Fincannon @ Aug 14 2010, 12:51 PM) *
With coarser grids (240 m by 240 m/pixel), the percentage of surface area with laser data spots is around 8%.

Do you mean globally? In June, polewards of ~85deg, we had ~90% coverage at that resolution.

All,
The September release is coming very soon, and the DEMs will be updated this time, with more than 2 billion (good) points which went into them.
I updated the Celestia products, and they are already available here: http://imbrium.mit.edu/EXTRAS/CELESTIA/
They were made from the to-be-released 128ppd grid. Annoying seams should be gone (note to djellison and John). We are also releasing a 256ppd map (in four tiles), but I do not have the time currently to do it from that source (that would bring us to level6). And currently, it might be overkill. Others are welcome to try it out!

As for the new polar maps you saw in Maria Zuber's Ames presentation, this is not exactly what is going to be released. I'm not going into details here, but basically, the PDS release will still show some (reduced compared to before) orbit streaks near the poles. I will try to provide a better image of the South Pole, as it seems to be of interest here wink.gif

Erwan
  Forum: LRO & LCROSS · Post Preview: #163700 · Replies: 70 · Views: 108499

zeBeamer
Posted on: Mar 19 2010, 10:58 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


The website with the Celestia textures has been updated with improved textures (new ZIP files).
Seams that were visible at 10-degree latitude interval are now gone, and the color scale for the false-color image has been changed.
There are still some minor issues with the normal map (equator, 0 longitude), so they may be further updated, but not immediately.

Erwan


screenshots (click to enlarge; large files ! ~4Mb, 2560x1600)


  Forum: LRO & LCROSS · Post Preview: #157380 · Replies: 99 · Views: 126495

zeBeamer
Posted on: Mar 19 2010, 02:09 AM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


John,

Nothing is 32bit except the GRDs.



Jim,

QUOTE (Jim Mosher @ Mar 18 2010, 01:56 PM) *
I don't think there are any major problems with the most recent *.LBL files, but I wonder if it would be possible to upload copies of "LDEM_4.LBL" and "LDEM_16.LBL" with the "OFFSET" parameter in "OBJECT = IMAGE" corrected to "1737400." <meters>? The text description implies this is the offset used for forming the signed integers, but it is correctly listed on the machine-readable "OFFSET" line only in "LDEM_64.LBL". The other two *.LBL files, as John points out, give "1728216.", a number which may never have been correct.

This seems sensible. I will double-check tomorrow and correct it.
We are working on improving the labels in general. Very soon you'll have one label file per product format (jp2,img,grd).
Bottom line, I think LDEM_64.LBL is correct.


QUOTE (Jim Mosher @ Mar 18 2010, 01:56 PM) *
This may seem a very insignificant point -- since users can easily hand-edit these text files -- but I was writing directions on how to use the LOLA data with a program that automatically reads the *.LBL files associated with the *.IMG files, and this seems to add an unnecessary level of complication and confusion.

Good to see people integrating the data in their program already wink.gif
On that website you say "Nonetheless, LOLA gridded data covering the period 2009-07-13 through 2009-12-17 are (unofficially?) available on an MIT website." Actually, this MIT website is the official LOLA PDS data node. PDS archives/mirrors it.

QUOTE (Jim Mosher @ Mar 18 2010, 01:56 PM) *
Since obtaining altimeter data by satellite at a particular geographic point seems largely a matter of luck, I was wondering, as many must be, if anyone on the LOLA team has attempted integrating the raw data from Kaguya with the new data from LRO to produce a more complete and denser data set from which a more comprehensive gridded product might be produced?

Emily is perfectly correct in her post. We don't want to take the Kaguya data at face value (even though they've done a good job) and simply put them in. The LOLA data are geolocated based on LRO orbit solutions, which we understand and are working on improving... And with time, we'll cover (very close) to those Kaguya tracks.

QUOTE (Jim Mosher @ Mar 18 2010, 01:56 PM) *
One other very minor point: the *.LBL files say your grid is reported in the "MEAN EARTH/POLAR AXIS OF DE421" coordinate system. To the best of my knowledge, the Moon's Mean Earth/Polar Axis system is offset from the JPL DE421 ephemeris system by small rotations about each axis. Did you apply those corrections? If so, did you use the rotations recommended in the "IAU/IAG Working Group on Cartographic Coordinates" reports of Seidelmann et al. or some other ones?

I think all your answers will be found in :
ftp://naif.jpl.nasa.gov/pub/naif/generic_...orientation.pdf
If you're familiar with SPICE, basically, in addition to using the "de421.bsp" kernel, we also load the following kernels, which define the "MOON_ME" frame.
moon_pa_de421_1900-2050.bpc, moon_080317.tf, moon_assoc_me.tf, also available from the NAIF website.

QUOTE (Jim Mosher @ Mar 18 2010, 01:56 PM) *
Finally, although I find nothing materially wrong with the *.LBL files, I find the references to "planetopotential TOPOGRAPHY" and "GEOID" in the explanation of the data format slightly confusing. As I understand the explanation, the data represent "PLANETARY_RADIUS" rather than "planetopotential TOPOGRAPHY", and since no geoid is defined, and no correction for it required to use the data, the references to this additional computation seem unnecessary?

well, you can see that as superficial; but it's just recalling what is in this dataset, so that people know it's not geoid-related ("huge discovery: lava flows going uphill!"). We may release planetopotential topography grids in the future. Plus, in the RDRs, the geoid value at each LOLA point is defined.


Erwan
  Forum: LRO & LCROSS · Post Preview: #157327 · Replies: 99 · Views: 126495

zeBeamer
Posted on: Mar 18 2010, 02:36 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


QUOTE (JohnVV @ Mar 17 2010, 11:25 PM) *
all of the lbl's are F-'ed up ( this is NOT an exaggeration)

the headers state 3 different bit formats and as 16 bit
the IMG files ARE 32 bit
however ther really are 16 bit images saved as 32 bit ???
also the "SCALING_FACTOR" and "OFFSET" are off
yes this is messed up

John...
as I noted earlier in response to mhoward, there was an issue with the cylindrical IMGs being unsigned instead of signed. This was corrected. Did you see that, and are talking about the IMGs currently on the website?

QUOTE (JohnVV @ Mar 17 2010, 11:25 PM) *
however you will find that in isis the map projection is off .It is in sym cyl BUT the lat/long are way off
you will need to run maplab on it

I personally haven't tried with the IMGs, but the JP2s seem fine when overlaid over a Clementine basemap. What do you mean by "way off" ?

Erwan
  Forum: LRO & LCROSS · Post Preview: #157287 · Replies: 99 · Views: 126495

zeBeamer
Posted on: Mar 17 2010, 01:29 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


QUOTE (mhoward @ Mar 16 2010, 08:43 PM) *
I have one technical question for Erwan: Is the data in LDEM_64.IMG signed? From the header file LDEM_64.LBL.txt I would expect it to be a signed integer offset from 1,737,400m with a scaling factor of 0.5; however, the data appears to be unsigned integer, not signed. It makes me wonder about the noted offset and scaling factor.


actually, thanks for finding that out (and reading the doc first wink.gif ). The cylindrical IMGs had a problem. They should now be fine (signed int16), so please redownload... Alternatively, you could download the smaller JP2 and decompress it to a raw binary file. For example, with "kdu_expand" by Kakadu Software (http://www.kakadusoftware.com/index.php).
  Forum: LRO & LCROSS · Post Preview: #157191 · Replies: 99 · Views: 126495

zeBeamer
Posted on: Mar 16 2010, 10:50 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


QUOTE (Rick Sternbach @ Mar 16 2010, 03:08 PM) *
I haven't a clue what netcdf-binaries are, so I'll stick to the .img and JP2 files. However, I have a question about the files other than the complete cylindrical maps. I downloaded one of the 45S JP2 files, and all I see is a single 7200x7200 pixel image. Is there more of 45S somewhere, or can I not see the rest of that latitude because Photoshop isn't made to do that? Or has the rest of that latitude not been released yet?


netcdf : http://www.unidata.ucar.edu/software/netcdf/ ; libraries allow such files to be used in various programs/platforms

this is a stereographic projection, so the sphere was projected onto a plane. This particular grid you mention extends to +/- 1440km in both directions. The projection of a point at 45degS from the south pole is ~1440km away from the pole, hence the name. Such points are at the center of each side. However, when you are at a corner of the grid, at a distance of 1440*sqrt(2)~2037km, you are actually at 29.25degS. The 45deg latitude circle would be a circle that is nearly tangent to the top-center, right-center, bottom-center and left-center point.
(it's like http://www.colorado.edu/geography/gcraft/n.../mapproj_f.html, but we're putting out a square grid instead of a disc).

Erwan
  Forum: LRO & LCROSS · Post Preview: #157169 · Replies: 99 · Views: 126495

zeBeamer
Posted on: Mar 16 2010, 07:22 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830



QUOTE (Rick Sternbach @ Mar 16 2010, 12:20 PM) *
They have:
45 degrees north and south at (I believe) 100 meters/pixel, 200m/px, 400m/px in the same formats.
60 degrees north and south at 120m/px, 240m/px
75 degrees north and south at 30m/px, 60m/px, 120m/px
80 degrees north and south at 20m/px, 40m/px, 80m/px
85 degrees north and south at 10m/px, 20m/px, 40m/px
87.5 degrees north and south at 5m/px, 10m/px, 20m/px

Correct. Polar maps are in stereographic projection (true scale at the pole, R=1737.4km).

QUOTE (Rick Sternbach @ Mar 16 2010, 12:20 PM) *
They offer the whole moon unwrapped as a cylindrical map at 4, 16, and 64 pixels per degree, in JPEG2000, .IMG, .GRD formats. Personally, I have no idea how to use the .GRD, so I'm sticking to the JPEG2000 and .IMG files.

The GRD are netcdf-binaries, created with the GMT package (gmt.soest.hawaii.edu). They are double-precision, unlike the IMG and JP2 which are downconverted to 16bit. GMT can convert those to binary 3-column (with grd2xyz), but any netcdf-reader will do.

QUOTE (Rick Sternbach @ Mar 16 2010, 12:20 PM) *
I'm going to assume that with more orbits and more laser points recorded, the density of detail will just keep going up, as will the file size.
I need a new computer.

With more orbits, the gaps between tracks will be reduced (density of detail), but the file sizes should not change.
If your computer can handle those, it will be fine with the future releases wink.gif


Erwan
  Forum: LRO & LCROSS · Post Preview: #157163 · Replies: 99 · Views: 126495

zeBeamer
Posted on: Mar 16 2010, 03:11 AM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


Nice rendering wink.gif
Yes, orbit improvement is ongoing... Hopefully next release some of those orbital track artifacts will be gone!
  Forum: LRO & LCROSS · Post Preview: #157117 · Replies: 99 · Views: 126495

zeBeamer
Posted on: Mar 16 2010, 01:17 AM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


QUOTE (Rick Sternbach @ Mar 15 2010, 07:42 PM) *
EDIT: Holy cow, I just downloaded one of the "smaller" 17MB JPEG2000 files, and it's already in 16-bit B&W. I see files in there that are 3+ GB. Yeeeoooowww. Many, many, many thanks!


Rick,
glad the JP2s are working for you (they are all unsigned INT16). But the IMGs are there as well, just in case!
  Forum: LRO & LCROSS · Post Preview: #157109 · Replies: 99 · Views: 126495

zeBeamer
Posted on: Mar 16 2010, 12:19 AM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


The LOLA data are now also available !
In addition to the RDR and GDR products, I would like to point you to some products which were made with users like you in mind!

First, the big binary GDR files (maps) were converted to GeoJPEG2000, much easier to import in software like ArcGIS. Projection information is included in the headers, so that should work transparently.
location: http://imbrium.mit.edu/DATA/LOLA_GDR/

Second, we are releasing ready-made textures for Celestia. Many of you know Celestia (shatters.net/celestia), and some of you produced normal maps from the Kaguya altimetry data. In addition to a LOLA normal map, a texture showing the topography in false-color was made.
location: http://imbrium.mit.edu/EXTRAS/CELESTIA/

Enjoy !

Erwan
for the LOLA Science Team
  Forum: LRO & LCROSS · Post Preview: #157106 · Replies: 99 · Views: 126495

zeBeamer
Posted on: Jul 1 2009, 03:03 AM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


This morning, the LOLA instrument was turned on (not the lasers, just the receptors), and began collecting Laser Ranging data later in the afternoon !
Those data are not exactly like SLR (Satellite Laser Ranging), because it is not a two-way link, but they are timetagged at both the transmitting end (the Goddard station) and the receiving end (the LOLA receptor #1, through a fiber optics between a small telescope attached to the Earth-pointing high-gain antenna and the Moon-pointing LOLA instrument). They give an absolute range betwen the Earth and LRO (after some careful correlation and calibration), which will help improve the position knowledge of the spacecraft and benefit all the instruments (especially LROC, which turned on today for a bit!)

(see the LRO blog)
  Forum: LRO & LCROSS · Post Preview: #142696 · Replies: 71 · Views: 91902

zeBeamer
Posted on: Jun 21 2009, 12:12 AM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


the positions of Luna 17 and 21 (or rather, their Lunokhod rovers) are fairly well known, from Lunar Laser Ranging (mostly used to monitor the position of the Apollo retro-reflectors). I think Luna 21 is the least constrained of the two.
  Forum: LRO & LCROSS · Post Preview: #142228 · Replies: 73 · Views: 79922

zeBeamer
Posted on: Jun 20 2009, 08:59 PM


Junior Member
**

Group: Members
Posts: 22
Joined: 20-June 09
Member No.: 4830


Hello guys,
thought I would register now that LRO has launched successfully wink.gif

Another cool video is on ULA's website (http://www.ulalaunch.com/)
direct link: http://www.ulalaunch.com/launch/LRO/LROLCR...hHighlights.wmv

I was lucky enough to be invited to the launch, and see it!
One of the pictures I took :

By the way, LRO has a blog with many updates about how it's doing and what's next:
http://lroupdate.blogspot.com/
  Forum: LRO & LCROSS · Post Preview: #142217 · Replies: 73 · Views: 79922


New Posts  New Replies
No New Posts  No New Replies
Hot topic  Hot Topic (New)
No new  Hot Topic (No New)
Poll  Poll (New)
No new votes  Poll (No New)
Closed  Locked Topic
Moved  Moved Topic
 

RSS Lo-Fi Version Time is now: 17th May 2024 - 09:55 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.