• daysep: The required days between when each of the instances of this session should be run. This is only valid if the "mult" field is greater than 1. For example if mult=2 and daysep=2, then there must be 2 days between each scheduled instance of this session. I am not sure if this is a minimum, maximum or exact value. I suspect minimum TBD ask Carl.

• daysep: The required days between when each of the instances of this session should be run. This is only valid if the "mult" field is greater than 1. For example if mult=2 and daysep=2, then there must be 2 days between each scheduled instance of this session. Sometimes this is an exact number, sometimes not.

• leeway: The center LST can be shifted by this amount. Units are radiams.

• leeway: The amount of play in the lst field. The edges of the session must remain in the bounds of the leeway and LST, e.g., lst = 4, leeway = 3, and hours = 2 implies a session could be as early as 1 to 3 or as late as 5 to 7. The units are radiams.

• delay: ?

• delay: The required days between different sessions (not instances of sessions). Sometimes this is an exact number, sometimes not. This is only valid for Projects with more than 1 session. The order of the session is specified in the project field.

DB Table Examples DBase and MySQL:

DB Table Examples DBase and MySQL:

Vprog table field descriptions for the Pas mysql database

• pcode: The project code
• pdate: I don't think we care if this is the input or submission date.
• project: This is an ordering of the sessions (not just an internal priority) for each session in the project. "a" comes before "b".
• bands: The receiver bands required. A session may require multiple receivers. In this case the receiver designations are concatenated togther. An example of this would be "KU", specifying that the K and Ku receivers are required. Most of the band designations are self explanatory except for the 2 listed below:
  • U = Ku band
  • 8 = ?
• backends: The backend(s) required for the session. The designations are the same ones used in the resource page. TBD list them here
• mult: The number of times this session should be run.
• daysep: The required days between when each of the instances of this session should be run. This is only valid if the "mult" field is greater than 1. For example if mult=2 and daysep=2, then there must be 2 days between each scheduled instance of this session. I am not sure if this is a minimum, maximum or exact value. I suspect minimum TBD ask Carl.
• hours: The hours to be observed in an instance of this session . Units are in Radians
• lst: The center LST for this session.
• leeway: The center LST can be shifted by this amount. Units are radiams.
• dayreq: Fixed time (or fixed window, since the session may be able to run in different telescope period for the given day?)
• delay: ?
• delayafterkey: ?
• outermult: Repeats the seesion AND the mult this many times. So if a session has mult=2 and a outermult = 3. The session would run 2 times with the session parameters and then this would be repeated 3 times with the outer* parameters (listed below).
• outerdaysep: The required days between when each of the Outer repeats (see outermult above) of this session. This is only valid if the "outermult" field is greater than 1. I am not sure if this is a minimum, maximum or exact value. I suspect minimum TBD ask
• dyncode: designates how this session should be scheduled. L = low frequency, F = Fixed, P = ?, H = high frequency, S= schedule per the band of the receiver required. Currently anything X band or higher is scheduled as high frequency.
• schedularnote: This seems to contain what the dynamic scheduling team calls "time between".

%META:TOPICINFO{author="MikeMcCarty" date="1162485180" format="1.0" version="1.1"}% %META:TOPICPARENT{name="SchedulingSoftware"}%

DB Table Examples DBase and MySQL:

• TableDoc.txt: DBase table structures
• propmysql.sql: SQL script for creating some the DBase tables. Resulting tables have been created under the database name "pas" on the MySQL server leo. Use phpmyadmin to access the MySQL database directly.

DBase Table Documentation

• DBaseDoc.vsd: Contains table diagrams.

-- MikeMcCarty - 02 Nov 2006 %META:FILEATTACHMENT{name="TableDoc.txt" attr="" comment="" date="1161107099" moveby="MikeMcCarty" movedto="Software.DBaseDocs" movedwhen="1162485006" movefrom="Software.SchedulingSoftware" path="TableDoc.txt" size="85369" user="MikeMcCarty" version="1.1"}% %META:FILEATTACHMENT{name="propmysql.sql" attr="" comment="" date="1161107117" moveby="MikeMcCarty" movedto="Software.DBaseDocs" movedwhen="1162485045" movefrom="Software.SchedulingSoftware" path="propmysql.sql" size="91042" user="MikeMcCarty" version="1.1"}% %META:FILEATTACHMENT{name="DBaseDoc.vsd" attr="" comment="" date="1161715114" moveby="MikeMcCarty" movedto="Software.DBaseDocs" movedwhen="1162485067" movefrom="Software.SchedulingSoftware" path="DBaseDoc.vsd" size="320512" user="MikeMcCarty" version="1.1"}%