Hi Hans,
I wonder whether you've tried the sequence on a fits file. (Tried using ASTAP 80.9.398)
1. Solve (for coordinates)
2. Image (CCD) Inspector
Solve goes as fast as usual. But on Win10 2004, it takes a very long time to do the Image Inspector. In fact, windows says that ASTAP is not responding. However, eventually, the solution is found.
However, the above sequence works fine. Both steps are very fast on Win10 1909. Weird!
cytan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's an interesting observation. I'm still on 1903 but will force an update to Win 10 2004.
In rare cases ASTAP can select the wrong background value for finding stars. It will take then a long time before it finds all stars. Would be strange if that is related to update 2004 but let's see. Sometimes Win10 is also very slow in disk access for some unknow reasons/background processes running.
Note also that ASTAP 0.9.398 was build with a newer compiler.
Anyhow user feedback is good and appreciated . It is difficult to test all features while releasing a new version. Only the source code which has changed is tested, but other featured should be uneffected since code hasn't changed.
Last edit: han.k 2020-08-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you just do either platesolve or ccd inspect, there is no loss in speed. It only exhibits this odd behavior when I do platesolve, then inspect on 2004. Very odd.
cytan
That's an interesting observation. I'm still on 1903 but will force an update to Win 10 2004.
In rar cases ASTAP can select the wrong background value for finding stars. It will take then a long time before it finds all stars. Would be strange if that is related update 2004 but let's see. Sometimes Win10 is also very slow in disk access for some unknow reasons/background processes running.
Note also that ASTAP 0.9.398 was build with a newer compiler.
Anyhow user feedback is good and appreciated . It is difficult to test all features while releasing a new version. Only the source code which has changed is tested, but other featured should be uneffected since code hasn't changed.
Hi Han,
I'm not too surprised that it's not reproducible. It's just weird that this slow down is seen only with the actions that I had posted. When done as the first action after restarting ASTAP, there's no slow down at all.
I have 2 laptops dedicated to imaging: an Athlon A9 (updated to win10 v2004) and the other a Celeron (not updated). The Celeron doesn't see this problem at all while the Athlon does. Like I said, it's just very weird.
cytan
On Thursday, August 13, 2020, 06:26:44 AM CDT, han.k han59@users.sourceforge.net wrote:
At the moment I don't see any problem with the win10 version 2004. Wait and see.
Hi Hans,
I wonder whether you've tried the sequence on a fits file. (Tried using ASTAP 80.9.398)
1. Solve (for coordinates)
2. Image (CCD) Inspector
Solve goes as fast as usual. But on Win10 2004, it takes a very long time to do the Image Inspector. In fact, windows says that ASTAP is not responding. However, eventually, the solution is found.
However, the above sequence works fine. Both steps are very fast on Win10 1909. Weird!
cytan
That's an interesting observation. I'm still on 1903 but will force an update to Win 10 2004.
In rare cases ASTAP can select the wrong background value for finding stars. It will take then a long time before it finds all stars. Would be strange if that is related to update 2004 but let's see. Sometimes Win10 is also very slow in disk access for some unknow reasons/background processes running.
Note also that ASTAP 0.9.398 was build with a newer compiler.
Anyhow user feedback is good and appreciated . It is difficult to test all features while releasing a new version. Only the source code which has changed is tested, but other featured should be uneffected since code hasn't changed.
Last edit: han.k 2020-08-06
If you just do either platesolve or ccd inspect, there is no loss in speed. It only exhibits this odd behavior when I do platesolve, then inspect on 2004. Very odd.
cytan
Sent from Yahoo Mail for iPad
On Thursday, August 6, 2020, 4:19 AM, han.k han59@users.sourceforge.net wrote:
That's an interesting observation. I'm still on 1903 but will force an update to Win 10 2004.
In rar cases ASTAP can select the wrong background value for finding stars. It will take then a long time before it finds all stars. Would be strange if that is related update 2004 but let's see. Sometimes Win10 is also very slow in disk access for some unknow reasons/background processes running.
Note also that ASTAP 0.9.398 was build with a newer compiler.
Anyhow user feedback is good and appreciated . It is difficult to test all features while releasing a new version. Only the source code which has changed is tested, but other featured should be uneffected since code hasn't changed.
ASTAP can be very slow on Win10 2004
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/astap-program/discussion/general/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
At the moment I don't see any problem with the win10 version 2004. Wait and see.
Hi Han,
I'm not too surprised that it's not reproducible. It's just weird that this slow down is seen only with the actions that I had posted. When done as the first action after restarting ASTAP, there's no slow down at all.
I have 2 laptops dedicated to imaging: an Athlon A9 (updated to win10 v2004) and the other a Celeron (not updated). The Celeron doesn't see this problem at all while the Athlon does. Like I said, it's just very weird.
cytan
On Thursday, August 13, 2020, 06:26:44 AM CDT, han.k han59@users.sourceforge.net wrote:
At the moment I don't see any problem with the win10 version 2004. Wait and see.
ASTAP can be very slow on Win10 2004
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/astap-program/discussion/general/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/