Updated SXT Analysis Software


Greetings,

As a result of recent work improvements are being made in dark
signal and leak signal corrections in analysis of SXT images.
Most of these improvements are now online at MSU for beta-testing.
The following message from Sam Freeland details what has been
done so far.

If you run into problems analyzing SXT data with these new tools
please let Freeland, Metcalf and Acton know with an information
copy to software@isass0.

Cheers,

Loren
==========================================================
Date: Tue, 10 Feb 1998 16:11:43 -0800
From: Samuel L. Freeland 
Subject: RE: "The Movie", corrections, msu status etc.

Here is what MSU has online at under Yohkoh ($ys) environment
as of Tue Feb 10 18:41:44 EST 1998.

   a. Leak image selection updated to use solar Diameter (match_index)
   b. morning interval dbase and access SW (sxt_uvf_info et at al)
   c. latest JPW ATT corrections
   d. latest TM updates to SDC orbital variation correction
      (dark_sub, get_dc_image, sel_dc_image, dc_orbit_correct)
   e. updated sxt_prep (/DC_ORBIT_CORRECT and /NO_DC_ORBIT_CORRECT switches)
   f. sfc_prep updated (to force orbital SDC orbital correction on)

>>    NOTE: Use /DC_ORBIT_CORRECT switch if applying SDC via sxt_prep
      (if calling dark_sub directly, include /ORBIT_CORRECT switch if desired)
      Until algorithm is optimized, the DEAFULT IS /NO_DC_ORBIT_CORRECT. 
      Preliminary indications (long auto-toban run times, etc) are that 
      the orbit dc correction adds lots of processing time - Greg and Tom
      will look into speeding this up users can force on with the switches.
      
What you DON'T have (independent of your updating the sfc history records)

   a. full SFC dbase with SDC oribital correction.
    
   The orbitally-corrected SFC job is currently running at isass0 with 
   a virgin SFC output diretory.  I set the delta-Pnt for Al.1 to .01" 
   (from 3") in the mk_sfc param file - we can reduce that parameter
   for other filters if that is desired (SFC DBASE size / network transfer
   times and remote site disk-clobbering are tradeoffs).
   In any case, it is likely to get large and take a while to transfer
   to MSU.
   
Sam (currently at GSFC for EIT/TRACE/SSW)


Return to help page