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 - David Serrano

Pages: [1] 2 3 ... 34
1
Announcements / Re: Happy New Year!
« on: 2018 January 04 13:48:54 »
Some personal issues have kept me out of my normal work for a few months, especially in the development and forum support fronts. This is going to change very soon

Sounds like hard times. Even that change could be actually good or bad for you—it's undefined but I'm not asking! :)

Happy new year Juan, and let's hope everything ends up on the green side.

2
General / Re: PI not running on Ubuntu upgraded to 17.10
« on: 2017 December 25 02:27:04 »
This is replied elsewhere in this forum. Just rename the symlink /opt/PixInsight/bin/lib/libz.so.1 to anything else.

3
I think the biggest problem is that you have to launch PixInsight  for each optimization step and this can be quite slow. I think that there is no way to launch a script in a running instance of PixInsight.

Maybe PI could be arranged to be launched only once, and the script would poll for the existence of the config file containing the parameters. When the file appears, the script would do its processing, delete the file and poll again. Then the user can write another file with different parameters to cause the script to fire again without the overhead of launching PI.

4
Gallery / Re: Total lunar eclipse, 2015-09-28
« on: 2015 October 01 13:37:55 »
Awesome work! The first one looks almost like a joke until you read the explanation :).

5
General / HDRComposition: Incompatible image geometry
« on: 2015 September 27 03:28:59 »
I'm trying to HDR compose 3 images and I'm finding this:

Code: [Select]
HDRComposition: Global context

Opening files:
/home/hue/IMG_003510.CR2

Timestamp: Sun Jun  7 16:26:09 2009
Camera: Canon EOS 40D
ISO speed: 100
Shutter: 1/1024.0 sec
Aperture: f/19.9
Focal length: 18.0 mm
Embedded ICC profile: no
Number of raw images: 1
Thumb size:  1936 x 1288
Full size:   3944 x 2622
Image size:  3908 x 2602
Output size: 2602 x 3908
Raw colors: 3
Filter pattern: RG/GB
Daylight multipliers: 2.444244 0.930336 1.163797
Camera multipliers: 2335.000000 1024.000000 1367.000000 1024.000000

Invoking: dcraw -4 -o 0 -w -q 2
Decoding Canon EOS 40D file (3908x2602 pixels, ISO=100, Exposure=1/1024s): done
Loading raw image: done
/home/hue/IMG_003511_r.fit
*** Error: /home/hue/IMG_003511_r.fit: Incompatible image geometry.
<* failed *>

It's one CR2 and two FIT images, these two being the result of a FFTRegistration made earlier this week.

Then I opened the 3 images to check their geometry:

Code: [Select]
Reading 3 image(s):
/home/hue/IMG_003510.CR2

Timestamp: Sun Jun  7 16:26:09 2009
Camera: Canon EOS 40D
ISO speed: 100
Shutter: 1/1024.0 sec
Aperture: f/19.9
Focal length: 18.0 mm
Embedded ICC profile: no
Number of raw images: 1
Thumb size:  1936 x 1288
Full size:   3944 x 2622
Image size:  3908 x 2602
Output size: 2602 x 3908
Raw colors: 3
Filter pattern: RG/GB
Daylight multipliers: 2.444244 0.930336 1.163797
Camera multipliers: 2335.000000 1024.000000 1367.000000 1024.000000

Invoking: dcraw -4 -o 0 -w -q 2
Decoding Canon EOS 40D file (3908x2602 pixels, ISO=100, Exposure=1/1024s): done
Loading raw image: done
/home/hue/IMG_003511_r.fit
27 FITS keywords extracted
ICC profile extracted: 'sRGB IEC61966-2.1', 3024 bytes
Reading FITS: 16-bit integers, 3 channel(s), 2602x3908 pixels: done
/home/hue/IMG_003512_r.fit
27 FITS keywords extracted
ICC profile extracted: 'sRGB IEC61966-2.1', 3024 bytes
Reading FITS: 16-bit integers, 3 channel(s), 2602x3908 pixels: done

