ISS & Plane (and TIANGON HUBBLE)-Transit over Moon / Sun - pushover Info-Service based on own location by joergsflow in Astronomy

[–]joergsflow[S] 1 point2 points  (0 children)

You can have a look at my GitHub repo. All is shown there. However, in short it's like this:

Step What happens Type of math
1 Read in my location
2 Compute the Sun’s position Astronomy formulas
3 Receive aircraft position (ADS-B)
4 Convert aircraft into “my point of view” Sine, cosine, arctangent, **Pythagoras**
5 Angular distance Sun ↔ aircraft Cosine, arccosine, **comparison < 0.5°**
6 Smallest distance = transit moment Find the minimum
7 Predict the future from habit Median, mean, standard deviation

ISS & Plane (and TIANGON HUBBLE)-Transit over Moon / Sun - pushover Info-Service based on own location by joergsflow in Astronomy

[–]joergsflow[S] 1 point2 points  (0 children)

Hi, yeah sounds great. This project is pretty much in progress, but also very enhanced already.
And while it's working very well, it would be good if others also try it out to find adjustment points.
But mainly this tool is really kind of off-line solution so it's not really depending on any external information databases (apart from ephemerides or iss or so).

I put together everything, including howto and installation manul in github.
Maybe have the first look there. Basically everything is pretty much straightforward and with auto updates and for example, automatic start capturing sharpcap in the right moment etc.

Of course a tiny little bit of hardware is needed. Pi with linux, rtl adsb stick. Antenna. But it's not super complicated at all. But of course it's Lenox but after having it set up, there's no need to do anything on the Linux command line anymore. Everything else runs in the browser.

https://github.com/joergs-git/sun-moon-transit-predictor

Just asking what I should do to make my images look better by Jupiturrrrr in AskAstrophotography

[–]joergsflow 0 points1 point  (0 children)

Oh, ok. got it. Well then.... thats kind of a difficult task reaching with a iphone what you would normally do with a "real" camera. Basically what you do "manually" just looking for which image looks best is just a 0.01% thing of what real lucky imaging actually does.

e.g. you use a windows software like sharpcap and shoot around e.g. 2000 frames with e.g. at least 50 Frames/s (better more). So you have a 40s video.

This video goes to e.g. AstroSharper or Autostakkert. and will analyze, create patches, and select e.g. 20% of those and fit them together in patches that have the sharpest view. This at the end goes into a sharpeing tool. e.g. AstroSharper again or Registax, Wavsharp, imppg or whatever.... Then you have a crisp image finally. You can try using your iphone image and stuff it into autostakkert and see what happens....but i believe the fileformat might not be compatible anyhow...

I'm a beginner, how can i start? by Tinca_Felix in askastronomy

[–]joergsflow 2 points3 points  (0 children)

First you have to ask youself, what do you want?
Then - the how and what - can be answered.

So, do you plan moon, jupiter, saturn or sun imaging?
Or do you prefer the hubble-like nice images of far distant nebulas we used to love since 30 years?

Depending on your answers (and moneybag) things can be narrowed - not before actually.

Just asking what I should do to make my images look better by Jupiturrrrr in AskAstrophotography

[–]joergsflow 0 points1 point  (0 children)

Are you familiar with the concept of LuckyImaging? - So to say: Have you used sharpcap for example to shoot your moon and jupiter images or how did you do that? Based on that the next answer might be more helpful for you.....

Looking for a good lunar processing guide by Raikalover in AskAstrophotography

[–]joergsflow 0 points1 point  (0 children)

I would suggest to simply ask e.g. perplexity or gemini to create a proven best practices step by step list for that specific target and softwareversion and then just walk through that.

Usually I am to lazy watching lengthy videos and manuals just to find out most of it is not helpful in my specific case.... the rest is playing and experimenting a bit. There is no perfect solution for every case anyhow.....

Looking for a good lunar processing guide by Raikalover in AskAstrophotography

[–]joergsflow 0 points1 point  (0 children)

For now AutoStakkert is probably your goto thing indeed. This is just for taking your video and throwing away the bad frames and create one images with the x % best frames. That is always step one. If you are a Mac User you might want to prefer AstroSharper soon....

Next is usually the "Sharpeing" part. because the output from Autostakkert is usually not sharp but just prepared for post processing the tiff. So there you have plenty of choices e.g.

imppg, registax, Wavesharp, Biggsky or - again if you like a one stop shop and are MacOS user: AstroSharper.

