FOV Size Preventing...
 
Share:
Notifications
Clear all

UPDATE FROM MABULA

I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.

 

Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.

 

APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46.  Before I release it, I will make sure that everything is working properly and then I will release it.

FOV Size Preventing Integration

2 Posts
2 Users
0 Reactions
386 Views
(@p-dickensky-com)
Molecular Cloud
Joined: 3 months ago
Posts: 1
Topic starter  

Hi, complete non-tech savvy newbie here. 

I have a Vaonis Vespera Pro.

I attempted my first stack with APP and failed at the integration stage.  I received three consecutive error messages all referrring to insufficient RAM.  I have 32 GB of RAM which I know ordinarily to be enough.  I tried reducing the scale right down but this did not solve the issue.  After the third error message there is a bell sound and the integration fails.  

I then checked the FOV size and it was utterly ginormous, millions x millions, clearly hence the problem.

I then changed to a completely diffrent data set for a different target.  This time the FOV size was 10000 x 11000 and would have needed 805 GB of hard disk space to integrate.

I seem to have a problem with the FOV size post Registration.

Can somebody please help as I cannot get beyond registration currently due to the FOV size.

Thank you


This topic was modified 3 months ago 3 times by Philip Dicken

   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5379
 

Hi Philip @p-dickensky-com,

Thank you very much for your question and welcome to the APP forum !

From your description, it does sound like that you are trying a big mosaic right? Or are the images all shot at the same part of the sky, the same Field of View?

How are your images shot and how many images are you trying to process?

If it is a mosaic, it is recommended that you make mosaic panels first. For instance, if you have 100 images divided over 10 different Field Of Views, then you want to make 10 stacks first of your 10 Field of Views. Then those 10 stacks/integrations can be loaded as lights and run as a mosaic in 4) Register. THen it will be much faster and easier, also way more robust.

Please let me know if this helps.

Mabula



   
ReplyQuote
Share: