Opened 12 years ago

Closed 12 years ago

#11 closed bug (fixed)

SCbedit & BSEQ/BIL external files in azgcorr

Reported by: mggr Owned by: mggr
Priority: alpha 4 high Milestone:
Component: azgcorr Keywords: bug
Cc: sbg Other processors:

Description

Just a tracker ticket for an issue found in #2. azgcorr wasn't handling the SCbedit vector correctly when BSEQ/BIL files were used.

Reported to Bill 18/May and fixed over the weekend in release 106. Some notes from Bill's email:

Updated azgcorr.481 by separate email.

SCbedit now works as advertised with the limitation that it only works for the first 16 bands of a data set (because it uses an unsigned int). It was originally only put in for the ATM anyway.

The "distortion" was because I had forgotten for BIL/BSEQ input to move the file when a line was skipped, so after each skipped line the image would shuffle up.

So now for CASI and Specim data the only option is the whole frame is skipped if it is flagged. This makes sense because with a CCD sensor it would be pretty unlikely to have a whole row dead, columns maybe but not rows.

The default in azgcorr.48* is if there is NO -be  the SCbedit vector is used;  if there is a -be then SCbedit is not used and no lines/scans are ignored. 

This needs testing

Change History (1)

comment:1 Changed 12 years ago by mggr

  • Resolution set to fixed
  • Status changed from new to closed

Tested, it works.

Note: See TracTickets for help on using tickets.