##// END OF EJS Templates
DATABASES » madrigal
RSS
Fix static links in documentation
jespinoza -
r20:b42471e4ae5f
parent child
Show More
Show file before | Show file after | Hide comments
@@ -1,75 +1,75
1 1 {% load static %}
2 2
3 3 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
4 4 <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
5 5 <head>
6 6 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
7 7 <!-- InstanceBeginEditable name="doctitle" -->
8 8 <title>Madrigal administrator's guide</title>
9 9 <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
10 <link href="/madrigal{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
10 <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
11 11 <style type="text/css">
12 12 html body {
13 13 background-color: {{bg_color}};
14 14 }
15 15 </style>
16 16 <!-- 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" -->
17 17 </head>
18 18
19 19 <body>
20 20 <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
21 21 <tr>
22 22 <td width="5%"><a href="{% url 'docs' 'rr_fortran95.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
23 23 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
24 24 <td width="5%"><a href="{% url 'docs' 'ad_appropriate.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
25 25 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Madrigal administrator's guide<!-- InstanceEndEditable --></td>
26 26 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
27 27 <td width="18%"><a href="/">Madrigal home</a></td>
28 28 </tr>
29 29 </table>
30 30 <div class='online-navigation'>
31 31 <b class="navlabel">Previous:</b>
32 32 <a class="sectref" href="{% url 'docs' 'rr_fortran95.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Fortran95 remote API reference <!-- InstanceEndEditable --></A>
33 33 <b class="navlabel">&nbsp;&nbsp;Up:</b>
34 34 <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Doc home <!-- InstanceEndEditable --></A>
35 35 <b class="navlabel">&nbsp;&nbsp;Next:</b>
36 36 <a class="sectref" href="{% url 'docs' 'ad_appropriate.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Is Madrigal appropriate?<!-- InstanceEndEditable --></A></div>
37 37 <hr/>
38 38 <!-- InstanceBeginEditable name="EditDoc" -->
39 39 <h1 align="center">Madrigal administrator's guide</h1>
40 40 <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>
41 41 <ul>
42 42 <li><a href="{% url 'docs' 'ad_appropriate.html' %}">Is Madrigal appropriate for my instrument(s)?</a></li>
43 43 <li><a href="{% url 'docs' 'ad_install.html' %}">Installing Madrigal for the first time </a></li>
44 44 <li><a href="{% url 'docs' 'ad_upgrade.html' %}">Upgrading Madrigal to the latest release</a></li>
45 45 <li><a href="{% url 'docs' 'ad_metadata.html' %}">The Madrigal data model and metadata files</a></li>
46 46 <li><a href="{% url 'docs' 'ad_experiments.html' %}">How Madrigal data is organized</a></li>
47 47 <li><a href="{% url 'docs' 'ad_createFiles.html' %}">Creating Madrigal data files</a></li>
48 48 <li><a href="{% url 'docs' 'ad_createExp.html' %}">Creating and updating Madrigal experiments</a></li>
49 49 <li><a href="{% url 'docs' 'ad_other.html' %}">Other administrative tasks</a></li>
50 50 <li><a href="{% url 'docs' 'ad_logging.html' %}">User access logging</a></li>
51 51 <li><a href="{% url 'docs' 'ad_links.html' %}">Creating direct links to experiments/files</a></li>
52 52 <li><a href="{% url 'docs' 'ad_isprint.html' %}">Using isprint for file quick looks</a></li>
53 53 </ul>
54 54 <!-- InstanceEndEditable -->
55 55 <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
56 56 <tr>
57 57 <td width="5%"><a href="{% url 'docs' 'rr_fortran95.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
58 58 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
59 59 <td width="5%"><a href="{% url 'docs' 'ad_appropriate.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
60 60 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Madrigal administrator's guide<!-- InstanceEndEditable --></td>
61 61 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
62 62 <td width="18%"><a href="/">Madrigal home</a></td>
63 63 </tr>
64 64 </table>
65 65 <div class='online-navigation'>
66 66 <b class="navlabel">Previous:</b>
67 67 <a class="sectref" href="{% url 'docs' 'rr_fortran95.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Fortran95 remote API reference <!-- InstanceEndEditable --></A>
68 68 <b class="navlabel">&nbsp;&nbsp;Up:</b>
69 69 <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Doc home <!-- InstanceEndEditable --></A>
70 70 <b class="navlabel">&nbsp;&nbsp;Next:</b>
71 71 <a class="sectref" href="{% url 'docs' 'ad_appropriate.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Is Madrigal appropriate? <!-- InstanceEndEditable --></A></div>
72 72 <hr/>
73 73 <p>&nbsp;</p>
74 74 </body>
75 75 <!-- InstanceEnd --></html>
Show file before | Show file after | Hide comments
@@ -1,212 +1,213
1 1 {% comment %}
2 2 Written by Bill Rideout brideout@haystack.mit.edu
3 3
4 4 Template for file buttons in single experiment web interface
5 5
6 6 $Id: file_buttons.html 7319 2021-03-04 21:22:21Z brideout $
7 7 {% endcomment %}
8 8 <!-- file_buttons is its own row in main column -->
9 9 <div class="row">
10 10
11 11 <div class="btn-toolbar" style="margin: 0;">
12 12 <div class="btn-group">
13 13 <button class="btn btn-primary" id="show_plots" data-toggle="tooltip" data-original-title="Click this button to show plots and any other documentation associated with this experiment." data-placement="bottom">{{ plot_label | default:"Plots/docs"}}</button>
14 14 </div><!-- /btn-group -->
15 15 <div class="btn-group">
16 16 <button class="btn btn-primary dropdown-toggle my-dropdown" data-toggle="dropdown" title="Use this dropdown menu to download the file to your computer either as is (faster), or with selected parameters and filters (slower)." data-placement="right">Download file <span class="caret"></span></button>
17 17 <ul class="dropdown-menu">
18 18 <li><a href="javascript:downloadAsIs()" data-toggle="tooltip" data-original-title="Download the file in your choice of formats as is (faster than Select parameters/filters)." data-placement="right">As is</a></li>
19 19 <li><a href="javascript:getAdvanced('download')" data-toggle="tooltip" data-original-title="Download the file with the parameters (and possibly data filters) you select (slower than As is)." data-placement="right">Select parameters/filters</a></li>
20 20 </ul>
21 21 </div><!-- /btn-group -->
22 22 <div class="btn-group">
23 23 <button class="btn btn-primary dropdown-toggle my-dropdown" data-toggle="dropdown" id="print_file_button" title="Use this dropdown menu to print the file to your web browser either as is (faster), or with selected parameters and filters (slower)." data-placement="right">Print file <span class="caret"></span></button>
24 24 <ul class="dropdown-menu">
25 25 <li><a href="javascript:printAsIs()" data-toggle="tooltip" data-original-title="Print the file in your browser as is (faster than Select parameters/filters)." data-placement="right">As is</a></li>
26 26 <li><a href="javascript:getAdvanced('print')" data-toggle="tooltip" data-original-title="Print the file in your browser with the parameters (and possibly data filters) you select (slower than As is)." data-placement="right">Select parameters/filters</a></li>
27 27 <li><a href="javascript:listRecords()" data-toggle="tooltip" data-original-title="List the individual records in this file." data-placement="right">List records in file</a></li>
28 28 </ul>
29 29 </div><!-- /btn-group -->
30 30 <div class="btn-group">
31 31 <button class="btn btn-primary" id="show_info" data-toggle="tooltip" data-original-title="Click this button to show the descriptive text associated with the selected file." data-placement="bottom">View file info</button>
32 32 </div><!-- /btn-group -->
33 33 <div class="btn-group">
34 34 <button class="btn btn-primary" id="show_doi" data-toggle="tooltip" data-original-title="Click this button to show a full citation with a permanent url useful for citing this data file in a publication." data-placement="bottom">Cite this file</button>
35 35 </div><!-- /btn-group -->
36 36 </div><!-- /btn-toolbar -->
37 37
38 38 <script>
39 39 $('[data-toggle="tooltip"]').tooltip();
40 40 $('[data-toggle="tooltip"]').on('show.bs.tooltip', function() {
41 41 // Only one tooltip should ever be open at a time
42 42 $('.tooltip').not(this).hide();
43 43 });
44 44 $('.my-dropdown').dropdown();
45 45 $('.my-dropdown').tooltip();
46 46
47 47 $('#show_plots').on('click', function (e) {
48 48 var expID = '{{ form.exp_id.label }}';
49 var url = '{% url 'show_plots' %}' + '?experiment_list=' + expID;
49 var basename = '{{ form.basename.label }}';
50 var url = '{% url 'show_plots' %}' + '?experiment_list=' + expID + '&filename=' + basename;
50 51 // first delete all forms that are now out of date
51 52 divIndex = $(".single_form").index($( "#file_data" ))
52 53 $(".single_form").slice(divIndex).empty()
53 54 // second populate the file_data html if '0' not selected
54 55 if (expID != '0') {
55 56 $(".single_form").slice(divIndex,divIndex+1).load(url);
56 57 }
57 58 })
58 59
59 60 function downloadAsIs () {
60 61 var expID = '{{ form.exp_id.label }}';
61 62 var basename = '{{ form.basename.label }}';
62 63 var url = '{% url 'download_as_is' %}' + '?experiment_list=' + expID + '&file_list=' + basename;
63 64 // first delete all forms that are now out of date
64 65 divIndex = $(".single_form").index($( "#file_data" ))
65 66 $(".single_form").slice(divIndex).empty()
66 67 // second populate the download as is html if '0' not selected
67 68 if (basename != '0') {
68 69 $(".single_form").slice(divIndex,divIndex+1).load(url);
69 70 }
70 71 }
71 72
72 73 function getAdvanced (type) {
73 74 var filesize = parseInt({{ form.filesize.label }});
74 75 var size_mb = parseInt(filesize / (1024*1025));
75 76 if (size_mb > 50) {
76 77 alert("The file to be analyzed is " + size_mb + " MBs. Files greater than 50 MBs cannot be analyzed fast enough for a response via the web, and downloading the file directly is recommended. You can download the file using the Download File -> As Is selection.");
77 78 return;
78 79 }
79 80 if (size_mb > 10) {
80 81 var answer = confirm("The file to be analyzed is " + size_mb + " MBs. Files greater than 10 MBs can take a long time to analyze, and downloading the file directly is recommended. You can download the file instead by hitting Cancel, then using the Download File -> As Is selection.");
81 82 if(!answer) {
82 83 return;
83 84 }
84 85 }
85 86 var expID = '{{ form.exp_id.label }}';
86 87 var basename = '{{ form.basename.label }}';
87 88 var url = '{% url 'get_advanced' %}' + '?type=' + type + '&experiment_list=' + expID + '&file_list=' + basename;
88 89 // refresh page
89 90 window.location.href = url;
90 91 }
91 92
92 93 function printAsIs () {
93 94 var filesize = parseInt({{ form.filesize.label }});
94 95 var size_mb = parseInt(filesize / (1024*1025));
95 96 if (size_mb > 10) {
96 97 var answer = confirm("The file to be printed is " + size_mb + " MBs. Files greater than 10 MBs can be even larger when converted to ascii and crash your browser. Downloading the file directly is recommended. You can download the file instead by hitting Cancel, then using the Download File -> As Is selection.");
97 98 if(!answer) {
98 99 return;
99 100 }
100 101 }
101 102 var expID = '{{ form.exp_id.label }}';
102 103 var basename = '{{ form.basename.label }}';
103 104 var url = '{% url 'print_as_is' %}' + '?experiment_list=' + expID + '&file_list=' + basename;
104 105 // first delete all forms that are now out of date
105 106 divIndex = $(".single_form").index($( "#file_data" ))
106 107 $(".single_form").slice(divIndex).empty()
107 108 // second populate the print as is html if '0' not selected
108 109 if (basename != '0') {
109 110 $.ajax({url: url,
110 111 beforeSend: function () {
111 112 $("#print_file_button").html("Printing...");
112 113 },
113 114 success: function(result){
114 115 var resultArr = result.split(":");
115 116 var filesize = parseInt(resultArr[0]);
116 117 var mbytes = Math.floor(filesize/1000000);
117 118 if (mbytes > 50) {
118 119 var answer = confirm("The ascii file to be printed is " + mbytes + " MBs. Are you sure you want to print it in your browser? You can download the file as ascii instead by hitting Cancel, then using the Download file button.");
119 120 if(!answer) {
120 121 $("#print_file_button").html("Print File ");
121 122 return;
122 123 }
123 124 }
124 125 // if we made it here, its okay to load the text
125 126 url = url + '&text=' + resultArr[1];
126 127 $.ajax({url: url,
127 128 success: function(result){
128 129 $(".single_form").slice(divIndex,divIndex+1).html(result);
129 130 $("#print_file_button").html("Print File ");
130 131 },
131 132 });
132 133 },
133 134 error: function (xhr) {
134 135 $("#print_file_button").html("Print File ");
135 136 alert('Printing error: ' + xhr);
136 137 }
137 138 });
138 139 }
139 140 }
140 141
141 142 function listRecords() {
142 143 var expID = '{{ form.exp_id.label }}';
143 144 var basename = '{{ form.basename.label }}';
144 145 var url = '{% url 'list_records' %}' + '?experiment_list=' + expID + '&file_list=' + basename;
145 146 // first delete all forms that are now out of date
146 147 divIndex = $(".single_form").index($( "#file_data" ))
147 148 $(".single_form").slice(divIndex).empty()
148 149 // second populate the print as is html if '0' not selected
149 150 if (basename != '0') {
150 151 $.ajax({url: url,
151 152 beforeSend: function () {
152 153 $("#print_file_button").html("Listing...");
153 154 },
154 155 success: function(result){
155 156 var resultArr = result.split(":");
156 157 $(".single_form").slice(divIndex,divIndex+1).html(result);
157 158 $("#print_file_button").html("Print File ");
158 159 },
159 160 error: function (xhr) {
160 161 $("#print_file_button").html("Print File ");
161 162 alert('Printing error: ' + xhr);
162 163 }
163 164 });
164 165 }
165 166 }
166 167
167 168 $('#show_info').on('click', function (e) {
168 169 var expID = '{{ form.exp_id.label }}';
169 170 var basename = '{{ form.basename.label }}';
170 171 var url = '{% url 'show_info' %}' + '?experiment_list=' + expID + '&file_list=' + basename;
171 172 // first delete all forms that are now out of date
172 173 divIndex = $(".single_form").index($( "#file_data" ))
173 174 $(".single_form").slice(divIndex).empty()
174 175 // second populate the print as is html if '0' not selected
175 176 if (basename != '0') {
176 177 //$(".single_form").slice(divIndex,divIndex+1).load(url);
177 178 $.ajax({url: url,
178 179 success: function(result){
179 180 $(".single_form").slice(divIndex,divIndex+1).html(result);
180 181 },
181 182 error: function (xhr) {
182 183 alert('Printing error: ' + xhr);
183 184 }
184 185 });
185 186 }
186 187 })
187 188
188 189 $('#show_doi').on('click', function (e) {
189 190 var expID = '{{ form.exp_id.label }}';
190 191 var basename = '{{ form.basename.label }}';
191 192 var url = '{% url 'show_doi' %}' + '?experiment_list=' + expID + '&file_list=' + basename;
192 193 // first delete all forms that are now out of date
193 194 divIndex = $(".single_form").index($( "#file_data" ))
194 195 $(".single_form").slice(divIndex).empty()
195 196 // second populate the print as is html if '0' not selected
196 197 if (basename != '0') {
197 198 //$(".single_form").slice(divIndex,divIndex+1).load(url);
198 199 $.ajax({url: url,
199 200 success: function(result){
200 201 $(".single_form").slice(divIndex,divIndex+1).html(result);
201 202 },
202 203 error: function (xhr) {
203 204 alert('Printing error: ' + xhr);
204 205 }
205 206 });
206 207 }
207 208 })
208 209
209 210 </script>
210 211
211 212 </div> <!-- end row -->
212 213
Show file before | Show file after | Hide comments
@@ -1,50 +1,51
1 {% load static %}
1 2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2 3 <html xmlns="http://www.w3.org/1999/xhtml">
3 4 <head>
4 5 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
5 6 <title>Madrigal documentation - v3.0</title>
6 <link href="/madrigal{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
7 <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
7 8 <style type="text/css">
8 9 html body {
9 10 background-color: {{bg_color}};
10 11 }
11 12 </style>
12 13 </head>
13 14
14 15 <body>
15 16 <center>
16 17 <h1>Madrigal Database v3.2.1 Documentation - Contents</h1>
17 18 <table width="100%" border="1">
18 19 <tr>
19 20 <td class="navigation"><a href="/">Home</a></td>
20 21 </tr>
21 22 </table>
22 23 </center>
23 24 <hr size="4" />
24 25 <ul>
25 26 <li><a href="{% url 'docs' 'madIntroduction.html' %}">1. Brief history of Madrigal</a></li>
26 27 </ul>
27 28 <ul>
28 29 <li><a href="{% url 'docs' 'whatsNew.html' %}">2. What's new in Madrigal 3.2.1</a></li>
29 30 </ul>
30 31 <ul>
31 32 <li><a href="{% url 'docs' 'wt_usersGuide.html' %}">3. Madrigal user's guide (How do I access Madrigal data?) </a>
32 33 <ul>
33 34 <li><a href="{% url 'docs' 'wt_contents.html' %}">2.1 Web interface tutorial </a></li>
34 35 <li><a href="{% url 'docs' 'rt_contents.html' %}">2.2 Remote data access programming tutorial</a></li>
35 36 <li><a href="{% url 'docs' 'rr_contents.html' %}">2.3 Remote data access programming reference guide</a></li>
36 37 </ul>
37 38 </li>
38 39 </ul>
39 40 <ul>
40 41 <li><a href="{% url 'docs' 'admin.html' %}">4. Madrigal Administrator's Guide</a></li>
41 42 </ul>
42 43 <ul>
43 44 <li><a href="{% url 'docs' 'dev_contents.html' %}">5. Madrigal Developer's Guide</a></li>
44 45 </ul>
45 46 <ul>
46 47 <li><a href="{{ siteSpecific }}">6. Site specific documentation</a></li>
47 48 </ul>
48 49 <p>&nbsp;</p>
49 50 </body>
50 51 </html>
Show file before | Show file after | Hide comments
@@ -1,71 +1,71
1 1 {% load static %}
2 2
3 3 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
4 4 <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
5 5 <head>
6 6 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
7 7 <!-- InstanceBeginEditable name="doctitle" -->
8 8 <title>Madrigal history</title>
9 9 <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" -->
10 10 <!-- InstanceEndEditable -->
11 <link href="/madrigal{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
11 <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
12 12 <style type="text/css">
13 13 html body {
14 14 background-color: {{bg_color}};
15 15 }
16 16 </style>
17 17 <!-- 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" -->
18 18 </head>
19 19
20 20 <body>
21 21 <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
22 22 <tr>
23 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
24 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
25 <td width="5%"><a href="{% url 'docs' 'whatsNew.html' %}"><img src="/madrigal{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
23 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
24 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
25 <td width="5%"><a href="{% url 'docs' 'whatsNew.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
26 26 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->Brief history of Madrigal <!-- InstanceEndEditable --></td>
27 27 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
28 28 <td width="18%"><a href="/">Madrigal home</a></td>
29 29 </tr>
30 30 </table>
31 31 <div class='online-navigation'>
32 32 <b class="navlabel">Previous:</b>
33 33 <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Doc home <!-- InstanceEndEditable --></A>
34 34 <b class="navlabel">&nbsp;&nbsp;Up:</b>
35 35 <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Doc home <!-- InstanceEndEditable --></A>
36 36 <b class="navlabel">&nbsp;&nbsp;Next:</b>
37 37 <a class="sectref" href="{% url 'docs' 'whatsNew.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->What's new in Madrigal 3.0? <!-- InstanceEndEditable --></A></div>
38 38 <hr/>
39 39 <!-- InstanceBeginEditable name="EditDoc" -->
40 40 <center>
41 41 <h1>Brief history of Madrigal </h1>
42 42 </center>
43 43 <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>
44 44 <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>
45 <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>
45 <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="{% static 'CEDARMadrigalHdf5Format.pdf' %}" target="_blank">here</a>. This format replaced the old <a href="{% 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>
46 46 <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>
47 47 <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>
48 48 <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>
49 49 <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>
50 50 <!-- InstanceEndEditable -->
51 51 <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
52 52 <tr>
53 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
54 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
55 <td width="5%"><a href="{% url 'docs' 'whatsNew.html' %}"><img src="/madrigal{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
53 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
54 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
55 <td width="5%"><a href="{% url 'docs' 'whatsNew.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
56 56 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->Brief overview of Madrigal <!-- InstanceEndEditable --></td>
57 57 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
58 58 <td width="18%"><a href="/">Madrigal home</a></td>
59 59 </tr>
60 60 </table>
61 61 <div class='online-navigation'>
62 62 <b class="navlabel">Previous:</b>
63 63 <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Doc Home <!-- InstanceEndEditable --></A>
64 64 <b class="navlabel">&nbsp;&nbsp;Up:</b>
65 65 <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Doc home <!-- InstanceEndEditable --></A>
66 66 <b class="navlabel">&nbsp;&nbsp;Next:</b>
67 67 <a class="sectref" href="{% url 'docs' 'whatsNew.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->What's new in Madrigal 3.0? <!-- InstanceEndEditable --></A></div>
68 68 <hr/>
69 69 <p>&nbsp;</p>
70 70 </body>
71 71 <!-- InstanceEnd --></html>
Show file before | Show file after | Hide comments
@@ -1,363 +1,363
1 1 {% load static %}
2 2
3 3 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
4 4 <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/doc_template.dwt" codeOutsideHTMLIsLocked="false" -->
5 5 <head>
6 6 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
7 7 <!-- InstanceBeginEditable name="doctitle" -->
8 8 <title>What's new in Madrigal 3.2?</title>
9 9 <!-- InstanceEndEditable --><!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable -->
10 <link href="/madrigal{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
10 <link href="{% static 'madrigal.css' %}" rel="stylesheet" type="text/css" />
11 11 <style type="text/css">
12 12 html body {
13 13 background-color: {{bg_color}};
14 14 }
15 15 </style>
16 16 <!-- InstanceParam name="href_up_top" type="text" value="madContents.html" --><!-- InstanceParam name="href_next_top" type="text" value="wt_usersGuide.html" --><!-- InstanceParam name="href_back_top" type="text" value="madIntroduction.html" --><!-- InstanceParam name="href_back_bottom" type="text" value="madIntroduction.html" --><!-- InstanceParam name="href_up_bottom" type="text" value="madContents.html" --><!-- InstanceParam name="href_next_bottom" type="text" value="wt_usersGuide.html" --><!-- InstanceParam name="href_prev_top" type="text" value="madIntroduction.html" --><!-- InstanceParam name="href_uptitle_top" type="text" value="madContents.html" --><!-- InstanceParam name="href_nexttitle_top" type="text" value="wt_usersGuide.html" --><!-- InstanceParam name="href_prevtitle_bottom" type="text" value="madIntroduction.html" --><!-- InstanceParam name="href_uptitle_bottom" type="text" value="madContents.html" --><!-- InstanceParam name="href_nexttitle_bottom" type="text" value="wt_usersGuide.html" -->
17 17 </head>
18 18
19 19 <body>
20 20 <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
21 21 <tr>
22 <td width="5%"><a href="{% url 'docs' 'madIntroduction.html' %}"><img src="/madrigal{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
23 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
24 <td width="5%"><a href="{% url 'docs' 'wt_usersGuide.html' %}"><img src="/madrigal{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
22 <td width="5%"><a href="{% url 'docs' 'madIntroduction.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
23 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
24 <td width="5%"><a href="{% url 'docs' 'wt_usersGuide.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
25 25 <td width="54%"><!-- InstanceBeginEditable name="EditTitleTop" -->What's new in Madrigal 3.0? <!-- InstanceEndEditable --></td>
26 26 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
27 27 <td width="18%"><a href="/">Madrigal home</a></td>
28 28 </tr>
29 29 </table>
30 30 <div class='online-navigation'>
31 31 <b class="navlabel">Previous:</b>
32 32 <a class="sectref" href="{% url 'docs' 'madIntroduction.html' %}"><!-- InstanceBeginEditable name="PreviousTitle" -->Brief History <!-- InstanceEndEditable --></A>
33 33 <b class="navlabel">&nbsp;&nbsp;Up:</b>
34 34 <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="UpTitle" -->Doc home <!-- InstanceEndEditable --></A>
35 35 <b class="navlabel">&nbsp;&nbsp;Next:</b>
36 36 <a class="sectref" href="{% url 'docs' 'wt_usersGuide.html' %}"><!-- InstanceBeginEditable name="NextTitle" -->Madrigal user's guide <!-- InstanceEndEditable --></A></div>
37 37 <hr/>
38 38 <!-- InstanceBeginEditable name="EditDoc" -->
39 39
40 40 <h1 align="center">What's new in Madrigal 3.2.2?</h1>
41 41 <h1 align="center" style="text-align: left">Madrigal 3.2.2 Release - Jan 2021</h1>
42 42 <p align="center" style="text-align: left">Fixed bug in linking to external data using the Select Single Experiment user interface. </p>
43 43
44 44
45 45 <h1 align="center">What's new in Madrigal 3.2.1?</h1>
46 46 <h1 align="center" style="text-align: left">Madrigal 3.2.1 Release - Nov 2020</h1>
47 47 <h2 align="center" style="text-align: left">Allows Madrigal to create citations to groups of files</h2>
48 48 <p align="center" style="text-align: left">With Madrigal 3.2.1, users can use the API to create citations to groups of files, and can display those groups with that citation. </p>
49 49
50 50
51 51 <h1 align="center">What's new in Madrigal 3.1.1?</h1>
52 52 <h1 align="center" style="text-align: left">Madrigal 3.1.1 Release - Nov 2019</h1>
53 53 <h2 align="center" style="text-align: left">Allows Madrigal to run using https</h2>
54 54 <p align="center" style="text-align: left">With Madrigal 3.1.1, the code is compatable with https. Instructions are given to install or convert Madrigal to https. </p>
55 55
56 56 <h1 align="center">What's new in Madrigal 3.1?</h1>
57 57 <h1 align="center" style="text-align: left">Madrigal 3.1 Release - Oct 2019</h1>
58 58 <h2 align="center" style="text-align: left">Conversion to Python 3</h2>
59 59 <p align="center" style="text-align: left">With Madrigal 3.1, all python code has been updated to use python 3 instead of python 2. The functionality is unchanged from Madrigal 3.0.</p>
60 60
61 61 <h1 align="center" style="text-align: left">Madrigal 3.0 Release - Sept 2017</h1>
62 62 <blockquote>
63 63 <h2 align="center" style="text-align: left">Migration to Hdf5 file format</h2>
64 64 <p align="center" style="text-align: left">With Madrigal 3.0, the old 16 bit integer based file format has been replaced with Hdf5. However, all the data model and well-defined parameters have been retained. The CEDAR Hdf5 format is designed to be completely self-contained. That is, any user with an Hdf5 reader can fully understand all data in the file without any reference to documentation. A full description of the format can be found <a href="{% static 'CEDARMadrigalHdf5Format.pdf' %}">here</a>.</p>
65 65 <h2 align="center" style="text-align: left">Web interface generates scripts to download any amount of data</h2>
66 66 <p align="center" style="text-align: left">With Madrigal 3, you can generate a script command to download a whole series of files with a few click. You can also create a script that will filter those same files and allow you to choose the parameters you want, again with just a few clicks. These scripts can be run with python, Matlab, or IDL.</p>
67 67 <h2 align="center" style="text-align: left">Download files in a new format</h2>
68 68 <p align="center" style="text-align: left">Prior to Madrigal 3, files could be downloaded only as ascii or Hdf5 (or the difficult to understand CEDAR format). Now they can be downloaded as ascii, Hdf5, or netCDF4.</p>
69 69 <h2 align="center" style="text-align: left">Get data with selected/derived parameters and filters in new formats</h2>
70 70 <p align="center" style="text-align: left">Prior to Madrigal 3, data with selected/derived parameters and filters was available
71 71 only as ascii. Now it can be downloaded as ascii, Hdf5, or netCDF4.</p>
72 72 <h2 align="center" style="text-align: left">Independent spatial parameters now built in to data model</h2>
73 73 <p align="center" style="text-align: left">Prior to Madrigal 3.0, there was no way to automatically tell what the independent spatial parameters were in vector data. With Madrigal 3.0, any data with vector data must define its independent spatial parameters, which can be found in the Hdf5 Metadata group. This allows Madrigal to automatically add array layouts of the data, making for easier plotting.</p>
74 74 <h2 align="center" style="text-align: left">All new web interface</h2>
75 75 <p align="center" style="text-align: left">A much simplified web interface based on Django and bootstrap. Developed with much assistance from Jicamarca Observatory and Jose Antonio Sal y Rosas Celi.</p>
76 76 <h2 align="center" style="text-align: left">Simple FTP-like web interface added</h2>
77 77 <p align="center" style="text-align: left">Designed for non-native English speakers. The url follows a very simple pattern that can be easily parsed if the user in unable to understand the Madrigal API's and automatically generated scripts.</p>
78 78 <h2 align="center" style="text-align: left">Create CEDAR Hdf5 files with either Matlab or python</h2>
79 79 <p align="center" style="text-align: left">Prior to Madrigal 3, there was only a python API to easily create Madrigal files. Now both Matlab and python can be used to create CEDAR Hdf5 files.</p>
80 80 <h2 align="center" style="text-align: left">All metadata easily accessible</h2>
81 81 <p align="center" style="text-align: left">The <em>Access metadata</em> menu item on the main navigation menu allows easy access to all Madrigal CEDAR metadata, including Madrigal sites, instruments, parameter definitions, and kind of data codes.</p>
82 82 </blockquote>
83 83 <h1>Madrigal 2.6.3.2 Release - March 22, 2012</h1>
84 84 <p>Added support to file download cgi scripts to allow logging of remote API requests to download files.</p>
85 85 <h1>Madrigal 2.6.3.1 Release - March 13, 2012</h1>
86 86 <p>Added popup javascript window to warn users not to click &quot;Download File&quot; button multiple times.</p>
87 87 <h1>Madrigal 2.6.3 Release - Febuary 27, 2012</h1>
88 88 <p>Small bug fixes in 3 cgi scripts affecting plots: madExperiment.cgi, madDataDisplay, getMadplot.py</p>
89 89 <h1>Madrigal 2.6.2 Release - Febuary 8, 2012</h1>
90 90 <p>Small bug fix involving creating Hdf5 export files in data.py.</p>
91 91 <h1>Madrigal 2.6.1 Release - January 20, 2012</h1>
92 92 <p>Small bug fix involving a memory leak in _Madrec.c and a rare problem creating Hdf5 export files in data.py. </p>
93 93 <h1>Madrigal 2.6 Release - November 2011 </h1>
94 94 <blockquote>
95 95 <h2>New simple local web user interface </h2>
96 96 <p>A new easy to use interface to access local Madrigal data was developed by Jicamarca with support from Millstone Hill staff. This interface in now very robust and has been tested with data from all Madrigal sites.</p>
97 97 <h2>HDF5 file download availablity</h2>
98 98 <p>Users can now download data files as HDF5, in addition to simple column delimited ascii and the more complex <a href="{% static 'cedarFormat.pdf' %}" target="_self">CEDAR formats</a>. This is also the result of a Jicamarca/Millstone Hill collaborations.</p>
99 99 <h2>Users can register interest in experiments or instruments</h2>
100 100 <p>Users can now register interest in experiments or instruments, and get emails whenever that Madrigal experiment or instrument is updated.</p>
101 101 <h2>Administrative improvements - can now add external disks to experiments</h2>
102 102 <p>It is now easy to expand the Madrigal database by <a href="ad_other.html#experiments" target="_self">mounting additional hard disks</a> to make more room for data.</p>
103 103 <h2>New metadata - experiment PI's and analyst</h2>
104 104 <p>Experiments now have direct email links to the experiment PI. These PI's can be updated on an experiment or intrument basis.</p>
105 105 <h2>Global seach now more robust</h2>
106 106 <p>The global search UI now generates scripts so you can run the global search right from your computer using either the <a href="rt_python.html" target="_self">python remote API</a>, the <a href="rt_matlab.html" target="_self">Matlab remote API</a>, or the<a href="rt_idl.html" target="_self"> IDL remote API</a>.</p>
107 107 <p>&nbsp;</p>
108 108 </blockquote>
109 109 <hr />
110 110 <p>&nbsp;</p>
111 111 <h1>Madrigal 2.5.2 Release - May 2009</h1>
112 112 <blockquote>
113 113 <p>A bug fix release - no new features. </p>
114 114 </blockquote>
115 115 <h1>Madrigal 2.5.1 Release - March 2009</h1>
116 116 <blockquote>
117 117 <p>This minor revision to Madrigal 2.5 was needed to support using Madrigal as an archiving database. The experiment metadata was expanded to allow archived experiments. Archived experiments are not shared between Madrigal sites, but are visible as local experiments. </p>
118 118 </blockquote>
119 119 <h1>Madrigal 2.5 Release - February 2009 </h1>
120 120 <blockquote>
121 121 <h2>Simplification of Web User Interface </h2>
122 122 <p>Both the Browse for Individual Madrigal Experiments and the Global Madrigal Database Report web interface have been simplified. Searching for instruments under Browse for Individual Madrigal Experiments is now easier through the use of an instrument category selector.</p>
123 123 <h2>One step file printing available</h2>
124 124 <p>Under Browse for Individual Madrigal Experiments, users can now choose to print an ascii version of any Madrigal file with one click. With this option they can not include any derived parameters or data filters.</p>
125 125 <h2>Installation simplified </h2>
126 126 <p>Autotools is now used to compile all code, significantly reducing the number of parameters in the madrigal.cfg configuration file.</p>
127 127 <h2>64-bit tested </h2>
128 128 <p>Madrigal has now been fully tested as a 64-bit application. It is important that all Madrigal installations switch to 64-bit machines by the year 2037, because 32-bit unix cannot handle dates beyond then.</p>
129 129 <h2>International Reference Ionosphere (IRI) derived parameters now available</h2>
130 130 <p>All parameters calculated by the International Reference Ionosphere (IRI) model can now be selected as derived parameters.</p>
131 131 <h2>Additional automatic sharing of metadata added</h2>
132 132 <p>For administrators: Now when new sites or instruments are added to Madrigal, these metadata files are automatically added to your site. </p>
133 133 <h2>Experiment level security</h2>
134 134 <p>Previously, individual Madrigal files could be made public or private. Now entire experiments can be made public, private, or hidden altogether. See the script <a href="ad_createExp.html#changeExpStatus">changeExpStatus.py</a> for details. </p>
135 135 <h2>Experiment directory naming convention modified </h2>
136 136 <p>Previous to Madrigal 2.5, all Madrigal experiments had to be stored in directory paths in the form:</p>
137 137 <pre>$MADROOT/experiments/YYYY/&lt;3 letter inst mnemonic&gt;/ddMMMyy[letter],
138 138 Example: /opt/madrigal/experiments/1998/mlh/20jan98b.</pre>
139 139 <p>Under this convention, the date of the directory name represented the start date of the experiment, with one letter optionally added. This meant there was a limited number of experiments that could be created for a particular day for a particular experiment. This part of the directory naming convention has been dropped, and now the convention is:</p>
140 140 <pre>$MADROOT/experiments/YYYY/&lt;3 letter inst mnemonic&gt;/*,
141 141 Example: /opt/madrigal/experiments/1998/mlh/mlh_exp_234.
142 142 </pre>
143 143 </blockquote>
144 144
145 145 <hr />
146 146 <h1>Madrigal 2.4 Release - February 2006 </h1>
147 147 <blockquote>
148 148 <h2>Simple web UI added</h2>
149 149 <p>A new web user-interface has been added that allows easy printing and plotting of basic Madrigal data. To make it easy to use, advanced Madrigal features such as derived parameters and filtering of data have been removed.</p>
150 150 <h2>On-demand plot creation</h2>
151 151 <p>Madrigal now allows users to create basic scatter plots and pcolor plots versus range or altitude of any measured or derived parameter in a data set.</p>
152 152 <h2>Logging of user data access</h2>
153 153 <p>Madrigal now <a href="ad_logging.html">logs user's names, emails, and affiliations</a> whenever data files are directly accessed in a file administrators can access. </p>
154 154 <h2>Automatic updating of all geophysical data</h2>
155 155 <p>Madrigal now automatically updates all its internal geophysical files (e.g., Kp, Fof2, Dst, Imf, etc) every time updateMaster is run. </p>
156 156 <h2>Simple-to-use python module to create and edit Madrigal files</h2>
157 157 <p>There is now a <a href="ad_createFiles.html#python">simple-to-use python module</a> to create and edit Madrigal files. </p>
158 158 <h2>New administrative scripts to manage Madrigal experiments</h2>
159 159 <p>Administrators can now add or modify all Madrigal experiments using <a href="ad_createExp.html">simple administrative scripts</a>, instead of trying to edit Madrigal metadata files themselves or use the complex genExp script. </p>
160 160 <h2>Complete documentation rewrite</h2>
161 161 <p>Madrigal documentation has now been completely rewritten and reorganized into three manuals: one for <a href="wt_usersGuide.html">users</a>, one for <a href="admin.html">administrators</a>, and one for <a href="dev_contents.html">developers</a>. </p>
162 162 <h2>Automatic graphics conversion</h2>
163 163 <p>Madrigal will now allow users to select any graphics format they prefer for <a href="ad_createExp.html#auxillary">graphics administrators place in experiments</a>. This feature was contributed by Eiscat. </p>
164 164 <h2>Update of IGRF/MSIS</h2>
165 165 <p>The Madrigal derivation engine is now using the <a href="http://www.ngdc.noaa.gov/IAGA/vmod/igrf.html">IGRF 2010 coefficients</a>, and the <a href="https://omniweb.gsfc.nasa.gov/vitmo/msis_vitmo.html">MSIS 2000 model</a>. </p>
166 166 <h2>Limiting of disk space used for global search files</h2>
167 167 <p>Administrators can now limit the maximum amount of disk space used to store temporary global search files. See the section on editing the madrigal.cfg file in the installation guide. </p>
168 168 </blockquote>
169 169 <p>&nbsp;</p>
170 170 <hr />
171 171 <p>&nbsp;</p>
172 172 <h1>Madrigal 2.3 Release - March 2004</h1>
173 173
174 174 <blockquote>
175 175 <h2>Remote programming access to Madrigal via web services using any platform</h2>
176 176 <p>Madrigal now exposes all the information and capabilities it has as web services, which allows
177 177 easy access to Madrigal from any computer on the internet using any platform (Unix, Windows, Mac, etc).
178 178 Madrigal's web services are basically cgi scripts with simple output that allows easy parsing of the
179 179 information. Any language that supports the HTTP standard can then access any Madrigal site. We have
180 180 written remote API's using python and Matlab, but almost any language could be used. See the section
181 181 on <a href="{% url 'docs' 'rt_contents.html' %}">remote programming access</a> for details of these APIs and the underlying web services.</p>
182 182 <p>Note that this approach of remotely accessing Madrigal data has been always possible before by parsing the
183 183 html output meant to be displayed in a web browser (this general programming method is referred to as "screen
184 184 scraping"). However, not only is this parsing difficult; but the code often breaks when the user interface
185 185 is modified in any way. With web services the returned cgi scripts are designed to be both simple to parse
186 186 and stable.</p>
187 187 <p>The web services are not implemented according to the SOAP or XMLRPC standard since not all scripting
188 188 languages have support for these standards (or for XML parsing). Instead they use the simple approach
189 189 of returning data requested via a query as a delimited text file. These web services are fully
190 190 documented <a href="{% url 'docs' 'rt_webServices.html' %}">here.</a></p>
191 191 <p>Users who want only to write programs to remotely access Madrigal, and not to install a Madrigal server
192 192 themselves, are now able to <a href="http://www.haystack.mit.edu/madrigal/madDownload.html"> download </a>
193 193 the remote python and Matlab API's from the
194 194 <a href="http://www.openmadrigal.org">OpenMadrigal</a> site.</p>
195 195 <h2> Command-line global search</h2>
196 196 <p>As an example of remote programming access to Madrigal via web services, an application
197 197 <a href="rt_python.html#globalIsprint">globalIsprint</a> was written
198 198 using the python remote API that does a global search of data on any Madrigal site that has installed Madrigal version
199 199 2.3. This application is installed as part of Madrigal, and also when the standalone remote python
200 200 API is installed. It has all the filtering ability of the web-based global search.</p>
201 201 <h2>Calculate any derivable Madrigal parameter for any time and point(s) in space</h2>
202 202 <p>By clicking on "Run Models", users can calculate any derived Madrigal parameter (such as magnetic fields,
203 203 or geophysical parameters) for arbitrary times and ranges of position. Note that this capability is also
204 204 available as a web service, and through the remote python and Matlab API's.</p>
205 205 <h2>New derived parameters</h2>
206 206 <ul>
207 207 <li>
208 208 CGM_LAT: <b>Corrected geomagnetic latitude</b> (deg) <br>
209 209 This parameter gives the location of a point in Corrected geomagnetic latitude.
210 210 This method uses code developed by Vladimir Papitashvili. For more information on CGM coordinates
211 211 and this code, click <a href="https://omniweb.gsfc.nasa.gov/vitmo/cgmm_des.html"> here.</a></li>
212 212 <li>
213 213 CGM_LONG: <b>Corrected geomagnetic longitude</b> (deg) <br>
214 214 This parameter gives the location of a point in Corrected geomagnetic longitude.
215 215 This method uses code developed by Vladimir Papitashvili. For more information on CGM coordinates
216 216 and this code, click <a href="https://omniweb.gsfc.nasa.gov/vitmo/cgmm_des.html"> here.</a></li>
217 217 <li>
218 218 TSYG_EQ_XGSM: <b>Tsyganenko field GSM XY plane X point</b> (earth radii) <br>
219 219 This parameter gives the X value in GSM coordinates of where the field line associated
220 220 with a given input point in space and time crosses the GSM XY plane (the magnetic equatorial plane). GSM stands for
221 221 Geocentric Solar Magnetospheric System, and its XY plane is the equatorial plane of
222 222 the earth's magnetic dipole field. The field lines are traced using the
223 223 Tsyganenko
224 224 Magnetospheric model, so external effects on the earth's magnetic field such the solar wind are
225 225 taken into account. This code uses the 2001 Tsyganenko model, which averages solar wind values
226 226 over the past hour, instead of simply using present values.</li>
227 227 <li> TSYG_EQ_YGSM: <b>Tsyganenko field GSM XY plane Y point</b> (earth radii) <br>
228 228 This parameter gives the Y value in GSM coordinates of where the field line associated
229 229 with a given input point in space and time crosses the GSM XY plane (the magnetic equatorial plane). GSM stands for
230 230 Geocentric Solar Magnetospheric System, and its XY plane is the equatorial plane of
231 231 the earth's magnetic dipole field. The field lines are traced using the Tsyganenko
232 232 Magnetospheric model, so external effects on the earth's magnetic field such the solar wind are
233 233 taken into account. This code uses the 2001 Tsyganenko model, which averages solar wind values
234 234 over the past hour, instead of simply using present values.</li>
235 235 <li> TSYG_EQ_XGSM: <b>Tsyganenko field GSE XY plane X point</b> (earth radii) <br>
236 236 This parameter gives the X value in GSE coordinates of where the field line associated
237 237 with a given input point in space and time crosses the GSE XY plane (the equatorial plane). GSE stands for
238 238 Geocentric Solar Ecliptic System, and its XY plane is the equatorial plane of
239 239 the earth's rotation. The field lines are traced using the Tsyganenko
240 240 Magnetospheric model, so external effects on the earth's magnetic field such the solar wind are
241 241 taken into account. This code uses the 2001 Tsyganenko model, which averages solar wind values
242 242 over the past hour, instead of simply using present values.</li>
243 243 <li> TSYG_EQ_YGSM: <b>Tsyganenko field GSE XY plane Y point</b> (earth radii) <br>
244 244 This parameter gives the Y value in GSE coordinates of where the field line associated
245 245 with a given input point in space and time crosses the GSE XY plane (the equatorial plane). GSE stands for
246 246 Geocentric Solar Ecliptic System, and its XY plane is the equatorial plane of
247 247 the earth's rotation. The field lines are traced using the Tsyganenko
248 248 Magnetospheric model, so external effects on the earth's magnetic field such the solar wind are
249 249 taken into account. This code uses the 2001 Tsyganenko model, which averages solar wind values
250 250 over the past hour, instead of simply using present values.</li>
251 251 <li> BHHMMSS and EHHMMSS: <b>Start and end time in HHMMSS</b> (suggested by Mary McCready at SRI)</li>
252 252 </ul>
253 253 <h2>Bug fixes</h2>
254 254 <p>The Madrigal C API now no longer aborts when a Cedar file contains cycle marks (Cedar
255 255 parameter 95) that are not in order. (Reported by Angela Li, SRI)</p>
256 256 <p>A problem launching the global search with the python module os.spawnlp was fixed.
257 257 (Reported by Angela Li, SRI)</p>
258 258 </blockquote>
259 259 <p>&nbsp;</p>
260 260 <hr></hr>
261 261 <h1>
262 262 Madrigal 2.2 Release - Feb 2003</h1>
263 263
264 264
265 265 <blockquote>
266 266 <h2>New derived parameters</h2>
267 267 <ul>
268 268 <li>
269 269 SUNRISE_HOUR - <b>Ionospheric sunrise</b> (hour)<br>
270 270 This parameter gives the hour UT that sunrise occurs at that particular
271 271 point in space that particular day. If that point in space is either in sunlight or in shadow
272 272 the entire UT day, sunrise_hour will be missing. To find out which, display the
273 273 Shadow height (SDWHT) parameter. If shadow height is less that the altitude of the
274 274 point, its in sunlight; if shadow height is greater than the altitude, its in the earth's shadow.</li>
275 275 <li>SUNSET_HOUR - <b>Ionospheric sunset</b> (hour)<br>
276 276 This parameter gives the hour UT that sunset occurs at that particular
277 277 point in space that particular day. If that point in space is either in sunlight or in shadow
278 278 the entire UT day, sunset_hour will be missing. To find out which, display the
279 279 Shadow height (SDWHT) parameter. If shadow height is less that the altitude of the
280 280 point, its in sunlight; if shadow height is greater than the altitude, its in the earth's shadow.</li>
281 281 <li>CONJ_SUNRISE_H - <b>Magnetic conjugate point sunrise</b> (hour)<br>
282 282 This parameter gives the hour UT that sunrise occurs at the magnetic conjugate point of the particular
283 283 point in space that particular day.</li>
284 284 <li>CONJ_SUNSET_H - <b>Magnetic conjugate point sunset</b> (hour)<br>
285 285 This parameter gives the hour UT that sunset occurs at the magnetic conjugate point of the particular
286 286 point in space that particular day.</li>
287 287 <li>SZEN - <b>Solar zenith angle in measurement vol</b> (deg) <br>
288 288 This parameter gives the solar zenith angle in degrees. If 0 degrees, the sun is directly
289 289 overhead. A solar zenith angle of between 90 and 180 degrees does not mean the sun is not
290 290 visible, due to the finite solid angle of the sun and the altitude the point may be above the
291 291 earth's surface.</li>
292 292 <li>SZENC - <b>Conjugate solar zenith angle</b> (deg) <br>
293 293 This parameter gives the solar zenith angle at the magnetic conjugate point in degrees.</li>
294 294 <li>SDWHT - <b>Shadow height</b> (km) <br>
295 295 This parameter gives the height above the earth's surface at which any part of the sun can be seen. It depends only
296 296 on the time, and on the geodetic latitude and longitude. During the day shadow height will be zero. Since the sun is
297 297 larger than the earth, the shadow height is always finite. If shadow height is less that the altitude of a given
298 298 point in space, its in sunlight; if shadow height is greater than the altitude, its in the earth's shadow.</li>
299 299 <li>MAGCONJSDWHT - <b>Magnetic conjugate shadow height</b> (km) <br>
300 300 This parameter gives the height above the earth's surface at the magnetic conjugate point's latitude and longitude at
301 301 which any part of the sun can be seen. </li>
302 302 <li><b>10 Interplanetary Magnetic Field parameters</b><br>
303 303 Includes field strength in GSM or GSE coordinates, solar wind plasma density, speed, and measuring satellite id.
304 304 Click on any parameter to see the definition of the two coordinate systems.</li>
305 305 </ul>
306 306 <h2>Filtering using any parameter</h2>
307 307 <ul>
308 308 <li>There are now also free-form filters at the end
309 309 of the filter section, which allow you to set up filters based on any
310 310 single parameter or on two parameters either added,
311 311 subtracted, multiplied, or divided together. For example, you can now filter on
312 312 Ti, the ratio Ti/dTi, or gdalt-sdwht (which is positive if the point is in sunlight).
313 313 See the tutorial for more details.</li>
314 314 </ul>
315 315 <h2>Better help understanding what each parameter means</h2>
316 316 <ul>
317 317 <li>Complex parameters now have full html descriptions accessible from the isprint page.
318 318 Just click on the parameter name and you'll see the short description. For more complex
319 319 parameters you'll also see a link to a more detailed explanation.</li>
320 320 </ul>
321 321 <h2>Improved data output</h2>
322 322 <ul>
323 323 <li>If you select only 1D parameters, or derived parameters that depend only on other 1D parameters,
324 324 isprint will only print a single line per record, making it easier to read.</li>
325 325 <li>All filters used are printed at the beginning of the report. Trivial filters that don't exclude
326 326 data (such as elevation from 0 to 90 degrees) are ignored.</li>
327 327 </ul>
328 328 <h2>Better consistency with Cedar standard</h2>
329 329 <ul>
330 330 <li>All units are now consistent with the Cedar standard (when displaying Cedar parameters).</li>
331 331 <li>The special Cedar values "missing", "assumed", and "known bad" are differentiated in isprint output,
332 332 and not all lumped together as "missing" as before.</li>
333 333 <li>Unknown parameter codes displayed with a scale factor of 1.0.</li>
334 334 </ul>
335 335 <h2>New derived parameters are simple to add</h2>
336 336 <ul>
337 337 <li>The isprint web page is now based on the madc library, and has been designed to
338 338 make it extremely simple to add new derived parameters. See the
339 339 madc API documentation for details.</li>
340 340 </ul>
341 341 </blockquote>
342 342 <!-- InstanceEndEditable -->
343 343 <table width="100%" border="1" cellpadding="0" cellspacing="2" class="navigation">
344 344 <tr>
345 <td width="5%"><a href="{% url 'docs' 'madIntroduction.html' %}"><img src="/madrigal{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
346 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="/madrigal{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
347 <td width="5%"><a href="{% url 'docs' 'wt_usersGuide.html' %}"><img src="/madrigal{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
345 <td width="5%"><a href="{% url 'docs' 'madIntroduction.html' %}"><img src="{% static 'previous.png' %}" alt="previous" width="32" height="32" /></a></td>
346 <td width="5%"><a href="{% url 'docs' 'madContents.html' %}"><img src="{% static 'up.png' %}" alt="up" width="32" height="32" /></a></td>
347 <td width="5%"><a href="{% url 'docs' 'wt_usersGuide.html' %}"><img src="{% static 'next.png' %}" alt="next" width="32" height="32" /></a></td>
348 348 <td width="54%"><!-- InstanceBeginEditable name="EditTitleBottom" -->What's new in Madrigal 3.0?<!-- InstanceEndEditable --></td>
349 349 <td width="13%"><a href="{% url 'docs' 'madContents.html' %}">Doc home </a></td>
350 350 <td width="18%"><a href="/">Madrigal home</a></td>
351 351 </tr>
352 352 </table>
353 353 <div class='online-navigation'>
354 354 <b class="navlabel">Previous:</b>
355 355 <a class="sectref" href="{% url 'docs' 'madIntroduction.html' %}"><!-- InstanceBeginEditable name="PreviousTitle2" -->Brief History <!-- InstanceEndEditable --></A>
356 356 <b class="navlabel">&nbsp;&nbsp;Up:</b>
357 357 <a class="sectref" href="{% url 'docs' 'madContents.html' %}"><!-- InstanceBeginEditable name="UpTitle2" -->Doc home <!-- InstanceEndEditable --></A>
358 358 <b class="navlabel">&nbsp;&nbsp;Next:</b>
359 359 <a class="sectref" href="{% url 'docs' 'wt_usersGuide.html' %}"><!-- InstanceBeginEditable name="NextTitle2" -->Madrigal user's guide <!-- InstanceEndEditable --></A></div>
360 360 <hr/>
361 361 <p>&nbsp;</p>
362 362 </body>
363 363 <!-- InstanceEnd --></html>
General Comments 0
You need to be logged in to leave comments. Login now