Astroart Forum

Great, thanks Fabio, just what I was looking for.

I have a set of over 500 fits, that I need to stack in groups of 10's.

stack1 = stack(i1, i2, ...i10)
stack2 = stack(i11, i12, ...i20)
.
.
.

Doing this manually, quickly becomes boring.

Is it possible to automate this in AA7? I san not find any suitable scripting functions.

The AA7 help says: If just one pixel has a value outside the range 0 to 65535 ADU or it is expressed as a floating point value, Astroart will save the file as a 32 bit FITS (integer or floating point). How do I switch between making AA7 save as 32-bit float and 32-bit integer? One of the sub systems...

Sounds very nice, would you mind sharing the script(s)?

I have gotten the ZWO EAF focuser with temperature sensor now, anything I can do to help?

Works fine on my setup; AA7 SP1.

Just right-clicked the Atlas, selected "Aladin web site" and got to this page:
http://aladin.u-strasbg.fr/AladinLite/? ... &fov=0.183

I have just tested with "ASICamera ASCOM Driver 1.0.3.23", ROI works fine now!

Thanks Fabio, I have just updated "ASICamera ASCOM Driver 1.0.3.22" to 1.0.3.23.
I will let you know the results once I have tested it.

Changelog for 1.0.3.23 simply says:

I tried ROI on M82 this night, but there seems to be a offset error for each scanline - or what? Am I doing something wrong? I checked all settings, but I couldn't find anything, that I might have to change. https://www.dropbox.com/s/u9e05mtmugqz3gv/m82_60s_ROI_001_L.jpg?raw=1 The fit file is here: ...

Thanks Iver, exactly what I was looking for.
That will save me a lot of disc space going ahead.

Is it possible to set a Region Of Interest?

If taking a huge number of frames, eg for exo planet transit, I have no need for the large FOV my ASI1600MM gives, but it would be nice, to be able to select a suitable ROI.

Great!

Thanks a lot for a fantastic support