Naming convention f...
 
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.

 

Naming convention for files created by APP

6 Posts
2 Users
1 Likes
1,193 Views
(@wvreeven)
Quasar
Joined: 6 years ago
Posts: 2133
Topic starter  

Hi all,

Happy new year!

I started using APP a few months ago and am very happy with it! I still have a LOT to learn in using it but basic stacking now works very well for me. Thanks for this great piece of software!!!

However, I have a request. I recently purchased an ASI1600MM-C Pro camera and filter wheel and I am doing LRGB imaging with it. In order to create a colour image, I do separate integrations of L, R, G and B and then combine them (using PixInsight but that's another topic). The stacks created by APP are all called something like

St-avg-480.0s-LNMWC_1_3.0_none-x_1.0_LZ3-NS-full-eq-add-sc_BWMV_nor-AAD-RL-noMBB_1stLNC_it1.fits

which gives a lot of info about the input data and the configuration options used to create the stack. But when I use the same config for another filter, the file name that gets created is exactly the same and APP prompts to ask if I want to overwrite the file, which obviously I don't want to. So the new file is called

St-avg-480.0s-LNMWC_1_3.0_none-x_1.0_LZ3-NS-full-eq-add-sc_BWMV_nor-AAD-RL-noMBB_1stLNC_it1-1.fits

This is a bit confusing and would like to request if it would be possible to include the filter name in the file name. The filter name is present as a key word in the FITS header of the input files so that info is available. The files name then could become something like

St-avg-480.0s-Luminance-LNMWC_1_3.0_none-x_1.0_LZ3-NS-full-eq-add-sc_BWMV_nor-AAD-RL-noMBB_1stLNC_it1.fits
St-avg-480.0s-Red-LNMWC_1_3.0_none-x_1.0_LZ3-NS-full-eq-add-sc_BWMV_nor-AAD-RL-noMBB_1stLNC_it1.fits
etc

Many thanks in advance for taking this under consideration and sorry if this has been requested before!

Clear skies, Wouter


   
ReplyQuote
(@wvreeven)
Quasar
Joined: 6 years ago
Posts: 2133
Topic starter  

Ah, sorry, I forgot to add one thing. Apparently APP expects DSLR files as input since the output files contain the ISO value of the inputs in their names. However, in case of a non-DSLR camera there is no ISO value but only a Gain value. Could this be detected as well and the file name adjusted to that? Many thanks once more!

Clear skies, Wouter


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

Happy newyear to you too!

I think you forgot to select to process the data with multiple filters (tab 1 Load, multi-channel/filter processing). Is that the case? If you select that, APP will ask you to assign loaded frames to a certain filter and after that it should have different names for all of them. My wild guess is that this is also the reason why you have trouble going further to combine all these...


   
ReplyQuote
(@wvreeven)
Quasar
Joined: 6 years ago
Posts: 2133
Topic starter  

Thanks, Vincent. That's it indeed!

And writing that I "have trouble going further to combine all these" may be a bit too strong. I just haven gotten around to trying to find out how to do this in APP yet. I am not a person that likes video tutorials (I prefer text with images) so I haven't had the patience yet to sit through them 😀


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

Didn't mean that to be a strong statement, sorry about that, I meant it could be related, but it was a guess. 🙂 Happy to help you out with whatever you come across ofcourse.


   
ReplyQuote
(@wvreeven)
Quasar
Joined: 6 years ago
Posts: 2133
Topic starter  

No worries, I am happy to explain myself better. Thanks for all the help so far 🙂


   
ReplyQuote
Share: