Tutorial - Revision history

Dean Whittaker: /* The graphics */

2008-08-05T11:25:12Z

The graphics

Dean Whittaker: /* Setting Colours and Styles on 1d Plots */

2008-08-05T11:20:03Z

Setting Colours and Styles on 1d Plots

Dean Whittaker at 16:14, 2 April 2008

2008-04-02T16:14:47Z

Dean Whittaker at 16:04, 2 April 2008

2008-04-02T16:04:01Z

Show changes

Dean Whittaker at 15:28, 2 April 2008

2008-04-02T15:28:41Z

Dean Whittaker: /* Some Rebinning */

2008-04-02T14:34:25Z

Some Rebinning

Dean Whittaker at 16:01, 1 April 2008

2008-04-01T16:01:43Z

Dean Whittaker: /* Getting Help */

2008-04-01T15:56:56Z

Getting Help

Dean Whittaker: /* Getting Help */

2008-04-01T15:55:55Z

Getting Help

Dean Whittaker at 14:18, 1 April 2008

2008-04-01T14:18:01Z

@@ Line 28: / Line 28: @@
 The graphics package is a powerful addition to the standard Libisis Core.
 *Lots of manipulation tools specifically for plotting
 *Several different plot types available
 *Flexibility and power through Matlab
 *Name-Tagging keeps control of what data will plot into which figure window.
 ===Objects of Desire===

