Problem processing ...
 
Share:
Notifications
Clear all

19 June 2021: Our upload server https://upload.astropixelprocessor.com/ has been migrated successfully to our new office with higher upload and download speeds (nearly 10MByte/sec up/down ) ! We now have 1 general upload user called: upload with password: upload. The users upload1 - upload5 have been disabled.

31 May 2021: APP 1.083-beta2 has been released ! APP 1.083 stable will follow soon afterwards. It includes a completely new Star Reducer Tool, New File Saver Module, Improved Comet registration and much more, check the release notes here!

DOWNLOADS are available HERE!

 

Problem processing DS16C images  

  RSS

(@glatiak)
Molecular Cloud Customer
Joined: 2 years ago
Posts: 5
December 30, 2019 20:19  

I have a number of images captured with a Mallincam DS16c (same Panasonic sensor as ZWO1600mc AFAK) that I have previously successfully integrated with PI but have run into issues doing the same thing with APP. If I process it with the master darks and flats I used in PI, I get an integrated image but APP does not see it as OSC. The images all have the fits tag COLORTYP='BGGR' but not BAYERPAT. If I toggle the force BAYER, processing fails as it claims my masters are one channel and the images are three -- when it is trying to normalize my images.  Why are these calibration files even an issue at this point? I suppose I could rebuild the darks and flats but the camera is in a box as its been replaced with cooled cameras. Also, the capture applications were rather idiosyncratic when writing the fits headers -- some are tagged 'Light Frame' but a bunch are 'Dark Frame' even though they are lights. One of the reasons I have moved my captures to SGP.

Any thoughts as to what I can do to be able to process these older images?

Thanks,

Greg Latiak


ReplyQuote
Topic Tags
(@vincent-mod)
Universe Admin
Joined: 4 years ago
Posts: 3694
January 7, 2020 11:46  

Hi Greg, sorry for the delay.

So first off, you need to recreate calibration masters with APP first. APP uses a different calibration engine and it most likely won't calibrate well if created by another application. You're mentioning a problem with the fits headers which might cause issues as well. So, best thing would be to get some data that you're sure about is correct, with new masters for APP.


ReplyQuote
(@glatiak)
Molecular Cloud Customer
Joined: 2 years ago
Posts: 5
January 7, 2020 16:19  

Thanks.

I will change my process flow to retain the raw files rather than build a library of masters as I am likely to continue using both APP and PI. Did not realize the differences in correction engines -- might be helpful as a user note in the software. As for the FIT headers -- that seems to be written by the data collection engine -- Mallincam Sky is very different from Sharpcap, Sequence Generator seems to have the most complete and least flaky headers. The DS16c is a nice camera with a big sensor but being uncooled its pretty noisy (same sensor as the ZWO1600mc).

greg


ReplyQuote
Share: