Author Topic: Image Container file names  (Read 2292 times)

Offline ngc1535

  • PixInsight Old Hand
  • ****
  • Posts: 326
Image Container file names
« on: 2017 December 01 12:41:57 »
Hi,

I think I understand how to use output file naming template feature of the Image Container process... but perhaps not.
I cannot seem to figure out a way to have the tool write out files with *exactly* the same name/format. This is a case where I want to clobber/overwrite my original files.
When I leave the field blank or add &filename, .xisf I always get an index concatenated as a suffix.

Thanks in advance for the answer!
-adam

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Image Container file names
« Reply #1 on: 2017 December 02 01:41:14 »
Hi Adam,

Use the following template to preserve existing file names and suffixes:

&filename;&extension;

You'll have to uncheck the Never overwrite output files option (which, admittedly, should read never overwrite _input_ files—I'll change this label in the next version) to convince IC to do what you want.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline ngc1535

  • PixInsight Old Hand
  • ****
  • Posts: 326
Re: Image Container file names
« Reply #2 on: 2017 December 02 12:35:59 »
Hi Juan,

Thank you for the response. Yes, I understood to uncheck. Could you please check the behavior on your end? When files already exist the UI says "Target file exists... " and adds the index.
E.G. "Target file already exists, writing to: C:/- m27_Date_jul08_-001rff01.xisf"
The "01" is added to an already existing file named m27_Date_jul08_-001rff.xisf.

Thanks,
adam

Offline Alejandro Tombolini

  • PTeam Member
  • PixInsight Jedi
  • *****
  • Posts: 1267
    • Próxima Sur
Re: Image Container file names
« Reply #3 on: 2017 December 02 14:04:33 »
Hi, I confirm that can reproduce the same behaviour working on Linux, it seems that the flag is not been interpreted.
I also couldn't edit instance source code which I don't know if it is normal behaviour for ImageContainer.

Saludos, Alejandro.