Go to the bottom.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! SDDL: constraint_windows.sddl
!
! Purpose: This file defines the constraint_windows relation.
!
! Modification History:
!
! Date PR Who Reason
! -------- ------- --- -------------------------------------------------
! 07/18/94 27073 SSW SPSS Planning Windows Support
! 02/02/95 28292 SK Modified "REPLICATION" wording under
! SUBSYSTEM_USING
! 03/14/95 28429 RJS comments update
! 04/16/97 33890 MRB Field names changed in ASSIST from wnd_ to _window
! 05/11/98 35530 PAP Added status field. Updated the values of the
! field. Field was previously in plan_windows.
! 05/11/98 36870 PAP Add C lanquage
! 06/09/98 35530 PAP Updated index name to conform to assist tables
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
LANGUAGE FORTRAN,SQL,C
INCLUDE ZSPSS_USER_TYPES.SDDL
CONSTANT WINDOW_TYPE_CONSTRAINT
FILE
VALUE 1
END_CONSTANT
RECORD CON_WIN_TYPE
DESCRIPTION "
Constraint windows are time intervals in the proposal cycle where
SPIKE thinks a scheduling unit (SU) can be scheduled. This is based
on the target position, orientation requirements, links, locks,
phase windows and the minimum visibility period. The windows are
start-to-start, i.e., an SU must start before the window end, but
may end after the window end.
This relation defines constraint windows for a scheduling unit. These
are verified by the CALOPT/VERIFY=SPIKE_CW command. That command
can be run to validate the schedulability of a SPIKE constraint window .
Feedback is provided to the user through reports and to SPIKE by
populating the sister relation constraint_windows_ver.
This gives SPIKE feedback on the accuracy of its constraint windows and
with that information it can create a more accurate LRP comprised of
plan windows known to be schedulable on SPSS calendars."
FIELD sunit_id
TYPE SUNIT_ID_TYPE
END_FIELD
FIELD version_num
TYPE VERSION_NUM_TYPE
END_FIELD
FIELD create_date
TYPE TIME_STAMP_TYPE
DESCRIPTION "This is the date the window was generated."
END_FIELD
FIELD visit_id
TYPE VISIT_ID_TYPE
END_FIELD
FIELD prop_id
TYPE INT_PROPOSAL_ID_TYPE
END_FIELD
FIELD window_begin
TYPE SOGS_CHAR_TIME_TYPE
DESCRIPTION "This field is the start time of the constraint or
verified constraint window."
END_FIELD
FIELD window_end
TYPE SOGS_CHAR_TIME_TYPE
DESCRIPTION "This field is the end time of the constraint or
verified constraint window."
END_FIELD
FIELD status
TYPE C3
DESCRIPTION "This field will be used to indicate the
following values:
SAA - This visit can be used for hiding the SAA
passages in occultation during this window.
CVZ - The visit's target is in the CVZ during this
window.
SAC - SAA and CVZ, the target is in the CVZ and it
satisfies the SAA hiding criteria during this
window
The field is used to aid program coordinators."
END_FIELD
END_RECORD
!------------------------------------------------------------------------------
!
! RELATION DECLARATION
!
!------------------------------------------------------------------------------
RELATION constraint_windows
TYPE CON_WIN_TYPE
DESCRIPTION "Long Range Plan Constraint Windows Relation"
SUBSYSTEM_USING "SPSS", "SPIKE", "REPLICATION-TO-SOGS"
RELATED_FIELDS "constraint_windows_ver.*" "constraint_win_ver_criteria.*" "plan_windows.*" "lrp_base_cat.*"
INDEX constraint_windows_index1
TYPE unique, clustered
FIELDS sunit_id, version_num, create_date, window_begin
END_INDEX
END_RELATION
!------------------------------------------------------------------------------
!
! INSTANCE DECLARATION
!
!------------------------------------------------------------------------------
INSTANCE constraint_windows
! FILE
TYPE CON_WIN_TYPE
END_INSTANCE
Go to the top.