What are img_tmp_nn files when using ASIDeepStack

johnpd

I did some stacking of a group of images of M16 using ASIDeepStack and ended up with a totally black result. There were dozens of img_tmp_nn files in the folder (where "nn" was a number sequence) which were the size of the .TIFF and FITS files that I would normally end up with. I ran it again and everything worked fine. I ran a stack on another image set and ended up with one img_tmp_11 file. What is causing this?

JohnD

ASIStudio@ZWO

johnpd
Hi John,
Can you share the fit file with us via google drive or dropbox?
Please send a ticket here. https://support.astronomy-imaging-camera.com/
And we can try to reproduce it.

johnpd

I attempted to submit a ticket under the software category and I receive a "Submit failed" message. No reason given for the failure". I included a link to the .FITS files on my Google Drive account.

JohnD

ASIStudio@ZWO

johnpd Did the ticket submitted now? Please retry, and we will check the system.
Can you help us by providing a screenshot of the message?

franco

I saw the same file on the ASIAir after doing a planetary stack. It wasn't in any of the directories visible in the app.

johnpd

Usually ASIDeepStack will create just two files in the same folder as the original .FITS files, the stacked .FITS file and a .TIFF version of that. I have not tried video stacking on the ASIAIR yet. I would think those files would end up somewhere in the Video folder. Why they are being generated and what is their purpose is unknown. Maybe they are temporary files created by the stacking process which would then be automatically deleted when stacking is completed? I would hope that ZWO will get to the bottom of this.

JohnD

ASIStudio@ZWO

johnpd Conveyed to the team and will get back to you once we get the result.
You can also share your google drive link here.

franco

Sorry, what I saw on the ASIAir was Image/batch_stack_tmp which is a directory. I was deleting stuff so didn't take much notice before I got rid of it.

Could have sworn this post was about AVIStack..

I just tested a DeepStack in ASI studio and found that if I cancelled the stack I was left with the tmp files.

-rw-rw-r-- 1 franco franco 70166208 Sep 11 21:18 img_tmp_0
-rw-rw-r-- 1 franco franco 70166208 Sep 11 21:18 img_tmp_1
-rw-rw-r-- 1 franco franco 70166208 Sep 11 21:18 img_tmp_2
-rw-rw-r-- 1 franco franco 70166208 Sep 11 21:18 img_tmp_3
-rw-rw-r-- 1 franco franco 70166208 Sep 11 21:18 img_tmp_4
-rw-rw-r-- 1 franco franco 70166208 Sep 11 21:18 img_tmp_5

johnpd

franco

Yes it was for ASIDeepStack. I can't recall cancelling the stack, but is seems ASIDeepStack v1.6.3 is having an issue cleaning up after it completes or cancels a stack.

JohnD

johnpd

@ASIStudio@ZWO#58554

OK I tried a different browser and was able to submit a ticket.
"Your request (2094) has been received and is being reviewed by our support staff."

JohnD

franco

@johnpd I was running the latest 1.7 release, which for some reason doesn't show up when you check for updates in the 1.6.3 version.

johnpd

franco

My understanding that v1.7 is still a BETA. I am having enough issues with 1.6.3. If you are getting the same problem in 1.7 then that issue has carried over into the new release. I was contacted by ZWO who said they are looking into it.
JohnD

ASIStudio@ZWO

johnpd
Can you make a video to show the problem? and send the feedback via ASI Feedback if you are using windows.
copy the crash detail of you are using the mac.
Thanks!

johnpd

@ASIStudio@ZWO#58617

Not sure what you are asking for. First off I am not sure it is reproducible. You want me to take a video of my computer screen showing the stacking process running?

JohnD

ASIStudio@ZWO

johnpd
Yes, our devs want to know how the black image was produced.
Btw, I get the google drive link from our colleague, it cannot be opened, can you help check it?

johnpd

@ASIStudio@ZWO#58643

I ran another stack Wednesday evening on an object and had no problem so it seems it might have been a one-off. I don't know what might have triggered it.
Regarding the Google Drive file, you get a couple of messages. One says it cannot be previewed (that is because it is a ZIP file). The next says it cannot be virus checked (again it is a ZIP file). I selected to download it anyway and I was able to open one of the .FITS files. The "tmp" file cannot be opened by any program as it does not have an extension so there is no way to associate it with any program. As I recall it had about the same size as a stacked file.

JohnD

ASIStudio@ZWO

johnpd
1 img_tmp_n files is the temporary files during stacking, and they will be deleted automatically, you do not need to worry about them.
2 still cannot open this link...
https://drive.google.com/file/d/1MMVpFiQnEID9yN2qPwSUYgRgY7q1LFVu/view?usp=sharing
However, if the black result still exsit, you can make a video to show the problem, and send the feedback via ASI Feedback if you are using windows, or copy the crash detail info if you are using the Mac.

johnpd

@ASIStudio@ZWO#58713

OK will do. At this point it is a one-off. Something went wrong and those "tmp" files were left. If I can duplicate it at some point, I will try to gather more info. The link should be:

https://drive.google.com/file/d/1MMVpFiQnElD9yN2qPwSUYgRgY7q1LFVu/view?usp=sharing

When I defined that, the link should be "...El(lower case "L")D9..." not "...EI(upper case "I")D9...".

JohnD

ASIStudio@ZWO

johnpd Stacked your file and did not reproduce the black image problem.

Please feel free to contact us when you meet it again.