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

Pages: 1 ... 263 264 [265] 266 267 ... 270
3961
You're not going crazy. I've had the same problem. Linux x86_64. Other than that no problems so far.

First. I created a new master bias/dark and flat per Vicent's tutorial.

I don't want to confuse the issues, as it is very easy to do so. So I'll state outright, that the presence of a master flat during the calibration of light frames whether the calibrate check box was selected or not, causes noise evaluation to fail during image integration.

I spent hours yesterday testing this, trying every combination of master bias/dark/flat - calibrate selected and not selected.

sub note: On the basis of the above. I assumed that no calibration of the Master Bias/Dark frames had taken place during the calibration of the Flat frames (although no errors were observed). And it was necessary to check the Master Bias/Dark Calibrate check box to avoid failure of noise estimates during image integration. This is consistent with Vicent's advice in another thread.

noise eval fails completely, or just falls back to the k-sigma estimate? i see the k-sigma fallback all the time but i never made the connection with flats.

looks like there's some issues in ImageCalibration then, hopefully Juan can get to the bottom of them.

3962
Release Information / Re: PixInsight 1.6.9.651
« on: 2010 December 31 13:06:49 »

No, this is not an update, this is a new version that you must install! ;D


Are there special install/uninstall instructions.
I had some issues getting both the 32 and 64 bit versions installed on my Mac.
Fortunately instructions were posted explaining the need to have (very specifically named) separate folders within the (Mac) applications folder for each of the PixInsight versions.
Do I need to uninstall these?
Or may I simply download the new versions and place the new apps in the appropriate folder.

Thanks,
Don

looks to me like you just put the new versions in /Applications and you should be good to go. they seem to be named PixInsight32 and PixInsight64 now so they can live side-by-side in /Applications. actually you can put them in whatever folder you want, as it appears that juan is now not hardcoding the location of the pixinsight binary into the plist file.

having said that, once you start 1.6.9.651 you won't be able to start the old 1.6.9 anymore because of the dynamic dereferencing of the pixinsight binary location. the old version won't be able to find it's processes and scripts. you'd need to delete ~/Library/PixInsight/Pixinsight*.plist (or move it out of the way temporarily) in order to start up the old version, but of course you'll lose all your prefs. so i guess make a backup copy of PixInsight64.plist and PixInsight32.plist before you start .651 for the first time, and you can swap those plists in if you need to revert to the older version of 1.6.9.

3963
okay, sorry for all the noise. i narrowed this down some more. even in 1.6.1, it seems that the flat scaling goes bad when the "calibrate" checkbox is ticked in the master flat section. this must be because i calibrated the master flat when i created it.

in 1.6.1 ImageCalibration seems to respect this checkbox.

in 1.6.9 (both versions) it would seem that ImageCalibration is ignoring the checkbox and always trying to calibrate the master flat. in the original 1.6.9 the scaling factors are small but the tool proceeds and the resultant calibrated light still shows vignetting. in 1.6.9.651, the scaling factors are determined to be 0 and the tool quits.

now, i think i might be going crazy because i seem to recall there was an update to ImageCalibration for this very problem, but now i can't find any evidence of that.

3964
okay, now i can see that the last time i did this, i used 1.6.1 to calibrate the lights. so it would appear that there's a problem with ImageCalibration in both versions of 1.6.9.

3965
hmm, well... the files from last night do not look so flat. i don't understand this though because i calibrated them identically. perhaps something else is going on.

i do know that if i debayer my master flat and divide one of my raw lights by the master flat, the resulting frame is very flat. so i'm not sure why PI wants to scale the flat so drastically.

regardless the behavior between versions of 1.6.9 does differ, but it is possible it's the prior version that is buggy and proceeding with such a drastic scaling of the master flat...?

3966
i just upgraded to the latest, and tried to calibrate some files from last night.

the master calibration frames i am using were prepared using astropixel's tutorial and are bayerRGB files with no CFA data, and have always worked in the past.

when it comes time for the ImageCalibration tool to compute the scaling factors for the master flat, it comes up with 0,0,0 and quits. i reverted to the previous release of 1.6.9 and was able to calibrate my CR2 files just fine with the same master calibration files. to be honest the scaling factors are quite low (0.013, 0.017,0.04), so maybe there's something wrong with my files. but the calibrated lights look very flat to me.

by the way, because of the way 651 dynamically finds it's process binaries, i could not revert to the previous version of 1.6.9 without moving PixInsight64.plist out of the way. otherwise it chokes trying to dereference the new pointer to the dylib directory...

