I can confirm it works fine without the parenthesis. Spaces seem to be OK in the path as well. I was posting more as an informational post to the original poster rather than looking for a big fix.
Also, thanks to you and the team for a great product!
I realize this is an older thread, but I just started having a similar issue. What I've realized, in my case, that the solver fails both via the CLI and via ekos when there is a parenthesis in the filename or path. Perhaps you all are having a similar issue?
Some logs here:
/usr/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -3 97.9257 -4 4.95925 -5 15 -L 1.07396 -H 1.31261 -u app --config /home/mike/.local/share/kstars/astrometry/astrometry.cfg -W /tmp/solution.wcs '/media/Storage/Astrophotography/Incoming/NGC 2238 (Rosette Nebula)/Light/OIII/NGC 2239_Light_OIII_600_secs_2019-03-22T00-28-26_001.fits' Reading input file 1 of 1: "/media/Storage/Astrophotography/Incoming/NGC 2238 (Rosette Nebula)/Light/OIII/NGC 2239_Light_OIII_600_secs_2019-03-22T00-28-26_001.fits"... Extracting sources... augment-xylist.c:941:augment_xylist Source extraction failed image2xy-files.c:47:image2xy_files Failed to open FITS input file /media/Storage/Astrophotography/Incoming/NGC 2238 (Rosette Nebula)/Light/OIII/NGC 2239_Light_OIII_600_secs_2019-03-22T00-28-26_001.fits ../util/cfitsutils.h:26:cfitserr could not open the named file ../util/cfitsutils.h:26:cfitserr failed to find or open the following file: (ffopen) ../util/cfitsutils.h:26:cfitserr /media/Storage/Astrophotography/Incoming/NGC 2238 (Rosette Nebula)/Light/OIII/NG ../util/cfitsutils.h:26:cfitserr C 2239_Light_OIII_600_secs_2019-03-22T00-28-26_001.fits
2019-04-01T17:34:11 Solver failed. Try again. 2019-04-01T17:34:11 Extracting sources... 2019-04-01T17:34:11 Reading input file 1 of 1: "/home/mike/Desktop/(Test)/NGC 2239_Light_OIII_600_secs_2019-03-22T00-28-26_001.fits"... 2019-04-01T17:34:11 /usr/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -3 97.9257 -4 4.95925 -5 15 -L 1.07396 -H 1.31261 -u app --config /home/mike/.local/share/kstars/astrometry/astrometry.cfg -W /tmp/solution.wcs /home/mike/Desktop/(Test)/NGC 2239_Light_OIII_600_secs_2019-03-22T00-28-26_001.fits 2019-04-01T17:34:11 Starting solver... 2019-04-01T17:34:11 Solver iteration #1 2019-04-01T17:34:11 Using solver options: -O --no-plots --no-verify --resort --downsample 2 -3 97.9257 -4 4.95925 -5 15 -L 1.07396 -H 1.31261 -u app
Thanks! Sorry for the late reply. I've done a little testing on my end and have noticed something that might be of interest. I experience the issue more on what I would consider "slow" devices. I typically use a raspberry pi, PI 3 MODEL B, for controlling my scope and gear. The pi, as we all know, has rather slow USB ports/IO. The issue is very reproducible on the pi. If I instead plug my gear directly into my laptop, using either the usb 2 or 3 ports, I experience the issue far less. It seems the issue is related to how long it takes to pull the image data off of the camera. I've seen similar issues reported with the PHD2 guiding suite. Here is a google group message I came across while poking around.
Any update on this issue? I'm seeing the exact same issues with my QHY guide cameras as well.
At this point, I'm assuming the issue was something I wasn't doing properly. I didn't have any issues last weekend, aside from the bright moon. Thanks!
Understood. Sadly I didn't grab them before I logged out last night and it's supposed to rain for the next few days. When I am able to test again, I'll upload some logs.
I've been using Ekos for a few months now, and am very impressed. Thanks for the great tool. I've noticed an issue, as of late, with the polar alignment (beta) tool. I am running Ekos on Ubuntu 17.04 64bit. Build: 2017-07-25T07:27:42Z works as expected. I navigate to the Polar Alignment tool. I click start, the tool captures an image, solves the image, then asks me if I want to auto-rotate my mount and capture the remaining two images. All is good.
I am unable to perform any successful polar alignments with any version after Build: 2017-07-25T07:27:42Z. The issue is when I begin the polar alignment, the tool will capture the first of three images, solve it, then just restart the capture and solve process over and over again. The tool never enters the mount rotation phase. I initially assumed it was me not pointing my scope close enough to the celestial pole, but that no longer seems to be the case.
Has something changed with the process for using the polar alignment tool? I've attempted to perform the polar alignment before, and after, using the Mount Model Tool. However, I am unsuccessful either way with any version of Ekos after Build: 2017-07-25T07:27:42Z.
Agreed. The connection issue is also resolved for me. Thanks for the hard work!
Thanks. I'll check in about an hour.
I've got the same issue as well still. I can confirm that version 0.3+r3130~201706160928~ubuntu17.04.1 on Ubuntu is working fine, though.