Author Topic: Zero or insignificant signal detected (empty image?) problem again PI ver.1.8.5  (Read 3404 times)

Offline pantarei

  • Newcomer
  • Posts: 14
Hello, jus tomorrow I had the problem "Zero or insignificant signal detected (empty image?)" when manually integrated 16 ha shots. I have downloaded and run the latest 1.8.5 version of PI. After successful  manual calibration and registration, integration shows this error. I have only managed the fits file into PI, without any manipulation before.
Any suggestions?

Thanks
Max

Offline Graham

  • PixInsight Enthusiast
  • **
  • Posts: 77
Hi, I am having this issue as well. It seems to stem from the calibration process. I ave checked and all files are saved as 32 Float.

Any tips on getting around this or is there a fix?

Thanks.

Offline Graham

  • PixInsight Enthusiast
  • **
  • Posts: 77

Offline wimvb

  • PixInsight Enthusiast
  • **
  • Posts: 91
    • Wims place
Try with noise evaluation turned off. Worked for me.
I have also had this issue when the offset on my camera (zwo asi174 cooled) was too low. Increasing the offset solved the issue as well.
Wim

AZ EQ6 GT + EQ3 PRO, SW 150P-DS, SW MN190, ZWO ASI174MM-Cool, Pentax K20D (retired),
SW ST80 + ZWO ASI120MM + Lin_guider

Offline RickS

  • PTeam Member
  • PixInsight Jedi
  • *****
  • Posts: 1298
Hi, I am having this issue as well. It seems to stem from the calibration process. I ave checked and all files are saved as 32 Float.

Any tips on getting around this or is there a fix?

It's unlikely to be a problem with PI that requires a fix.  The basic calibration processes have been around for a long time and work very reliably.  It's much more likely the problem is elsewhere.  I have seen something similar happen with cameras that have bias drift over time.  You can do some basic troubleshooting with the Statistics process and previews.  A quick fix may be to add a small pedestal to avoid truncation of data values to zero (Output Pedestal in ImageCalibration.)

Cheers,
Rick.

Offline Graham

  • PixInsight Enthusiast
  • **
  • Posts: 77
Thanks Rick, it must be my data(most likely) or my calibration frames(unlikely, as they work on all the other data frames). I ditched the troublesome ones and carried one. Still left me with a significant amount of data to use successfully.  :)

Offline RickS

  • PTeam Member
  • PixInsight Jedi
  • *****
  • Posts: 1298
Thanks Rick, it must be my data(most likely) or my calibration frames(unlikely, as they work on all the other data frames). I ditched the troublesome ones and carried one. Still left me with a significant amount of data to use successfully.  :)

That's good, Graham.  If it happens again it might be worth digging a bit to figure out what is going on.

Cheers,
Rick.