3967
Release Information / Re: PixInsight 1.6.9.651
« on: 2010 December 30 19:54:31 »
?? both pixinsight32 and 64 (osx here) are not showing any updates available, and it's been several hours since i received the email...  ???

3968
Hi Rob,

...while I was in a different space, and the scripts terminate execution without disturbing...

oh sorry, i can't read.

This may not be a OSX only bug. When my code opened a new window, while I was on another desktop, it was changed to the one where PI was running. Fedora + KDE.

BatchDebayer definitely creates all kinds of windows as it's running but IIRC BatchFormatConversion does not. both scripts will cause this "spontaneous raise" behavior in PI, for me at least.

3969
General / Re: Problem with image integration in PI 1.06.09?
« on: 2010 December 24 00:50:20 »
that's how i prepare the bias frames to make a master bias frame: CR2->fits using DSLR_RAW set to raw bayer RGB.

you should not convert the bias frames to TIF with lightroom, it's going to make the linear data nonlinear as part of it's debayer process... the only way to properly calibrate DSLR images is to work in bayerRGB format until calibration is finished. at that point you can use the BatchDebayer script to interpolate the images, and then register and stack the debayered images.


3970
i'm finding that it comes and goes. i have not figured out what triggers it.

maybe can you try turning on spaces? it's just a virtual desktop manager, i'm sure you're familiar with those. it in the system preferences, top row, "expose and spaces". i have 8 spaces going (2 rows and 4 columns).

thanks

3971
this also happens with the 32-bit version. is it just me? it's super annoying  :-\

3972
Bug Reports / 1.6.9 osx x86_64 gui behavior (and 1.6.1 actually)
« on: 2010 December 22 15:28:17 »
Hi Juan -

i'm not sure if this behavior is only present on the x86_64 version of PI or not; i need to try it on the 32-bit version still. so this might fall under "graphical weirdness" on osx x86_64:

when a script is running, PI just will not stay "lowered". at some point during the execution of the script (batchformatconversion and batchdebayer both cause this), PI comes to the foreground on its own. when using OSX's spaces feature this is particularly annoying because you switch to another space while PI is working and boom, it comes right back to the space that PI is in with PI on top.

i'm still on osx 10.6.3, not sure if this has something to do with it.


3973
Bug Reports / 1.6.1 osx x86_64 hang when writing 32-bit fits file
« on: 2010 December 17 12:25:55 »
i didn't have the presence of mind to figure out why PI hung. i was too scared i was going to lose everything.

all i can say is that i attempted to save an image window as f32 fits, and PI reported a segmentation violation right after the file was written.
i then tried to overwrite the file by saving it a 2nd time, and PI hung.

i was able to attach with gdb and get it unstuck:

(gdb) attach 32300
Attaching to process 32300.
Reading symbols for shared libraries . done
Reading symbols for shared libraries ... done
0x00000001002b3e26 in pi::__DisposeFormatData ()
(gdb) return
Make selected stack frame return now? (y or n) y
#0  0x00000001002bb22b in pi::ImageWindow::Write ()
(gdb) cont
Continuing.

Program received signal SIGSTOP, Stopped (signal).
0x00000001002bb22b in pi::ImageWindow::Write ()
(gdb) cont
Continuing.

i should have tried to figure out exactly where in DisposeFormatData it was stuck, sorry about that.


3974
Workshops and Conferences / Re: AIC2010
« on: 2010 December 10 11:12:59 »
yeah, it's silly. the place was packed and i'm not sure how limiting the talk collateral is going to encourage more people to attend. if anything it's pissing people off :)

RBA's PDF is really good; the text of his presentation is on each slide so you can actually learn something even though you were not there. most of the other PDFs are simply the slides so sometimes they are hard to follow.

3975
General / Re: Saved Image Format
« on: 2010 December 03 09:49:17 »
Pde: I am trying to calibrate, in PI, an image that has been acquired in Maxim.
The Master Dark, Master Bias, and Master Flats have also been created in Maxim.



this is exactly the situation that i had a lot of problems with. in particular, for whatever reason, the illumination profile of the flat coming out of maxim just seemed completely wrong. it greatly exaggerated the vignetting. i never got to the bottom of it because i don't own maxim.

maybe you can calibrate the frames with maxim? that worked fine for me, and then the file format was not as much of a problem. since PI is by default set to expect the range [0..1] in an f32 fits file, it does then ask what to do when it encounters values > 1.0 in the calibrated file from maxim.

at this point you might want to post the files and see if Juan or Vincent can take a look at them and make a suggestion as to how to proceed.

Pages: 1 ... 263 264 [265] 266 267 ... 270