i4Ds/STIX-GSW

Issues

• Add DOI to GSW github home page/readme

  #210 opened 7 months ago by hannahc243
  0

• Use 'stx_get_science_fits_file' in spectroscopy demo

  #204 opened 7 months ago by paolomassa
  0

• Call to "stx_check_config_files.pro" can cause the startup script to hang

  #205 opened 7 months ago by ennosigaeus
  2

• Check config files at setup

  #192 opened 9 months ago by grazwegian
  0

• Print out ELUT file used for correction

  #200 opened 9 months ago by grazwegian
  0

• Determine best way to implement fine output bin DRM

  #199 opened 10 months ago by grazwegian
  0

• Using .lower_bound and .upper_bound for location in forward fit gives wrong results

  #198 opened 10 months ago by Muriel23
  0

• Option to correct counts per sub-collimator

  #197 opened 10 months ago by grazwegian
  0

• Perform lightcurve ELUT correction only at edges

  #193 opened 10 months ago by grazwegian
  0

• Sum over fine energy bins by default

  #194 opened 10 months ago by grazwegian
  0

• Include transmission through tungsten grids

  #150 opened 10 months ago by grazwegian
  0

• stx_construct_pixel_data.pro works only if both the science and the background L1 fits files contain more than 1 energy bin

  #190 opened 10 months ago by paolomassa
  0

• Some functions fail when time range contains change of day

  #162 opened 10 months ago by FredSchuller
  2

• Option not to write file with stx_science_data_lightcurve?

  #168 opened a year ago by ianan
  0

• Option to subtract the background monitor counts from pixel data

  #187 opened a year ago by grazwegian
  0

• Facility for downloading ELUT and energy bin files without a software update

  #145 opened a year ago by grazwegian
  0

• Demo scripts should not download files to SSW directory

  #142 opened a year ago by grazwegian
  0

• New "imaging-spectroscopy" branch: required steps before merging with the main branch

  #173 opened a year ago by afbattaglia
  0

• xcom estimate of attenuator transmission is outdated

  #141 opened a year ago by grazwegian
  0

• STX_CONSTRUCT_CALIBRATED_VISIBILITY

  #163 opened a year ago by JSGH2020
  1

• SAS pipeline: implement a 'quality flag'

  #129 opened 2 years ago by FredSchuller
  2

• Add support to search for STIX data by time, request etc

  #158 opened a year ago by samaloney
  0

• Background data files with only one time bin don't work as expected in OSPEX

  #156 opened a year ago by samaloney
  0

• Automatic check for FITS file compatibility

  #146 opened a year ago by grazwegian
  0

• Avoid applying time corrections twice to science data

  #148 opened a year ago by grazwegian
  0

• STIX SRM reader in IDL giving the same format as stx_build_pixel_drm

  #154 opened a year ago by afbattaglia
  2

• Default value of 'sumcase' not consistent with documentation

  #139 opened a year ago by FredSchuller
  1

• Update the grid separation to measured value from default of 550.

  #149 opened a year ago by samaloney
  0

• If 'sumcase' is set to 'ALL' but data not present for all pixels then imaging pipeline throws an error

  #152 opened a year ago by FredSchuller
  0

• stx_science_data_lightcurve: Feature for concatenating time profiles of different FITS files

  #113 opened a year ago by afbattaglia
  0

• Add stx_map2fits to the ssw software

  #143 opened 2 years ago by hayesla
  3

• Rename stx_fsw_sd_spectrogram2ospex.pro

  #147 opened a year ago by grazwegian
  0

• User selected spectrum filenames are not always respected

  #126 opened 2 years ago by grazwegian
  0

• Setting `specfile` and `drmfile` has no effect when calling `stx_convert_spectrogram`

  #131 opened 2 years ago by settwi
  3

• HK SAS Data is aggregated onboard

  #115 opened 2 years ago by samaloney
  1

• Add author info for Zenodo

  #128 opened 2 years ago by samaloney
  0

• Option to semi-calibrate lightcurve data for attenuator

  #127 opened 2 years ago by grazwegian
  0

• imaging: should not use SAS solution if not reliable

  #110 opened 2 years ago by FredSchuller
  1

• Additional useful info in output of imaging pipeline

  #111 opened 2 years ago by FredSchuller
  1

• Check if spectrum files exist before writing

  #125 opened 2 years ago by grazwegian
  0

• Environment variables are not correctly set in case sensitive systems

  #112 opened 2 years ago by grazwegian
  0

• Threshold for SAS use needs to be documented e.g. why 200 and not 180 or 220

  #122 opened 2 years ago by samaloney
  0

• For aux-ephemeris do not hard code to 32s but use 1/2 the time between bins?

  #121 opened 2 years ago by samaloney
  0

• Some magic -1 hiding in the coordinate transformation codes need to document why there are needed

  #120 opened 2 years ago by samaloney
  0

• Doc string / name / code don't seem to match

  #119 opened 2 years ago by samaloney
  0

• Improve naming of coordinate/frame conversion function names

  #118 opened 2 years ago by samaloney
  0

• Improve documentation around direction of rolls

  #117 opened 2 years ago by samaloney
  0

• A lot of assumptions made in the conversation of pixel to world coordinates need ensure can't be miss used

  #116 opened 2 years ago by samaloney
  0

• Adjust energy edges to handle 50 eV shift

  #107 opened 2 years ago by grazwegian
  0

• Use daily calibration information to augment spectral correction

  #106 opened 2 years ago by grazwegian
  0