×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

[~ SOLVED] remote solver | unable to solve

  • Posts: 2247
  • Thank you received: 223
I have amended the solve-field attributes with -d 31-40 and it solves much quicker. However, how can I possibly know this value on new pictures?

# solve-field -O --no-plots --no-verify --resort -d 31-40 --downsample 2 -3 314.991 -4 43.6215 -5 15 -L 51.3588 -H 94.0029 -u aw NEW_NGC7000_300sec_1x1_Ha_frame1.fit 
Reading input file 1 of 1: "NEW_NGC7000_300sec_1x1_Ha_frame1.fit"...
Header has 57 cards
Extracting sources...
Downsampling by 2...
simplexy: found 2744 sources.
Reading sort column "FLUX"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./NEW_NGC7000_300sec_1x1_Ha_frame1.axy"...
Only searching for solutions within 15 degrees of RA,Dec (314.991,43.6215)
Field 1 did not solve (index index-4211.fits, field objects 31-40).
Field 1 did not solve (index index-4210.fits, field objects 31-40).
Field 1 did not solve (index index-4209.fits, field objects 31-40).
  log-odds ratio 97.0462 (1.40161e+42), 16 match, 0 conflict, 50 distractors, 41 index.
  RA,Dec = (314.992,43.6219), pixel scale 1.20457 arcsec/pix.
  Hit/miss:   Hit/miss: ++++---++-+--------+--+-------+---+--+----------++----------+----+(best)-----------------------------+----
Field 1: solved with index index-4208.fits.
Field 1 solved: writing to file ./NEW_NGC7000_300sec_1x1_Ha_frame1.solved to indicate this.
Field: NEW_NGC7000_300sec_1x1_Ha_frame1.fit
Field center: (RA,Dec) = (314.991619, 43.621719) deg.
Field center: (RA H:M:S, Dec D:M:S) = (20:59:57.989, +43:37:18.190).
Field size: 85.3286 x 56.9721 arcminutes
Field rotation angle: up is 179.509 degrees E of N
Creating new FITS file "./NEW_NGC7000_300sec_1x1_Ha_frame1.new"...
#


from the solve-field man page:
Last edit: 5 years 8 months ago by Gonzothegreat.
5 years 8 months ago #27268

Please Log in or Create an account to join the conversation.


So I investigated the FITS file generated by SGP and it was using a non-standard FITS keyword (SCALE) that is not officially defined by the standard. WIth the scale keyword, it's possible to use the "app" parameter in astrometry. So long story short, I added support for SCALE keyword in KStars in the next release.
The following user(s) said Thank You: Bill
5 years 8 months ago #27273

Please Log in or Create an account to join the conversation.

  • Posts: 131
  • Thank you received: 11
I’m also having almost no luck plate solving. Is their anything else settings wise we should be doing to improve the chance of plate solving working?
5 years 8 months ago #27385

Please Log in or Create an account to join the conversation.

  • Posts: 131
  • Thank you received: 11
Any idea when this release will be out?
5 years 8 months ago #27386

Please Log in or Create an account to join the conversation.

What's your problem specifically? log? The above fix was for solving specific SGP generated FITS files.
5 years 8 months ago #27387

Please Log in or Create an account to join the conversation.

  • Posts: 131
  • Thank you received: 11
It's just timing out and not resolving. Attached is some screen shots of the astrometry configuration and a log file that. The log file is big though, what "text" should I be looking for?
Last edit: 5 years 8 months ago by Craig.
5 years 8 months ago #27430

Please Log in or Create an account to join the conversation.

Under Logs, enable the following: INDI + Mount + Align + CCD.

If the file is large, zip it first or post a link to it if you cannot attach it. Is your FOV indicated as 0x0 or already have your correct FOV value?
5 years 8 months ago #27436

Please Log in or Create an account to join the conversation.

  • Posts: 158
  • Thank you received: 32
I dont see the screenshots.
5 years 8 months ago #27438

Please Log in or Create an account to join the conversation.

  • Posts: 131
  • Thank you received: 11
I think I hit some size limits and the screen shots and logs didn't upload.....

I have had some success as I had the chance to test some other settings on the weekend. I have a pretty wide FOV on my current setup (8" EdgeHD with Hyperstar with a ZWO 1600MC Cool Pro) and I had a *lot* more success with plate solving when I set the binning to 2x2 (from 1x1). It completely flipped my results around to solving pretty much every time I tried it. So it must have been related to sending an image with too big a FOV. At least, that's the only setting I changed that made an immediate difference, and it improved the results considerably.

Does that sound right?

PS Also, while I've got Stellarmate, I'm setting it to resolve remotely on my laptop and not on the Stellarmate itself.
5 years 8 months ago #27493

Please Log in or Create an account to join the conversation.

  • Posts: 131
  • Thank you received: 11
Here are some of screen shots from when I having problems consistently plate solving as an FYI.

Here is a link to the screen shots and the logs in Box as I can't seem to attach screen shots in the forum

app.box.com/s/6ztprhy5vw36yeoaqracfbq0ecc1tjhz

While I'm having more success now, it'd still be good to try and get to the bottom of what I was doing wrong to help others and myself in the future.

Thanks in advance, Craig
Last edit: 5 years 8 months ago by Craig. Reason: Trying to attach screen shots. It's not taking them for some reason
5 years 8 months ago #27494

Please Log in or Create an account to join the conversation.

There isn't enough in the logs to say why it failed. I might make Ekos try to ekos the maximum binning by default for new users. I use 4x4 all the time on my QSI583
5 years 8 months ago #27504

Please Log in or Create an account to join the conversation.

  • Posts: 131
  • Thank you received: 11
Ah, thank you, that's good advice Jasem. I hope to have the scope out in the next day or two and will test 4x4 as well as 2x2 again. Sounds like 2x2 as a default setting is a good place to start at a minimum. I'll add that to my checklist.

One question, there are tons of settings in EKOS. Can I just take a snap shot of them all and once connected have them applied, including the devices themselves??? For example, in my ZWO camera, every time I connect I have to go in there and remember to set it to 16bit and not the 8bit default. I lost a whole night's data because I forgot this setting on my 1st time out. Binning settings would be something similar here. So along with the base profile you create in EKOS, be able to store *all* these settings in one place and have them re-apply when you are connecting devices and other settings in the focuser/solver/equipment etc.

The other plus, for support, is that I could simply then create this settings file and it'd make troubleshooting issues considerably easier too I am thinking.
5 years 8 months ago #27538

Please Log in or Create an account to join the conversation.

Time to create page: 1.360 seconds