Cloudy SolarSoftware: Difference between revisions

From HelioWiki Home Page
Jump to navigation Jump to search
imported>Elaszlo
No edit summary
imported>Elaszlo
No edit summary
Line 5: Line 5:
|first_author = Laszlo I. Etesi
|first_author = Laszlo I. Etesi
|second_author = Brian R. Dennis
|second_author = Brian R. Dennis
|publish_date = TBD
|publish_date = 2010 July 5
|next_nugget = TBD
|next_nugget = TBD
|previous_nugget = TBD
|previous_nugget = TBD
Line 31: Line 31:
[http://hesperia.gsfc.nasa.gov/~zarro/synop/show_synop.html SHOW_SYNOP] shown in Figure 2 is an IDL graphical user interface (GUI) to search for and retrieve instrument data within a specified time interval using the VSO or other data finding facilities.  
[http://hesperia.gsfc.nasa.gov/~zarro/synop/show_synop.html SHOW_SYNOP] shown in Figure 2 is an IDL graphical user interface (GUI) to search for and retrieve instrument data within a specified time interval using the VSO or other data finding facilities.  


Search results can be directly downloaded into the active SSW IDL environment. To start searching with SHOW_SYNOP, first open the GUI by typing <code>SHOW_SYNOP</code> in your SSW IDL environment command line. The red box highlights the VSO search form with "Start Time" and "End Time" specifying the search interval and "remote sites ->" defining the instrument (TRACE in this example). Click on the "Search" button to query the VSO for data files that will be displayed in the list below the search form shown in the green box.
Search results can be directly downloaded into the active SSW IDL environment. To start searching with SHOW_SYNOP, first open the GUI by typing <code>SHOW_SYNOP</code> in your SSW IDL environment command-line. The red box highlights the VSO search form with "Start Time" and "End Time" specifying the search interval and "remote sites ->" defining the instrument (TRACE in this example). Click on the "Search" button to query the VSO for data files that will be displayed in the list below the search form shown in the green box.


For information on command-line VSO data searching, please click [[#Step_1:_Finding_the_Data_2|here]]
For information on command-line VSO data searching, please click [[#Step_1:_Finding_the_Data_2|here]]
Line 38: Line 38:


=== Step 2: Pre-processing ===
=== Step 2: Pre-processing ===
Typically, instrument data found with the VSO are unprocessed level-0 data. The PrepServer offers remote pre-processing of those data from within SHOW_SYNOP or from the IDL command line before or after downloading. In SHOW_SYNOP, search results are displayed in the list underneath the VSO search form (see Figure 2, green box). There are two different pre-processing behaviors configurable:
Typically, instrument data found with the VSO are unprocessed level-0 data. The PrepServer offers remote pre-processing of those data from within SHOW_SYNOP or from the IDL command-line before or after downloading. In SHOW_SYNOP, search results are displayed in the list underneath the VSO search form (see Figure 2, green box). There are two different pre-processing behaviors configurable:
* By default a click on "Download" retrieves the level-0 data file, stores it on the local hard drive and adds it to a list (Figure 2, blue box). The level-0 data file is pre-processed by selecting it in the blue box and clicking on "Display". This uploads the level-0 data file to the PrepServer where it is pre-processed, and downloads the pre-processed product to the local hard drive.
* By default a click on "Download" retrieves the level-0 data file, stores it on the local hard drive and adds it to a list (Figure 2, blue box). The level-0 data file is pre-processed by selecting it in the blue box and clicking on "Display". This uploads the level-0 data file to the PrepServer where it is pre-processed, and downloads the pre-processed product to the local hard drive.
* In auto-preprocessing mode, which can be activated in the configuration menu (Figure 2, yellow box), SHOW_SYNOP sends the URL of the level-0 data file to the PrepServer and only downloads the pre-processed data.
* In auto-preprocessing mode, which can be activated in the configuration menu (Figure 2, yellow box), SHOW_SYNOP sends the URL of the level-0 data file to the PrepServer and only downloads the pre-processed data.
Line 59: Line 59:
The data are visualized with PLOTMAN, which handles different data types such as light curves, images, spectra, and spectrograms. It provides basic display operations such as zooming, image overlays, solar rotation, etc. To display data with PLOTMAN from within SHOW_SYNOP, simply select a data file (Figure 2, blue box) and click on "Display". If the data file has already been pre-processed, it will be displayed immediately in a PLOTMAN window. Otherwise, it is first sent to the PrepServer for processing. If multiple files have been selected, all are displayed in the same PLOTMAN window.
The data are visualized with PLOTMAN, which handles different data types such as light curves, images, spectra, and spectrograms. It provides basic display operations such as zooming, image overlays, solar rotation, etc. To display data with PLOTMAN from within SHOW_SYNOP, simply select a data file (Figure 2, blue box) and click on "Display". If the data file has already been pre-processed, it will be displayed immediately in a PLOTMAN window. Otherwise, it is first sent to the PrepServer for processing. If multiple files have been selected, all are displayed in the same PLOTMAN window.


Like all other GUIs discussed in this nugget, PLOTMAN can also be called from the command line. An example is shown in the script [[#Step_3:_Visualizing_2|here]].
Like all other GUIs discussed in this nugget, PLOTMAN can also be called from the command-line. An example is shown in the script [[#Step_3:_Visualizing_2|here]].


== IDL Command Line Tools ==
== IDL Command-Line Tools ==


=== Step 1: Finding the Data ===
=== Step 1: Finding the Data ===
The VSO search can be initiated directly from the IDL command line using the procedure [https://team.i4ds.ch/projects/JIDL/wiki/vso_files VSO_FILES]. Two different search strategies are supported:
The VSO search can be initiated directly from the IDL command-line using the procedure [https://team.i4ds.ch/projects/JIDL/wiki/vso_files VSO_FILES]. Two different search strategies are supported:
* An interval search that returns URLs to files containing data for the specified interval.
* An interval search that returns URLs to files containing data for the specified interval.
* A proximity search that returns a URL to the data file that is closest to the specified time.
* A proximity search that returns a URL to the data file that is closest to the specified time.
Line 79: Line 79:


=== Step 2: Pre-processing ===
=== Step 2: Pre-processing ===
VSO_PREP allows for data pre-processing from an IDL command line without the requirement of a local installation of instrument software or calibration data. VSO_PREP takes as a minimum a local file or a URL to a remote file for a parameter. If a URL is provided then the PrepServer will download the data and send them back pre-processed; otherwise they are uploaded to the PrepServer, pre-processed, and downloaded.
VSO_PREP allows for data pre-processing from an IDL command-line without the requirement of a local installation of instrument software or calibration data. VSO_PREP takes as a minimum a local file or a URL to a remote file for a parameter. If a URL is provided then the PrepServer will download the data and send them back pre-processed; otherwise they are uploaded to the PrepServer, pre-processed, and downloaded.


The following instrument data can be pre-processed:
The following instrument data can be pre-processed:
Line 90: Line 90:


=== Step 3: Visualizing ===
=== Step 3: Visualizing ===
PLOTMAN displays level-0 and pre-processed data. It is integrated with VSO_PREP and allows visualizing data returned by VSO_PREP with one command. Data that have not been processed with VSO_PREP can be read into IDL objects and then visualized. This applies to all instrument data listed in the [[#Step_2:_Pre-processing_2|previous section]].
PLOTMAN displays level-0 and pre-processed data. It is integrated with VSO_PREP and allows visualizing data returned by VSO_PREP with one command.


=== Examples ===
=== Examples ===
All the following examples demonstrate steps 1-2-3 on the command line with the tools described above.
* All examples demonstrate steps 1-2-3 on the command-line with the tools described above
* All examples can be copy-pasted into IDL and run from the command-line


==== Example 1 ====
==== Example 1 ====
This example is the same as the one for SHOW_SYNOP (see [[#Step_1:_Finding_the_Data| here]]
<source lang="ittvis_idl">
<code>
; Step 1: Search the VSO and return a URL to the XRT image closest to January 25 2007 06:57
<span style="color:#408080">; Step 1: Search the VSO and return a URL to the XRT image closest to January 25 2007 06:57</span><br/>
; Step 2: Pre-process that data file and create an XRT object (xrt_obj)
<span style="color:#408080">; Step 2: Pre-process that data file, and create an XRT object (xrt)</span><br/>
; Step 3: Display the data file with PLOTMAN using standard coloring '''(see Figure XXX)'''
<span style="color:#408080">; Step 3: Display the data file with PLOTMAN using standard coloring</span><br/>
 
xrt_file= <span style="color:#00C0C0">'''vso_files'''</span>(<span style="color:#FF0000">'25-Jan-2007 06:57'</span>, instr=<span style="color:#FF0000">'xrt'</span>)<br/>
xrt_file = [f]vso_files[/f]('25-Jan-2007 06:57', instr='xrt')
<span style="color:#007F7F">'''vso_prep'''</span>, xrt_file, oprep=xrt<br/>
[p]vso_prep[/p], xrt_file, oprep=xrt_obj
xrt-><span style="color:#007F7F">'''plotman'''</span>, /colors<br/>
xrt_obj->[p]plotman[/p], /colors
</code>
</source>
 
==== Example 2 ====
<source lang="ittvis_idl">
; Step 1: Search the VSO and return URLs to EIT images that have been observed between January 25 2007 06:45 and January 25 20007 07:15
; Step 2: Pre-process one EIT image at the time and...
; Step 3: ...display it with PLOTMAN using standard coloring. All images are displayed in the same PLOTMAN window.
 
eit_files = [f]vso_files[/f]('25-Jan-2007 06:45', '25-Jan-2007 07:15', instr='eit')
FOR i=0, N_ELEMENTS(eit_files)-1 DO BEGIN $
[p]vso_prep[/p], eit_files[i], oprep=eit_obj & $
eit_obj->[p]plotman[/p], /colors, plotman=p & $
ENDFOR
</source>
 
==== Example 3 ====
<source lang="ittvis_idl">
; Step 1: Search the VSO and return a URL to the TRACE data file closest to January 25 2007 07:00
; Step 2: The TRACE data file contains multiple images. Pre-process images one to 5 and create TRACE objects for them (trace_obj).
;        Not specifying an index would result in VSO_PREP opening the selection widget from '''Figure XXX'''.
; Step 3: Display all TRACE images in PLOTMAN using standard coloring '''(see Figure XXX)'''
 
trace_file = [f]vso_files[/f]('25-Jan-2007 07:00', instr='trace')
[p]vso_prep[/p], trace_file, image_no=[1,2,3,4,5], oprep=trace_obj
trace_obj->[p]plotman[/p], /colors
</source>
 
==== Example 4 ====
<source lang="ittvis_idl">
; Step 1: Not required
; Step 2: Use VSO_PREP to reconstruct a RHESSI clean 6-12keV image on the PrepServer
; Step 3: Display RHESSI image with PLOTMAN using standard coloring '''(see Figure XXX)'''
 
[p]vso_prep[/p], instrument='rhessi', im_time_interval=['25-Jan-2007 06:53:44', '25-Jan-2007 06:57:40'], image_alg='clean', im_energy_binning=[6,12], oprep=rhessi_obj
rhessi_obj->[p]plotman[/p], /colors
</source >
 
==== Example 5 ====
<source lang="ittvis_idl">
; Step 1: Search the VSO and return a URL to the EUVI data file closest to January 25 2007 06:57
; Step 2: The EUVI image is pre-processed (incl. rolling) and an EUVI object is created (euvi_obj)
; Step 3: Display the EUVI image in PLOTMAN using standard coloring '''(see Figure XXX)'''
 
euvi_file = [f]vso_files[/f]('25-Jan-2007 06:57', instr='euvi')
[p]vso_prep[/p], euvi_file, /roll, oprep=euvi_obj
euvi_obj->[p]plotman[/p], /colors
</source>


<span style="color:#00007F">'''print'''</span>, urls<br/>
<nowiki>http://sohodata.nascom.nasa.gov//archive/soho/private/data/processed/eit/lz/2007/01/efz20070125.070013</nowiki><br/>
<span style="color:#00C0C0">'''sock_copy'''</span>, urls<br/><br/>
<span style="color:#408080">; This will return URLs to XRT images between January 25 2007 06:00 and January 25 2007 07:00</span><br/>
urls = <span style="color:#00C0C0">'''vso_files'''</span>(<span style="color:#FF0000">'25-Jan-2007 06:00'</span>, <span style="color:#FF0000">'25-Jan-2007 07:00'</span>, instrument=<span style="color:#FF0000">'xrt'</span>)<br/>
<span style="color:#00007F">'''print'''</span>, urls<br/>
<nowiki>http://kurasuta.cfa.harvard.edu/DATA/2007/01/25/H0600/XRT20070125_060117.2.fits</nowiki><br/>
<nowiki>http://kurasuta.cfa.harvard.edu/DATA/2007/01/25/H0600/XRT20070125_060120.2.fits</nowiki><br/>
...<br/>
</code>
<code>
<span style="color:#408080">; This searches the VSO for an EIT file and sends the returned link to the PrepServer for pre-processing</span><br/>
urls = <span style="color:#00C0C0">'''vso_files'''</span>(<span style="color:#FF0000">'25-Jan-2007 06:55'</span>, inst=<span style="color:#FF0000">'eit'</span>)<br/>
<span style="color:#007F7F">'''vso_prep'''</span>, urls, out=<span style="color:#FF0000">'eit.fits'</span><br/>
% VSO_PREP_MAIN: Prepping completed successfully.<br/>
% VSO_PREP_MAIN: Wrote prepped data to - /home/user/eit.fits<br/><br/>
<span style="color:#408080">; This command will reconstruct a RHESSI clean 6-12keV image on the PrepServer</span><br/>
<span style="color:#007F7F">'''vso_prep'''</span>, instrument=<span style="color:#FF0000">'rhessi'</span>, im_time_interval=[<span style="color:#FF0000">'25-Jan-2007 06:53:44'</span>, <span style="color:#FF0000">'25-Jan-2007 06:57:40'</span>], image_alg=<span style="color:#FF0000">'clean'</span>, im_energy_binning=[<span style="color:#7F7F00">6</span>,<span style="color:#7F7F00">12</span>]<br/>
% VSO_PREP_MAIN: Prepping completed successfully.<br/>
% VSO_PREP_MAIN: Wrote prepped data to - /home/user/prepped_temp.fits
</code>
<code>
<span style="color:#408080">; This command pre-processes an XRT image, writes it into an object and displays the XRT image in PLOTMAN (see Figure 3)</span><br/>
<span style="color:#007F7F">'''vso_prep'''</span>, <span style="color:#FF0000">'<nowiki>http://kurasuta.cfa.harvard.edu/DATA/2007/01/25/H0600/XRT20070125_065656.3.fits</nowiki>'</span>, oprep=xrt<br/>
xrt-><span style="color:#007F7F">'''plotman'''</span>, /color<br/><br/>
<span style="color:#408080">; The first command searches the VSO for the TRACE data file (contains multiple images) closest to January 25 06:30. The second command detects the instrument type TRACE and opens a window for image selection (see Figure 4), then pre-processes the specified images. The last command displays all pre-processed images in PLOTMAN (see Figure 5)</span><br/>
urls = <span style="color:#00C0C0">'''vso_files'''</span>(<span style="color:#FF0000">'25-Jan-2007 06:30'</span>, instr=<span style="color:#FF0000">'trace'</span>)<br/>
<span style="color:#007F7F">'''vso_prep'''</span>, urls, oprep=trace<br/>
trace-><span style="color:#007F7F">'''plotman'''</span>, /color<br/><br/>
<span style="color:#408080">; This last example first reconstructs a RHESSI clean 6-12keV image on the PrepServer; then searches the VSO for the EIT data file closest to January 25 2007 6:55 and sends the URL to the PrepServer for pre-processing; and finally opens both images in the same PLOTMAN window (parameter plotman=p) where the RHESSI contours are manually overlaid with the EIT image to create the image in Figure 6.</span><br/>
<span style="color:#007F7F">'''vso_prep'''</span>, instrument=<span style="color:#FF0000">'rhessi'</span>, im_time_interval=[<span style="color:#FF0000">'25-Jan-2007 06:53:44'</span>, <span style="color:#FF0000">'25-Jan-2007 06:57:40'</span>], image_alg=<span style="color:#FF0000">'clean'</span>, im_energy_binning=[<span style="color:#7F7F00">6</span>,<span style="color:#7F7F00">12</span>], oprep=rhessi<br/>
urls = <span style="color:#00C0C0">'''vso_files'''</span>(<span style="color:#FF0000">'25-Jan-2007 06:55'</span>, inst=<span style="color:#FF0000">'eit'</span>)<br/>
<span style="color:#007F7F">'''vso_prep'''</span>, urls, oprep=eit<br/>
rhessi-><span style="color:#007F7F">'''plotman'''</span>, plotman=p<br/>
eit-><span style="color:#007F7F">'''plotman'''</span>, plotman=p<br/>
</code>


== Conclusion ==
== Conclusion ==

Revision as of 02:45, 26 June 2010


Nugget
Number: XXX"XXX" is not a number.
1st Author: Laszlo I. Etesi
2nd Author: Brian R. Dennis
Published: 2010 July 5
Next Nugget: TBD
Previous Nugget: TBD



NOTE

This nugget is unfinished and still undergoing changes.

Introduction

In our project "Extending the Virtual Solar Observatory (VSO)," we have combined features available in Solar Software (SSW) to produce an integrated environment, supporting data location, retrieval, preparation, and analysis. This workflow in shown Figure 1 with examples given below. Our goal is an integrated analysis experience in IDL, easy-to-use but flexible enough to allow more sophisticated procedures such as multi-instrument analysis. To that end, we have made the transition from a locally oriented setting where all the analysis is done on the user’s computer, to an extended analysis environment where IDL has access to services available on on other computers through the Internet. We have implemented a form of Cloud Computing that uses the VSO search and a new data retrieval and pre-processing server (PrepServer) that provides remote execution of instrument-specific data preparation. The raw and pre-processed data can be displayed with our GUI plotting suite, PLOTMAN, which can display different data types and perform basic data operations. Figure 1 shows the entire framework with numbers corresponding to steps 1-2-3 explained below in the text.

Our environment supports data from a growing number of solar instruments that currently includes RHESSI, SOHO/EIT, TRACE, SECCHI/EUVI, HINODE/XRT, and HINODE/EIS.

Minimum Requirements

  • IDL 6.4
  • Sun Java 1.5
  • SolarSoftware (SSW) with GEN package (standard)

SHOW_SYNOP IDL Widget

Step 1: Finding the Data

SHOW_SYNOP shown in Figure 2 is an IDL graphical user interface (GUI) to search for and retrieve instrument data within a specified time interval using the VSO or other data finding facilities.

Search results can be directly downloaded into the active SSW IDL environment. To start searching with SHOW_SYNOP, first open the GUI by typing SHOW_SYNOP in your SSW IDL environment command-line. The red box highlights the VSO search form with "Start Time" and "End Time" specifying the search interval and "remote sites ->" defining the instrument (TRACE in this example). Click on the "Search" button to query the VSO for data files that will be displayed in the list below the search form shown in the green box.

For information on command-line VSO data searching, please click here

Figure 2. This is a screen shot of the SHOW_SYNOP GUI used to find and retrieve specific data sets within a given time interval. The three colored boxes indicate: (red) the VSO search form (start/end time and instrument), (green) the search result list, and (blue) the downloaded level-0 and pre-processed data. The yellow button is to display the configuration menu.

Step 2: Pre-processing

Typically, instrument data found with the VSO are unprocessed level-0 data. The PrepServer offers remote pre-processing of those data from within SHOW_SYNOP or from the IDL command-line before or after downloading. In SHOW_SYNOP, search results are displayed in the list underneath the VSO search form (see Figure 2, green box). There are two different pre-processing behaviors configurable:

  • By default a click on "Download" retrieves the level-0 data file, stores it on the local hard drive and adds it to a list (Figure 2, blue box). The level-0 data file is pre-processed by selecting it in the blue box and clicking on "Display". This uploads the level-0 data file to the PrepServer where it is pre-processed, and downloads the pre-processed product to the local hard drive.
  • In auto-preprocessing mode, which can be activated in the configuration menu (Figure 2, yellow box), SHOW_SYNOP sends the URL of the level-0 data file to the PrepServer and only downloads the pre-processed data.

Please note: SHOW_SYNOP and the PrepServer are dependent on data providers for downloading speed. Be aware that downloading data may take a few minutes, during which SHOW_SYNOP or your SSW IDL session may be unresponsive.


For information on command-line data pre-processing, please click here

Figure 4. When pre-processing a TRACE data file that contains multiple TRACE images, a selection widget will open allowing picking a set of images.

Step 3: Visualizing

The data are visualized with PLOTMAN, which handles different data types such as light curves, images, spectra, and spectrograms. It provides basic display operations such as zooming, image overlays, solar rotation, etc. To display data with PLOTMAN from within SHOW_SYNOP, simply select a data file (Figure 2, blue box) and click on "Display". If the data file has already been pre-processed, it will be displayed immediately in a PLOTMAN window. Otherwise, it is first sent to the PrepServer for processing. If multiple files have been selected, all are displayed in the same PLOTMAN window.

Like all other GUIs discussed in this nugget, PLOTMAN can also be called from the command-line. An example is shown in the script here.

IDL Command-Line Tools

Step 1: Finding the Data

The VSO search can be initiated directly from the IDL command-line using the procedure VSO_FILES. Two different search strategies are supported:

  • An interval search that returns URLs to files containing data for the specified interval.
  • A proximity search that returns a URL to the data file that is closest to the specified time.

Data for the following instruments can be searched:

  • euvi
  • eit
  • xrt
  • eis
  • trace
  • aia

VSO_FILES does not download any data files. Instead, SOCK_COPY or VSO_PREP (see next section) are used.

Step 2: Pre-processing

VSO_PREP allows for data pre-processing from an IDL command-line without the requirement of a local installation of instrument software or calibration data. VSO_PREP takes as a minimum a local file or a URL to a remote file for a parameter. If a URL is provided then the PrepServer will download the data and send them back pre-processed; otherwise they are uploaded to the PrepServer, pre-processed, and downloaded.

The following instrument data can be pre-processed:

  • euvi
  • eit
  • xrt
  • eis
  • trace (single and zipped files)
  • rhessi (image reconstruction)

Step 3: Visualizing

PLOTMAN displays level-0 and pre-processed data. It is integrated with VSO_PREP and allows visualizing data returned by VSO_PREP with one command.

Examples

  • All examples demonstrate steps 1-2-3 on the command-line with the tools described above
  • All examples can be copy-pasted into IDL and run from the command-line

Example 1

; Step 1: Search the VSO and return a URL to the XRT image closest to January 25 2007 06:57
; Step 2: Pre-process that data file and create an XRT object (xrt_obj)
; Step 3: Display the data file with PLOTMAN using standard coloring '''(see Figure XXX)'''

xrt_file = [f]vso_files[/f]('25-Jan-2007 06:57', instr='xrt')
[p]vso_prep[/p], xrt_file, oprep=xrt_obj
xrt_obj->[p]plotman[/p], /colors

Example 2

; Step 1: Search the VSO and return URLs to EIT images that have been observed between January 25 2007 06:45 and January 25 20007 07:15
; Step 2: Pre-process one EIT image at the time and...
; Step 3: ...display it with PLOTMAN using standard coloring. All images are displayed in the same PLOTMAN window.

eit_files = [f]vso_files[/f]('25-Jan-2007 06:45', '25-Jan-2007 07:15', instr='eit')
FOR i=0, N_ELEMENTS(eit_files)-1 DO BEGIN $
 [p]vso_prep[/p], eit_files[i], oprep=eit_obj & $
 eit_obj->[p]plotman[/p], /colors, plotman=p & $
ENDFOR

Example 3

; Step 1: Search the VSO and return a URL to the TRACE data file closest to January 25 2007 07:00
; Step 2: The TRACE data file contains multiple images. Pre-process images one to 5 and create TRACE objects for them (trace_obj).
;         Not specifying an index would result in VSO_PREP opening the selection widget from '''Figure XXX'''.
; Step 3: Display all TRACE images in PLOTMAN using standard coloring '''(see Figure XXX)'''

trace_file = [f]vso_files[/f]('25-Jan-2007 07:00', instr='trace')
[p]vso_prep[/p], trace_file, image_no=[1,2,3,4,5], oprep=trace_obj
trace_obj->[p]plotman[/p], /colors

Example 4

; Step 1: Not required
; Step 2: Use VSO_PREP to reconstruct a RHESSI clean 6-12keV image on the PrepServer
; Step 3: Display RHESSI image with PLOTMAN using standard coloring '''(see Figure XXX)'''

[p]vso_prep[/p], instrument='rhessi', im_time_interval=['25-Jan-2007 06:53:44', '25-Jan-2007 06:57:40'], image_alg='clean', im_energy_binning=[6,12], oprep=rhessi_obj
rhessi_obj->[p]plotman[/p], /colors

Example 5

; Step 1: Search the VSO and return a URL to the EUVI data file closest to January 25 2007 06:57
; Step 2: The EUVI image is pre-processed (incl. rolling) and an EUVI object is created (euvi_obj)
; Step 3: Display the EUVI image in PLOTMAN using standard coloring '''(see Figure XXX)'''

euvi_file = [f]vso_files[/f]('25-Jan-2007 06:57', instr='euvi')
[p]vso_prep[/p], euvi_file, /roll, oprep=euvi_obj
euvi_obj->[p]plotman[/p], /colors


Conclusion

Documentation

Contacts

  • SHOW_SYNOP: Dominic Zarro (dominic dot zarro at nasa dot gov)
  • PrepServer: Laszlo I. Etesi (laszlo dot etesi at nasa dot gov)
  • PLOTMAN: Kim Tolbert (kim dot tolbert at nasa dot gov)