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

Pages: [1] 2
General / Re: Juan and Vicente
« on: 2018 September 15 13:33:19 »
Ive been curious about what is happening on the back end. Glad to see things are going back into motion.

Wish List / Read Write speeds
« on: 2018 July 19 10:39:01 »
Im not sure if there is a bottleneck somewhere in my system but I would really like Pi to push my system at least to 75% when it is performing a process.  It does a good job of this during image registration and integration but when I do a batch file conversion for instance or an image container/process container batch process on lets say 200 dslr images, I find that Pixinisght is not pushing my system very hard and it seems to take longer than necessary to complete an operation. 

For example today I converted a big stack of RGB images to Lum and my 960evo m.2 ssd has very high read wrote speeds, but Pi was utlizing less than 25% of the write speed, the cpu and ram were not maxed out.  I dont see a bottle neck anywhere, is there something in the software that limits read/writespeeds?  Could this be user adjusted in Windows?

Announcements / Re: New RAW Module - Ready for Testing
« on: 2018 July 17 08:59:54 »
Im not sure what is going on with Pixinsight lately, it seems like there have not been any updates in months.

I have a serious issue with this module.  First of all, I have no way to uninstall it from Pi, I have uninstalled the program itself but upon re installation the new raw module is still loaded in the program.  The raw module works fine for a period of time and then mysteriously disappears from the format explore window.  Once this happens I can no longer open ANY dslr files. It completely brickwalls my workflow and I am no longer able to use Pixinisght to open and process my astrophotography.

General / Re: Combining Images from 2 Different cameras
« on: 2018 May 26 21:31:09 »
Ive tried that a few times but the ram maxes out and the computer will just computer for hours.  It never actually registers the image.  Ive tried reducing the magnitude of the stars of the synthetic field but it seems if I go below mag 10, I get an error in star alignment and it wont work.  I think it might be because I am under sampling, but even so I select the fwhm of my stars and have never been able to get it to work.  It would be alot easier if it did though!

General / Re: Help! Can no longer open .CR2 in Pi
« on: 2018 May 26 20:36:39 »
Anything?  This is killing me Im dead in the water right now, been waiting all week to process this data. 

Yea I also have noticed that it takes a lot longer to integrate big datasets.  Its pretty disappointing, I went with a 5960x just to run big data in Pi.

Off-topic / Re: problem with DSLR image
« on: 2018 May 26 20:26:25 »
When you have a data set this large you can try creating a custom registration frame. 

You have 487 light frames so go through each night and pick 3 subs at the beginning middle and end of the night.  You then use the mosaic merge tool in Star Alignment to merge these together.  I prefer to use the frame adaptation setting for this.  Alternatively you can use register/ union-separate on each sub and use dynamic alignment to combine them.
When you have a mosaic image created from each night you can combine these in star alignment and then either register them into an image or again use mosaic merge in star alignment or dynamic alignment to combine all 3.  The final goal here is to have a master reference frame that has not bee cropped to 1 image.  It should show all of the different subtle offset you had from re framing and dithering each night.  You will register all of your images to this master frame and then integrate them in image integration. 

I highly suggest using the linear fit clipping rejection algorithm along with large scale pixel rejection. I probably sound like a broken record because of the past few posts, but use a very small ROI box on an opened image and run image integration.  See if you are able to notice a difference in your back ground.  After an integration the high clipped pixel map will be filled with hot pixels and the low clipping map will contain the overlapping edges of your frames, you can fine tune this.  Large scale pixel rejection will also play a role in how your edges overlap, you cna adjust these to taste as well depending on how much signal loss or gain may have occured in an overlapping area.  Its good to crank up the buffer and stack size when you are using an ROI, assuming you have enough ram and a fast processor, be sure to set them back to normal when you are happy with the results and ready to stack everything at once.  I suggest you sepnd a long time with ROI in different areas of an image before you finally integrate. 

Also, when you have the final integrated image, are you linear fitting the data first? 
For dslr especially with this large of an integration you should be splitting the channels, running statistics on each channel at 14bit with normalization off to find the lowest median
now you use the linear fit tool to fit the lowest median channel to the other two channels, and finally recombine the channels using recombination.
Now you can do background neutralization with a small sampled area and determine if further gradient removal is needed.  I have much better results with ABE than DBE with thick ifn areas, For me the best solution is to try and have ABE apply very subtle improvements to any gradients so that it does not over correct and darken areas where it suspects a flaw.  When you have a good subtle setting dialed in you can run multiple iterations of abe until you have the data where it should be.  In your example with excessive noise issues, I seem to notice that abe does this alot, it just seems to be the nature of this tool.  I try to avoid using background gradient removal if at all possible. 

