Does "Default Bad Bands" applied to trr3 Data?

[Rochdi]

Hello Explorers,

I want to make sure whether the default bad bands algorithm is already applied to TRR3 datasets or not. I noticed that in your useful doc "CRISM Data Users' Workshop Nili Fossae Data Processing Walkthrough". The example of (page 10) shows that before the S (VNIR) TRR2 cube being converted to CAT format, some bad bands have been detected at 0.4um and 0.7um as well while TRR3 version not, in this version it seems like the mentioned algorithm is already applied. If it's so, does conversion to CAT can affect on the future pre-processing analyses (I mean photometric correction, atmospheric correction, etc)?

Look forward to your reply,

Rochdi Khalid.

[Ray Arvidson]

Bad bands have been applied to TRR3 products. TRR2 products should not be used as they represent only an initial phase of calibration. You can see which bands have been assigned as bad by looking at the ENVI header records.

Ray Arvidson

[Rochdi]

That's it, but why when I extracted the spectral profile to a *.txt file, the file still include the default bad bands?

[Ray Arvidson]

Because the bad bands are applied in CAT using the HDR record and in the spectral display. Remove them manually from the text file using the bad band list in the HDR list.

[Rochdi]

That's what I did yesterday, thanks a lot sir.