What is "working di...
 
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.

[Solved] What is "working directory"?

5 Posts
4 Users
1 Reactions
3,771 Views
(@thomehm)
White Dwarf
Joined: 5 years ago
Posts: 5
Topic starter  

I have just downloaded and installed APP, so I am new.  So, I have a directory ngc6888 with frames from a couple of nights ago.  In this Dir, I have a directory for light, and a directory for flats.  In the light directory, I have directories lum, HAlpha, OIII, and SII.  The first thing I need to do is to set the "working" directory.  Is the working directory ngc6888?  Or am I going to run the program with working directory set to lum, then running everything again with directory set to HAlpha, repeat process with the working directory set in turn to OIII, then SII?  And then combine the results in a separate step?  Or do all types of raw images put into the single working directory and are then tagged somehow?  Or if having subdirectories Lum, HAlpha, OIII, SII is correct, how does APP know what is in what directory?  How does it know where the flats are and what flats go with what filter?  Is there a suggested directory structure?  Is there a document that says how to structure the subdirectories and how to configure APP to understand the structure?



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

The working directory is the place where APP does its processing and can save the end result (and other things like your calibration masters it creates). We are going to change that so you can setup a processing directory just for app which will be remembered and a directory you point to to save any results. This will be in a future version though (likely 1.085). I usually set the working directory to the main folder where my data is, with the lights etc. in subfolders. You can load the lights etc. in APP which will then open in that working directory.



   
ReplyQuote
(@woldsweather)
Neutron Star
Joined: 6 years ago
Posts: 89
 

@thomehm Is it possible to set up a workinmg APP directory? It doesn't even ask me ast the start for one any more.



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

Hi Trevor @woldsweather,

The newer 2.0.0 beta versions will remember your Working Directory per restart of APP, so you do not need to set it each time that you restart APP. But you can easily change it any time by clicking on the big button above the tabbed menu on the left side with 1) Load etc... In the below screenshot, the Working Directory button is the button that says "D:\Rosette-M101-2025-03" which actually is the current Working Directory. Please let me know if that solves it?

WorkingDirectory Button

Mabula



   
ReplyQuote
(@woldsweather)
Neutron Star
Joined: 6 years ago
Posts: 89
 

@mabula-admin many thanks Mabula



   
Mabula-Admin reacted
ReplyQuote
Share: