<?
	include("includes/pagesetup.inc");
?>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="StyleSheet" href="<? echo $css; ?>" type="text/css" media="screen">
<title></title>
<meta name="description" content="">
<meta name="keywords" content="">
</head>
<body>
<?
include( $banner );
?>

<table border=0><tr>
<td valign="top" class="navcol">
<?
include("$sitenav");
?>
</td>
<td valign="top" class="contentcol">
<h2>Tentative Operating Schedule</h2>

<p>
Note that this schedule is subject to change and about the only thing we can promise is that the final schedule will be different. 
However flawed, the tentative schedule does offer insights into which layouts may only be offered in confict with each other and that ***MAY*** help some groups come to better decsions on their collective choices.
Individuals within Groups MUST submit identical choices: we can't read your minds. 
</p>
<p>
Layouts with times noted in <span style="background-color:#0f0;">GREEN</span> are BONUS sessions and do not conflict with or count against your regular op sessions.
</p>

<p>
Nothing on this page changes the BayRails layout assignment process: you will still submit a list of the layouts you want in order of preference and that list along with your date of registration will determine your assignments. 
We start with the highest priority guest (determined by time of registration and distance travelled) and give you the best available layout per your requests. 
After we've gone through the whole list (everyone gets a first round pick), we start over at the top until every guest has had their best three choices. 
Therefore you should fill out the priority list down to 10, and you should register as early as possible. Once assignments have been published (and people have negotiated carpools, etc.) we fill the dropouts by hand to minimize disruption. 
Note that groups traveling together will get a collective priority closer to the priority of the guest with the lowest priority in the group.  
</p>

<p>
Of course we reserve the right to make adjustments to ensure operators with the right mix of skills are at all sessions and these procedures may be modified at any time at the whim of the BayRails Committee
</p>


<!-- Formatting for EventTools table -->
<style TYPE="text/css">
    /* center everything */
    .et-faobd-table { text-align: center; }
    /* except left align owner and layout name cells */
    .et-faobd-td-1 { text-align: left; }
    .et-faobd-td-2 { text-align: left; }

    /* dont display the distance/time (3) or crew (4) columns */
    .et-faobd-th-3 { display: none; }
    .et-faobd-td-3 { display: none; }
  /*  .et-faobd-th-4 { display: none; }
    .et-faobd-td-4 { display: none; }*/
    .et-faobd-slots-total{ display: none; } /* don't display totals */

    /* sessions with "bonus" status show green  */
    .et-faobd-session-status-50 { background: #80FF80; }
</style>
<?php
require_once('eventtools/access.php');
require_once('eventtools/utilities.php');
require_once('eventtools/formatting.php');
require_once('eventtools/parsers.php');

//$where = parse_layout_query();
$where = "status_code >= 50";

$order = parse_order();

if ($where == NULL) $where = "";
if ($where != "") $where = " WHERE ".$where;

format_all_ops_by_day("edit_layouts_all.php?layoutid=", $where, $order, NULL, "layout_photo_url", NULL, NULL);

?>
</table>





