Ihoujin wrote: Can we get a warning in the status output for low star SNR with a recommendation to increase exposure time?


... and a check-box to automatically increase the exposure time if checked, and try again, say 3 times? I would not want it to be indefinite retries. This would be similar to the filter module where flats need to achieve an ADU range.

Jim

Read More...

Maybe just 2 sets of solver configs that are tried before failing? It is fast after all, what would it hurt? With luck, this could remove the need to manual tune much, and the system could make the configuration that worked the first configuration for the next solve.

All the tuning could still be in an advanced tab, of course, but it would be nice to not have to worry about it if possible.

$.02

Jim

Read More...

Rob, Jasem, contributers, and testers,

The amount of work and features going into this release is amazing. Thank you all very much.

Jim

Read More...

rlancaste wrote: Hey Jim,

I just pushed a possible fix for your build issue. Please see if it fixes the problem. If not, I will see what Jasem says.

Thanks,

Rob


Thanks Rob, I confirmed it was fixed yesterday, but failed to make it back here to let you know. Thanks!

Jim

Read More...

rlancaste wrote: Hi Jim, we will check it out. Thanks!


Just a friendly bump, the latest builds are still failing. download.copr.fedorainfracloud.org/resul.../builder-live.log.gz
make[2]: Leaving directory '/builddir/build/BUILD/stellarsolver-1.4.git'
In file included from /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/sep/extract.h:26,
                 from /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/sep/lutz.h:23,
                 from /builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/sep/lutz.cpp:25:
/builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/sep/lutz.cpp: In member function 'int SEP::Lutz::lutzalloc(int, int)':
/builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/sep/sepcore.h:69:23: error: 'malloc' was not declared in this scope
   69 |   {if (!(ptr = (typ *)malloc((size_t)(nel)*sizeof(typ))))  \
      |                       ^~~~~~
/builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/sep/lutz.cpp:63:5: note: in expansion of macro 'QMALLOC'
   63 |     QMALLOC(info, infostruct, stacksize, status);
      |     ^~~~~~~
/builddir/build/BUILD/stellarsolver-1.4.git/stellarsolver/sep/lutz.cpp:32:1: note: 'malloc' is defined in header '<cstdlib>'; did you forget to '#include <cstdlib>'?
   31 | #include <cstring>
  +++ |+#include <cstdlib>
   32 |


Read More...

Jim is friends with Rob Lancaster

@rlancaste @knro

Hi Rob, the latest merge to master is not playing well with the copr build. Realizing you may still be working on this, here is a link to the output if it helps: download.copr.fedorainfracloud.org/resul.../builder-live.log.gz

Jim

Read More...

Jim replied to the topic 'Problems with the internal guide' in the forum. 2 weeks ago

I have found not setting the guider camera, when both cameras are ZWO, to be best. The driver is wise, and still recognizes both cameras and lets you set one as the guide camera in the guider configuration. Just leave the Guider: entry blank in the Profile Editor.

Jim

Read More...

Jim replied to the topic 'IC1318 - SHO' in the forum. 2 weeks ago

www.flickr.com/photos/howarj/45666231995...m-72157701997082182/

An example of the lensing. It only happens with very bright stars. This was taken last year with my 1600MM-C Pro. For just about everything else though, it is a great camera.

@Deesk06, that is a great image, thanks for sharing!

Jim

Read More...

Jim replied to the topic 'joystick crash logitech f310' in the forum. 2 weeks ago

They are not installed by default. I gave a command on how to add them for the base qt5-qtbase package, but there are probably others that would be helpful as well. If you know what package in particular, we can ask that he install additional debug packages.

Read More...

Jim replied to the topic 'joystick crash logitech f310' in the forum. 2 weeks ago

Since he is using the copr for Fedora,it _should have_ built and been made available minutes after your push to master. I, however, prevented this from happening because the build was still set up to point to my repository for testing, which of course did not change. I updated it to point to knro/ekosdebugger now, and kicked a build. The new package should be available in a couple minutes, and going forward, will be available a couple minutes after a push to master in krno/ekosdebugger.

Jim

Read More...