Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - kkretzsch

Pages: [1] 2 3 ... 5
Hi Juan,
I have no asteroid images yet, but a confirmation how good the plate solving algorithm works (see attachment). The resolution of the image is 0.8 arc seconds per pixel.

Thanks !

PCL and PJSR Development / Re: INDIClient compile error
« on: 2019 January 16 07:42:05 »
Hi Joe,
I'll check. I know from Juan, that he also had problems to compile the INDIClient on windows. Do you use INDI on windows? If not please ignore the module. I am currently rewriting the INDI client to use a different INDI library. Then this problem will become obsolete.


PCL and PJSR Development / Re: INDIClient compile error
« on: 2019 January 13 01:50:23 »
Hi Joe,
are talking about compiling on windows? Whicv version (PCL & VS compiler version) are you using?


PCL and PJSR Development / Re: Using the PCL and the API
« on: 2018 December 24 04:11:53 »
Hi Christer,
the PCL documentation can be found here The API is well documented. On github you can find a minimal module called Sandbox (src/modules/processes/Sandbox), which is useful to understand what is needed to create your own C++ module. There you also find the make or vsproject files to build the project.

If you create your own module, you can use the PixInsight script Script->Development->Makefile Generator to create make/vsproject files for your new module. Please note that the PCL environment variables as described on the github Readme (, have to be correctly set when you want to use the Makefile generator.

A new module can be loaded into PI with PI under  Process->Modules->Install Modules. If the new module was installed correctly, it will be loaded automatically after PI restart. If the new modules crashes, it will be removed from the installation list and you have to add it manually again with Process->Modules->Install Modules.

Hope that helps!

General / Re: PixInsight API Error
« on: 2018 June 18 07:01:10 »
Looks if there is still a space -> last character "Nuit_du_17_au_18_Juin_2018_Ha "

General / Re: PixInsight API Error
« on: 2018 June 18 06:32:43 »
not sure, but maybe the spaces in your directory "Nuit du 17 au 18 Juin 2018 Ha " could be the cause of the problem.


General / Re: Photometric Color Calibration Error Message
« on: 2018 June 05 03:33:11 »
the error message comes from the fitting procedure to evaluate the white balance -> Interactive Graphs

I think the image that causes the problem does not contain enough stars.


Bug Reports / Re: Assertion in nouveau_pushbuf_data
« on: 2018 June 01 14:20:56 »
seems that on ubunutu the nouveau driver is installed by default, even if e.g. an nvidia graphics card is installed. Installing the correct nvidia driver solves the problem.

Here an excellent wiki article about finding the correct driver (sorry in german only)


Hi Colin,
good to know thanks! Just to clarify, the indiserver itself runs fine even on a raspberry pi 2. If you use a pi with ubuntu mate it is very easy to install and upgrade all the required indi software.


Bug Reports / Assertion in nouveau_pushbuf_data
« on: 2018 May 19 10:33:51 »
Hi Juan,
after starting the docuemnt browser I often run into an assertion as shown below. Seems to be an problem between the qt5 webengine  and the nouveau driver?


(gdb) bt
#0  0x00007f87dc4b6428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#1  0x00007f87dc4b802a in __GI_abort () at abort.c:89
#2  0x00007f87dc4aebd7 in __assert_fail_base (fmt=<optimized out>, assertion=assertion@entry=0x7f87cc698729 "kref", file=file@entry=0x7f87cc69870a "../../nouveau/pushbuf.c",
    line=line@entry=727, function=function@entry=0x7f87cc698750 "nouveau_pushbuf_data") at assert.c:92
#3  0x00007f87dc4aec82 in __GI___assert_fail (assertion=0x7f87cc698729 "kref", file=0x7f87cc69870a "../../nouveau/pushbuf.c", line=727,
    function=0x7f87cc698750 "nouveau_pushbuf_data") at assert.c:101
#4  0x00007f87cc696b04 in nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/
#5  0x00007f87cc696a4b in nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/
#6  0x00007f87cc696b99 in ?? () from /usr/lib/x86_64-linux-gnu/
#7  0x00007f87cc696e3f in ?? () from /usr/lib/x86_64-linux-gnu/
#8  0x00007f87cc697a00 in nouveau_pushbuf_kick () from /usr/lib/x86_64-linux-gnu/
#9  0x00007f87cd067ab6 in ?? () from /usr/lib/x86_64-linux-gnu/dri/
#10 0x00007f87ccd481c6 in ?? () from /usr/lib/x86_64-linux-gnu/dri/
#11 0x00007f87cce8e782 in ?? () from /usr/lib/x86_64-linux-gnu/dri/
#12 0x00007f87da9c74cc in ?? () from /usr/lib/x86_64-linux-gnu/mesa/
#13 0x00007f87e90cf68a in QGLXContext::swapBuffers(QPlatformSurface*) () from /opt/PixInsight/bin/lib/qt-plugins/xcbglintegrations/
#14 0x00007f87de12a55d in QOpenGLContext::swapBuffers(QSurface*) () from /opt/PixInsight/bin/lib/
#15 0x00007f87de38fae6 in QPlatformBackingStore::composeAndFlush(QWindow*, QRegion const&, QPoint const&, QPlatformTextureList*, QOpenGLContext*, bool) ()
   from /opt/PixInsight/bin/lib/
