Jump to content
PDS Geosciences Node Community

Search the Community

Showing results for tags 'summary products'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • PDS Geosciences Node
    • Announcements
    • For data providers
    • For data users
  • PDS Geo Tools
    • Analyst's Notebook
    • ODE - Orbital Data Explorer
    • Virtual Astronaut
    • Spectral Library
  • Workshops
    • MRO/CRISM Data Users' Workshop 2012

Categories

  • Data user tools

Blogs

  • Working with PDS data
  • Using the Analyst's Notebook

Found 2 results

  1. Hello, This is largely an IDL question concerning the new release of 2014 CRISM summary parameters in the CAT v7.3.1, so I'm not sure if it's appropriate here. I am working with: CAT_ENVI/save_add/CAT_Programs/Supplementals/select_summary_parameters.pro CAT_ENVI/save_add/CAT_Programs/Event_Handlers/mro_crism_summary_params_2014_event.pro Is there a way to bypass the control widget in 'select_summary_params.pro' and simply generate the default selections (basic products) without waiting for "OK" to be pressed? I want to link several CAT pre-processing steps together and don't require the widgets, but I am finding it difficult to manage widgets and events in these pro files because I am a beginner with IDL. I have looked into all the available IDL help files, but am still having trouble getting around this. I think my main problem is understanding where/how the program stores the event that the OK button is pressed in 'select_summary_params.pro'. I can see the structure of the widget being created in the second half of the pro file, then it is handed off to xmanager ~ line 236 Then an event, such as a button press, must occur in order for its uvalue to be returned to the event handler in the upper portion of the code ~ line 28 I only require the possibility of 'OK', because I don't want any other selections to be made or changed. But if I manually set uvalue to 'OK', it's not linked to any event ID, so I don't think it is recognized in any case. Elyse
  2. CRISM MRRSU

    Hello, I have just downloaded t0902_mrrsu_05s138_0256_1.img covering Gale crater, and just have some general questions: - Is the coverage for all mrrsu* products typically about 40% of a tile? I wasn't expecting such a large amount of missing data. - Is there any reason why each image strip seems to be individually normalised, but only in some products? For example, the IRAC product seems to have consistent values across the mosaic (I can clearly see the crater from the image), however, other products (mainly single band images, eg R440) appear to have each image strip with different ranges across the mosaic, as do the mrrif* images.
×