Hi @han59, Thank you for the reply :-) Yes, the solving works, but stacking has a problem, visible on the image I posted earlier, it seem the registering was not correct. I expected the similar behavior like DSS, but the stacking result from ASTAP is not good in my case.. What could go wrong here?
Hi @han59Han, Thank you for the reply :-) Yes, the solving works, but stacking has a problem, visible on the image I posted earlier, it seem the registering was not correct. I expected the similar behavior like DSS, but the stacking result from ASTAP is not good in my case.. What could go wrong here?
Bump.
I am very new to this application (so far I was using DSS), and interested in ASTAP because of possibility to stack on very faint objects based on ephemerides. However, my first attempt in stacking producesd strange result, see attached image. While DSS stack is OK, it seems ASTAP didn't register frames properly.. there is a shift and stars are not round. Also, I tried to solve one of the CR2 frames and the stacked image below, but solution was not found (I have D50 installed). What am I doing wrong?...
I am very new to this application (so far I was using DSS), and interested in ASTAP because of possibility to stack on very faint objects based on ephemerides. However, my first attempt in stacking producesd strange result, see attached image. While DSS stack is OK, it seems ASTAP didn't register frames properly.. there is a shift and stars are not round. Also, I tried to solve one of the CR2 frames and the stacked image below, but solution was not found (I have D50 installed). What am I doing wrong?...
I am very new to this application (so far I was using DSS), and interested in ASTAP because of possibility to stack on very faint objects based on ephemerides. However, my first attempt in stacking producesd strange result, see attached image. While DSS stack is OK, it seems ASTAP didn't register frames properly.. there is a shift and stars are not round. What am I doing wrong? Thank you in advance and clear skies, Bojan
I have HP Compaq 6300 desktop, and I want to clone existing SSD to a slightly smaller one (256GB => 250GB). First, i shrunk OS (C:) partition in order the whole thing to fit. Then, the procedure was as follow: dev-dev, expert, local -icds, k1 I ended with 2.39 GB unalocated (at the right, see image). How to avoid this situation, because 98MB partition is unmovable and w/o name. Originally it was HP recovery partition. Thanks in advance!
I have HP Compaq 6300 desktop, and I want to clone existing SSD to a slightly smaller one (256GB => 250GB). First, i shrunk OS (C:) partition in order the whole thing to fit. Then, the procedure was as follow: dev-dev, expert, local -icds, k1 I ended with 2.39 GB unalocated (at the right, see image). Gow to avoid this situation, because 98MB partition is unmovable and w/o name. Originally it was HP recovery partition. Thanks in advance!