oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sally Khudairi ...@apache.org>
Subject Re: NASA's OCO-2 mission instrument processing system: OODT and Tika inside!
Date Thu, 03 Jul 2014 15:28:17 GMT
Ack; thanks, Chris --I watched the liftoff! 

I'll tweet a hats-off later today.

Great job, everyone!

-Sally


>________________________________
> From: "Mattmann, Chris A (3980)" <chris.a.mattmann@jpl.nasa.gov>
>To: "dev@oodt.apache.org" <dev@oodt.apache.org> 
>Cc: "dev@tika.apache.org" <dev@tika.apache.org>; Sally Khudairi <sk@apache.org>

>Sent: Thursday, 3 July 2014, 11:25
>Subject: NASA's OCO-2 mission instrument processing system: OODT and Tika inside!
> 
>
>Hey Guys,
>
>Just as an FYI: the NASA OCO-2 mission successfully launched yesterday
>July 2, 2014,
>and is now in its in-orbit checkout phase and slowly getting ready to
>start watching 
>the Earth breath from space:
>
>http://oco.jpl.nasa.gov/
>
>Something that we can all be proud of: the instrument ground data system
>that will process the data for the mission is powered by OODT and Tika!
>OODT does file and workflow and resource management and Tika identifies
>files, extracts metadata and helps to put the data files in the right
>place.
>
>Congrats OODT and Tika communities!
>
>https://twitter.com/chrismattmann/status/484541298439778307
>
>
>Cheers,
>Chris
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>Chris Mattmann, Ph.D.
>Chief Architect
>Instrument Software and Science Data Systems Section (398)
>NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>Office: 168-519, Mailstop: 168-527
>Email: chris.a.mattmann@nasa.gov
>WWW:  http://sunset.usc.edu/~mattmann/
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>Adjunct Associate Professor, Computer Science Department
>University of Southern California, Los Angeles, CA 90089 USA
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>
>
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message