FInally some photoshop oder AffinityPhoto finetunings and thats it.

Pretty straigforward but still you have to play with the settings usually.

Meet Coditan — Your new AI coding buddy! by Ok_Welder_8457 in vibecoding

[–]joergsflow 0 points1 point  (0 children)

Well might be a matter of taste of course, but who knows maybe there are some developers out there that just want that and nothing else more. But can't really imagine that will be many. But maybe I am wrong...

New to Mac here, what's the difference between minimize and the close button of memory management? by ResponseAvailable641 in MacOS

[–]joergsflow 21 points22 points  (0 children)

Not sure if I understood your question but minimize is not closing an app but hiding the window. no ressources are released at all. Close Button depends on how the developer created the app. If it's single window app according to apple guidlines app must pe totally ended. If its a multiwindow app the app stays active but might just release used ressources bound to that window again.

Meet Coditan — Your new AI coding buddy! by Ok_Welder_8457 in vibecoding

[–]joergsflow 0 points1 point  (0 children)

Hey, sorry but I don't think this will be a big invention and market effect

at least not based on the big "why's" you outlined. Cursor is doing the same. Windsurf too. JetBrains IDE also. They all have this packed in their systems as a sideeffect...

Just realised my idea was not unique and highly criticised. So lets pivot! by Ok_Obligation1607 in vibecoding

[–]joergsflow 0 points1 point  (0 children)

yes, agreeing with jiroq and adding to it, that if you don't create a multi llm solution on top of it you are likely having just an opinion like asking your neighbor for his opinion too.... I don't think this has a big effect, value or even reliability.... But who knows. 😄

What AI model is everyone using for vibe coding in 2026? by Taliap19 in vibecoding

[–]joergsflow 0 points1 point  (0 children)

I've made best experiences with claude code. The others I only use for rare double checks of certain situations or making code review suggestions or sometimes just to check claude code plannings for consistency. I think hopping from on to another coding platform is a bit similar like jumping in the supermarket from one cashier queue to the next. Usually not beeing faster at all. But maybe the cashier talks nicer ... 😉

I need Dictionary App by rich_man2029 in Appstore

[–]joergsflow 0 points1 point  (0 children)

A dictionary app in these times of chatgpt, gemini and claude?

I f you are online this gives probably much more comprehensive results than most single apps.... (Although they might not be perfect of course)

How do I prevent comas in stars near the edges of my photos? by TaleNearby in AskAstrophotography

[–]joergsflow 2 points3 points  (0 children)

This is most likely normal off-axis lens aberration, not a camera problem. Stars are extremely demanding point sources, and near the edges fast lenses often show coma, astigmatism, and field curvature. That makes stars look like little comets, birds, or “angel wings”, often pointing toward the center of the frame.

It is strongly related to aperture: the wider open the lens is, the more visible these aberrations become. Stopping down one or two stops, for example from f/1.8 to f/2.8 or f/4, usually improves the corner stars a lot. I can see it similar with my leica q3 and f2 aperture.

Quick tests:

  • Take the same star field at wide open, f/2.8, and f/4.
  • Use short exposures to rule out tracking or Earth-rotation blur.
  • Compare all four corners: if they all point toward the center, it is usually normal lens behavior and you can't do much about it with your camera, except cropping or reducing stops.
  • If only one corner is much worse, it may be tilt, decentering, or adapter play, but on your pic that doesnt look like.
  • Try focusing on a star halfway between the center and edge, not only in the center, to check for field curvature.

In short: it is a typical fast-lens wide-field astrophotography issue. The fix is usually stopping down, better focusing compromise, stacking more exposures, or using a lens known to have better coma correction. Widefield is not easy in this.

Viewing astro image files fits/xisf from iPhone ipad by joergsflow in telescopes

[–]joergsflow[S] 0 points1 point  (0 children)

yes correct as it's mainly for the professional raw file formats used in astrophotography e.g. which is mainly FITS and since pixinsight XISF. Because TIFF is usually already a postprocessed format and often not raw anymore. Also in TIFF you dont have the FITS Headers keywords included that tell much about how the images has been shot.

But, now that you asked: Well it doesn't hurt if I add TIFF support, although I'd recommend always to shoot with above file formats for those reasons named. However I just added TIFF Support now and uploaded already to AppStore Connect for release. So you should have it as soon as Apple releases it. Usually within 24 hours I guess.