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 - gvanhau

Pages: [1] 2 3 ... 23
1
General / LarsonSekanina coordinates not saved in proyect
« on: 2019 October 28 14:53:46 »
Hello

I was just re taking the processing of my solar images of the las solar eclipse (july 2)
Since it has passed some time y wanted to revise some of the parameters stored in some process icons.

I found out that center coordinates of the LarsonSecanina process where 0.
In order to verify, I entered the coordinates, saved the project  then loaded it again and coordinates where cero again.

Regards
Geert


 

2
New Scripts and Modules / Re: Pattern subtraction scripts
« on: 2019 May 13 13:46:06 »
Hello Vicent.

Have you checked it is realy te CCD aging?
I had a simmilar issue on  my CCD Camera (increasing amount of hot pixels), but after several tests, I decided to open de Camera to see if there was any visible damaged component. What I found out was that the Thermal paste between the cooling element a the CDD had lost contact.
After replacing the thermal paste the camera worked again like new.

Regards
Geert

3
General / Re: Cursor Readout Preview Disappears
« on: 2019 March 14 13:29:48 »
Hello

I had the same issue, so thanks Steve for your help.

Geert

4
Hola
En este foro se supone que que el idioma oficial es Ingles.
No obstante lo anterior,
Te comento lo siguiente para que puedas dar los primeros pasos:

Primero debes calibrar las imagenes agrupadas por filtro, es decir, por ejemplo, calibra las imagenes rojas con los flats hechos con ese mismo filtro, mas los bias y darks (que no usan filtro).
Después de calibrar cada conjunto debes alinear (registrar) todas las imagenes contra la misma referencia (da lo mismo si la referencia es rojo verde luminancia, etc)
Luego debes integrar las imágenes de cada grupo (los rojos con los rojos, los verdes con los verdes, etc. Ahí obtendrás una imagen combinada para cada filtro.

Ahora puedes combinar las imágenes obtenidas en el paso anterior usando el proceso channel combination (existen claro otras formas de combinar, pero para empezar este proceso es el mas sencillo. el resultado será una imagen en color, que puedes ahora seguir procesando como lo hacías con la 450D (por ejemplo DBE, color calibration,....)

Espero este breve resumen te sirva.

Saludos







5
General / Re: Masking in PixelMath: I can't make it work
« on: 2019 March 04 05:32:40 »
Hello

In order to use  pixel math with masks, the mask should be applied to the target image.
You have also to tell pixel math to replace the target image.  (if you let pixel math to create a new image, it won't work.

Regards
Geert

6
General / Re: Pixel Math If (Case or Switch statement)
« on: 2019 February 21 06:01:00 »
Hello

I dont have access to my PI computer right now, but I think something like this could work:

P(0)= 0.020749760758206493;
P(1)= 0.02083269071095121;
P(2)= 0.020591074008640423;
P(3)= 0.020587894424854085;
P(4)= 0.02125898032182231;
iif(x()>=0 && x()<5, P(x()),$T)

Asuming that we can declare P as an array

Regards
Geert

7
General / Re: Strange Artifacts in Lum only
« on: 2018 July 18 19:52:19 »
Hello

If the sensor is a KAF8300, and the exposure time is short, may be it is an artifact produced by the camera shutter.
In my atik383 (same sensor) I had to expose at least 10 secconds in order to avoid shutter artifacts.

Regards
Geert

8
General / Re: Amp Glow removal
« on: 2018 April 12 11:40:50 »
Hello
Normally if darks match the lights the amp glow sould be removed during calibration.

Be aware that your flats should also be calibrated with the apropiate dark flats, else it could be that the remaining amp glow is introduced by your flats.

You can do a test calibrating the ligths without flats to see if there is still ampglow (of course, vignetting and dust dognuts will be present)

Regards
Geert


9
General / Probable bug in last imagesolver update
« on: 2017 September 18 17:25:57 »
Hello
I got this message when trying to solve an image:

Processing script file: C:/Program Files/PixInsight/src/scripts/AdP/ImageSolver.js
* Using an automatically calculated limit magnitude of 14.88.
** Warning [162]: C:/Program Files/PixInsight/src/scripts/AdP/ImageSolver.js, line 2490: reference to undefined property this.solvercfg
*** Error [222]: C:/Program Files/PixInsight/src/scripts/AdP/ImageSolver.js, line 2490: TypeError: this.solvercfg is undefined

regards
Geert

10
General / Re: running into Flat subtraction issue
« on: 2017 March 08 06:44:52 »
Hello
May be you could try calibrating using the method I described in this link:
http://pixinsight.com/forum/index.php?topic=9312.msg59752#msg59752

At least it gives good results for me on my QHY8L.


Regards
Geert

11
General / Re: running into Flat subtraction issue
« on: 2017 March 06 05:42:12 »
Hello
Since the integration images include images of both meridian sides, it is perfectly posible that the spots are the effect of the rotation during image registration.

So I agree with Rob that the investigation should be centered on "why flats are over correcting".

One thing I would investigate is if the QHY10 is working linear; As far as I know you have gain and offset adjustments, if they are to far off, meay be you are working outside the linear part of the sensor.

Regards
Geert


12
Thank You very much Juan.

I installed the update and tested it several times on the FX PC. Could not krash PI anymore.
Also reverted the clocking of my PC to normal and tested again wo issues.

The load on the machine is a litle less than before (98-99% CPU vs 100%), but speed is very, very high compared to the mono thread version.

For me this issue is solved.

Regards
Geert

13
Hello Mike

I'm not overclocking my machine, I always used it at the rated values. At contrary, I'm currently downgrading it . My RAM is rated at 1.866GHZ and Im now using it at 1.333 GHZ
My CPU is rated at 4GHz and Im now using it at 3.6 GHz. 

The only APP that crashes is PI, all other concurrent tasks still work. I can immediatelly restart PI and test again, without rebooting. If there was a HW issue most likely it should also affect other running app's  but it doesnt.

Obviously, I can not completelly discard HW issues on both machines, and therefore,  I am still testing every thing again and again. 

Regards









14
Hello Juan
Thank you for your answer.
I know this is a difficult issue to analyze.

I also know, there are/were other processes in PI that were running on multiple cores long before the last upgrade, an they did never crash on my computers.

Im currently working on several sets of 100 to 200 fits images of a Kaf 8300 mono camera (8M pix); the same sets before the upgrade did never crash.

Not that I'm willing to discard a HW issues a priory, but I think it is not likely thay 2 computer suffer from the same issue at once.

Both computers are desktops; one using a Phenom 4 core AMD processor and 8GB ram the other using a FX AMD processor and 32GB ram the last one has a liquid cooler - radiator; I monitored the temp CPU and several components in M.Bo and none ever rised above 48° C, so I dont think this is a temp issue.

The FX processor is running at its rated 4 GHz speed, but even limiting (downgrading) the processor speed and /or ram speed prevented the crash. Only limiting PI to use 1 core on global settings does its job ok. 

On the Phenom computer I am using Kaspersky antivirus, on the FX computer I'm using Norton.

I dont think that running this on a virtual machine is a throughout test, since the VM introduces a lot of other stuff between OS and HW and/or Bios which can alter timing.

Regards.
Geert







15
Hello
Since the last update, where image registration and image integration are now using multiple cpu cores, I am getting random PI crashes.
Sometimes it chashes wit few procesed images, other times it crashes after processing lots of images.
After each crash, PI is aborted and has to be started again.

I could reproduce this issue in two different computers using windows 10.

I like the performace increase of both proceses, so hopefully this bug is solved asp. 

Regards
Geert

Pages: [1] 2 3 ... 23