0000204: incorrect observation time of line observation in new year.

  

Viewing Issue Simple Details Jump to Notes ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000204 [TMS] block always 28-12-09 11:35 14-06-10 07:55
Reporter Jurjen Sluman View Status public  
Assigned To Arno Schoenmakers
Priority normal Resolution open  
Status closed  
Summary 0000204: incorrect observation time of line observation in new year.
Description By converting the records which have the observations in it to start in 2009 and end in 2010, the line observation is incorrect added to the MeasurementTable.
The records in FILPRP 212-214 are correct and also the entires in MOM (R10A/005/NGC 2594_obs_2)

Entries in MeasurementTable:
R10A/005/3C48 Scheduled 2009-12-31 18:42:00 2009-12-31 19:12:00 00:30:00 ...
R10A/005/3C286 Scheduled 2010-01-01 07:24:40 2010-01-01 07:54:40 00:30:00 ...
R10A/005/NGC2594 Scheduled 2010-12-31 19:19:40 2011-01-01 07:18:40 11:59:00 ...

It should be :
R10A/005/3C48 Scheduled 2009-12-31 18:42:00 2009-12-31 19:12:00 00:30:00 ...
R10A/005/NGC2594 Scheduled 2009-12-31 19:19:40 2010-01-01 07:18:40 11:59:00 ...
R10A/005/3C286 Scheduled 2010-01-01 07:24:40 2010-01-01 07:54:40 00:30:00 ...
Additional Information
Attached Files

- Relationships

- Notes
(0000216)
Jurjen Sluman
28-12-09 11:41

After calling Arno Shoenmakers, he will change directly the entry in the MeasurementTable, so that the observation will start on the correct time by the TMSSystem.
The entires are now:
R10A/005/3C48 Scheduled 2009-12-31 18:42:00 2009-12-31 19:12:00 00:30:00 ...
R10A/005/NGC2594 Scheduled 2009-12-31 19:19:40 2010-01-01 07:18:40 11:59:00 ...
R10A/005/3C286 Scheduled 2010-01-01 07:24:40 2010-01-01 07:54:40 00:30:00 ...
 
(0000217)
Jurjen Sluman
28-12-09 11:43

The entry is changed directly in the database, so now we still have to find the bug, why an incorrect year is calculated by the conversion from FILPRP to TMSSystem by obsco
 
(0000220)
Arno Schoenmakers
05-01-10 13:52

Hallo Arno,
 
Dit probleem (nr 204 in mantis) heb ik opgelost.
Het was een probleem in stfma, en zat heel diep.
De routine grego (zet dag van het jaar om in maand en dag van de maand) had een fout.
Die routine veranderde ook het jaar, als de dag van het jaar boven 365 kwam, maar dat
was het jaar in de COMMON, zodat dus alle code daarna ook dacht dat het 2010 was, en
een 2e aanroep van grego maakte het jaar zelfs 2011 !
 
Ik kan echter de status van dit probleem niet veranderen omdat het aan jou toegekend is,
kun je dat zelf doen, of liever, het probleem aan mij toekennen zodat ik het doe ?
 
Groeten
Hans
 

- Issue History
Date Modified Username Field Change
28-12-09 11:35 Jurjen Sluman New Issue
28-12-09 11:36 Jurjen Sluman Assigned To  => Jurjen Sluman
28-12-09 11:36 Jurjen Sluman Status new => assigned
28-12-09 11:38 Jurjen Sluman Description Updated
28-12-09 11:41 Jurjen Sluman Note Added: 0000216
28-12-09 11:43 Jurjen Sluman Note Added: 0000217
28-12-09 11:43 Jurjen Sluman Assigned To Jurjen Sluman => Arno Schoenmakers
05-01-10 13:52 Arno Schoenmakers Note Added: 0000220
05-01-10 13:52 Arno Schoenmakers Status assigned => resolved
14-06-10 07:55 Arno Schoenmakers Status resolved => closed