Memory required for...
 
Share:
Notifications
Clear all

15th Feb 2024: Astro Pixel Processor 2.0.0-beta29 released - macOS native File Chooser, macOS CMD-Q fixed, read-only Fits on network fixed and other bug fixes

7th December 2023:  added payment option Alipay to purchase Astro Pixel Processor from China, Hong Kong, Macau, Taiwan, Korea, Japan and other countries where Alipay is used.

 

Memory required for processing

4 Posts
2 Users
0 Likes
757 Views
(@tommohawk)
Main Sequence Star
Joined: 5 years ago
Posts: 24
Topic starter  

Hi all. Recently did a big stack with APP - about 1100 LRGB subs each about 32Mb - and also requested integration of all channels. APP said about 19GB would be required but actually used nearer to 90GB. I only just had enough space to do this and also it took about 7 hours. Maybe it didnt allow for the all channels integration?

Maybe this is normal behaviour for such a big stack - but if so perhaps APP could do the maths accordingly and warn that more space will be required.

Kind regards and take care all

Tom


   
ReplyQuote
(@vincent-mod)
Universe Admin
Joined: 7 years ago
Posts: 5707
 

Well, that's a rather big difference in the estimates so I'm not sure that is correct actually. 1100 frames are a lot though, I normally chop such data into several sessions to integrate and then combine later on.


   
ReplyQuote
(@tommohawk)
Main Sequence Star
Joined: 5 years ago
Posts: 24
Topic starter  
Posted by: @vincent-mod

Well, that's a rather big difference in the estimates so I'm not sure that is correct actually. 1100 frames are a lot though, I normally chop such data into several sessions to integrate and then combine later on.

I guess maybe that's the way to go then. But how do I know the reference frame from the first stack and use that as reference for subsequent stacks?


   
ReplyQuote
(@vincent-mod)
Universe Admin
Joined: 7 years ago
Posts: 5707
 

To find that out I think you still would need to do a star analysis on all frames. Then pick that one frame and use it for all sub-integrations. But I think, when data is consistent enough, you can just stack 300 or so frames with it selecting the reference from those each time.


   
ReplyQuote
Share: