www.pixinsight.com
Welcome,
Guest
. Please
login
or
register
.
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
This forum is closed since 5 March 2020
PixInsight Forum is now available at:
https://pixinsight.com/forum/
News:
Home
Help
Search
Login
Register
PixInsight Forum (historical)
»
PixInsight
»
Bug Reports
»
An other possible Bug in BatchPreprocessing script
« previous
next »
Print
Pages: [
1
]
Author
Topic: An other possible Bug in BatchPreprocessing script (Read 3038 times)
vesa_k
Newcomer
Posts: 6
An other possible Bug in BatchPreprocessing script
«
on:
2014 December 23 09:03:36 »
When you use BatchPreprocessing script for CFA images it will use Debayer process.
For some reason all images are missing DATE-OBS information after Debayer process.
If you run just DeBayer prosess outside this script there will be that information in FITSHeader.
You need this FITSHeader info it you like to use for example CometAlignment process.
BatcPreprocessing script is good also when you will calibrate Comet images but at this time you cannot use CometAlignment process after calibration.
Vesa
Logged
"Logic will get you from A to B. Imagination will take you everywhere" Albert Einstein
Juan Conejero
PTeam Member
PixInsight Jedi Grand Master
Posts: 7111
Re: An other possible Bug in BatchPreprocessing script
«
Reply #1 on:
2014 December 23 12:47:09 »
Hi Vesa,
I have just released an update that should fix this bug - please confirm. Sorry for the inconvenience.
Logged
Juan Conejero
PixInsight Development Team
http://pixinsight.com/
vesa_k
Newcomer
Posts: 6
Re: An other possible Bug in BatchPreprocessing script
«
Reply #2 on:
2014 December 23 13:15:21 »
Hi Juan,
Thank you. It looks fine, everything is ok now except I think you should start your Christmas time.
Merry Christmas
Feliz Navidad
Greetings from La Palma
Vesa
Logged
"Logic will get you from A to B. Imagination will take you everywhere" Albert Einstein
Print
Pages: [
1
]
« previous
next »
PixInsight Forum (historical)
»
PixInsight
»
Bug Reports
»
An other possible Bug in BatchPreprocessing script