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

Pages: [1] 2 3 ... 15
1
General / Re: Color space confusion...need help
« on: Today at 15:00 »
John,
I tried that...changing the profile tag alone (to PhoPhoto) leaves the image unchanged in PI. But saving-reopening it leads to a dark image that has the ProPhoto tag. Changing that tag to sRGB does not change the inmage.

If I assign the image a ProPhoto profile, it immediately has major color shifts.
Alex

2
General / Color space confusion...need help
« on: Today at 13:46 »
Hi, I have a problem. Normally I work in ProPhoto, and convert to sRGB for final output. However, I did something wrong at the wrong time and now have a fully processed image-that looks just like I want it to,...but I cannot save and recover that image (say as a jpg).-I think I at some point change the tag from ProPhoto to sRGB without actually transforming the profile, then continued processing. Now, if I save the image, as is, then re-open it, it is too dark and has a color shift (just like opening a ProPhoto image in a pgm that expects sRGB). If I change the tag (no transform applied) to sRGB and save it. When reopened, again it is wrong.
Is there some way to keep the image I see in PI, and assign a color space to the image (or apply some other magic or program) so that it reopens looking just like the image I saved?

Thanks, Alex

3
General / Re: Pixinsight not starting...
« on: 2019 April 11 15:18:20 »
Sometimes happens to me if there is a instance running in the task manager that closed improperly, I guess.
Try...
Right click task bar and open task manager
Look for PI, if there, terminate it.
Try to star PI again.

Here's hoping! Alex

4
Bug Reports / Re: 2 bugs
« on: 2019 March 27 10:47:40 »
Maybe all I needed was a little motivation? Anyway, I double-clicked the header and a down arrow appeared in the field I clicked, and the boundaries became movable...Sorry for crying 'Wolf'!

I have another request for a future version. Some form of a Highlight/Shadow/Clarity tool...are these part of a "pyramid scheme"???

Alex

5
Bug Reports / 2 bugs
« on: 2019 March 26 13:58:48 »
1) Cannot slide field dividers to make more room for folder and file names in dialogs of the type shown in the attached--which are not the standard Windows dialogs
2) I new SubframeSelector, if a criterion is modified for star recognition, the re-measure button just reads the cache (unless it is unchecked). I cannot conceive a case where someone would change criteria on the form not want clicking the Measure button to do the new measurements regardless of whether the cache checkbox is checked or not.

Running latest PI, Windows 10pro up to date.

Alex

6
General / Re: Error message using Batch Preprocessing
« on: 2019 March 06 14:01:40 »
If you are not using overscan (generally, most imagers do not), click the Bias tab at the top and uncheck the "Apply" checkbox in the Overscan box.

If you are using overscan, then the values you specified must be incorrect/inconsistent.

Alex

7
General / Re: MAD and Average Absolute Deviation
« on: 2019 February 26 08:46:16 »
You are correct...we statistical types (my career) use MAD most often for a deviation from the median.

AlexW

8
I have written a new, logical, rigorous, flexible, and user friendly--Excel spreadsheet that makes generating subframe-weighting equations (for use within SubframeSelector).

Here is the link to a zipped folder that contains the spreadsheet and the instructions: https://www.dropbox.com/s/hxjz7pdq483zqfe/SWT0301.zip?dl=0

The reason to use the SubframeSelector (SS) is not just accept/reject subs, but to assign rational weights to each frame. This is an important operation, and if you do not use SS, you should learn to do so. The idea of a rational weight scheme requires a way to evaluate variables that make a subframe better or worse. Within SS the facilities for evaluating subs is improved over the previous version, but still it is rather minimal and not very interactive. Because of this, so folks have written Excel spreadsheets to help. I am among those folks. Furthermore, as far as I know, at this time mine is the only one that runs on the new version of SS.

If you've used PixInsights SubframeSelector Script before, then you probably notice there is another version now that is under Procedures. It runs much faster and uses updated algorithms for FWHM, star identification, .... , and has 3 windows. It also is now programmed (the weighting equation) using JavaScript.


Alex Woronow




9
M42 is a prime (and rare) example of an astronomical target whose brightness range is greater than the dynamic range covered by our cameras. The best images of M42 require a short and a long (relative, speaking) to cover all that range. Then the HDR capabilities in PI are used to blend the two separate stacks together.

Alex

10
Gerrit,

It works for me. I tried it on a fully processed image from a grayscale camera (RGBHS). It added color to the biggest brightest stars (and to some quite small, but, presumably, bright stars). The effect was to dull the stars a bit, but I think that can be remediated without much difficulty.

Thanks for a nice addition to the tool set.

Alex

BTW, I often use Repair HSV Separation to good effect, but this is faster and does the job well.

11
Would be nice! Could do a crop on all the images in a ImageContainer and analyze those then and manually transfer learnings to the full frames. OUCH!

Alex

12
New Scripts and Modules / Re: Debug Environment for Scripts?
« on: 2019 February 02 05:32:34 »
I agree with Mr. OldSkyEyes. I'm trying to write a small script, and am neither familiar with the PI library, nor with JavaScript. (I' bought 2 books on the latter.) Other than copying code from other scripts and hoping they are compatible, I'm at a loss for how to efficiently get to the end game. A rich-featured debugger would be a real head start.

Alex

13
I have a process container that, as the first process, has a pixelmath process that creates a new image. I want subsequent processes to act on that new image. However, the subsequent processes act on the parent of the new image instead.
If I click the container processes one at at time, then the pixelmath's new image is active as the next procedure executes, and as expected, acts on that new image.
Is there some reason that the process container does not work the same way? Is there a coercion I can use to make it do what I need?

Thanks, Alex

14
Bug Reports / Re: SubframeSelector does not handel repaired 'nan'
« on: 2019 January 08 07:16:26 »
I guess I was not entirely clear. The 'nan' is written by the program when my equation is in error. After it is written into the Weight column, the problem arises that the program appears to try to read the field before calculating an new equation, and throws the error I reported.
The only field I change is the Expression.

Alex

15
Bug Reports / SubframeSelector does not handel repaired 'nan'
« on: 2019 January 08 06:50:53 »
I entered an equation that cause the all the weights to become 'nan'. Repairing the equation (setting it to 1-.5) and pressing the right arrow in the Expression window then causes the console to report "*** Error [001]: ReferenceError: nan is not defined" and no execution." Clearing the measurement table and remeasuring does not clear the nan weights, and the same error persists.
Even clearing the Measurements Table and the subframes, reload and remeasuring, the nan is still there (Cached?).
And, even exiting the procedure and coming back in, everything is restored, including the nan's.

Only by clearing all three windows, exiting the procedure and coming back in, can one remove the dreaded 'nan'.

Alex

Pages: [1] 2 3 ... 15