FEATURE Overview & Update
description
Transcript of FEATURE Overview & Update
BTC/PCT 2009-05-19 1
FEATURE Overview & Update
Brian Carcich
Peter Thomas
Cornell University
Based on CIRCLE.PRO by Ernest Bowman-Cisneros
BTC/PCT 2009-05-19 2
FEATURE Agenda
• Why FEATURE?• Status of FEATURE• What FEATURE does (demo)• FEATURE output, input, environment• How FEATURE models data
– Geometry; Shape; SPICE Kernels
• Issues of note, To Do• VRML Tool (demo)• Backup slides
BTC/PCT 2009-05-19 3
Why FEATURE?
Mapping, note taking, simple measures
• Points: locations, density distribution
• Lines: sizes and azimuths
• Circles: sizes and density distribution
BTC/PCT 2009-05-19 4
Status – Since Nov, 2008
• Done
– Successfully used flight test data!– LRO/generic TDI/Line imager intersection framework– Site-independent SPICE kernel management
• EKKM not site-independent, but close enough
– Hi-resolution lunar rotation model• Generic shape model interface: user supplies model
– Read PDS subwindows• Postponed/obsolete: use pds2isis
– Developed VRML tool
BTC/PCT 2009-05-19 5
What FEATURE doesLocate, identify & record surface FEATUREs
• Locate– Line, Sample– Latitude, Longitude
• Identify– Points: PRFs; &c.– Lines: Grooves; ridges; &c.– Circles: Craters; &c.– Assign comments, IDs
• Record– Flat ASCII format
• One line/feature
BTC/PCT 2009-05-19 6
FEATURE Output: Sample record file
VERSION 1 9 311.66 29907.18 -999.00 -999.00 -999.00 -999.00 -999.000 -999.00 -999.00 -999.000 50000 5000 m00725569 PRF 536.29 29782.81 12.84 -999.00 -999.00 -999.00 -999.000 -999.00 -999.00 -999.000 50000 5000 m00725569 Crater 87.15 29872.54 23.12 -999.00 -999.00 -999.00 -999.000 -999.00 -999.00 -999.000 50000 5000 m00725569 Crater 312.40 29841.20 21.84 -999.00 -999.00 -999.00 -999.000 -999.00 -999.00 -999.000 50000 5000 m00725569 Crater 175.00 29767.00 170.00 29837.00 -999.00 -999.00 -999.000 -999.00 -999.00 -999.000 50000 5000 m00725569 Ridge 547.00 28434.00 847.00 28501.00 -999.00 -999.00 -999.000 -999.00 -999.00 -999.000 50000 5000 m00725569 Ridge
<--1---> <--2---> <-----3------> <-----4------> <---5---> <--6---> <-7->
1. Feature: S1,L1 (Center if circle)2. Feature: S2,L2 (line) or Radius,-999 (circle) or -999,-
9993. Feature: Lat,Long,Radius of S1,L14. Feature: Lat,Long,Radius of S1,L1 (line) or -999,-9995. Image: NL, NS6. Image: filename prefix7. Feature: User comment, ID
BTC/PCT 2009-05-19 7
FEATURE Input
• Local IsisCube: PDS EDR=>[pds2isis]
– Alternative: SOC Server proposal; see backup slides
• Lunar shape model
– Radius map; FITS file w/specific keywords
• SPICE kernels– Mirror of SOC directory hierarchy– Two FEATURE-specific meta-kernels
• Requires Minimal localization to text file
– Scripts exist to automate update
BTC/PCT 2009-05-19 8
FEATURE Environment
• Linux– Eunuchs™, OSX, Windows/Cygwin should also work
• IDL (V5+?) with GUI– GSFC Astron library (FITS)– Misc Cornell IDL utilities
• ISIS– Pds2isis
• Replace with web application?– IsisDlm– 3rd-party libraries
• Carcich time
BTC/PCT 2009-05-19 9
How FEATURE models data
BTC/PCT 2009-05-19 10
How: Geometry Model
∙
BTC/PCT 2009-05-19 11
How: Shape Model description
Image [line,samp] to [latitude,long.]• Local image: PDS => [pds2isis] => IsisCube• Geometry(t) TDI model from image header info
Pixel line,sample in image … time of pixel exposure …
t = A + B x line + C x sampA, B from image header; C=0 for LROC
SPICE lookup F(t,sample,SCLK,SPK,CK,FK,IK) … Body-fixed image- & pixel-specific ray … DEM shape intersection … Selenocentric latitude & longitude
BTC/PCT 2009-05-19 12
How: Shape Model
• Generic user-supplied DEM (FITS file)– Mapping info in FITS header– Moon: CLEM. Data
• Delta from spheroid (Req = 1738km; ƒ = 1/3234.93)
• 4 pixel/deg (~8km/pixel)• PDS CLEM1-L-LIDAR-5-TOPO-V1.0 data set
BTC/PCT 2009-05-19 13
How – SPICE Kernel Management
• “The Achilles heel of SPICE is kernel management”• You can try this at home
– Scripts mirror LROC SOC SPICE kernel directories– EKKM: E-Kernel Kernel Management
• E-Kernel: portable database w/SPICE toolkit I/F• Loads only the necessary kernels
– Object interface for IDLIDL> ekkm = newekkm(‘lro.ek’)IDL> ekkm->FindByTime,START_TIME,STOP_TIMEIDL> delekkm,ekkm∙
BTC/PCT 2009-05-19 14
Issues of note
• Flight-quality Kernels (FK, IK): TBD– AI: Project
• ISIS IDL DLM: 32kLine limitation– AI: USGS/ISIS/KBecker
• Moon reference frame for shape model– IAU_MOON, MOON_PA, MOON_ME
BTC/PCT 2009-05-19 15
FEATURE TODO
• ISIS DLM to handle > 32k lines (USGS/KBecker)• Continue documentation: installation; use; tutorial• Port/install to volunteers’ environments• Port new framework back to MRO• Flight-quality Frames kernels (Project)
BTC/PCT 2009-05-19 16
VRML Visualization Tool
∙
BTC/PCT 2009-05-19 17
VRML Visualization Tool (cont’d)
∙
BTC/PCT 2009-05-19 18
Backup slides (details)
• Status – Done
• How - Code
• Where
• Who & When
• SOC Server proposal
BTC/PCT 2009-05-19 19
Backup slides (details)
• Status – Done
• How - Code
• Where
• Who & When
• SOC Server proposal
BTC/PCT 2009-05-19 20
Status - Done
• Week ending 2008-11-07– Create & use subwindow object– Read ISIS cubes & subwindows– Read ddd subwindows
BTC/PCT 2009-05-19 21
How - Code
• IDL– Based on EBC CIRCLE.PRO– ICY SPICE/IDL interface (DLM)– READ_ANY_IMAGE.PRO
• Custom code; extends IDL’s QUERY_*, READ_*• FITS via GSFC Astron library• PDS via custom code• IsisCube via ISIS DLM• DDD via custom reader• Recent sub-window object/reader for performance
– DDD, IsisCube working– PDS future
BTC/PCT 2009-05-19 22
Where
• Bodies (for line,samp=>Lat,Long)– Mars– Moon– TDI/Line CCD extendible to any near-sphere
• Missions (for line,samp=>Lat,Long)– MRO– LRO (CUB only)
• Development– Cornell
BTC/PCT 2009-05-19 23
Who & When
• EBC CIRCLE.PRO ca 2002?• PCT Updated specs (point, line, circle) ca 2006
• BTC CIRCLE.PRO => FEATURE.PRO ca 2006– ddd, MRO line,sample=>Lat,Long
• November, 2007, updated July, 2008
– IsisCube, LRO line,samp=>Lat,Long• May, 2009
BTC/PCT 2009-05-19 24
SOC Server Proposal
• Problem: large files copied to local disk• Need image + ancillary data
– Header info, SPICE/geometry
• Deliver subwindows a la JPEG2000/JPIP• Pros
– JIT delivery of desired image data– Could eliminate stale local files
• Cons– Network dependency (availability, performance)