StarTools

admin wrote: ↑Mon Jul 19, 2021 1:28 am Hi,

The 1.8 alpha has already been ported and confirmed to work natively on M1/ARM via a universal binary without problems.

I have, however, not heard of any terrible slowdowns via Rosetta, particularly when it comes to simple tasks like opening files, so something else may be at play.

It is possible the files you are importing are stored in a format that is "not ideal" (for example floating point format - integer format is preferred), contain out-of-bounds pixels, and/or do not report the used dynamic range (MIN/MAX) in their headers.

In such cases, importing may take longer depending on, for example, the amount of aberrant pixels (if any). In the latter case StarTools will substitute every singularity's pixel with "plausible" values, so that subsequent processing will not be disturbed by their presence (this, for example, avoids the propagation of ringing artefacts, or prevents algorithms that rely on local neighborhood pixels from backing-off).

Your stacker of choice will often allow you to avoid such things. Is your stacker listed here?

I can also point you the closed alpha, but - it being an alpha - I probably would not recommend learning the ropes with that.

Clear skies!

Hello, I am currently evaluating startools. Are there plans to update it to run natively on apple m1? I managed to install it on mac and go through the hoops to get it to work, but performance running through rosetta 2 emulation seems really bad. Like just pressing a button to open a file there is a huge lag and it seemed to just hang up at one point. I use other astro software through emulation and it is not as fast as it potentially could be but not unusable like this. Is anyone successfully using startools on apple m1?

I do like the idea of the software and having another alternative, and i have an intel mac at home as well (currently on the road), but I am curious if there is commitment to supporting mac and the new macs in the future.