DATABASES/madrigal Commit - r14:8f437cc4b32c

Update html images routes

jespinoza -

r14:8f437cc4b32c

parent child

Context file:

r14:8f437cc4b32c

Expand all files

The requested changes are too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/ad_appropriate.html +8 -8

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>Is Madrigal appropriate</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="admin.html" --><!-- InstanceParam name="href_next_top" type="text" value="ad_install.html" --><!-- InstanceParam name="href_back_top" type="text" value="admin.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="ad_install.html" --><!-- InstanceParam name="href_prev_top" type="text" value="admin.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="ad_install.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="ad_install.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_install.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_install.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Is Madrigal appropriate for my instrument(s)?<!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_install.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Installing Madrigal <!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">Is Madrigal appropriate for my instrument(s)?</h1>
             <p>The Madrigal database is designed to hold data about the upper atmosphere. One of the strengths of the Madrigal is that most of the measured parameters it contains are defined
-            in a community standard, whose metadata can be found under the Access metadata tab. With the release of Madrigal 3.0, the file format is now Hdf2 with the restrictions defined in the <a href="/static/CEDARMadrigalHdf5Format.pdf">CEDAR Madrigal Hdf5 file format</a>. This standard defines many frames of reference used commonly in atmospheric science, such as geodetic coordinates, geomagnetic coordinates, or radar (azimuth, elevation, and range) coordinates. Upper atmospheric data that can fit into one of these coordinate systems is a good candidate for Madrigal. Madrigal is not presently designed to handle spacecraft ephemeris in order to determine location, and to date Madrigal has only been used to hold spacecraft data that is independent of position (such as solar wind) or can be converted to one of the coordinate systems discussed above (such as total electron concentration in geodetic coordinates from GPS satellites).</p>
+            in a community standard, whose metadata can be found under the Access metadata tab. With the release of Madrigal 3.0, the file format is now Hdf2 with the restrictions defined in the <a href="{% static 'CEDARMadrigalHdf5Format.pdf">CEDAR Madrigal Hdf5 file format</a>. This standard defines many frames of reference used commonly in atmospheric science, such as geodetic coordinates, geomagnetic coordinates, or radar (azimuth, elevation, and range) coordinates. Upper atmospheric data that can fit into one of these coordinate systems is a good candidate for Madrigal. Madrigal is not presently designed to handle spacecraft ephemeris in order to determine location, and to date Madrigal has only been used to hold spacecraft data that is independent of position (such as solar wind) or can be converted to one of the coordinate systems discussed above (such as total electron concentration in geodetic coordinates from GPS satellites).</p>
             <p>Generally, if the <a href="{% url 'parameter_metadata' %}">parameters found in the metadata</a> are appropriate for you, or only a few additions need to be made, then data from your instrument(s) is probably appropriate for Madrigal. Please feel free to contact the <a href="mailto:madrigal@haystack.mit.edu">OpenMadrigal administrator</a> if you have any questions about using Madrigal. </p>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_install.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_install.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Is Madrigal appropriate for my instrument(s)?<!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_install.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Installing Madrigal <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/ad_createExp.html +8 -8

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>Creating and modifying Madrigal experiments</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="admin.html" --><!-- InstanceParam name="href_next_top" type="text" value="ad_other.html" --><!-- InstanceParam name="href_back_top" type="text" value="ad_createFiles.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="ad_createFiles.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="ad_other.html" --><!-- InstanceParam name="href_prev_top" type="text" value="ad_createFiles.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="ad_other.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="ad_createFiles.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="ad_other.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_createFiles.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_createFiles.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_other.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_other.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Creating and modifying Madrigal experiments <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_createFiles.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Creating Madrigal data files <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_other.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Other admin tasks <!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">Creating and modifying Madrigal experiments</h1>
             <p>Adding data to Madrigal involves two steps. The first step is <a href="{% url 'docs' 'ad_createFiles.html' %}">creating Madrigal data files</a>, as discussed in the previous section. The next is installing them on the Madrigal database, with the appropriate metadata and any additional plots or other information you want to supply. </p>
             <p>There are a number of scripts supplied with Madrigal to simplify the task of creating or modifying experiments on Madrigal. Use these scripts if you want to:</p>
             <ul>
               <li><a href="#createExpWithFile">Create an experiment using a pre-existing Madrigal file</a></li>
               <li><a href="#createRTExp">Create an experiment when no Madrigal file yet exists</a> (such as to create a real-time file)</li>
               <li><a href="#changeExpStatus">Modify the status of a given experiment</a></li>
               <li><a href="#addFileToExp">Add a new file to an experiment</a></li>
               <li><a href="#updateFileInExp">Modify an existing file in an experiment</a></li>
               <li><a href="#changeFileStatus">Change the status of a file in an experiment</a></li>
               <li><a href="#removeFileFromExp">Remove a file from an experiment</a></li>
               <li><a href="#auxillary">Adding auxiliary plots and information to a Madrigal experiment</a></li>
             </ul>
             <p>After  changing  a Madrigal experiment using one or more of the scripts above, the script <em>madroot</em>/bin/updateMaster must be run for the changes to take effect. That's because these scripts change the metadata files in the local directory, and updateMaster combines all the local metadata files into the ones in <em>madroot</em>/metadata, which the used by the user interface to Madrigal. </p>
             <p>This page also describes how you can add auxiliary information to a given Madrigal experiment. </p>
             <h4><a name="createExpWithFile" id="createExpWithFile"></a>Create an experiment using a pre-existing Madrigal file</h4>
             <p>If you have already created a Madrigal file for a given experiment, and want to add that new experiment to Madrigal, use the script createExpWithFile.py, located in <em>madroot</em>/bin. Usage:</p>
             <pre>
             createExpWithFile.py is a script used to create a new Madrigal experiment
             based on an already existing file.  Information such as the duration of the
             experiment is obtained by analyzing the file.
             With Madrigal 3, accepts either old CEDAR database format files, or CEDAR Madrigal
             Hdf5 files.
             Required arguments:
                 --madFilename - full path to the complete Madrigal file. Basename will
                                 be maintained. If old CEDAR databse format, .hdf5 will
                                 be appended
                 --expTitle - experiment title. Use quotes if title contains spaces.
                 --permission - 0 for public, 1 for private (restricted to certain IP range)
                                (both the experiment and the file will set)
                 --fileDesc - file decription
             Optional arguments:
                 --instCode - instrument code. If this argument missing, instrument code is
                              taken from file, but error is thrown if more than one kinst found.
                 --category - 1=default, 2=variant, or 3=history If this argument is missing,
 (default) used.
                 --dirName  - directory name to use for experiment.  If not given, the directory
                              name will be the default name DDmmmYY[optChar].  Cannot contain "/"
                 --optChar  - optional character to be added to experiment directory if no dirName
                              given.  If dirName argument given, this argument ignored.  optChar
                              is used if the default directory name DDmmmYY is used for
                              more than one experiment created for a given instrument on a given day.
                              For example, if --optChar=h for a MLH experiment on September 12, 2005,
                              then the experiment directory created would be experiments/2005/mlh/12sep05h.
                 --kindat  -  Set file kindat independently from one (or more) in file
                 --experimentsDirNum - the number to be appended to the experiments directory, if experiments
                                   directory being used is of the form experiments[0-9]* instead of just
                                   experiments.  For example, if experimentsDirNum is 7, then the experiment
                                   would be created in MADROOT/experiments7 instead of MADROOT/experiments.
                                   Default is to create in experiments directory.
                 --PI - set Principal Investigator for this experiment
                 --PIEmail - set PI email for this experiment
                 --fileAnalyst - set file analyst name for this file.  This will default to blank.
                 --fileAnalystEmail - set file analyst email for this file.  This will default to blank.
             </pre>
             <pre>&nbsp;</pre>
             <p>Example: If you have already created the Madrigal file mlh060120g.001.hdf5 in the /tmp directory,
             and the experiment name is Calibration, the file should be public, and the description is "Final", you would enter:</p>
             <pre>/opt/madrigal/bin/createExpWithFile.py --madFilename=/tmp/mlh060120g.001.hdf5 \
                 --expTitle="Calibration" --permission=0 --fileDesc="Final"</pre>
             <p>If your input file is an old style CEDAR database file mlh060120g.001, the only difference is that there is not hdf5 extension:</p>
             <pre>/opt/madrigal/bin/createExpWithFile.py --madFilename=/tmp/mlh060120g.001 \
                 --expTitle=&quot;Calibration&quot; --permission=0 --fileDesc=&quot;Final&quot;</pre>
             <h4><a name="createRTExp" id="createRTExp"></a>Create an experiment when no Madrigal file yet exists</h4>
             <p>If you want to create an experiment for a Madrigal data yet to be created (such as when you want to create the Madrigal file in real-time), use the script createRTExp.py, located in <em>madroot</em>/bin. Usage: </p>
             <pre>createRTExpWithFile.py is a script used to create a new Madrigal experiment
                that will contain real-time files.  These real-time files are assumed not to exist
                yet.</pre>
             <pre>Required arguments::</pre>
             <pre> --startDate - experiment start date in form YYYY-MM-DD</pre>
             <pre> --inst - instrument code or 3-letter Madrigal mnenonic</pre>
             <pre> --expTitle - experiment title. Use quotes if title contains spaces.</pre>
             <pre> --rtFiles - comma-separated list of realtime file basenames to be created</pre>
             <pre> --kindats - comma-separated list of ints or single int of kindats for each realtime file.
                The length and order must be the same as rtFiles.  If only one
                given, it is assumed that all rtFiles have the same kindat.</pre>
             <pre> --fileDescs - comma-separated list of file descriptions. If the file description contains spaces,
                quotes must be used.</pre>
             <pre>Optional argument::</pre>
             <pre> --numDays - number of days the experiment is estimated to run - if not given, and no start
                and end times specified, defaults to one day.  Error raised if endDate and endTime
                also specified.</pre>
             <pre> --startTime - start time in form HH:MM:DD.  Defaults to 00:00:00</pre>
             <pre> --endDate - end day in form YYYY-MM-DD. endTime must also be specified</pre>
             <pre> --endTime - end time in form HH:MM:DD.  endDate must also be specified</pre>
             <pre> --permissions - comma-separated list of 0 for public, 1 for private (restricted to certain IP range).
                If only one given, it is assumed it applied to all.  If this argument is not
                given, it defaults to 0 (public)</pre>
             <pre> --dirName  - directory name to use for experiment.  If not given, the directory
                name will be the default name DDmmmYY[optChar].  Cannot contain &quot;/&quot;</pre>
             <pre> --optChar  - optional character to be added to experiment directory if no dirName
                given.  If dirName argument given, this argument ignored.  optChar
                is used if the default directory name DDmmmYY is used for
                more than one experiment created for a given instrument on a given day.
                For example, if --optChar=h for a MLH experiment on September 12, 2005,
                then the experiment directory created would be experiments/2005/mlh/12sep05h.</pre>
             <pre> --security - overall experiment access.  0 for public, 1 for private, -1 for ignore.
              Defaults to public (0)</pre>
              <pre>--experimentsDirNum - the number to be appended to the experiments directory, if experiments
                                   directory being used is of the form experiments[0-9]* instead of just
                                   experiments.  For example, if experimentsDirNum is 7, then the experiment
                                   would be created in /Users/brideout/madroot31/experiments7 instead of MADROOT/experiments.
                                   Default is to create in experiments directory.</pre>
              <pre> --PI - set Principal Investigator for this experiment</pre>
              <pre> --PIEmail - set PI email for this experiment</pre>
              <pre> --fileAnalyst - set file analyst name for these files (no commas allowed).
                     This will default to blank.  If a different
                     fileAnalyst is desired for each file, the names must be comma separated.</pre>
              <pre> --fileAnalystEmail - set file analyst email for this file.  This will default to blank.
                     If a different fileAnalyst email is desired for each file, the emails must be comma separated.</pre>
             <p>Example: If you plan to create two real-time Madrigal files called mlh021001a.000.hdf5 and mlh021001b.000.hdf5 for the
             Millstone Hill Radar for an experiment planned to run 2 days, with both files having the kindat 3410, you would enter:</p>
             <pre>/opt/madrigal/bin/createRTExp.py --startDate=2002-10-01 --numDays=2 --inst=mlh --expTitle="test experiment" \
                 --rtFiles=mlh021001a.000.hdf5,mlh021001b.000.hdf5 --kindats=3410 \
                 --fileDescs="preliminary - single pulse,preliminary - alternating code"
             </pre>
             <h4><a name="changeExpStatus" id="changeExpStatus"></a>Modify the status of a given experiment</h4>
             <p>All of the experiment attributes can be changed by the script changeExpStatus.py,  located in <em>madroot</em>/bin. The most common reason you'd want to run this script is to change an experiment's security, with the options being 0 (public), 1 (<a href="ad_other.html#private">limited by IP address</a>), and -1 (ignored, or hidden from everyone). To completely remove an experiment, simply delete the directory. However, setting security to -1 allows you to bring the experiment back at some later time by running changeExpStatus.py again. </p>
             <p>A number of other attributes can also be modified, but most are set automatically, and should not need modification.</p>
             <p>Usage:</p>
             <pre>changeExpStatus.py is a script used to change the status of an
              existing Madrigal experiment.  The following attributes can be changed:</pre>
             <pre> expUrl
                experiment name
                siteID
                start date
                start time
                end date
                end time
                instrument code
                security (public, private. ignore)
                PI (optional - overrides default for instrument)
                PIEmail (optional - overrides default for instrument</pre>
             <pre>Required argument: </pre>
             <pre> --expDir - full path to experiment directory. Example:
                &quot;/opt/madrigal/experiments/1998/mlh/20jan98&quot;</pre>
             <pre>Optional arguments - set these to change an experiment attribute:</pre>
             <pre> --expUrl - must be in form &lt;cgi base&gt;/madtoc/YYYY/&lt;3 letter lower case inst code&gt;/&lt;expDir&gt;
                example: http://www.haystack.mit.edu/cgi-bin/madtoc/1997/mlh/03dec97g</pre>
             <pre> --expName - experiment name.  Quotes required if contains spaces.  Example: &quot;World Day&quot;</pre>
             <pre> --siteID - Madrigal siteID of where data will be stored.  Error raised if not the siteID
                of the local Madrigal site. Example: 4</pre>
             <pre> --startDate - new start date of experiment (UT).  In form YYYY-MM-DD.  Example: 1998-01-20</pre>
             <pre> --startTime - new start time of experiment (UT).  In form HH:MM:DD.  Example: 12:30:00</pre>
             <pre> --endDate - new end date of experiment (UT).  In form YYYY-MM-DD.  Example: 1998-01-21</pre>
             <pre> --endTime - new end time of experiment (UT).  In form HH:MM:DD.  Example: 23:30:00</pre>
             <pre> --inst - new instrument code.  Example: 30</pre>
             <pre> --security - new security code.  Allowed values are 0 for public, 1 for private (limited IP range access)
                             -1 for ignore, 2 for archived experiment, 3 for private (limited IP range access) archived
                             experiment.</pre>
             <pre> --PI - set Principal Investigator for this experiment</pre>
             <pre> --PIEmail - set PI email for this experiment</pre>
             <p>Example: to change to experiment /opt/madrigal/experiments/2006/mlh/20jan to be private, you would run: </p>
             <pre>/opt/madrigal/bin/changeExpStatus.py --expDir=/opt/madrigal/experiments/2006/mlh/20jan06 --security=1
             </pre>
             <h4><a name="addFileToExp" id="addFileToExp"></a>Add a new file to an experiment</h4>
             <p>If you want to add a new file to an existing Madrigal experiment, use addFileToExp.py, located in <em>madroot</em>/bin. You can use this script to add a completely new file, or to update an existing one. It you update an existing file and want to change the status of the older file to history or variant, use the  script <a href="#changeFileStatus">changeFileStatus.py</a>. </p>
             <p>Usage: </p>
             <pre>
             addFileToExp.py is a script used to add a new Madrigal file to an
             existing experiment.  Information such as the duration of the
             experiment is updated by analyzing the file.
             With Madrigal 3, accepts either old CEDAR database format files, or CEDAR Madrigal
             Hdf5 files.
             Required arguments:
                 --madFilename - full path to the complete Madrigal file. Basename will
                                 be maintained. If old CEDAR databse format, .hdf5 will
                                 be appended
                 --expDir - full path to experiment directory. Example:
                            "/opt/madrigal/experiments/1998/mlh/20jan98"
                 --permission - 0 for public, 1 for private (restricted to certain IP range)
                 --fileDesc - file decription
             Optional arguments:
                 --category - 1=default, 2=variant, or 3=history If this argument is missing,
 (default) used.
                 --kindat  -  Set file kindat independently from one (or more) in file
                 --skipNotify - if this flag set (no arguments), registered users will NOT be notified
                                of this change.  The default is to email all registered users.
                 --fileAnalyst - set file analyst name for this file.  This will default to blank.
                 --fileAnalystEmail - set file analyst email for this file.  This will default to blank.
             </pre>
             <p>Example: If you want to add the new file /tmp/mlh060120g.002.hdf to an existing experiment, you would enter:</p>
             <pre>/opt/madrigal/bin/createExpWithFile.py --madFilename=/tmp/mlh060120g.002.hdf5 \
                  --expDir=/opt/madrigal/experiments/2006/mlh/20jan06 --permission=0 \
                  --fileDesc=&quot;alternative analysis&quot;  --category=1
             </pre>
             <p>If you are adding an old style Cedar databse file /tmp/mlh060120g.002 to an existing experiment, you would enter the same command except without the .hdf5 extension:</p>
             <pre>/opt/madrigal/bin/createExpWithFile.py --madFilename=/tmp/mlh060120g.002 \
                  --expDir=/opt/madrigal/experiments/2006/mlh/20jan06 --permission=0 \
                  --fileDesc=&quot;alternative analysis&quot;  --category=1
             </pre>
             <h4><a name="updateFileInExp" id="updateFileInExp"></a>Modify an existing file in an experiment</h4>
             <p>If you want to modify an existing file in a Madrigal experiment, use updateFileInExp.py, located in <em>madroot</em>/bin. Note that if the modification in the file is significant, it is preferable to make the old file a history file using <a href="#changeFileStatus">changeFileStatus.py</a>, and to add a new file with a different name using <a href="#addFileToExp">addFileToExp.py</a>.</p>
             <p>Usage: </p>
             <pre>updateFileInExp.py is a script used to update an existing Madrigal file in an
                existing experiment. Information such as the duration of the
                experiment is updated by analyzing the file. This script is use to replace
                an existing Madrigal file. Use addFileToExp.py to add a new file, and
              changeFileStatus.py to change any file attribute.</pre>
             <pre>Required arguments:</pre>
             <pre> --madFilename - full path to the new version of the Madrigal file. Basename will
                be maintained.</pre>
             <pre> --expDir - full path to experiment directory. Example:
              &quot;/opt/madrigal/experiments/1998/mlh/20jan98&quot;
             </pre>
             <p>Example: To modify the existing file /opt/madrigal/experiments/2002/01oct02/mlh021001a.000.hdf5 with the file /tmp/mlh021001a.000.hdf5, you would enter:</p>
             <pre>/opt/madrigal/bin/updateFileInExp.py --madFilename=/tmp/mlh021001a.000.hdf5 \
              --expDir=/opt/madrigal/experiments/2002/01oct02 </pre>
             <h4><a name="changeFileStatus" id="changeFileStatus"></a>Change the status of a file in an experiment</h4>
             <p>If you want to change the status of any existing file in an experiment, such as to make a default file into a history file, use changeFileStatus.py, located in <em>madroot</em>/bin. Usage: </p>
             <pre>
             changeFileStatus.py is a script used to change the status of an
             existing Madrigal file.  The file permission, the file description,
             or the file category can be changed.
             Required arguments:
                 --filename - basename of existing Madrigal file.
                 --expDir - full path to experiment directory. Example:
                            "/opt/madrigal/experiments/1998/mlh/20jan98"
             Optional arguments - set these to change a file attribute:
                 --permission - 0 for public, 1 for private (restricted to certain IP range)
                 --fileDesc - file decription
                 --category - 1=default, 2=variant, 3=history, or 4=realtime
                 --fileAnalyst - set file analyst name for this file.
                 --fileAnalystEmail - set file analyst email for this file.
             </pre>
             <p>Example: If you want to change the status of /opt/madrigal/experiments/2002/01oct02/mlh021001a.000.hdf5 to be a history file, you would enter:</p>
             <pre>
             /opt/madrigal/bin/changeFileStatus.py --filename=mlh021001a.000.hdf5 \
                 --expDir=/opt/madrigal/experiments/2002/01oct02 \
                 --category=3</pre>
             <h4><a name="removeFileFromExp" id="removeFileFromExp"></a>Remove a file from an experiment</h4>
             <p>To completely remove a file from an existing experiment, rather than simply make it a history file, use removeFileFromExp.py, located in <em>madroot</em>/bin. Usage: </p>
             <pre>
             removeFileFromExp.py is a script used to remove an existing Madrigal file from an
             existing experiment. Information such as the duration of the
              experiment is updated by analyzing the remaining files. </pre>
             <pre>Required arguments:</pre>
             <pre> --filename - basename of the Madrigal file to be removed.</pre>
             <pre> --expDir - full path to experiment directory. Example:
              &quot;/opt/madrigal/experiments/1998/mlh/20jan98&quot;
              </pre>
             <p>Example: To remove the file /opt/madrigal/experiments/2002/01oct02/mlh021001a.000.hdf5, you would enter:</p>
             <pre>/opt/madrigal/bin/removeFileFromExp.py --filename=mlh021001a.000.hdf5 \
                  --expDir=/opt/madrigal/experiments/2002/01oct02
             </pre>
             <h4><a name="auxillary" id="auxillary"></a>Adding auxiliary plots and information to a Madrigal experiment</h4>
             <p>Since Madrigal is a web-based application, you can also display auxiliary plots and information about your experiment as web pages. If you add additional web documents according to the rules below, these documents will also show up through the standard Madrigal interface. </p>
             <ul>
               <li>Subdirectories containing an html file named index.html . Links to these files will show up the experiment page. The
                   page title will be displayed as a link.</li>
               <li>Html pages in the main directory, and again links to these files will show up the experiment page. The
                   page title will be displayed as a link.</li>
               <li>Plots or other files related to individual records in the dataset. Links to these files appear next to the appropriate record in the summarizeCedarFile.cgi page. These files must be located in the subdirectory "plots/[file name]/records" under the experiment directory, where &quot;file name&quot; is the base name of the experiment record.. In order for the script to determine which file goes with which record, the files must include a five digit number somewhere in its name. For example, plot00027.gif would appear as a link next to record 27 in summarizeCedarFile.cgi. More than one file can be associated with a given record.
                 <ul>
                   <li>If you want to create individual record plots for an incoherent scatter radar with the standard parameters Te, Ti, Ne, and ion velocity, simply run the script createRecordPlots.py. For example, to create all the individual record plots for the Madrigal file mlh980120g.001.hdf5, you would run a command similar to the following:</li>
                 </ul>
                 <blockquote>
                   <pre>/opt/madrigal/bin/createRecordPlots.py /opt/madrigal/experiments/1998/mlh/20jan98/mil980120g.001.hdf5</pre>
                 </blockquote>
               </li>
             </ul>
-            <p>As an example of plots associated with individual records, lets say you have a Madrigal experiment in the directory /opt/madrigal/experiments/2002/01oct02, with a file named mlh021001a.001.hdf5. If this file had 10 records, you could then create 10 plot files called plot001.png through plot010.png. You would then create the subdirectories plots/mlh021001a.001.hdf5/ under the main directory /opt/madrigal/experiments/2002/01oct02/, and put those 10 plot files there. </p>
+            <p>As an example of plots associated with individual records, lets say you have a Madrigal experiment in the directory /opt/madrigal/experiments/2002/01oct02, with a file named mlh021001a.001.hdf5. If this file had 10 records, you could then create 10 plot files called plot001.png' %} through plot010.png' %}. You would then create the subdirectories plots/mlh021001a.001.hdf5/ under the main directory /opt/madrigal/experiments/2002/01oct02/, and put those 10 plot files there. </p>
             <p><br>
             </p>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_createFiles.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_createFiles.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_other.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_other.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Creating and modifying Madrigal experiments<!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_createFiles.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Creating Madrigal data files <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_other.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Other admin tasks <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/ad_createFiles.html +8 -8

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>Creating and editing Madrigal data files </title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" -->
               <style type="text/css">
             td.linenos { background-color: #f0f0f0; padding-right: 10px; }
             span.lineno { background-color: #f0f0f0; padding: 0 5px 0 5px; }
             pre { line-height: 125%; }
             body .hll { background-color: #ffffcc }
             body  { background: #f8f8f8; }
             body .c { color: #408080; font-style: italic } /* Comment */
             body .err { border: 1px solid #FF0000 } /* Error */
             body .k { color: #008000; font-weight: bold } /* Keyword */
             body .o { color: #666666 } /* Operator */
             body .ch { color: #408080; font-style: italic } /* Comment.Hashbang */
             body .cm { color: #408080; font-style: italic } /* Comment.Multiline */
             body .cp { color: #BC7A00 } /* Comment.Preproc */
             body .cpf { color: #408080; font-style: italic } /* Comment.PreprocFile */
             body .c1 { color: #408080; font-style: italic } /* Comment.Single */
             body .cs { color: #408080; font-style: italic } /* Comment.Special */
             body .gd { color: #A00000 } /* Generic.Deleted */
             body .ge { font-style: italic } /* Generic.Emph */
             body .gr { color: #FF0000 } /* Generic.Error */
             body .gh { color: #000080; font-weight: bold } /* Generic.Heading */
             body .gi { color: #00A000 } /* Generic.Inserted */
             body .go { color: #888888 } /* Generic.Output */
             body .gp { color: #000080; font-weight: bold } /* Generic.Prompt */
             body .gs { font-weight: bold } /* Generic.Strong */
             body .gu { color: #800080; font-weight: bold } /* Generic.Subheading */
             body .gt { color: #0044DD } /* Generic.Traceback */
             body .kc { color: #008000; font-weight: bold } /* Keyword.Constant */
             body .kd { color: #008000; font-weight: bold } /* Keyword.Declaration */
             body .kn { color: #008000; font-weight: bold } /* Keyword.Namespace */
             body .kp { color: #008000 } /* Keyword.Pseudo */
             body .kr { color: #008000; font-weight: bold } /* Keyword.Reserved */
             body .kt { color: #B00040 } /* Keyword.Type */
             body .m { color: #666666 } /* Literal.Number */
             body .s { color: #BA2121 } /* Literal.String */
             body .na { color: #7D9029 } /* Name.Attribute */
             body .nb { color: #008000 } /* Name.Builtin */
             body .nc { color: #0000FF; font-weight: bold } /* Name.Class */
             body .no { color: #880000 } /* Name.Constant */
             body .nd { color: #AA22FF } /* Name.Decorator */
             body .ni { color: #999999; font-weight: bold } /* Name.Entity */
             body .ne { color: #D2413A; font-weight: bold } /* Name.Exception */
             body .nf { color: #0000FF } /* Name.Function */
             body .nl { color: #A0A000 } /* Name.Label */
             body .nn { color: #0000FF; font-weight: bold } /* Name.Namespace */
             body .nt { color: #008000; font-weight: bold } /* Name.Tag */
             body .nv { color: #19177C } /* Name.Variable */
             body .ow { color: #AA22FF; font-weight: bold } /* Operator.Word */
             body .w { color: #bbbbbb } /* Text.Whitespace */
             body .mb { color: #666666 } /* Literal.Number.Bin */
             body .mf { color: #666666 } /* Literal.Number.Float */
             body .mh { color: #666666 } /* Literal.Number.Hex */
             body .mi { color: #666666 } /* Literal.Number.Integer */
             body .mo { color: #666666 } /* Literal.Number.Oct */
             body .sb { color: #BA2121 } /* Literal.String.Backtick */
             body .sc { color: #BA2121 } /* Literal.String.Char */
             body .sd { color: #BA2121; font-style: italic } /* Literal.String.Doc */
             body .s2 { color: #BA2121 } /* Literal.String.Double */
             body .se { color: #BB6622; font-weight: bold } /* Literal.String.Escape */
             body .sh { color: #BA2121 } /* Literal.String.Heredoc */
             body .si { color: #BB6688; font-weight: bold } /* Literal.String.Interpol */
             body .sx { color: #008000 } /* Literal.String.Other */
             body .sr { color: #BB6688 } /* Literal.String.Regex */
             body .s1 { color: #BA2121 } /* Literal.String.Single */
             body .ss { color: #19177C } /* Literal.String.Symbol */
             body .bp { color: #008000 } /* Name.Builtin.Pseudo */
             body .vc { color: #19177C } /* Name.Variable.Class */
             body .vg { color: #19177C } /* Name.Variable.Global */
             body .vi { color: #19177C } /* Name.Variable.Instance */
             body .il { color: #666666 } /* Literal.Number.Integer.Long */
               </style>
             <!-- InstanceEndEditable -->
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="admin.html" --><!-- InstanceParam name="href_next_top" type="text" value="ad_createExp.html" --><!-- InstanceParam name="href_back_top" type="text" value="ad_experiments.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="ad_experiments.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="ad_createExp.html" --><!-- InstanceParam name="href_prev_top" type="text" value="ad_experiments.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="ad_createExp.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="ad_experiments.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="ad_createExp.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_experiments.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_experiments.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_createExp.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_createExp.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Creating and editing Madrigal data files <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_experiments.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Madrigal data organization <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_createExp.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Creating Madrigal experiments <!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">Creating and editing Madrigal data files</h1>
-            <p>A key element in administering the Madrigal database is the ability to create and edit Madrigal data files. An ambitious Madrigal administrator could  read the <a href="/static/CEDARMadrigalHdf5Format.pdf" target="_blank">CEDAR Madrigal Hdf5 format</a> description and write their own code from scratch. However, Madrigal provides API's and examples in two languages, Python and Matlab, to make this chore much, much easier. This section describes how to create Madrigal files using each of those two languages.</p>
+            <p>A key element in administering the Madrigal database is the ability to create and edit Madrigal data files. An ambitious Madrigal administrator could  read the <a href="{% static 'CEDARMadrigalHdf5Format.pdf" target="_blank">CEDAR Madrigal Hdf5 format</a> description and write their own code from scratch. However, Madrigal provides API's and examples in two languages, Python and Matlab, to make this chore much, much easier. This section describes how to create Madrigal files using each of those two languages.</p>
             <ul>
               <li><a href="#python">Python</a></li>
               <li><a href="#matlab">Matlab</a></li>
             </ul>
             <h2><a name="python" id="python"></a>Python</h2>
             <h3>How have things changed with Madrigal 3?</h3>
             <p>For the most part, python scripts that created Madrigal 2 files will only need to be slightly modified to create Madrigal 3 files. With Madrigal 3, the independent parameters (excluding time) must be explicitly declared. This is because Madrigal 3 files contain both a table layout, and (if there are independent parameters) a grid layout, with the number of dimensions = 1 + (number of independent parameters). The first dimension is always time. The independent parameters are declared in the MadrigalDataRecord init method.</p>
             <p>The second small change is the addition of an optional argument <em>arraySplitParms</em>. If one of more array splitting parameters are given, then multiple grids of data will be created, one grid for each unique combination of values of the array splitting parameters. The idea behind this argument is to make the gridded data less sparse and more useful to the end user. For example, a phased array incoherent scatter radar such as PFISR that simultaneously measures along different beams would split its arrays by the parameter beam_id. This would make the gridded data both dense and more user friendly - a user could simply open the data for the beam of interest.</p>
             <h2>Instructions</h2>
             <p>This section gives an introduction to using the madrigal python API to create new Cedar Madrigal Hdf5 files, and to edit existing Cedar Madrigal Hdf5 files. Examples are given of  <a href="#create"> creating new normal-sized files, </a> <a href="#create_large">creating new large files</a>, and <a href="#edit">editing existing files.</a> Users creating Cedar Madrigal Hdf5 files with python can choose between two sightly different patterns, one which maximizes speed but could have memory issues with very large files, and another that limits memory use with very large files, but is somewhat slower. Complete <a href="madrigal/cedar.m.html">documentation</a> is available as part of the Madrigal Python API documentation. </p>
             <p>The python cedar module was written to simplify the task of creating Cedar Madrigal Hdf5 files as much as possible. The user of this module only needs to know the following about the Cedar format: </p>
             <ul>
               <li>Cedar Madrigal Hdf5 files are made up of  metadata and data records. Each data record consists of a measurement made with a single instrument over a single interval of time.</li>
               <li>All parameters in Cedar Madrigal Hdf5 files are defined in the standard. Contact Bill Rideout if you can't find a parameter you need; more can be added.</li>
               <li>Each data record in a Cedar Madrigal Hdf5 file has the same parameters. These parameters are either scalar (a single measurement per data record), or vectors (called 2D sometimes for historical reasons, but there is a limit of 5 for the number of independent spatial parameters).</li>
               <li>If there are vector parameters, then the parameters which serve as independent parameters must be specified. Up to 5 may be given.</li>
               <li>The Cedar Madrigal Hdf5 always contains a Table Layout, where the data is listed in a flat table, which means the scalar parameters are repeated for each row in a single data record.</li>
               <li>If there are vector parameters, then there will also be one or more Array Layouts. The array layout is a multidimensional layout, with time in one dimension, and one dimension for each independent parameter. When you create this file, you can also choose to specify parameters used to split these arrays. For example, incoherent scatter radar taken with radars that measure different beams over the same time period may decide to have separate arrays for each beam code.</li>
               <li>A list of Cedar parameters and their units can be found under<em> Access metadata</em> menu item from any Madrigal 3 site. A complete description of each parameter can also be seen by clicking on any parameter name. Parameters can be referred to in the python API either by case-insensitive mnemonics (e.g., "Gdalt") or by integer id. Parameters are set either to float, integer, or string values, according to their type, or to the special values 'missing', 'assumed', or 'knownbad' may be used for numeric values. The values 'assumed' and 'knownbad' can only be applied to error parameters.</li>
               <li>In addition to data records, the Cedar format also allows two types of records that contain human-readable descriptions of the data: a catalog record and a header record. They are two only for historical reasons; each contains different metadata fields.</li>
             </ul>
             <blockquote>
               <h3>MadrigalCedarFile</h3>
             </blockquote>
             <p>The high level object in the cedar module is <a href="madrigal/cedar.m.html"> MadrigalCedarFile</a>. This class emulates a python list, and so users may treat it just like a python list. The restriction enforced is that all items in the list must be either <a href="madrigal/cedar.m.html">MadrigalCatalogRecords</a>, <a href="madrigal/cedar.m.html">MadrigalHeaderRecords</a>, or <a href="madrigal/cedar.m.html">MadrigalDataRecords</a>. Each of these three classes supports the method getType(), which returns 'catalog', 'header', and 'data', respectively.</p>
             <blockquote>
               <a name="catHeadRec" id="catHeadRec"></a><h3>Using Python to add catalog and header records.</h3>
             </blockquote>
             <p>Cedar catalog and header records can be difficult to create.  With the cedar module
                 <a href="madrigal/cedar.m.html"> CatalogHeaderCreator</a>, creating
                 these records should now be much easier.  Catalog and header records contain a lot of information
                 that can be deduced from the data - this includes which parameters are present, minimum and maximums
                 of certain parameters, and start and stop times.  The only parts of the catalog or header record that
                 can't be determined automatically are some optional descriptive text fields.  With this new module,
                 you simply pass in strings of any length if you want to fill in one of those optional descriptive
                 text fields - the module will handle all formating for you.</p>
             <p>Here's a list of the optional descriptive text fields for a <i>catalog</i> record:</p>
             <ul>
               <li><b>principleInvestigator: </b>names of responsible Principal Investigator(s) or others knowledgeable
                                               about the experiment</li>
               <li><b>expPurpose: </b>brief description of the experiment purpose</li>
               <li><b>expMode: </b>further elaboration of meaning of experiment mode; e.g. antenna patterns and
                                   pulse sequences</li>
               <li><b>cycleTime: </b>minutes for one full measurement cycle (this needs to be a number)</li>
               <li><b>correlativeExp: </b>any correlative experiments (experiments with related data)</li>
               <li><b>sciRemarks: </b>scientific remarks</li>
               <li><b>instRemarks: </b>instrument remarks</li>
             </ul>
             <p>Here's a list of the optional descriptive text fields for a <i>header</i> record:</p>
             <ul>
               <li><b>kindatDesc: </b>description of how this data was analyzed (the kind of data)</li>
               <li><b>analyst: </b>name of person(s) who analyzed this data</li>
               <li><b>comments: </b>additional comments about data (describe any instrument-specific parameters)</li>
               <li><b>history: </b>a description of the history of the processing of this file</li>
             </ul>
             <p><a name="create" id="create"></a> </p>
             <blockquote>
               <h3>Creating a new normal-sized file example</h3>
             </blockquote>
             <div class="highlight">
               <pre><span></span><span class="sd">&quot;&quot;&quot;createSample.py shows an example of creating an entirely new Madrigal</span>
             <span class="sd">file using the Python cedar module.  In particular, it creates a file with</span>
             <span class="sd">a catalog record, a header record, and two data records.  The data records</span>
             <span class="sd">contain two 1D parameters (System temperature - SYSTMP and Transmitter</span>
             <span class="sd">Frequency TFREQ) and five 2D parameters (GDALT, GDLAT, GLON, and TR, and DTR)</span>
             <span class="sd">The independent spatial parameter in this example is just GDALT.</span>
             <span class="sd">This example uses the normal-sized pattern for speed, where normal sized is considered
             less than 3000 records</span><span class="sd">.  In that pattern, all the records are appended to the MadrigalCedarFile </span>
             <span class="sd">object, and then write is called to write everything to file at once, including both the Table and </span>
             <span class="sd">Array Layouts.</span>
             <span class="sd">$Id$</span>
             <span class="sd">&quot;&quot;&quot;</span>
             <span class="kn">import</span> <span class="nn">os</span><span class="o">,</span> <span class="nn">os.path</span>
             <span class="kn">import</span> <span class="nn">types</span>
             <span class="kn">import</span> <span class="nn">datetime</span>
             <span class="kn">import</span> <span class="nn">madrigal.metadata</span>
             <span class="kn">import</span> <span class="nn">madrigal.cedar</span>
             <span class="c1">################# sample data #################</span>
             <span class="n">kinst</span> <span class="o">=</span> <span class="mi">30</span> <span class="c1"># instrument identifier of Millstone Hill ISR</span>
             <span class="n">kindat</span> <span class="o">=</span> <span class="mi">3408</span> <span class="c1"># id of kind of data processing</span>
             <span class="n">nrow</span> <span class="o">=</span> <span class="mi">5</span> <span class="c1"># all data records have 5 2D rows</span>
             <span class="n">SYSTMP</span> <span class="o">=</span> <span class="p">(</span><span class="mf">120.0</span><span class="p">,</span> <span class="mf">122.0</span><span class="p">)</span>
             <span class="n">TFREQ</span> <span class="o">=</span> <span class="p">(</span><span class="mf">4.4E8</span><span class="p">,</span> <span class="mf">4.4E8</span><span class="p">)</span>
             <span class="n">GDALT</span> <span class="o">=</span> <span class="p">((</span><span class="mf">70.0</span><span class="p">,</span> <span class="mf">100.0</span><span class="p">,</span> <span class="mf">200.0</span><span class="p">,</span> <span class="mf">300.0</span><span class="p">,</span> <span class="mf">400.0</span><span class="p">),</span>
                      <span class="p">(</span><span class="mf">70.0</span><span class="p">,</span> <span class="mf">100.0</span><span class="p">,</span> <span class="mf">200.0</span><span class="p">,</span> <span class="mf">300.0</span><span class="p">,</span> <span class="mf">400.0</span><span class="p">))</span>
             <span class="n">GDLAT</span> <span class="o">=</span> <span class="p">((</span><span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">),</span>
                      <span class="p">(</span><span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">))</span>
             <span class="n">GLON</span>  <span class="o">=</span> <span class="p">((</span><span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">),</span>
                      <span class="p">(</span><span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">))</span>
             <span class="n">TR</span>    <span class="o">=</span> <span class="p">((</span><span class="s1">&#39;missing&#39;</span><span class="p">,</span> <span class="mf">1.0</span><span class="p">,</span> <span class="mf">1.0</span><span class="p">,</span> <span class="mf">2.3</span><span class="p">,</span> <span class="mf">3.0</span><span class="p">),</span>
                      <span class="p">(</span><span class="s1">&#39;missing&#39;</span><span class="p">,</span> <span class="mf">1.0</span><span class="p">,</span> <span class="mf">1.7</span><span class="p">,</span> <span class="mf">2.4</span><span class="p">,</span> <span class="mf">3.1</span><span class="p">))</span>
             <span class="n">DTR</span>   <span class="o">=</span> <span class="p">((</span><span class="s1">&#39;missing&#39;</span><span class="p">,</span> <span class="s1">&#39;assumed&#39;</span><span class="p">,</span> <span class="s1">&#39;assumed&#39;</span><span class="p">,</span> <span class="mf">0.3</span><span class="p">,</span> <span class="mf">0.7</span><span class="p">),</span>
                      <span class="p">(</span><span class="s1">&#39;missing&#39;</span><span class="p">,</span> <span class="s1">&#39;assumed&#39;</span><span class="p">,</span> <span class="mf">0.7</span><span class="p">,</span> <span class="mf">0.4</span><span class="p">,</span> <span class="mf">0.5</span><span class="p">))</span>
             <span class="c1">################# end sample data #################</span>
             <span class="n">newFile</span> <span class="o">=</span> <span class="s1">&#39;/tmp/testCedar.hdf5&#39;</span>
             <span class="c1"># create a new Madrigal file </span>
             <span class="n">cedarObj</span> <span class="o">=</span> <span class="n">madrigal</span><span class="o">.</span><span class="n">cedar</span><span class="o">.</span><span class="n">MadrigalCedarFile</span><span class="p">(</span><span class="n">newFile</span><span class="p">,</span> <span class="bp">True</span><span class="p">)</span>
             <span class="c1"># create all data records -  each record lasts one minute</span>
             <span class="n">startTime</span> <span class="o">=</span> <span class="n">datetime</span><span class="o">.</span><span class="n">datetime</span><span class="p">(</span><span class="mi">2005</span><span class="p">,</span> <span class="mi">3</span><span class="p">,</span> <span class="mi">19</span><span class="p">,</span> <span class="mi">12</span><span class="p">,</span> <span class="mi">30</span><span class="p">,</span> <span class="mi">0</span><span class="p">,</span> <span class="mi">0</span><span class="p">)</span>
             <span class="n">recTime</span> <span class="o">=</span> <span class="n">datetime</span><span class="o">.</span><span class="n">timedelta</span><span class="p">(</span><span class="mi">0</span><span class="p">,</span><span class="mi">60</span><span class="p">)</span>
             <span class="k">for</span> <span class="n">recno</span> <span class="ow">in</span> <span class="nb">range</span><span class="p">(</span><span class="mi">2</span><span class="p">):</span>
                 <span class="n">endTime</span> <span class="o">=</span> <span class="n">startTime</span> <span class="o">+</span> <span class="n">recTime</span>
                 <span class="n">dataRec</span> <span class="o">=</span> <span class="n">madrigal</span><span class="o">.</span><span class="n">cedar</span><span class="o">.</span><span class="n">MadrigalDataRecord</span><span class="p">(</span><span class="n">kinst</span><span class="p">,</span>
                                                             <span class="n">kindat</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">year</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">month</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">day</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">hour</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">minute</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">second</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">microsecond</span><span class="o">/</span><span class="mi">10000</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">year</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">month</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">day</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">hour</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">minute</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">second</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">microsecond</span><span class="o">/</span><span class="mi">10000</span><span class="p">,</span>
                                                             <span class="p">(</span><span class="s1">&#39;systmp&#39;</span><span class="p">,</span> <span class="s1">&#39;tfreq&#39;</span><span class="p">),</span>
                                                             <span class="p">(</span><span class="s1">&#39;gdalt&#39;</span><span class="p">,</span> <span class="s1">&#39;gdlat&#39;</span><span class="p">,</span> <span class="s1">&#39;glon&#39;</span><span class="p">,</span> <span class="s1">&#39;tr&#39;</span><span class="p">,</span> <span class="s1">&#39;dtr&#39;</span><span class="p">),</span>
                                                             <span class="n">nrow</span><span class="p">,</span> <span class="n">ind2DList</span><span class="o">=</span><span class="p">[</span><span class="s1">&#39;gdalt&#39;</span><span class="p">])</span>
                 <span class="c1"># set 1d values</span>
                 <span class="n">dataRec</span><span class="o">.</span><span class="n">set1D</span><span class="p">(</span><span class="s1">&#39;systmp&#39;</span><span class="p">,</span> <span class="n">SYSTMP</span><span class="p">[</span><span class="n">recno</span><span class="p">])</span>
                 <span class="n">dataRec</span><span class="o">.</span><span class="n">set1D</span><span class="p">(</span><span class="s1">&#39;tfreq&#39;</span><span class="p">,</span> <span class="n">TFREQ</span><span class="p">[</span><span class="n">recno</span><span class="p">])</span>
                 <span class="c1"># set 2d values</span>
                 <span class="k">for</span> <span class="n">n</span> <span class="ow">in</span> <span class="nb">range</span><span class="p">(</span><span class="n">nrow</span><span class="p">):</span>
                     <span class="n">dataRec</span><span class="o">.</span><span class="n">set2D</span><span class="p">(</span><span class="s1">&#39;gdalt&#39;</span><span class="p">,</span> <span class="n">n</span><span class="p">,</span> <span class="n">GDALT</span><span class="p">[</span><span class="n">recno</span><span class="p">][</span><span class="n">n</span><span class="p">])</span>
                     <span class="n">dataRec</span><span class="o">.</span><span class="n">set2D</span><span class="p">(</span><span class="s1">&#39;gdlat&#39;</span><span class="p">,</span> <span class="n">n</span><span class="p">,</span> <span class="n">GDLAT</span><span class="p">[</span><span class="n">recno</span><span class="p">][</span><span class="n">n</span><span class="p">])</span>
                     <span class="n">dataRec</span><span class="o">.</span><span class="n">set2D</span><span class="p">(</span><span class="s1">&#39;glon&#39;</span><span class="p">,</span>  <span class="n">n</span><span class="p">,</span> <span class="n">GLON</span><span class="p">[</span><span class="n">recno</span><span class="p">][</span><span class="n">n</span><span class="p">])</span>
                     <span class="n">dataRec</span><span class="o">.</span><span class="n">set2D</span><span class="p">(</span><span class="s1">&#39;tr&#39;</span><span class="p">,</span>    <span class="n">n</span><span class="p">,</span> <span class="n">TR</span><span class="p">[</span><span class="n">recno</span><span class="p">][</span><span class="n">n</span><span class="p">])</span>
                     <span class="n">dataRec</span><span class="o">.</span><span class="n">set2D</span><span class="p">(</span><span class="s1">&#39;dtr&#39;</span><span class="p">,</span>   <span class="n">n</span><span class="p">,</span> <span class="n">DTR</span><span class="p">[</span><span class="n">recno</span><span class="p">][</span><span class="n">n</span><span class="p">])</span>
                 <span class="c1"># append new data record</span>
                 <span class="n">cedarObj</span><span class="o">.</span><span class="n">append</span><span class="p">(</span><span class="n">dataRec</span><span class="p">)</span>
                 <span class="n">startTime</span> <span class="o">+=</span> <span class="n">recTime</span>
             <span class="c1"># write new file</span>
             <span class="n">cedarObj</span><span class="o">.</span><span class="n">write</span><span class="p">()</span>
             <span class="c1"># next, use the cedar.CatalogHeaderCreator class to add catalog and header </span>
             <span class="n">catHeadObj</span> <span class="o">=</span> <span class="n">madrigal</span><span class="o">.</span><span class="n">cedar</span><span class="o">.</span><span class="n">CatalogHeaderCreator</span><span class="p">(</span><span class="n">newFile</span><span class="p">)</span>
             <span class="n">catHeadObj</span><span class="o">.</span><span class="n">createCatalog</span><span class="p">(</span><span class="n">principleInvestigator</span><span class="o">=</span><span class="s2">&quot;John Holt&quot;</span><span class="p">,</span> <span class="n">sciRemarks</span><span class="o">=</span><span class="s2">&quot;Test data only - do not use&quot;</span><span class="p">)</span>
             <span class="n">catHeadObj</span><span class="o">.</span><span class="n">createHeader</span><span class="p">(</span><span class="n">analyst</span><span class="o">=</span><span class="s2">&quot;Bill Rideout&quot;</span><span class="p">,</span> <span class="n">comments</span><span class="o">=</span><span class="s2">&quot;Do not use this data&quot;</span><span class="p">)</span>
             <span class="n">catHeadObj</span><span class="o">.</span><span class="n">write</span><span class="p">()</span>
             </pre></div>
             <p><a name="create_large" id="create2"></a></p>
               <h3>Creating a new large file example</h3>
               <div class="highlight"><pre><span></span><span class="sd">&quot;&quot;&quot;createSampleLargeFile.py shows an example of creating an entirely new,</span>
             <span class="sd">very large Madrigal file using the Python cedar module.  </span>
             <span class="sd">In particular, it creates a file with</span>
             <span class="sd">a catalog record, a header record, and one hundred thousand data records.  Because this</span>
             <span class="sd">is a large file, it calls dump for every five hundred records, which writes all the data</span>
             <span class="sd">to file in the Table Layout.  This limits the memory footprint to just over 1GB.</span>
             <span class="sd">This example closes with a call to close(), which triggers the </span>
             <span class="sd">creation of Array Layout, which again keeps the memory footprint down by only reading</span>
             <span class="sd">in a set number of records at a time.</span>
             <span class="sd">The data records</span>
             <span class="sd">contain two 1D parameters (System temperature - SYSTMP and Transmitter</span>
             <span class="sd">Frequency TFREQ) and five 2D parameters (GDALT, GDLAT, GLON, and TR, and DTR)</span>
             <span class="sd">The independent spatial parameter in this example is just GDALT.</span>
             <span class="sd">$Id$</span>
             <span class="sd">&quot;&quot;&quot;</span>
             <span class="kn">import</span> <span class="nn">os</span><span class="o">,</span> <span class="nn">os.path</span>
             <span class="kn">import</span> <span class="nn">types</span>
             <span class="kn">import</span> <span class="nn">datetime</span>
             <span class="kn">import</span> <span class="nn">madrigal.metadata</span>
             <span class="kn">import</span> <span class="nn">madrigal.cedar</span>
             <span class="c1">################# sample data #################</span>
             <span class="n">kinst</span> <span class="o">=</span> <span class="mi">30</span> <span class="c1"># instrument identifier of Millstone Hill ISR</span>
             <span class="n">kindat</span> <span class="o">=</span> <span class="mi">3408</span> <span class="c1"># id of kind of data processing</span>
             <span class="n">nrow</span> <span class="o">=</span> <span class="mi">5</span> <span class="c1"># all data records have 5 2D rows</span>
             <span class="n">SYSTMP</span> <span class="o">=</span> <span class="p">(</span><span class="mf">120.0</span><span class="p">,</span> <span class="mf">122.0</span><span class="p">)</span>
             <span class="n">TFREQ</span> <span class="o">=</span> <span class="p">(</span><span class="mf">4.4E8</span><span class="p">,</span> <span class="mf">4.4E8</span><span class="p">)</span>
             <span class="n">GDALT</span> <span class="o">=</span> <span class="p">((</span><span class="mf">70.0</span><span class="p">,</span> <span class="mf">100.0</span><span class="p">,</span> <span class="mf">200.0</span><span class="p">,</span> <span class="mf">300.0</span><span class="p">,</span> <span class="mf">400.0</span><span class="p">),</span>
                      <span class="p">(</span><span class="mf">70.0</span><span class="p">,</span> <span class="mf">100.0</span><span class="p">,</span> <span class="mf">200.0</span><span class="p">,</span> <span class="mf">300.0</span><span class="p">,</span> <span class="mf">400.0</span><span class="p">))</span>
             <span class="n">GDLAT</span> <span class="o">=</span> <span class="p">((</span><span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">),</span>
                      <span class="p">(</span><span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">,</span> <span class="mf">42.0</span><span class="p">))</span>
             <span class="n">GLON</span>  <span class="o">=</span> <span class="p">((</span><span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">),</span>
                      <span class="p">(</span><span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">,</span> <span class="mf">270.0</span><span class="p">))</span>
             <span class="n">TR</span>    <span class="o">=</span> <span class="p">((</span><span class="s1">&#39;missing&#39;</span><span class="p">,</span> <span class="mf">1.0</span><span class="p">,</span> <span class="mf">1.0</span><span class="p">,</span> <span class="mf">2.3</span><span class="p">,</span> <span class="mf">3.0</span><span class="p">),</span>
                      <span class="p">(</span><span class="s1">&#39;missing&#39;</span><span class="p">,</span> <span class="mf">1.0</span><span class="p">,</span> <span class="mf">1.7</span><span class="p">,</span> <span class="mf">2.4</span><span class="p">,</span> <span class="mf">3.1</span><span class="p">))</span>
             <span class="n">DTR</span>   <span class="o">=</span> <span class="p">((</span><span class="s1">&#39;missing&#39;</span><span class="p">,</span> <span class="s1">&#39;assumed&#39;</span><span class="p">,</span> <span class="s1">&#39;assumed&#39;</span><span class="p">,</span> <span class="mf">0.3</span><span class="p">,</span> <span class="mf">0.7</span><span class="p">),</span>
                      <span class="p">(</span><span class="s1">&#39;missing&#39;</span><span class="p">,</span> <span class="s1">&#39;assumed&#39;</span><span class="p">,</span> <span class="mf">0.7</span><span class="p">,</span> <span class="mf">0.4</span><span class="p">,</span> <span class="mf">0.5</span><span class="p">))</span>
             <span class="c1">################# end sample data #################</span>
             <span class="n">newFile</span> <span class="o">=</span> <span class="s1">&#39;/tmp/testCedar.hdf5&#39;</span>
             <span class="k">try</span><span class="p">:</span>
                 <span class="n">os</span><span class="o">.</span><span class="n">remove</span><span class="p">(</span><span class="n">newFile</span><span class="p">)</span>
             <span class="k">except</span><span class="p">:</span>
                 <span class="k">pass</span>
             <span class="c1"># create a new Madrigal file </span>
             <span class="n">cedarObj</span> <span class="o">=</span> <span class="n">madrigal</span><span class="o">.</span><span class="n">cedar</span><span class="o">.</span><span class="n">MadrigalCedarFile</span><span class="p">(</span><span class="n">newFile</span><span class="p">,</span> <span class="bp">True</span><span class="p">)</span>
             <span class="c1"># create all data records -  each record lasts one minute</span>
             <span class="n">startTime</span> <span class="o">=</span> <span class="n">datetime</span><span class="o">.</span><span class="n">datetime</span><span class="p">(</span><span class="mi">2005</span><span class="p">,</span> <span class="mi">3</span><span class="p">,</span> <span class="mi">19</span><span class="p">,</span> <span class="mi">12</span><span class="p">,</span> <span class="mi">30</span><span class="p">,</span> <span class="mi">0</span><span class="p">,</span> <span class="mi">0</span><span class="p">)</span>
             <span class="n">recTime</span> <span class="o">=</span> <span class="n">datetime</span><span class="o">.</span><span class="n">timedelta</span><span class="p">(</span><span class="mi">0</span><span class="p">,</span><span class="mi">4</span><span class="p">)</span>
             <span class="k">for</span> <span class="n">recno</span> <span class="ow">in</span> <span class="nb">range</span><span class="p">(</span><span class="mi">100000</span><span class="p">):</span>
                 <span class="n">endTime</span> <span class="o">=</span> <span class="n">startTime</span> <span class="o">+</span> <span class="n">recTime</span>
                 <span class="n">dataRec</span> <span class="o">=</span> <span class="n">madrigal</span><span class="o">.</span><span class="n">cedar</span><span class="o">.</span><span class="n">MadrigalDataRecord</span><span class="p">(</span><span class="n">kinst</span><span class="p">,</span>
                                                             <span class="n">kindat</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">year</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">month</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">day</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">hour</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">minute</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">second</span><span class="p">,</span>
                                                             <span class="n">startTime</span><span class="o">.</span><span class="n">microsecond</span><span class="o">/</span><span class="mi">10000</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">year</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">month</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">day</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">hour</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">minute</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">second</span><span class="p">,</span>
                                                             <span class="n">endTime</span><span class="o">.</span><span class="n">microsecond</span><span class="o">/</span><span class="mi">10000</span><span class="p">,</span>
                                                             <span class="p">(</span><span class="s1">&#39;systmp&#39;</span><span class="p">,</span> <span class="s1">&#39;tfreq&#39;</span><span class="p">),</span>
                                                             <span class="p">(</span><span class="s1">&#39;gdalt&#39;</span><span class="p">,</span> <span class="s1">&#39;gdlat&#39;</span><span class="p">,</span> <span class="s1">&#39;glon&#39;</span><span class="p">,</span> <span class="s1">&#39;tr&#39;</span><span class="p">,</span> <span class="s1">&#39;dtr&#39;</span><span class="p">),</span>
                                                             <span class="n">nrow</span><span class="p">,</span> <span class="n">ind2DList</span><span class="o">=</span><span class="p">[</span><span class="s1">&#39;gdalt&#39;</span><span class="p">])</span>
                 <span class="c1"># set 1d values</span>
                 <span class="n">dataRec</span><span class="o">.</span><span class="n">set1D</span><span class="p">(</span><span class="s1">&#39;systmp&#39;</span><span class="p">,</span> <span class="n">SYSTMP</span><span class="p">[</span><span class="n">recno</span> <span class="o">%</span> <span class="mi">2</span><span class="p">])</span>
                 <span class="n">dataRec</span><span class="o">.</span><span class="n">set1D</span><span class="p">(</span><span class="s1">&#39;tfreq&#39;</span><span class="p">,</span> <span class="n">TFREQ</span><span class="p">[</span><span class="n">recno</span> <span class="o">%</span> <span class="mi">2</span><span class="p">])</span>
                 <span class="c1"># set 2d values</span>
                 <span class="k">for</span> <span class="n">n</span> <span class="ow">in</span> <span class="nb">range</span><span class="p">(</span><span class="n">nrow</span><span class="p">):</span>
                     <span class="n">dataRec</span><span class="o">.</span><span class="n">set2D</span><span class="p">(</span><span class="s1">&#39;gdalt&#39;</span><span class="p">,</span> <span class="n">n</span><span class="p">,</span> <span class="n">GDALT</span><span class="p">[</span><span class="n">recno</span> <span class="o">%</span> <span class="mi">2</span><span class="p">][</span><span class="n">n</span><span class="p">])</span>
                     <span class="n">dataRec</span><span class="o">.</span><span class="n">set2D</span><span class="p">(</span><span class="s1">&#39;gdlat&#39;</span><span class="p">,</span> <span class="n">n</span><span class="p">,</span> <span class="n">GDLAT</span><span class="p">[</span><span class="n">recno</span> <span class="o">%</span> <span class="mi">2</span><span class="p">][</span><span class="n">n</span><span class="p">])</span>
                     <span class="n">dataRec</span><span class="o">.</span><span class="n">set2D</span><span class="p">(</span><span class="s1">&#39;glon&#39;</span><span class="p">,</span>  <span class="n">n</span><span class="p">,</span> <span class="n">GLON</span><span class="p">[</span><span class="n">recno</span> <span class="o">%</span> <span class="mi">2</span><span class="p">][</span><span class="n">n</span><span class="p">])</span>
                     <span class="n">dataRec</span><span class="o">.</span><span class="n">set2D</span><span class="p">(</span><span class="s1">&#39;tr&#39;</span><span class="p">,</span>    <span class="n">n</span><span class="p">,</span> <span class="n">TR</span><span class="p">[</span><span class="n">recno</span> <span class="o">%</span> <span class="mi">2</span><span class="p">][</span><span class="n">n</span><span class="p">])</span>
                     <span class="n">dataRec</span><span class="o">.</span><span class="n">set2D</span><span class="p">(</span><span class="s1">&#39;dtr&#39;</span><span class="p">,</span>   <span class="n">n</span><span class="p">,</span> <span class="n">DTR</span><span class="p">[</span><span class="n">recno</span> <span class="o">%</span> <span class="mi">2</span><span class="p">][</span><span class="n">n</span><span class="p">])</span>
                 <span class="c1"># append new data record</span>
                 <span class="n">cedarObj</span><span class="o">.</span><span class="n">append</span><span class="p">(</span><span class="n">dataRec</span><span class="p">)</span>
                 <span class="n">startTime</span> <span class="o">+=</span> <span class="n">recTime</span>
                 <span class="k">if</span> <span class="n">recno</span> <span class="o">%</span> <span class="mi">500</span> <span class="o">==</span> <span class="mi">0</span> <span class="ow">and</span> <span class="n">recno</span> <span class="o">&gt;</span> <span class="mi">0</span><span class="p">:</span>
                     <span class="n">cedarObj</span><span class="o">.</span><span class="n">dump</span><span class="p">()</span> <span class="c1"># this puts everything on disk and removes it from RAM</span>
                 <span class="k">if</span> <span class="n">recno</span> <span class="o">%</span> <span class="mi">10000</span> <span class="o">==</span> <span class="mi">0</span><span class="p">:</span>
                     <span class="c1"># give some feedback</span>
                     <span class="k">print</span><span class="p">(</span><span class="s1">&#39;At </span><span class="si">%i</span><span class="s1"> records&#39;</span> <span class="o">%</span> <span class="p">(</span><span class="n">recno</span><span class="p">))</span>
             <span class="c1"># finished adding new records</span>
             <span class="n">cedarObj</span><span class="o">.</span><span class="n">dump</span><span class="p">()</span> <span class="c1"># write whatever records are still in RAM</span>
             <span class="k">print</span><span class="p">(</span><span class="s1">&#39;about to call close, which will also create the array layout&#39;</span><span class="p">)</span>
             <span class="n">cedarObj</span><span class="o">.</span><span class="n">close</span><span class="p">()</span> <span class="c1"># this triggers creation of the Array Layout, then closes file</span>
             <span class="k">print</span><span class="p">(</span><span class="s1">&#39;Finally, using CatalogHeaderCreator to add some descriptive text.&#39;</span><span class="p">)</span>
             <span class="c1"># next, use the cedar.CatalogHeaderCreator class to add catalog and header </span>
             <span class="n">catHeadObj</span> <span class="o">=</span> <span class="n">madrigal</span><span class="o">.</span><span class="n">cedar</span><span class="o">.</span><span class="n">CatalogHeaderCreator</span><span class="p">(</span><span class="n">newFile</span><span class="p">)</span>
             <span class="n">catHeadObj</span><span class="o">.</span><span class="n">createCatalog</span><span class="p">(</span><span class="n">principleInvestigator</span><span class="o">=</span><span class="s2">&quot;John Holt&quot;</span><span class="p">,</span> <span class="n">sciRemarks</span><span class="o">=</span><span class="s2">&quot;Test data only - do not use&quot;</span><span class="p">)</span>
             <span class="n">catHeadObj</span><span class="o">.</span><span class="n">createHeader</span><span class="p">(</span><span class="n">analyst</span><span class="o">=</span><span class="s2">&quot;Bill Rideout&quot;</span><span class="p">,</span> <span class="n">comments</span><span class="o">=</span><span class="s2">&quot;Do not use this data&quot;</span><span class="p">)</span>
             <span class="n">catHeadObj</span><span class="o">.</span><span class="n">write</span><span class="p">()</span>
             </pre></div>
             <p><a name="edit" id="edit"></a>
             </p>
             <h2>Editing an existing file example</h2>
             <div class="highlight">
               <pre><span class="sd">&quot;&quot;&quot;editSample.py shows an example of editing existing data in a Madrigal</span>
             <span class="sd">file using the Python cedar module.  In particular, it edits the sample file</span>
             <span class="sd"><span class="s">mlh980120g.002.hdf5</span> to increase all Ti values by a factor of 1.2</span>
             <span class="sd">&quot;&quot;&quot;</span>
             <span class="kn">import</span> <span class="nn">os</span><span class="o">,</span> <span class="nn">os.path</span>
             <span class="kn">import</span> <span class="nn">types</span>
             <span class="kn">import</span> <span class="nn">madrigal.metadata</span>
             <span class="kn">import</span> <span class="nn">madrigal.cedar</span>
             <span class="n">metaObj</span> <span class="o">=</span> <span class="n">madrigal</span><span class="o">.</span><span class="n">metadata</span><span class="o">.</span><span class="n">MadrigalDB</span><span class="p">()</span>
             <span class="n">orgFile</span> <span class="o">=</span> <span class="n">os</span><span class="o">.</span><span class="n">path</span><span class="o">.</span><span class="n">join</span><span class="p">(</span><span class="n">metaObj</span><span class="o">.</span><span class="n">getMadroot</span><span class="p">(),</span> <span class="s">&#39;experiments/1998/mlh/20jan98/mlh980120g.002.hdf5&#39;</span><span class="p">)</span>
             <span class="n">newFile</span> <span class="o">=</span> <span class="s">&#39;/tmp/mlh980120g.002.hdf5&#39;</span>
             <span class="c"># read the Madrigal file into memory</span>
             <span class="n">cedarObj</span> <span class="o">=</span> <span class="n">madrigal</span><span class="o">.</span><span class="n">cedar</span><span class="o">.</span><span class="n">MadrigalCedarFile</span><span class="p">(</span><span class="n">orgFile</span><span class="p">)</span>
             <span class="c"># loop through each record, increasing all Ti values by a factor of 1.2</span>
             <span class="k">for</span> <span class="n">record</span> <span class="ow">in</span> <span class="n">cedarObj</span><span class="p">:</span>
                 <span class="c"># skip header and catalog records</span>
                 <span class="k">if</span> <span class="n">record</span><span class="o">.</span><span class="n">getType</span><span class="p">()</span> <span class="o">==</span> <span class="s">&#39;data&#39;</span><span class="p">:</span>
                     <span class="c"># loop through each 2D roow</span>
                     <span class="k">for</span> <span class="n">row</span> <span class="ow">in</span> <span class="nb">range</span><span class="p">(</span><span class="n">record</span><span class="o">.</span><span class="n">getNrow</span><span class="p">()):</span>
                         <span class="n">presentTi</span> <span class="o">=</span> <span class="n">record</span><span class="o">.</span><span class="n">get2D</span><span class="p">(</span><span class="s">&#39;Ti&#39;</span><span class="p">,</span> <span class="n">row</span><span class="p">)</span>
                         <span class="c"># make sure its not a special string value, eg &#39;missing&#39;</span>
                         <span class="k">if</span> <span class="nb">type</span><span class="p">(</span><span class="n">presentTi</span><span class="p">)</span> <span class="o">!=</span> <span class="n">types</span><span class="o">.</span><span class="n">StringType</span><span class="p">:</span>
                             <span class="n">record</span><span class="o">.</span><span class="n">set2D</span><span class="p">(</span><span class="s">&#39;Ti&#39;</span><span class="p">,</span> <span class="n">row</span><span class="p">,</span> <span class="n">presentTi</span><span class="o">*</span><span class="mf">1.2</span><span class="p">)</span>
             <span class="c"># write edited file</span>
             <span class="n">cedarObj</span><span class="o">.</span><span class="n">write</span><span class="p">(</span><span class="n">newFilename</span><span class="o">=</span><span class="n">newFile</span><span class="p">)</span></pre></div>
             <p>&nbsp; </p>
             <h2><a name="matlab" id="matlab"></a>Matlab</h2>
             <p>To create CEDAR Madrigal Hdf5 files with Matlab, you will need to put the file MadrigalHdf5File.m on your Matlab path.  You also need to run the Matlab script on a server with Madrigal installed, since ultimately Matlab will simply write your information to a *.mat file, and then call the python script createMadrigalHdf5FromMatlab.py to convert that *.mat file to the output Hdf5 file. The script createMadrigalHdf5FromMatlab.py is installed in MADROOT/bin as part of the Madrigal installation.</p>
             <p>You may however, run MadrigalHdf5File.m on a non-Madrigal server, and save the output file as a *.mat file, rather than an Hdf5 file.  You could then convert that *.mat file into a Madrigal file on a server with Madrigal installed, using the convertToMadrigal function also defined in MadrigalHdf5File.m.</p>
             <p>There are only seven methods in the main class of this API, along with one helper method needed only if not running on a Madrigal server:</p>
             <ol>
               <li>MadrigalHdf5File (the init method)</li>
               <li>appendRecord (called once for each Madrigal record added)</li>
               <li>set1DParm (called  for each one D parameter in each Madrigal record)</li>
               <li>set2DParm (called  for each two D parameter in each Madrigal record, passes in a vector of length equal to number of rows in record)</li>
               <li>setCatalog - called once per file; set some metadata beyond the default automatically added</li>
               <li>setHeader - called once per file; set the rest of the metadata</li>
               <li>write - called when file complete</li>
             </ol>
             <p>These seven methods are documented below, along with the helper method convertToMadrigal. An <a href="#matlab_example">example Matlab script</a> that creates a CEDAR Madrigal Hdf5 file is also given.</p>
             <div class="highlight">
               <pre><span class="nn">classdef</span> MadrigalHdf5File<br />    <span class="nb">% class MadrigalHdf5File allows the creation of Madrigal Hdf5 files via<br />    % Matlab.  The general idea of this class is to simply write out all<br />    % data for the file in a Matlab struct array.  Then the python script<br />    % createMadrigalHdf5FromMatlab is called from this scriptto create all <br />    % metadata and alternate array layouts.  This keeps the amount of Matlab <br />    % code here at a minimum.  See file testMadrigalHdf5File.m for example<br />    % usage.</span>
                <span class="nn">methods<br />        function</span> madFile = MadrigalHdf5File(filename, oneDParms, ...<br />                independent2DParms, twoDParms, arraySplittingParms)<br />            <span class="nb">% Object constructor for MadrigalHdf5File<br />            % Inputs:<br />            %   filename - the filename to write to.  Must end *.hdf5,<br/>            %     .hdf, or .mat.  If .mat, writes a Matlab file that must<br/>            %     later be converted to Madrigal using convertToMadrigal<br />            %   oneDParms - a cell array of strings representing 1D parms.  May be<br />            %     empty.  Example:<br />            %     cellstr(char('azm', 'elm', 'sn', 'beamid'))<br />            %   independent2DParms - a cell array of strings representing independent <br />            %     2D parms.  May be empty (ie, {}). Examples:<br />            %       cellstr(char('range'))<br />            %       cellstr(char('gdlat', 'glon'))<br />            %       cellstr(char())<br />            %   twoDParms - a cell array of strings representing dependent <br />            %     2D parms.  May be empty (ie, {}). Examples:<br />            %       cellstr(char('ti', 'dti', 'ne', 'dne'))<br />            %       cellstr(char())<br />            %   arraySplittingParms - a cell array of strings representing  <br />            %     parameters whose values are used to split arrays.  May <br />            %     be empty, in which case set to {}. Example:<br />            %       cellstr(char('beamid'))<br />            %  skipArray - optional argument.  If set to true, no array<br />            %      layout created.  If false or not passed in, array layout<br />            %     created if any 2D variables.</span>
                  <span class="nn">function</span> madFile = appendRecord(madFile, ut1_unix, ut2_unix, kindat, ...<br />                kinst, numRows)<br />            <span class="nb">% appendRecord adds a new record to MadrigalHdf5File.  It<br />            % returns the record number of the present row (first will be<br />            % 0)<br />            %  Inputs:<br />            %    madFile - the created MadrigalHdf5File object<br />            %    ut1_unix, ut2_unix - unix start and end time of record in<br />            %      float seconds since 1970-01-01<br />            %    kindat - integer kind of data code. See metadata.<br />            %    kinst - integer instrument code.  See metadata.<br />            %    numRows - number of rows of 2D data.  If all 1D data, set<br />            %    to 1<br />            %  Returns:<br />            %    the record number of the present row (first will be 0)<br />            %  Affects:<br />            %    Updates madFile.recordCount, appends to madFile.data the<br />            %    number of rows numRows with all data except stdParms set<br />            %    to NaN.  Use set1D and set2D to populate that record using<br />            %    recNum as index.</span>
                 <span class="nn">function</span> madFile = set1DParm(madFile, parm, value, lastRec)<br />            <span class="nb">% set1DParm sets the values of 1D parm parm to value value for<br />            % record with lastRecord value lastRec</span>
                 <span class="nn">function</span> madFile = set2DParm(madFile, parm, values, lastRec)<br />            <span class="nb">% set2DParm sets the values of 2D parm parm to value values for<br />            % record with lastRecord value lastRec</span>
                 <span class="nn">function</span> madFile = setCatalog(madFile, principleInvestigator, expPurpose, expMode, ...<br />                                      cycleTime, correlativeExp, sciRemarks, instRemarks)<br />            <span class="nb">% setCatalog allows setting extra information in the catalog<br />            % record.  This method is optional.  Even if this method is not<br />            % called, the catalog record will contain a description of the<br />            % instrument (kinst code and name) and kind of data brief<br />            % description, along with a list of description of the<br />            % parameters in the file, and the first and last times of the<br />            % measurements.<br />            %<br />            % Inputs:<br />            %<br />            %    principleInvestigator - Names of responsible Principal Investigator(s) or <br />            %       others knowledgeable about the experiment.<br />            %    expPurpose - Brief description of the experiment purpose<br />            %    expMode - Further elaboration of meaning of MODEXP; e.g. antenna patterns <br />            %       and pulse sequences.<br />            %    cycleTime - Minutes for one full measurement cycle - must<br />            %       be numeric<br />            %    correlativeExp - Correlative experiments (experiments with related data)<br />            %    sciRemarks - scientific remarks<br />            %    instRemarks - instrument remarks<br />            %</span>
                 <span class="nn">function</span> madFile = setHeader(madFile, kindatDesc, analyst, comments, history)<br />            <span class="nb">% setHeader allows setting extra information in the header<br />            % record.  This method is optional.<br />            %<br />            % Inputs:<br />            %<br />            %    kindatDesc - description of how this data was analyzed (the kind of data)<br />            %    analyst - name of person who analyzed this data<br />            %    comments - additional comments about data (describe any instrument-specific parameters)<br />            %    history - a description of the history of the processing of this file<br />            %</span>
                 <span class="nn">function</span> write(madFile)<br />            <span class="nb">% write writes out the complete Hdf5 file to madFile.filename</span>
             <span class="nn">function</span> convertToMadrigal(matFile, madrigalFile)<br />    <span class="nb">% convertToMadrigal converts a matlab mat file to Madrigal Hdf5 file<br/>    %   Inputs:<br/>    %      matFile - existing Matlab .mat file created earlier<br/>    %      madrigalFile - madrigal file to create.  Must end *.hdf5, .h5,<br/>    %     .hdf, or .mat.<br/></span>
                 </pre>
             </div>
             <a name="matlab_example"></a>Example usage of MadrigalHdf5File
             <div class="highlight">
             <pre>
             <span class="nb">% test/example script to exercise MadrigalHdf5File
             %
             % $Id: testMadrigalHdf5File.m 4644 2015-01-13 19:30:37Z brideout $</span>
             filename = <span class="s">'/Users/brideout/Documents/workspace/mad3_0/madroot/source/madmatlab/example.h5'</span>;
             oneDParms = cellstr(char(<span class="s">'azm'</span>, <span class="s">'elm'</span>, <span class="s">'sn'</span>, <span class="s">'beamid'</span>));
             independent2DParms = cellstr(char(<span class="s">'range'</span>));
             twoDParms = cellstr(char(<span class="s">'ti'</span>, <span class="s">'dti'</span>));
             <span class="nb">% Use {} for independent2DParms and twoDParms if all scalar parameters</span>
             arraySplittingParms = cellstr(char(<span class="s">'beamid'</span>));
             <span class="nb">% Use arraySplittingParms = {}; for no splitting</span>
             <span class="nb">% some hard-coded fake data</span>
             ut1_unix = 1.0E9;
             ut2_unix = 1.0E9 + 100;
             kindat = 3410;
             kinst= 30;
             numRows = 5;
             azm = 100.0;
             elm = 45.0;
             sn = 0.5;
             range = [100.0, 150.0, 200.0, 250.0, 300.0];
             ti = [1000.0, 1100.0, 1200.0, 1300.0, 1400.0];
             dti = [100.0, 150.0, 200.0, 250.0, 300.0];
             beamids = [1,2,1,2,1,2,1,2,1,2];
             madFile = MadrigalHdf5File(filename, oneDParms, ...
                       independent2DParms, twoDParms, arraySplittingParms);
             <span class="nn">for</span> rec = 1:10
                 madFile = madFile.appendRecord(ut1_unix, ut2_unix, kindat, ...
                     kinst, numRows);
                 <span class="nb">% set 1D values</span>
                 madFile = madFile.set1DParm(<span class="s">'azm'</span>, azm, madFile.lastRecord);
                 madFile = madFile.set1DParm(<span class="s">'elm'</span>, elm, madFile.lastRecord);
                 madFile = madFile.set1DParm(<span class="s">'sn'</span>, sn, madFile.lastRecord);
                 madFile = madFile.set1DParm(<span class="s">'beamid'</span>, beamids(rec), madFile.lastRecord);
                 <span class="nb">% set 2D and independent variables</span>
                 madFile = madFile.set2DParm(<span class="s">'range'</span>, range, madFile.lastRecord);
                 madFile = madFile.set2DParm(<span class="s">'ti'</span>, ti, madFile.lastRecord);
                 madFile = madFile.set2DParm(<span class="s">'dti'</span>, dti, madFile.lastRecord);
             <span class="nn">end</span>
             <span class="nb">% add catalog and header info</span>
             principleInvestigator = <span class="s">'Bill Rideout'</span>;
             expPurpose = <span class="s">'Measure the ionosphere'</span>;
             expMode = <span class="s">'Vector measurements'</span>;
             cycleTime = 20.0;
             correlativeExp = '';
             sciRemarks = <span class="s">'Big solar storm'</span>;
             instRemarks = <span class="s">'Working well!!!'</span>;
             madFile = madFile.setCatalog(principleInvestigator, expPurpose, expMode, ...
                                         cycleTime, correlativeExp, sciRemarks, instRemarks);
             kindatDesc = <span class="s">'Regular processing'</span>;
             analyst = <span class="s">'Phil Erickson'</span>;
             comments = <span class="s">'Include unusual parameter description here'</span>;
             history = <span class="s">'Reprocessed four times'</span>;
             madFile = madFile.setHeader(kindatDesc, analyst, comments, history);
             write(madFile);
             </pre>
             <h3>Converting an old Madrigal 2 file to Madrigal 3</h3>
             <p>If you have old Madrigal 2 files you want to convert to Madrigal 3, you can use $MADROOT/bin/exportToHdf.py</p>
             <pre>
             $MADROOT/bin/exportToHdf.py -h
             exportToHdf.py is a script used to convert a Cedar file to hdf5 format.
             Required arguments:
                 --cedarFilename - full path of existing Madrigal file.
                 --hdf5Filename - full path of hdf5 file to write.
             Optional arguments - set these to add layouts, parameters or filters.  Default is to use cachedFiles.ini:
                 --independentSpatialParms - a comma separated list of parameters as mnemonics
                     that represent independent spatial variables.  Causes array layout to be added to
                     output Hdf5 file.  If not given, uses $/home/midasop/mad3/cachedFiles.ini
                 --arraySplittingParms - a comma separated list of parameters as mnemonics used to split
                     arrays into subarrays.  For example, beamcode would split data with separate beamcodes
                     into separate arrays. The number of separate arrays will be up to the product of the number of
                     unique values found for each parameter, with the restriction that combinations with no records will
                     not create a separate array. .  If not given, uses $/home/midasop/mad3/cachedFiles.ini
                 --extraParameters - These parameters will be added to the output file if
                                     they are not already in the input file. Comma-delimited.  Default is no
                                     extra parameter
                 --filter - Filter argument as in isprint command as string (eg, 'ti.500,2000') Only one allowed.
                            Default is no filtering
                 --status - use to set status of file.  Default is 1 (default).  Use -1 to get from fileTab (error raised
                         if not available)
             Example:
                 exportToHdf --cedarFilename=/opt/madrigal/experiments/1998/mlh/20jan98/mil20100112.001
                             --hdf5Filename=/home/user/data/mil20100112.hdf5
                             --independentSpatialParms=range
                             --arraySplittingParms=kinst,pl,mdtyp
                             --extraParameters=ti,te
                             --filter=ti,500,1000
             </pre>
             </div>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_experiments.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_experiments.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_createExp.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_createExp.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Creating and editing Madrigal data files <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_experiments.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Madrigal data organization <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_createExp.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Creating Madrigal experiments <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/ad_experiments.html +8 -8

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>How Madrigal data is organized</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="admin.html" --><!-- InstanceParam name="href_next_top" type="text" value="ad_createFiles.html" --><!-- InstanceParam name="href_back_top" type="text" value="ad_metadata.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="ad_metadata.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="ad_createFiles.html" --><!-- InstanceParam name="href_prev_top" type="text" value="ad_metadata.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="ad_createFiles.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="ad_metadata.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="ad_createFiles.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_metadata.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_metadata.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_createFiles.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_createFiles.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->How Madrigal data is organized <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_metadata.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Madrigal data model <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_createFiles.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Creating Madrigal data files <!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">How Madrigal data is organized </h1>
             <p>In the Madrigal database, the data are organized by experiment. An experiment consists of data from a single instrument, and, as a rule, is meant to address a particular scientific goal. Most often an experiment will correspond to a particular set of operating modes run for a contiguous interval of time. For example, the data collected by an incoherent scatter radar during a world day would constitute an experiment. More complicated situations exist, and judgment may have to be exercised in determining what constitutes an experiment. For example, an experiment might be interrupted temporarily in order to use a different set of operating modes in support of a satellite overpass. In this case there could be two experiments which overlap in time.</p>
             <p>To each experiment there corresponds a directory. These directories are of the form <em>madroot</em>/experiments[0-9]*/&lt;year&gt;/&lt;instrument&gt;/&lt;<em>directory</em>&gt;, where year is the four-digit year. The next level is the experiments[0-9]*, where the directory must begin &quot;experiments&quot; and then may be followed by any number of digits. This is to allow additional hard drives to be mounted to expand the directory space. The next level, instrument, is the 3-letter mnemonic for the instrument (set in the instTab.txt file), and &lt;<em>directory</em>&gt; is an arbitrary directory name. An example might be /opt/madrigal/experiments/1997/son/06jan1997_001, which would contain a 1997 Sondrestrom (son) experiment. The use of the starting date in the experiment directory name is not required. </p>
             <p>Prior to Madrigal 2.5, the final directory name was required to be in the form DDmmmYY*, where the date was  the start date of the experiment  and * is an optional character to distinguish different experiments with the same start date. For example, /opt/madrigal/experiments/1997/son/06jan97 contained Sondrestrom data for an experiment beginning on 6 January, 1997, where year =1997, instrument =son, start_date =06jan97, and there was no optional character because there was only one Sondrestrom experiment starting on that date. This convention has been dropped as a requirement, although it is still commonly used as a convention.</p>
             <p>Previously, experiments that did not follow the above naming convention were effectively &quot;hidden&quot;. With Madrigal 2.5, the security field in the metadata file expTab.txt can be used to hide (or restrict access to) an experiment. (See the <a href="ad_createExp.html#changeExpStatus">change experiment status</a> tool). </p>
             <p>Each experiment directory must contain: </p>
             <ul>
               <li>The Experiment Table entry (expTab.txt) for this experiment. This file is created automatically if you use the tools described in the <a href="{% url 'docs' 'ad_createExp.html' %}">creating experiments</a> section. </li>
             </ul>
             Each experiment directory may contain:
             <ul>
               <li>The metadata file fileTab.txt for this experiment. This table must have one entry for each Madrigal format file in the experiment. This file is created automatically if you use the tools described in the <a href="ad_createExp.html">creating experiments</a> section. </li>
-              <li>One or more datasets in <a href="/static/CEDARMadrigalHdf5Format.pdf" target="_blank">CEDAR Madrigal Hdf5 format</a>. </li>
+              <li>One or more datasets in <a href="{% static 'CEDARMadrigalHdf5Format.pdf' %}" target="_blank">CEDAR Madrigal Hdf5 format</a>. </li>
               <li>Subdirectories containing an html file named index.html . Links to these files will show up the experiment page. </li>
               <li>Html pages in the main directory, and again links to these files will show up the experiment page. </li>
               <li>Plots or other files related to individual records in the dataset. Links to these files appear next to the appropriate record in the summarizeCedarFile.cgi page. These files must be located in the subdirectory "plots/[file name]/records" under the experiment directory. In order for the script to determine which file goes with which record, the files must include a five digit number somewhere in its name. For example, plot00027.gif would appear as a link next to record 27 in summarizeCedarFile.cgi. More than one file can be associated with a given record. </li>
             </ul>
             <p>An essential role for a Madrigal administrator is to run the script <em>madroot</em>/bin/updateMaster on a regular basis. This script performs a number of functions:</p>
             <ul>
               <li>It gathers all the separate metadata files in the individual experiment directories into the central directory <em>madroot</em>/metadata. </li>
               <li>It gathers metadata files from other Madrigal sites into the central directory <em>madroot</em>/metadata. </li>
               <li>It updates geophysical files from the OpenMadrigal site.</li>
             </ul>
             <p>It is recommended that this script be set as a cron job to run once a day. </p>
             <p>For Madrigal sites with limited bandwidth, updateMaster can occasionally be run with the -s flag. This will skip any possible download of the latest geophysical files, and so maybe run faster.  However, it is still important to run updateMaster without the -s flag on a regular basis.</p>
             <p>A complete description of the various ways to add and modify experiments in a Madrigal database is given <a href="{% url 'docs' 'ad_createExp.html' %}">in the next section.</a> The updateMaster script must be run after each change described in that section for the changes to take effect. </p>
             <p>Note that an experiment need not contain any Madrigal files. </p>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_metadata.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_metadata.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_createFiles.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_createFiles.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->How Madrigal data is organized<!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_metadata.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Madrigal data model <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_createFiles.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Creating Madrigal data files <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/ad_install.html +7 -7

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>Installing Madrigal for the first time</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="admin.html" --><!-- InstanceParam name="href_next_top" type="text" value="ad_upgrade.html" --><!-- InstanceParam name="href_back_top" type="text" value="ad_appropriate.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="ad_appropriate.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="ad_upgrade.html" --><!-- InstanceParam name="href_prev_top" type="text" value="ad_appropriate.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="ad_upgrade.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="ad_appropriate.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="ad_upgrade.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_appropriate.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_appropriate.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_upgrade.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_upgrade.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Installing Madrigal for the first time <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_appropriate.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Is Madrigal appropriate? <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_upgrade.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Upgrading Madrigal <!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">Installing Madrigal for the first time </h1>
             <h4 align="left">Prerequisites</h4>
             <p>Madrigal is meant to be installed on any Unix-like OS, including Mac and Linux. Most of the prerequisites for Madrigal are pre-installed in any modern unix distribution. They are: </p>
             <ol>
               <li>A C and a FORTRAN  compiler. The free GNU compilers may be downloaded from the <a href="http://www.gnu.org/software/gcc/">GNU Website </a>.</li>
               <li>Autotools (automake, autoconf, aclocal, libtoolize, autoheader)</li>
               <li>A web server. See instructions below to run a Django application (which Madrigal is) on apache.</li>
               <li>The environmental variable MADROOT should be set to the path to the Madrigal installation directory. Its recommended this be done in your login script (eg, .bash_profile) because you will need it to run administrative scripts later.</li>
               <li>With Madrigal 3, the installation uses a version of python 3 you install yourself. The easiest way I have found to install python with scientific tools is to use either apt-get (for ubuntu), or the Anaconda python distribution, or pip. The following python modules need to be installed:
                 <ol>
                   <li>django (version 1.11 or greater)</li>
                   <li>pip and setuptools</li>
                   <li>numpy</li>
                   <li>scipy</li>
                   <li>matplotlib</li>
                   <li>netCDF4</li>
                   <li>h5py</li>
                   <li>sqlparse</li>
                   <li>filelock</li>
                   <li>bootstrap3 (can be installed via <em>pip install django-bootstrap3</em>)</li>
                   <li>aacgmv2 (can be installed via <em>pip install aacgmv2</em>)<br />
                   </li>
                 </ol>
               </li>
             </ol>
             <p>In addition, you need to have Autotools (automake, autoconf, aclocal, libtoolize, autoheader) installed, along with h5repack (may be part of h5utils package).</p>
             <pre></pre>
             <h4 align="left">Installation instructions </h4>
             <p align="left">Madrigal can be installed on any unix server with a web server configured for Django. If you want to link your data in with data on other Madrigal servers, please notify the <a href="mailto:madrigal@haystack.mit.edu">OpenMadrigal administrator</a>. In general you do not need root permission to install madrigal once the prerequisites listed above are installed. </p>
             <ol>
               <li>Create a directory to be used as your Madrigal root directory on your unix server. This directory will be referred to as MADROOT. </li>
               <li>Create the environment variable MADROOT with that directory path. </li>
               <li>Download the latest Madrigal distribution file, madrigal*.tar.gz from the <a href="http://cedar.openmadrigal.org/madrigalDownload/">OpenMadrigal distribution page</a> to MADROOT. </li>
               <li>gunzip madrigal*.tar.gz </li>
               <li>tar -xf madrigal*.tar </li>
               <li>Repeat the 3 steps above to get and untar the Sample Experiments file <em>experiments.tar.gz</em>. </li>
               <li>Make sure $MADROOT/bin/python links to the version of python with the required modules listed above. For example, if you are using anaconda, you might run &lt;<em>ln -s //anaconda/bin/python $MADROOT/bin/python</em>&gt;.</li>
               <li>If desired, copy any data from your old $MADROOT/experiments directory to this new $MADROOT/experiments directory.</li>
               <li>In madroot, there will now be a file called madrigal.cfg.template. Copy it to madrigal.cfg, and edit all the configuration parameters, as described in the <a href="#edit">Editing madrigal.cfg</a> section below. </li>
               <li>Configure your web server to run the Madrigal Django application. Instruction for apache can be found in the <a href="#django">Configuring Apache for a Madrigal Django Application</a> section below. If you are running a webserver other than apache, please consult the Django documentation for your particular webserver. </li>
               <li>Edit the file MADROOT/metadata/siteTab.txt with a unique id to include your site. The format of siteTab.txt is described <a href="ad_metadata.html#siteTab">here</a>. Note that if your site will be running https, the third field will begin https://.  If you want to be an official Madrigal site that other Madrigal sites share data with, request the <a href="mailto:madrigal@haystack.mit.edu">OpenMadrigal administrator</a> to assign you this id. If this is just a test site, use any id not already in the siteTab.txt file. Finally, make sure the last column of the line for your site ends <em>,3.0</em> . This tells all sites that you site is now a Madrigal 3 site. For example: <pre>999,mad31,localhost,madrigal,cgi-bin/madrigal,madrigal/servlets,Bill Rideout,MIT Haystack Observatory,Route 40,,Westford,MA,01886,USA,1-781-981-5624,brideout@haystack.mit.edu,3.0</pre></li>
               <li>Be sure to cd to MADROOT before running the following step. Then you should be able to complete the installation simply by typing <br />
                 <pre>&lt;sudo&gt; bash installMadrigal  &> install.log &</pre>
               The <em>sudo</em> is required only if installing modules on your default version of python requires sudo. There may be a long pause when running updateMaster near the end of the installation since the instParmTab.txt metadata file is being built for the first time by examining every data file, but future calls to updateMaster will be much faster since only new experiments are examined. Help with any installation errors is available from the <a href="mailto:madrigal@haystack.mit.edu">OpenMadrigal administrator</a>. </li>
               <li>If there were no errors, your madrigal installation should be running at the url given by MADSERVERROOT. </li>
               <li>If you want to receive notices about updates to Madrigal, sign up for the openmadrigal-admin mailing list under http://cedar.openmadrigal.org/openmadrigal. </li>
               <li>Set the script <em>madroot</em>/bin/updateMaster up as a cron job to run once a day. </li>
               <li>If you want to add any documentation pages specific to your site to the Madrigal documentation pages, see the <a href="ad_other.html#siteSpecific">other admin tasks</a> section of this manual.</li>
               <li>If you want to add your own rules of the road to the Madrigal experiment page, see the <a href="ad_other.html#rules">other admin tasks</a> section of this manual.</li>
             </ol>
             <p> </p>
             <h4><a name="edit" id="edit"></a>Editing the madrigal.cfg file </h4>
             The madrigal.cfg file contains all the configuration information specific to your installation. This section discusses how to edit that file for each parameter.  The madrigal.cfg.template file contains examples of each parameter.
             <ul>
               <li>MADROOT - Madrigal root directory (absolute). This must be set as an environmental variable. </li>
               <li>MAD<b></b>SERVER - Web server for accessing Madrigal.  For https, add https:// to the beginning.  If not given, uses http </li>
               <li>MAD<b></b>SERVERROOT - document virtual directory relative to MAD<b></b>SERVER.
               If the full Madrigal Url is the same as the MAD<b></b>SERVER field
                (for example, if the url is <i>http://madrigal.hao.ucar.edu/</i>), then set this field to a period. (Example:
                <i>MAD<b></b>SERVERROOT = .</i> ) </li>
               <li>SITEID - Site ID - Must be unique and same as in siteTab.txt </li>
               <li>HTMLSTYLE - Body style of html pages </li>
               <li>INDEXHEAD - Heading in the top-level Madrigal page </li>
               <li>CONTACT - Mailto link of contact person(s) for this madrigal installation. Multiple email addresses may be included if separated by commas. </li>
               <li>MAILSERVER - Name of mailserver (possibly localhost if running sendmail) </li>
               <li>PLOTBUTTONLABEL - By default the button to show additional documentation is labelled Plots/Docs. Change this line for a different label. <br>
               </li>
             </ul>
             <h4><a name="django" id="django"></a>Configuring Apache for a Madrigal Django Application</h4>
             <p>Some configuration of apache is required to run a Django application like Madrigal. If you are running a webserver other than apache, please consult the Django documentation for your particular webserver. We will configure apache to run Madrigal in mod_wsgi daemon mode for improved performance.</p>
             <p>The first step is to make sure mod_wsgi is installed as part of your apache webserver. If not, see mod_wsgi installation directions. Once installed, add the line</p>
             <pre>LoadModule wsgi_module modules/mod_wsgi.so</pre>
             <p>near the top of the httpd.conf file. Next add the follow section, with <em>MADROOT</em>, <em>MADSERVERROOT</em> and <em>YOUR_SERVER</em> replaced with values for your server from the madrigal.cfg file described below. Note that if <em>MADSERVERROOT</em> is zero length (that is, if the full Madrigal Url is the same as the MAD<b></b>SERVER field
               - for example, if the url is <i>http://madrigal.hao.ucar.edu/</i>) then /<em>MADSERVERROOT</em> just becomes / unlike in the madrigal.cfg file when it becomes a period.  Set <em>NUM_CPU</em> to about one half available on your server.</p>
             <pre>SetEnv PYTHONPATH <em>MADROOT</em>/source/madpy/djangoMad/
             WSGIDaemonProcess <em>YOUR_SERVER</em> python-path=<em>MADROOT</em>/source/madpy/djangoMad processes=<em>NUM_CPU</em> display-name=%{GROUP} lang='en_US.UTF-8' locale='en_US.UTF-8'
             WSGIProcessGroup <em>YOUR_SERVER</em>
             WSGIScriptAlias /<em>MADSERVERROOT</em> <em>MADROOT</em>/source/madpy/djangoMad/djangoMad/wsgi.py process-group=<em>YOUR_SERVER</em>
             Alias /static/ <em>MADROOT</em>/source/madpy/djangoMad/madweb/static/
             WSGIApplicationGroup %{GLOBAL}</pre>
             <pre> &lt;Directory <em>MADROOT</em>/source/madpy/djangoMad/madweb/static&gt;</pre>
             <blockquote>
               <pre>Require all granted</pre>
             </blockquote>
             <pre>
             &lt;/Directory&gt;
             &lt;Directory <em>MADROOT</em>/source/madpy/djangoMad/djangoMad&gt;</pre>
             <blockquote>
               <pre>&lt;Files wsgi.py&gt;  </pre>
               <blockquote>
                 <pre>Require all granted</pre>
               </blockquote>
               <pre>&lt;/Files&gt;</pre>
             </blockquote>
             <pre>&lt;/Directory&gt;
             </pre>
             <p>You may also need to add to your apache configuration file <em>SetEnv LD_LIBRARY_PATH $MADROOT/lib</em>, possibly along with other library paths.</p>
             <p>Finally, you need to edit the file <em>MADROOT</em>/source/madpy/djangoMad/djangoMad/settings_production_template.py, and save it as <em>MADROOT</em>/source/madpy/djangoMad/djangoMad/settings_production.py. The lines to be edited are:</p>
             <pre>SECRET_KEY = '*****'
             ALLOWED_HOSTS = ['madrigal3.haystack.mit.edu']
             ADMINS = (('Bill Rideout', 'brideout@haystack.mit.edu'),)
             EMAIL_HOST = 'hyperion.haystack.mit.edu'
             MANAGERS = (('Bill Rideout', 'brideout@haystack.mit.edu'),)
             STATIC_URL = '/static/'</pre>
             <p>The STATIC_URL line only needs to be edited if MAD<b></b>SERVERROOT is not empty; that is, if your madrigal is installed in a subdirectory.
             For example, if your url is http://madrigal.sri.com/madrigal, you would change that line to be STATIC_URL = '/madrigal/static/'.  But if your
             url is http://madrigal.sri.com, you would leave that STATIC_URL line as is.</p>
             <p>You can generate a new secret key for your site at http://www.miniwebtool.com/django-secret-key-generator/, which is recommended for security reasons.  The other lines are self-explanatory. </p>
             <p>When you are done, be sure to restart apache for the changes to take effect. Note that because this Madrigal Django application runs in daemon mode, it will be necessary to restart the web server if you ever update the python code.</p>
             <h3>Throttling Madrigal admin emails</h3>
             <p>Sometimes Madrigal users write scripts that cause numerous admin emails, and in addition malicious users can also generate numerous admin emails.
             If you would like to throttle the number of Madrigal admin emails you receive, see <a href="{% url 'docs' 'ad_other.html' %}#throttle">Throttling admin emails</a></p>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_appropriate.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_appropriate.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_upgrade.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_upgrade.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Installing Madrigal for the first time <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_appropriate.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Is Madrigal appropriate? <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_upgrade.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Upgrading Madrigal <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/ad_isprint.html +7 -7

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>Using isprint</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="admin.html" --><!-- InstanceParam name="href_next_top" type="text" value="dev_contents.html" --><!-- InstanceParam name="href_back_top" type="text" value="ad_logging.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="ad_logging.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="dev_contents.html" --><!-- InstanceParam name="href_prev_top" type="text" value="ad_logging.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="dev_contents.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="ad_logging.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="dev_contents.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_links.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_links.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'dev_contents.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'dev_contents.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Using isprint  <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_links.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Creating direct links<!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'dev_contents.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Developer's toc<!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">Admin command line tool: isprint</h1>
             <p>Madrigal administrators can get a quick look print out of a CEDAR Madrigal using the command line tool isprint. This may be more convenient than using the web interface or using an Hdf5 viewer such as Hdfview.</p>
             <p> The application isprint is used to display both measured and derived data from one particular Cedar/Madrigal file. The input file can be any valid Cedar format. It will generate a table of user selected parameters subject to user specified filters. The name isprint original referred to &quot;<strong><u>I</u></strong>ncoherent <strong><u>s</u></strong>catter <strong><u>print</u></strong>&quot; but the application now generically prints any data file in the Cedar format. The engine underlying isprint is the main method for outputting Madrigal data. This application is located in <em>madroot</em>/bin.</p>
             <p>The isprint application: </p>
             <ul>
               <li>Treats measured and derived parameters in the same way. </li>
               <li>Accepts any parameter (or two parameters added, subtracted, multiplied, or divided) as a filter, with any number of allowed ranges. </li>
               <li>Keeps track of 1D versus 2D data, and only prints one line of data if only 1D parameters are requested. </li>
             </ul>
             <p>To use isprint, the user needs to specify:</p>
             <ol>
               <li>The full filename </li>
               <li>Output file (if not given, prints ascii to stdout)</li>
               <li>The parameters desired to be displayed (if any) </li>
               <li>Any filters to limit the amount of data shown (if any) </li>
               <li>Any non-default formatting options </li>
             </ol>
             <blockquote>
               <h3>The full filename </h3>
             </blockquote>
             <p>file= path to file (this argument is required) <br />
                 <em>Example: file=/opt/madrigal/experiments/1998/mlh/20jan98/mlh980120g.001.hdf5 </em> </p>
             <blockquote>
               <h3>The output file</h3>
             </blockquote>
             <p>output=&lt;output file&gt;. If not given, default is text file to stdout.  If given and extension is one of<br />
             &lt;.hdf5, .h5, .hdf&gt;, then will save as Hdf5 file.  If extension is .nc, will be saved as netCDF4. In<br />
             all other cases, will be saved as ascii text.  If hdf5 or netCDF4, arguments (header, summary, badval,<br />
             assumed, and knownbad) ignored if given.</p>
             <blockquote>
               <h3>The parameters desired to be displayed </h3>
             </blockquote>Simply enter the desired parameter mnemonic (case-insensitive). They will be displayed in the order entered. If none given, only the header records will be displayed. <br />
             <em>Example: azm gdalt Range ti Dti </em>
             <blockquote>
               <h3>Any filters to limit the amount of data shown </h3>
               <h5>Time range </h5>
             </blockquote>
             <p>date1=mm/dd/yyyy - starting date to be examined. If time1 not given, defaults to 0 UT. <br />
                 <em>Example: date1=01/20/1998 </em> </p>
             <p>time1=hh:mm:ss - starting UT time to be examined. If date1 given, is applied to date1. If not, applies on the first day of the experiment. <br />
                 <em>Example: time1=13:30:00 </em> </p>
             <p>date2=mm/dd/yyyy - ending date to be examined. If time2 not given, defaults to 0 UT. <br />
                 <em>Example: date2=01/21/1998 </em> </p>
             <p>time2=hh:mm:ss - ending UT time to be examined - If date2 not given, refers to date1. If date1 and date2 not given, refers to 1st day. <br />
                 <em>Example: time2=15:45:00 </em> </p>
             <p><em><strong>In the follow arguments ranges are used. If any range value is not given, it may be used to indicate no lower or upper limit (but the comma is always required). Ranges are inclusive of the end points. </strong></em> </p>
             <blockquote>
               <h5>Geodetic altitude </h5>
             </blockquote>
             <p>z=lower alt limit1, upper alt limit1 [or lower alt limit2 , upper alt limit2 ...] (km) <br />
                 <em>Example 1: z=100,500 </em> This would limit the geodetic altitude to 100 to 500 km. <br />
                 <em>Example 2: z=100,200or300,400 </em> This would limit the geodetic altitude to 100 to 200 km or 300 to 400 km. <br />
                 <em>Example 3: z=,200or300,400 </em> Since the lower limit of the first range is missing, this would limit the geodetic altitude to anything below 200 km or from 300 to 400 km. </p>
             <blockquote>
               <h5>Azimuth (from -180 to 180) </h5>
             </blockquote>
             <p>az=lower az limit1, upper az limit1 [or lower az limit2 , upper az limit2 ...] (from -180 to 180 degrees) <br />
                 <em>Example 1: az=100,120 </em> This would limit the azimuth to 100 to 120 degrees. <br />
                 <em>Example 2: az=-180,-90or90,180 </em> This would limit the azimuth to between -180 and -90 degrees or to between 90 and 180 degrees. Note this allows a filter to go through 180 degrees. </p>
             <blockquote>
               <h5>Elevation (from 0 to 90) </h5>
             </blockquote>
             <p>el=lower el limit1, upper el limit1 [or lower el limit2 , upper el limit2 ...] (from 0 to 90) <br />
                 <em>Example 1: el=0,45 </em> This would limit the elevation from 0 to 45 degrees. </p>
             <blockquote>
               <h5>Pulse length (in seconds) </h5>
             </blockquote>
             <p>plen=lower pl limit1, upper pl limit1 [or lower pl limit2 , upper pl limit2 ...] (pulse len in sec) <br />
                 <em>Example 1: plen=,5e-4 </em> This would limit the pulse length to 5e-4 seconds or less. </p>
             <blockquote>
               <h5>Free form filters </h5>
             </blockquote>
             <p>filter=[mnemonic] or [mnemonic1,[+-*/]mnemonic2] , lower limit1 , upper limit1 [or lower limit2 , upper limit2 ...] (any number of filters may be added) <br />
                 <em>Example: filter=ti,500,1000or2000,3000 </em> Limits the data to points where Ti is between 500 and 1000 degrees or between 2000 and 3000 degrees. Note that the units are always those of the Cedar standard. <br />
                 <em>Example: filter=gdalt,-,sdwht,0, </em> This filter implies "gdalt - sdwht" must be greater than 0.0. Since sdwht is shadow height (the distance above any point on the earth where the sun is first visible), this filter implies that only data in direct sunlight will be displayed. <br />
                 <em>Example: filter=ti,/,Dti,100, </em> Limits the data to points where the ratio Ti/dTi is more than 100. </p>
             <blockquote>
               <h3>Format options </h3>
             </blockquote>
             <p>header=t or f (defaults to header=t, show headers at the beginning of each record) <br />
                 <em>Example: header=f </em> </p>
             <p>badval=bad value string (defaults to "missing") <br />
                 <em>Example: badval=n/a </em> </p>
             <p>assumed=assumed value string (defaults to "assumed") <br />
                 <em>Example: assumed=-32766 </em> </p>
             <p>knownbad=known bad value string (defaults to "knownbad") <br />
                 <em>Example: knownbad=WARNING-BADVALUE </em> </p>
             <p>mxchar=maximum characters per line (defaults to no maximum) <br />
                 <em>Example: mxchar=80 </em></p>
             <p>indSpatialParms=&lt;comma separated list of parms&gt;.  Used only if saving to an hdf5 or netCDF4 file.  If not given,<br />
             the default is to use the independent parms in the original file. Ignored if only 1D parms requested.</p>
             <p>Example: <code>isprint file=/opt/madrigal/experiments/1998/mlh/20jan98/mil980120g.003.hdf5 date1=01/20/1998 time1=15:00:00 date2=01/20/1998 time2=16:00:00 z=200,300or500,600 badval=noData filter=gdalt,-,sdwht,0, filter=ti,500,1000 uth gdalt gdlat glon ti te </code></p>
             <p>This example would show data from mil980120g.003.hdf5 between 15 and 16 UT on 01/20/1998 where altitude is either between 200 and 300 km or between 500 and 600 km, and where gdalt-sdwht is greater than 0 (point is in sunlight), and where ti is between 500 and 1000. "noData" would be printed if data was not available. </p>
             <p>&nbsp;</p>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_links.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_links.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'dev_contents.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'dev_contents.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Command line interface to Madrigal<!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_links.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Creating direct links<!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'dev_contents.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Developer's toc <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/ad_links.html +7 -7

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>User access logging</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="admin.html" --><!-- InstanceParam name="href_next_top" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_back_top" type="text" value="ad_other.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="ad_other.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_prev_top" type="text" value="ad_other.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="ad_other.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="ad_isprint.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_logging.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_logging.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_isprint.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_isprint.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Creating direct links to experiments/files <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_logging.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->User access logging<!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_isprint.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Using isprint<!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">Creating direct links to experiments/files</h1>
             <p>There are times you as administrator might want to create urls that directly take a user to a particular experiment, or to a particular
             file within an experiment.  Below HOME refers to the url to your site's home page.  In all cases, if a user has not yet registered,
             they will first go to the register page, and then directly to the requested url.</p>
             <h3>To go directly to a particular Madrigal experiment, follow the example below:</h3>
             <pre>HOME/showExperiment?experiment_list=experiments/2017/arg/27jul17</pre>
             <h3>To go directly to a particular Madrigal experiment and activate the show plots/docs button, follow the example below:</h3>
             <pre>HOME/showExperiment?experiment_list=experiments/2017/arg/27jul17&show_plots</pre>
             <h3>To go directly to a particular Madrigal file, follow the example below:</h3>
             <pre>HOME/showExperiment?experiment_list=experiments/2017/arg/27jul17&file_list=one_ion_aro20170727topg.000.hdf5</pre>
             <h3>To go directly to a particular Madrigal file and activate the show plots/docs button, follow the example below:</h3>
             <pre>HOME/showExperiment?experiment_list=experiments/2017/arg/27jul17&file_list=one_ion_aro20170727topg.000.hdf5&show_plots</pre>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_logging.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_logging.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_isprint.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_isprint.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Creating direct links to experiments/files<!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_logging.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->User access logging<!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_isprint.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Using isprint <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/ad_logging.html +7 -7

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>User access logging</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="admin.html" --><!-- InstanceParam name="href_next_top" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_back_top" type="text" value="ad_other.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="ad_other.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_prev_top" type="text" value="ad_other.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="ad_other.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="ad_isprint.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_other.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_other.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_links.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_links.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->User access logging <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_other.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Other admin tasks <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_links.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Creating direct links<!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">User access logging</h1>
             <p>Madrigal now logs each time a user accesses data from a Madrigal data file. This log file is stored in <em>madroot</em>/metadata/userdata/access_&lt;YYYY&gt;.log. Each line in the log file has five comma-separated fields:</p>
             <ol>
               <li>User name</li>
               <li>User email</li>
               <li>User affiliation</li>
               <li>Time stamp &lt;YYYY-MM-DD HH-MM-SS&gt; </li>
               <li>Full path the Madrigal file accessed.    </li>
             </ol>
             <p>Sample:</p>
             <pre>Bill Rideout,brideout@haystack.mit.edu,MIT Haystack,2006-01-03 10-10-09,/opt/madrigal/experiments/2005/mlh/04sep05/mlh050904a.000.hdf5
             Bill Rideout,brideout@haystack.mit.edu,MIT Haystack,2006-01-03 10-10-10,/opt/madrigal/experiments/2005/mlh/04sep05/mlh050904b.000.hdf5
             Bill Rideout,brideout@haystack.mit.edu,MIT Haystack,2006-01-03 10-10-17,/opt/madrigal/experiments/2005/mlh/04sep05/mlh050904c.000.hdf5
             </pre>
             <p>When a user is accessing Madrigal through the web, they will be asked for this information the first time they use any Data Access <a href="wt_accessData.html"></a> page. No attempt is made to verify the data they enter. This data is then stored as a cookie, and information from that cookie is used for this logging.</p>
             <p>All the latest releases of the <a href="rt_introduction.html">remote API</a> also require the caller to supply these additional fields.  </p>
             <p>The log file will automatically roll over once a year.  </p>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_other.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_other.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_links.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_links.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->User access logging <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_other.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Other admin tasks <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_links.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Creating direct links<!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/ad_metadata.html +9 -9

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>Madrigal data model</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="admin.html" --><!-- InstanceParam name="href_next_top" type="text" value="ad_experiments.html" --><!-- InstanceParam name="href_back_top" type="text" value="ad_upgrade.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="ad_upgrade.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="ad_experiments.html" --><!-- InstanceParam name="href_prev_top" type="text" value="ad_upgrade.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="ad_experiments.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="ad_upgrade.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="ad_experiments.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_upgrade.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_upgrade.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_experiments.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_experiments.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->The Madrigal data model and metadata files <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_upgrade.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Upgrading Madrigal <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_experiments.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Madrigal data organization <!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">The Madrigal data model and metadata files </h1>
             <p align="left">Understanding the Madrigal data model is an important step in understanding how Madrigal works. There is a correspondence between each level of the data model and the metadata files that are found in the MADROOT/metadata directory. In this section we describe each level of the Madrigal data model and the corresponding metadata file.</p>
             <ul>
               <li><a href="#siteTab">Madrigal site</a></li>
               <li><a href="#instTab">Instrument</a></li>
               <li><a href="#instType">Instrument type</a></li>
               <li><a href="#expTab">Experiment</a></li>
               <li><a href="#fileTab">Experiment files</a></li>
               <li><a href="#parcods">Data parameters</a>
                 <ul>
                   <li><a href="#explanation">Parameter explanations</a></li>
                 </ul>
               </li>
               <li><a href="#madCatTab">Parameter categories</a></li>
               <li><a href="#typeTab">Data types (kindat)</a></li>
               <li><a href="#instParmTab">Instrument parameters</a></li>
               <li><a href="#instKindatTab">Instrument kindats</a></li>
               <li><a href="#instDataTab">Instrument data</a></li>
               <li><a href="#data">Madrigal files</a></li>
             </ul>
             <h4 align="left"><a name="siteTab" id="siteTab"></a>Madrigal site - siteTab.txt </h4>
             <p align="left">The highest level of Madrigal is a Madrigal site. A Madrigal site is one particular web site controlled by
             one particular group, that holds all their own data. While each Madrigal site stores their own data locally, they also share metadata with all the other sites. This makes it possible for users to search for data at all the Madrigal sites at once no matter which site they visit, and simply follow links to the Madrigal site that has the data they are interested in.</p>
             <p align="left">Metadata about all sites is stored in MADROOT/metadata/siteTab.txt. When new Madrigal sites are added, this table is updated and all Madrigal sites are notified so they can update this file. If a site is running Madrigal 2.5 or higher, this file will be automatically updated unless the file has been manually modified by the administrator in a way not reported to <a href="mailto:madrigal@haystack.mit.edu">OpenMadrigal administrator</a>. This file contains the following comma-separated fields: </p>
             <ul>
               <li>Site ID (e.g., 1) </li>
               <li>Site Name (e.g., Millstone Hill Observatory)</li>
               <li>Madrigal server (e.g., www.haystack.mit.edu).  If https, then you need to append https:// (e.g., https://www.haystack.mit.edu)</li>
               <li>Madrigal document root relative to server (e.g., madrigal)  Leave empty if not needed.</li>
               <li>Madrigal CGI directory relative to server (e.g., cgi-bin/madrigal) - This field is no longer used.</li>
               <li>Madrigal servlet directory relative to server (e.g., madrigal/servlets) - This field is no longer used. </li>
               <li>Contact name (e.g., John M. Holt)</li>
               <li>Contact Address 1 (e.g., MIT Haystack Observatory)</li>
               <li>Contact Address 2 (e.g., Route 40)</li>
               <li>Contact Address 3 (e.g., &quot;&quot; )</li>
               <li>Contact City (e.g., Westford)</li>
               <li>Contact State/Province (e.g., MA)</li>
               <li>Contact Postal Code (e.g., 01886)</li>
               <li>Contact Country (e.g., USA)</li>
               <li>Contact Telephone (e.g., 1-617-981-5624)</li>
               <li>Contact email  (e.g., mailto:jmh@haystack.mit.edu) Multiple addresses may be listed if separated by semicolons.</li>
               <li>Site version (e.g. 3.0) Version of Madrigal installed as period seperated integers. If not given, default is 2.6.</li>
             </ul>
             <h4><a name="instTab" id="instTab"></a>Instrument - instTab.txt </h4>
             <p>The next layer of the Madrigal data model is the instrument. All data in Madrigal is associated with one and only one instrument. Any given Madrigal site will hold data from one or more instruments. Since Madrigal focuses on ground-based instruments, most instruments have a particular location associated with them. However, some Madrigal data is based on measurements from multiple instruments, and so have no particular location. Some examples are &quot;EISCAT Scientific Association IS Radars&quot; which combine data from the multiple EISCAT radars, and &quot;World-wide GPS Receiver Network&quot;, which consists of over a thousand individual GPS receivers distributed around the globe.</p>
             <p>Metadata about all instruments is stored in MADROOT/metadata/instTab.txt. When new Madrigal instruments are added, this table is updated and all Madrigal sites are notified so they can update this file.  If a site is running Madrigal 2.5 or higher, this file will be automatically updated unless the file has been manually modified by the administrator in a way not reported to <a href="mailto:madrigal@haystack.mit.edu">OpenMadrigal administrator</a>. This instrument code list is usually consistent with the Cedar instrument list. This file contains the following comma-separated fields: </p>
             <ul>
               <li>Instrument Code (e.g., 30) </li>
               <li>Instrument 3-letter Mnemonic - either of second two characters may also be numbers (e.g., mlh or p4p)</li>
               <li>Instrument Name (e.g., Millstone Hill Incoherent Scatter Radar)</li>
               <li>Latitude (e.g., 42.5)</li>
               <li>Longitude (e.g., -71.9)</li>
               <li>Altitude in km above sea level (e.g., 0.146)</li>
               <li>Contact name (e.g., John M. Holt)</li>
               <li>Contact Address 1 (e.g., MIT Haystack Observatory)</li>
               <li>Contact Address 2 (e.g., Route 40)</li>
               <li>Contact Address 3 (e.g., &quot;&quot; )</li>
               <li>Contact City (e.g., Westford)</li>
               <li>Contact State/Province (e.g., MA)</li>
               <li>Contact Postal Code (e.g., 01886)</li>
               <li>Contact Country (e.g., USA)</li>
               <li>Contact Telephone (e.g., 1-617-981-5625)</li>
               <li>Contact email (e.g., mailto:jmh@haystack.mit.edu)</li>
               <li>Instrument category id (e.g., 6)</li>
             </ul>
             <p>&nbsp;</p>
             <h4><a name="instType" id="instType"></a>Instrument type - instType.txt </h4>
             <p>The instrument type table lists categories of instruments, to allow the user to search instruments more easily.  If a site is running Madrigal 2.5 or higher, this file will be automatically updated unless the file has been manually modified by the administrator in a way not reported to <a href="mailto:madrigal@haystack.mit.edu">OpenMadrigal administrator</a>. This file contains the following comma-separated fields: </p>
             <ul>
               <li>Instrument category id (e.g., 6) </li>
               <li>Instrument category description (e.g., Incoherent Scatter Radar) </li>
             </ul>
             <p>&nbsp;</p>
             <h4><a name="expTab" id="expTab"></a>Experiment - expTab.txt </h4>
             <p>All the data from a given instrument is organized into experiments. An experiment consists of data from a single instrument covering a limited period of time, and, as a rule, is meant to address a particular scientific goal. Madrigal makes the assumption that instruments may be run in different modes, and so the data generated may vary from one experiment to another. By organizing one instrument's data into experiments, the purpose and limitations of each experiment can be made clearer. As a Madrigal administrator, you can also provide  users with supplemental plots and documentation about that experiment, in addition to the standard Madrigal data files. See the section on <a href="ad_createExp.html">creating and updating Madrigal experiments</a> for more information.</p>
             <p>Madrigal has a number of security codes for different types of experiments. Most experiments are public, which allows them to be accessed by everyone. An experiment can also be made private, which means that only users with set ranges of ip addresses can access them. (See<a href="ad_other.html#private"> Set private versus public access</a>.) Private experiments are never shared with other Madrigal sites. There is also a hidden experiment state to completely remove an experiment from access by Madrigal (if, for example, the data is discovered to be corrupt, but might be fixed in the future). </p>
             <p>There are also two  experiment states for archiving experiments. These are <em>public archive</em> and <em>private archive</em>. These states are meant to support the archiving of Madrigal data at a central Madrigal site, such as the one at NCAR. These archived experiments are duplicates of experiments found at other Madrigal sites. In general these archived experiments are ignored by any part of the user interface that searches all sites, because the user will only want to find the main data source. However, when the user interface is only accessing local data, these archived experiments will appear. A private archived experiment is subject to the same restriction as a regular private experiment. </p>
             <p>Metadata about all experiments is stored in MADROOT/metadata/expTab.txt. This file is automatically generated from individual expTab.txt files located in each experiment directory, as will be described in the <a href="ad_experiments.html">next section on experiment organization</a>. This file contains the following comma-separated fields: </p>
             <ul>
               <li>Experiment ID (auto-generated) </li>
               <li>Experiment URL (e.g., http://www.haystack.mit.edu/cgi-bin/madtoc/1997/mlh/03dec97g). Note this url is historical, and no longer works. </li>
               <li>Experiment Name (e.g., Wide Latitude Substorm Study)</li>
               <li>Site ID (e.g., 1)</li>
               <li>Start Date (YYYYMMDD) (e.g., 19971203) </li>
               <li>Start Time  (HHMMSS)(e.g., 011356)</li>
               <li>End Date (e.g., 19971205) (YYYYMMDD)</li>
               <li>End Time (e.g., 123525) (HHMMSS)</li>
               <li>Instrument Code (e.g., 30)</li>
               <li>Security Code (e.g., 0) - 0 for public, 1 for private, -1 for completely ignored, 2 for public archive, 3 for private archive. </li>
               <li>Principle Investigator (e.g., Phil Erickson) optional field - used to override the instrument PI </li>
               <li>Principle Investigator email (e.g., perickson@haystack.mit.edu) optional - PI must also be given </li>
             </ul>
             <p>There is also a file called MADROOT/metadata/expTabAll.txt which is also automatically generated. If differs from expTab.txt in that it contains experiment metadata from all Madrigal sites, not just the local one. Any remote experiment with a non-zero security code will be excluded. </p>
             <h4><a name="fileTab" id="fileTab"></a>Experiment Files - fileTab.txt </h4>
             <p>The data from a given experiment is stored in one or more experiment files. There are a number of reasons
             there may be more than one file for a given experiment. The first is that different kinds of data
             may be stored in different files.  Also, the experimental data may be analyzed in more than one way, leading
             to files with different sets of measured parameters. For these two cases, each file should have its own
             kindat code (see below).  Another reason for multiple files is that older, historical files can be
             kept on-line for reference purposes. </p>
-            <p>With Madrigal 3, the format of these files is Hdf5 as defined by the <a href="/static/CEDARMadrigalHdf5Format.pdf" target="_blank">CEDAR Madrigal Hdf5 file format</a>.  Each file may contain only one kindat. The category field is used to distinguish
+            <p>With Madrigal 3, the format of these files is Hdf5 as defined by the <a href="{% static 'CEDARMadrigalHdf5Format.pdf' %}" target="_blank">CEDAR Madrigal Hdf5 file format</a>.  Each file may contain only one kindat. The category field is used to distinguish
             files which are of historical interest only, e.g. a file which have been superseded by a file with an
             improved electron density calibration. In some cases there may be more than one up-to-date variant of a
             file, e.g. when different analysis options have been chosen. In this case one of these files is designated
             the default, and the others are designated as variants.</p>
             <p>Metadata about all experiment files is stored in MADROOT/metadata/fileTab.txt. This file is automatically generated from individual fileTab.txt files located in each experiment directory, as will be described in the <a href="ad_experiments.html">next section on experiment organization</a>. This file contains the following comma-separated fields: </p>
             <ul>
               <li>File Name (e.g., mil971203g.002) </li>
               <li>Experiment ID (e.g., 10000125) </li>
               <li>Data Type (e.g., 3001) </li>
               <li>Category (1=default, 2=variant, 3=history, 4=real-time)</li>
               <li>Size of File (e.g., 241920) </li>
               <li>File contains at least one Catalog Record File (0 for no, 1 for yes)</li>
               <li>File contains at least one Header Record File (0 for no, 1 for yes)</li>
               <li>Analysis/modify Date  (YYYYMMDD) (e.g., 19980101)</li>
               <li>Analysis/modify Time (HHMMSS) (e.g., 115131) </li>
               <li>File processing status description (preliminary, final, or any other description)</li>
               <li>Permission flag: 0 for public, 1 for private</li>
               <li>File analyst - who did the analysis of the data and created this file (e.g. John Holt) optional</li>
               <li>File analyst email (e.g., jholt@haystack.mit.edu) optional - File analyst must also be given </li>
             </ul>
             <p>There is also a file called MADROOT/metadata/fileTabAll.txt which is also automatically generated. If differs from fileTab.txt in that it contains experiment file metadata from all Madrigal sites, not just the local one. </p>
             <p>&nbsp;</p>
             <h4><a name="parcods" id="parcods"></a>Data parameters - parmCodes.txt </h4>
             <p>Any given file is made up a series of records holding measured parameters. Note that based on which parameters are in the file, Madrigal will automatically derive a large number of other parameters such as Kp and Magnetic field strength that aren't in the file itself. In the web browser, measured parameters are shown in bold, derived parameters in normal font. </p>
             <p> The metadata file parmCodes.txt contains information about what Madrigal or Cedar parameters are supported. It replaces the old format file parmCodes.txt used in Madrigal 2 because that old file limited the size of id codes with its column delimited format. . If a  parameter has a parameter code of 0, it cannot be stored in a Cedar file and is meant the be a derived value only. All Madrigal mnemonics must be unique. All non-zero parameter codes must be unique. If a new parameter is desired, it should be done in coordination with Bill Rideout at brideout@haystack.mit.edu.</p>
             <p>The file parmCodes.txt is comma delimited. </p>
             <ol>
               <li>Parameter Code (may be zero) </li>
               <li>Description (cannot include a comma)</li>
               <li>Units</li>
               <li>Mnemonic</li>
               <li>Format (Now use C-style formatting)</li>
               <li>Width</li>
               <li>Category Id (see madCatTab.txt) </li>
               <li>Mnemonic has Html description (1 or 0) - used to <a href="#explanation">display extra information</a> about the parameter </li>
               <li>Err mnemonic has Html description (1 or 0) - used to <a href="#explanation">display extra information</a> about the error parameter</li>
               <li>Is duplicate of code (optional field - used because old cedar format format had duplicate parameters to represent different dynamic range).</li>
             </ol>
             <blockquote>
               <h5><a name="explanation" id="explanation"></a>Parameter explanations</h5>
               <p>For parameters that cannot be fully described in the simple string in the parmCodes.txt file, additional explanation about the parameter or its corresponding error parameter can be added to the file madroot/doc/parmDesc.html. Simply create a new named anchor in that file, where the anchor name is the parameter mnemonic in all capitals. Following that, a description of arbitrary length can be given using html. Change one of the last two columns from 0 to 1 for that parameter in parmCodes.txt to let Madrigal know that this explanation exists. In general, the parameter order in parmDesc.html matches that of parmCodes.txt, but that is not a functional requirement. </p>
             </blockquote>
             <h4><a name="madCatTab" id="madCatTab"></a>Parameter categories - madCatTab.txt</h4>
             <p>The Madrigal category metadata file(madCatTab.txt) contains information about what categories Madrigal parameters belong in. The categories are similar to the Cedar categories, but do not follow them exactly. This file does not change. This file contains the following comma-separated fields: </p>
             <ul>
               <li>Category id (integers, starting at 0) </li>
               <li>Category name </li>
               <li>Minimum parameter code (integer). Used only for codes not listed in parmCodes.txt. If category doesn't have a range of codes, use -1. </li>
               <li>Maximum parameter code (integer). Used only for codes not listed in parmCodes.txt. If category doesn't have a range of codes, use -1.</li>
             </ul>
             <h4><a name="typeTab" id="typeTab"></a>Data type (kindat) table - typeTab.txt </h4>
             <p>The Madrigal data type (also called kind of data or kindat) metadata file(typeTab.txt) contains a list of all data
             types in the database. The purpose of the kindat is to uniquely identify the data processing algorithm used to compute
             the parameters in the associated Madrigal file. Each individual Madrigal site is free to update this table, as long as
             there are no duplicate kindats in your own file. It is best to simply keep the kindat codes in ascending order to aviod
             any chance of a duplicate. The kindat description must not contain a comma.</p>
             <ul>
               <li>Data Type Code (e.g., 3001) </li>
               <li>Data Type Brief Description (e.g., Basic Derived Parameters ) </li>
             </ul>
             <h4><a name="instParmTab" id="instParmTab"></a>Instrument parameter table - instParmTab.txt </h4>
             <p>The instrument parameter metadata file (instParmTab.txt) contains information about what measured parameters are found in the data for any given instrument. This data is used to support the global database query web page, and is rebuild by updateMaster.
             This file contains the following comma-separated fields:</p>
             <ul>
               <li>Instrument Code (e.g., 30) </li>
               <li>Parameter mnemonic list (e.g., range rangei az1 az2 el1 el2 pl snp3 chisq mhdqc1 systmp systmi power tfreq popl dpopl ti dti tr dtr vo dvo ph+ dph+ pm dpm fa dfa pnrmd pnrmdi vdopp dvdopp) </li>
             </ul>
             <h4><a name="instKindatTab" id="instKindatTab"></a>Instrument kindat table - instKindatTab.txt </h4>
             <p> The instrument kindat metadata file (instKindatTab.txt) contains information about what kindat codes are used with any given instrument. This data is used to support the global database query web page, and is rebuild by updateMaster. This file contains the following comma-separated fields:</p>
             <ul>
               <li>Instrument Code (e.g., 30) </li>
               <li>Kindat code list (e.g., 3408 13204 13210 3001) </li>
             </ul>
             <h4><a name="instDataTab" id="instKindatTab2"></a>Instrument data table - instData*.txt </h4>
             <p> The instrument data metadata files (instData.txt and instDataPriv.txt) contain information about for what years and instruments each Madrigal site has data. Effectively these file are summaries of data in expTabAll.txt, and only exist to speed UI performance. Note that there will be only one line per kinst value. If muliple sites have data for the same instrument, the rules as to which siteID is used are:</p>
             <ol>
               <li>Test experiments are ignored</li>
               <li>If the local site has that instrument, the local site id is always used (thus archive sites will show data as local).</li>
               <li>Non-local archived experiments are ignored in favor of the main site.</li>
               <li>If the instrument is at multiple non-archived, non-local sites, the site with the largest number of experiments is used.</li>
             </ol>
             <p>The two files instData.txt and instDataPriv.txt diff only in that private data is included in instDataPriv.txt, whereas public data isd included in both.</p>
             <p>This data is used to enhace performance of various web pages, and is rebuild by updateMaster. </p>
             <p>This file contains the following comma-separated fields:</p>
             <ul>
               <li>Site ID (eg, 10)</li>
               <li>Instrument Code (e.g., 30) </li>
               <li>Year for whihc there is data list (e.g., 1998 1999 2002) </li>
             </ul>
             <p>&nbsp;</p>
             <h4><a name="data" id="data"></a>File data </h4>
-            <p>The bottom level of the Madrigal data model is of course the data itself. With Madrigal 3.0 and beyond, the actual file format is Hdf5 that follows the rules defined in the <a href="/static/CEDARMadrigalHdf5Format.pdf" target="_blank">CEDAR Madrigal Hdf5 format</a> document. A Madrigal file is made up of a series of records, each with a start and stop time, representing the integration period of measurement (Madrigal tries to enforce the idea that all measurements take a finite time, but sometimes the start time = the stop time).</p>
+            <p>The bottom level of the Madrigal data model is of course the data itself. With Madrigal 3.0 and beyond, the actual file format is Hdf5 that follows the rules defined in the <a href="{% static 'CEDARMadrigalHdf5Format.pdf' %}" target="_blank">CEDAR Madrigal Hdf5 format</a> document. A Madrigal file is made up of a series of records, each with a start and stop time, representing the integration period of measurement (Madrigal tries to enforce the idea that all measurements take a finite time, but sometimes the start time = the stop time).</p>
             <p>Each Cedar parameter can also have an associated error value. This error value can have the special values &quot;missing&quot;, &quot;assumed&quot;, or &quot;known bad&quot;. If an error parameter is &quot;assumed&quot;, the implication is that the measured value itself is assumed, and does not represent a measured value. If the error value is &quot;known bad&quot;, the measured data is known to have a problem.</p>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_upgrade.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_upgrade.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_experiments.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_experiments.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->The Madrigal data model and metadata files <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_upgrade.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Upgrading Madrigal <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_experiments.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Madrigal data organization <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/ad_other.html +7 -7

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>Other administrative tasks</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" -->
             <style type="text/css">
             <!--
             .style1 {font-family: "Courier New", Courier, monospace}
             -->
             </style>
             <!-- InstanceEndEditable -->
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="admin.html" --><!-- InstanceParam name="href_next_top" type="text" value="ad_logging.html" --><!-- InstanceParam name="href_back_top" type="text" value="ad_createExp.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="ad_createExp.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="ad_logging.html" --><!-- InstanceParam name="href_prev_top" type="text" value="ad_createExp.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="ad_logging.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="ad_createExp.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="ad_logging.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_createExp.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_createExp.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_logging.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_logging.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Other administrative tasks <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_createExp.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Creating Madrigal experiments <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_logging.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->User access logging  <!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">Other administrative tasks</h1>
             <p>Some other tasks a Madrigal administrator might need to do:</p>
             <ul>
               <li><a href="#cached_files">Create cached text or netCDF4 versions of CEDAR Madrigal Hdf5 files</a></li>
               <li><a href="#private">Set private versus public access for Madrigal data files</a></li>
               <li><a href="#links">Modifying the Madrigal homepage</a></li>
               <li><a href="#madrigal_cfg">Modify settings in the madrigal.cfg file</a></li>
               <li><a href="#siteSpecific">Add documentation specific to your site to Madrigal documentation page</a></li>
               <li><a href="#rules">Add site-specific  rules-of the-road to the Madrigal experiment page</a></li>
               <li><a href="#static">Add static pages to your Madrigal site</a></li>
               <li><a href="#copy_exp">Copy entire experiment directories from one Madrigal site to another</a></li>
               <li><a href="#updateExpTimes">Reset experiment start and end times according to data in the experiment files</a></li>
               <li><a href="#register">Registering interest in an experiment or an intrument</a></li>
               <li><a href="#rebuilding">Rebuilding the madrigal python library</a></li>
               <li><a href="#experiments">Mounting additional hard drives to expand the experiments disc capacity</a></li>
               <li><a href="#throttle">Throttling admin emails if too many are sent</a></li>
               <li><a href="#convert">Converting from http to https</a></li>
             </ul>
             <p>Contact the <a href="mailto:madrigal@haystack.mit.edu">OpenMadrigal administrator</a> <a href="mailto:brideout@haystack.mit.edu"></a> if some other administrative issue arises. </p>
             <h4><a name="cached_files" id="cached_files"></a>Create cached text or netCDF4 versions of CEDAR Madrigal Hdf5 files</h4>
             <p>When users download ascii or netCDF4 versions of CEDAR Madrigal Hdf5 files as is (that is, just the parameters in the file without filtering), these alternative file formats by default are dynamically created. If this takes too long, the Madrigal admistrator can speed that up by creating cached files in the &lt;<em>experiment directory</em>&gt;/overview directory. The cached text file has <em>'.txt.gz</em>' appended to the basename of the CEDAR Madrigal Hdf5 file, and the netCDF4 file has '<em>.nc</em>' appended to the basename of the CEDAR Madrigal Hdf5 file.  These cached files are created with the $MADROOT/bin/createCachedFiles.py script. Here's the usage:</p>
             <pre>
             createCachedFiles.py [--excludeText --excludeNetCDF4 --inst=<instList>  --path=<expPath>
             --includeNonDefault  --overwrite --includeGeo --numCPU=<numCPU> -h --help]
             By default, both text and netCDF4 files created.  Use --excludeText or --excludeNetCDF4 to only create one type.
             By default all instruments will be included.  Use --inst=<comma delimited kinst list> to only include some instruments.
             By default, all experiment directories will be included.  Use --path to limit to a particular directory and all subdirectories.
             By default only default files will be cached.  Use --includeNonDefault to include all files.
             Use --overwrite to overwrite all Hdf5 cached files. Default is to skip existing cached files.
             Set --includeGeo to also convert geophysical files. Default is to skip them.
             numCPU by default is the maximum of (1, numCPUs available - 2).  Use --numCPU to override, but still will not be highter than default.
             -h or --help - print usage and exit
             </pre>
             <h4><a name="private" id="private2"></a>Set private versus public access for Madrigal data files</h4>
             <p>This new feature of Madrigal allows data files to be made either publicly available, or restricted to a limited set of IP address listed in a file. </p>
             <p>To disable this feature and make all your data public, run the following from the $MADROOT directory: </p>
             <pre>$MADROOT/bin/setAccess $MADROOT/experiments public </pre>
             <p>To enable this feature, you must first create a file called "trustedIPs.txt" under MADROOT. This file should contain the IP addresses of hosts considered to be part of the private group, or partial IPs if whole sub-nets should be included. This file is not created during installation. Anyone whose browser's IP matches this list will be able to view files marked as private. For example, if trustedIPs.txt contains the line 132.197.*, any IP address that begins 132.197 will have private access. </p>
             <p>Also, if the fileTab.txt file for that experiment can be overwritten by the web server, anyone whose browser's IP matches this list will be able to to change the access of any file between public and private from the madExperiments listing page. </p>
             <p>To change a large number of experiments to be either public or private, run the following script from the $MADROOT directory: </p>
             <pre>$MADROOT/bin/setAccess dirPath [public || private] </pre>
             <p>where dirPath is the full path name of any directory in $MADROOT/experiments, and the second argument is either public or private. This script will set all experiments in dirPath and below to be public or private. </p>
             <p>The access permission for any given file is set in the fileTab.txt file. See <a href="ad_metadata.html">metadata documentation </a> for details. </p>
             <h4><a name="links" id="links"></a>Modifying the Madrigal homepage</h4>
             <p>You can easily modify the Madrigal homepage of you site by modifying the template file $MADROOT/source/madpy/djangoMad/madweb/templates/madweb/index.html.</p>
             <h4><a name="madrigal_cfg" id="madrigal_cfg"></a>Modify settings in the madrigal.cfg file</h4>
             <p>The following settings in the <em>madroot</em>/madrigal.cfg file can be modified at any time and the changes will take effect immediately:</p>
             <ul>
               <li>CONTACT - Mailto link of contact person(s) for this madrigal installation. Multiple email addresses may be included if separated by commas. </li>
               <li>MAILSERVER - Name of mailserver (possibly localhost if running sendmail) </li>
               <li>NOTESMANAGER - If you want someone to be notified whenever a user adds a note to an experiment, uncomment this optional line and add the email address. See below for a discussion of the optional notes feature and how to configure it after installation.</li>
               <li>HTMLSTYLE - Body style of html pages </li>
               <li>INDEXHEAD - Heading in the top-level Madrigal page </li>
             </ul>
             <h4><a name="siteSpecific" id="siteSpecific"></a>Add documentation specific to your site to Madrigal documentation page</h4>
             <p>If you want to add any documentation pages specific to your site to the Madrigal documentation pages, simply put them at a url where they can be indexed. Then edit the file MADROOT/source/madpy/djangoMad/madweb/templates/madweb/madContents.html to modify the line</p>
             <pre>&lt;a href=&quot;#&quot;&gt;</pre>
             <p>to replace # with the url where your site specific documentation is.</p>
             <h4><a name="rules" id="rules"></a>Add site-specific  rules-of the-road to the Madrigal experiment page</h4>
             <p>By default, users see only the Cedar rules-of-the-road on the data access page when they first enter the Madrigal site. If you want your users to see rules-of the-road specific to your Madrigal site when the reach the Madrigal experiment page, simply create a text file with your rules called <strong>local_rules_of_the_road.txt</strong> in the <em>madroot</em> directory. </p>
             <h4><a name="static" id="static"></a>Add static pages to your Madrigal site</h4>
             <p>Soemtimes its helpful to add static pages to your Madrigal site, such as a page describing your instrument, that you can then simply reference from each individual experiment page.  To do this, simply copy the static file to
             MADROOT/source/madpy/djangoMad/madweb/static/siteSpecific, and use the url "/static/siteSpecific/[filename]" to refer to it.</p>
             <h4><a name="copy_exp" id="copy_exp"></a>Copy entire experiment directories from one Madrigal site to another</h4>
             <p> If you want to copy data from one Madrigal site into yours (such as is done during the standard installation with the test data from Haystack) copy all the desired data from another Madrigal site into the appropriate directory in $MADROOT/experiments. Then follow these steps: </p>
             <ol>
               <li>cd $MADROOT </li>
               <li>./configureExperiments </li>
               <li>$MADROOT/bin/updateMaster </li>
             </ol>
             <p>The script configureExperiments automatically edits the metadata files, changing the site id to your site id. This same procedure also works for <a href="#experiments">moving experiments between experiments[0-9]* directories</a>.</p>
             <h4><a name="updateExpTimes" id="updateExpTimes"></a>Reset experiment start and end times according to data in the experiment files</h4>
             <p>Sometimes the experiment start and end times in the metadata (the expTab.txt file) are manually edited, and do not match the start and end times of the data found in the files. The script updateExpTimes.py will examine the start and end times of all the files in an experiment, and set the experiment metadata start and end times to be the earliest and latest times found. Usage:</p>
             <pre>$MADROOT/bin/updateExpTimes.py [experiment_directory]</pre>
             <p>If optional argument <em>experiment_directory</em> given, then it will only update all experiments found in that directory. Default is to update the entire database. Only default or real time files are used to determine the times. Example:</p>
             <pre>$MADROOT/bin/updateExpTimes.py $MADROOT/experiments/1998</pre>
             <p>will update all experiment times for the year 1998.  </p>
             <p>&nbsp; </p>
             <h4><a name="register" id="register"></a>Registering interest in an experiment or an instrument</h4>
             <p>With Madrigal 2.6, users can register interest in an existing experiment or in an instrument.  When a data file is updated
             in that experiment using the standard admin scripts, by default all users registered for that experiment or instrument
             are sent an email.  To ensure that is possible, you simply need to make sure the files
             <em>$MADROOT/metadata/userdata/regExp.txt</em> and <em>$MADROOT/metadata/userdata/regExp.txt</em> are writable by the web server. If you get a request from a user to unregister them from an experiment or an instrument, simply delete that line with their email from that file. With Madrigal 3.0, you can also use the utility<em> $MADROOT/bin/registrationAdmin.py</em>. Usage is:</p>
             <pre>registrationAdmin.py [--unregister | --register]
              [--inst=&lt;kinst&gt; | --exp=&lt;expDir&gt;] userEmail</pre>
             <pre>Either unregister or register must be set.
                Either --inst=&lt;instrument code&gt; or --exp=&lt;expDir&gt; must be set.
                expDir is in form &lt;experiments/2010/mlh/18jan10&gt;
             </pre>
             <h4><a name="rebuilding" id="rebuilding"></a>Rebuilding the madrigal python library</h4>
             If for any reason you rebuild the madrigal python library by running <em>MADROOT/bin/python setup.py install</em> in the MADROOT/sopurce/madpy directory, you will need to restart the web server after you are done.
             <h4><a name="experiments" id="experiments"></a>Mounting additional hard drives to expand the experiments disc capacity</h4>
             <p>With Madrigal 2.6, administrators can expand the disc space available for experiments by mounting a directory named <em>experiments[0-9]*</em> in the Madroot directory. For example, you can add a directory called <em>experiments2</em> in the Madroot directory and use it for a mount point for additional space for Madrigal experiments. After you create this additional mount, you will need to create a soft link in your web server document root with a soft link to that new directory. For example, say you do the following:</p>
             <ul>
               <li>You create a new mount called <em>experiments2</em> in your Madroot directory<em>.</em></li>
               <li>Be sure to set the permission of this new directory so that the Madrigal administrator and the web server can read and write in it.</li>
               <li>You need to create a soft link from &lt;madroot&gt;/source/madpy/djangoMad/madweb/static to &lt;madroot&gt;/experiments2. For example, <em>cd /opt/madrigal3/source/madpy/djangoMad/madweb/static</em> and then <em>ln -s /opt/madrigal3/experiments2 experiments2</em>.</li>
             </ul>
             <p>You can now make use of this new directory in two ways:</p>
             <ol>
               <li>You can move experiments or whole directory trees of experiments between different <em>experiments[0-9]*</em> directrories as described in <a href="#copy_exp">Copy entire experiement directories</a> section (remember to run configureExperiments and updateMaster afterwards). Note, however, the experiments with geophysical data should not be moved (years 1950, 1957, and 1963).</li>
               <li>When running the scripts createExpWithFile.py or createRTExp.py, use the <em>--experimentsDirNum</em> argument to choose the new directory to use. By default the base <em>experiments</em> directory will be used. In the example above, the option <em>--experimentsDirNum</em>=2 would cause <em>experiments2</em> to be used.</li>
             </ol>
             <p>&nbsp;</p>
             <h4><a name="throttle" id="throttle"></a>Throttling admin emails if too many sent</h4>
             <p>If you receive too many emails, you can use a third party tool to throttle the amount.  The tool I have used successfully is django-email-throttler,
             which is described at https://github.com/robert-kisteleki/django-email-throttler.  To install, use pip and then edit your settings_production.py file:</p>
             <pre>pip install django-email-throttler</pre>
             <p>Then add the following lines to the end of your file MADROOT/source/madpy/djangoMad/djangoMad/settings_production.py.
             The top lines can be adjusted to set exactly how many emails you get, but these numbers should work fine.  When done, you will
             need to restart apache for the changes to take affect.</p>
             <pre>
             # stuff for email throttling and their defaults
             EMAILTHROTTLER_TMPDIR = '/tmp'
             EMAILTHROTTLER_PREFIX = 'emailthrottler-'
             EMAILTHROTTLER_INTERVAL = 600
             EMAILTHROTTLER_TRUNCATE_SUBJECT = None # 128 is also ok
             EMAILTHROTTLER_SUBJECT_THRESHOLD = 3 # 0 for no-check
             EMAILTHROTTLER_OVERALL_THRESHOLD = 6 # 0 for no-check
             LOGGING = {
                 'version': 1,
                 'disable_existing_loggers': True,
                 'handlers': {
                     'mail_admins': {
                         'level': 'ERROR',
                         'class': 'django.utils.log.AdminEmailHandler',
                         'email_backend': 'django_email_throttler.throttler.ThrottledEmailBackend',
                         'include_html': False,
                     }
                 },
                 'loggers': {
                     'django': {
                         'handlers': ['mail_admins'],
                         'level': 'ERROR',
                         'propagate': True,
                     },
                 }
             }
             </pre>
             <h4><a name="convert" id="convert"></a>Converting from http to https</h4>
             <p>The following are the steps needed to change an existing Madrigal site from http to https</p>
             <ol>
             	<li>In $MADROOT/metadata/siteTab.txt, include https:// in the third field of your site.  For example, change millstone.haystack.mit.edu to https://millstone.haystack.mit.edu</li>
             	<li>Change the MAD<b></b>SERVER line in $MADROOT/madrigal.cfg to include https://  For example, change millstone.haystack.mit.edu to https://millstone.haystack.mit.edu</li>
             	<li>cd $MADROOT/source/madpy</li>
             	<li>$MADROOT/bin/python setup.py install</li>
             	<li>$MADROOT/configureExperiments</li>
             	<li>$MADROOT/bin/updateMaster</li>
             	<li>Let Bill Rideout (brideout@mit.edu) know about the change.</li>
             </ol>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_createExp.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_createExp.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_logging.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_logging.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Other administrative tasks <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_createExp.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Creating Madrigal experiments <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_logging.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->User access logging  <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/ad_upgrade.html +7 -7

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>Upgrading Madrigal</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="admin.html" --><!-- InstanceParam name="href_next_top" type="text" value="ad_metadata.html" --><!-- InstanceParam name="href_back_top" type="text" value="ad_install.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="ad_install.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="ad_metadata.html" --><!-- InstanceParam name="href_prev_top" type="text" value="ad_install.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="ad_metadata.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="ad_install.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="ad_metadata.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_install.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_install.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_metadata.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_metadata.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Upgrading  to Madrigal 3<!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_install.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Installing Madrigal <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_metadata.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Madrigal data model <!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">Upgrading  Madrigal to version 3</h1>
             <p align="left">The following directions assume you have a version of Madrigal 2 already running, and you want to upgrade it to Madrigal 3. It is recommended you back up your existing Madrigal installation before proceeding. You will also need to upgrade slightly any loading programs you are running to create the new Madrigal 3 Hdf4 CEDAR format. Contact Bill Rideout or go to <a href="{% url 'docs' 'ad_createFiles.html' %}">Create Madrigal files</a> to learn more.</p>
             <h4 align="left">Prerequisites</h4>
             <p>With Madrigal 3, the installation uses a version of python 3 you install yourself. The easiest way I have found to install python with scientific tools is to use either apt-get (for ubuntu), or the Anaconda python distribution, or pip. The following python modules need to be installed:</p>
             <ol>
                   <li>django (version 1.11 or greater)</li>
                   <li>pip and setuptools</li>
                   <li>numpy</li>
                   <li>scipy</li>
                   <li>matplotlib</li>
                   <li>netCDF4</li>
                   <li>h5py</li>
                   <li>sqlparse</li>
                   <li>filelock</li>
                   <li>bootstrap3 (can be installed via <em>pip install django-bootstrap3</em>)</li>
                   <li>aacgmv2 (can be installed via <em>pip install aacgmv2</em>)<br />
                   </li>
             </ol>
             <p>In addition, you need to have Autotools (automake, autoconf, aclocal, libtoolize, autoheader) installed, along with h5repack (may be part of h5utils package).</p>
             <pre></pre>
             <h4 align="left">Installation instructions</h4>
             <ol>
               <li>Be sure the environmental variable MADROOT is set to your main Madrigal directory (where madrigal.cfg is locatied). </li>
               <li>Make sure $MADROOT/bin/python links to the version of python with the required modules listed above. For example, if you are using anaconda, you might run &lt;<em>ln -s //anaconda/bin/python $MADROOT/bin/python</em>&gt;.</li>
               <li>Download the latest Madrigal 3 distribution file, madrigal*.tar.gz from the <a href="http://cedar.openmadrigal.org/madrigalDownload/">OpenMadrigal distribution page</a> to MADROOT. </li>
               <li>tar -xzf madrigal*.tar.gz </li>
               <li>Configure your web server to run the Madrigal Django application. Instruction for apache can be found in the <a href="#django">Configuring Apache for a Madrigal Django Application</a> section below. If you are running a webserver other than apache, please consult the Django documentation for your particular webserver. </li>
               <li>Edit your file $MADROOT/metadata/siteTab.txt. The format of siteTab.txt is described <a href="ad_metadata.html#siteTab">here</a>. Note that if your site will be running https, the third field will begin https://.   Make sure the last column of that line for your site ends <em>,3.0</em> . This tells all sites that you site is now a Madrigal 3 site.  For example: <pre>999,mad31,localhost,madrigal,cgi-bin/madrigal,madrigal/servlets,Bill Rideout,MIT Haystack Observatory,Route 40,,Westford,MA,01886,USA,1-781-981-5624,brideout@haystack.mit.edu,3.0</pre></li>
               <li>Be sure to cd to MADROOT before running the following step. Then you should be able to complete the installation simply by typing <br />
                 <pre>bash installMadrigal  &amp;&gt; install.log &amp;</pre>
                 Help with any installation errors is available from the <a href="mailto:madrigal@haystack.mit.edu">OpenMadrigal administrator</a>. </li>
               <li>If there were no errors, your madrigal installation should be running at the url given by MADSERVERROOT. </li>
               <li>Set the script <em>madroot</em>/bin/updateMaster up as a cron job to run once a day. </li>
               <li>If you want to add any documentation pages specific to your site to the Madrigal documentation pages, see the <a href="ad_other.html#siteSpecific">other admin tasks</a> section of this manual.</li>
               <li>If you want to add your own rules of the road to the Madrigal experiment page, see the <a href="ad_other.html#rules">other admin tasks</a> section of this manual.</li>
             </ol>
             <p> </p>
             <h4><a name="edit" id="edit"></a>Editing the madrigal.cfg file </h4>
             The madrigal.cfg file contains all the configuration information specific to your installation. This section discusses how to edit that file for each parameter.  The madrigal.cfg.template file contains examples of each parameter.  For an upgrade, this file does not generally need to be edited.
             <ul>
               <li>MADROOT - Madrigal root directory (absolute). This must be set as an environmental variable. </li>
               <li>MAD<b></b>SERVER - Web server for accessing Madrigal.  For https, add https:// to the beginning.  If not given, uses http </li>
               <li>MAD<b></b>SERVERROOT - document virtual directory relative to MAD<b></b>SERVER.
                 If the full Madrigal Url is the same as the MAD<b></b>SERVER field
                 (for example, if the url is <i>http://madrigal.hao.ucar.edu/</i>), then set this field to a period. (Example: <i>MAD<b></b>SERVERROOT = .</i> ) </li>
               <li>SITEID - Site ID - Must be unique and same as in siteTab.txt </li>
               <li>HTMLSTYLE - Body style of html pages </li>
               <li>INDEXHEAD - Heading in the top-level Madrigal page </li>
               <li>CONTACT - Mailto link of contact person(s) for this madrigal installation. Multiple email addresses may be included if separated by commas. </li>
               <li>MAILSERVER - Name of mailserver (possibly localhost if running sendmail) </li>
               <li>PLOTBUTTONLABEL - By default the button to show additional documentation is labelled Plots/Docs. Change this line for a different label. <br>
               </li>
             </ul>
             <h4><a name="django" id="django"></a>Configuring Apache for a Madrigal Django Application</h4>
             <p>Some configuration of apache is required to run a Django application like Madrigal. If you are running a webserver other than apache, please consult the Django documentation for your particular webserver. We will configure apache to run Madrigal in mod_wsgi daemon mode for improved performance.</p>
             <p>The first step is to make sure mod_wsgi is installed as part of your apache webserver. If not, see mod_wsgi installation directions. Once installed, add the line</p>
             <pre>LoadModule wsgi_module modules/mod_wsgi.so</pre>
             <p>near the top of the httpd.conf file. Next add the follow section, with <em>MADROOT</em>, <em>MADSERVERROOT</em> and <em>YOUR_SERVER</em> replaced with values for your server from the madrigal.cfg file described below. Note that if <em>MADSERVERROOT</em> is zero length (that is, if the full Madrigal Url is the same as the MAD<b></b>SERVER field
               - for example, if the url is <i>http://madrigal.hao.ucar.edu/</i>) then /<em>MADSERVERROOT</em> just becomes / unlike in the madrigal.cfg file when it becomes a period.  Set <em>NUM_CPU</em> to about one half available on your server.</p>
             <pre>SetEnv PYTHONPATH <em>MADROOT</em>/source/madpy/djangoMad/
             WSGIDaemonProcess <em>YOUR_SERVER</em> python-path=<em>MADROOT</em>/source/madpy/djangoMad processes=<em>NUM_CPU</em> display-name=%{GROUP} lang='en_US.UTF-8' locale='en_US.UTF-8'
             WSGIProcessGroup <em>YOUR_SERVER</em>
             WSGIScriptAlias /<em>MADSERVERROOT</em> <em>MADROOT</em>/source/madpy/djangoMad/djangoMad/wsgi.py process-group=<em>YOUR_SERVER</em>
             Alias /static/ <em>MADROOT</em>/source/madpy/djangoMad/madweb/static/
             WSGIApplicationGroup %{GLOBAL}</pre>
             <pre> &lt;Directory <em>MADROOT</em>/source/madpy/djangoMad/madweb/static&gt;</pre>
             <blockquote>
               <pre>Require all granted</pre>
             </blockquote>
             <pre>
             &lt;/Directory&gt;
             &lt;Directory <em>MADROOT</em>/source/madpy/djangoMad/djangoMad&gt;</pre>
             <blockquote>
               <pre>&lt;Files wsgi.py&gt;  </pre>
               <blockquote>
                 <pre>Require all granted</pre>
               </blockquote>
               <pre>&lt;/Files&gt;</pre>
             </blockquote>
             <pre>&lt;/Directory&gt;</pre>
             <p>You may also need to add to your apache configuration file <em>SetEnv LD_LIBRARY_PATH $MADROOT/lib</em>, possibly along with other library paths.</p>
             <p>Finally, you need to edit the file <em>MADROOT</em>/source/madpy/djangoMad/djangoMad/settings_production_template.py, and save it as <em>MADROOT</em>/source/madpy/djangoMad/djangoMad/settings_production.py. The lines to be edited are:</p>
             <pre>SECRET_KEY = '*****'
             ALLOWED_HOSTS = ['madrigal3.haystack.mit.edu']
             ADMINS = (('Bill Rideout', 'brideout@haystack.mit.edu'),)
             EMAIL_HOST = 'hyperion.haystack.mit.edu'
             MANAGERS = (('Bill Rideout', 'brideout@haystack.mit.edu'),)
             STATIC_URL = '/static/'</pre>
             <p>The STATIC_URL line only needs to be edited if MAD<b></b>SERVERROOT is not empty; that is, if your madrigal is installed in a subdirectory.
             For example, if your url is http://madrigal.sri.com/madrigal, you would change that line to be STATIC_URL = '/madrigal/static/'.  But if your
             url is http://madrigal.sri.com, you would leave that STATIC_URL line as is.</p>
             <p>You can generate a new secret key for your site at http://www.miniwebtool.com/django-secret-key-generator/, which is recommended for security reasons.  The other lines are self-explanatory. </p>
             <p>When you are done, be sure to restart apache for the changes to take effect. Note that because this Madrigal Django application runs in daemon mode, it will be necessary to restart the web server if you ever update the python code.</p>
             <h3>Throttling Madrigal admin emails</h3>
             <p>Sometimes Madrigal users write scripts that cause numerous admin emails, and in addition malicious users can also generate numerous admin emails.
             If you would like to throttle the number of Madrigal admin emails you receive, see <a href="{% url 'docs' 'ad_other.html' %}#throttle">Throttling admin emails</a></p>
             <h4>&nbsp;</h4>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'ad_install.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_install.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'admin.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'ad_metadata.html' %}"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'ad_metadata.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Upgrading or moving Madrigal <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_install.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Installing Madrigal <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'admin.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Madrigal admin guide <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_metadata.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Madrigal data model <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/admin.html +1 -1

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>Madrigal administrator's guide</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
-            <link href="/madrigal/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="/madrigal{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="madContents.html" --><!-- InstanceParam name="href_next_top" type="text" value="ad_appropriate.html" --><!-- InstanceParam name="href_back_top" type="text" value="rr_fortran95.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="rr_fortran95.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="madContents.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="ad_appropriate.html" --><!-- InstanceParam name="href_prev_top" type="text" value="rr_fortran95.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="madContents.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="ad_appropriate.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="rr_fortran95.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="madContents.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="ad_appropriate.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
             	  <td width="5%"><a href="{% url 'docs' 'rr_fortran95.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
             	  <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
             	  <td width="5%"><a href="{% url 'docs' 'ad_appropriate.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Madrigal administrator's guide<!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'rr_fortran95.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Fortran95  remote API reference <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Doc home <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_appropriate.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Is Madrigal appropriate?<!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">Madrigal administrator's guide</h1>
             <p>This section of the Madrigal documentation is meant for people considering installing Madrigal to hold data from their instruments, or those who have already installed Madrigal and are responsible for administering or updating it. This guide describes how to determine whether Madrigal is right for your data, and how to install it if it is. It also discusses how to create Madrigal data files, and how to add them to Madrigal. </p>
             <ul>
               <li><a href="{% url 'docs' 'ad_appropriate.html' %}">Is Madrigal appropriate for my instrument(s)?</a></li>
               <li><a href="{% url 'docs' 'ad_install.html' %}">Installing Madrigal for the first time </a></li>
               <li><a href="{% url 'docs' 'ad_upgrade.html' %}">Upgrading Madrigal to the latest release</a></li>
               <li><a href="{% url 'docs' 'ad_metadata.html' %}">The Madrigal data model and metadata files</a></li>
               <li><a href="{% url 'docs' 'ad_experiments.html' %}">How Madrigal data is organized</a></li>
               <li><a href="{% url 'docs' 'ad_createFiles.html' %}">Creating Madrigal data files</a></li>
               <li><a href="{% url 'docs' 'ad_createExp.html' %}">Creating and updating Madrigal experiments</a></li>
               <li><a href="{% url 'docs' 'ad_other.html' %}">Other administrative tasks</a></li>
               <li><a href="{% url 'docs' 'ad_logging.html' %}">User access logging</a></li>
               <li><a href="{% url 'docs' 'ad_links.html' %}">Creating direct links to experiments/files</a></li>
               <li><a href="{% url 'docs' 'ad_isprint.html' %}">Using isprint for file quick looks</a></li>
             </ul>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
             	  <td width="5%"><a href="{% url 'docs' 'rr_fortran95.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
                 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
                 <td width="5%"><a href="{% url 'docs' 'ad_appropriate.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Madrigal administrator's guide<!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'rr_fortran95.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Fortran95 remote API reference <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Doc home <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'ad_appropriate.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Is Madrigal appropriate? <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/dev_contents.html +2 -2

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>Madrigal developer's guide</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
             <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="madContents.html" --><!-- InstanceParam name="href_next_top" type="text" value="madrigal/index.html" --><!-- InstanceParam name="href_back_top" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="madContents.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="madrigal/index.html" --><!-- InstanceParam name="href_prev_top" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="madContents.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="madrigal/index.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="madContents.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="madrigal/index.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
             	  <td width="5%"><a href="{% url 'docs' 'ad_isprint.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
             	  <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
             	  <td width="5%"><a href="{% url 'docs' 'madrigal/index.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Madrigal developer's guide <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_isprint.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Using isprint<!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Doc home <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'madrigal/index.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Internal python API<!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">Madrigal developer's guide</h1>
             <p>This section of the Madrigal documentation is meant for developers working to extend or modify Madrigal. It is not meant for users of Madrigal or Madrigal administrators. </p>
             <p>With the release of Madrigal 3.0, Madrigal has only a single python API. The C and Fortran code installed in Madrigal is purely scientific code used in the derivation engine, and is exposed only as a python extension, madrigal._derive.</p>
             <p>The web interface is now a Django web application, and no direct cgi scripts remain. The django application is contained in MADROOT/source/madpy/djangoMad.</p>
             <ul>
               <li><a href="madrigal/index.html">Internal Madrigal Python API</a>
                 <ul>
                   <li><a href="{% url 'docs' 'madrigal/admin.m.html' %}">madrigal.admin</a></li>
                   <li><a href="{% url 'docs' 'madrigal/cedar.m.html' %}">madrigal.cedar</a></li>
                   <li><a href="{% url 'docs' 'madrigal/data.m.html' %}">madrigal.data</a></li>
                   <li><a href="{% url 'docs' 'madrigal/derivation.m.html' %}">madrigal.derivation</a></li>
                   <li><a href="{% url 'docs' 'madrigal/isprint.m.html' %}">madrigal.isprint</a></li>
                   <li><a href="{% url 'docs' 'madrigal/metadata.m.html' %}">madrigal.metadata</a></li>
                   <li><a href="{% url 'docs' 'madrigal/openmadrigal.m.html' %}">madrigal.openmadrigal</a></li>
                   <li><a href="{% url 'docs' 'madrigal/ui/index.html' %}">madrigal.ui</a>
                     <ul>
                       <li><a href="{% url 'docs' 'madrigal/ui/madrigalPlot.m.html' %}">madrigal.ui.madrigalPlot</a></li>
                       <li><a href="{% url 'docs' 'madrigal/ui/userData.m.html' %}">madrigal.ui.userData</a></li>
                       <li><a href="{% url 'docs' 'madrigal/ui/web.m.html' %}">madrigal.ui.web</a></li>
                     </ul>
                   </li>
                 </ul>
               </li>
               <li><a href="{% url 'docs' 'dev_derivation.html' %}">Madrigal derivation engine</a></li>
-              <li><a href="/static/CEDARMadrigalHdf5Format.pdf">CEDAR Madrigal Hdf5 file format</a></li>
+              <li><a href="{% static 'CEDARMadrigalHdf5Format.pdf' %}">CEDAR Madrigal Hdf5 file format</a></li>
-              <li><a href="/static/cedarFormat.pdf">Deprecated Cedar file format</a></li>
+              <li><a href="{% static 'cedarFormat.pdf' %}">Deprecated Cedar file format</a></li>
             </ul>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
             	  <td width="5%"><a href="{% url 'docs' 'ad_isprint.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
             	  <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
             	  <td width="5%"><a href="{% url 'docs' 'madrigal/index.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Madrigal developer's guide<!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'ad_isprint.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Using isprint <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Doc home <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'madrigal/index.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Internal python API  <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/dev_derivation.html +10 -10

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>Madrigal Derivation Engine</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
-            <!-- InstanceParam name="href_up_top" type="text" value="dev_contents.html" --><!-- InstanceParam name="href_next_top" type="text" value="/static/CEDARMadrigalHdf5Format.pdf" --><!-- InstanceParam name="href_back_top" type="text" value="madrigal/ui/web.m.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="madrigal/ui/web.m.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="dev_contents.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="/static/CEDARMadrigalHdf5Format.pdf" --><!-- InstanceParam name="href_prev_top" type="text" value="madrigal/ui/web.m.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="dev_contents.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="/static/CEDARMadrigalHdf5Format.pdf" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="madrigal/ui/web.m.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="dev_contents.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="/static/CEDARMadrigalHdf5Format.pdf" -->
+            <!-- InstanceParam name="href_up_top" type="text" value="dev_contents.html" --><!-- InstanceParam name="href_next_top" type="text" value="{% static 'CEDARMadrigalHdf5Format.pdf' %}" --><!-- InstanceParam name="href_back_top" type="text" value="madrigal/ui/web.m.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="madrigal/ui/web.m.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="dev_contents.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="{% static 'CEDARMadrigalHdf5Format.pdf' %}" --><!-- InstanceParam name="href_prev_top" type="text" value="madrigal/ui/web.m.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="dev_contents.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="{% static 'CEDARMadrigalHdf5Format.pdf' %}" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="madrigal/ui/web.m.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="dev_contents.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="{% static 'CEDARMadrigalHdf5Format.pdf' %}" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'madrigal/ui/web.m.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'madrigal/ui/web.m.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'dev_contents.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'dev_contents.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="/static/CEDARMadrigalHdf5Format.pdf"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% static 'CEDARMadrigalHdf5Format.pdf' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Madrigal Derivation Engine<!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'madrigal/ui/web.m.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->madrigal.ui.web <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'dev_contents.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Developer's toc <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
-            <a class="sectref" href="/static/CEDARMadrigalHdf5Format.pdf"><!-- InstanceBeginEditable name="NextTitle" -->CEDAR Madrigal Hdf5 File Format<!-- InstanceEndEditable --></A></div>
+            <a class="sectref" href="{% static 'CEDARMadrigalHdf5Format.pdf' %}"><!-- InstanceBeginEditable name="NextTitle" -->CEDAR Madrigal Hdf5 File Format<!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <h1 align="center">Madrigal Derivation Engine</h1>
             <p>The Madrigal derivation is defined in the python module madrigal.derivation. In particular, that module begins with a collections.OrderedDict dictionary called MadrigalDerivedMethods. To add a new derivation method, simply define the new method in MadrigalDerivedMethods, and then implement it in C or python. If you add a new C method, you will also need to update the file source/madpy/madrigal/_derive.c, which is done simply by running <em>$MADROOT/bin/python $MADROOT/source/madpy/scripts/bin/updateMadDerivations.py</em>. This page goes into the derivation engine in detail.</p>
             <h4>MadrigalDerivedMethods</h4>
             <p>MadrigalDerivedMethods is a collections.OrderDict in madrigal.derivation. The name of each derivation method is the key, and so must be unique.  The value is a list with between two and four items.</p>
             <ol>
               <li>The first item is the input mnemonic(s).</li>
               <li>The second item is the output mnemonic(s).</li>
               <li>The optional third parameter is either 'python' or 'C'.  If only two parameters, 'C' is assumed. This determines whether the method is implementated on C (or Fortran wrapped in C), or python.</li>
               <li>The optional fourth parameter is a list of kinst values for which the derivation is valid (used in statistical models, etc).  This feature requires 'python' to be the implementation method.</li>
             </ol>
              <p>The order of these derivation methods matter - they will be called in a single pass from first to last.  The MadrigalDerivationPlan
                 determines which need to be called, and what parameters are derivable given the initial measured parameters.
                 Any parameter will be derived by the first available method that has that parameter as an output and
                 for which all input parameters are measured or themselves derivable.</p>
             <p>For the C derivation methods, the methods are implemented in source/madc/madrec/madDeriveMethods.c.  All methods must have a signature of the form:</p>
             <pre>int methodName(int inCount,
                double * inputArr,
                int outCount,
                double * outputArr,
                FILE * errFile)</pre>
             <p>where inCount is the number of input arguments, and inputArr is a double array of length inCount, with
                values for each input variable.  Likewise, outCount is the number of output arguments, and outputArr
                is already allocated double array of length outCount, where the C method sets the values for each
               output variable when it returns.  If values cannot be calulated, that output value is set to nan.</p>
             <p>When a new C derivation method is added, this method needs to be exposed to python. This is done through the file madpy/madrigal/_derive.c. However, you do not need to manually edit this file. Instead, cd $MADROOT/source/madpy/scripts/bin and then run:</p>
             <pre>$MADROOT/bin/python $MADROOT/source/madpy/scripts/bin/updateMadDerivations.py</pre>
             <p>This will create the file madpy/madrigal/_derive_new.c. Compare this new file with the existing file madpy/madrigal/_derive.c, and if the change looks reasonable, add it to source control.</p>
             <p>For the python derivation methods, all methods are defined in madrigal.derivation.MadrigalDerivationMethods
               in this module.  Each method has two arguments - a double array of input values of length the number of input
               variables, and the output array the length of the number of output variable.  As in the C, the output
               array is passed in to the derivation method preallocated.</p>
             <P>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'madrigal/ui/web.m.html' %}"><img src="/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'madrigal/ui/web.m.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'dev_contents.html' %}"><img src="/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'dev_contents.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="/static/CEDARMadrigalHdf5Format.pdf"><img src="/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% static 'CEDARMadrigalHdf5Format.pdf' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Madrigal C API<!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'madrigal/ui/web.m.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->madrigal.ui.web<!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'dev_contents.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Developer's toc<!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
-            <a class="sectref" href="/static/CEDARMadrigalHdf5Format.pdf"><!-- InstanceBeginEditable name="NextTitle2" -->CEDAR Madrigal Hdf5 File Format <!-- InstanceEndEditable --></A></div>
+            <a class="sectref" href="{% static 'CEDARMadrigalHdf5Format.pdf' %}"><!-- InstanceBeginEditable name="NextTitle2" -->CEDAR Madrigal Hdf5 File Format <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/filter_desc.html +1 -1

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <title>Isprint filters description</title>
-            <link href="/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="admin.html" --><!-- InstanceParam name="href_next_top" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_back_top" type="text" value="ad_other.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="ad_other.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_prev_top" type="text" value="ad_other.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="ad_isprint.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="ad_other.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="admin.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="ad_isprint.html" -->
             </head>
             <body>
             <h2>Isprint filter description</h2>
             	<center><h4>Creating filter strings for isprint</h4></center>
             	<p>Combine filters below into one string with spaces. Example:</p>
             <pre>
             	"date1=12/01/2005 time1=12:00:00 date1=12/02/2005 time1=08:00:00 el=0,45 filter=ti,500,1000"
             </pre>
             <h4>Time range</h4>
             <pre>
             date1=mm/dd/yyyy - starting date to be examined. If time1 not given, defaults to 0 UT.
             Example: date1=01/20/1998
             time1=hh:mm:ss - starting UT time to be examined. If date1 given, is applied to date1. If not, applies on the first day of the experiment.
             Example: time1=13:30:00
             date2=mm/dd/yyyy - ending date to be examined. If time2 not given, defaults to 0 UT.
             Example: date2=01/21/1998
             time2=hh:mm:ss - ending UT time to be examined - If date2 not given, refers to date1. If date1 and date2 not given, refers to 1st day.
             Example: time2=15:45:00
             </pre>
             <p>In the follow arguments ranges are used. If any range value is not given, it may be used to indicate no lower or upper limit (but the comma is always required). Ranges are inclusive of the end points.</p>
             <h4>Geodetic altitude</h4>
             <pre>
             z=lower alt limit1, upper alt limit1 [or lower alt limit2 , upper alt limit2 ...] (km)
             Example 1: z=100,500 This would limit the geodetic altitude to 100 to 500 km.
             Example 2: z=100,200or300,400 This would limit the geodetic altitude to 100 to 200 km or 300 to 400 km.
             Example 3: z=,200or300,400 Since the lower limit of the first range is missing, this would limit the geodetic altitude to anything below 200 km or from 300 to 400 km.
             </pre>
             <h4>Azimuth (from -180 to 180)</h4>
             <pre>
             az=lower az limit1, upper az limit1 [or lower az limit2 , upper az limit2 ...] (from -180 to 180 degrees)
             Example 1: az=100,120 This would limit the azimuth to 100 to 120 degrees.
             Example 2: az=-180,-90or90,180 This would limit the azimuth to between -180 and -90 degrees or to between 90 and 180 degrees. Note this allows a filter to go through 180 degrees.
             </pre>
             <h4>Elevation (from 0 to 90)</h4>
             <pre>
             el=lower el limit1, upper el limit1 [or lower el limit2 , upper el limit2 ...] (from 0 to 90)
             Example 1: el=0,45 This would limit the elevation from 0 to 45 degrees.
             </pre>
             <h4>Pulse length (in seconds)</h4>
             <pre>
             plen=lower pl limit1, upper pl limit1 [or lower pl limit2 , upper pl limit2 ...] (pulse len in sec)
             Example 1: plen=,5e-4 This would limit the pulse length to 5e-4 seconds or less.
             </pre>
             <h4>Free form filters</h4>
             <pre>
             filter=[mnemonic] or [mnemonic1,[+-*/]mnemonic2] , lower limit1 , upper limit1 [or lower limit2 , upper limit2 ...] (any number of filters may be added)
             Example: filter=ti,500,1000or2000,3000 Limits the data to points where Ti is between 500 and 1000 degrees or between 2000 and 3000 degrees. Note that the units are always those of the Cedar standard.
             Example: filter=gdalt,-,sdwht,0, This filter implies "gdalt - sdwht" must be greater than 0.0. Since sdwht is shadow height (the distance above any point on the earth where the sun is first visible), this filter implies that only data in direct sunlight will be displayed.
             Example: filter=ti,/,Dti,100, Limits the data to points where the ratio Ti/dTi is more than 100.
             </pre>

source/madpy/djangoMad/madweb/templates/madweb/madContents.html +1 -1

             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml">
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <title>Madrigal documentation - v3.0</title>
-            <link href="/madrigal/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="/madrigal{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             </head>
             <body>
             <center>
               <h1>Madrigal Database v3.2.1 Documentation - Contents</h1>
               <table width="100%" border="1">
                 <tr>
                   <td class="navigation"><a href="/">Home</a></td>
                 </tr>
               </table>
             </center>
             <hr size="4" />
             <ul>
               <li><a href="{% url 'docs' 'madIntroduction.html' %}">1. Brief history of Madrigal</a></li>
             </ul>
             <ul>
               <li><a href="{% url 'docs' 'whatsNew.html' %}">2. What's new in Madrigal 3.2.1</a></li>
             </ul>
             <ul>
               <li><a href="{% url 'docs' 'wt_usersGuide.html' %}">3. Madrigal user's guide (How do I access Madrigal data?) </a>
                 <ul>
                   <li><a href="{% url 'docs' 'wt_contents.html' %}">2.1 Web interface tutorial </a></li>
                   <li><a href="{% url 'docs' 'rt_contents.html' %}">2.2 Remote data access programming tutorial</a></li>
                   <li><a href="{% url 'docs' 'rr_contents.html' %}">2.3 Remote data access programming reference guide</a></li>
                 </ul>
               </li>
             </ul>
             <ul>
               <li><a href="{% url 'docs' 'admin.html' %}">4. Madrigal Administrator's Guide</a></li>
             </ul>
             <ul>
               <li><a href="{% url 'docs' 'dev_contents.html' %}">5. Madrigal Developer's Guide</a></li>
             </ul>
             <ul>
               <li><a href="{{ siteSpecific }}">6. Site specific documentation</a></li>
             </ul>
             <p>&nbsp;</p>
             </body>
             </html>

source/madpy/djangoMad/madweb/templates/madweb/madIntroduction.html +8 -8

             {% load static %}
             <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
             <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
             <head>
             <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
             <!-- InstanceBeginEditable name="doctitle" -->
             <title>Madrigal history</title>
             <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" -->
             <!-- InstanceEndEditable -->
-            <link href="/madrigal/static/madrigal.css" rel="stylesheet" type="text/css" />
+            <link href="/madrigal{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
             <style type="text/css">
             	html body {
             		background-color: {{bg_color}};
             	}
             </style>
             <!-- InstanceParam name="href_up_top" type="text" value="madContents.html" --><!-- InstanceParam name="href_next_top" type="text" value="whatsNew.html" --><!-- InstanceParam name="href_back_top" type="text" value="madContents.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="madContents.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="madContents.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="whatsNew.html" --><!-- InstanceParam name="href_prev_top" type="text" value="madContents.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="madContents.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="whatsNew.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="madContents.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="madContents.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="whatsNew.html" -->
             </head>
             <body>
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'whatsNew.html' %}"><img src="/madrigal/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'whatsNew.html' %}"><img src="/madrigal{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Brief history of Madrigal <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Doc home <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Doc home <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'whatsNew.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->What's new in Madrigal 3.0?  <!-- InstanceEndEditable --></A></div>
             <hr/>
             <!-- InstanceBeginEditable name="EditDoc" -->
             <center>
               <h1>Brief history of Madrigal </h1>
             </center>
             <p>Madrigal is a database of ground-based measurements and models of   the Earth's upper atmosphere and ionosphere. It is the community database of the   Coupling, Energetics and Dynamics of Atmospheric Regions (<a href="http://cedarweb.vsp.ucar.edu/wiki/index.php/Main_Page">CEDAR</a>) program, which   is devoted to the characterization and understanding of the atmosphere above   about 60 km, with emphasis on the various processes that determine the basic   structure and composition of the atmosphere, and on the mechanisms that couple   different atmospheric regions. Instruments developed or upgraded under CEDAR   include interferometers, spectrometers, imagers, lidars and medium,   high-frequency and incoherent scatter radars.  The success of   CEDAR has been due, in large measure, to its ability to encourage collaborative   efforts coalescing observations, theory and modeling. The CEDAR community   includes about 800 scientists and students from around the world.</p>
             <p>From the inception of the CEDAR program in 1988, there has been a   great concern among the members of the CEDAR community to make the data   collected by the CEDAR instruments easily accessible for joint studies.   Consequently, a high priority was placed on establishing a repository for CEDAR   data and model results. An incoherent scatter radar database had been   established at the National Center for Atmospheric Research (NCAR) in 1985, and   this evolved into the CEDAR Database in 1989. By the end of 1997, it had grown   to include data from 44 instruments and 16 models. Over 200 users have requested   information from the Database. In 2012, the Madrigal database and the CEDAR database were combined into a single database system, the Madrigal CEDAR database, based at MIT Haystack Observatory.</p>
-            <p>A central element of the CEDAR Database is a standard data format.   With Madrigal 3.0 the file format is now Hdf5, with a well-defined layout and parameters. This new CEDAR Hdf5 format is described <a href="/madrigal/static/CEDARMadrigalHdf5Format.pdf" target="_blank">here</a>. This format replaced the old <a href="/madrigal/static/cedarFormat.pdf">16 bit integer based format</a> that evolved from the format used by the earlier incoherent scatter   database, which in turn evolved from an earlier version of Madrigal developed at the MIT Haystack   Observatory in 1980. </p>
+            <p>A central element of the CEDAR Database is a standard data format.   With Madrigal 3.0 the file format is now Hdf5, with a well-defined layout and parameters. This new CEDAR Hdf5 format is described <a href="/madrigal{% static 'CEDARMadrigalHdf5Format.pdf' %}" target="_blank">here</a>. This format replaced the old <a href="/madrigal{% static 'cedarFormat.pdf' %}">16 bit integer based format</a> that evolved from the format used by the earlier incoherent scatter   database, which in turn evolved from an earlier version of Madrigal developed at the MIT Haystack   Observatory in 1980. </p>
             <p>Haystack maintains and develops  the Madrigal CEDAR database as an open-source project with community contributions.  With the Madrigal CEDAR database, the site owner stores only their own data, which they can add to or update at any time. However, because the Madrigal database shares its metadata with all other Madrigal sites, users browsing any Madrigal site can search for data at any other Madrigal site. In addition, a central archival Madrigal site (<a href="http://cedar.openmadrigal.org" target="_self">cedar.openmadrigal.org</a>) archives all Madrigal sites and stores data not stored at other Madrigal sites.</p>
             <p>Madrigal data are arranged into &quot;experiments&quot;, which may contain   data files, images, documentation, links, etc.   A key feature of Madrigal is its  seamless integration   of archival and real-time data. A realtime file on Madrigal is accessed in exactly the same way as any archival file.</p>
             <p>Madrigal has been installed at numerous locations in addition to   Millstone Hill, including EISCAT, SRI International, and Jicamarca. The inventories of   experiments available at each installation are available to the other   installations through shared metadata.  New Madrigal sites can be automatically added at any time.</p>
             <p>Madrigal is an open source project with a central <a href="http://cedar.openmadrigal.org/openmadrigal">developer's web site</a> and a <a href="http://atlas.haystack.mit.edu/cgi-bin/millstone_viewvc.cgi/openmadrigal/" target="_self">central repository</a>. A complete Subversion archive of all   Madrigal software, including software which is not included with the standard   distribution, is available at the developer's web site. There is also an Open Madrigal mailing list   and developer's forum. Any group wishing to install Madrigal to distribute their instrument's data is welcome to - see the http://cedar.openmadrigal.org/openmadrigal web site for details. The  <a href="http://atlas.haystack.mit.edu/cgi-bin/millstone_viewvc.cgi/openmadrigal/" target="_self">central repository</a> link is a place where all data from all Madrigal sites is archived. It can also be used to access data, although accessing the local sites is preferred.</p>
             <!-- InstanceEndEditable -->
             <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
               <tr>
-                <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal/static/previous.png" alt="previous" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal/static/up.png" alt="up" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
-                <td width="5%"><a href="{% url 'docs' 'whatsNew.html' %}"><img src="/madrigal/static/next.png" alt="next" width="32" height="32" /></a></td>
+                <td width="5%"><a href="{% url 'docs' 'whatsNew.html' %}"><img src="/madrigal{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
                 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Brief overview of Madrigal <!-- InstanceEndEditable --></td>
                 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
                 <td width="18%"><a href="/">Madrigal home</a></td>
               </tr>
             </table>
             <div class='online-navigation'>
             <b class="navlabel">Previous:</b>
             <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Doc Home <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Up:</b>
             <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Doc home <!-- InstanceEndEditable --></A>
             <b class="navlabel">&nbsp;&nbsp;Next:</b>
             <a class="sectref" href="{% url 'docs' 'whatsNew.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->What's new in Madrigal 3.0? <!-- InstanceEndEditable --></A></div>
             <hr/>
             <p>&nbsp;</p>
             </body>
             <!-- InstanceEnd --></html>

source/madpy/djangoMad/madweb/templates/madweb/madrigal/admin.m.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/madrigal/cedar.m.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/madrigal/data.m.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/madrigal/derivation.m.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/madrigal/index.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/madrigal/isprint.m.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/madrigal/metadata.m.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/madrigal/openmadrigal.m.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/madrigal/ui/index.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/madrigal/ui/madrigalPlot.m.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/madrigal/ui/userData.m.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/madrigal/ui/web.m.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rr_contents.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rr_fortran95.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rr_idl.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rr_matlab.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rr_python.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rr_webServices.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rt_contents.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rt_fortran95.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rt_idl.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rt_introduction.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rt_matlab.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rt_python.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/rt_webServices.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/whatsNew.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/wt_accessData.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/wt_contents.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/wt_dataOrg.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/wt_usersGuide.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/madweb/templates/madweb/wt_whatIsMadrigal.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/templates/base.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

source/madpy/djangoMad/templates/base_single.html 0 0

	1	NO CONTENT: modified file			NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff

General Comments 0

Write
Preview

You need to be logged in to leave comments. Login now

No TODOs yet

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages