@olav wrote:
Hi there, new here.
Judging from CN-threads, a lot of users has already come over from MaxImDL to SGP, and seems awfully happy. I also understand that most users of SGP have chosen Pixinsight for processing.
Want to try SGP now.
But not Pixinsight, at least not yet. I'll stick to the easy calibration and stacking for a while. I don't have time to swap everything at once.
Has anyone chosen this track? Good/bad experiences?And it would be a good exercise to check that any new capture software I invest my time in, will not streamline my imaging files for just one processing software. Never liked that MaxIm had imaging and processing in the same program, but should not be a problem with the aging/strange UI for doing just processing.
I became a bit worried when I saw how poorly MaxIm imported RAW files that I had from a mobile session.
The first thing to check was matching write/read of essential FITS header keyword/value pairs:
http://mainsequencesoftware.com/Content/SGPHelp/SequenceGeneratorPro.html?DataStoredintheFITSHeader.html
https://diffractionlimited.com/help/maximdl/FITS_File_Header_Definitions.htmI assume both parties honor standard/common dictionaries; http://heasarc.gsfc.nasa.gov/docs/fcg/standard_dict.html and http://heasarc.gsfc.nasa.gov/docs/fcg/common_dict.html.
But already from my first glance at the use of "extended" keywords, this seems to fail completely:
MaxIm uses CCD-TEMP and SET-TEMP. While SGP writes TEMPERAT, for the same as CCD-TEMP.Anyone with an incredibly smooth (script based etc) FITS conversion utility?
Is it correct that SGP does not write SET-TEMP? (some keyword I didn't guess?)I really would like to take the SGP-path, but I'm drawn towards a principle of having certain critical interfaces clearly defined and working at more than a single point of connection with the outside world.
Please assure me
Thanks.
Posts: 1
Participants: 1