Details

    • Type: Task
    • Status: Open (View Workflow)
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Sprint:
      PreRun21Mar

      Description

      R3 has a bright feature on right-on side, that seems to be evolving with time.

      One has to look at all the r3 darks taken recently, and see how this feature evolve with time.
      We certainly need a two component darks. as far as I understand we currently scale the dark by using a bbox on the defect but that's not a good model overall.

        Attachments

        1. dark_2023-07-19.gif
          dark_2023-07-19.gif
          4.83 MB
        2. dark_2023-12-16.gif
          dark_2023-12-16.gif
          4.78 MB
        3. dark_2024-05-02.gif
          dark_2024-05-02.gif
          10.13 MB
        4. dark_2024-08-25.gif
          dark_2024-08-25.gif
          5.70 MB
        5. dark_20241017_128x256.gif
          dark_20241017_128x256.gif
          1.02 MB
        6. Diffs_from_original_113492.png
          Diffs_from_original_113492.png
          736 kB
        7. Diffs_from_original_115591.png
          Diffs_from_original_115591.png
          705 kB
        8. Diffs_from_original_combined.png
          Diffs_from_original_combined.png
          724 kB
        9. Diffs_from_original_v2_run18.png
          Diffs_from_original_v2_run18.png
          791 kB
        10. Diffs_from_original_v2.png
          Diffs_from_original_v2.png
          1.60 MB
        11. Diffs_from_original.png
          Diffs_from_original.png
          776 kB
        12. Figure 1 - 2024-09-22T132720.065.png
          Figure 1 - 2024-09-22T132720.065.png
          1.82 MB
        13. pca_components_all_combined.png
          pca_components_all_combined.png
          1.68 MB
        14. PCA_components.png
          PCA_components.png
          1.09 MB
        15. PCA_Cumulative_Variance.png
          PCA_Cumulative_Variance.png
          65 kB
        16. PCAcomponents_r3dark_2025Jan.png
          PCAcomponents_r3dark_2025Jan.png
          1.54 MB
        17. run18_components_v2.png
          run18_components_v2.png
          1.02 MB
        18. run18_run19_combined_components.png
          run18_run19_combined_components.png
          955 kB
        19. run19_components_v2.png
          run19_components_v2.png
          1.87 MB
        20. run19_components.png
          run19_components.png
          440 kB
        21. stdev.png
          stdev.png
          108 kB

          Activity

          Hide
          naoki.yasuda naoki.yasuda added a comment -

          I have done the same analysis for run18 data.

          Here is PCA components.

          This is the difference between the original image and the reconstructed image with various numbers of components for a visit (113513).

          In this case, 1 or 4 components are preferable.

          Show
          naoki.yasuda naoki.yasuda added a comment - I have done the same analysis for run18 data. Here is PCA components. This is the difference between the original image and the reconstructed image with various numbers of components for a visit (113513). In this case, 1 or 4 components are preferable.
          Hide
          naoki.yasuda naoki.yasuda added a comment -

          When the data from run18 and run19 are combined, the PCA components will become this.

          In this case, ~3 components may be needed.

          However, there is a case we cannot reconstruct the image properly even if we use more components.

          This visit is not used for the calculation of PCA.

           

           

          Show
          naoki.yasuda naoki.yasuda added a comment - When the data from run18 and run19 are combined, the PCA components will become this. In this case, ~3 components may be needed. However, there is a case we cannot reconstruct the image properly even if we use more components. This visit is not used for the calculation of PCA.    
          Hide
          naoki.yasuda naoki.yasuda added a comment -

          I'm trying to use all the data from previous runs. I have selected 5 frames each from the previous 5 runs (run12 20230719, run14 20231216, run16 20240502, run18 20240825, run19 20241017), for a total of 25 frames. Then I did the PCA analysis. However, as shown in the figure showing the first 20 PCA components, I'm not sure yet what's happening. Components 11, 12, and 15 look more important than 6-10. Residual CRs or some other features may contribute to components 6-10 but I need more investigation to confirm.

           

          Show
          naoki.yasuda naoki.yasuda added a comment - I'm trying to use all the data from previous runs. I have selected 5 frames each from the previous 5 runs (run12 20230719, run14 20231216, run16 20240502, run18 20240825, run19 20241017), for a total of 25 frames. Then I did the PCA analysis. However, as shown in the figure showing the first 20 PCA components, I'm not sure yet what's happening. Components 11, 12, and 15 look more important than 6-10. Residual CRs or some other features may contribute to components 6-10 but I need more investigation to confirm.  
          Hide
          naoki.yasuda naoki.yasuda added a comment -

          The following figure shows how StDev of residual images for each dark frame varies as a function of the number of PCA components used. The frames with the same color were taken on the same night. As can be seen, except for the first few components, each PCA component affects only the data taken on a specific night and seems to trace noise-level details. Something seems to be wrong. ???

          Show
          naoki.yasuda naoki.yasuda added a comment - The following figure shows how StDev of residual images for each dark frame varies as a function of the number of PCA components used. The frames with the same color were taken on the same night. As can be seen, except for the first few components, each PCA component affects only the data taken on a specific night and seems to trace noise-level details. Something seems to be wrong. ???
          Hide
          naoki.yasuda naoki.yasuda added a comment - - edited

          I have analyzed the dark data taken during the January 2025 commissioning run (run20). Specifically I have used the following visits. 

          {20250123: [119786, 119792, 119790, 119787, 119789],
           20250125: [120106, 120112, 120111, 120105, 120093],
           20250127: [120581, 120579, 120580],
           20250128: [120727, 120726, 120721, 120723, 120722]}
          

          Only two PCA components are significant, with the first component explaining 99.8% of the variance. This suggests that the amplifier glow is stable within each run. While applying just the first component is sufficient, the second component can also be included. Despite applying the RepairTask on each frame and using the Robust PCA algorithm to isolate a low-rank matrix from noisy features (in this case, cosmic rays), some cosmic ray contamination remains. To include the second PCA component for dark subtraction, Robert's new cosmic ray remover may need to be applied. 

          Show
          naoki.yasuda naoki.yasuda added a comment - - edited I have analyzed the dark data taken during the January 2025 commissioning run (run20). Specifically I have used the following visits.  {20250123: [119786, 119792, 119790, 119787, 119789], 20250125: [120106, 120112, 120111, 120105, 120093], 20250127: [120581, 120579, 120580], 20250128: [120727, 120726, 120721, 120723, 120722]} Only two PCA components are significant, with the first component explaining 99.8% of the variance. This suggests that the amplifier glow is stable within each run. While applying just the first component is sufficient, the second component can also be included. Despite applying the RepairTask on each frame and using the Robust PCA algorithm to isolate a low-rank matrix from noisy features (in this case, cosmic rays), some cosmic ray contamination remains. To include the second PCA component for dark subtraction, Robert's new cosmic ray remover may need to be applied. 

            People

            • Assignee:
              naoki.yasuda naoki.yasuda
              Reporter:
              arnaud.lefur arnaud.lefur
            • Votes:
              0 Vote for this issue
              Watchers:
              Start watching this issue

              Dates

              • Created:
                Updated: