[Groundstation-commits] CVS: gpredict2/src sat-popup-menu.c, 1.24, 1.25

[Alexandru C. <cs...@us...>]

Update of /cvsroot/groundstation/gpredict2/src
In directory sc8-pr-cvs2.sourceforge.net:/tmp/cvs-serv6154

Modified Files:
	sat-popup-menu.c 
Log Message:
Fixed wrong epoch day in the satellite info dialogue.

Index: sat-popup-menu.c
===================================================================
RCS file: /cvsroot/groundstation/gpredict2/src/sat-popup-menu.c,v
retrieving revision 1.24
retrieving revision 1.25
diff -C2 -d -r1.24 -r1.25
*** sat-popup-menu.c	21 Oct 2006 19:25:45 -0000	1.24
--- sat-popup-menu.c	28 Oct 2006 20:07:40 -0000	1.25
***************
*** 434,440 ****
  	guint      size;
  
! 
  	epd = g_date_new_dmy (1, 1, sat->tle.epoch_year);
! 	g_date_add_days (epd, sat->tle.epoch_day);
  
  	/* convert date to struct tm */
--- 434,450 ----
  	guint      size;
  
! 	/* http://celestrak.com/columns/v04n03/#FAQ02
! 	   ... While talking about the epoch, this is perhaps a good place to answer
! 	   the other time-related questions. First, how is the epoch time format
! 	   interpreted? This question is best answered by using an example. An epoch
! 	   of 98001.00000000 corresponds to 0000 UT on 1998 January 01st in other
! 	   words, midnight between 1997 December 31 and 1998 January 01. An epoch of
! 	   98000.00000000 would actually correspond to the beginning of 1997 December
! 	   31st strange as that might seem. Note that the epoch day starts at UT
! 	   midnight (not noon) and that all times are measured mean solar rather than
! 	   sidereal time units (the answer to our third question).
! 	*/
  	epd = g_date_new_dmy (1, 1, sat->tle.epoch_year);
! 	g_date_add_days (epd, sat->tle.epoch_day-1);
  
  	/* convert date to struct tm */