Comment 2 for bug 693764

Revision history for this message
Marina Rejkuba (mrejkuba) wrote : Re: [Bug 693764] Re: Period - run matching

Diego wrote:
> The period and the runID are obtained from the columns "period" and
> "prog_id" of the phase2_metadata table.
>
> In the case of run ID 179.A-2010(B) some of the OBs have period 84
> (1093) and others period 85 (34).
>
> I'm not an expert on the semantics of data but as far as I know the
> period stored in data base corresponds to the period when the OB was
> executed that can be different from the period when the OB was
> scheduled. For the period 179.A-2010(B) 34 of the OBs were executed on
> period 85 that is what you see on SVMT. You should review the semantics
> of the data base in order to avoid future confusions.
>
> Diego.
>
> ** Changed in: svmt
> Status: New => Invalid
>
>

Hmmm,

Interesting, but I don't think that what you suggest is true.
P84 is between October 1, 2009 - March 31, 2010
P85 is between April 1, 2010 - September 30, 2010
P86 is between October 1, 2010 - March 31, 2011

If period corresponds to teh time when an OB was executed, that would
imply that in 6 months between April - September 2010 we only executed
34 OBs, while in the period when we had science verification, and start
of operations (P84) we executed 1093 OBs.
I know for fact that this cannot be true.... so there must be something
else there.
I'll have to check with Adam/Ignacio how is period associated to run and
to OB in the phase2_metadata table.

Best wishes,
Marina