From: IN%"brain@pele.Colorado.EDU" "David Brain" 7-JUN-1996 23:31:36.66 To: IN%"karen.simmons@miranda.Colorado.EDU" CC: Subj: Look_vector Files Return-path: Received: from miranda (miranda.Colorado.EDU) by pisces.colorado.edu (PMDF V4.2-13 #12962) id <01I5N23CKWNKA3C8J5@pisces.colorado.edu>; Fri, 7 Jun 1996 20:28:43 GMT Received: from pele.colorado.edu by miranda via SMTP (940816.SGI.8.6.9/940406.SGI) for id OAA05629; Fri, 7 Jun 1996 14:29:52 -0700 Received: by pele.colorado.edu (5.65/DEC-Ultrix/4.3) id AA11133; Fri, 7 Jun 1996 14:28:26 -0600 Date: Fri, 07 Jun 1996 14:28:25 -0600 (MDT) From: David Brain Subject: Look_vector Files To: karen.simmons@miranda.Colorado.EDU Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT Karen, Hello. I wrote up a file called 'look_vectors.txt' that I am keeping on surt2/brain/galileo at the moment. It explains what I was doing (ad nauseum) in case I don't finish this weekend. I'm forwarding you a copy, in case someone else ends up finishing for me. I sent one to Martin Taylor already. Not included in the file: The plots are in a file folder on my desk, as is my lab notebook. dave brain look_vectors.txt Text file explaining method used for obtaining "look-vectors" for the EUV instrument aboard Galileo, using the GGGS software package. Also, contains information on what remains to be completed as of June 7. written by David Brain June 7, 1996 ************************************************************************** HOW TO CREATE LOOK VECTOR FILES: I don't understand everything thoroughly yet, but I will try my best to explain everything for whoever needs things explained. I'm assuming you know absolutely nothing about this, which is probably untrue, so bear with me. Look vector files are created using GGGS. Inputs necessary to create the files can be found in a combination of two notebooks at the moment. For the current pass, the notebooks are labelled "J0CD Sequence Notebook" and "J0 ---- MWG observation plots", and can be found on the top shelf in the Northwest corner of the "Galileo room". To create a file, run GGGS, and start a design session (Session menu). The window that pops up will ask for a time to plot. I prefer to enter times using the rim time. Rim times to be entered can be found in the J0CD Sequence Notebook, under the yellow-tabbed divider labeled 'UVS/EUV Commands'. The packet titled: EUV DISKH:[GLLSEQ.JAJ0.J0CD]SEF_960528.strip_J0CDUH has my pencil marks all over it and is the packet you should use. I have marked everything that has been created already, and indicated the name of the file in pencil. Choose a line of data, and find the median rim time associated with that data. Enter this rim time into GGGS. (When reading off of the data-line, it may help you to notice that the 'delta rim time' is given as well.) The session window also asks for a time increment (I choose 60 seconds), and a target body (Jupiter, hello!). Enter these and click on 'Done'. When a plot comes up, give it a title using the 'Plot Objects' Menu. Nomenclature for the file is given in a section below. Then to create the file choose 'EUV Data Scan' from the 'Io Torus' section of the 'Analysis Tools' Menu. An input window/widget will appear. Three values need to be entered, and they are obtained by cross-referencing the rim time you entered with information in the second notebook. On the first page of the second notebook, time intervals are given for a series of activities, each having associated 'activity ID'. Later in the notebook, there are 'Galileo Activity Plan Forms' (it says so in the bottom left-hand corner of the page) with some nice observation plots following each, showing what the UVS is doing during the times associated with the activity. Find the activity ID associated with your rim time (if there is no activity associated with your rim time, take the activity that most recently precedes your rim time. Go to the appropriate Activity Plan Form and look in the Design Detail Section for a line called EUVCMD (EUV Command). In parenthesis next to that line, it will tell you how many sectors there are, scans/sector, and starting angle. Enter the starting angle in the top line of your input window. In the next line, enter the sectors (followed by a comma) and the scans per sector. When you have done this, and pressed return on each input line, hit the 'Done' button. You may not find a line labelled EUVCMD. If this is the case, it means the EUV configuration has not changed from the activity before that, so look on the page. It looks like for this particular pass, all data was taken with Starting Angle = 88, 1 scan/sector, and 24 sectors. After you have hit 'Done' wait a few seconds, and the look_vector file will be displayed in a window on the screen. Save the look vector file using the same nomenclature described for the title of the plot. Then hit 'Done'. Finally, adjust the zoom slider on the main plot window to fit the plot in the screen . You should notice a title, and that the actual sectors are indicated in the plot. Print this plot out, please, and add it to the folder of existing plots that Martin or Karen can get for you. You are done! (except for the fact that you have to make a kazillion of these). NOMENCLATURE FOR PLOTS AND DATA FILES ok...this is mostly easy. In the above process, you associated your median rim time for the integrated observation with a UVS activity id. The name of your file should be very similar to this activity id. For now, all activity id's begin with J0. Then there is a one-letter indication of what is being observed (t for torus, j for Jupiter). Then the instrument being used is indicated (the notebook uses U for UVS...but you should use V, for EUV). Next, the orbit is indicated (G1), then a name of the observation (MANS11, AURA01, MPRO04, etc). Finally, add an underscore and a TWO DIGIT number (01, 12, 36, etc) indicating the cardinality of the look_vector file under this nomenclature (huh?). Basically, add an '_01' if it is the first plot having all the previous characters, add an '_02' if it is the second, and so on. "Now," you ask. "What about this rim time that I have that is not assoiated with any activity ID?" Good question. Basically, when I was doing things, if a rim time didn't fall within a particular activity in the observation plots notebook, I chose the NEXT activity listed. "But this is backwards!" you say. "The starting angle and sectors are based on the activity PRECEDING your rim time!" Yeah...I know...but I started this way, and if things need to be changed we can fix them later. EXTRA STUFF: Also, you may be wondering why I didn't run files and plots for those three really really long time integrations on the first and second page. Well...I didn't get to them yet. We want to break them up into times of an hour or half hour. The two 599 delta rim time integrations should be broken up into 60 delta rim time increments, and be run that way. The 219 rim time itegration hould be broken up into 30 rim time increments and be run separately as well. LOCATION OF EXISTING FILES: Right now, the files I have run are on DISKA:[BRAIN.LOOK_VECTORS.J0CD] WHAT NEEDS TO BE DONE: 1. The three big integrations 2. Everything from page 3, about 6 lines down. Look in my directory of data files, or in my lab notebook on my desk (page 7) to see the name of the last file I ran. **************************************************************************