I shot this region using DSLR about a year ago using the aforementioned technique.

General / Re: Black artefacts in some star centers.
« on: 2018 May 26 20:05:37 »
I have not used the drizzle feature.

Can you use an roi over the stars during integration and check how the percentile/sigma/linear/high settings are affecting your stars at their given setting?  Sometimes I have issues with hotpixels not being rejected if the settings are to high.

Additionally, the only time I can remember coring out my stars was when I used cosmetic correction too aggressively, I realized after integrating that alot of my fainter undersampled stars had been hollowed out, while in my sample window I had not created any damage. 

General / Re: Combining Images from 2 Different cameras
« on: 2018 May 26 19:51:25 »
I hope I'm understanding your situation correctly.  I have been combining data from 2 and 3 cameras at once for about 6 months now, I wish I had seen this post earlier and hopefully this might still be of some use. 

First I create a master registration frame from each camera. 
I pick a few of the best images from each camera and stack these to create a reference frame.

Next I use Star Alignment and select the (register/union - separate) function with (Frame Adaptation) checked. 
This will fit each image to the reference, you may want the reference to contain the highest snr.

Next you use Dynamic Alignment to merge the registered union separate images.  Select image 1 and 2 then select stars in the corners and the center of the image.  You may need to manually train the second image on the first 2 stars.  Run the tool to get a master mosaic.
If there are more than 2 images then you will need to add each consecutive image to the mosaic created by the first 2 images.

Now take your master mosaic and use the registration tool again and re register all of your data to this.  Be sure to keep the Frame Adaptation icon checked.

Finally Integrated everything, I prefer to use linear fits and large scale pixel rejection.  Its a good idea to spend time fine tuning with the roi tool over a small area at this step, especially if you are using several hundred subs.  I have found that this gives me a very clean stack with smooth edge transitions.  If I image over 2 or 3 nights with a dual camera setup, this technique helps out alot.   

Have you tried creating an roi over one of the areas and fine tuning the structure rejection settings in image integration? 

General / Help! Can no longer open .CR2 in Pi
« on: 2018 May 26 19:28:07 »
Im not sure what has happened but I cannot get Pi to see .Cr2 files any longer.  It is not an option in the files list when I go to open them either.
It was working fine up until about an hour ago, Im not sure what is wrong.

I recently installed the Raw file format support module version

Package type : Module
File name    :
Release date : 2018-02-05 00:00:00
Install date : 2018-05-23 17:56:15
This update installs a development version of the new RAW file format support module for PixInsight 1.8.5. RAW implements digital camera raw format support based on the LibRaw open-source library. The new RAW module replaces the old DSLR_RAW module, which was based on the (now discontinued) dcraw program.
Copyright (c) 2003-2018 Pleiades Astrophoto S.L.

Announcements / Re: New RAW Module - Ready for Testing
« on: 2018 May 23 10:58:31 »
how can you fine tune fbdd?

Bug Reports / Image integration
« on: 2018 February 05 13:11:32 »
Hello, I am trying to integrate a stack of data and it keeps failing.  I am not sure what the proper way is to share this bug, if it is a bug.  2 days ago I registered the data with frame adaptation selected in image registration, there is a slight overlap in these two data sets.  Today I re registered all of the data without using frame adaptation to see how the integrated image would look by comparison.  For some reason the data will no longer integrate.  It does not matter if I try to use an ROI or the entire image, image integration crashes every time.  I am getting this message below. Let me know if I need to pull more info from anywhere else. 

A:/M81 and M82 master/t2i plus t5/IMG_1502_c_d_r.xisf
Loading image: w=5695 h=4038 n=3 RGB Float32
Computing image statistics:

* Waiting for running tasks to terminate...
*** Error:
*** Error: Unknown exception
<* failed *>

Preferences: Global context
1.018 ms

General / RAM Bottleneck Win10 Image integration
« on: 2018 January 16 20:51:19 »
I am working a large data set and I am troubled because I have a custom page file setup on one of my SSD's for when I run out of RAM, which is not working for some reason.   
I am using image integration right now and it appears that the ram is bottle necking, Pi has been integrating 450 dslr light frame subs now for 3 hours.   
I need to figure out what the optimal settings are for my machine in a win10 environment.  maybe I have something configured incorrectly?
My imaging equipment consists of multiple dslr's and I typically end up with large data sets, calibrated outputs approach 500gb.

Whenever this gets finished I would like to make sure I have everything optimized to handle workflows of this volume.
Can anyone offer me a suggestion on how to improve performance?  I did some some screen shots of the current bottlenecking status if they might help.


General / Re: Understanding Local Normalization Jargon
« on: 2017 November 28 21:17:30 »
Thanks, I guess I will try out both options.

Pages: [1] 2