Same way with the "Change keyword" popup menu. The only benifit would be that you could stack serveral image series in one stap. It will stack the files based on the object. There is an option to add the object name as round julian day. I could add an option to take the first 7 charactors of the filename. That would work if the filename is started with the object name.
Probably it is better to add the object name while converting the raws. That is more logical since the raws don't contain any info accept the filename. I will take the first 7 characters of the filename.
Clear skies, Han
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK. Don't change it. By default APT uses the object name as the folder into which the data files are placed.
Can I ask, what made you decide to write ASTAP and HNSKY when there are other solutions around. I am halfway through a rewrite of EQMOD/EQASCOM which I started because it is written in VB6 and is no longer being actively developed. I can see a day coming when it no longer functions.
The basics and UI are working, clunky in places but it passes (or did pass) the ASCOM platform tests. I now need to work out the more complicated bits like how to handle star alignment and guiding but I find it difficult to keep motivated and put in the time necessary. That is why I am so impressed by what you have done here.
Already done. I had a function to extract the object name from the file name. (double click on Ra in the viewer). So dowload again (version 0.9.362f) it will add an object name if it can find one in the file name.
I didn't realise EQACOM was writen in VB6. So will your project be a replacement for EQACOM? There is also a similar EQASCOM INDI version. I'm not familiar with VB. I know just enough to rewrite the ASCOM camera simulator for my "Sky simulator" :)
I use EQASCOM but not the modeling . With astrometric (plate) solving it not nessesary and I have to unlock the telescope to move around in my shed. So a simpler version would do for me.
HNSKY is an old project started in1997. ASTAP started 3 years ago. Why? Same reason why you and other people write freeware software I guess. Making something usefull can be fun. I didn't like the other stacking programs.
Han
Last edit: han.k 2020-05-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My initial intentions were that it would be available to replace EQASCOM if people wanted to stay with something that looked vaguely familiar. There is at least one other ASCOM Telescope controller that speaks Skywatcher under development that I am aware of but it is very different to EQASCOM.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It looks like Robert has been busy since I last looked so I'm going to give it a try. If it does everything I need I'll probably go with his and put Lunatic down to experience. His source code is a available and he's using the same developement stack as I am, C# .NET etc.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
sorry for asking, how did you decide to deal with object name? Will it be retrived from the filename also for FITS? I am currently using 0.9.361 on a Mac and the only working method is to use Change keyword in selected files.
Thank you
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version 0.9.362 will retrieve the object from the file name. It hasn't been compiled for the Mac. I will do it tonight. Please report any problem with it. Else use version 0.9.361
Clear skies, Han
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is astap expected to retrieve the object name from the file name and update the Object column in Images tab in the Stack window?
I tried loading the file and also analyzing it but the column is not updated.
Thank you!
G
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I understand. May I propose a slightly different strategy? You may grab the object name from the filename for any file format and then overwrite it for FITS if the OBJECT header is available. This would lead to a more uniform behaviour, imho.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In principle a good idea, but looking into the code it is tricky. The name has to be in the final file header. I 'have no problem updating the converted JPG or raw file header with the object name since they where created by the program anyhow. But updating a FITS file header is more a less a violation of the principle never modify the orginal FITS file. I prefer not to do that. The aquisition program should have written the object name in the header.
The object name is only used for seperating series of different object if you stack them all in one step. Further more for naming the final result. Is the name of the final stacked image "No object...." ? If so its better to correct that 'final name in case no object name is found.
Han
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I see your point and I agree with it, given the principle of not modifying the original file, what you do is the rigth thing.
Actually, this could be an option to be selected by the user. Imagine to have a checkbox close to the Browse button allowing the user to choose whether to modify or not the original file upon loading it. This would put the choice in user's hand :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Han,
I notice that the result filename always includes "no_object". If I wanted to include the object name is there a way to do this?
Kind regards,
Phil
Same way with the "Change keyword" popup menu. The only benifit would be that you could stack serveral image series in one stap. It will stack the files based on the object. There is an option to add the object name as round julian day. I could add an option to take the first 7 charactors of the filename. That would work if the filename is started with the object name.
Last edit: han.k 2020-05-12
Probably it is better to add the object name while converting the raws. That is more logical since the raws don't contain any info accept the filename. I will take the first 7 characters of the filename.
Clear skies, Han
See my comment.
OK. Don't change it. By default APT uses the object name as the folder into which the data files are placed.
Can I ask, what made you decide to write ASTAP and HNSKY when there are other solutions around. I am halfway through a rewrite of EQMOD/EQASCOM which I started because it is written in VB6 and is no longer being actively developed. I can see a day coming when it no longer functions.
The basics and UI are working, clunky in places but it passes (or did pass) the ASCOM platform tests. I now need to work out the more complicated bits like how to handle star alignment and guiding but I find it difficult to keep motivated and put in the time necessary. That is why I am so impressed by what you have done here.
https://github.com/JPhilC/LunaticAstroEQ
Already done. I had a function to extract the object name from the file name. (double click on Ra in the viewer). So dowload again (version 0.9.362f) it will add an object name if it can find one in the file name.
I didn't realise EQACOM was writen in VB6. So will your project be a replacement for EQACOM? There is also a similar EQASCOM INDI version. I'm not familiar with VB. I know just enough to rewrite the ASCOM camera simulator for my "Sky simulator" :)
I use EQASCOM but not the modeling . With astrometric (plate) solving it not nessesary and I have to unlock the telescope to move around in my shed. So a simpler version would do for me.
HNSKY is an old project started in1997. ASTAP started 3 years ago. Why? Same reason why you and other people write freeware software I guess. Making something usefull can be fun. I didn't like the other stacking programs.
Han
Last edit: han.k 2020-05-12
My initial intentions were that it would be available to replace EQASCOM if people wanted to stay with something that looked vaguely familiar. There is at least one other ASCOM Telescope controller that speaks Skywatcher under development that I am aware of but it is very different to EQASCOM.
No problem to test LunaticAstroEQ, but do you provide compiled binaries?
I'm not looking for it to be tested. I have just been looking a the other ASCOM telescope controller that I was aware of at :
https://sites.google.com/view/greenswamp/home
It looks like Robert has been busy since I last looked so I'm going to give it a try. If it does everything I need I'll probably go with his and put Lunatic down to experience. His source code is a available and he's using the same developement stack as I am, C# .NET etc.
GS Server looks good except I can't set my time zone. Will report it.
Hi,
sorry for asking, how did you decide to deal with object name? Will it be retrived from the filename also for FITS? I am currently using 0.9.361 on a Mac and the only working method is to use Change keyword in selected files.
Thank you
Version 0.9.362 will retrieve the object from the file name. It hasn't been compiled for the Mac. I will do it tonight. Please report any problem with it. Else use version 0.9.361
Clear skies, Han
Version 0.9.362 is now available for the Mac. The webpage need to be updated but if you download you will get version 0.9.362g
Thank you!
I will try it soon.
Gaetano
Thank you!
I will try it soon.
Gaetano
Version Beta 0.9.362g on MacOS 10.15
Is astap expected to retrieve the object name from the file name and update the Object column in Images tab in the Stack window?
I tried loading the file and also analyzing it but the column is not updated.
Thank you!
G
For FITS files it will read from the header the value of keyword OBJECT. For all other files having no header it tries to read it from the filename.
So if the FITS file has no name behind keyword OBJECT = then there will be no object name.
Clear skies, Han
I understand. May I propose a slightly different strategy? You may grab the object name from the filename for any file format and then overwrite it for FITS if the OBJECT header is available. This would lead to a more uniform behaviour, imho.
In principle a good idea, but looking into the code it is tricky. The name has to be in the final file header. I 'have no problem updating the converted JPG or raw file header with the object name since they where created by the program anyhow. But updating a FITS file header is more a less a violation of the principle never modify the orginal FITS file. I prefer not to do that. The aquisition program should have written the object name in the header.
The object name is only used for seperating series of different object if you stack them all in one step. Further more for naming the final result. Is the name of the final stacked image "No object...." ? If so its better to correct that 'final name in case no object name is found.
Han
I see your point and I agree with it, given the principle of not modifying the original file, what you do is the rigth thing.
Actually, this could be an option to be selected by the user. Imagine to have a checkbox close to the Browse button allowing the user to choose whether to modify or not the original file upon loading it. This would put the choice in user's hand :)