A PixInsight user, jt_3232 (Jaxon) began a topic on the PixInsight forum this week reporting that he could not open images in AIJ that'd been batch calibrated in PixInsight.
You can view the topic here:
After investigation the problem appears to be caused by two ZWO ASIAIR generated FITS keywords, IMAGEW and IMAGEH, which seem to be duplicates of NAXIS1 and NAXIS2 keys.
The issue begins with the IMAGEW and IMAGEH keys that are written as integers in the FITS header by the ASIAIR app without a trailing period ".", i.e, IMAGEW 1560 - IMAGEH 1044
After calibration, PixInsight saves theses FITS files using the standard method of appending a period "." following the integer in the IMAGEW and IMAGEH fields, i.e, IMAGEW 1560. - IMAGEH 1044.
If the image is now opened in AIJ with the trailing period in the IMAGEW, IMAGEH integer fields then it is not displayed, even though the image is actually open and information can be read from the file.
This appears to be a bug in AIJ since most other FITS image readers and FITS image post processing applications are able to display the image normally, with or without the trailing period in those IMAGEW and IMAGEH FITS header fields.
You can find two sample images in this GoogleDrive folder that demonstrate the problem:
One image is direct from the ASIAIR app that contains no trailing period "." in the integer fields for IMAGEW and IMAGEH while the second image has those trailing periods.
You can open and display the former in AIJ but the latter image opens in AIJ but does not display.
While I'm not an ASIAIR user and not personally affected by this I am posting this as a courtesy and possible bug report for AIJ developers.