@@ Line 168: / Line 168: @@
-<pre>>> help [[Pre-Emptive Formatting#Colors|acolor]]
+  >> help [[Pre-Emptive Formatting#Colors|acolor]]
->> help [[Pre-Emptive Formatting#Lines|aline]]
+  >> help [[Pre-Emptive Formatting#Lines|aline]]
->> help [[Pre-Emptive Formatting#Markers|amark]]</pre>
+  >> help [[Pre-Emptive Formatting#Markers|amark]]
@@ Line 279: / Line 279: @@
 All this name-tagging business is much more useful when you’re writing your own ''applications'' so you can keep track of windows, set your own defaults etc. etc.  So it is useful to know. For the rest of this tutorial we wont use it much though, since it becomes tedious to type out every time!
 ==[[Plot Commands#Two Dimensional Plotting|Two Dimensional Plotting]]==

@@ Line 394: / Line 394: @@
-<pre>>> w1 = rebin(w1, [xlo1, dx1, xhi1, dx2, xhi2….])
+  >> w1 =  [[Rebin Functions#Rebin Functions|rebin]](w1, [xlo1, dx1, xhi1, dx2, xhi2….])
->> w2 = regroup(w2, xref)</pre>
+  >> w2 = [[Rebin Functions#Regroup Functions|regroup]](w2, xref)
@@ Line 401: / Line 401: @@
-<pre>>> w3 = rebunch(w3, nbins)</pre>
+  >> w3 =  [[Rebin Functions#Rebunch Functions|rebunch]](w3, nbins)
-Where '''xref''' is a reference dataset with the required binning. Here dataset w1 will be rebinned with bin boundaries between xlo1 and xhi1 width dx1, between xhi1 and xhi2 width dx2. w2 will be rebinned with the same bins as xref and w3 will have nbins grouped together – if it previously had 400 x values and nbins was 4, it will now have 100 x values.
+Where '''xref''' is a reference dataset with the required binning. Here dataset '''w1''' will be rebinned with bin boundaries between ''xlo1'' and ''xhi1'' width ''dx1'', between ''xhi1'' and ''xhi2'' width ''dx2''. '''w2''' will be rebinned with the same bins as ''xref'' and '''w3''' will have nbins grouped together – if it previously had 400 ''x'' values and '''nbins''' was 4, it will now have 100 ''x'' values.
-wd2 is a '''''BIG''''' dataset, so lets rebin it so it’s a little smaller. First lets rebunch it’s y dimension by typing
+'''wd2''' is a '''''BIG''''' dataset, so lets rebin it so it’s a little smaller. First lets rebunch it’s y dimension by typing
-<pre>>> wd2 = rebunch_y(wd2, 2)</pre>
+  >> wd2 = [[Rebin Functions#Rebunch Functions|rebunch_y]] (wd2, 2)
-See how the size of the dataset changes. We’ve halved the size of the y dimension in our wd2. Ok, now to get wd1 and wd3 compatable with each other. First lets work with wd1 and get it down to a size we can easily see the pixels.
+See how the size of the dataset changes. We’ve ''halved'' the size of the y dimension in our '''wd2'''. Ok, now to get '''wd1''' and '''wd3''' compatable with each other. First lets work with '''wd1''' and get it down to a size we can easily see the pixels.
-*Lets start by rebunching by 15 in the y dimension
+*Lets start by rebunching by 15 in the ''y dimension ''
-<pre>>> wd4 = rebunch_y(wd1, 15)
+  >> wd4 = [[Rebin Functions#Rebunch Functions|rebunch_y]](wd1, 15)
->> wd3 = rebunch_y(wd3, 15)</pre>
+  >> wd3 = [[Rebin Functions#Rebunch Functions|rebunch_y]](wd3, 15)
@@ Line 426: / Line 426: @@
-*Now lets rebin the x dimension in wd1, we wanna look at 200 to 800, so we type
+*Now lets rebin the ''x dimension'' in '''wd1''', we wanna look at 200 to 800, so we type
-<pre>>> wd4 = rebin_x(wd4, [200, 800])</pre>
+  >> wd4 = [[Rebin Functions#Rebin Functions|rebin_x]](wd4, [200, 800])
-By omitting the dx part, it is assumed we want to keep the same bin widths.
+By omitting the ''dx'' part, it is assumed we want to keep the same bin widths.
-*Plot wd1 to see what the plot looks like.
+*Plot '''wd1''' to see what the plot looks like.
@@ Line 441: / Line 441: @@
-<pre>>> wd4 = rebin_x(wd4, [200,20,800])</pre>
+  >> wd4 = [[Rebin Functions#Rebin Functions|rebin_x]](wd4, [200,20,800])
@@ Line 447: / Line 447: @@
-To make wd3 match the binning in wd1, we simply type
+To make '''wd3''' match the binning in wd1, we simply type
-<pre>>> wd3 = rebin_x(wd3, wd4)</pre>
+  >> wd3 = [[Rebin Functions#Rebin Functions|rebin_x]](wd3, wd4)
@@ Line 457: / Line 457: @@
 *Plot both datasets at once to have a look.
-*Use the color_slider command and look at where you get the most contrast.
+*Use the [[Other_Commands#Add_a_Color_Slider|color_slider]] command and look at where you get the most contrast.
-You’ll notice you get a good view of wd4 at around the limits 0-180 while wd3 is closer to 0-0.1. That’s a factor of 1800 difference in the upper limit.
+You’ll notice you get a good view of '''wd4''' at around the limits 0-180 while '''wd3''' is closer to 0-0.1. That’s a factor of 1800 difference in the upper limit.
 ==Some [[Binary Operators|Binary Operations]]==
@@ Line 475: / Line 475: @@
-This is an example of the binary operators. You can add, subtract, multiply, divide signal data by numbers. You can also do this with comparable datasets – the errors will be added using error addition methods. So lets have a look at the difference between the datasets by doing
+This is an example of the [[Binary Operators|binary operators]]. You can add, subtract, multiply, divide signal data by numbers. You can also do this with comparable datasets – the errors will be added using error addition methods. So lets have a look at the difference between the datasets by doing
@@ Line 484: / Line 484: @@
-This could be useful in subtracting an estimated background function or comparing a fit to real data. We have 2 slices, data and a fit.
+This could be useful in subtracting an estimated background function or comparing a fit to ''real data''. We have 2 slices, data and a fit.
-'''''Task:'''''
+<font {{task}}>'''''Task:'''''
 *Have a look at the difference between the data slice and the fitted slice.
@@ Line 502: / Line 503: @@
-Now we can take this array away from the signal data.
+Now we can take this ''array'' away from the signal data.

@@ Line 64: / Line 64: @@
-So, we’ve got some data we want to look at using Libisis. You can find this in the [[Media:Tutorial_Files.zip|Tutorial_Files.zip]] folder that you should have downloaded and unzipped, we are going to use HET15870.RAW and HET16538.RAW. There isn’t much data of interest there but it’ll do to demonstrate Libisis on it’s own.
+So, we’ve got some data we want to look at using Libisis. You can find this in the [[Media:Tutorial_Files.zip|Tutorial_Files.zip]] folder that you should have downloaded and unzipped, we are going to use '''HET15870.RAW''' and '''HET16538.RAW'''. There isn’t much data of interest there but it’ll do to demonstrate Libisis on it’s own.
@@ Line 70: / Line 70: @@
-<pre>>> rawfile1=IXTraw_file('c:/Tutorial_Files/HET15870.RAW');</pre>
+  >> rawfile1=[[IXTraw_file]]('c:/Tutorial_Files/HET15870.RAW');
@@ Line 82: / Line 82: @@
-<pre>>> w1=getspectrum(rawfile1,25);</pre>
+  >> w1=[[Input and Output Functions#RAW Files|getspectrum]] (rawfile1,25);
@@ Line 88: / Line 88: @@
-<pre>>> wd1=getspectra(rawfile1,[1:500]);</pre>
+  >> wd1=[[Input and Output Functions#RAW Files|getspectra]] (rawfile1,[1:500]);
@@ Line 94: / Line 94: @@
-<pre>>> ww=getspectrum(rawfile1,[10:34]);</pre>
+  >> ww=[[Input and Output Functions#RAW Files|getspectrum]] (rawfile1,[10:34]);
@@ Line 100: / Line 100: @@
-'''''Task:'''''
+<font {{task}}>'''''Task:'''''
@@ Line 109: / Line 109: @@
 *Put spectrum 233 into the variable w2
 *Put spectra 1-500 into variable wd3
+</font>
 The first thing we want to do is have a quick look at the data to make sure we’ve got the right stuff, we can do this by typing

@@ Line 381: / Line 381: @@
-[[Rebin Functions#Regroup Functions|regroup]] and [[Rebin Functions#Rebin Functions|rebin] effectively do the same thing, they change the bins so that they start at xlo, end at xhi and have a spacing dx inbetween. [[Rebin Functions#Regroup Functions|Regroup]]  just makes sure that the bins are always coincident with original bins, the bin width (dx) will be the '''MINIMUM''' bin width that will be used.
+[[Rebin Functions#Regroup Functions|regroup]] and [[Rebin Functions#Rebin Functions|rebin]] effectively do the same thing, they change the bins so that they start at xlo, end at xhi and have a spacing dx inbetween. [[Rebin Functions#Regroup Functions|Regroup]]  just makes sure that the bins are always coincident with original bins, the bin width (dx) will be the '''MINIMUM''' bin width that will be used.
@@ Line 387: / Line 387: @@
-There are also an extraudinary number of different syntaxes you can use with the [[Rebin Functions|rebin functions]]. This is for various historical reasons. We’ll look at the most powerful syntax only. [[Rebin Functions#Rebin Functions|rebin] and [[Rebin Functions#Regroup Functions|regroup]] take the same syntax. You can do one of two things
+There are also an extraudinary number of different syntaxes you can use with the [[Rebin Functions|rebin functions]]. This is for various historical reasons. We’ll look at the most powerful syntax only. [[Rebin Functions#Rebin Functions|rebin]] and [[Rebin Functions#Regroup Functions|regroup]] take the same syntax. You can do one of two things
@@ Line 440: / Line 440: @@
-Now we can see some individual pixels. Ok, so they’re pretty meaningless for scientists, but it’ll show us how libisis works.
+Now we can see some individual pixels. Ok, so they’re pretty meaningless, but it’ll show us how libisis works.

@@ Line 39: / Line 39: @@
 There are some Libisis objects you’ll find difficult to live without. These are listed below.
 ====[[IXTdataset_1d]]====
 Stores signal and error data against 1 spatial dimension (x). This is analogous to an mgenie spectrum.
 ====[[IXTdataset_2d]]====
 Dataset_2d objects store x,y,signal and error data. An array of [[IXTdataset_1d]] objects can be turned into a single [[IXTdataset_2d]] object if they have the same x values.
 ====[[IXTrunfile]]====
 Much like an array of [[IXTdataset_2d]] objects, except much more information is stored about the instrument, run and experiment. Most things that can be done with an [[IXTdataset_2d]] can be done with an [[IXTrunfile]].
 ====[[IXTdatum]]====
 This is a number and error dataset. Used when [[IXTdataset_1d]] objects are integrated
 ====[[IXTdataset_3d]]====
@@ Line 66: / Line 61: @@
+==[[Input and Output Functions|Reading In Data]]==
 So, we’ve got some data we want to look at using Libisis. You can find this in the [[Media:Tutorial_Files.zip|Tutorial_Files.zip]] folder that you should have downloaded and unzipped, we are going to use HET15870.RAW and HET16538.RAW. There isn’t much data of interest there but it’ll do to demonstrate Libisis on it’s own.
 We read the raw file into an [[IXTraw_file]] object using the command:

← Older revision		Revision as of 15:56, 1 April 2008
Line 665:		Line 665:


−	See the [[User Reference]] and [[User ~~Guide~~]] for more information	+	See the [[User Reference]] and [[User Manual]] for more information

← Older revision		Revision as of 15:55, 1 April 2008
Line 663:		Line 663:

	will give a list of graphics functions.		will give a list of graphics functions.
		+
		+
		+	See the [[User Reference]] and [[User Guide]] for more information

← Older revision		Revision as of 14:18, 1 April 2008
Line 633:		Line 633:
	The same idea works for 2d functions.		The same idea works for 2d functions.

		+
		+	==Using the [[Using_Homer_and_Getting_Started\|Homer GUI]]==
		+
		+	[[Using_Homer_and_Getting_Started\|Homer]] is a big part of getting data into Libisis, here's a quick tutorial about how to use the Homer GUI
		+
		+	{{:Homer GUI}}
		+
		+
		+	===Example Scripts===
		+
		+	Some example scripts are provided used when [[Scripting Homer Functions\|scripting homer functions]].
		+
		+	{{:Example Scripts}}