PixInsight won't save files

[ttrinko]

On my Mac running OS X 10.12.5 and the latest version of pixinsight the star registration tool won't save the registered files to my hard drive.

I have to manually save each registered view which is a bit of a pain.

Any insight would be appreciated.

Thanks!

[pfile]

most likely you are dragging the triangle or pressing the square? you need to load all the target files into the target box, choose an output directory (if you want it to be different than the source directory of the input files) and hit the _round_ button. the target files to be registered do not need to be open on the desktop.

rob

[chris.bailey]

Another gotcha is having a space at the end of the directory name. OSX is quite happy to save to such directories, PI is not.

[ttrinko]

Directory name doesn't end with a space.

All files that are to be aligned are in the target images list with a green check mark

A registered version of all files show us views

Used the round button.

Tried to save to main disk and external disk.

In no case did any of the registered files actually get saved.

Any more ideas?

[pfile]

look at the console log - the only thing that i can think of is that every single image failed to register.

rob

[ttrinko]

look at the console log - the only thing that i can think of is that every single image failed to register.

rob

The images all register I just have to manually save them.  I turned on stop for errors and the process never stopped.  Is it a problem that the path in the dialog doesn't end with a / ?

[pfile]

if you have used "Add Views" to add a bunch of images on your desktop, then SA puts the registered files on the desktop.

if you use "Add Files" to add files from disk, then SA writes the images to disk.

rob

[ttrinko]

if you have used "Add Views" to add a bunch of images on your desktop, then SA puts the registered files on the desktop.

if you use "Add Files" to add files from disk, then SA writes the images to disk.

rob

I open files to the desktop.  I then run the staralignment tool and it doesn't save the registered versions of the files.

[pfile]

hi, i am trying to say that if you open files on the desktop and add those views to StarAlignment, SA will not save the registered files to disk. it will put the registered files on the desktop.

to get SA to save the registered files to disk, the unregistered files have to be on the disk to start with.

that's just how it works.

there's really no need to open all the unregistered files to the desktop... just leave them on the disk, and open them using "add files" in staralignment and the registered versions will be written out to disk.

rob

[ttrinko]

hi, i am trying to say that if you open files on the desktop and add those views to StarAlignment, SA will not save the registered files to disk. it will put the registered files on the desktop.

to get SA to save the registered files to disk, the unregistered files have to be on the disk to start with.

that's just how it works.

there's really no need to open all the unregistered files to the desktop... just leave them on the disk, and open them using "add files" in staralignment and the registered versions will be written out to disk.

rob

Not sure what you're saying. Sorry.  What do you mean by the desktop?  The Pixinsight window or the computer OS Desktop?

I use the open file dialog in PixInSight to open a bunch of files.

I then add the views to the star alignment tool and it registers them and creates new views.

Are you saying that if i add the files rather than the views in the star alignment tool then PixInSight will save the files to disk? If so that's poor design

I'll go try it.

Thanks for your help!

[pfile]

Are you saying that if i add the files rather than the views in the star alignment tool then PixInSight will save the files to disk? If so that's poor design

that is what i am saying.

it is not poor design, it is completely symmetrical design.

load views -> get views as output
load files -> get files as output

no one uses it like you're trying to use it, which is why i was so confused by your question. since we need to register 10s or maybe 100s of files at a time, it's far more advantageous to write the calibrated files to disk, then open them directly from the disk to register them. opening all the calibrated files to the PI workspace would be a colossal waste of time (and one hell of a mess with 10-100 files open in the workspace.)

if you want to figure out which of your calibrated frames are good enough to register, use SubframeSelector and/or Blink to winnow them down.

rob

[ttrinko]

Are you saying that if i add the files rather than the views in the star alignment tool then PixInSight will save the files to disk? If so that's poor design

that is what i am saying.

it is not poor design, it is completely symmetrical design.

load views -> get views as output
load files -> get files as output

no one uses it like you're trying to use it, which is why i was so confused by your question. since we need to register 10s or maybe 100s of files at a time, it's far more advantageous to write the calibrated files to disk, then open them directly from the disk to register them. opening all the calibrated files to the PI workspace would be a colossal waste of time (and one hell of a mess with 10-100 files open in the workspace.)

if you want to figure out which of your calibrated frames are good enough to register, use SubframeSelector and/or Blink to winnow them down.

rob

It's poor design because the options for saving the files to disk appear even when all the inputs were views.

It's always horrible UI design to give users options that don't work at all.

thanks for the help.

[Juan Conejero]

It's poor design because the options for saving the files to disk appear even when all the inputs were views.

Because you can mix views and disk files in the same process instance. That's why the Add Files and Add Views buttons are always enabled in the Target Images section, when the selected working mode allows disk files. These degrees of flexibility and complexity are common design paradigms in PixInsight. In general, we don't have many toy tools of the "point-and-shoot" kind, especially for sophisticate batch tasks such as StarAlignment.

[ngc1535]

Because you can mix views and disk files in the same process instance. That's why the Add Files and Add Views buttons are always enabled in the Target Images section, when the selected working mode allows disk files. These degrees of flexibility and complexity are common design paradigms in PixInsight. In general, we don't have many toy tools of the "point-and-shoot" kind, especially for sophisticate batch tasks such as StarAlignment.

Hi Juan,

I understand your answer concerning the mixed files- but you tacitly state that views are not written to output directories- that is multiple views (their data) cannot be saved to the disk as a group.  You can save an individual view (its data only) to the disk by using Save As. But this isn't permitted with multiple views in a process. I didn't find documentation or a thread that mentioned the reason for this methodology.

For example, if views are loaded in the Image Container and No Operation is performed with an Output directory specified- the view is of course processed but not written to disk. There must be some logic to the prohibition (or perhaps programming issue) for this behavior. If it became possible, the user would have to accept that only the data from the view would be written disk and all other information would be broken/lost. This is already an understood norm.

My projects contain quite a few files. If I want to create and output a subset of views written to disk (having been processed in a way different than I intend to keep in my saved project)- it would be useful to have this option.

Let us know your "insight" on this!

-adam