|
REPORT COPYRIGHT VIOLATION IN REPLY
|
|
Message Subject
|
"Skyview" Debunked (page 4)! They suggest that TBar and I should die! I show 'em how it's done and take a picture of a REAL KBO!
|
|
Poster Handle
|
Astromut |
|
Post Content
|
Just FYI, I can set the CPU timeout limit to anything I want, right now it's set to 1 hour 40 minutes, but I can extend that indefinitely later if needed. I intend to solve for every detected source in the image (all 705 of them). The web version usually times out before it can go through every single source. I'm also using index files that span the full range of possible fields of view (image scale) all the way from 2 arcminutes wide to 2000 arcminutes wide (33 degrees). Each index is designed to be between 10-100% the size of the field of view it is solving, so for instance the widest index of 33 degrees can solve images up to 330 degrees wide, the index for 2 arcminute wide images can solve images up to 20 arcminutes wide. I also have an index for 11 arcminutes, which goes from 11 up to 110 arcminutes, and so on. There's considerable overlap as well as you can see, so I've got it all covered. If this doesn't solve it, then it's either not a real image, or it's badly distorted and the relative positions of the stars are no longer true to real life.
Quoting: Astromut Meh, I went ahead and gave it the full monty; I changed the setting to allow it to solve for up to something ridiculous like 100 hours. No sense in waiting an hour and a half just to find out I have to start over and give it longer to try every detected source in the image. It shouldn't take anywhere near 100 hours to do that, but if I fall asleep I don't want it to have stopped an hour and a half into it long before I woke up. It was still solving when I woke up, so I went back and adjusted the levels on the image histogram to clip out all the noise from the image, leaving just the stars. That reduced the detected sources to something like 150 or so, which it can get through in a few hours time. I just went and checked on it and it's halfway done already. I posted this last night and it's being ignored, "OK, the video DARK STAR COMETH has two images near the end at times 3:32 & 3:44. Why is it that when those Images are submitted to Astrometry they don't solve? Real Images solve in about a second or less. Your two images time out unsolved. Do you have any Images that will stand up to Astrometry? It would be nice if you did. Anyone can try it, extract the Images and submit them to nova.astrometry.net" [ link to www.youtube.com] I also ran another image from your video after the scope was adjusted. Their coordinates are pretty close to the center of this image [ link to nova.astrometry.net] The KMZ is here [ link to nova.astrometry.net] Yeah, that's the thing, real images generally solve within the first few stars that it looks at; the pattern would be consistent with some location in the real sky. Even if there are extra dots there from some "planet X and its moons" by the time it's searched 20 or 30 or heck, even 50 stars there should be no question where it is in the sky. Instead it was still searching after including 70-80 stars. It had about another 75 to go. When it runs out then I can absolutely say it's not a real image of stars or was photoshopped/altered/distorted so that the 'stars' don't match the positions of any real stars anywhere in the sky. It should be done when I get home this evening.
|
|
|
Please verify you're human:
|
|
|
Reason for copyright violation:
|