So geometry is 2602x3908 in all cases. It should work, right? But I noticed that when decoding the CR2 it says:

Code: [Select]
Image size:  3908 x 2602
Output size: 2602 x 3908

So it switches from "landscape" to "portrait", so to speak. If I open the JPG that was created by the camera alongside the CR2, it opens in "landscape". This may have something to do…

Is it a bug? ;). If not, what can I do besides the obvious step of rotating the first (CR2) image?

6
So I need to figure out the order of debayering, multiplying with WB factors and rescaling to span the dynamic range. I plan to post back here once I think I've found the solution. In short I hope to know all of the steps that are performed under the hood when an image is read as debayer-RGB with the camera white balance applied.

That would be pretty interesting. If you did that and if you had a spare bitcoin address to share, I'd happily invite you to a pizza. No kidding.

7
The problem here is that, frankly, I've run out of ideas as to how to fix this. The compiler bug persists even after disabling optimizations and reorganizing the code. There is something in the code shared by these routines that VC++ 2013 cannot compile correctly. This would need a debug session to identify the problem at the assembler level, but I haven't found the time to do this.

<mode="wonderland">Well you have paid for the product, right? Can't you nag the support team?</mode> Sorry for the stupid question, just an idea :).

8
Often, the back-of-camera image looks pretty good for me, so I would like to use a similar histogram transformation as a starting point when working with daytime raw images. Are there specific settings in HistogramTransformation or some other process I could use to emulate the stretch that the camera gives me?

Probably not what you're looking for, but I usually shoot in RAW+small JPG mode and then I open both files in PI so I have the JPG one as a reference.

9
General / Re: Does GREYCstoration depend on scale?
« on: 2015 May 25 23:40:52 »
I know that I'm not going to solve your question, but... Why are you using GREYCstoration? TGVDenoise should by way better for this job. :)

I'm finding I don't like TGVDenoise's results that much. "It's a poor workman who blames his tools" yeah, I guess the workman will have to improve :)—it's a new tool after all. For completeness, I must say that GREYCstoration worked fine on the next day with a different image. I'll have to try again with this one...

10
General / Does GREYCstoration depend on scale?
« on: 2015 May 22 17:50:08 »
I'm killing the noise in this Corona Borealis shot:



With the parameters that can be seen there, this is the result for the first preview:



Pretty poor indeed, but in p02 things do change:



Wow, we're improving, although I can't understand why. I thought this tool gave the same results regardless the size of the view. If applying on p03 we get:



Pretty much the same, although a couple of faint stars are no longer there. Not good… then, applying to the whole image:



