The SEDRIS Data Representation Model
APPENDIX A - Classes
Relative Time

Class Name: Relative Time

Superclass - <Time Point>

Subclasses

This DRM class is concrete and has no subclasses.

Definition

An instance of this DRM class specifies a date and time relative to either a specified <Absolute Time> instance or (if an <Absolute Time> instance is not specified) relative to the simulation start time.

Primary Page in DRM Diagram:

Secondary Pages in DRM Diagram:

This class appears on only one page of the DRM class diagram.

Example

  1. The date/time is an astronomical Julian day of 2449143.77083 (June 5, 1993 0630Z). Astronomical Julian dates are referenced to 1 January 4712 BCE at 12Z. Since the fractional days are converted to hours, minutes and seconds, the fields in the <Relative Time> instance are set as follows.

    delta_days 2449143
    delta_hours 18
    delta_minutes 30
    delta_seconds 0.0

    The fields in the <Absolute Time> component are set as follows.

    time_value.configuration SE_TIMECFG_DATE_YMD_AND_TIME_H
    time_value.value. ymd_h.year -4712
    time_value.value. ymd_h.month SE_MONTH_JANUARY
    time_value.value.ymd_h.day 1
    time_value.value.ymd_h.hour 12

  2. The time is 6 hours 25 minutes and 30 seconds after the start of the simulation. The fields of the <Relative Time> instance are set as follows.

    delta_days 0
    delta_hours 6
    delta_minutes 25
    delta_seconds 30.0

  3. A DRM object becomes active 20 minutes after the simulation starts. That is, its activation time is expressed in simulation time (relative to the start of the simulation), so the activation time is specified using a <Relative Time> instance. The time_significance field is set to SE_TIMESIGNIF_OCCURRENCE.

FAQs

What is the purpose of this class?

This class provides a means to specify a time relative to another time. It can be used in the same manner as <Absolute Time>.

How can a data provider indicate the Julian day of the year?

Specify a component <Absolute Time> to indicate the reference date/time as 0Z 1 January of the appropriate year. If year = -1, the date applies to any year. See example 1.

Can a data provider specify times relative to date/times other than January 1?

Yes. See example 2.

How can a data provider indicate a time relative to start of the simulation?

If a <Relative Time> does not have an <Absolute Time> component, the time is relative to the start of the simulation. See example 3.

Constraints

Composed of (two-way)

Component of (two-way) (inherited)

Inherited Field Elements

SE_Time_Significance

time_significance;

1

Field Elements

SE_Integer

delta_days;

2

SE_Byte_Unsigned

delta_hours;

3

SE_Byte_Unsigned

delta_minutes;

4

SE_Long_Float

delta_seconds;

5

Notes

Fields Notes

time_significance

The time_significance field specifies the usage of the time information.

delta_days

The delta_days field specifies the number of whole days relative to the specified time.

delta_hours

The delta_hours field specifies the number of whole hours relative to the specified time, after delta_days has been taken into account.

delta_minutes

The delta_minutes field specifies the number of whole minutes relative to the specified time, after delta_days and delta_hours have been taken into account.

delta_seconds

The delta_seconds field specifies the remaining seconds relative to the specified time. Fractions provide sub-second accuracy, if needed.

Prev: Regular Axis. Next: Relative Time Interval. Up:Index.

Last updated: July 1, 2011 Copyright © 2011 SEDRIS™