#16 0x00007f87cea3c949 in QXcbBackingStore::composeAndFlush(QWindow*, QRegion const&, QPoint const&, QPlatformTextureList*, QOpenGLContext*, bool) ()
   from /opt/PixInsight/bin/lib/
#17 0x00007f87de6f9fef in QWidgetBackingStore::qt_flush(QWidget*, QRegion const&, QBackingStore*, QWidget*, QPoint const&, QPlatformTextureList*, QWidgetBackingStore*) ()
   from /opt/PixInsight/bin/lib/
---Type <return> to continue, or q <return> to quit---
#18 0x00007f87de6fb548 in QWidgetBackingStore::flush(QWidget*) () from /opt/PixInsight/bin/lib/
#19 0x00007f87de6fc250 in QWidgetBackingStore::doSync() () from /opt/PixInsight/bin/lib/
#20 0x00007f87de6fd8c9 in QWidgetBackingStore::sync() () from /opt/PixInsight/bin/lib/
#21 0x00007f87de716ebf in QWidgetPrivate::syncBackingStore() () from /opt/PixInsight/bin/lib/
#22 0x00007f87de72b614 in QWidget::event(QEvent*) () from /opt/PixInsight/bin/lib/
#23 0x00007f87de818eeb in QMainWindow::event(QEvent*) () from /opt/PixInsight/bin/lib/
#24 0x00007f87de6ee23c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /opt/PixInsight/bin/lib/
#25 0x00007f87de6f4f80 in QApplication::notify(QObject*, QEvent*) () from /opt/PixInsight/bin/lib/
#26 0x00000000005f1c9f in ?? ()
#27 0x00007f87ddb00275 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /opt/PixInsight/bin/lib/
#28 0x00007f87ddb025c3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /opt/PixInsight/bin/lib/
#29 0x00007f87ddb502d3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /opt/PixInsight/bin/lib/
#30 0x00007f87e7112197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/
#31 0x00007f87e71123f0 in ?? () from /lib/x86_64-linux-gnu/
#32 0x00007f87e711249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/
#33 0x00007f87ddb4fb1c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /opt/PixInsight/bin/lib/
#34 0x00007f87ddafe6eb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /opt/PixInsight/bin/lib/
#35 0x00007f87ddb068a4 in QCoreApplication::exec() () from /opt/PixInsight/bin/lib/
#36 0x0000000000463360 in ?? ()
#37 0x00007f87dc4a1830 in __libc_start_main (main=0x45fe70, argc=1, argv=0x7ffe69c546f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>,
    stack_end=0x7ffe69c546e8) at ../csu/libc-start.c:291
#38 0x000000000048e473 in ?? ()

General / Re: Using PixInsight for variabel star observations?
« on: 2017 December 06 01:32:22 »
Hi Magnus,
I used the aperture photometry script to measure an exoplanet transit some time ago.

The script is able to automatically measure the (uncalibrated) fluxes of many stars in the field, so that you get a good statistic for your measurement (see picture in tresca database). The result of the script can be exported to .csv format, so that you easily can calculate relative star fluxes and magnitudes from these data. The quality of the data are flagged, e.g. if the statistic is bad, or a second star is too close for a precise measurement.

But I didn't, submit my data to AAVSO or similar, so I don't know, whether theses data comply the requirements of an official AAVSO submission.


General / Re: INDI Device Controller
« on: 2017 November 17 01:52:26 »
please find first examples here:


Tutorials and Processing Examples / INDI client tutorial videos
« on: 2017 November 09 10:21:04 »
I managed to create some videos showing new and old features of the INDI client in PixInsight 1.8.5

Getting started with INDI client:

Image Acquisition including centering to target coordinates

Mosaic acquisition with new BatchAcquisition script


Gallery / Re: 2017 eclipse - HDR
« on: 2017 November 01 09:40:29 »
i just used the readout cursor to measure the corona near the edge of the shadow of the moon, and yes i used a circular pixelmath equation to fill it in.
Thanks Rob, this indeed solved my problem. I used the following PixelMath expression

iif( sqrt((x()-x0)*(x()-x0) + (y()-y0)*(y()-y0)) < r, h_R/G/B , $T )

, where (x0,y0) is the center of the moon shadow, r is the radius (in pixel units) and h_R/G/B the intensity values of the R/G/B channels. After applying  this PixelMath expression the HDRMultiScale trafo produced much better results. I applied LHE and Larsson-Sekanina to the stretched image (MaskedStretch) to protect the bright structures close to the sun surface.     

Gallery / Re: 2017 eclipse - HDR
« on: 2017 October 24 15:19:07 »
Hi Rob,
what i did was to use pixelmath to replace the moon with the color of the corona that was just outside of the moon's edge. i believe that removing the brightness discontinuity represented by the moon helps the HDRMultiscale transform work better without ringing.
I have a similar problem with a ringing effect after applying the HDRMultiscale to the HDRcomposed image. How did you replace the moon with the color of the corona using pixelmath? Did you create a special mask to define the moon? Which expression did you use?


Pages: [1] 2 3 ... 5