Lots of stars go away :(.

Now, I'm aware that some processes like HDRMultiscaleTransform are scale-sensitive and it's pointless to use previews with them. But I've always regarded GRECYstoration as not falling into this category so I'm pretty surprised (and mystified) by these results. Is there any plausible explanation for this?

FWIW, I'm running with 'parallel --disable' because of this, which I'm still experiencing in PixInsight 1.8.

11
General / Re: How do I get out of 'full screen' mode?
« on: 2015 May 13 23:24:20 »
Right, I'm pretty sure a reboot would clear the problem. I'm also pretty sure that simply killing PI would clear the issue.

Oh, that suggests PI is running 100% of the time in that box. I didn't knew that, sorry.

12
General / Re: How do I get out of 'full screen' mode?
« on: 2015 May 12 23:19:37 »
I was hoping for a method that would not involve shutting down PI.

I think he means "rebooting the computer" as in a way to get rid of the problem that is preventing you from going to full screen to windowed, ie. a one time event.

13
In CurvesTransformation, CIE c* doesn't seem to be transformed when CIE a* is also touched. However, if a* is reset and we edit b* instead, then c* is honoured. This alone is why I'm posting under "Bug reports".

Code: [Select]
var P = new CurvesTransformation;
P.R = [ // x, y
   [0.00000, 0.00000],
   [1.00000, 1.00000]
];
P.Rt = CurvesTransformation.prototype.AkimaSubsplines;
P.G = [ // x, y
   [0.00000, 0.00000],
   [1.00000, 1.00000]
];
P.Gt = CurvesTransformation.prototype.AkimaSubsplines;
P.B = [ // x, y
   [0.00000, 0.00000],
   [1.00000, 1.00000]
];
P.Bt = CurvesTransformation.prototype.AkimaSubsplines;
P.K = [ // x, y
   [0.00000, 0.00000],
   [1.00000, 1.00000]
];
P.Kt = CurvesTransformation.prototype.AkimaSubsplines;
P.L = [ // x, y
   [0.00000, 0.00000],
   [1.00000, 1.00000]
];
P.Lt = CurvesTransformation.prototype.AkimaSubsplines;
P.a = [ // x, y
   [0.00000, 0.00000],
   [0.48930, 0.52941],
   [1.00000, 1.00000]
];
P.at = CurvesTransformation.prototype.AkimaSubsplines;
P.b = [ // x, y
   [0.00000, 0.00000],
   [1.00000, 1.00000]
];
P.bt = CurvesTransformation.prototype.AkimaSubsplines;
P.c = [ // x, y
   [0.00000, 0.00000],
   [0.03743, 0.42513],
   [1.00000, 1.00000]
];
P.ct = CurvesTransformation.prototype.AkimaSubsplines;
P.H = [ // x, y
   [0.00000, 0.00000],
   [1.00000, 1.00000]
];
P.Ht = CurvesTransformation.prototype.AkimaSubsplines;
P.S = [ // x, y
   [0.00000, 0.00000],
   [1.00000, 1.00000]
];
P.St = CurvesTransformation.prototype.AkimaSubsplines;

To reproduce: open an image, open CT, edit its source code, paste that, apply to the image. What this does is alter CIE a* a bit, and do an obvious modification to CIE c*. However, c* is, in this computer at this moment, ignored. (edit: Real-Time Preview works as expected)

To rule out the possibility of being bitten by a memory corruption that might have happened elsewhere during the previous 2 hours of PixInsight'ing, I restarted the program—however I could immediately reproduce this. Can anyone else try, please?

14
Wish List / DynamicCrop has it backwards. And, thirds.
« on: 2015 May 05 12:08:54 »
DynamicCrop works by interactively letting the user choose an area to crop. This area is displayed with reduced contrast. However, wouldn't it make more sense to reduce the contrast (and/or brightness!) of the area outside the crop? Cropping is useful not only for easily getting rid of unwanted things near the borders, but it's also a composition tool. It's useful to be able to concentrate on the resulting image by having it displayed unmodified, while the uninteresting parts are obscured.

And, since it's a composition tool, it could very well display a couple of vertical and horizontal lines at 33/67% of width/height. Or maybe at Fibonacci's 38.2/61.8%. Those would also help when a diurnal landscape image is tilted and we want to rotate it to get a horizon that honours it's name :).

15
Quote
I do not always necrobump…


…but when I do, it's in an 8 year old own thread 8)

I'm curious about any specific reason why this script hasn't made its way into the bundle. Half an hour ago I thought it had just become rotten and a decision had been made to drop it, however I tried running it and, lo and behold, still works like a charm! So I infer that it was never included in the first place. Is there anything better these days?

For anyone interested, at this point (PixInsight 1.8.3.1123) there are two fixes needed:

  • At line 336 we have "for (n = 0; ..." but that gives a warning "assignment to undeclared variable". Turning it into "for (var n = 0" makes the error go bother someone else.
  • At 154 there's a more serious one: "ImageWindow.zoomToFit(): Wrong number of arguments". The script calls "window.zoomToFit (false)", I guess there has been an API change here. "window.zoomToFit ()" works fine.

Pages: [1] 2 3 ... 34