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.
Is there a method of pausing APP mid-flow without cancelling the current operation?
I am running a big stack of 9849 frames, it will take a few days, and I will need to put the machine to sleep overnight.
Thanks.
There is not, but I would advise to not do almost 10000 frames in 1 go. It's better to split those kind of volumes up into several integrations as I'm afraid your memory will be very limiting in this case.
@vincent-mod
Hi Vincent,
I will try... My computer has 64GB of system memory with 224GB of NVMe as memory page space and another NVMe(x4) with 1.74TB for workspace; with an AMD Ryzen 9 3900X 12-Core processor. It's a newly rebuilt computer (I kept the same case so it's not a new computer) specifically to cope with APP, as my 2nd Gen i7 was very slow.
I have noted that because I am doing a long scan there is an issue with the normal method of having reference frames, so I have to stack in Mosaic mode otherwise I am limited to about 400 to 500 frames before the registration process starts to go squiffy.
Thanks.
Best,
Susan.
Next problem:
===================== 6) INTEGRATE ========================
It seems that there is not enough free space on this harddisk partition for APP to perform it's task.
Please choose what to do now:
1) I will try to clear space on my harddrive now before trying to continue.
2) Let APP try to test the actual available space.
3) just ignore this warning and try to continue...
4) cancel this Integration task.
Solutions could be to choose
- another Work Directory on another harddisk or
- reduce the integration scale factor
before starting a new integration task.
free space left in GBs: 1787.2
harddisk space required for this task in GBs: 3928.6
========================================
Oops!
Trying with a Scale of 0.5...
Changing work directory works well for me Never try scale reduction
Kijja
Hi Kijja, thanks but I do not have a 4TB drive 🙁
..................
Next Issue - APP can create an image which it can then NOT read!!!
My guess, "combine RGB" uses a signed 16 bit integer for it's array size. Or there is a maximum array dimension?
=================== Combine RGB ======================
Encountered error in module:
LokationAndScaleEstimateWorker
Error message:
java.lang.NegativeArraySizeException
Cause:
null
h.a(Unknown Source)
s.a(Unknown Source)
s.doInBackground(Unknown Source)
javax.swing.SwingWorker$1.call(SwingWorker.java:295)
======================== END ===========================
Exposurer: 394 seconds/frames
Size: 59983 x 7437
Hi
Oh! That is an extremely big project The only thing I can think of is deselecting 3/4 normalized frames to integrate 1/4 each time. Once you have all 4 integrated files saved, go back to tab 1 and clear all files. Then load the 4 integrated files as lights and start integration. Hope this would work for your project.
kijja
Okay, restacked BUT still won't open with a 0.2x size of 23993 x 2975...
Mmm, this could be pushing the limits indeed. So the making of the 4 seperate integrations did work?
