Welcome to iraf.net Thursday, May 02 2024 @ 05:39 PM GMT
valdes |
12/06/2005 03:41PM (Read 3102 times)
|
|
|
Status: offline
Registered: 11/11/2005
Posts: 728
|
[b:dbd62a37a9]From: [/b:dbd62a37a9]Cristina Rodríguez López <cristina@iaa.es ([email]cristina@iaa.es[/email])>
[b:dbd62a37a9]Date: [/b:dbd62a37a9]December 6, 2005 3:44:03 AM MST
[b:dbd62a37a9]To: [/b:dbd62a37a9]Frank Valdes <valdes@noao.edu ([email]valdes@noao.edu[/email])>
[b:dbd62a37a9]Subject: [/b:dbd62a37a9][b:dbd62a37a9]Re: help with asttimes[/b:dbd62a37a9]
Hola Frank,
Thanks for your help, it worked perfectly. I haven't realized about the asthedit functions even if I had already used it once for 'juldays' a time ago.
Thanks again, and greetings,
Cristina.
Frank Valdes wrote:
[quote:dbd62a37a9]Hola Cristina,
The task you want is ASTHEDIT in the ASTUTIL package. The command that I think works for your data is:
as> asthedit ngc7094-001B lst.dat
as> hselect ngc7094-001B lst yes
18:52:47.74
where
as> type lst.dat
lst = mst (@"date-obs", obsdb ("osn", "longitude"))
This takes your DATE-OBS, where the time is supposed to be UT, and the information from the observatory database and computes the LST and puts it in your header as keyword LST. I assume your observatory database has OSN since it is in the file I have here.
Let me know if you have questions or if you think this is wrong.
Yours,
Frank Valdes
[/quote:dbd62a37a9]
|
|
|
|
| |
|
Content generated in: 0.04 seconds |
|