PixInsight Forum (historical)
Software Development => New Scripts and Modules => Topic started by: NKV on 2012 March 11 01:50:13
-
Hello everyone.
There are many topics about Comet preprocessing. click, (http://pixinsight.com/forum/index.php?topic=3367) click, (http://pixinsight.com/forum/index.php?topic=2008.15) click (http://pixinsight.com/forum/index.php?topic=3311.0)... but I don't found any useful tools for automation.
So, I start writing the CometAlignment modul.
Please check Tutorial there (http://pixinsight.com/forum/index.php?topic=8161.0).
Best regards,
Nikolay.
Version history:
v.1.0.0.0002
+ Support for RAW images. Note: while original MetaData unaccessible inside PI, I use FileLastModificationDate.
For RAW images( which impossible to modify ) FileLastModificationDate equal to DATE-OBS + Exposure and equal to time when exposure ended. So FileLastModificationDate can be used if DATE-OBS FitKeyword and MetaData unavailable.
v.1.0.0.0003 Minor code improvements.
v.1.0.0.0004 BugFix: module skip all images if first Image disabled. fixed.
v.1.0.1.0001 + pixels/hour core movement parameter. BugFix: interpolation method was ignored - fixed.
v.1.0.2.0001 BugFix: process icon problem(impossible to load process icon) - fixed.
v.1.0.3.0001 PI 1.8 PCL2.0.
v.1.0.4.0001 BugFix: support for date format 'yyyy-mm-dd' and 'yyyy-mm-ddTHH:MM:SS'
v.1.2.0.0001 + Align CometIntegration to every target and subtract. with LinearFit and Normalization options.
v.1.2.1.0001 + Subtract StarIntegration from every target, and align result to Comet position.
v.1.2.2.0001 BugFix: support for Iris Software date format "DD/MM/YYYY" added.
Sources code for PI 1.8.3 PCL2.00.13.0689
v.1.2.2.0001 (http://endor.uv.es/files/data/public/f355e8.php?lang=en)
Bin v.1.2.2.0001
Lunux x64 (http://endor.uv.es/files/data/public/cfc8ee.php?lang=en)
Win x64 (http://endor.uv.es/files/data/public/7a01f1.php?lang=en)
-
Great work !
Can't wait to test oder use it.
-
I am sitting here and looking at my comet frames from last night... and waiting for your script :)
No pressure ;)
-
Hi Nikolay,
nice work.
Unfortunately, Canon DSLR users don't have the DATE-OBS keyword in their fits files, as they seem not to be
implemented during RAW->Fits conversion.
I don't know if you are calculating with the fits header data (except maybe to get the files in the right order).
As a proposal : If there is no DATE-OBS header in the fits files, could you simply use the order of files, as the user
entered it ? DSLR Users also do a straight forward exposure sequence of 60 - 100 Files (and this is quite "crispy",
to enter the fitsheader by hand for each single frame or to spend lots of money for doing this with another application) ?
Just an idea ....
Christoph
-
Unfortunately, Canon DSLR users don't have the DATE-OBS keyword in their fits files, as they seem not to be
implemented during RAW->Fits conversion.
Christoph, it's not my problem... it's RAW->Fits problem, so it's Juan problem ;)
Push Juan please. I push him every time when i do some thing in other astronomical software.
For example you can convert your RAW to Fits in MaximDL. Juan!!! Attention!!! :D
-
Any plans to release it for Linux?
-
Any plans to release it for Linux?
Added. See first post.
PS Juan, thank you for Endor PixInsight File Server (http://pixinsight.com/forum/index.php?topic=4039.0)
-
v.1.0.0.0002
+ Support for RAW images. Note: while original MetaData unaccessible inside PI, I use FileLastModificationDate.
For RAW images( which impossible to modify ) FileLastModificationDate equal to DATE-OBS + Exposure and equal to time when exposure ended. So FileLastModificationDate can be used if DATE-OBS FitKeyword and MetaData unavailable.
-
Hi all,
so it's Juan problem
Problem? did I hear problem? Problem solved! :)
FileLastModificationDate equal to DATE-OBS + Exposure
Nice trick ;) The latest version of the DSLR_RAW module, which I have just released as an update, simulates DATE-OBS keywords (along with a few more ones), so this is no longer needed. Sorry for taking so long to solve this issue. Your module, as usual, is absolutely terrific.
-
The latest version of the DSLR_RAW module, which I have just released as an update, simulates DATE-OBS keywords (along with a few more ones), so this is no longer needed.
Cool! Thank you. OK, i will remove the feature.
In any case, the module is checked for FitKeyword. Therefore, the module will work with any version of DSLR_RAW. 8)
-
I´ve installed the module in C:\Archivos de programa\PixInsight\bin and reboot the pc, but when I open Pixinsight isn´t appear the "comet alignment" with other modules, like GradientMergeMosaic. Any help?
-
I´ve installed the module in C:\Archivos de programa\PixInsight\bin and reboot the pc, but when I open Pixinsight isn´t appear the "comet alignment" with other modules, like GradientMergeMosaic. Any help?
Go to Process>Modules>Install Modules...> and Search in .../PixInsight/bin
Saludos. Alejandro.
-
Thank you very much, Alejandro. Now I´ve installed the module. I´ll test it.
-
I ask you, because I used StarDetection method from DynamicPSF module.
Can I open source code or not?
If you have used only the star detection routine, then yes, you can open it. In fact I'll probably open this and other parts of StarAlignment/DynamicPSF soon.
Thank you! I added link to sources in first post.
Best regards,
Nikolay.
-
Excellent module! Thank you.
Here is my first comet image ever
Garradd C/2009 P1
(http://www.astropics.eu/wp-content/uploads/2012/04/L90-113-121-P1_c_ca.gif)
Taken from city apartment, trough skyline window. 13x90 sec.
-
Hi Nikolay,
Thanks a lot for the script, it works as expected, and really easy and straightforward to use!
Very simple - but it saves hours of manual alignment! Great job! :)
***
Garradd as of Aug 25, 2011
-
v.1.0.0.0004 BugFix: module skip all images if first Image disabled. fixed.
-
Hi Nikolay. My latest try to register images of Holmes was unsuccessfull. My set contains set of short exposures with core and set of long exposures with faint large coma. This second set also contains saturated core and I cannot register these images. Solution for me is to take one short exposure after the set of long exposures. Another possible sollution is to allow user enter velocities dx and dy obtained from other set of images. I think, that images taken in one or two hour have no problem with different speed.
Can you please update your module to allow manual entry for these two parameters? Thank you very much.
Tomáš
-
saturated core
Tomáš, try to use CTRL key ;)
-
Hi Nikolay.
I know this feature, but where is the center of my saturated core? This is extremely stretched image, where I want to find some feature to register. The central area was totaly saturated. I don't know, where to click. :-)
Tomáš
-
I don't know, where to click.
How I can help you to calculate the center of saturated core ?
Tomáš, if you know core center , you can enter the x,y manually.
-
You don't need to know center of the saturated area. From previous set of images I know velocities in x and y axes (for example 3.5684px/hour and -1.12345px/hour). If I know these values, it is possible to realign images. I did this proces in Iris, but it is uncomfortable to switch tool for this small task.
-
I know velocities in x and y axes (for example 3.5684px/hour and -1.12345px/hour). If I know these values, it is possible to realign images.
I understood! I will add it.
-
This is product of my work with Comet Alignment module. It is difficult for me to process this image like HDR, but this is question to other forum thread. Alignment was done well. Thank you for your tool.
-
v.1.0.1.0001 + comet velocity pixels/hour. BugFix: interpolation method was ignored - fixed.
-
Hi Nikolay.
This is unbelievable. You are faster than Speedy Gonzales (fastest mouse in Mexico) :o . Many thanks.
Tomáš
-
Welcome!
-
Added binaries for PI 1.8 (http://pixinsight.com/forum/index.php?topic=3980.msg27348#msg27348)
-
Hello Nicolay
I did a try on this module, and shure I did something wrong.
I marked the comet in the first and last Image, but after processing, in the images in between the comet was not aligned correcty.
I then selected arbitrary images by double click on the module and the comet was not aligned there also.
(attached image of first, arbitrary in the middle and last image)
Regards
Geert
-
Please share with me first, last and one of intermediate image(which not aligned).
-
Hello Nicolay
I saved the files in rapidshare
Here are the links:
https://rapidshare.com/files/4203171076/debayer_garradd-099L_c_r.fit;
https://rapidshare.com/files/1398331872/debayer_garradd-078L_c_r.fit;
https://rapidshare.com/files/2455703676/debayer_garradd-046L_c_r.fit;
They are calibrated, registered and debayerd
Regards
Geert
-
They are calibrated, registered and debayerd
Hi,
Problem in ImageRegistration. Blink the images to see that image #099 is not registered to other two.
Best regards,
Nikolay.
-
Thanks Nikolay
I removed #99 from the process and it worked great.
Regards
Geert
-
I removed #99 from the process and it worked great.
:)
If you have any idea for improvement the module - welcome.
-
Hello Nikolay
I have some trouble with the module.
When I save a project containing the module (process icon) I can not load the project anymore because it crashes PI.
I tried wit a project containing only this module as process icon.
Can you please verify this?
Regards
Geert
-
When I save a project containing the module (process icon) I can not load the project anymore because it crashes PI.
Bug fixed.
v.1.0.2.0001 BugFix: process icon problem(impossible to load process icon) - fixed.
-
That worked ok, even with my previously saved project.
Thanks
Geert
-
Hi All, I am a newbie to PixInsight but I have collected about 20-odd images of comet P168 last night and am trying to process the images using the Comet Alignment Module. I note that it uses the Date-Obs field which is in the original image file, but as I have single shot colour QHY-8 when I debayer the images, the Date-Obs field plus all the other FITS camera data appears to be lost in the debayered header files. Have I missed something? Any suggestions? Cheers Grant
-
when I debayer the images, the Date-Obs field plus all the other FITS camera data appears to be lost
There are problem in BatchDeBayer Script, which don't preserve FitsKeywords.
Use Debayer Module + Image Container. ;) That combination doing same, but preserve FitsKeywords.
-
It seems I am a little slow. I have tried the CometAlignment tool and it seems to see the comet fine (I can select the comet in the first and last image, I can see the green circle move as I open other images as it should). I then select an output directory and click apply. It makes a series of fit files. If I open those fit files in BatchPreprocessing it does not seem to do any different than the raw files before using CometAlignment.
I know I am doing something stupid, can you point me in the right direction?
Allan
-
I have tried the CometAlignment tool and it seems to see the comet fine (I can select the comet in the first and last image, I can see the green circle move as I open other images as it should). I then select an output directory and click apply. It makes a series of fit files. If I open those fit files in BatchPreprocessing it does not seem to do any different than the raw files before using CometAlignment.
Please check ( Menu>File>FitsHeader ) are really images was processed by Comet Alignment module. Open one image and check history in FitsHeader. Look my print screen for example.
-
Hello Nicolay,
thanks for the great Comet Script. It works well! :)
What do you think is the best integration algoritm after registration! I used Winzorized Sigma but I;m looking forward to your answer!
Greetings from Germany
Karsten
-
best integration algoritm
Sorry, I have no idea.
-
What do you think is the best integration algoritm after registration! I used Winzorized Sigma but I;m looking forward to your answer!
I think there are some hints in the documentation. I cannot check this right now... No access to PI here...
-
See http://pixinsight.com/doc/tools/ImageIntegration/ImageIntegration.html#usage_004
-
v1.0.3 for PI 1.8 RC1 Linux64
-
v1.0.3 for PI 1.7 MacOSX x86_64
http://endor.uv.es//data/public/adc4c121f0951f1a5b78286e97e9473e.php (http://endor.uv.es//data/public/adc4c121f0951f1a5b78286e97e9473e.php)
i'll build for 1.8 when i get my new PCL environment established
-
Bin for PI 1.8 RC3:
Linux x64
Win x32
Win x64
-
Hi :)
I'm trying to download the linux 64bits version, for 1.7, but the link doesn't work (well, not a single link to endor here works...). It is my problem, or do you experience the same?
-
Hi Carlos. This is general problem of the links. I got the same error.
-
Something wrong in repository.
All links updated.
-
Hi!
the links are ok now, but for win 32bit and win64bit comes the CosmeticCorrection tool.
Click on the image to download
CosmeticCorrection-pxm_PI1.8RC3_Win64_1.0.3.0001.rar
to your hard drive
Best regards.
Herbert, Austria
-
Hi Herbert - if you haven't already done so, just download the module. When you unzip it, it is indeed the CometAlignment-pxm.dll you're looking for.
Unzip the file, then move or copy it to the C:/Program Files/PixInsight/bin/ subdirectory, then start PI.
Open the Process menu, and at the bottom you'll see "Modules". Choose "Install Modules...". A dialog box pops up with no new modules in it. Press "Search" in bottom left corner of dialog, and the new module will be identified as "new" and added to the selection list. Select it from the list, and hit "Install". The Process Console will do its thing and show the following when done:
Module Id ............ CometAlignment
Version .............. 01.00.03.0001
Language ............. eng: English
Development status ... <* Unspecified *> (release)
Release date ......... 2012/12/25
Author ............... Nikolay Volkov
Copyright ............ Copyright (c) 2012 Nikolay Volkov
Trade marks .......... PixInsight
Original file name ... CometAlignment-pxm.dll
API version .......... 138
Module Description:
CometAlignment module
You're done!
Rod
-
Bin updated for PI 1.8 RC5:
Linux x64
Win x32
Win x64
Best regards,
Nikolay.
-
Hello Nik
I can not find the file CometAlignment-pxm.dll,
in zip files i find it kind CPP and H, not pxm.dll
thanks.
Giorgio
-
I can not find the file CometAlignment-pxm.dll,
in zip files i find it kind CPP and H, not pxm.dll
Giorgio, you downloaded C++ Sources code package.
Try to download Bin for PI.
Best regards,
Nikolay.
-
Thank you Nikolay
everything works
Giorgio. :)
-
Some program generate FITS file with different DATE-OBS format. See doc (http://www.saao.ac.za/~lab/fits/fits/node3.html)
So, the module crash if DATE-OBS deffer from format 'yyyy-mm-ddThh:mm:ss.sss'
v1.0.4.1 BugFix. added support for short format (DATE-OBS + TIME-OBS)
-
Hi, i can't load images in Coment aligment tool..., it's don't load, nothing . I use 1.8 RC7
Plase i need help.
Thanks
Rafael
-
Hi, i can't load images in Coment aligment tool..., it's don't load, nothing . I use 1.8 RC7
Plase i need help.
Impossible without your files...
Give me link where is i can download your files.
And which OS you use?
-
Hi,
After processing C/2014Q2(Lovejoy) and getting the result
StarRegistredIntegration :
(http://www.astronomy.ru/forum/index.php?action=dlattach;topic=121466.0;attach=683001;image) (http://www.astronomy.ru/forum/index.php?action=dlattach;topic=121466.0;attach=683000;image)
CometRegistredIntegration:
(http://www.astronomy.ru/forum/index.php?action=dlattach;topic=121466.0;attach=683005;image) (http://www.astronomy.ru/forum/index.php?action=dlattach;topic=121466.0;attach=683004;image)
I found very long Comet trail in StarRegistredIntegration image and impossible to remove it completely in MixelMach via simple subtracting CometRegistredIntegration.
So, what if subtract CometRegistredIntegration from every StarRegistred, and after integrate it in to Star image without Comet?
Of course it's possible only in CometAlignment module, because we must slightly move CometRegistredIntegration according real comet position in every StarRegistred image.
I think it's good idea.
PS maybe LinearFit adaptation as option will added too, but i not sure... because ABE can do all at once via ImageContainer.
-
v.1.2.0.0001 New: Subtract Comet integration from every Targets. with LinearFit and Normalization options.
video:
Star aligned (https://drive.google.com/file/d/0B6_GVJXOaWIVM0VkeDVCMldIYjQ/view?usp=sharing)
Star aligned minus Coma Integration (https://drive.google.com/file/d/0B6_GVJXOaWIVS0xpajVzSlNSTnc/view?usp=sharing)
Final result:
-
Great!
Nikolay, can you help me understand better a few point of the script:
-the OBS-date is a mandatory field for the script to align the frames on the comet nucleous?
-does the script work if the images were guided on the comet nucleus? (we can set precise comet track rate, star would be a little trailed in the frames)
Thanks a lot
Andrea
PS: the script is awesome
-
Hi, Andrea.
-the OBS-date is a mandatory field for the script to align the frames on the comet nucleous?
Yes.
The module required StarAligned images with DATE-OBS in FITS Keywords.
-does the script work if the images were guided on the comet nucleus?
Yes. Just align images to stars. And after that, align comet.
PS To avoid double alignment, you can use DynamicAlignment module. Or i can write new tool... maybe in future
-
Nikolay, I'm trying to get my head around the workflow using version 1.2.
Do I do this:
* Align light frames on the stars
* Use CometAlign on these star aligned light frames
* Integrate the comet aligned frames
* Use this "comet" Integration image and run CometAlign again, but this time using the subtract option which will remove the comet from each star aligned light frame?
* Now integrate these comet subtracted frames to get a star only Integration?
* Finally recombine the comet only and star only integrations?
Thanks, Craig
-
Hi Craig. I think that is the correct procedure.
Nikolay, this is an excellent improvement, Thanksss!
Alejandro.
-
Hi Craig. I think that is the correct procedure.
Nikolay, this is an excellent improvement, Thanksss!
Yes, you are understand me perfectly.
PS next version coming. new option: subtract StarIntegratedImage from every StarRegistred and align to comet position.
I think, if StarIntegratedImage made with strong rejection and cleared from comet core manually, it's good idea!
Subtract Stars from every sources image, align to comet and integrate to OnlyCometImage. 8)
PSS released v.1.2.1.0001 Subtract StarIntegration from every target, and align result to Comet position.
-
I am new to PixInsight and am having trouble figuring out from where to download this newer script. The only one I found was a .rar file and I didn't know what to do with it. I have a version of the comet alignment script but I do not know if it is the latest - I doubt it. Any advice would be appreciated.
Larry
-
I am new to PixInsight and am having trouble figuring out from where to download this newer script. The only one I found was a .rar file and I didn't know what to do with it. I have a version of the comet alignment script but I do not know if it is the latest - I doubt it. Any advice would be appreciated.
Larry
1) It's not Script. It's Module.
2) http://en.wikipedia.org/wiki/RAR
3) your OS name? If Windows x64 and latest PixInsight extract file from .rar file to PixInsight/bit folder.
4) Run PixInsight
Enjoy.
-
NKV, thanks. With your response I was finally able to figure it out.
Larry
-
v.1.2.2.0001 BugFix: support for Iris Software date format "DD/MM/YYYY" added.
-
CometAlignment Tutorial. (http://pixinsight.com/forum/index.php?topic=8161)
-
Great!
Nikolay, one more question:
If I manually put the comet speed, does this "jump" the calculation based on obs-date field?
Many thanks,
Andrea
-
If I manually put the comet speed, does this "jump" the calculation based on obs-date field?
Yes, of course.
You can select where at comet in first image and set comet speed(pixels per hour). Module will calculate according obs-date the position of comet for all other images.
-
Ok,
So in this case obs-date is used just to sequence the files?
The exact time is not used because the speed is already available.
I have some tiff files.
I converted them to fits and set a dummy obs- date in each of them, taking care of the real acquisition number.
If I put the comet rate at that time ( from Skyx), it should work, right?
Thanks again,
Andrea
-
Ok,
So in this case obs-date is used just to sequence the files?
The exact time is not used because the speed is already available.
I have some tiff files.
I converted them to fits and set a dummy obs- date in each of them, taking care of the real acquisition number.
If I put the comet rate at that time ( from Skyx), it should work, right?
Thanks again,
Andrea
No ano No.
obs-date required to calculate real time between shoots.
For example. You can set comet speed 60pixel per hour. You can take one shoot per minute. So the comet must move 1pixel from shoot to shoot.
Bat, what happen if you stop shooting in middle of the night for refocusing. How to calculate time between that shoots? Who can warranty that images taken exactly one per 60.00000000000 seconds, not 60.1 ?
So obs-date must be present. You can create obs-date KeyWord in many ways. From EXIF of FileSystem(DateOfFileWritten). Anyway, obs-date should represent one of time event type (start, stop, middle, create,...). And should be stable.
-
Hi everybody,
I have just released an update with version 1.2.2.65 of the CometAlignment module for all platforms.
It is the same version Nikolay has published here with the following additions:
* New output file extension parameter (.xisf by default).
* New input and output hints parameters.
* The interface has been cleaned up and reorganized to meet PixInsight tool GUI guidelines.
Nikolay, congratulations on an excellent work!
PS: I like the icon! ;)
-
thanks Nikolay, I think I understand now..
Andrea
-
Nicolay & Juan
Great. Works like a charm.
Thanks a lot!
-
The problem:
I have a stack of 186 sub-images of comet 252P that was moving very fast.
The images are 6016x4016 pixels.
In image #1 the comet is at 3140,1085 and in #186 it is at 2665,2555.
That is, the comet has moved -475 pixels in X direction and 1470 in y direction. As such, I would have liked the resultant stacked image to be larger than the individual subs at (6016+475)x(4016x1470) with the center of the comet at (2665-475/2),(1085+1470/2). I would then crop the center (6016x4016) of the image as necessary and re-combine it with the star aligned image.
Alas, I end up with a stacked comet image that is the same dimensions as the sub, the comet in the location of image #1 and all of those extra pixels above the comet in the later subs cropped away by the tool.
Attached is an example of one of the subs that has been re-aligned with significant loss of information.
Does anyone know how I can force the tool (or another tool) to align the subs without cropping the information in the subs (ie. by enlarging the canvas to allow the alignment to proceed whilst retaining all of the information in the subs).
-
Here are more image that show the problem ...
1. star alignment showing incomplete removal of comet path through the centre of the image.
2. resultant comet aligned image
3. simulation of how the final image might look with the current comet aligned image (what I don't want); and
4. simulation of where I want the comet to appear in the final image (with all the information above the comet retained (which currently is not))
Any ideas on how I can achieve it would be greatly appreciated.
Cheers
mike
-
Hi Mike, if I remember well you can select the image that will determine the final position of the comet, with the blue arrow (double click in the # section). This (http://pixinsight.com.ar/en/info/processing-examples/38/lovejoy-comet.html) processing example may help.
Saludos,
Alejandro.
-
Does anyone know how I can force the tool (or another tool) to align the subs without cropping the information in the subs (ie. by enlarging the canvas to allow the alignment to proceed whilst retaining all of the information in the subs).
ImageContainer + Crop 200% to create black spaces around read pixels. ;)
-
Hi Mike, if I remember well you can select the image that will determine the final position of the comet, with the blue arrow (double click in the # section). This (http://pixinsight.com.ar/en/info/processing-examples/38/lovejoy-comet.html) processing example may help.
Saludos,
Alejandro.
Thanks Alejandro, I did not know that. I've tried it and it does re-align the images to centre on the selected image. Unfortunately though it does not enlarge the canvas to accommodate all of the subs. That is, the problem remains that the individual comet aligned subs are all still the original dimensions with the image content shifted (and the remainder filled with black) so I still miss out on a lot of data.
Cheers
Mike
-
Does anyone know how I can force the tool (or another tool) to align the subs without cropping the information in the subs (ie. by enlarging the canvas to allow the alignment to proceed whilst retaining all of the information in the subs).
ImageContainer + Crop 200% to create black spaces around read pixels. ;)
Thanks for that, yes the Crop tool worked :)
In case anyone else is wondering about the details...
The Crop tool can also be used to increase the canvas size around the image. The Image Container tool was also new to me and allows you to collect together all the images that you want before applying a tool to the whole collection as a single action.
Cheers
Mike
-
Hi,
I have a question on the Subctract operand image functionality.
this is what I did:
-star align my images
-crop my images
-run comet align and integrate a Comet Aligned image (very good)
-run again comet align module on star aligned (and cropped) frames, subtracting comet aligned image at each step.
The resulting files are not good bacause the operation digs to much in the data and the background is lost.
I have tried to replicate the operation in pixelmath and it seems that a "rescale" option can cure the problem.
is this step already included in the processing?
I couldn't check the final integrated star only image because re-aligning the comet image to star manually is painful.
Thank you very much,
Andrea
-
Hello.
I noted a little GUI problem in the CometAlignment process: when loading the file list with long file names, the list windows is missing the Horizontal Scroll bar and the file names are going "under" the right buttons and they also has their labels truncated (see screen shot attached).
Checking into the code I noted a comment that suggest that behavior is required.
I'm wandering why...
Any idea?