1. 22 Jan, 2021 1 commit
  2. 03 Jan, 2021 1 commit
  3. 07 Nov, 2020 2 commits
  4. 26 Oct, 2020 1 commit
  5. 25 Oct, 2020 1 commit
    • Jasem Mutlaq's avatar
      Major refactoring for FITSViewer and how FITS and other data is handled: · e1289951
      Jasem Mutlaq authored
      1. Eliminate any unncessary "temporary" files. If we have a buffer, use it without creating any files on disk unless strictly required.
      2. Use a shared pointer for data so that FITSView instances are implicitly sharing the same pointer. This finally allowed for Summary View to load the same view as FITS Viewer without incurring any memory penalty.
      3. Add metadata to the FITSImage object to pass information that were passed before using AUX members of the blob which was not safe.
      4. Add support to load RAW camera files directly in the FITS Viewer along with loading JPEG/PNGs that were added by Robert earliar.
  6. 13 Oct, 2020 1 commit
  7. 29 Sep, 2020 1 commit
  8. 22 Sep, 2020 1 commit
  9. 20 Sep, 2020 1 commit
  10. 03 Jul, 2020 1 commit
  11. 26 Apr, 2020 1 commit
  12. 17 Apr, 2020 1 commit
    • Hy Murveit's avatar
      SEP Focus improvements · 515efd42
      Hy Murveit authored
      This PR should improve the HFR calculations with SEP for the focus module and for displaying HFR for those that want to track it in subs.
      It is not the end-all, but should be an improvement. There is still work to do.
      - Updated and added to tests for the fitssepdetector.cpp
      - Removed saturated stars from the HFR calculation, if possible.
      - Sped up the SEP star detector 2X when used with full exposures.
      - Improved SEP star detector quality, especially for focus/hfr, by (1) changing the deblend constant, and (2) removing the largest stars
      - Fixed two bugs in the SEP star detector (1) major issue, ushorts being treated as shorts, and (2) a memory leak for (rare) float images
      - Added logging for HFR when calculated
      - Fixed bug so that Mark Stars now works
      - Improved drawing of circles for Mark Stars, now uses star radius, instead of flakey star width.
      - Updated the fitsviewer status to include the HFR when calculated
      - Increased a threshold in SEP extract.c which previously would fail on images, e.g. like M42, where there was a lot of area over background.
      Not done, but related:
      - Should improve the MarkStars UI so that HFR could be calculated without star annotation on display, and could turn on on first image.
      - API to star detection methods should be generalized (should wait on rlancaste's investigations of SEP best practices)
      - Some display of HFR trends.
      Test Plan:
      Basic test added to testfitsdata for SEP, run that.
      Load a .fits file into fitsviewer. Select view->MarkStars, for a full-exposure sub, you should see ~100 stars circled with an HFR displayed in the status bar.
      Load another image and the HFR should continue to be displayed.
      Similarly, one could make a capture sequence job with, say 20 5s simulator exposures. After the first exposure completes and the fitsviewer displays
      the image, go to the view menu and turn on Mark Stars, then the rest of the images should display with stars circled and HFR displayed in the status bar.
      This way of turning on the star/HFR detection should be improved in a future PR.
      Reviewers: mutlaqja, lancaster, TallFurryMan
      Reviewed By: mutlaqja, lancaster, TallFurryMan
      Subscribers: kde-edu
      Tags: #kde_edu
      Differential Revision: https://phabricator.kde.org/D28767
  13. 08 Dec, 2019 1 commit
    • Hy Murveit's avatar
      New UI to allow the user to modify the stretch being used. · 08fd2a3b
      Hy Murveit authored
      In fitsviewer, the toggle stretch button is removed and replaced with a
      stretch bar at the bottom of the window. It is always there and allows
      the user to turn on/off stretching, use the automatically generated stretch
      or modify the stretch parameters. As before, this is a display-only change
      to the image, it does not modify the image itself.
      Test Plan:
      In kstars, open a new fits file with the auto-stretch option either set
      or not, and see if it displays accordingly. Then switch the other way
      using the UI and play with the sliders to adjust the stretch. Try another
      image also. Go back to the first image, it should remember the parameters
      that were last used. Should work similarly with images from capture.
      Evaluate the UI.
      Reviewers: mutlaqja, lancaster, wreissenberger
      Reviewed By: mutlaqja, lancaster
      Subscribers: kde-edu
      Tags: #kde_edu
      Differential Revision: https://phabricator.kde.org/D25645
  14. 27 Oct, 2019 1 commit
    • Hy Murveit's avatar
      Write FITS file on separate thread · c72edccb
      Hy Murveit authored
      When capturing images, previously once the capture was complete, images were written
      to disk, then read back, then displayed in the fits viewer (if enabled), and finally the
      next image could be captured. This delayed the next capture by a few seconds.
      With this change, the FITS data is displayed using (a copy of) the INDI blob
      sent to indiccd, a memory buffer, and the FITS data is written to disk on a separate thread,
      which does not block the next capture nor the display of the indi data.
      This was only implemented for FITS data. This change also involved some refactoring
      in the affected files.
      Reviewers: mutlaqja
      Reviewed By: mutlaqja
      Subscribers: kde-edu
      Tags: #kde_edu
      Differential Revision: https://phabricator.kde.org/D24976
  15. 14 Sep, 2019 1 commit
  16. 04 Sep, 2019 2 commits
  17. 03 Aug, 2019 1 commit
  18. 25 Jul, 2019 1 commit
  19. 16 Jul, 2019 1 commit
  20. 08 Jul, 2019 1 commit
  21. 06 Dec, 2018 1 commit
  22. 04 Dec, 2018 1 commit
  23. 29 Nov, 2018 1 commit
    • Robert Lancaster's avatar
      Fixing a crash caused by QCustomPlot's replot method in a concurrent thread · de5eb025
      Robert Lancaster authored
      Fixing an intermittent crash caused by QCustomPlot's replot method
      being used in a concurrent thread  The reason for it is because Qt does not
      support painting to GUI elements in any thread but the GUI thread and
      QCustomPlot's replot method includes a repaint.  So if the Histogram is
      currently visible and construct histogram is run in a concurrent thread,
      the program would call replot and crash.
      Reviewers: mutlaqja
      Reviewed By: mutlaqja
      Subscribers: kde-edu
      Tags: #kde_edu
      Differential Revision: https://phabricator.kde.org/D17228
  24. 26 Nov, 2018 1 commit
    • Robert Lancaster's avatar
      Creating the FitsTools Panel and Histogram Fixes · 5c39c2da
      Robert Lancaster authored
      Creating the FitsTools Panel on the left side of the FITSViewer to contain the Histogram, the FITSHeader, and the Statistics.
      In the future, this will be a good location for parameters for liveStacking and possibly a recent tab too.
      Also fixed some bugs in the Histogram and made the histogram more responsive.
      Reviewers: mutlaqja
      Reviewed By: mutlaqja
      Subscribers: yurchor, kde-edu
      Tags: #kde_edu
      Differential Revision: https://phabricator.kde.org/D17147
  25. 05 Nov, 2018 1 commit
  26. 24 Oct, 2018 1 commit
  27. 02 Oct, 2018 1 commit
  28. 01 Oct, 2018 2 commits
  29. 29 Sep, 2018 1 commit
  30. 01 Jul, 2018 1 commit
  31. 27 Jun, 2018 1 commit
  32. 29 May, 2018 1 commit
  33. 21 Apr, 2018 1 commit
  34. 11 Apr, 2018 1 commit
  35. 05 Apr, 2018 1 commit
  36. 27 Jul, 2017 2 commits