Koa Wu

Thanks again, Martin. As I described in the reply to Han, I don't get calibration frames from Origin, only masters do I get. So my question is still how to use the master calibration files to calibrate multi-session lights data in ASTAP. I have to admit that when generate darks, I only tell Origin to take 10 frames of 60" exp. That takes me about 12' before starting a session. If I do 20 frames, it will be 25'... For 40 frames, it will be about 1 hour! Maybe I should take a cloudy night to make 5...

Hi Han, Thanks for coming back to help me. Ok, now I understand if there are same file names from different sessions, as long as they come from different folders containing the lights from different session, it does not cause ASTAP to "over-write" or delete any data files. Great news. Calibration files still confuse me here. How Origin generates calibration files is as below: the user has to activate to generate darks and flat from its app, then Origin will create master dark, master bias, and master...

Thank you for providing the info and documentation, Martin. I run Celestron Origin for OSC imaging only (so far). There are two issues need to be clarified/verified when adopting your multiple nights stacking method. First, all sessions' lights file names are mostly the same, as they run the frame number starting like: Light0001.fits, Light0002.fits, ... I suspect ASTAP will over-write all same name files and delete most of the sessions data. Do I need to rename all lights file names before stacking?...

Hi, how can I run multi-session stacking with ASTAP? I need a guideline to do my multi-session project. Please help.

Same here. Meteorologist 4.1.1 just disappeared and won't re-start.

Thanks, good to know. Yet, what does the background value mean (range from 10xxx to 2yyyy)? I see high value related to cloudy situation, so poor quality, in one of my sessions. When using ASTAP fits viewer, can it be pushed to auto stretch view, so a faint (at least) target can be visible or the target disappears behind clouds?

Thank you, Han. I reloaded all the light subs and "quickly" analyzed them. I checked the "quality" tab showing a number (from 1 to 50?) for each light frame and "stars" tab showing number of stars detected for each light frame. Roughly the quality numbers from 1 to 10 are with poor shaped (elongated) stars and lower quantity of stars (< 200). These are validated with the fits viewer in ASTAP. I assume the frames with elongated stars are related with poor/no guiding during the long exp time. The second...

Thanks for the tip. Your suggestion of adjusting the detection settings implies to loosen the rejection criteria, thus lowering the rejection rate. However, it's not what in my mind, yet still good to know. So, let's say we keep same detection settings as all defaults for different imaging sessions (projects). It comes out 1 in 10 sessions has a significantly high rejection rate during the stacking process. I would assume the rejected frames must contain some poor data (or lack of data) with no contribution...