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.
I am trying to work with comet C/2020 F3 using the 1.083 beta. I get to Integration and it aborts, complaining about not having enough disk space (21GB) to complete the task.
I have 42 lights and 164 each of darks, flats and biases. All of them are NEF files (raw Nikon). The work directory is set to an external USB drive with a capacity of 5 TB and which is now half-full. I would expect that APP would figure that 21 GB needed to integrate the 42 normalized images is much less than the 2.2 TB of free space.
Why is this happening and what can be done to correct this?
Mmm, it could be that the OS is reporting a wrong number maybe, I’ve seen this before. Or there is an issue with working with the external drive somehow, can you check if it works when you use a local disk? It is usually recommended to use a fast internal disk as APP is doing a lot of disk interaction during the processes.
Vincent, I have been checking the previous threads. I am using an external USB3 drive for a working directory.
What happens is that during integration, the File Explorer comes up after Windows 10 chimes with the contents of the I: drive (the external drive). Eventually APP fails, despite the fact that there are 2.3 TB available, because it cannot find 21 GB. I point the working directory to a folder called I:/C2020 F3 APP.
I am working with a gaming machine: ASUS 751GJ, 24GB RAM, running Windows 10 Home version 1903. The internal drive (C:) is 1 TB (931GB) with 910 GB used and 21 GB remaining. Perhaps APP is reading C: instead of I:.
I will move the pictures off C: and onto the I: drive, thus freeing 663 GB. I will repeat the operation and let you know of the results. It is just that I have wasted hours dealing with this nonsense.
Ah now that is interesting. If Windows comes up with the contents of the directory, it means the external drive got disconnected and reconnected somehow. Maybe there is an issue with that? This is exactly one of the reasons not to have a working directory on an external drive, that connection needs to be both fast and very stable.
I checked the connections. The external drive connections were and are good. I am in the process of moving data to the I: drive to clear up space. No issues at all, so far.
Usually when these kind of strange behaviors occur, it has something to do with the specific system. These can be caused by a multitude of different things, so that’s really hard to pinpoint. Maybe adding an extra SSD to your system is possible? That will greatly benefit the speed as well.
