Re: MkIV database - duplicate data

[Tom Droege <tdroege2@earthlink.net>]

Well, I try to keep all this straight.  I am still evolving a bookkeeping 
scheme.  So this is possible.  But I did send all the .cal files.  So a 
duplicate name check *could* catch this.  It could also fail.  One has to 
search for a duplicate julian day.  Depending on the cloud problems, a 
frame could be skipped at the beginning of the run.  If I processed a day 
twice, and with a different cloud rejection scheme, then it is possible to 
have two .cal files from the same day with slightly different names.  The 
check is not to allow two .cal files from the same telescope and the same 
day.

For some time I have been processing a day at a time.  I see no reason that 
I will not continue this.  Earlier I was processing a disk pair at a 
time.  This would give more than one .cal file a day.

I propose that all the sites generate one .cal file per evening per system 
of processed stars.  This should then allow pretty simple bookkeeping to 
keep everything straight.

Tom Droege

At 11:58 AM 1/1/03 -0600, you wrote:
>Forgot to mention this in my previous email.
>
>Patrick Wils has brought it to my attention that there is some duplication 
>of data in the database. It is object #24508 in the database.
>It appears that the observations of this object for JD 2452251 were 
>included in 2 different .cal files that Tom sent me.
>I will check to see if there are any other duplicates in the database and 
>deal with them accordingly.
>
>Mike
>