Jump to content
PDS Geosciences Node Community

Feng

Members
 View Profile  See their activity

  • Posts

    48

  • Joined

  • Last visited

 Content Type 

Everything posted by Feng

  1. Feng
    Hi Wladimir, This is Feng, I will try to answer your questions: Should I obtain the summary parameters and then apply the map projection or it is the opposite? Basically they are identical. For my opinion, I will do map projection then summary parameters since it reserves the summary parameters band name. It is necessary the "ratioing" for the spectra and use the "Flatten summary parameters" option?. I've seen a post where its says that is enough the "Continuum Removed" option Sorry I don't understand this question. I will take the team scientist about this. - How can i obtain a better resolution for the summary parameters image?. I've seen very good resolution images from papers that doesn't look like what I have obtaining (img_1) The summary parameters doesn't change the resolution. For this product, it is 18m/pixel. Here is all CRISM EDR resolution: https://ode.rsl.wustl.edu/venus/pagehelp/quickstartguide/index.html?crism_edr.htm For some Along-track oversampled (ATO) Spatial pixels unbinned for target – 18 m/pixel cross-track, up to ~3 m/pixel downtrack, requires special processing for increased resolution; half swath length as above. For img-1, if you only select one band (BDI1000IR), you can see When I create the summary parameters image the spectra doesn't look like the TRDR pure image because the data values change. Does that mean that I have to use the spectra from the TRDR and the summary parameters image is just like a "color guide" fot the mineral phases? (img_2) Yes. For your attached Img-2, the index is not the wavelength but the summary parameters band: Finally, how can I use the summary parameters properly and elaborate mineralogical maps from they? For the summary parameters, you can read the following paper: Revised CRISM spectral parameters and summary products based on the currently detected mineral diversity on Mars https://agupubs.onlinelibrary.wiley.com/doi/10.1002/2014JE004627 Hope this helps. Thanks, Feng
  2. Feng
    Hi Wladimir, Would you please provide the scenes you worked on so that we can better go through from there? Thanks, Feng
  3. Feng
    hi Wladimir, I think the only difference between yours and mine is the data ignore value. Since you cannot change -1 to 65535. How about you directly open the .hdr file in NotePad and change -1 to 65535 then save the file? You need close the .img in ENVI otherwise, you are unable to save the .hdr file. Thanks, Feng
  4. Feng
    Hi Wladimir, I processed the same data as you did and there is no problem at all (the black img_1 and img_2). Would you please redo it? For your additional question, the answer from the team scientist is: The user will need to look at both the product type and data type to figure out the state of the data – and there are also keywords in the label that indicate the corrections that have been applied. A quick summary – IF TRR3 – top-of-atmosphere apparent spectral reflectance (no corrections) AL TRR3 – surface spectral lambert albedo (photometric and atmospheric corrected via RT modeling) IF TER3 – top-of-atmosphere corrected I/F – CAT-like PHT and ATM corrections (and some other steps) have been applied IF MTR3 – map projected version of the corresponding TER For these correction, you can use the ATP correction function in CAT. Thanks, Feng
  5. Feng
    Hi Wladimir, The CAT_WAVELENGTH_FILTER in the header files is a numeric code from PDS label (in PDS3 label: "MRO WAVELENGTH_FILTER"). It is used when reading original CRISM data into CAT. When parsing PDS label, the default wavelength array to apply to the data (i.e., the standard re-sampling wavelengths for the appropriate wavelength filter used for the observation). It is most likely a book-keeping value. Thanks, Feng
  6. Feng
    Hi Wladimir, Your adjustment of the x and y in img_2 is correct. This is also what I did to ignore the non-data or bad bands. The number 65535 is also assigned to the bad bands. That's why you see the two straight lines between 2.5 to 3.0 um. For the problem you mentioned in img_3, you can do the following step to make it work: 1, Add wavelength through Edit ENVI header 2, edit the wavelength of your selected band, for example for D2300: tyep in 2.300 then hit Enter, it will update D2300 wavelength 3, after update wavelength of your selected bands, plot the spectral profile, and change the X range: Please let me know if you have other questions. Thanks, Feng
  7. Feng
    Hi Wladimir, For your first question, the trr3 is not map projected. So you will see the rectangle instead of the ones you saw on the paper. To map project the trr3, you can use the CAT map projection function. Or you can download the corresponding MTRDR (which is map projected TRDR) if it is available. I don't understand " additionally it opens inverted so i have to apply a 180° rotation. ". I think the original one is correct and you don't need rotate 180 degree. For your second question, the band 1 with value of 65535 is the non-data band. There are other bands which is bad band, these bad band data can not be used. For the bad band list you shall ignore these bands. For example, the following screenshot shows a symbol before the bad bands: Please let me know if you have any other questions. Thanks, Feng
  8. Feng
    CAT 7.4 is now available. User can download the latest version through: http://pds-geosciences.wustl.edu/missions/mro/crism.htm
  9. Feng
    Hi Harish, It is about the permission. Would you please run the IDL with "Run as Administrator" then run the previous SAVE command again? Please let me know if you still have problem. Thanks, Feng
  10. Feng
    Hi Chandan, It seems the customized datum is not recognized by ENVI. Would you please check if the three map projection files are in the right place? According to CAT installation document: Set up CRISM Customized Map Projection Move the CRISM customized map projection definitions files (datum.txt, geogcs.txt, spheroid.txt) from the CAT_ENVI\aux_files\crism_projection\ folder to your ENVI installed path inside the idl8x\resource\pedata\user_defined\ folder (the location of user_defined folder may vary based on your ENVI version, idl8x: idl86 for ENVI 5.3 and 5.4; idl87 for ENVI 5.5). If there files are not in the right place, please copy them to related folder and then start ENVI+IDL again. Thanks, Feng
  11. Feng
    Hi Emran, There is no problem for the map context and CAT projected TRR3 image. The map context is coming from DDR which contains all lines including the key area and lines before it reaches key area. CAT map projection removes the lines before key area. If you run map projection in ENVI (on standard 5.4: Geometric Correction -> Georeference IGM), you can see all lines as following: But the lines CAT excludes is not useful and that's why CAT projection cuts these lines. Also please note: this is typical for the FRS and ATO data. Hope this answer your questions. Thanks, Feng
  12. Feng
    Hi Emran, This is Feng. I am going to look into this. Have two questions: are you using ENVI 5.4 standard (not classic version)? Do you copy the three map projections files inside \CAT_ENVI\aux_files\crism_projection folder to your ENVi IDL folder (like C:\Program Files\Harris\ENVI54\IDL86\resource\pedata\user_defined folder)? Thanks, Feng
  13. Feng
    Hi Emran, The image cube product after ATP correction (...._trr3_CAT_corr.img) has all original bands (438 which include 8 bad bands, you can see it through Data Manager in ENVI 5.4 ) When you project the image cube, these bad bands are removed, so there are 430 bands left. Can you do the spectral enhancement before map projection then projection the output afterwards? Thanks, Feng
  14. Feng
    Hello Emran, Do you mean which file I used in the instruction? I use frt000047a3_07_if166l_trr3_corr_p_2014params_flat.img Thanks, Feng
  15. Feng
    Hi Emran, Would you please check attached file which describes the processing steps? Please let me know if you have any questions regarding to these steps. Thanks, Feng Steps.pdf
  16. Feng
    Hi Emran, I did replicate the error in classical ENVI. I will fix this problem. Meanwhile would you please use the recent ENVI CAT? Thanks, Feng
  17. Feng
    Hi Emran, You may apply Custom Stretch to stretch this image. Thanks, Feng
  18. Feng
    Hi Emran, I want to double check with you that the error happened on ENVI classic version not the recent ENVI version? Like your previous post shows a processed flatten image in recent ENVI version. I will run the processing on the classic ENVi to see if the error shows up. Thanks, Feng
  19. Feng
    Hi Emran, I never see this error before. So I try to see if I can replicate this error on my end with the data you are working on. It went smoothly without any error. See screenshot below. What is your ENVI version? Thanks, Feng
  20. Feng
    Hi Emran, Would you please attached the hdr file of the data that you process the flattening summer here? Thanks, Feng
  21. Feng
    Hi Emran, Would you please try to do the processing again to see if the error showing again? I want to check if the error can be replicated or just one time issue. Thanks, Feng
  22. Feng
    Hi Al, I am here to assistant you to fix this issue. By tracking the error message you posted, it seems there is some problem with ENVI views. When you do the processing, how many views do you open? It may be too many views opened so ENVI throws out an OVERLOADEQ error. Thanks, Feng
  23. Feng
    Hi Al, I am ready to help. The problem to me seems an IDL_PATH issue. Would you please verify the following path in the idl.pref file (in default installation, it locates C:\Program Files\Harris\ENVI54\IDL86\resource\pref folder)? IDL_PATH: + C:\Programmi\CAT_ENVI;<IDL_DEFAULT> If there is no such statement in this file, would you please add it? Let's me know if you do see this path. Thanks, Feng Friday at 10:31 AM Edit Report Al Emran Hi Feng, Thank you for the reply. Yes, I have solved the problem. Thanks, Emran Sunday at 04:16 PM 0 Report
  24. Feng

    Hi Al,

    I am ready to help. The problem to me seems an IDL_PATH issue. Would you please verify the following path in the idl.pref file (in default installation, it locates C:\Program Files\Harris\ENVI54\IDL86\resource\pref folder)?

    IDL_PATH: + C:\Programmi\CAT_ENVI;<IDL_DEFAULT>

    If there is no such statement in this file, would you please add it? Let's me know if you do see this path.

     

    Thanks,

     

    Feng

     

    1. Al Emran

      Al Emran

      Hi Feng,

      Thank you for the reply. Yes, I have solved the problem.

      Thanks,

      Emran

×
×
  • Create New...