1. 25 Dec, 2016 1 commit
  2. 24 Dec, 2016 2 commits
    • Mohammad Akhlaghi's avatar
      One pixel rows or columns adjusted in MUSE cutouts · 2135a3ba
      Mohammad Akhlaghi authored
      Due to very small WCS differences, we might be having one column or
      row difference between the warped HST images and the MUSE images. To
      generate the catalog, the two images need to be the same size, so this
      was a problem.
      
      To solve it, the MUSE images are now cutout from the input image in a
      new directory (`muse-cutouts'). Then, after the HST images are warped,
      the MUSE and HST-warped image sizes are compared and if they are
      different, the MUSE image corrected (by one row or column of pixels
      along the respective dimension). Then it is put into the old `cutouts'
      directory. If the sizes are the same, then a copy is just put there.
      2135a3ba
    • Mohammad Akhlaghi's avatar
      Catalogs generated for similar sized cutouts · 0654f265
      Mohammad Akhlaghi authored
      Magnitude and position catalogs are now generated for both the HST
      images and the MUSE images. Using GNU Make's Secondary expansion, we
      don't need the `-h' or `-m' suffixes for the segmentation maps any
      more. Since the instrument name will be removed from the output
      filename during secondary expansion.
      
      The Sky and Sky standard deviation images are now also created. Note
      that since the purpose of this study is calibration, they are set to
      all 0 and all 1 valued images. Finally, using the filters and
      instrument the zeropoint magnitudes are calculated and used for
      MakeCatalog.
      
      Currently the catalogs are only used for similarly sized original
      cutouts. But the cutouts can be differently sized (due to sub-pixel
      differences in the WCS). So when the images have a different size, it
      currently stops.
      0654f265
  3. 23 Dec, 2016 1 commit
    • Mohammad Akhlaghi's avatar
      Segmentation maps built, directories reorganized · e4e7a6c5
      Mohammad Akhlaghi authored
      NoiseChisel is now run on the original HST images and the object
      labeled image is then warped to the MUSE resolution and prepared to
      derive the segmentation maps. To make the prerequisite management of
      the final catalog much more easier, the final cutouts of both MUSE and
      HST are now in the same directory, only differing with a `-m.fits' or
      `-h.fits' suffix. The segmentation maps also follow the same naming
      convention, however, since the segmentation map is identical, the
      `-m.fits' file is actually a symbolic link to the `-h.fits' file.
      e4e7a6c5
  4. 22 Dec, 2016 2 commits
    • Mohammad Akhlaghi's avatar
      Correct estimation of MUSE PSFs and deconvolution · 2c31a594
      Mohammad Akhlaghi authored
      The model MUSE PSFs were incorrectly calculated until now! I was
      mistakenly assuming that the `FSF01FWA' was the FWHM. However, the
      FWHM must be calculated from `b*lambda+a' where `b' is the value to
      `FSF01FWB' keyword and `a' is the value of `FSF01FWA'. The effective
      `lambda' (or wavelength) to use for each broad-band filter is the
      throughput-weighted average wavelength of the filter.
      
      So, the pipeline now uses the HST filter throughputs to find `lambda'
      and then uses the values of these keywords to generate the proper FWHM
      for the Moffat function. The throughputs will be downloaded if not
      already available. The FWHMs decreased from around 14 pixels to around
      10 pixels.
      
      After implementing this correction, a test run of the deconvolution
      gave a better result. The reason was that the image crop to feed into
      the deconvolution algorithm was larger and so lower frequencies could
      be sampled. After seeing this trend, I increased the truncation radius
      of the model MUSE PSFs and also the deconvolution image size and saw
      that the deconvolution output kernel is becoming better and better. I
      finally stopped at 6 times the FWHM since it was apparently not making
      much more change.
      
      So, now the proper kernel to convolve with the HST images is created
      and we can directly compare the results with the MUSE images without
      worrying about a larger PSF. After convolution, the HST images are now
      also sampled to the same pixel size as MUSE.
      2c31a594
    • Mohammad Akhlaghi's avatar
      Top level dirs in build made by one rule · 42f5ffb5
      Mohammad Akhlaghi authored
      The directories directly under the build directory are now built by
      one rule in the top level `Makefile' to avoid the confusion and Make
      errors that can be caused by doing it every time. This can also
      encourage building more of these directories for easy checking.
      
      The size of the kernel was also increased because in the MUSE PSF, 21
      pixels was too small. The problem with the deconvolution is certainly
      more fundamental than that and must be solved separately. So for the
      time being we are ignoring the steps in generating the HST PSF.
      42f5ffb5
  5. 21 Dec, 2016 2 commits
    • Mohammad Akhlaghi's avatar
      Moved the aligned UDF images to a separate directory · 487d752d
      Mohammad Akhlaghi authored
      The aligned UDF (not UDF10) images were in the same directory as the
      cutouts of each subfield. They are now saved in a separate directory
      of the top build directory to make the cutouts directory more easily
      understandable/managable. Especially since the HST images will be
      coming in too soon.
      487d752d
    • Mohammad Akhlaghi's avatar
      MUSE and HST PSFs created, but images not matched · bdca120b
      Mohammad Akhlaghi authored
      The MUSE PSFs were given as parameters to a Moffat function fit. So
      they were created using Gnuastro's MakeProfiles. The HST PSF was also
      generated from one of the bright stars in the UDF. It isn't the
      brightest, but so far we haven't checked if it was saturated or
      not. However, apparently, Gnuastro's convolve had problems in finding
      the kernel to convolve with the HST image to get to the MUSE
      resolution.
      
      So for now, we have kept the rules (to work on them later), but they
      are currently ignored in the pipeline (they aren't a prerequisite to
      anything). Since the MUSE PSF is much wider than the HST, for now, we
      will just convolve the HST image with the MUSE PSF. Later, when the
      problem above is solved, we will find the proper kernel more
      accurately.
      bdca120b
  6. 18 Dec, 2016 2 commits