u/thomac

325 post karma · 103 comment karma · joined Dec 2014

  1. 0points

    Package vs. files (self.golang)

    4 comments

  2. 36points

    Which CPU has fastest DIV/IDIV instruction? (self.hardware) [Discussion]

    53 comments

  3. 2points

    Slice of slices and cap (self.golang)

    4 comments

  4. 32points

    Integer multiplication in time O(n log n) [PDF] (hal.archives-ouvertes.fr)

    5 comments · source

  5. 114points

    Integer multiplication in time O(n log n) [PDF] (hal.archives-ouvertes.fr)

    39 comments · source

  6. 0points

    Number of issues at GitHub (self.golang)

    1 comments

  7. 3points

    How to load values to slice? (self.golang)

    14 comments

  8. 2points

    Inline functions (self.golang)

    3 comments

  9. 2points

    Stack of various types manipulation (self.golang)

    11 comments

  10. 1points

    Printing big.Int (self.golang)

    4 comments

  11. 4points

    Big arithmetic (self.golang)

    10 comments

  12. 7points

    Union alternative (self.golang)

    9 comments

thomac

Ok, but does "the same package" also mean "the same folder"?

thomac

Astrophotography program, that would be cool! Unfortunately no, I'm asking because of finite field arithmetic where modulo operation is very common and one has to rely on tricks like Montgomery reduction to get somewhat acceptable speed.

thomac

Why "half-broken"?

thomac

Thanks!

thomac

From the docs: "release cycle is aligned to start on February 1" and GitHub 1.12 milestone was recently shifted from February to March.

thomac

Please forgive, I new here, but GitHub currently lists 208 issues tagged with 1.12, why the RC1 then?

Also I thought Go has time-based releases and 1.12 was supposed to come out by February 1st, does anyone know the reasoning why it was pushed back to March?

thomac

Could you please clarify, how similar is "ISO 1600" and "unity gain (gain 90, offset 65)"? In other words, are the two exposures comparable?

thomac

Thanks!

thomac

I read about the allocation also, but if `x.Add(x, y)` re-uses the memory, why write `x = x.Add(x, y)` instead?

thomac

If that is the case, what is the point of using the former over the later?

thomac

Cool! Just curious, why not more that 64bits? If there was support for uint128_t, would it be possible to make it work as quadruple precision float?

thomac

Thank you all for the replies!

Please, two more questions:

  • Autoostakkert and Registax seem to be Windows only. Is there anything for Mac or Linux? What about an open source application?

  • How does it work, anyway? Is it just matter of registering and stacking of images or, in addition, do the pictures get somehow locally deformed? I mean are the images projectively transformed and blended or is there more to it? And what exactly is "more"?

thomac

Combat seeing

So I took many not-so-great pictures of the moon and they are all distorted because of the atmospheric seeing. Is there a way to combine all these low quality pictures and combine them to single better quality picture? Is there any software for such an operation? And in general, what common ways there are to combat the seeing?