Making Movies


After being a lenghty process for a wihle, most of the movie making process is now automated. The movies are created automatically by batch jobs. A new movie should be ready for the planner to make his activity report when he comes in. However, if for some reason the movies were not made (like if the batch job died, see below), or if they look bad (too many bad images for example), the planner has to remake them manually. There are different ways to do this. You can automatically remake the last movies (intensities and differences) up to the current time with:

IDL> automovie_so_far [,[date=date],[time=time],[wave=wave]]

If no keywords are passed, automovie_so_far will just make the movies fro the beginning of the day to the current time. If present, the time keyword must be a two-elements string array containing the desired start and end times.


Restarting the automovie batch job

First, check if the automovie batch job is running by entering:


which should return something like this:

Batch queue AUTOMOVIE$BATCH, idle, on GAVROC:: Entry

Jobname Username Status
----- ------- -------- ------
901 AUTOMOVIE EIT Holding until 13-DEC-2001 00:25:00

If the batch job is not present, then you can restart it with:

$ subm[it] /queue = automovie$batch user_disk0:[eit.oper]automovie /log = user_disk0:[eit.log]automovie.log

Finally, check that it's back in the batch queue.


Using MovieMaker2

If some movies still don't look good, the planner has to remake them manually. There are several ways to do this. One is to use the movie_maker2 IDL program. At an IDL prompt, type:

IDL> movie_maker2, /rtv

Select the appropriate file name wavelength, time range and binning option and hit Update Listing. Make sure that the file name you entered follows the standard naming scheme. For example, the four CME watch movies for May 31st 2001 would be named:

The "a" movie spanning from 00:00 to 12:00 and the "b" movie from 12:00 to 00:00. When there is only one movie covering the all day, like in telemetry submode 5, ommit the "_a" at the end of the name.

You can now press theSave Movie button. When prompted to select a max value, type in 16000. You can adjust this value iff you don't like the output, A higher value will produce a darker movie, while a lower value will tend to saturate active regions. After the movie is saved, hit the View Movie button th visualize the result. See the movie section of this guide for more ways to make movies.


Telemetry submode

The number of movies made every day depends on the amount of data we get and therefore on the current telemetry submode. To signal the automovie batch jobs on how to make movies, and how many to save per day (i.e. two each intensity and difference movies a day in high-res, and one movie each for half-res), the logical name (environment variable) TELEMETRY_SUBMODE needs manual setting on gavroche:

define /system /exec telemetry_submode <n>

where <n> is 5 or 6 for low or high rate respectively. When EIT runs a high cadence CME watch (i.e. when LASCO's door is closed and EIT gets all the telemetry allocated to EIT/LASCO), the TELEMETRY_SUBMODE logical must be set to 42 so that the automovie batch jobs create 4 movies a day. For reference, the default value is 6 at boot time.


Wavelength selection

When EIT runs the CME watch program at another wavelength than 195, the automovie batch job chooses the correct wavlength images to assemble into movies if the logical name CME_WATCH_WAVE is defined correctly (e.g. 304 instead of 195). If the logical name is not defined, the routine defaults to 195


Web curator: Frédéric Auchère
Responsible NASA official: Joseph B. Gurman, Facility Scientist, Solar Data Analysis Center
+1 301 286-4767
NASA Goddard Space Flight Center
Solar Physics Branch / Code 682

Last revised: Tuesday, April 2, 2002 1:08 PM - F. Auchère