Welcome, Guest
Username: Password: Remember me
20 Aug 2017
INDI development team is happy to announce the release of INDI Library v1.5.0. This new exciting release builds on the maturity of INDI Library and comes with many new supported devices and fixes for existing drivers.
Read More...

TOPIC: Remote astrometry solver

Remote astrometry solver 1 year 1 month ago #10976

1. I completely agree, that should be done higher, by the scheduler as you mention. I'll review my config, I missed the step where it ca be configured.
2. Suddenly I have a doubt: are the contents of the settings editbox actually used when the solver set is to online? I thought they were not, though the box isn't greyed out.
-Eric

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

Remote astrometry solver 1 year 1 month ago #10978

Yes some options are parsed and sent to online solver (-L -H -3 -4 -5 --downsample), will check parity as well soon.

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?

Remote astrometry solver 1 year 4 weeks ago #11003

Regarding parity. Would this value change if you flip to the other side of meridian?

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?

Remote astrometry solver 1 year 4 weeks ago #11004

From what I could understand from the astrometry code, the parity relates to flipping the sources in the capture, not rotating them. In my tests, I used a negative parity with a meridian orientation, and the solver successfully resolved the capture on both sides of the meridian while adjusting.
-Eric

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

Remote astrometry solver 1 year 4 weeks ago #11005

ok I made it so that it reuses parity after capture unless explicitly set otherwise by the user in the astrometry options. The parity resets also to "both" whenever the solver fails.
The following user(s) said Thank You: TallFurryMan

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?

Remote astrometry solver 11 months 3 weeks ago #12766

At long last, tested this evening with an Orion 50mm guider, works quite great on my side.

However, I'm using libindi1 version 1.2.0+r2671~201610271134~ubuntu16.04.1 and kstars-bleeding 1.2.0+r2671~201610271134~ubuntu16.04.1 and I don't see the use of switch "--parity". Sorry I didn't look into the code to find the option was provided, I think I have a discrepancy between libindi1 on the computer running KStars and libindi1 on the remote indiserver. But anyway, the solver solves relatively fast enough. When the input is wrong, the default distance of 30 degrees takes forever to finish on my Atom but succeeds to finish nonetheless.

I also observe a message stating the focal length is incorrect. In my case, the guider has a diameter of 50mm and a focal length of 162mm. Kstars warns the focal length should be 354mm from the results of plate solving. When I look at the actual log output of solve-field, there's no mention of that erroneous focal length and FOV values do match the input, so I suspect the warning is computed incorrectly at some point.

I ran this session with a few additional patches:
- indiserver is reaping terminated children by itself instead of blocking SIGCHLD
- V4L2 manual exposure is set unconditionally for every capture to work around the corrupted frames on my DMx ccd (though this seems to break streaming, will look into this)
- V4L2 buffers are checked for byte length when dequeued to drop corrupted frames on my DMx (though this patch doesn't trigger anymore with the exposure patch).
- Refactoring on buffer ioctls.
I'll push the changes soon, clear sky this week for test runs.
-Eric

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

Last Edit: by TallFurryMan.

Remote astrometry solver 11 months 3 weeks ago #12770

You probably mean version libindi v1.3? And KStars version is different as well. The "parity" settings was not implemented for the remote solver, it was implemented for online and offline solvers only. I will try to add support for remote solver as well today. The focal length is partly calculated from the pixel scale returned by the solver, so what was it in your case?

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?

Remote astrometry solver 11 months 3 weeks ago #12792

I've probably fumbled with the update sources on the Ekos VM, I'll check :) This means I'd verify the described behavior before actually raising any issue.

Here's an excerpt of the output of the remote solve-field:
log-odds ratio 78.5722 (1.32885e+34), 17 match, 0 conflict, 14 distractors, 30 index.
   RA,Dec = (61.8879,35.837), pixel scale 13.0917 arcsec/pix.
   Hit/miss:   Hit/miss: ++++++++-+++-+-+-+-+---------++(best)-++++
Field 1: solved with index index-4108.fits.
Field 1 solved: writing to file /tmp/ccdsolver.solved to indicate this.
Field: /tmp/ccdsolver.fits
Field center: (RA,Dec) = (61.890328, 35.837853) deg.
Field center: (RA H:M:S, Dec D:M:S) = (04:07:33.679, +35:50:16.272).
Field size: 69.9222 x 52.5107 arcminutes Field rotation angle: up is 20.7892 degrees E of N Creating new FITS file "/tmp/ccdsolver.new"...

The field size matches what Ekos computed from diameter (50mm) and focal length (162mm). The input values are assigned in my EQMod driver configuration, and the 70x52 field result is properly shown in the Capture&Solve tab. And if I use the focal length from the warning message in the EQMod configuration, the solver fails.
-Eric

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

Remote astrometry solver 11 months 3 weeks ago #12793

What's the pixel scale reported in the INDI Control Panel Solver tab?

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?

Remote astrometry solver 11 months 3 weeks ago #12797

I didn't understand your question at first, and replied with the field size instead of the pixel scale.
I really meant version 1.2.0 actually, for some reason the updates were stuck at Oct. 2016 (incidentally date at which I was in another country). It's being updated as I write.

In 1.2.0, I don't have a pixel scale in the align tab, and this is what the bottom log reports:
2016-11-29T21:50:26 Target is within acceptable range. Astrometric solver is successful.
2016-11-29T21:50:24 Slewing to target coordinates: RA (21h 30m 48s) DEC ( 12° 14' 37").
2016-11-29T21:50:24 Syncing to RA (21h 30m 47s) DEC ( 12° 14' 57") is successful.
2016-11-29T21:50:24 Target is within  0° 00' 20" degrees of solution coordinates.
2016-11-29T21:50:24 Solution coordinates: RA (21h 30m 47s) DEC ( 12° 14' 57") Telescope Coordinates: RA (21h 30m 49s) DEC ( 12° 14' 37")
2016-11-29T21:50:24 Current focal length is 162 mm while computed focal length from the solver is 351.68 mm. Please update the mount focal length to obtain accurate results.
2016-11-29T21:50:24 Solver completed in 13 seconds.

I'll update shortly with a more recent codebase, sorry about that.
-Eric

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

Remote astrometry solver 11 months 3 weeks ago #12804

This is what I get with libindi1 1.3.1+r2747~201611281623~ubuntu16.04.1 (Ekos and remote indiserver + patches) and kstars 5:16.12+201611281535~ubuntu16.04.1
2016-11-29T23:38:56 Target is within acceptable range. Astrometric solver is successful.
2016-11-29T23:38:56 Target is within  0° 00' 04" degrees of solution coordinates.
2016-11-29T23:38:56 Solution coordinates: RA (23h 05m 37s) DEC ( 15° 17' 50") Telescope Coordinates: RA (23h 05m 37s) DEC ( 15° 17' 51")
2016-11-29T23:38:56 Current focal length is 162 mm while computed focal length from the solver is 351.73 mm. Please update the mount focal length to obtain accurate results.
2016-11-29T23:38:56 Solver completed in 13 seconds.

Sorry, I don't see where the pixel scale is shown... :( The only one I found is in V4L2 CCD Astrometry, "Pixscale (arcmin)"=6.5679.
-Eric

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

Remote astrometry solver 11 months 3 weeks ago #12809

Ok, I found the issue. INDI CCD wasn't accounting for binning when sending pixel scale. I also added support for parity, however astrometry.net just added it in Git, so if you want to use that, you need to use the github version.
The following user(s) said Thank You: TallFurryMan

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Time to create page: 0.161 seconds

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!


Gallery

Replica

Why INDI

Replica