Menu

ASTAP Error: Not able to decompress .fz file

JMM
2024-03-01
2024-03-04
  • JMM

    JMM - 2024-03-01

    Hello,
    I have a situation where on occasion, certain .fz files created with NINA for some reason will not open in ASTAP. 98% of the time there is no problem, but for some unknown reason, ASTAP cannot decompress or open some files and does not log any error as to what the problem is. The files are good as they can be opened sucessfully in Astro Pixel Processor and appear to have no issues.

    Any ideas? I have included a sample file that will not decompress.

    Thanks

     
  • han.k

    han.k - 2024-03-01

    There is something in the file name which the unpack program doesn't like. After renaming it to a shorter name works.
    I will investigate.

    Han

     
  • JMM

    JMM - 2024-03-01

    I also have this file that will not work either. The filename is different but perhaps it will help with the issue. Maybe it does not like the ()?

     
  • han.k

    han.k - 2024-03-02

    The character " (" in the file name is the problem. There are two solutions. 1) rename the file prior to conversion or I update the funpack code. I will see what the latest fpack/unpack version is doing:

    https://heasarc.gsfc.nasa.gov/fitsio/fpack/

     
  • JMM

    JMM - 2024-03-02

    I see. A 3rd option would for your code to replace the offending characters with perhaps an underscore or something prior to calling funpack as part of the decompression routine. Just a thought.

    Thanks for the information, please let me know.

     
  • han.k

    han.k - 2024-03-02

    I have implemented a rename. Only the "(" is replaced by an underscore. Here is the new ASTAP installer:

    http://www.hnsky.org/astap_setup.exe

    That should work for you.

    Han

     
  • JMM

    JMM - 2024-03-02

    I tried your new version, but it throws an Access Violation (see attached).

     
  • han.k

    han.k - 2024-03-02

    Looks like I uploaded not the very last compile. Upload the compled one again. Try this one again:

    http://www.hnsky.org/astap_setup.exe

     
  • JMM

    JMM - 2024-03-02

    Sorry, no go, same error. It looks like the link is loading the same file as before.
    Any Ideas?

    Thanks

     
  • han.k

    han.k - 2024-03-03

    Must something very simple. I tested here the file below on a different computer:

    LIGHT_IC 410 TadPoles)_1x1_94_65_L-eXtreme_60.00s_0277 (62).fits

    This file is processed. At which file does it fail? Can you share that file?

    Last night I uploaded a second new ASTAP version. Should not make a difference but it is version 2024-01-02 instead of 2024-03-1. Can you check the version you have. If it is not 2024-03-02 download a new version.

    This problem should be fixed.

    Cheers, Han

     
  • JMM

    JMM - 2024-03-03

    Hi Han,
    The link you provided above kept downloading 2024-03-1, so yes I was still running 2024-03-1.

    I tried the normal download method (and yes now I have 2024-03-02).

    This version works well.

    Thanks for your help!

     
  • han.k

    han.k - 2024-03-03

    Good it is fixed.

    Maybe the 2024-03-01 file came from browser cache.

    If you find any problem, please report.

    Cheers, Han

     
  • JMM

    JMM - 2024-03-03

    Just a further note for your interest;
    If there is ANY folder in the path that contains a '(', that will also cause funpack to throw an error. Something to bear in mind, perhaps add a sanity check to the input/output path/throw a message to the user or add a comment to your documentation.

    Thanks

     
  • han.k

    han.k - 2024-03-04

    Thnaks for the info.

    I have modified the code to change only the "(" in the filename.. not the path That did not work. Probably it is better to fix the funpack program itself. I reported it as a bug. At the moment it is too much hassle to look into the funpack code myself.

    For the moment I will make a remark in the manual as you suggested.

    Han.

     
  • han.k

    han.k - 2024-03-04

    I have added an error message in the code for a path with "(". That was the easiest.

     
  • JMM

    JMM - 2024-03-04

    That should help others whom may hit this problem in the future.

    Thanks

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.