<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.sternwarte.uni-erlangen.de/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ballhausen</id>
	<title>Remeis-Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.sternwarte.uni-erlangen.de/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ballhausen"/>
	<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php/Special:Contributions/Ballhausen"/>
	<updated>2026-04-09T20:32:32Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.7</generator>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=X2Go_Remote_Desktop&amp;diff=2210</id>
		<title>X2Go Remote Desktop</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=X2Go_Remote_Desktop&amp;diff=2210"/>
		<updated>2021-06-01T14:45:42Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
A remote desktop connection allows you to work with the full desktop, but remotely from home. Currently all desktop computers at Remeis support a remote desktop connection with '''X2Go'''.&lt;br /&gt;
&lt;br /&gt;
=== IMPORTANT NOTE ===&lt;br /&gt;
&lt;br /&gt;
When exiting your session, please make sure to log out in xfce in the same way you would when sitting in front of your machine. Do not just close the x2go window, otherwise the sessions will not terminate properly and use up lots of RAM!&lt;br /&gt;
&lt;br /&gt;
=== Installation ===&lt;br /&gt;
&lt;br /&gt;
All you need to do is to install the X2Go Client on your laptop, available for Linux, Mac, and Windows. This page shows how to do this: [https://wiki.x2go.org/doku.php/doc:installation:x2goclient X2Go Client Download and Installation]&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
Start the X2Go Client an click on &amp;quot;New Session&amp;quot;&lt;br /&gt;
&lt;br /&gt;
In the client software you have to specify the following things:&lt;br /&gt;
* Host:  &amp;lt;desktop-computer&amp;gt;.sternwarte.uni-erlangen.de   (fill in &amp;lt;desktop-computer&amp;gt; with the machine you typically use when working at the observatory)&lt;br /&gt;
* Login: your remeis username&lt;br /&gt;
* Session type: XFCE   &lt;br /&gt;
* if you have ssh-keys installed, you can also check the box with &amp;quot;try auto login&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This could then look like the following (in case of user dauser on host corona):&lt;br /&gt;
&lt;br /&gt;
[[File:x2goclient_session_example.png|800px]]&lt;br /&gt;
&lt;br /&gt;
Save the session, type in the session name into &amp;quot;Session&amp;quot;, click enter and type in your password. This will launch the XFCE environment on the Remeis machine.&lt;br /&gt;
&lt;br /&gt;
[[Category:Working Remotely]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2149</id>
		<title>PhD hat Simon</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2149"/>
		<updated>2021-02-10T23:49:53Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Simon's defense is beginning of March.&lt;br /&gt;
&lt;br /&gt;
Timeline:&lt;br /&gt;
&lt;br /&gt;
Feb 17: All items should be ready&lt;br /&gt;
Feb 18: Next hat meeting for status update and organizational questions&lt;br /&gt;
week of Feb 22: transport to Bamberg/Erlangen and construction of the hat&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please email all pictures to Ralf!&lt;br /&gt;
&lt;br /&gt;
Center piece is going to be a Milkyway disk, hat platform will be 30x30cm, cylinder will be 13cm high.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Biggest problem: How to gather all things to put on the hat.&lt;br /&gt;
Idea: People that commute between Bamberg &amp;amp; Erlangen (or pass Erlangen) can deliver things. (Max, Jakob, Ralf, ...)&lt;br /&gt;
&lt;br /&gt;
'''Work things''':&lt;br /&gt;
* The &amp;quot;Slurm Snail&amp;quot; [Christian, Amy]&lt;br /&gt;
Futurama can or logo, ASCII art snail going once around the hat&lt;br /&gt;
* Photo from Astroplate III conference dinner with Simon, Aakash and David [Steven]&lt;br /&gt;
Send pictures to Ralf&lt;br /&gt;
* HV-stars (maybe one holding a beer??) [Steven, Jakob, Max]&lt;br /&gt;
Hypervelocity skier, maybe on Galactic plane as slope, paper model, holding a Stiegl (http://www.wonko.info/365origami/?p=837&lt;br /&gt;
)&lt;br /&gt;
* &amp;quot;Blue Giants&amp;quot; in Andromeda&lt;br /&gt;
Make hat base the Milkyway and add small galaxies (pictures or cotton balls) outside with blue balls [???]&lt;br /&gt;
* Guided tours and VHS courses, Schuelerakademie [Ralf]&lt;br /&gt;
Make small models of the stations usually visited during the guided tours&lt;br /&gt;
* Observing (and vacation) in Chile [Ralf]&lt;br /&gt;
Use pictures from his whatsapp group&lt;br /&gt;
* violent typing [Ralf]&lt;br /&gt;
Take keys from and old keyboard (Ingo or Philipp probably have some).&lt;br /&gt;
* Search and replace with a stapler [I have maybe a photo Eugenia]&lt;br /&gt;
* Star catalogue query tool [???]&lt;br /&gt;
Use as backup (print out source code)&lt;br /&gt;
* Fucktopus [Melanie]&lt;br /&gt;
Picture&lt;br /&gt;
&lt;br /&gt;
'''Private things''':&lt;br /&gt;
* Spruz label [Jakob, Katya]&lt;br /&gt;
Comic of Simon calculating how much money he spent in Spruz during his PhD time&lt;br /&gt;
* Bierwanderung (A map of a path with breweries? Maybe the &amp;quot;certificate&amp;quot; with stamps?) [Christian, Ralf]&lt;br /&gt;
Metzgerbraeu Wanderweg, statue of an angel, Bierdeckel mit Logos (Papierlogo aufkleben wenn nicht verfuegbar) &lt;br /&gt;
* Whiskey tastings [Ralf]&lt;br /&gt;
* Spicy food, Chili, hot sauce, Korean Instant Noodle [Andrea]&lt;br /&gt;
Chilis auf Faden als Tassle &lt;br /&gt;
* Seminars on Fluid Dynamics [Ralf, Jakob, Ole]&lt;br /&gt;
Ask Markus Poetsch for his talk&lt;br /&gt;
* Chartreuse&lt;br /&gt;
Print logo&lt;br /&gt;
* Beer brewing [Jakob, Max]&lt;br /&gt;
Hopfen&lt;br /&gt;
* Skiing? (Skier paper model, artificial snow)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2147</id>
		<title>PhD hat Simon</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2147"/>
		<updated>2021-02-05T15:29:17Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Simon's defense is beginning of March.&lt;br /&gt;
&lt;br /&gt;
Timeline:&lt;br /&gt;
&lt;br /&gt;
Feb 17: All items should be ready&lt;br /&gt;
Feb 18: Next hat meeting for status update and organizational questions&lt;br /&gt;
week of Feb 22: transport to Bamberg/Erlangen and construction of the hat&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please email all pictures to Ralf!&lt;br /&gt;
&lt;br /&gt;
Center piece is going to be a Milkyway disk, hat platform will be 30x30cm, cylinder will be 13cm high.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Biggest problem: How to gather all things to put on the hat.&lt;br /&gt;
Idea: People that commute between Bamberg &amp;amp; Erlangen (or pass Erlangen) can deliver things. (Max, Jakob, Ralf, ...)&lt;br /&gt;
&lt;br /&gt;
'''Work things''':&lt;br /&gt;
* The &amp;quot;Slurm Snail&amp;quot; [Christian, Amy]&lt;br /&gt;
Futurama can or logo, ASCII art snail going once around the hat&lt;br /&gt;
* Photo from Astroplate III conference dinner with Simon, Aakash and David [Steven]&lt;br /&gt;
Send pictures to Ralf&lt;br /&gt;
* HV-stars (maybe one holding a beer??) [Steven, Jakob, Max]&lt;br /&gt;
Hypervelocity skier, maybe on Galactic plane as slope, paper model, holding a Stiegl &lt;br /&gt;
* &amp;quot;Blue Giants&amp;quot; in Andromeda&lt;br /&gt;
Make hat base the Milkyway and add small galaxies (pictures or cotton balls) outside with blue balls [???]&lt;br /&gt;
* Guided tours and VHS courses, Schuelerakademie [Ralf]&lt;br /&gt;
Make small models of the stations usually visited during the guided tours&lt;br /&gt;
* Observing (and vacation) in Chile [Ralf]&lt;br /&gt;
Use pictures from his whatsapp group&lt;br /&gt;
* violent typing [Ralf]&lt;br /&gt;
Take keys from and old keyboard (Ingo or Philipp probably have some).&lt;br /&gt;
* Search and replace with a stapler [I have maybe a photo Eugenia]&lt;br /&gt;
* Star catalogue query tool [???]&lt;br /&gt;
Use as backup (print out source code)&lt;br /&gt;
&lt;br /&gt;
'''Private things''':&lt;br /&gt;
* Spruz label [Jakob, Katya]&lt;br /&gt;
Comic of Simon calculating how much money he spent in Spruz during his PhD time&lt;br /&gt;
* Bierwanderung (A map of a path with breweries? Maybe the &amp;quot;certificate&amp;quot; with stamps?) [Christian, Ralf]&lt;br /&gt;
Metzgerbraeu Wanderweg, statue of an angel, Bierdeckel mit Logos (Papierlogo aufkleben wenn nicht verfuegbar) &lt;br /&gt;
* Whiskey tastings [Ralf]&lt;br /&gt;
* Spicy food, Chili, hot sauce, Korean Instant Noodle [Andrea]&lt;br /&gt;
Chilis auf Faden als Tassle &lt;br /&gt;
* Seminars on Fluid Dynamics [Ralf, Jakob, Ole]&lt;br /&gt;
Ask Markus Poetsch for his talk&lt;br /&gt;
* Chartreuse&lt;br /&gt;
Print logo&lt;br /&gt;
* Beer brewing [Jakob, Max]&lt;br /&gt;
Hopfen&lt;br /&gt;
* Skiing? (Skier paper model, artificial snow)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2141</id>
		<title>PhD hat Simon</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2141"/>
		<updated>2021-02-01T15:51:20Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Simon's defense is planned in a few weeks.&lt;br /&gt;
&lt;br /&gt;
Biggest problem: How to gather all things to put on the hat.&lt;br /&gt;
Idea: People that commute between Bamberg &amp;amp; Erlangen (or pass Erlangen) can deliver things. (Max, Jakob, Ralf, ...)&lt;br /&gt;
&lt;br /&gt;
'''Work things''':&lt;br /&gt;
* The &amp;quot;Slurm Snail&amp;quot;&lt;br /&gt;
* Photo from Astroplate III conference dinner with Simon, Aakash and David&lt;br /&gt;
* HV-stars (maybe one holding a beer??)&lt;br /&gt;
* Guided tours and VHS courses [Ralf]&lt;br /&gt;
* Observing (and vacation) in Chile [Ralf]&lt;br /&gt;
* violent typing [Ralf]&lt;br /&gt;
&lt;br /&gt;
'''Private things''':&lt;br /&gt;
* Spruz label&lt;br /&gt;
* Bierwanderung (A map of a path with breweries? Maybe the &amp;quot;certificate&amp;quot; with stamps?)&lt;br /&gt;
* Whiskey tastings [Ralf] &lt;br /&gt;
* Seminars on Fluid Dynamics [Ralf]&lt;br /&gt;
&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2140</id>
		<title>PhD hat Simon</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2140"/>
		<updated>2021-01-29T17:44:47Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Simon's defense is planned in a few weeks.&lt;br /&gt;
&lt;br /&gt;
Biggest problem: How to gather all things to put on the hat.&lt;br /&gt;
Idea: People that commute between Bamberg &amp;amp; Erlangen (or pass Erlangen) can deliver things. (Max, Jakob, Ralf, ...)&lt;br /&gt;
&lt;br /&gt;
'''Work things''':&lt;br /&gt;
* The &amp;quot;Slurm Snail&amp;quot;&lt;br /&gt;
* Photo from Astroplate III conference dinner with Simon, Aakash and David&lt;br /&gt;
* HV-stars (maybe one holding a beer??)&lt;br /&gt;
* Guided tours and VHS courses [Ralf]&lt;br /&gt;
* Observing (and vacation) in Chile [Ralf]&lt;br /&gt;
&lt;br /&gt;
'''Private things''':&lt;br /&gt;
* Spruz label&lt;br /&gt;
* Bierwanderung (A map of a path with breweries? Maybe the &amp;quot;certificate&amp;quot; with stamps?)&lt;br /&gt;
* Whiskey tastings [Ralf] &lt;br /&gt;
* Seminars on Fluid Dynamics [Ralf]&lt;br /&gt;
&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2139</id>
		<title>PhD hat Simon</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2139"/>
		<updated>2021-01-29T17:41:55Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Simon's defense is planned in a few weeks.&lt;br /&gt;
&lt;br /&gt;
Biggest problem: How to gather all things to put on the hat.&lt;br /&gt;
Idea: People that commute between Bamberg &amp;amp; Erlangen (or pass Erlangen) can deliver things. (Max, Jakob, Ralf, ...)&lt;br /&gt;
&lt;br /&gt;
'''Work things''':&lt;br /&gt;
* The &amp;quot;Slurm Snail&amp;quot;&lt;br /&gt;
* Photo from Astroplate III conference dinner with Simon, Aakash and David&lt;br /&gt;
* HV-stars (maybe one holding a beer??)&lt;br /&gt;
* Guided tours and VHS courses [Ralf]&lt;br /&gt;
&lt;br /&gt;
'''Private things''':&lt;br /&gt;
* Spruz label&lt;br /&gt;
* Bierwanderung (A map of a path with breweries? Maybe the &amp;quot;certificate&amp;quot; with stamps?)&lt;br /&gt;
* Whiskey tastings [Ralf] &lt;br /&gt;
* Seminars on Fluid Dynamics [Ralf]&lt;br /&gt;
&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2138</id>
		<title>PhD hat Simon</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2138"/>
		<updated>2021-01-29T17:41:14Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Simon's defense is planned in a few weeks.&lt;br /&gt;
&lt;br /&gt;
Biggest problem: How to gather all things to put on the hat.&lt;br /&gt;
Idea: People that commute between Bamberg &amp;amp; Erlangen (or pass Erlangen) can deliver things. (Max, Jakob, Ralf, ...)&lt;br /&gt;
&lt;br /&gt;
'''Work things''':&lt;br /&gt;
* The &amp;quot;Slurm Snail&amp;quot;&lt;br /&gt;
* Photo from Astroplate III conference dinner with Simon, Aakash and David&lt;br /&gt;
* HV-stars (maybe one holding a beer??)&lt;br /&gt;
&lt;br /&gt;
'''Private things''':&lt;br /&gt;
* Spruz label&lt;br /&gt;
* Bierwanderung (A map of a path with breweries? Maybe the &amp;quot;certificate&amp;quot; with stamps?)&lt;br /&gt;
* Whiskey tastings [Ralf] &lt;br /&gt;
* Seminars on Fluid Dynamics [Ralf]&lt;br /&gt;
&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2137</id>
		<title>PhD hat Simon</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=PhD_hat_Simon&amp;diff=2137"/>
		<updated>2021-01-29T17:38:46Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Simon's defense is planned in a few weeks.&lt;br /&gt;
&lt;br /&gt;
Biggest problem: How to gather all things to put on the hat.&lt;br /&gt;
Idea: People that commute between Bamberg &amp;amp; Erlangen (or pass Erlangen) can deliver things. (Max, Jakob, Ralf, ...)&lt;br /&gt;
&lt;br /&gt;
'''Work things''':&lt;br /&gt;
* The &amp;quot;Slurm Snail&amp;quot;&lt;br /&gt;
* Photo from Astroplate III conference dinner with Simon, Aakash and David&lt;br /&gt;
* HV-stars (maybe one holding a beer??)&lt;br /&gt;
&lt;br /&gt;
'''Private things''':&lt;br /&gt;
* Spruz label&lt;br /&gt;
* Bierwanderung (A map of a path with breweries? Maybe the &amp;quot;certificate&amp;quot; with stamps?)&lt;br /&gt;
* Whiskey tastings [Ralf] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Phd_hat_list&amp;diff=2115</id>
		<title>Phd hat list</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Phd_hat_list&amp;diff=2115"/>
		<updated>2020-11-11T15:09:24Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Name&lt;br /&gt;
! submission date&lt;br /&gt;
! defense date&lt;br /&gt;
! responsible person for the hat&lt;br /&gt;
|-&lt;br /&gt;
| Ralf&lt;br /&gt;
| End of 2020&lt;br /&gt;
| &lt;br /&gt;
| Simon&lt;br /&gt;
|-&lt;br /&gt;
| Simon &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| Ralf&lt;br /&gt;
|-&lt;br /&gt;
| Max L.&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| David&lt;br /&gt;
|-&lt;br /&gt;
| David&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| Jonathan&lt;br /&gt;
|-&lt;br /&gt;
| Dominic&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| Andrea&lt;br /&gt;
|-&lt;br /&gt;
| Andrea&lt;br /&gt;
| 2021&lt;br /&gt;
| &lt;br /&gt;
| Dominic&lt;br /&gt;
|-&lt;br /&gt;
| Katya&lt;br /&gt;
| 2021&lt;br /&gt;
|&lt;br /&gt;
| Max L. &lt;br /&gt;
|-&lt;br /&gt;
| Jonathan &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| Ole&lt;br /&gt;
|-&lt;br /&gt;
| Christian K.&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| does not want a hat?&lt;br /&gt;
|-&lt;br /&gt;
| Ole&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| Philipp T.&lt;br /&gt;
|-&lt;br /&gt;
| Philipp T.&lt;br /&gt;
| 2023&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Jakob&lt;br /&gt;
| 2023&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Steven&lt;br /&gt;
| 2023&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Mirjam &lt;br /&gt;
| &lt;br /&gt;
| ? &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Eugenia&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| Ralf&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Skivergnuegen_2020&amp;diff=1928</id>
		<title>Skivergnuegen 2020</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Skivergnuegen_2020&amp;diff=1928"/>
		<updated>2020-01-07T16:49:54Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Remeis Skifahren 2020''' The same procedure as every year ;-) &lt;br /&gt;
Hier werden die wichtigsten organisatorischen Dinge festgehalten. Jeder darf hier gerne editieren; wer keinen Account für das Wiki hat, muss sich bitte an jemanden wenden, der Zugang hat.&lt;br /&gt;
&lt;br /&gt;
[[File:154854 silvretta-montafon-panorama.jpeg|right|700px]]&lt;br /&gt;
&lt;br /&gt;
== Allgemeine Infos ==&lt;br /&gt;
*Wann: 11.01.19 (Sa) bis 18.01.19 (Sa)&lt;br /&gt;
&lt;br /&gt;
*Ferienwohnung(en):&lt;br /&gt;
**Wir kommen wieder unter im [https://www.grandau.at/montafon/zimmer/ferienhaus-enzian Haus Enzian] des [https://www.grandau.at/ Sporthotels Grandau], sowie dem 6-er Apartment [https://www.grandau.at/montafon/zimmer/ferienwohnung-edelweiss-top-1 TOP1] nebenan.&lt;br /&gt;
**Adresse des Sporthotel: Montafonerstraße 274a, 6791 St. Gallenkirch, Österreich. Unsere Unterkünfte liegen im Türkeiweg.&lt;br /&gt;
&lt;br /&gt;
*Skigebiet: Montafon (Vorarlberg)&lt;br /&gt;
**Skigebiet Karte: https://winter.intermaps.com/montafon?lang=de&lt;br /&gt;
**Skipass Preise: https://www.montafon.at/de/Service/Bergbahn-Preise-Tickets/Mehrtageskarte-Winter&lt;br /&gt;
**Wer nicht alle 7 Tage Skifahren möchte: Es gibt Angebote wie z.B. 5 aus 7, mit einem solchen Skipass kann man innerhalb von 7 Tagen an 5 beliebigen Tagen skifahren.&lt;br /&gt;
&lt;br /&gt;
*Skiverleih: [http://www.sportharry.at/ Sport Harry], direkt an der Talstation.&lt;br /&gt;
&lt;br /&gt;
== Unterkunft ==&lt;br /&gt;
=== Aufteilung ===&lt;br /&gt;
Dieses Jahr gibt es neben der Hütte noch zusätzlich das 6-er Appartment (TOP1).&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Zimmer&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Insassen&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | 2-er&lt;br /&gt;
| Andrea, Basti &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | 3-er&lt;br /&gt;
| Ralf, Dominik, Thomas&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | 4-er&lt;br /&gt;
| Nela, Ohle, Eva, Katya&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | 5-er&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Apartment (1x 2er, 1x 4er Zimmer)&lt;br /&gt;
| 2er: Eugenia, Michi, kleiner Johannes; 4er: Johannes Veh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Bettwäsche/Handtücher sind dort vorhanden und müssen nicht mitgenommen werden. Kaffeemaschine, Waffeleisen sind ebenfalls vorhanden.&lt;br /&gt;
Brötchen können wir vorbestellen im Hotel. Dazu müssen wir sie am Vortag vorbestellen und am nächsten Morgen bei der Besitzerin bzw. im Hotel gegen 7:15 Uhr abholen.&lt;br /&gt;
&lt;br /&gt;
== Fahrer ==&lt;br /&gt;
Fahrer können sich hier eintragen und Eckdaten angeben. Diejenige, die mitfahren möchten, sprechen sich mit den Fahrern ab und tragen sich ebenfalls ein. Klärt bitte auch die Gepäcklage, ggf. kann ein anderer Fahrer z.B. Skiausrüstung mitnehmen.&lt;br /&gt;
&lt;br /&gt;
'''Auf der Suche nach einer Mitfahrgelegenheit: '''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Fahrer&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | # Plätze&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Anreise&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Mitfahrer Anreise&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Abreise&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Mitfahrer Abreise&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Skimitnahme&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Kommentar&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Basti&lt;br /&gt;
| 3-4&lt;br /&gt;
| Anreise Auto 1&lt;br /&gt;
| Andrea, Domini'''k''',...&lt;br /&gt;
| Abreise Auto 1&lt;br /&gt;
| Andrea, Dominik&lt;br /&gt;
| Skimitnahme moeglich, dann nur max. 3 Mitfahrer&lt;br /&gt;
| Voll, da voraussichtlich Ski mitgenommen werden&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Nela&lt;br /&gt;
| 3-4&lt;br /&gt;
| München Samstag &lt;br /&gt;
| Ohle, Tobi(?)&lt;br /&gt;
| Samstag München&lt;br /&gt;
| Ohle, Tobi&lt;br /&gt;
| Skimitnahme Auto 2&lt;br /&gt;
| Kommentar Auto 2&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Eva&lt;br /&gt;
| 3&lt;br /&gt;
| Samstag &lt;br /&gt;
| Johannes Veh, Christian H.&lt;br /&gt;
| Samstag &lt;br /&gt;
| Johannes Veh, Steffen&lt;br /&gt;
| Eigene&lt;br /&gt;
| Voll bei Hin und Rückfahrt &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Thomas&lt;br /&gt;
| 2&lt;br /&gt;
| Sa Früh&lt;br /&gt;
| Ole &lt;br /&gt;
| Sa&lt;br /&gt;
| ??&lt;br /&gt;
| Kann mehrere Ski mitnehmen&lt;br /&gt;
| ---&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Ralf&lt;br /&gt;
| 3&lt;br /&gt;
| Samstag&lt;br /&gt;
| Jakob, Katya&lt;br /&gt;
| Samstag&lt;br /&gt;
| Max, Katya&lt;br /&gt;
| Eigene&lt;br /&gt;
| -&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Eugenia&lt;br /&gt;
| 2&lt;br /&gt;
| Fürth Samstag Mittag&lt;br /&gt;
| Michi, kl. Johannes&lt;br /&gt;
| Samstag Früh&lt;br /&gt;
| Michi, kl. Johannes&lt;br /&gt;
| Eigene&lt;br /&gt;
| Leider kein Platz für weitere Mitfahrer&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Schwarzes Brett ==&lt;br /&gt;
&lt;br /&gt;
=== Essen ===&lt;br /&gt;
Hier gibt's den Essensplan, soweit übernommen von den letzten Jahren. Da wir sehr viele Leute sind, sollten wir wieder vorab grob planen, was wir kochen wollen. Wir können einige Dinge in Deutschland besorgen und mitnehmen, es gib aber auch einen nahe gelegen Supermarkt. Generelle Dinge, wie z.B. Gewürze oder Aufstriche für Frühstücksbrötchen könnte man auch mitbringen.&lt;br /&gt;
&lt;br /&gt;
Wer Kochvorschläge oder andere Ideen hat, gerne unten eintragen und kommentieren. Bedenkt, dass die Zubereitung (relativ) einfach sein sollte. Da sich die Liste in den letzten Jahren gut bewaehrt hat, behalten wir sie bei, aber die Reihenfolge/Tage kann man sicher noch hin und her bewegen. Einige (wenige) Sachen müssen wir dann manchmal trotzdem noch beim Spar kaufen, da ja auch der Kühlschrank nur begrenzt Platz hat.&lt;br /&gt;
&lt;br /&gt;
'''Einkaufsliste größtenteils vom letztem Jahr uebernommen!'''&lt;br /&gt;
&lt;br /&gt;
https://docs.google.com/document/d/1zO3t_mv9WZWZc8WNze6kCcR0sw3R922zs0f9wej-4d0/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Alkohol/Party ===&lt;br /&gt;
Wir werden dieses mal sicher wieder feiern und dafür sollten wir auch vorsorgen :)&lt;br /&gt;
Vorschlag: jeder bringt mit, was er/sie gern möchte mit Vermerk im Wiki?!&lt;br /&gt;
&lt;br /&gt;
''* Liste von alkoholischen Getraenken hier '' &lt;br /&gt;
&lt;br /&gt;
=== Spiele ===&lt;br /&gt;
 &lt;br /&gt;
Immer lustig sind gemeinsame Spieleabende. Also, wer im Besitz von Gesellschaftsspielen ist, bringt diese gerne mit! Um eine Übersicht zu bekommen auch bitte hier eintragen:&lt;br /&gt;
&lt;br /&gt;
''* Spiele hier eintragen''&lt;br /&gt;
&lt;br /&gt;
=== Sonstiges ===&lt;br /&gt;
* Audiokabel für Anschluss Laptop - Aux-Anschluss Stereoanlage '''(Michi)'''&lt;br /&gt;
* Musikbox --&amp;gt; Christian Heuser (?)&lt;br /&gt;
&lt;br /&gt;
=== Alternativprogramm ===&lt;br /&gt;
  *  Rodeln (http://www.montafon.at/de/urlaubswelten/echte_naturliebhaber/rodeln)&lt;br /&gt;
  *  Schneeschuhwandern (http://www.montafon.at/schneeschuhwanderungen)&lt;br /&gt;
  *  Therme (http://www.montafon.at/schwimmen), z.B. http://www.aqua-dome.at/de (ca. 130km entfernt!)&lt;br /&gt;
&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Skivergnuegen_2020&amp;diff=1904</id>
		<title>Skivergnuegen 2020</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Skivergnuegen_2020&amp;diff=1904"/>
		<updated>2019-12-19T15:32:14Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Remeis Skifahren 2020''' The same procedure as every year ;-) &lt;br /&gt;
Hier werden die wichtigsten organisatorischen Dinge festgehalten. Jeder darf hier gerne editieren; wer keinen Account für das Wiki hat, muss sich bitte an jemanden wenden, der Zugang hat.&lt;br /&gt;
&lt;br /&gt;
[[File:154854 silvretta-montafon-panorama.jpeg|right|700px]]&lt;br /&gt;
&lt;br /&gt;
== Allgemeine Infos ==&lt;br /&gt;
*Wann: 11.01.19 (Sa) bis 18.01.19 (Sa)&lt;br /&gt;
&lt;br /&gt;
*Ferienwohnung(en):&lt;br /&gt;
**Wir kommen wieder unter im [https://www.grandau.at/montafon/zimmer/ferienhaus-enzian Haus Enzian] des [https://www.grandau.at/ Sporthotels Grandau], sowie dem 6-er Apartment [https://www.grandau.at/montafon/zimmer/ferienwohnung-edelweiss-top-1 TOP1] nebenan.&lt;br /&gt;
**Adresse des Sporthotel: Montafonerstraße 274a, 6791 St. Gallenkirch, Österreich. Unsere Unterkünfte liegen im Türkeiweg.&lt;br /&gt;
&lt;br /&gt;
*Skigebiet: Montafon (Vorarlberg)&lt;br /&gt;
**Skigebiet Karte: https://winter.intermaps.com/montafon?lang=de&lt;br /&gt;
**Skipass Preise: https://www.montafon.at/de/Service/Bergbahn-Preise-Tickets/Mehrtageskarte-Winter&lt;br /&gt;
**Wer nicht alle 7 Tage Skifahren möchte: Es gibt Angebote wie z.B. 5 aus 7, mit einem solchen Skipass kann man innerhalb von 7 Tagen an 5 beliebigen Tagen skifahren.&lt;br /&gt;
&lt;br /&gt;
*Skiverleih: [http://www.sportharry.at/ Sport Harry], direkt an der Talstation. Promotioncode ALPISKI auf alpinresorts.com spart bis zu 35% auf die Preise.&lt;br /&gt;
&lt;br /&gt;
== Unterkunft ==&lt;br /&gt;
=== Aufteilung ===&lt;br /&gt;
Dieses Jahr gibt es neben der Hütte noch zusätzlich das 6-er Appartment (TOP1).&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Zimmer&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Insassen&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | 2-er&lt;br /&gt;
|  &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | 3-er&lt;br /&gt;
| Ralf&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | 4-er&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | 5-er&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Apartment (6)&lt;br /&gt;
| Eugenia, Michi, kleiner Johannes, Johannes Veh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Bettwäsche/Handtücher sind dort vorhanden und müssen nicht mitgenommen werden. Kaffeemaschine, Waffeleisen sind ebenfalls vorhanden.&lt;br /&gt;
Brötchen können wir vorbestellen im Hotel. Dazu müssen wir sie am Vortag vorbestellen und am nächsten Morgen bei der Besitzerin bzw. im Hotel gegen 7:15 Uhr abholen.&lt;br /&gt;
&lt;br /&gt;
== Fahrer ==&lt;br /&gt;
Fahrer können sich hier eintragen und Eckdaten angeben. Diejenige, die mitfahren möchten, sprechen sich mit den Fahrern ab und tragen sich ebenfalls ein. Klärt bitte auch die Gepäcklage, ggf. kann ein anderer Fahrer z.B. Skiausrüstung mitnehmen.&lt;br /&gt;
&lt;br /&gt;
'''Auf der Suche nach einer Mitfahrgelegenheit: '''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Fahrer&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | # Plätze&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Anreise&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Mitfahrer Anreise&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Abreise&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Mitfahrer Abreise&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Skimitnahme&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Kommentar&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Basti&lt;br /&gt;
| 3-4&lt;br /&gt;
| Anreise Auto 1&lt;br /&gt;
| Andrea, ...&lt;br /&gt;
| Abreise Auto 1&lt;br /&gt;
| Mitfahrer Abreise Auto 1&lt;br /&gt;
| Skimitnahme moeglich, dann nur max. 3 Mitfahrer&lt;br /&gt;
| Kommentar Auto 1&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Fahrer Auto 2&lt;br /&gt;
| Plaetze Auto 2&lt;br /&gt;
| Anreise Auto 2&lt;br /&gt;
| Mitfahrer Anreise Auto 1&lt;br /&gt;
| Abreise Auto 2&lt;br /&gt;
| Mitfahrer Abreise Auto 2&lt;br /&gt;
| Skimitnahme Auto 2&lt;br /&gt;
| Kommentar Auto 2&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Fahrer Auto 3&lt;br /&gt;
| Plaetze Auto 3&lt;br /&gt;
| Anreise Auto 3&lt;br /&gt;
| Mitfahrer Anreise Auto 3&lt;br /&gt;
| Abreise Auto 3&lt;br /&gt;
| Mitfahrer Abreise Auto 3&lt;br /&gt;
| Skimitnahme Auto 3&lt;br /&gt;
| Kommentar Auto 3&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Fahrer Auto 4&lt;br /&gt;
| Plaetze Auto 4&lt;br /&gt;
| Anreise Auto 4&lt;br /&gt;
| Mitfahrer Anreise Auto 4&lt;br /&gt;
| Abreise Auto 4&lt;br /&gt;
| Mitfahrer Abreise Auto 4&lt;br /&gt;
| Skimitnahme Auto 4&lt;br /&gt;
| Kommentar Auto 4&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Fahrer Auto 5&lt;br /&gt;
| Plaetze Auto 5&lt;br /&gt;
| Anreise Auto 5&lt;br /&gt;
| Mitfahrer Anreise Auto 5&lt;br /&gt;
| Abreise Auto 5&lt;br /&gt;
| Mitfahrer Abreise Auto 5&lt;br /&gt;
| Skimitnahme Auto 5&lt;br /&gt;
| Kommentar Auto 5&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Schwarzes Brett ==&lt;br /&gt;
&lt;br /&gt;
=== Essen ===&lt;br /&gt;
Hier gibt's den Essensplan, soweit übernommen von den letzten Jahren. Da wir sehr viele Leute sind, sollten wir wieder vorab grob planen, was wir kochen wollen. Wir können einige Dinge in Deutschland besorgen und mitnehmen, es gib aber auch einen nahe gelegen Supermarkt. Generelle Dinge, wie z.B. Gewürze oder Aufstriche für Frühstücksbrötchen könnte man auch mitbringen.&lt;br /&gt;
&lt;br /&gt;
Wer Kochvorschläge oder andere Ideen hat, gerne unten eintragen und kommentieren. Bedenkt, dass die Zubereitung (relativ) einfach sein sollte. Da sich die Liste in den letzten Jahren gut bewaehrt hat, behalten wir sie bei, aber die Reihenfolge/Tage kann man sicher noch hin und her bewegen. Einige (wenige) Sachen müssen wir dann manchmal trotzdem noch beim Spar kaufen, da ja auch der Kühlschrank nur begrenzt Platz hat.&lt;br /&gt;
&lt;br /&gt;
'''Einkaufsliste von letztem Jahr uebernommen, wird noch geupdated!'''&lt;br /&gt;
&lt;br /&gt;
Nachtrag von 2019:&lt;br /&gt;
*es waren 9 Dosen zu viel Bohnen&lt;br /&gt;
&lt;br /&gt;
''VEGANE Optionen für Christian: vegane Sahne, Quark, Leinöl''&lt;br /&gt;
&lt;br /&gt;
*Samstag: Spaghetti Bolognese + veg. Bolognese&lt;br /&gt;
*Sonntag: Käse Spätzle&lt;br /&gt;
*Montag: Burritos &lt;br /&gt;
*Dienstag: Risotto&lt;br /&gt;
*Mittwoch: Gulasch &lt;br /&gt;
*Donnerstag: Kartoffeln mit Kräuter-Quark&lt;br /&gt;
*Freitag: Curry mit Suesskartoffeln (Johannes Vehs Rezept)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Einkaufliste Abendessen ====&lt;br /&gt;
'' Wird von X &amp;amp; Y eingekauft''&lt;br /&gt;
*2.5kg Hackfleisch &lt;br /&gt;
*3.5kg Spaghetti&lt;br /&gt;
*2.5kg Risotto Reis &lt;br /&gt;
*4.0kg Basmati Reis (für Burritos und Curry)&lt;br /&gt;
*12 Dosen gestückelte Tomaten &lt;br /&gt;
*6.0kg Spätzle (vorgekocht aus dem Kühlregal) &lt;br /&gt;
*1 Olivenöl (extra nativ) &lt;br /&gt;
*3kg geriebenen Käse &lt;br /&gt;
*1kg Emmentaler am Stück &lt;br /&gt;
*1kg Parmesan / Grana Padano&lt;br /&gt;
*1 Flaschen Weißwein (2-3€ pro Flasche dürfen es schon sein) &lt;br /&gt;
*2 Flasche Rotwein (2-3€ pro Flasche dürfen es schon sein)&lt;br /&gt;
*2 Knollen Sellerie (od 4 mal Staudensellerie)&lt;br /&gt;
*6kg Karotten&lt;br /&gt;
*3 Netze Zwiebeln &lt;br /&gt;
*2kg Pilze &lt;br /&gt;
*3kg Paprika&lt;br /&gt;
*1.5 kg Zucchini (2-3 Packungen)&lt;br /&gt;
*10kg (große) festkochende Kartoffeln&lt;br /&gt;
*ca. 50 größere Tortillas (2-3 pro Person)&lt;br /&gt;
*12 Dose schwarze Bohnen&lt;br /&gt;
*1-2 Gläser Jalapenos (je nach Größe)&lt;br /&gt;
*2kg Quark (halbfett, 20% sollte genügen)&lt;br /&gt;
*1kg Saure Sahne&lt;br /&gt;
*Tacos-Salsa-Soße für die Burritos (gerne scharf)&lt;br /&gt;
*10 Avocados&lt;br /&gt;
*Knoblauch&lt;br /&gt;
*Salz&lt;br /&gt;
*Pfeffer&lt;br /&gt;
*Rosmarin&lt;br /&gt;
*Basilikum&lt;br /&gt;
*Paprika-Gewürz (scharf)&lt;br /&gt;
*roter Chilli (fürs Gulasch)&lt;br /&gt;
*Zutaten für Curry??? --&amp;gt; Johannes V.&lt;br /&gt;
&lt;br /&gt;
==== Früh und Mittags ====&lt;br /&gt;
'' Wird von X &amp;amp; Y eingekauft''&lt;br /&gt;
*Obst (Bananen, Äpfel, Orangen, Mandarinen) &lt;br /&gt;
*5 Gurken &lt;br /&gt;
*einige Tomaten (für die Brotzeit) &lt;br /&gt;
*5 Butter &lt;br /&gt;
*3kg Wurst &amp;amp; Käseaufschnitt (Auswahl, gerne gute Qualität und von der Theke) &lt;br /&gt;
*Obstriegel &lt;br /&gt;
*Frischkäse (natur und Kräuter)&lt;br /&gt;
*2 Gläser Essiggurken &lt;br /&gt;
*mehr Marmelade (Himbeer und Hagebutte) &lt;br /&gt;
*Nutella &lt;br /&gt;
*kernige Haferflocken (für Porridge)&lt;br /&gt;
*Honig &lt;br /&gt;
*40 Eier (Freilandhaltung!!!)&lt;br /&gt;
*Auswahl an Müsli-Riegel / Snickers&lt;br /&gt;
&lt;br /&gt;
====Allgemeines ====&lt;br /&gt;
'' Wird von X &amp;amp; Y eingekauft''&lt;br /&gt;
*Spülmittel &lt;br /&gt;
*Spülschwamm &lt;br /&gt;
*Seife &lt;br /&gt;
*1 Packung Kaffee (1 Pfund mittelstarker Kaffee)&lt;br /&gt;
*[Tee (Ceylon &amp;amp; Früchtetee) noch vorhanden!] &lt;br /&gt;
*O-Saft &amp;amp; anderer Saft (&amp;gt; 10 Liter)&lt;br /&gt;
*24 Liter Milch &lt;br /&gt;
*2 Liter Sojamilch (Natur)&lt;br /&gt;
*[Kaffeefilter noch vorhanden von letztem Jahr]&lt;br /&gt;
*Zucker&lt;br /&gt;
*[Toilettenpapier schon vorhanden!]&lt;br /&gt;
*Müllsäcke &lt;br /&gt;
*Lappen &lt;br /&gt;
*Spülmaschinen Tabs&lt;br /&gt;
*Schnapsglaeser fuer B52&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Alkohol/Party ===&lt;br /&gt;
Wir werden dieses mal sicher wieder feiern und dafür sollten wir auch vorsorgen :)&lt;br /&gt;
Vorschlag: jeder bringt mit, was er/sie gern möchte mit Vermerk im Wiki?!&lt;br /&gt;
&lt;br /&gt;
''* Liste von alkoholischen Getraenken hier '' &lt;br /&gt;
&lt;br /&gt;
=== Spiele ===&lt;br /&gt;
 &lt;br /&gt;
Immer lustig sind gemeinsame Spieleabende. Also, wer im Besitz von Gesellschaftsspielen ist, bringt diese gerne mit! Um eine Übersicht zu bekommen auch bitte hier eintragen:&lt;br /&gt;
&lt;br /&gt;
''* Spiele hier eintragen''&lt;br /&gt;
&lt;br /&gt;
=== Sonstiges ===&lt;br /&gt;
* Audiokabel für Anschluss Laptop - Aux-Anschluss Stereoanlage '''Bringt das wieder der Michi mit?'''&lt;br /&gt;
* Musikbox --&amp;gt; Christian Heuser (?)&lt;br /&gt;
&lt;br /&gt;
=== Alternativprogramm ===&lt;br /&gt;
  *  Rodeln (http://www.montafon.at/de/urlaubswelten/echte_naturliebhaber/rodeln)&lt;br /&gt;
  *  Schneeschuhwandern (http://www.montafon.at/schneeschuhwanderungen)&lt;br /&gt;
  *  Therme (http://www.montafon.at/schwimmen), z.B. http://www.aqua-dome.at/de (ca. 130km entfernt!)&lt;br /&gt;
&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=GIT_--_The_Fast_Version_Control_System&amp;diff=1875</id>
		<title>GIT -- The Fast Version Control System</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=GIT_--_The_Fast_Version_Control_System&amp;diff=1875"/>
		<updated>2019-06-06T08:53:17Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= What is a GIT Repository? (by Matthias Kühnel) =&lt;br /&gt;
&lt;br /&gt;
''A repository is a container for project files and a program, in this case 'git', handles the different versions of the files and takes care about merging of different file versions. That means many persons can work on the same project (or more precisely on the same files) simultaneously without taking care about the modifications of the other editors. So in principle each editor 'clones' the repository to his or her local computer, does some modifications and at last 'pushes' these changes back into the repository.''&lt;br /&gt;
&lt;br /&gt;
= Clone existing repositories and add changes =&lt;br /&gt;
&lt;br /&gt;
=== Get repository clone ===&lt;br /&gt;
&lt;br /&gt;
==== git clone ====&lt;br /&gt;
&lt;br /&gt;
If you want to use or contribute to a repository, you will first have to get a&lt;br /&gt;
full copy of it (called a &amp;quot;clone&amp;quot;):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
git clone git@serpens.sternwarte.uni-erlangen.de:&amp;lt;group&amp;gt;/&amp;lt;repository&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
where &amp;lt;tt&amp;gt;&amp;lt;group&amp;gt;&amp;lt;/tt&amp;gt; is the group the &amp;lt;tt&amp;gt;&amp;lt;repository&amp;gt;&amp;lt;/tt&amp;gt; belongs to&lt;br /&gt;
&amp;lt;ref&amp;gt;other repositories are distributed in the file system and can be obtained&lt;br /&gt;
via &amp;lt;code&amp;gt;git clone ssh://&amp;lt;user&amp;gt;@crux.sternwarte.uni-erlangen.de:/path/to/repo&lt;br /&gt;
&amp;lt;/code&amp;gt;(always use this over &amp;lt;code&amp;gt;file://...&amp;lt;/code&amp;gt; !)&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Add changes to the repository ===&lt;br /&gt;
&lt;br /&gt;
Before changing anything in the new clone it is good practice&amp;lt;ref&amp;gt;it might be&lt;br /&gt;
necessary if the repo is located under gitlab&amp;lt;/ref&amp;gt; to work on a new branch.&lt;br /&gt;
&lt;br /&gt;
==== git checkout ====&lt;br /&gt;
&lt;br /&gt;
To create a new branch and change to it, use:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
git checkout -b &amp;lt;branch-name&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Choose a representative branch name for the feature you want to add or change!&lt;br /&gt;
&lt;br /&gt;
==== git add / git commit====&lt;br /&gt;
&lt;br /&gt;
In this fresh and new branch you can freely change anything you like. Keep your&lt;br /&gt;
changes logically together and add/commit every time you start working on a new&lt;br /&gt;
feature.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
git add &amp;lt;filename1&amp;gt; &amp;lt;filename2&amp;gt; ...&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
adds all named files to the staging area. &amp;lt;code&amp;gt;git status&amp;lt;/code&amp;gt; might prove&lt;br /&gt;
useful as it will list all untracked changes.&lt;br /&gt;
&lt;br /&gt;
When you have staged all necessary files, use&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
git commit&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
to apply your changes locally. (This will ask you for a commit message. See&lt;br /&gt;
[[GIT -- The Fast Version Control System#Good commit practice|here]] for examples on how to explain what you did).&lt;br /&gt;
&lt;br /&gt;
==== git push ====&lt;br /&gt;
&lt;br /&gt;
With&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
git push origin &amp;lt;branch-name&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
your changes will be added to the global repository (in the new branch).&lt;br /&gt;
If the repository is located under gitlab and you want to provide your code&lt;br /&gt;
for everyone it is probably necessary to send a merge request. (See&lt;br /&gt;
[[GIT -- The Fast Version Control System#Merge request|here]] for more details)&amp;lt;ref&amp;gt;In smaller projects it might&lt;br /&gt;
be sufficient to directly push to the master branch&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==== git merge ====&lt;br /&gt;
&lt;br /&gt;
To combine (merge) the branch ''feature'' with branch ''master'' of the&lt;br /&gt;
same repository it is sufficient to call&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
git fetch origin&lt;br /&gt;
git checkout master&lt;br /&gt;
git merge feature&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and probably also&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
git branch -d feature&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
to delete the branch in your local repository and/or&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
git push origin :feature&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
to delete the ''feature'' branch on the remote repository&lt;br /&gt;
&lt;br /&gt;
= Create your own repository =&lt;br /&gt;
&lt;br /&gt;
The most easy way to create a new repository (empty or from existing code)&lt;br /&gt;
is to use the [http://www.sternwarte.uni-erlangen.de/gitlab gitlab] interface.&lt;br /&gt;
Here you will also find first steps you want to do before start working.&lt;br /&gt;
&lt;br /&gt;
However, if you do not want to use gitlab you can call&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
git init --bare --shared&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
in an empty folder. This, obviously empty, repository can then get pulled with&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
git ssh://&amp;lt;user&amp;gt;@curx.sternwarte.uni-erlangen.de:/path/to/folder&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and following the steps to&lt;br /&gt;
[[GIT -- The Fast Version Control System#Clone existing repositories and add changes|clone a repository]] and add&lt;br /&gt;
files.&lt;br /&gt;
&lt;br /&gt;
==== Gitignore ====&lt;br /&gt;
&lt;br /&gt;
For many projects (especially latex) it is very convenient to prevent you and&lt;br /&gt;
others from adding temporary or unnecessary files. This can be done by creating&lt;br /&gt;
a file called &amp;lt;code&amp;gt;.gitignore&amp;lt;/code&amp;gt; in the root of the directory.&lt;br /&gt;
&lt;br /&gt;
Example contents of &amp;lt;code&amp;gt;.gitignore&amp;lt;/code&amp;gt; for a latex project:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#&lt;br /&gt;
# git ignore file for TeX files&lt;br /&gt;
#&lt;br /&gt;
*~&lt;br /&gt;
*.aux&lt;br /&gt;
*.log&lt;br /&gt;
*.bbl&lt;br /&gt;
*.blg&lt;br /&gt;
*.bak&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this example no file ending in &amp;lt;code&amp;gt;~, .aux, .log, .bbl, .blg,&amp;lt;/code&amp;gt; or&lt;br /&gt;
&amp;lt;code&amp;gt;.bak&amp;lt;/code&amp;gt; can get pushed to the repository.&lt;br /&gt;
Be aware that &amp;lt;code&amp;gt;.gitignore&amp;lt;/code&amp;gt; only prevents files from getting pushed.&lt;br /&gt;
It does not affect files that are already part of the repository. So every file&lt;br /&gt;
that is added before the &amp;lt;code&amp;gt;.gitignore&amp;lt;/code&amp;gt; was added must be explicitly&lt;br /&gt;
removed with &amp;lt;code&amp;gt;git rm &amp;lt;filename1&amp;gt; &amp;lt;filename2&amp;gt; ...&amp;lt;/code&amp;gt; (also &amp;lt;code&amp;gt;git&lt;br /&gt;
push origin master&amp;lt;/code&amp;gt; to apply it to the remote repository).&lt;br /&gt;
&lt;br /&gt;
= Configure git =&lt;br /&gt;
&lt;br /&gt;
Every time you commit changes to a repository your message is appended with&lt;br /&gt;
your name and mail address. If you have not specified a name and/or a mail&lt;br /&gt;
address you can do this (globally) with&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
git config --global user.name &amp;quot;John Doe&amp;quot;&lt;br /&gt;
git config --global user.email johndoe@example.com&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will also overwrite existing entries, in case your mail address has&lt;br /&gt;
changed.&lt;br /&gt;
&lt;br /&gt;
= Gitlab =&lt;br /&gt;
&lt;br /&gt;
The gitlab interface provides a powerful overview of all projects you are&lt;br /&gt;
involved in. Also it gives you hints about what you should do with a fresh&lt;br /&gt;
repository.&lt;br /&gt;
&lt;br /&gt;
To create a new repository you first have to log in at &lt;br /&gt;
[http://www.sternwarte.uni-erlangen.de/gitlab www.sternwarte.uni-erlangen.de/gitlab]&lt;br /&gt;
&lt;br /&gt;
For creating the new repository just click on the &amp;quot;new project&amp;quot; button.&lt;br /&gt;
Following the steps you will end up with a fresh repository.&lt;br /&gt;
&lt;br /&gt;
=== Good commit practice ===&lt;br /&gt;
&lt;br /&gt;
When you contribute to a repository there are a few rules for best practice&lt;br /&gt;
which make life much more easier:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;&lt;br /&gt;
  every time you work on a new (or old) feature&lt;br /&gt;
  do your changes in a new branch with a meaningful name.&lt;br /&gt;
  &amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;&lt;br /&gt;
  commit frequently and each time for separate changes/features that are not related to&lt;br /&gt;
  each other&lt;br /&gt;
  &amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;&lt;br /&gt;
  commit messages should start with a &amp;lt;50 character summary in&lt;br /&gt;
  ''imperative mode''. This is a headline! Capitalize the first word and no periods. &lt;br /&gt;
  A more complete description of what you did, where, and how, may follow&lt;br /&gt;
  '''after''' a blank line.&lt;br /&gt;
  Example commit message:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Add awesome_feature&lt;br /&gt;
  &lt;br /&gt;
This adds the awesome feature to foo by using the functionality&lt;br /&gt;
bar. foo may now be unstable when used with out of range values.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
Although this message is very generic here, notice the ~80 character&lt;br /&gt;
line break for better appearance.&lt;br /&gt;
  &lt;br /&gt;
In general try to complete the following sentence with your summary:&lt;br /&gt;
&amp;quot;With this commit you &amp;lt;insert summary here&amp;gt;&amp;quot;&lt;br /&gt;
  &lt;br /&gt;
In the description explain why you did something, how did you accomplish it&lt;br /&gt;
and what are the consequences.&lt;br /&gt;
  &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
Further information about good commit practice can be found on &lt;br /&gt;
[https://chris.beams.io/posts/git-commit/ this web page].&lt;br /&gt;
&lt;br /&gt;
=== Merge request ===&lt;br /&gt;
&lt;br /&gt;
When you work on a repository located on gitlab, it might be necessary to fill&lt;br /&gt;
a merge request. A merge request informs the maintainers of the repository that&lt;br /&gt;
a new feature is available and ready for publication.&lt;br /&gt;
&lt;br /&gt;
The easiest way to send a merge request is to follow the link that is given in your&lt;br /&gt;
command line when you've pushed your branch.&lt;br /&gt;
&lt;br /&gt;
On this page just select one maintainer to send the request to and check the mark for&lt;br /&gt;
&amp;quot;delete branch after merge&amp;quot;. You are not forced to delete your branch, but it is very&lt;br /&gt;
good practice. Under normal conditions when you will work any further on the same feature&lt;br /&gt;
(e.g., bug fixing) just checkout a new branch instead of keeping old ones. This will just&lt;br /&gt;
lead to an unnecessary amount of dead branches. &lt;br /&gt;
&lt;br /&gt;
= Useful git commands =&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| git log || list log overview&lt;br /&gt;
|-&lt;br /&gt;
| git log --stat || list commits with stats&lt;br /&gt;
|-&lt;br /&gt;
| git log --oneline || display only first line of commit messages&lt;br /&gt;
|-&lt;br /&gt;
| git branch || list local branches&lt;br /&gt;
|-&lt;br /&gt;
| git branch -v || list local branches with more information&lt;br /&gt;
|-&lt;br /&gt;
| git branch -d &amp;lt;branch-name&amp;gt; || delete branch &amp;lt;branch-name&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| git branch &amp;lt;branch-name&amp;gt; || add branch &amp;lt;branch-name&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| git remote || list repository urls&lt;br /&gt;
|-&lt;br /&gt;
| git remote rename &amp;lt;old&amp;gt; &amp;lt;new&amp;gt; || rename &amp;lt;old&amp;gt; url to &amp;lt;new&amp;gt; url&lt;br /&gt;
|-&lt;br /&gt;
| git remote add &amp;lt;url-name&amp;gt; &amp;lt;address&amp;gt; || add new remote address under &amp;lt;url-name&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| git push &amp;lt;url-name&amp;gt; &amp;lt;branch-name&amp;gt; || push &amp;lt;branch-name&amp;gt; to &amp;lt;url-name&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| git push &amp;lt;url-name&amp;gt; :&amp;lt;branch-name&amp;gt; || delete &amp;lt;branch-name&amp;gt; from remote &amp;lt;url-name&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| git status || list untracked files/changes&lt;br /&gt;
|-&lt;br /&gt;
| git add &amp;lt;filename&amp;gt; || add &amp;lt;filename&amp;gt; to staging&lt;br /&gt;
|-&lt;br /&gt;
| git commit || commit staged changes&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- add many more here --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
More information about the different tools of git can be found in the man page&lt;br /&gt;
&amp;lt;code&amp;gt;git &amp;lt;tool&amp;gt; --help&amp;lt;/code&amp;gt; or [https://git-scm.com/docs here].&lt;br /&gt;
&lt;br /&gt;
= git and latexdiff =&lt;br /&gt;
Find the version you want to compare your current document with via&lt;br /&gt;
&amp;lt;pre&amp;gt; git log &amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
produce a pdf showing the differences between the two files via&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
latexdiff-vc --git --flatten -r long_weird_number_of_the_older_commit --pdf --disable-citation-markup file.tex&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
No need to checkout the older version! See latexdiff documentation for further options.&lt;br /&gt;
&lt;br /&gt;
= Notes =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- = Existing Repositories: How to clone and commit changes =&lt;br /&gt;
&lt;br /&gt;
''The following text is copied from an e-mail from Joern concerning the software scripts of the Remeis observatory. More information one these scripts can be found at [[Software at the Remeis-Observatory]].''&lt;br /&gt;
&lt;br /&gt;
== Get the files ==&lt;br /&gt;
&lt;br /&gt;
If you want to modify scripts, you will first have to get a full copy&lt;br /&gt;
of the repository (called a &amp;quot;clone&amp;quot;):&lt;br /&gt;
&lt;br /&gt;
  git clone ssh://account@crux.sternwarte.uni-erlangen.de/data/git/aitlib&lt;br /&gt;
&lt;br /&gt;
(same for intscripts, xmmscripts, xtescripts, xspecscripts,&lt;br /&gt;
isisscripts, cyclo, fpipe) where account is your account at the&lt;br /&gt;
Sternwarte. &lt;br /&gt;
&lt;br /&gt;
Please use the above command EVEN IF YOU ARE WORKING locally in&lt;br /&gt;
Bamberg/Erlangen. Do NOT do a clone with the file://-syntax of git to&lt;br /&gt;
allow you to work on several machines (since the git push command will&lt;br /&gt;
not work properly). Just forget that file://... is an allowed git URL.&lt;br /&gt;
&lt;br /&gt;
== Committing your changes ==&lt;br /&gt;
&lt;br /&gt;
After doing the clone, edit the scripts and check them. In case you edit the isisscripts: Do not forget to &amp;lt;code&amp;gt;make&amp;lt;/code&amp;gt; the isisscripts, i.e. compile your changes into the overall &amp;lt;code&amp;gt;isisscripts.sl&amp;lt;/code&amp;gt; by typing&lt;br /&gt;
  make&lt;br /&gt;
in the &amp;lt;code&amp;gt;isisscripts/&amp;lt;/code&amp;gt; directory.  &lt;br /&gt;
You should usually do your changes in smallish steps, i.e., applying a few changes,&lt;br /&gt;
checking them, and then committing them to the repository as follows: &lt;br /&gt;
&lt;br /&gt;
  git commit filename&lt;br /&gt;
&lt;br /&gt;
OR&lt;br /&gt;
&lt;br /&gt;
  git commit -a &lt;br /&gt;
&lt;br /&gt;
(the last if you've made changes to many files). This command will ask&lt;br /&gt;
you to enter information for the change log.&lt;br /&gt;
&lt;br /&gt;
CONTRARY to CVS, a commit does not yet make your changes available to&lt;br /&gt;
others. This is advantageous, because it allows you to do commits&lt;br /&gt;
locally while you're developing a code, and then go back to an older&lt;br /&gt;
version once you realize that you've made a mistake. However, let's&lt;br /&gt;
assume that you've programmed something that is working and you want&lt;br /&gt;
to make it available to everybody. In this case, commit everything as&lt;br /&gt;
described above and then do a &lt;br /&gt;
&lt;br /&gt;
  git push&lt;br /&gt;
&lt;br /&gt;
(do NOT forget this last command).&lt;br /&gt;
&lt;br /&gt;
After you have committed and pushed your changes, WE STRONGLY&lt;br /&gt;
RECOMMEND THAT YOU REMOVE YOUR CLONED REPOSITORY (rm -r repo). The&lt;br /&gt;
reason is that experience shows that people often start working on&lt;br /&gt;
their &amp;quot;private&amp;quot; versions of the scripts and then either forget to&lt;br /&gt;
commit their changes (=nobody else gets access to them) OR they forget&lt;br /&gt;
to do regular updates of their local clones and then run into problems&lt;br /&gt;
that have already been fixed in the official repository. Access to the&lt;br /&gt;
current version of the scripts is better obtained using the approach&lt;br /&gt;
outlined below (and implemented on the Remeis machines, for example).&lt;br /&gt;
&lt;br /&gt;
== Other useful commands ==&lt;br /&gt;
* assuming you've already cloned the repository and you want to update it to the newest version, use &amp;lt;pre&amp;gt;git pull&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* to obtain a change log of the repository &amp;lt;pre&amp;gt;git log&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* to obtain a change log for one file &amp;lt;pre&amp;gt;git log filename&amp;lt;/pre&amp;gt; (which will work pretty much for all files, but for some reason does not work for the intscripts; note that even for the intscripts the full change log is still available and you can still check out older versions of the script should you desire to do so)&lt;br /&gt;
&lt;br /&gt;
* to tag one of the commits with a tagname, e.g., to mark the submitted version of your paper as submitted, get the commit id from &amp;lt;code&amp;gt;git log&amp;lt;/code&amp;gt; and do &amp;lt;pre&amp;gt;git tag 'tagname' id&amp;lt;/pre&amp;gt; where tagname only needs quotes if it contains, e.g., spaces&lt;br /&gt;
&lt;br /&gt;
* to push the tag&amp;lt;pre&amp;gt;git push --tags&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* optimize the local git repository &amp;lt;pre&amp;gt;git gc --aggressive&amp;lt;/pre&amp;gt; this will optimize the tree of stored local changes, removing intermediate data that are not needed anymore. This makes your local repository dramatically faster and can save significant space. You should run this every now and then (on very active directories probably once a week). &lt;br /&gt;
  &lt;br /&gt;
* find out where the repository originally came from before it was cloned:&amp;lt;pre&amp;gt;git remote -v&amp;lt;/pre&amp;gt;or for a little more information&amp;lt;pre&amp;gt;git remote show origin&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* showing the differences between the old and new file:&amp;lt;pre&amp;gt;diff -u new_file old_file&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Create your own repository =&lt;br /&gt;
&lt;br /&gt;
'' The following entry is from an email by Matthias Kühnel to Jieun (with additional comments added afterwards) and was intended to explain '''how to create a repository in order to edit a paper together using GIT'''.''&lt;br /&gt;
&lt;br /&gt;
Now we'll create a git-repository for your paper: in your Remeis home&lt;br /&gt;
directory create a directory where to store all your repositories in,&lt;br /&gt;
such as ~/git (at the moment we'll create only one ;-)). Create a&lt;br /&gt;
subdirectory for your paper in there, ~/git/choi2011a for example.&lt;br /&gt;
Change into that directory and create an empty repository by&lt;br /&gt;
   git init --bare --shared&lt;br /&gt;
You should get a message like &amp;quot;Initialized empty Git repository in&lt;br /&gt;
/home/choi/git/choi2011a/&amp;quot;. Add &amp;lt;code&amp;gt;--shared&amp;lt;/code&amp;gt; only if everyone in your group should be able to &lt;br /&gt;
commit changes.&lt;br /&gt;
All in all, this should create a structure of&lt;br /&gt;
files and subdirectories in your repository directory. Later your files&lt;br /&gt;
will be hidden somewhere in this structure (I'm not sure where to be&lt;br /&gt;
honest). The thing is that a bare repository only contains&lt;br /&gt;
modifications, that means no whole file, only different pieces depending&lt;br /&gt;
on the file version.&lt;br /&gt;
Now you have to modify the 'config' file of the repository (//note:// you should not need the following modifications if you initialized the repository with the &amp;lt;code&amp;gt;--shared&amp;lt;/code&amp;gt; option), for example&lt;br /&gt;
   /home/choi/git/choi2011a/config&lt;br /&gt;
The file should look like&amp;lt;pre&amp;gt;&lt;br /&gt;
   [core]&lt;br /&gt;
        repositoryformatversion = 0&lt;br /&gt;
        filemode = true&lt;br /&gt;
        bare = true&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Your repository is now ready to be used, but empty. So let's add some&lt;br /&gt;
files into it!&lt;br /&gt;
&lt;br /&gt;
Create an empty directory somewhere that will contain your paper. We now clone your&lt;br /&gt;
(empty) repository into your source directory:&lt;br /&gt;
   git clone crux:/home/choi/git/choi2011a .&lt;br /&gt;
Note that we clone from machine &amp;lt;code&amp;gt;crux&amp;lt;/code&amp;gt;, even if we are working on that machine. This approach will make your life easier if you are working on multiple machines in the Remeis cluster. Do not forget the trailing dot!&lt;br /&gt;
&lt;br /&gt;
Now your directory is a clone of the repository. Copy all files and subdirectories that you would like to be part of the repository into the directory and then add these files to git&lt;br /&gt;
  git add filenames&lt;br /&gt;
where filenames can include (relative) paths to files somewhere in the directory tree of your repository.&lt;br /&gt;
&lt;br /&gt;
A general rule for tex repositories for papers is to only add the source code and&lt;br /&gt;
*no* compiled or auxiliary files. That means, just add the .tex file,&lt;br /&gt;
any used styles (.sty) and images (.pdf, .ps, .eps or whatever). If you have&lt;br /&gt;
also isis scripts (.sl) which creates some plots, you may add them also.&lt;br /&gt;
Once you have added all necessary files, you have to 'commit' the changes:&lt;br /&gt;
  git commit -a&lt;br /&gt;
Now your default editor should open automatically, where you have to&lt;br /&gt;
enter a comment describing the changes (attention: the default editor should be set first in the ~/.cshrc, see [[csh:start|TC shell]]). This&lt;br /&gt;
comment will be put into the log. The editor also shows a list of files&lt;br /&gt;
which will be added/modified/removed. Please note that this list is for&lt;br /&gt;
your information *only*. Any changes to the list have no effect!&lt;br /&gt;
After you have entered a comment, quick save the file (if you use jed&lt;br /&gt;
Ctrl-X-S) and exit the editor (Ctrl-X-C). You should see something like:&amp;lt;pre&amp;gt;&lt;br /&gt;
  [master 5e91497] your_entered_comment&lt;br /&gt;
   1_or_more files changed, 3341_or_any_other_number insertions(+), 0&lt;br /&gt;
   deletions(-)&lt;br /&gt;
   create mode 100644 a_file_you_have_added&lt;br /&gt;
   ...&amp;lt;/pre&amp;gt;&lt;br /&gt;
   &lt;br /&gt;
In order to avoid being prompted that unnecessary files such as editor backup files (e.g., filenames ending in a tilde or with .bak and other unnecessary files are not part of the repository, you can generate files called &amp;lt;code&amp;gt;.gitignore&amp;lt;/code&amp;gt; in your git directories. These files contain descriptions of files which should not be in the repository. a &amp;lt;code&amp;gt;.gitignore&amp;lt;/code&amp;gt; file is valid in the current directory and all of its subdirectories. These may contain further &amp;lt;code&amp;gt;.gitignore&amp;lt;/code&amp;gt;-files. A good &amp;lt;code&amp;gt;.gitignore&amp;lt;/code&amp;gt; for a paper would be:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#&lt;br /&gt;
# git ignore file for TeX files&lt;br /&gt;
#&lt;br /&gt;
*~&lt;br /&gt;
*.aux&lt;br /&gt;
*.log&lt;br /&gt;
*.bbl&lt;br /&gt;
*.blg&lt;br /&gt;
*.bak&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Note that after creating the file you will have to add it to the repository! Files that were checked in before the .gitignore exists are not affected by adding the .gitignore, even if the filename is explicitly written down there. In this case, do a git rm [filename] and commit, and afterwards the file will not be checked in again.&lt;br /&gt;
&lt;br /&gt;
That's a summary of the changes, which will be put into the repository&lt;br /&gt;
once you have 'push'ed them:&lt;br /&gt;
   git push origin master&lt;br /&gt;
Please note, that the usual command is&lt;br /&gt;
   git push&lt;br /&gt;
without the origin-master-stuff, which has to be done only once if an&lt;br /&gt;
empty repository was created!&lt;br /&gt;
If you modify previously added files later, you don't have to add them&lt;br /&gt;
again, of course. Instead skip the adding command and 'commit' and&lt;br /&gt;
'push' the changes directly.&lt;br /&gt;
&lt;br /&gt;
Everybody knowing the path to your repository can now clone it, edit&lt;br /&gt;
files and push changes. To update your local copy with the repository&lt;br /&gt;
(i.e. to get the changes of somebody else) use&lt;br /&gt;
   git pull&lt;br /&gt;
&lt;br /&gt;
= Committing only parts of the modifications =&lt;br /&gt;
''A further functionality Manfred finds particularly useful.''&lt;br /&gt;
&lt;br /&gt;
It has been mentioned above that one can only commit selected files with&lt;br /&gt;
&lt;br /&gt;
  git add file1 [file2 ...]  &amp;amp;&amp;amp;  git commit&lt;br /&gt;
&lt;br /&gt;
(Do not use &amp;lt;code&amp;gt;git commit -a&amp;lt;/code&amp;gt; in this case. If you really want to commit all changes, there is no need to first &amp;lt;code&amp;gt;git add&amp;lt;/code&amp;gt; the files for this next commit.) &lt;br /&gt;
&lt;br /&gt;
It is also possible to &amp;lt;code&amp;gt;git add&amp;lt;/code&amp;gt; only parts of the modifications, namely with the &amp;lt;code&amp;gt;-i&amp;lt;/code&amp;gt;(nteractive) Option. When I run&lt;br /&gt;
  &lt;br /&gt;
  git add -i file1 [file2 ...]&lt;br /&gt;
&lt;br /&gt;
and press &amp;lt;code&amp;gt;p&amp;lt;/code&amp;gt; for (patch), 1 for the first file, and then hit [Return], I can decide for every changed block (&amp;quot;hunk&amp;quot;) in file 1 whether (&amp;lt;code&amp;gt;y&amp;lt;/code&amp;gt;) I want to add (&amp;quot;stage&amp;quot;) this change to the next commit or not (&amp;lt;code&amp;gt;n&amp;lt;/code&amp;gt;). If I want to commit only part of what git considers a &amp;quot;hunk&amp;quot; in first place, I can press &amp;lt;code&amp;gt;s&amp;lt;/code&amp;gt; in order to split the current hunk. When I'm done with file 1 or when I quit with &amp;lt;code&amp;gt;q&amp;lt;/code&amp;gt;, I can start over from the beginning, e.g. patching the next file.&lt;br /&gt;
&lt;br /&gt;
After the desired hunks have been staged to the index, you run&lt;br /&gt;
&lt;br /&gt;
   git commit&lt;br /&gt;
&lt;br /&gt;
as usual, without &amp;lt;code&amp;gt;-a&amp;lt;/code&amp;gt;!&lt;br /&gt;
&lt;br /&gt;
= GIT Config =&lt;br /&gt;
&lt;br /&gt;
Make sure to update your name and e-mail-address in your home under ''.gitconfig'' like&amp;lt;pre&amp;gt;&lt;br /&gt;
  [user]&lt;br /&gt;
        email = matthias.kuehnel@sternwarte.uni-erlangen.de&lt;br /&gt;
        name = Matthias Kuehnel&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:GIT]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=General_organisation_of_the_lab&amp;diff=1809</id>
		<title>General organisation of the lab</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=General_organisation_of_the_lab&amp;diff=1809"/>
		<updated>2019-02-19T14:53:35Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:internal]]&lt;br /&gt;
This page is up to date for the Spring Lab 2019.&lt;br /&gt;
=== Who is involved in which experiment? ===&lt;br /&gt;
'''Azimuth''': Katya, Philipp (T.), Thomas, Ole &amp;lt;br/&amp;gt;&lt;br /&gt;
'''CCD''': Maria, Matthias, Dominic, Melanie, Katrin, Christian &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Error propagation''': Max, Basti &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Imaging''': Simon &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Observing''': David &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Radio''': Ralf, Jonathan, (Jakob), Andrea, (Konstantin, Florian) &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Spectroscopy''': Andreas &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Labtable ===&lt;br /&gt;
This is the link to our labtable: https://www.sternwarte.uni-erlangen.de/internal-area/labtable/ &amp;lt;br/&amp;gt;&lt;br /&gt;
Please insert the dates of both experiment and final protocol as well as your scores in this table. You can also leave comments. &amp;lt;br/&amp;gt;&lt;br /&gt;
This link is a permanent link, so for simplicity you might want to save it as a bookmark in your favorite browser.&lt;br /&gt;
&lt;br /&gt;
=== Attendance ===&lt;br /&gt;
In order to have an overview of the individual attendances during the lab, there is a Doodle poll, where you have sign in for the days you will be at the observatory. At the days marked with 'yes', you are expected to be in Bamberg. &amp;lt;br/&amp;gt;&lt;br /&gt;
First block: &amp;lt;br/&amp;gt;&lt;br /&gt;
Second block: &amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
Additionally, it is mandatory for everyone to help during the observing night(s) in the garden. In order to have enough people around and to distribute this task fairly, you need to sign into additional Doodle polls, whose outcome Ingo is using to create a list containing the night shifts for everyone. &amp;lt;br/&amp;gt;&lt;br /&gt;
The decision whether observing is planned for that night will be made until 5 pm by the profs. &amp;lt;br/&amp;gt;&lt;br /&gt;
Night Doodle first block: &amp;lt;br/&amp;gt;&lt;br /&gt;
Night Doodle second block: &amp;lt;br/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Plotting_with_the_S-Lang_Xfig_module&amp;diff=1791</id>
		<title>Plotting with the S-Lang Xfig module</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Plotting_with_the_S-Lang_Xfig_module&amp;diff=1791"/>
		<updated>2019-02-12T10:56:58Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: /* Random pieces of helpful code: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;SLxfig will not usually come with your standard ISIS installation, but it's an easy to install module. Get it from [http://www.jedsoft.org/fun/slxfig/ JedSoft/Xfig]&lt;br /&gt;
&lt;br /&gt;
= Where to find examples =&lt;br /&gt;
Most important&lt;br /&gt;
* [[Isis_slxfig_fancyremeisplots| The Remeis X-fig plot gallery ]]&lt;br /&gt;
&lt;br /&gt;
Note also the examples on the SLxfig websites of [http://www.jedsoft.org/fun/slxfig/examples.html John E. Davis]&lt;br /&gt;
and [http://pulsar.sternwarte.uni-erlangen.de/hanke/science/X-ray/ISIS/SLxfig/ Manfred Hanke].&lt;br /&gt;
&lt;br /&gt;
--- ''Manfred's notes from his first introduction on 2010-04-28'' --- (to be continued?)&lt;br /&gt;
&lt;br /&gt;
= General Tips &amp;amp; Tricks =&lt;br /&gt;
--- ''Manfred's notes from his first introduction on 2010-04-28'' --- (to be continued?)&lt;br /&gt;
&lt;br /&gt;
If you never plotted with slxfig, please have a look at the next section.&lt;br /&gt;
&lt;br /&gt;
== Random pieces of helpful code: ==&lt;br /&gt;
&lt;br /&gt;
* Prevent the ticlabels from exceeding the plot size: &amp;lt;code&amp;gt;pl.axis(;ticlabels_confine);&amp;lt;/code&amp;gt;&lt;br /&gt;
* Format ticlabels:&lt;br /&gt;
** linear scale: to e.g. 2 places after decimal point: &amp;lt;code&amp;gt;pl.axis(;linear, format=&amp;quot;$%.2f$&amp;quot;);&amp;lt;/code&amp;gt;&lt;br /&gt;
** log scale: to e.g. 2 places after decimal point in power of number: &amp;lt;code&amp;gt;pl.axis(; log, format=&amp;quot;$10^{%+.2f}$&amp;quot;);&amp;lt;/code&amp;gt; where the &amp;lt;tt&amp;gt;+&amp;lt;/tt&amp;gt; tells to always show the sign of the power&lt;br /&gt;
* LaTex packages which are not loaded per default can be added manually with &amp;lt;code&amp;gt;xfig_add_latex_package(&amp;quot;PACKAGENAME&amp;quot;);&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== eps-Files with slxfig ==&lt;br /&gt;
(''after Jörns Mail'')&lt;br /&gt;
&lt;br /&gt;
The eps produced by the slxfig module is usually '''VERY large''' because the postscript&lt;br /&gt;
code produced by transfig is very inefficient. With some postprocessing&lt;br /&gt;
you can significantly reduce the figure sizes:&lt;br /&gt;
&lt;br /&gt;
- convert your figure to pdf (the -dEPSCrop is important - this tells ps2pdf to use the eps bounding box): &amp;lt;code&amp;gt;ps2pdf -dEPSCrop bla.eps&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- if you really need postscript, e.g., for a journal submission where pdf figures are not allowed, then convert the pdf back to (encapsulated) postscript: &amp;lt;code&amp;gt;pdf2ps -dLanguageLevel=3 bla.pdf bla.ps&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
a few numbers:&lt;br /&gt;
&lt;br /&gt;
* original eps file size: 3.9MB&lt;br /&gt;
* pdf file size: 37kB&lt;br /&gt;
* eps file size after converting back: 187kB&lt;br /&gt;
&lt;br /&gt;
== the autoeps and tmp folders ==&lt;br /&gt;
&lt;br /&gt;
The autoeps and tmp folders are always created by default in the folder you're executing your script. These folders contain caching information such that plotting of the same or similar things doesn't have to be done over and over again from scratch. As you have them in each folder separately, these folders tend to be annoying. Either you're deleting the folders occasionally, or you spent quite some amount of disk space for really useless stuff. The solution is to tell slxfig to create these folders in a specifc location. There they don't take up space on /home or /userdata and don't appear in your scripting folders. &lt;br /&gt;
&lt;br /&gt;
So, in order to achieve this you have to do the following:&lt;br /&gt;
&lt;br /&gt;
# Create a file named &amp;quot;.slxfigrc&amp;quot; in your home directory&lt;br /&gt;
# Add the lines&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   variable slxfig_tmp_dir;&lt;br /&gt;
   if (stat_file(&amp;quot;/scratch1&amp;quot;) == NULL) {&lt;br /&gt;
      slxfig_tmp_dir = &amp;quot;/tmp/&amp;quot;+getenv(&amp;quot;USER&amp;quot;)+&amp;quot;/xfig/&amp;quot;;&lt;br /&gt;
   } else {&lt;br /&gt;
      slxfig_tmp_dir = &amp;quot;/scratch1/&amp;quot;+getenv(&amp;quot;USER&amp;quot;)+&amp;quot;/xfig/&amp;quot;;&lt;br /&gt;
   }&lt;br /&gt;
   xfig_set_tmp_dir(slxfig_tmp_dir);&lt;br /&gt;
   xfig_set_autoeps_dir(slxfig_tmp_dir);&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then all the temporary files in all of your slxfig scripts will from now &lt;br /&gt;
on be stored in these directories. &lt;br /&gt;
&lt;br /&gt;
Note that this more complicated setup is done in order to avoid putting files on /tmp, if a /scratch1 file system exists. The reason being that too many files on /tmp might crash your computer, as there is a maximal number of files that can be on a certain disk. And /tmp is located on the disk where the operating system is installed. And now just imagine the chaos when the system itself is not able to write any more files ... so better use a different disk (that means the /scratch1 disk) for the SLxfig tmp files, by following the approach above.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Programming preliminaries ==&lt;br /&gt;
&lt;br /&gt;
=== References in S-Lang ===&lt;br /&gt;
&lt;br /&gt;
==== References to variables ====&lt;br /&gt;
&lt;br /&gt;
Functions cannot change scalar arguments that are passed by value:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
define test(v)&lt;br /&gt;
{ vmessage(&amp;quot;in test: v=%d&amp;quot;, v);&lt;br /&gt;
  v = -1;  % only modifies variable local to test&lt;br /&gt;
  vmessage(&amp;quot;in test: v=%d&amp;quot;, v);&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
variable a=42;&lt;br /&gt;
test(a);              % a is passed by value&lt;br /&gt;
vmessage(&amp;quot;a=%d&amp;quot;, a);  % a has not been changed outside of test&lt;br /&gt;
test(42);             % test can also be run with a constant&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
reference operator ''&amp;amp;'', dereference operator ''@'':&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
variable r = &amp;amp;a;                 % reference to a (from previous example)&lt;br /&gt;
vmessage(&amp;quot;r=%S; @r=%d&amp;quot;, r, @r);  % reference and dereferenced reference&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
references to variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
define test2(r)&lt;br /&gt;
{ vmessage(&amp;quot;in test: @r=%d&amp;quot;, @r);&lt;br /&gt;
            % r is still only a local variable&lt;br /&gt;
  @r = -1;  % r is not changed, but the variable referenced by r&lt;br /&gt;
  vmessage(&amp;quot;in test: @r=%d&amp;quot;, @r);&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
test2(&amp;amp;a);  % (from previous examples)&lt;br /&gt;
vmessage(&amp;quot;a=%d&amp;quot;, a);  % a *has* been changed&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[References to variables|see also]]&lt;br /&gt;
&lt;br /&gt;
==== References to functions ====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
variable my_fun = &amp;amp;sin;&lt;br /&gt;
print( @my_fun(0) );&lt;br /&gt;
print( @my_fun(PI/2) );&lt;br /&gt;
&lt;br /&gt;
variable x=[0:10:0.01];&lt;br /&gt;
plot(x, @my_fun(x));&lt;br /&gt;
&lt;br /&gt;
my_fun = &amp;amp;exp;&lt;br /&gt;
plot(x, @my_fun(x));&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Object-oriented programming ===&lt;br /&gt;
&lt;br /&gt;
The following function only operates on &amp;quot;car-structures&amp;quot;:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
define drive_car(c, dest)&lt;br /&gt;
{&lt;br /&gt;
  vmessage(&amp;quot;%s drives from %s to %s&amp;quot;, c.plate, c.place, dest);&lt;br /&gt;
  c.place = dest;&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
define init_car(plate, place)&lt;br /&gt;
{&lt;br /&gt;
  return struct { plate=plate, place=place };&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
variable car = init_car(&amp;quot;S-FR 3011&amp;quot;, &amp;quot;Erlangen&amp;quot;);&lt;br /&gt;
drive_car(car, &amp;quot;Bamberg&amp;quot;);&lt;br /&gt;
drive_car(car, &amp;quot;Erlangen&amp;quot;);&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It should thus be more directly connected to such an object.&lt;br /&gt;
=&amp;gt; Define a new field of the structure with reference to the function:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
define init_car(plate, place)&lt;br /&gt;
{&lt;br /&gt;
  return struct { plate=plate, place=place, drive=&amp;amp;drive_car };&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
variable car = init_car(&amp;quot;S-FR 3011&amp;quot;, &amp;quot;Erlangen&amp;quot;);&lt;br /&gt;
(@car.drive)(car, &amp;quot;Bamberg&amp;quot;);  % @car.drive  is actually the function  drive_car&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== OO in S-Lang ===&lt;br /&gt;
&lt;br /&gt;
from the S-Lang manual, Appendix A.3 ''What's new for S-Lang 2.0:''&lt;br /&gt;
&lt;br /&gt;
 Syntactic sugar for objected-oriented style method calls.&lt;br /&gt;
 S-Lang 1 code such as&lt;br /&gt;
 &amp;lt;code&amp;gt;(@s.method)(s, args);&amp;lt;/code&amp;gt;&lt;br /&gt;
 may be written much more simply as&lt;br /&gt;
 &amp;lt;code&amp;gt;s.method(args);&amp;lt;/code&amp;gt;&lt;br /&gt;
 This should make &amp;quot;object-oriented&amp;quot; code somewhat more readable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;car.drive(&amp;quot;Erlangen&amp;quot;);  % car is implicitly passed as first argument to drive_car&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Xfig ==&lt;br /&gt;
&lt;br /&gt;
http://www.xfig.org/&lt;br /&gt;
&lt;br /&gt;
=== The S-Lang xfig module ===&lt;br /&gt;
&lt;br /&gt;
see [http://jedsoft.org/fun/slxfig/ John E. Davis' homepage],&lt;br /&gt;
especially the [http://jedsoft.org/fun/slxfig/examples.html examples page]&lt;br /&gt;
&lt;br /&gt;
The examples from the git repository &lt;br /&gt;
  git://git.jedsoft.org/git/slxfig.git&lt;br /&gt;
(or my ''Mh'' branch on [http://www.sternwarte.uni-erlangen.de/~hanke/git.public/?p=slxfig;a=shortlog;h=Mh http://www.sternwarte.uni-erlangen.de/~hanke/git.public/slxfig])&lt;br /&gt;
are also available on http://pulsar.sternwarte.uni-erlangen.de/hanke/science/X-ray/ISIS/SLxfig/.&lt;br /&gt;
&lt;br /&gt;
=== Xfig objects as OO-style S-Lang structures ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
variable po = xfig_new_polygon([0, 2, 1, 0], [0, 0, 2, 0]);&lt;br /&gt;
print(po);  % structure with many internal fields&lt;br /&gt;
            % and methods (function references) that should be used as interface&lt;br /&gt;
po.render(&amp;quot;polygon.eps&amp;quot;);  % writes .fig file, runs xfig to produce output&lt;br /&gt;
&lt;br /&gt;
po.set_fill_color(&amp;quot;red&amp;quot;);&lt;br /&gt;
po.set_area_fill(20);&lt;br /&gt;
po.render(&amp;quot;polygon_red.eps&amp;quot;);&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
[[File:polygon.png]][[File:polygon_red.png]]&lt;br /&gt;
&lt;br /&gt;
=== High-level plot objects ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
variable pl = xfig_plot_new();&lt;br /&gt;
variable x = [0:10:0.01];&lt;br /&gt;
pl.plot(x, sin(x));  % x-y plot&lt;br /&gt;
pl.title(&amp;quot;a nice sine wave $y=\sin(x)$&amp;quot;R);  % SLxfig renders text via latex&lt;br /&gt;
pl.xlabel(&amp;quot;$x$&amp;quot;);&lt;br /&gt;
pl.ylabel(&amp;quot;$y$&amp;quot;);&lt;br /&gt;
pl.render(&amp;quot;plot.pdf&amp;quot;);  % run XFig's fig2dev to create an pdf file&lt;br /&gt;
pl.render(&amp;quot;plot.eps&amp;quot;);  % run XFig's fig2dev to create an eps file&lt;br /&gt;
pl.render(&amp;quot;plot.png&amp;quot;);  % run XFig's fig2dev to create a png&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
[[File:plot.png|plot]]&lt;br /&gt;
&lt;br /&gt;
define world coordinate system(s):&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
variable pl2 = xfig_plot_new(7, 5);  % size of the plot window in cm x cm (default is 14 cm x 10 cm)&lt;br /&gt;
pl2.world(-2, 12, -1.5, 1.5);&lt;br /&gt;
pl2.world2(-2/PI, 12/PI, -1.5, 1.5);&lt;br /&gt;
pl2.plot(x, sin(x));&lt;br /&gt;
pl2.render(&amp;quot;plot2.eps&amp;quot;);&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
[[File:plot2.png]]&lt;br /&gt;
&lt;br /&gt;
configuration of the axes via qualifiers&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
variable pl3 = xfig_plot_new(7, 5);&lt;br /&gt;
pl3.world(-2, 12, -1.5, 1.5);&lt;br /&gt;
pl3.world2(-2/PI, 12/PI, -1.5, 1.5);&lt;br /&gt;
pl3.y2axis(; off);  % totally switch off y2-axis&lt;br /&gt;
pl3.y1axis(; ticlabels=0);  % only remove y1 tic mark labels&lt;br /&gt;
pl3.x2axis(; major=[0, PI/2, PI]);  % define own major tic marks&lt;br /&gt;
pl3.x1axis(; major=[-1, 5, 11], minor=[-5:15:0.5]);  % But then, one (currently) also has to define the minor tic marks!&lt;br /&gt;
pl3.plot(x, sin(x));&lt;br /&gt;
pl3.render(&amp;quot;plot3.eps&amp;quot;);&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
[[File:plot3.png]]&lt;br /&gt;
&lt;br /&gt;
I'm trying to document these functions.&lt;br /&gt;
Suggested syntax for methods of objects:&lt;br /&gt;
&amp;lt;code&amp;gt;help(&amp;quot;xfig_plot.x1axis&amp;quot;);&amp;lt;/code&amp;gt;&lt;br /&gt;
Or directly from the method itself:&lt;br /&gt;
&amp;lt;code&amp;gt;pl.x1axis(; help);&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:SLxfig]]&lt;br /&gt;
[[Category:Isis / Slang]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Skivergnuegen_2019&amp;diff=1717</id>
		<title>Skivergnuegen 2019</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Skivergnuegen_2019&amp;diff=1717"/>
		<updated>2018-11-20T14:03:03Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Remeis Skifahren 2019''' The same procedure as every year ;-) &lt;br /&gt;
Hier werden die wichtigsten organisatorischen Dinge festgehalten. Jeder darf hier gerne editieren; wer keinen Account für das Wiki hat, soll sich bitte an jemanden wenden der Zugang hat.&lt;br /&gt;
&lt;br /&gt;
[[File:154854 silvretta-montafon-panorama.jpeg|right|700px]]&lt;br /&gt;
&lt;br /&gt;
== Allgemeine Infos ==&lt;br /&gt;
*Wann: 12.01.19 (Sa) bis 19.01.19 (Sa)&lt;br /&gt;
&lt;br /&gt;
*Ferienwohnung(en):&lt;br /&gt;
**Wir kommen wieder unter im [https://www.ferienwohnungen-montafon.com/ferienhaus-enzian/ Haus Enzian] des [https://www.grandau.at/ Sporthotels Grandau], sowie dem 5-er Apartment [https://www.grandau.at/zimmer/ferienwohnungen/Ferienwohnung-Edelweiss-Top-5/ TOP5] nebenan.&lt;br /&gt;
**Adresse des Sporthotel: Montafonerstraße 274a, 6791 St. Gallenkirch, Österreich. Unsere Unterkünfte liegen im Türkeiweg.&lt;br /&gt;
&lt;br /&gt;
*Skigebiet: Montafon (Vorarlberg)&lt;br /&gt;
**Skigebiet Karte: https://winter.intermaps.com/montafon?lang=de&lt;br /&gt;
**Skipass Preise: https://www.montafon.at/de/Service/Bergbahn-Preise-Tickets/Mehrtageskarte-Winter&lt;br /&gt;
**Wer nicht alle 7 Tage Skifahren möchte: Es gibt Angebote wie z.B. 5 aus 7, mit einem solchen Skipass kann man innerhalb von 7 Tagen an 5 beliebigen Tagen skifahren.&lt;br /&gt;
&lt;br /&gt;
*Skiverleih: [http://www.sportharry.at/ Sport Harry], direkt an der Talstation. Promotioncode news110 auf alpinresorts.com spart bis zu 30% auf die Preise.&lt;br /&gt;
&lt;br /&gt;
== Unterkunft ==&lt;br /&gt;
=== Aufteilung ===&lt;br /&gt;
Dieses Jahr gibt es neben der Hütte noch zusätzlich das 5-er Appartment (TOP5).&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Zimmer&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Insassen&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | 2-er&lt;br /&gt;
| Person 1, Person 2 &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | 3-er&lt;br /&gt;
| Ralf, Person 2, Person 3&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | 4-er&lt;br /&gt;
| Nela, Ohle, Eva, Katya&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | 5-er&lt;br /&gt;
| Person 1, Person 2, Person 3, Person 4, Person 5&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Apartment (5)&lt;br /&gt;
| Eugenia, Michi, Person 3, Person 4, Person 5&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Bettwäsche/Handtücher sind dort vorhanden und müssen nicht mitgenommen werden. Kaffeemaschine, Waffeleisen sind ebenfalls vorhanden.&lt;br /&gt;
Brötchen können wir vorbestellen im Hotel am Vortag vorbestellen und dort am naechsten morgen, bei der Besitzerin bzw. im Hotel, die wir dann morgens um 7:15 erhalten.&lt;br /&gt;
&lt;br /&gt;
== Fahrer ==&lt;br /&gt;
Fahrer koennen sich hier eintragen und Eckdaten angeben. Diejenige, die mitfahren möchten, sprechen sich mit den Fahrern ab und tragen sich ebenfalls ein. Klärt bitte auch die Gepäcklage, ggf. kann ein anderer Fahrer z.B. Skiausrüstung mitnehmen.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Fahrer&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | # Plätze&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Anreise&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Mitfahrer Anreise&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Abreise&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Mitfahrer Abreise&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Skimitnahme&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Kommentar&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Fahrer Auto 1&lt;br /&gt;
| Anzahl Plätze Auto 1&lt;br /&gt;
| Anreise Auto 1&lt;br /&gt;
| Mitfahrer Anreise Auto 1&lt;br /&gt;
| Abreise Auto 1&lt;br /&gt;
| Mitfahrer Abreise Auto 1&lt;br /&gt;
| Skimitnahme Auto 1&lt;br /&gt;
| Kommentar Auto 1&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Fahrer Auto 2&lt;br /&gt;
| Anzahl Plätze Auto 2&lt;br /&gt;
| Anreise Auto 2&lt;br /&gt;
| Mitfahrer Anreise Auto 2&lt;br /&gt;
| Abreise Auto 2&lt;br /&gt;
| Mitfahrer Abreise Auto 2&lt;br /&gt;
| Skimitnahme Auto 2&lt;br /&gt;
| Kommentar Auto 2&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Fahrer Auto 3&lt;br /&gt;
| Anzahl Plätze Auto 3&lt;br /&gt;
| Anreise Auto 3&lt;br /&gt;
| Mitfahrer Anreise Auto 3&lt;br /&gt;
| Abreise Auto 3&lt;br /&gt;
| Mitfahrer Abreise Auto 3&lt;br /&gt;
| Skimitnahme Auto 3&lt;br /&gt;
| Kommentar Auto 3&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Fahrer Auto 4&lt;br /&gt;
| Anzahl Plätze Auto 4&lt;br /&gt;
| Anreise Auto 4&lt;br /&gt;
| Mitfahrer Anreise Auto 4&lt;br /&gt;
| Abreise Auto 4&lt;br /&gt;
| Mitfahrer Abreise Auto 4&lt;br /&gt;
| Skimitnahme Auto 4&lt;br /&gt;
| Kommentar Auto 4&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;row&amp;quot; | Fahrer Auto 5&lt;br /&gt;
| Anzahl Plätze Auto 5&lt;br /&gt;
| Anreise Auto 5&lt;br /&gt;
| Mitfahrer Anreise Auto 5&lt;br /&gt;
| Abreise Auto 5&lt;br /&gt;
| Mitfahrer Abreise Auto 5&lt;br /&gt;
| Skimitnahme Auto 5&lt;br /&gt;
| Kommentar Auto 5&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Schwarzes Brett ==&lt;br /&gt;
&lt;br /&gt;
=== Essen ===&lt;br /&gt;
Hier gibts den Essensplan, soweit übernommen von den letzten Jahren. Da wir sehr viele Leute sind, sollten wir wieder vorab grob planen, was wir kochen wollen. Wir können einige Dinge in Deutschland besorgen und mitnehmen, es gib aber auch einen nahe gelegen Supermarkt. Generelle Dinge, wie z.B. Gewürze oder Aufstriche für Frühstücksbrötchen könnte man auch mitbringen.&lt;br /&gt;
&lt;br /&gt;
Wer Kochvorschläge oder andere Ideen hat, gerne unten eintragen und kommentieren. Bedenkt, dass die Zubereitung (relativ) einfach sein sollte. Ich (Thomas) habe jetzt mal eine Liste unten erstellt, aber vor allem die Reihenfolge/Tage kann man sicher noch hin und her bewegen. Einige (wenigere) Sachen müssen wir dann manchmal trotzdem noch beim Spar kaufen, da ja auch der Kühlschrank nur begrenzt Platz hat.&lt;br /&gt;
&lt;br /&gt;
''VEGANE Optionen für Christian: vegane Sahne, Quark, Leinöl''&lt;br /&gt;
&lt;br /&gt;
*Samstag: Spaghetti Bolognese + veg. Bolognese&lt;br /&gt;
*Sonntag: Käse Spätzle&lt;br /&gt;
*Montag: Burritos &lt;br /&gt;
*Dienstag: Risotto&lt;br /&gt;
*Mittwoch: Gulasch m. Nudeln &amp;amp; Pilze ?&lt;br /&gt;
*Donnerstag: Kartoffeln mit Kräuter-Quark&lt;br /&gt;
*Freitag: Linseneintopf + Bolognese für Basti&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Einkaufliste Abendessen ====&lt;br /&gt;
'' Wird von X &amp;amp; Y eingekauft''&lt;br /&gt;
*2.5kg Hackfleisch &lt;br /&gt;
*2.5kg Spaghetti&lt;br /&gt;
*0.5kg Vollkorn-Spaghetti&lt;br /&gt;
*2.0kg Risotto Reis &lt;br /&gt;
*1.5 kg Langkorn/Basmati Reis&lt;br /&gt;
*10 Dosen gestückelte Tomaten &lt;br /&gt;
*6.0kg Spätzle (vorgekocht aus dem Kühlregal) &lt;br /&gt;
*1 Olivenöl (extra nativ) &lt;br /&gt;
*4kg geriebenen Käse &lt;br /&gt;
*3.0kg Emmentaler am Stück &lt;br /&gt;
*1.0 kg Parmesan / Grana Padano&lt;br /&gt;
*Gemüsebrühe &lt;br /&gt;
*1 Flaschen Weißwein (2-3€ pro Flasche dürfen es schon sein) &lt;br /&gt;
*2 Flasche Rotwein (2-3€ pro Flasche dürfen es schon sein)&lt;br /&gt;
*2 Knollen Sellerie (od 4 mal Staudensellerie)&lt;br /&gt;
*6kg Karotten&lt;br /&gt;
*3 Netze Zwiebeln &lt;br /&gt;
*1.5 kg Pilze (5 Packungen)&lt;br /&gt;
*1.5 kg Zucchini (2-3 Packungen)&lt;br /&gt;
*1.5kg (Teller)-linsen (getrocknet!)&lt;br /&gt;
*8.0kg (große) festkochende Kartoffeln&lt;br /&gt;
*40-45 große Tortillas&lt;br /&gt;
*10 Dose schwarze Bohnen&lt;br /&gt;
*1-2 Gläser Jalapenos (je nach Größe)&lt;br /&gt;
*2.5kg Quark (halbfett, 20% sollte genügen)&lt;br /&gt;
*Tacos-Salse-Soße für die Burritos (gerne scharf)&lt;br /&gt;
*10 Avocados&lt;br /&gt;
*Knoblauch&lt;br /&gt;
*Salz&lt;br /&gt;
*Pfeffer&lt;br /&gt;
*Rosmarin&lt;br /&gt;
*Basilikum&lt;br /&gt;
*Paprika-Gewürz (scharf)&lt;br /&gt;
 &lt;br /&gt;
==== Früh und Mittags ====&lt;br /&gt;
'' Wird von X &amp;amp; Y eingekauft''&lt;br /&gt;
*Obst (Bananen, Äpfel, Orangen, Mandarinen) &lt;br /&gt;
*3 Gurken &lt;br /&gt;
*einige Tomaten (für die Brotzeit) &lt;br /&gt;
*3 Butter &lt;br /&gt;
*2-3kg Wurst &amp;amp; Käseaufschnitt (eine gute Auswahl halt :-)) &lt;br /&gt;
*Obstriegel &lt;br /&gt;
*Frischkäse (natur und Kräuter)&lt;br /&gt;
*Essiggurken &lt;br /&gt;
*mehr Marmelade (Himbeer und Hagebutte) &lt;br /&gt;
*Nutella &lt;br /&gt;
*kernige Haferflocken (für Porridge)&lt;br /&gt;
*Honig &lt;br /&gt;
*30 Eier (Freilandhaltung!!!)&lt;br /&gt;
*Auswahl an Müsli-Riegel / Snickers&lt;br /&gt;
&lt;br /&gt;
====Allgemeines ====&lt;br /&gt;
'' Wird von X &amp;amp; Y eingekauft''&lt;br /&gt;
*Spülmittel &lt;br /&gt;
*Spülschwamm &lt;br /&gt;
*Seife &lt;br /&gt;
*2 Packungen Kaffee (1 Pfund mittel- + 1 Pfund starker Kaffee)&lt;br /&gt;
*Tee (Earl Gray, Früchtetee) &lt;br /&gt;
*O-Saft &amp;amp; anderer Saft (&amp;gt; 10 Liter)&lt;br /&gt;
*10 Liter Milch &lt;br /&gt;
*2 Liter Sojamilch (Natur)&lt;br /&gt;
*Kaffeefilter&lt;br /&gt;
*Zucker&lt;br /&gt;
*Toilettenpapier / Küchenpapier (gibt es eigtl auch vor Ort von den Putzfrauen)&lt;br /&gt;
*Müllsäcke &lt;br /&gt;
*Lappen &lt;br /&gt;
*Spülmaschinen Tabs&lt;br /&gt;
  &lt;br /&gt;
==== Persönliches ====&lt;br /&gt;
Bitte bringt mit was ihr selbst gerne esst, aber schreibt es trotzdem hier rein (kann dann von mir aus auch gerne am Schluss abgerechnet werden)&lt;br /&gt;
* '' bitte hier persönliches, wie z.B. Süßigkeiten, etc. auflisten''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Alkohol/Party ===&lt;br /&gt;
Wir werden dieses mal sicher wieder feiern und dafür sollten wir auch vorsorgen :)&lt;br /&gt;
Vorschlag: jeder bringt mit, was er/sie gern möchte mit Vermerk im Wiki?!&lt;br /&gt;
* '' bitte hier Alkohol auflisten''&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
=== Spiele ===&lt;br /&gt;
 &lt;br /&gt;
Immer lustig sind gemeinsame Spieleabende. Also, wer im Besitz von Gesellschaftsspielen ist, bringt diese gerne mit! Um eine Übersicht zu bekommen auch bitte hier eintragen:&lt;br /&gt;
*''bitte hier Spiele auflisten''&lt;br /&gt;
&lt;br /&gt;
=== Sonstiges ===&lt;br /&gt;
* Audiokabel für Anschluss Laptop - Aux-Anschluss Stereoanlage '''wer hat sowas?'''&lt;br /&gt;
&lt;br /&gt;
=== Alternativprogramm ===&lt;br /&gt;
  *  Rodeln (http://www.montafon.at/de/urlaubswelten/echte_naturliebhaber/rodeln)&lt;br /&gt;
  *  Schneeschuhwandern (http://www.montafon.at/schneeschuhwanderungen)&lt;br /&gt;
  *  Therme (http://www.montafon.at/schwimmen), z.B. http://www.aqua-dome.at/de (ca. 130km entfernt!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Category:Tools&amp;diff=1467</id>
		<title>Category:Tools</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Category:Tools&amp;diff=1467"/>
		<updated>2018-05-03T07:54:14Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;What tools to use and how to use them best&lt;br /&gt;
&lt;br /&gt;
* Shells&lt;br /&gt;
** Bash&lt;br /&gt;
** [[TcShell]]&lt;br /&gt;
* [[Editors]]&lt;br /&gt;
** [[Editors#EMACS|Emacs]]&lt;br /&gt;
** [[Editors#JED|Jed]]&lt;br /&gt;
** [[Editors#VI|Vi]]&lt;br /&gt;
** [[Slang-mode|Slang-Mode]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Software]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Category:Tools&amp;diff=1466</id>
		<title>Category:Tools</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Category:Tools&amp;diff=1466"/>
		<updated>2018-05-03T07:53:34Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;What tools to use and how to use them best&lt;br /&gt;
&lt;br /&gt;
* Shells&lt;br /&gt;
** Bash&lt;br /&gt;
** [[TcShell]]&lt;br /&gt;
* [[Editors]]&lt;br /&gt;
** [[Editors#EMACS|Emacs]]&lt;br /&gt;
** [[Editors#JED|Jed]]&lt;br /&gt;
** [[Editors#VI|Vi]]&lt;br /&gt;
** [[Editors#Slang-mode|Slang-Mode]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Software]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Lab_course_equipment&amp;diff=1402</id>
		<title>Lab course equipment</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Lab_course_equipment&amp;diff=1402"/>
		<updated>2018-05-02T11:11:07Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: Created page with &amp;quot;====== Overview over lab course equipment ======  * Meridian building - Radio room * intern:equipment:basement:start|Main building - Basement (U1.105...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====== Overview over lab course equipment ======&lt;br /&gt;
&lt;br /&gt;
* [[Observing_equipment|Meridian building - Radio room]]&lt;br /&gt;
* [[intern:equipment:basement:start|Main building - Basement (U1.105)]]&lt;br /&gt;
* [[intern:equipment:1stfloor:start|Main building - 1st floor (1.105)]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Current Members]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Observing_equipment&amp;diff=1400</id>
		<title>Observing equipment</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Observing_equipment&amp;diff=1400"/>
		<updated>2018-05-02T11:08:24Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: Created page with &amp;quot;#  Koffer Zubehör 60cm Teleskop #  Koffer Zubehör 40cm Teleskop # SBIG ST11000M #  Koffer Filter und Reinigungsmaterial # Fernglas  Categor...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;# [[60cm | Koffer Zubehör 60cm Teleskop]]&lt;br /&gt;
# [[40cm | Koffer Zubehör 40cm Teleskop]]&lt;br /&gt;
# SBIG ST11000M&lt;br /&gt;
# [[filter | Koffer Filter und Reinigungsmaterial]]&lt;br /&gt;
# Fernglas&lt;br /&gt;
&lt;br /&gt;
[[Category:Current Members]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Filter&amp;diff=1397</id>
		<title>Filter</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Filter&amp;diff=1397"/>
		<updated>2018-05-02T11:04:22Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====== Filter / Reinigung ======&lt;br /&gt;
Beschreibung: Koffer: klein (blau)&lt;br /&gt;
* Schmallbandfilter&lt;br /&gt;
* Breitbandfilter&lt;br /&gt;
* Reinigungstücher&lt;br /&gt;
* Pinsel&lt;br /&gt;
* Reinigungsflüssigkeit Optical Wonder&lt;br /&gt;
* Blasebalg&lt;br /&gt;
* etc.&lt;br /&gt;
&lt;br /&gt;
[[Category:Current Members]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=60cm&amp;diff=1396</id>
		<title>60cm</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=60cm&amp;diff=1396"/>
		<updated>2018-05-02T11:04:03Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====== Zubehör 60cm Teleskop ======&lt;br /&gt;
Beschreibung: Koffer: gross (silber)&lt;br /&gt;
&lt;br /&gt;
* Zenitspiegel&lt;br /&gt;
* 2” Okular Williams Optics UWAN 28mm&lt;br /&gt;
* 1 1/4” Okular  Williams Optics UWAN 16mm&lt;br /&gt;
* Adapter 2” nach 1 1/4”&lt;br /&gt;
* Adapter 2” nach T2&lt;br /&gt;
* zwei weitere Adapterringe&lt;br /&gt;
* 3 alte Okulare&lt;br /&gt;
&lt;br /&gt;
[[Category:Current Members]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=40cm&amp;diff=1395</id>
		<title>40cm</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=40cm&amp;diff=1395"/>
		<updated>2018-05-02T11:03:40Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====== Zubehör 40cm Teleskop ======&lt;br /&gt;
Beschreibung: Koffer: gross (schwarz)&lt;br /&gt;
* Zoomokular Baader 8-24mm&lt;br /&gt;
* Planetenokular Williams optics UWAN 4mm&lt;br /&gt;
* Okular Televue 55mm&lt;br /&gt;
* Zenitspiegel&lt;br /&gt;
* Barlowlinse &lt;br /&gt;
* Shapleylinse&lt;br /&gt;
* Adapter 2” auf T2&lt;br /&gt;
* Baader Adapter 2” auf T2 (2408151)&lt;br /&gt;
* Adapter 2” auf 1 1/4”&lt;br /&gt;
* Baader Clicklock 2” auf T2 mit Verlängerung (2458100)&lt;br /&gt;
* SBIG e-Finder f 5.85/3.85 mit Verlängerung 1 1/4”&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Current Members]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Filter&amp;diff=1391</id>
		<title>Filter</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Filter&amp;diff=1391"/>
		<updated>2018-05-02T10:49:43Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: Created page with &amp;quot;====== Filter / Reinigung ====== Beschreibung: Koffer: klein (blau) * Schmallbandfilter * Breitbandfilter * Reinigungstücher * Pinsel * Reinigungsflüssigkeit Optical Wonder...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====== Filter / Reinigung ======&lt;br /&gt;
Beschreibung: Koffer: klein (blau)&lt;br /&gt;
* Schmallbandfilter&lt;br /&gt;
* Breitbandfilter&lt;br /&gt;
* Reinigungstücher&lt;br /&gt;
* Pinsel&lt;br /&gt;
* Reinigungsflüssigkeit Optical Wonder&lt;br /&gt;
* Blasebalg&lt;br /&gt;
* etc.&lt;br /&gt;
&lt;br /&gt;
[[Category:Observatory]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=60cm&amp;diff=1390</id>
		<title>60cm</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=60cm&amp;diff=1390"/>
		<updated>2018-05-02T10:48:15Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: Created page with &amp;quot;====== Zubehör 60cm Teleskop ====== Beschreibung: Koffer: gross (silber)  * Zenitspiegel * 2” Okular Williams Optics UWAN 28mm * 1 1/4” Okular  Williams Optics UWAN 16mm...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====== Zubehör 60cm Teleskop ======&lt;br /&gt;
Beschreibung: Koffer: gross (silber)&lt;br /&gt;
&lt;br /&gt;
* Zenitspiegel&lt;br /&gt;
* 2” Okular Williams Optics UWAN 28mm&lt;br /&gt;
* 1 1/4” Okular  Williams Optics UWAN 16mm&lt;br /&gt;
* Adapter 2” nach 1 1/4”&lt;br /&gt;
* Adapter 2” nach T2&lt;br /&gt;
* zwei weitere Adapterringe&lt;br /&gt;
* 3 alte Okulare&lt;br /&gt;
&lt;br /&gt;
[[Category:Observatory]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=40cm&amp;diff=1389</id>
		<title>40cm</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=40cm&amp;diff=1389"/>
		<updated>2018-05-02T10:46:53Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: Created page with &amp;quot;====== Zubehör 40cm Teleskop ====== Beschreibung: Koffer: gross (schwarz) * Zoomokular Baader 8-24mm * Planetenokular Williams optics UWAN 4mm * Okular Televue 55mm * Zenitsp...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====== Zubehör 40cm Teleskop ======&lt;br /&gt;
Beschreibung: Koffer: gross (schwarz)&lt;br /&gt;
* Zoomokular Baader 8-24mm&lt;br /&gt;
* Planetenokular Williams optics UWAN 4mm&lt;br /&gt;
* Okular Televue 55mm&lt;br /&gt;
* Zenitspiegel&lt;br /&gt;
* Barlowlinse &lt;br /&gt;
* Shapleylinse&lt;br /&gt;
* Adapter 2” auf T2&lt;br /&gt;
* Baader Adapter 2” auf T2 (2408151)&lt;br /&gt;
* Adapter 2” auf 1 1/4”&lt;br /&gt;
* Baader Clicklock 2” auf T2 mit Verlängerung (2458100)&lt;br /&gt;
* SBIG e-Finder f 5.85/3.85 mit Verlängerung 1 1/4”&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Observatory]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Xmm&amp;diff=727</id>
		<title>Xmm</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Xmm&amp;diff=727"/>
		<updated>2018-04-11T13:14:43Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== XMM Data Extraction ======&lt;br /&gt;
&lt;br /&gt;
After the system got updated from Ubuntu 11 to Ubuntu 12 a problem occured with the function &amp;quot;dssetattr&amp;quot; inside the &amp;quot;epchain&amp;quot;.&lt;br /&gt;
This function can set/add an attribute to the HDU (Header/Data Unit).&lt;br /&gt;
The solution is to call &lt;br /&gt;
''''source $SOFTDIR/sas_init.csh''''&lt;br /&gt;
at the beginning of each script in order to initialize SAS inside your script.&lt;br /&gt;
&lt;br /&gt;
A little example script:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
     #!/bin/csh                                        &lt;br /&gt;
     source $SOFTDIR/sas_init.csh     # initialize the SAS software &lt;br /&gt;
     set xmmscripts = ${XMMTOOLS}    # make sure the proper xmmscripts are loaded&lt;br /&gt;
     &lt;br /&gt;
     set obsid = '0147190101'&lt;br /&gt;
     set datadir = /eu/X-ray/XMM/data/????/$obsid/odf&lt;br /&gt;
     &lt;br /&gt;
     ${xmmscripts}/xmmprepare --datadir=$datadir --prepdir=$obsid --pn                     # prepare the data&lt;br /&gt;
     ${xmmscripts}/xmmextract --prepdir=$obsid --pn --full                                 # full extraction of the chip&lt;br /&gt;
     ${xmmscripts}/xmmextract --prepdir=$obsid --pn --srcreg=src.fits --bkgreg=bkg.fits    # source and background extraction of the chip&lt;br /&gt;
     &lt;br /&gt;
note that it is usually better to have the data preparation and the extraction in separate scripts (since one usually prepares once and then tries several extractions with different settings).&lt;br /&gt;
The xmmscripts need the region files to be fits files. You can convert them via&lt;br /&gt;
     ds9tocxc outset=outfilename.fits &amp;lt; infilename.reg&lt;br /&gt;
&lt;br /&gt;
==== Workaround for the xmmscripts ====&lt;br /&gt;
There were some problems occuring with the XMM-data extraction. Joern has implemented a workaround in the xmmscripts that has to be called as shown in the example below.&lt;br /&gt;
Here the issues:&lt;br /&gt;
# If your observation includes sub-observations, choose one of them. Do this with &amp;quot;onlyexp=1&amp;quot; not &amp;quot;onlyexp=PNU001&amp;quot; for example.&lt;br /&gt;
# Since our Calibration database gets updated frequently, we ran into the problem that new calibration files only like the latest SAS. As it is very problematic to just install the new SAS, there is a workaround. You have to address the calibration files that are working with our SAS version until the new SAS is installed (we must be patient as this is not trivial). The following, however, works perfectly:&lt;br /&gt;
&lt;br /&gt;
example:&lt;br /&gt;
&lt;br /&gt;
     #!/bin/csh&lt;br /&gt;
     setenv XMMTOOLS /home/wilms/xmmscripts&lt;br /&gt;
     source ~wilms/progmapper15/progmapper.csh&lt;br /&gt;
     ${XMMTOOLS}/xmmprepare --datadir=/eu/X-ray/XMM/data/2290/0679780201/odf/ &lt;br /&gt;
     --prepdir=./test --pn --analysisdate=2014-01-11T01:05:00.000&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== XMM OM Data Extraction ======&lt;br /&gt;
&lt;br /&gt;
For extracting the data of the Optical Monitor (OM) onboard XMM, there exist three tools which do this automatically: ''omichain'', ''omfchain'' and ''omgchain''.&lt;br /&gt;
&amp;quot;i&amp;quot; stands for image mode, &amp;quot;f&amp;quot; for fast mode and &amp;quot;g&amp;quot; for grism mode. Which mode you have can be found on the XMM log browse site: http://xmm2.esac.esa.int/external/xmm_obs_info/obs_view_frame.shtml.&lt;br /&gt;
If you want to extract your images you first have to set some paths:&lt;br /&gt;
&lt;br /&gt;
     $source $SOFTDIR/sas_init.csh &lt;br /&gt;
     $setenv SAS_ODF path_to_your_data   #normally /eu/X-ray/XMM/data/rev/ObsID/odf/&lt;br /&gt;
     $cifbuild&lt;br /&gt;
     $setenv SAS_CCF ccf.cif&lt;br /&gt;
     $odfingest&lt;br /&gt;
     $setenv SAS_ODF `ls -1 *SUM.SAS`&lt;br /&gt;
&lt;br /&gt;
After this you can run&lt;br /&gt;
     &lt;br /&gt;
     $omichain   #or omfchain, omgchain&lt;br /&gt;
     &lt;br /&gt;
You can also do the extraction step-by-step. For a description see http://xmm.esac.esa.int/sas/current/documentation/threads/omi_stepbystep.shtml.&lt;br /&gt;
At the end you should have several images (&amp;lt;code&amp;gt;*IMAGE*&amp;lt;/code&amp;gt;), region files (&amp;lt;code&amp;gt;*REGION*&amp;lt;/code&amp;gt;) and source lists (&amp;lt;code&amp;gt;*SWSRLI*&amp;lt;/code&amp;gt;) for the OM exposures and filters. The nomenclatur for the files are:   &lt;br /&gt;
&lt;br /&gt;
* IOOOOOOOOOODDUEEETTTTTTSXXX.FFF or POOOOOOOOOODDUEEETTTTTTSXXX.FFF (for PPS product files)&lt;br /&gt;
* OOOOOOOOOO = XMM-ObsID (10 characters)&lt;br /&gt;
* DD = Data source idetifier (here OM)&lt;br /&gt;
* U = exposure flag (S = sched, U = unsched, X = not aplicable)&lt;br /&gt;
* EEE = exposure number within the instrument observation (3 characters)&lt;br /&gt;
* TTTTTT = product type (6 characters)&lt;br /&gt;
* S = 0 or data subset number/character&lt;br /&gt;
* XXX = source number or slew step number (3 characters)&lt;br /&gt;
* FFF = file format (3 characters)&lt;br /&gt;
&lt;br /&gt;
From all exposures for one filter a mosaiced sky image is produced which contains *SIMAG?.FIT. The ? stands for the filter: L = UVW1, M = UVM2, S = UVW2, B = B, U = U, V = V. &lt;br /&gt;
Open the image with ds9 and have a look if your source is seen and where it is. You can check this by loading a region file, produced e.g. by simbad2ds9, into the image. &lt;br /&gt;
&lt;br /&gt;
Then check the detector images (&amp;lt;code&amp;gt;P*IMAGE_*000.FIT&amp;lt;/code&amp;gt;) for your source (it can be, that some detector images don't contain your source because the window was off). Load the region file which belongs to the detector image (&amp;lt;code&amp;gt;*REGION*000.ASC&amp;lt;/code&amp;gt;, e.g. &amp;lt;code&amp;gt;P0090050801OMS006IMAGE_0000.FIT&amp;lt;/code&amp;gt; -&amp;gt; ''I0090050801OMS006REGION0000.ASC&amp;lt;/code&amp;gt;) and identify the number of your source. &lt;br /&gt;
&lt;br /&gt;
[[File:image_region.jpeg|thumb]]&lt;br /&gt;
&lt;br /&gt;
Look into the source list for your exposure (&amp;lt;code&amp;gt;P*SWSRLI*.FIT&amp;lt;/code&amp;gt;) and note the SRC_ID in the last column. Open the combined source list (&amp;lt;code&amp;gt;*COMBO*&amp;lt;/code&amp;gt;) and search for your SRC_ID. Here you can find all the magnitudes and fluxes of your source for the different filters.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== Choosing correct XMM-EPIC filter ======&lt;br /&gt;
&lt;br /&gt;
Choosing the correct EPIC filter for your observation depends on the&lt;br /&gt;
visual magnitudes of the other objects (usually stars) in the EPIC&lt;br /&gt;
field of view.&lt;br /&gt;
&lt;br /&gt;
The XMM user's handbook (sect. 3.3.6; &lt;br /&gt;
http://xmm.esac.esa.int/external/xmm_user_support/documentation/uhb/epicfilters.html) recommends:&lt;br /&gt;
&lt;br /&gt;
Thick filter:  suppress up to magnitudes of  -2 to -1 (pn), or +1 to +4 (mos)&lt;br /&gt;
&lt;br /&gt;
Medium filter: if there is nothing above magnitude ~ 6 to 9&lt;br /&gt;
&lt;br /&gt;
Thin filter:   for point sources that are 12 mag fainter than thick filter limitations&lt;br /&gt;
&lt;br /&gt;
The UHB notes that these magnitudes apply when you use the full frame mode; if you use a partial window mode, then sources up to 2-3 magnitudes brighter than these values should be okay.&lt;br /&gt;
 &lt;br /&gt;
Use the United States Naval Observatory catalog at&lt;br /&gt;
http://www.nofs.navy.mil/data/fchpix/ to find the stars within a 9'&lt;br /&gt;
radius.&lt;br /&gt;
&lt;br /&gt;
At that website, enter your R.A. and Decl., and for the output file&lt;br /&gt;
options in the left column, unclick everything except RA,DEC,&lt;br /&gt;
magnitude, and offset from center.  Then click 'retrieve data' in the&lt;br /&gt;
right column.&lt;br /&gt;
&lt;br /&gt;
Next window: Click on &amp;quot;USNO B1.0 Star List&amp;quot; to download a gzipped&lt;br /&gt;
ASCII file with typically hundreds of rows/stars for lines of sight&lt;br /&gt;
away from the Galactic Plane (or many thousands of rows/stars for&lt;br /&gt;
lines of sight in the Galactic Plane).&lt;br /&gt;
&lt;br /&gt;
Example file: See /home/markowitz/proposals/xmm2014/GS1826USNO for a&lt;br /&gt;
Galactic XRB, GS1826, located in the Galactic Bulge (optically-crowded&lt;br /&gt;
fields).&lt;br /&gt;
&lt;br /&gt;
The star list is ordered by R.A., and but you can then re-order the ASCII list &lt;br /&gt;
by magnitude, e.g.,&lt;br /&gt;
&lt;br /&gt;
 cat GS1826USNO | grep -v '#' | awk '{print $7 &amp;quot;  &amp;quot; $12}' | sort -g &amp;gt;   starlist_sortB&lt;br /&gt;
 cat GS1826USNO | grep -v '#' | awk '{print $8 &amp;quot;  &amp;quot; $12}' | sort -g &amp;gt;   starlist_sortR&lt;br /&gt;
&lt;br /&gt;
since the B and R magnitudes are columns 7 and 8, and distance from the center&lt;br /&gt;
of f.o.v. (in arcsec) is column 12&lt;br /&gt;
&lt;br /&gt;
Ignore the rows with zero magnitudes; a zero means unmeasured flux.&lt;br /&gt;
&lt;br /&gt;
For these example files, e.g., /home/markowitz/proposals/xmm2014/starlist_sortB&lt;br /&gt;
we see that the brightest B- and R-band magnitudes are 10.0-10.3, including some&lt;br /&gt;
objects that are only 3-5' from the center, and at least one that's only 1.2'&lt;br /&gt;
from the center, so one cannot use the thin epic filter; one must use&lt;br /&gt;
the MEDIUM filter for all three EPIC cameras.&lt;br /&gt;
&lt;br /&gt;
[[Category:Data Extraction]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Xmm&amp;diff=721</id>
		<title>Xmm</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Xmm&amp;diff=721"/>
		<updated>2018-04-11T13:04:18Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: Created page with &amp;quot; ====== XMM Data Extraction ======  After the system got updated from Ubuntu 11 to Ubuntu 12 a problem occured with the function &amp;quot;dssetattr&amp;quot; inside the &amp;quot;epchain&amp;quot;. This functio...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== XMM Data Extraction ======&lt;br /&gt;
&lt;br /&gt;
After the system got updated from Ubuntu 11 to Ubuntu 12 a problem occured with the function &amp;quot;dssetattr&amp;quot; inside the &amp;quot;epchain&amp;quot;.&lt;br /&gt;
This function can set/add an attribute to the HDU (Header/Data Unit).&lt;br /&gt;
The solution is to call &lt;br /&gt;
**'source $SOFTDIR/sas_init.csh'**&lt;br /&gt;
at the beginning of each script in order to initialize SAS inside your script.&lt;br /&gt;
&lt;br /&gt;
A little example script:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
     #!/bin/csh                                        &lt;br /&gt;
     source $SOFTDIR/sas_init.csh     # initialize the SAS software &lt;br /&gt;
     set xmmscripts = ${XMMTOOLS}    # make sure the proper xmmscripts are loaded&lt;br /&gt;
     &lt;br /&gt;
     set obsid = '0147190101'&lt;br /&gt;
     set datadir = /eu/X-ray/XMM/data/????/$obsid/odf&lt;br /&gt;
     &lt;br /&gt;
     ${xmmscripts}/xmmprepare --datadir=$datadir --prepdir=$obsid --pn                     # prepare the data&lt;br /&gt;
     ${xmmscripts}/xmmextract --prepdir=$obsid --pn --full                                 # full extraction of the chip&lt;br /&gt;
     ${xmmscripts}/xmmextract --prepdir=$obsid --pn --srcreg=src.fits --bkgreg=bkg.fits    # source and background extraction of the chip&lt;br /&gt;
     &lt;br /&gt;
note that it is usually better to have the data preparation and the extraction in separate scripts (since one usually prepares once and then tries several extractions with different settings).&lt;br /&gt;
The xmmscripts need the region files to be fits files. You can convert them via&lt;br /&gt;
     ds9tocxc outset=outfilename.fits &amp;lt; infilename.reg&lt;br /&gt;
&lt;br /&gt;
==== Workaround for the xmmscripts ====&lt;br /&gt;
There were some problems occuring with the XMM-data extraction. Joern has implemented a workaround in the xmmscripts that has to be called as shown in the example below.&lt;br /&gt;
Here the issues:&lt;br /&gt;
  - If your observation includes sub-observations, choose one of them. Do this with &amp;quot;onlyexp=1&amp;quot; not &amp;quot;onlyexp=PNU001&amp;quot; for example.&lt;br /&gt;
  - Since our Calibration database gets updated frequently, we ran into the problem that new calibration files only like the latest SAS. As it is very problematic to just install the new SAS, there is a workaround. You have to address the calibration files that are working with our SAS version until the new SAS is installed (we must be patient as this is not trivial). The following, however, works perfectly:&lt;br /&gt;
&lt;br /&gt;
example:&lt;br /&gt;
&lt;br /&gt;
     #!/bin/csh&lt;br /&gt;
     setenv XMMTOOLS /home/wilms/xmmscripts&lt;br /&gt;
     source ~wilms/progmapper15/progmapper.csh&lt;br /&gt;
     ${XMMTOOLS}/xmmprepare --datadir=/eu/X-ray/XMM/data/2290/0679780201/odf/ &lt;br /&gt;
     --prepdir=./test --pn --analysisdate=2014-01-11T01:05:00.000&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== XMM OM Data Extraction ======&lt;br /&gt;
&lt;br /&gt;
For extracting the data of the Optical Monitor (OM) onboard XMM, there exist three tools which do this automatically: ''omichain'', ''omfchain'' and ''omgchain''.&lt;br /&gt;
&amp;quot;i&amp;quot; stands for image mode, &amp;quot;f&amp;quot; for fast mode and &amp;quot;g&amp;quot; for grism mode. Which mode you have can be found on the XMM log browse site: [[http://xmm2.esac.esa.int/external/xmm_obs_info/obs_view_frame.shtml]].&lt;br /&gt;
If you want to extract your images you first have to set some paths:&lt;br /&gt;
&lt;br /&gt;
     $source $SOFTDIR/sas_init.csh &lt;br /&gt;
     $setenv SAS_ODF path_to_your_data   #normally /eu/X-ray/XMM/data/rev/ObsID/odf/&lt;br /&gt;
     $cifbuild&lt;br /&gt;
     $setenv SAS_CCF ccf.cif&lt;br /&gt;
     $odfingest&lt;br /&gt;
     $setenv SAS_ODF `ls -1 *SUM.SAS`&lt;br /&gt;
&lt;br /&gt;
After this you can run&lt;br /&gt;
     &lt;br /&gt;
     $omichain   #or omfchain, omgchain&lt;br /&gt;
     &lt;br /&gt;
You can also do the extraction step-by-step. For a description see [[http://xmm.esac.esa.int/sas/current/documentation/threads/omi_stepbystep.shtml]].&lt;br /&gt;
At the end you should have several images (''*IMAGE*''), region files (''*REGION*'') and source lists (''*SWSRLI*'') for the OM exposures and filters. The nomenclatur for the files are:   &lt;br /&gt;
&lt;br /&gt;
   * IOOOOOOOOOODDUEEETTTTTTSXXX.FFF or POOOOOOOOOODDUEEETTTTTTSXXX.FFF (for PPS product files)&lt;br /&gt;
   * OOOOOOOOOO = XMM-ObsID (10 characters)&lt;br /&gt;
   * DD = Data source idetifier (here OM)&lt;br /&gt;
   * U = exposure flag (S = sched, U = unsched, X = not aplicable)&lt;br /&gt;
   * EEE = exposure number within the instrument observation (3 characters)&lt;br /&gt;
   * TTTTTT = product type (6 characters)&lt;br /&gt;
   * S = 0 or data subset number/character&lt;br /&gt;
   * XXX = source number or slew step number (3 characters)&lt;br /&gt;
   * FFF = file format (3 characters)&lt;br /&gt;
&lt;br /&gt;
From all exposures for one filter a mosaiced sky image is produced which contains ''*SIMAG?.FIT''. The ? stands for the filter: L = UVW1, M = UVM2, S = UVW2, B = B, U = U, V = V. &lt;br /&gt;
Open the image with ds9 and have a look if your source is seen and where it is. You can check this by loading a region file, produced e.g. by simbad2ds9, into the image. &lt;br /&gt;
&lt;br /&gt;
Then check the detector images (''P*IMAGE_*000.FIT'') for your source (it can be, that some detector images don't contain your source because the window was off). Load the region file which belongs to the detector image (''*REGION*000.ASC'', e.g. ''P0090050801OMS006IMAGE_0000.FIT'' -&amp;gt; ''I0090050801OMS006REGION0000.ASC'') and identify the number of your source. &lt;br /&gt;
&lt;br /&gt;
{{:satext:image_region.jpeg?200|}}&lt;br /&gt;
&lt;br /&gt;
Look into the source list for your exposure (''P*SWSRLI*.FIT'') and note the SRC_ID in the last column. Open the combined source list (''*COMBO*'') and search for your SRC_ID. Here you can find all the magnitudes and fluxes of your source for the different filters.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== Choosing correct XMM-EPIC filter ======&lt;br /&gt;
&lt;br /&gt;
Choosing the correct EPIC filter for your observation depends on the&lt;br /&gt;
visual magnitudes of the other objects (usually stars) in the EPIC&lt;br /&gt;
field of view.&lt;br /&gt;
&lt;br /&gt;
The XMM user's handbook (sect. 3.3.6; &lt;br /&gt;
http://xmm.esac.esa.int/external/xmm_user_support/documentation/uhb/epicfilters.html) recommends:&lt;br /&gt;
&lt;br /&gt;
Thick filter:  suppress up to magnitudes of  -2 to -1 (pn), or +1 to +4 (mos)&lt;br /&gt;
&lt;br /&gt;
Medium filter: if there is nothing above magnitude ~ 6 to 9&lt;br /&gt;
&lt;br /&gt;
Thin filter:   for point sources that are 12 mag fainter than thick filter limitations&lt;br /&gt;
&lt;br /&gt;
The UHB notes that these magnitudes apply when you use the full frame mode; if you use a partial window mode, then sources up to 2-3 magnitudes brighter than these values should be okay.&lt;br /&gt;
 &lt;br /&gt;
Use the United States Naval Observatory catalog at&lt;br /&gt;
http://www.nofs.navy.mil/data/fchpix/ to find the stars within a 9'&lt;br /&gt;
radius.&lt;br /&gt;
&lt;br /&gt;
At that website, enter your R.A. and Decl., and for the output file&lt;br /&gt;
options in the left column, unclick everything except RA,DEC,&lt;br /&gt;
magnitude, and offset from center.  Then click 'retrieve data' in the&lt;br /&gt;
right column.&lt;br /&gt;
&lt;br /&gt;
Next window: Click on &amp;quot;USNO B1.0 Star List&amp;quot; to download a gzipped&lt;br /&gt;
ASCII file with typically hundreds of rows/stars for lines of sight&lt;br /&gt;
away from the Galactic Plane (or many thousands of rows/stars for&lt;br /&gt;
lines of sight in the Galactic Plane).&lt;br /&gt;
&lt;br /&gt;
Example file: See /home/markowitz/proposals/xmm2014/GS1826USNO for a&lt;br /&gt;
Galactic XRB, GS1826, located in the Galactic Bulge (optically-crowded&lt;br /&gt;
fields).&lt;br /&gt;
&lt;br /&gt;
The star list is ordered by R.A., and but you can then re-order the ASCII list &lt;br /&gt;
by magnitude, e.g.,&lt;br /&gt;
&lt;br /&gt;
cat GS1826USNO | grep -v '#' | awk '{print $7 &amp;quot;  &amp;quot; $12}' | sort -g &amp;gt;   starlist_sortB&lt;br /&gt;
&lt;br /&gt;
cat GS1826USNO | grep -v '#' | awk '{print $8 &amp;quot;  &amp;quot; $12}' | sort -g &amp;gt;   starlist_sortR&lt;br /&gt;
&lt;br /&gt;
since the B and R magnitudes are columns 7 and 8, and distance from the center&lt;br /&gt;
of f.o.v. (in arcsec) is column 12&lt;br /&gt;
&lt;br /&gt;
Ignore the rows with zero magnitudes; a zero means unmeasured flux.&lt;br /&gt;
&lt;br /&gt;
For these example files, e.g., /home/markowitz/proposals/xmm2014/starlist_sortB&lt;br /&gt;
we see that the brightest B- and R-band magnitudes are 10.0-10.3, including some&lt;br /&gt;
objects that are only 3-5' from the center, and at least one that's only 1.2'&lt;br /&gt;
from the center, so one cannot use the thin epic filter; one must use&lt;br /&gt;
the MEDIUM filter for all three EPIC cameras.&lt;br /&gt;
&lt;br /&gt;
[[Category:Data Extraction]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Swift&amp;diff=718</id>
		<title>Swift</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Swift&amp;diff=718"/>
		<updated>2018-04-11T12:56:40Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: Created page with &amp;quot;====== Swift extractions ======  Swift extraction scripts are written in perl. The help for each function can be called with functionname --help  ===== XRT =====  Use wrapper...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====== Swift extractions ======&lt;br /&gt;
&lt;br /&gt;
Swift extraction scripts are written in perl. The help for each function can be called with functionname --help&lt;br /&gt;
&lt;br /&gt;
===== XRT =====&lt;br /&gt;
&lt;br /&gt;
Use wrapper script by L. Barragan and J. Wilms, can be found at&lt;br /&gt;
$SWIFTTOOLS/xrtprepare and $SWIFTTOOLS/xrtextract.&lt;br /&gt;
&lt;br /&gt;
It is possible to use a second wrapper which extracts multiple observations at once. Example:&lt;br /&gt;
/userdata/data/krauss/tanami/xrt/allprep and allex&lt;br /&gt;
This wrapper also automatically sets a source region and background region for extraction. Radius can be checked and adjusted and the script rerun.&lt;br /&gt;
&lt;br /&gt;
===== UVOT =====&lt;br /&gt;
&lt;br /&gt;
Use wrapper scripts by F. Krauss at $SWIFTTOOLS/uvotimage and $SWIFTTOOLS/uvotpha.&lt;br /&gt;
It is possible to use a second wrapper which extracts multiple observations at once. Example:&lt;br /&gt;
/userdata/data/krauss/tanami/uvot/allsum and allpha&lt;br /&gt;
&lt;br /&gt;
====== Useful tips ======&lt;br /&gt;
&lt;br /&gt;
* simbad2ds9: If you want to check for other possible source in the FoV use the simbad2ds9 tool, e.g. &amp;quot;simbad2ds9 --name=&amp;quot;Vela X-1&amp;quot; &amp;quot;: This will create a ds9 region file with all sources in the vicinity of the specified source. This can be helpful to avoid possible source confusion.&lt;br /&gt;
&lt;br /&gt;
====== Known Swift problems ======&lt;br /&gt;
&lt;br /&gt;
* For e-mails concerning missing Swift observations in the Remeis archive: Only a plain text file or list of observation IDs in the email is sufficient to start the download. It is not necessary to include source name, observation dates or any other information.&lt;br /&gt;
&lt;br /&gt;
===== XRT problems and what to do =====&lt;br /&gt;
&lt;br /&gt;
# Bug concerning observation target: &amp;quot;Source J0619-1140 not found in SIMBAD either.. please enter target coordinates manually via the tarra and tardec options&amp;quot; [It's a feature not a bug!] Swift observations always have a target, those are the coordinates the telescope was pointed at. These are not necessarily those of the source you're interested in. The Swift scripts check the target name and search for its coordinates in SIMBAD. The reason for this is a bug in the data generation pipeline that was only recently fixed and still affects observations. ''For some cryptic target names that are not found by SIMBAD the name or coordinates of the TARGET have to be given manually via --tarobj, OR via --tarra and --tardec'' If you are confident or if you have checked the target header coordinates you can disable this feature with --noco &lt;br /&gt;
# Bug occurring in the XRT pipeline: Occassionally a bug with a cryptic error message appears: &lt;br /&gt;
&amp;lt;blockquote&amp;gt;pc: .... Stage   I: Calibrating Level 1 Event File: /userdata/data/krauss/tanami/xrt/neutrinos100tev/ev39/CRATESJ061733.67-171522.8/00039134001/reprocessed/sw00039134001xpcw3po_uf.evt pc: .... Stage   I: ERROR ============================================================================================= xrtpipeline_0.13.2: ERROR: Pipeline exit with errors - Tue Jul 19 14:52:04 CEST 2016 ============================================================================================= =============================================================================================&amp;lt;/blockquote&amp;gt;  &lt;br /&gt;
'''and before:'''  &lt;br /&gt;
&amp;lt;blockquote&amp;gt;FITSIO status = 104: could not open the named file failed to find or open the following file: (ffopen) /userdata/data/krauss/tanami/xrt/neutrinos100tev/ev39/CRATESJ061733.67-171522.8/00039134001/reprocessed/sw00039134001xpcw3po_uf att_fatal: code=104 CFITSIO ERROR FILE_NOT_OPENED: could not open the named file Task coordinator 0.1 terminating with status 104 xrtpipeline_0.13.2: Error: running 'coordinator'&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
'''This error occurs when the full path of the file is too long (&amp;gt;48 characters). Choose a shorter path and rerun. If the long pathname is necessary, copy the final extraction into your subsubsubfolder or folderwithreallylongname.'''&lt;br /&gt;
# &amp;quot;Target Object found: PHOTON&amp;quot; and &amp;quot;no products foreseen for 'SLEW' data&amp;quot;:WARNING! This type of observation yields no errors! Check reprocessed folder, if it doesn't contain any file ending in &amp;quot;*po_uf*&amp;quot; only e.g. &amp;quot;*sl_uf&amp;quot; and &amp;quot;*st_uf*&amp;quot; this means that the satellite was only slewing during the observation. '''Skip this observation, it is not usable.'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== UVOT problems and what to do =====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
# &amp;quot;Checking ASPCORR ...     ASPCORR set to NONE...performing correcting coordinates ...&amp;quot; If aspect correction has not been applied the system will launch &amp;quot;uvotskycorr&amp;quot; which attempts to do the aspect correction by comparing the FoV with known stars. This can fail. If does so with: &amp;quot;aspcorr: not applying correction to any HDUs&amp;quot; and &amp;quot;uvotskycorr: no correction for m2471780312I&amp;quot; '''No known fix at the moment. If coordinates look ok perform a manual extraction via the Swift Tools uvotimsum and uvot2pha'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Data Extraction]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Suzaku&amp;diff=713</id>
		<title>Suzaku</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Suzaku&amp;diff=713"/>
		<updated>2018-04-11T12:45:56Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====== Suzaku Data Extraction ======&lt;br /&gt;
&lt;br /&gt;
Suzaku consists of four detectors:&lt;br /&gt;
* four XISs (X-ray Imaging Spectrometer, 0-3), useable energy range 1-9 keV&lt;br /&gt;
* PIN, useable energy range 12-60 keV&lt;br /&gt;
* GSO, useable energy range 57-300 keV&lt;br /&gt;
* XRS (X-ray Spectrometer), not useable since it failed after launch&lt;br /&gt;
PIN and GSO are mounted together within the HXD (Hard X-ray Detector). Unfortunately, XIS2 was hit by a micro meteorite in [http://www.astro.isas.jaxa.jp/suzaku/news/2006/1123/ 2006 November] and can no longer be used for analysis. A similar event happened to XIS0 in [http://www.astro.isas.jaxa.jp/suzaku/news/2009/0702/ July 2009], but the damage is much less such that data is still useable. Also note that XIS1 is back illuminated, while the other ones are front illuminated (causing a difference in the background level).&amp;lt;br \&amp;gt;&lt;br /&gt;
You might visit the [http://www.astro.isas.jaxa.jp/suzaku/news/ Suzaku News for Researches] to stay up to date about the current status of the satellite and instruments. For a detailed description please have a look on the [http://www.astro.isas.jaxa.jp/suzaku/doc/ Suzaku Documents], where you can also find the [http://www.astro.isas.jaxa.jp/suzaku/doc/suzaku_td/ Technical Description]. The extraction scripts introduced below are written by Laura Barragan, Joern Wilms, Felix Fuerst, et al. and basically follow the [http://heasarc.gsfc.nasa.gov/docs/suzaku/analysis/abc/abc.html Suzaku ABC Guide].&lt;br /&gt;
&lt;br /&gt;
Until some calibrations problems around the Si- and Au-edges are solved, the useable energy range of the XIS has to be modified slightly. According to [(:biblio:Nowak11a)] the following energy ranges should be ignored for all XIS:&lt;br /&gt;
  ignore_en(xis_datasets, 1.72, 1.88);&lt;br /&gt;
  ignore_en(xis_datasets, 2.19, 2.37);&lt;br /&gt;
For the back-illuminated XIS1, [(:biblio:Kuehnel13a)] had to exclude the energy range between both edges (1.88-2.19 keV) as well to get a consistent description compared to XIS0 and XIS3.&lt;br /&gt;
&lt;br /&gt;
===== Preparing the data =====&lt;br /&gt;
&lt;br /&gt;
First, apply the newest calibration to the rawdata:&lt;br /&gt;
  suzprepare --datadir path_to_raw_data --prepdir path_to_extraction --all&lt;br /&gt;
Thereby, ''datadir'' specifies the raw data directory, which you can find by, e.g., using the [[satext:findobs|findobs]] script. The ''prepdir'' argument sets the extraction directory and the last one tells the script to prepare the data for all instruments listed above. Other parameters are ''xisN'' with the XIS number N (0-3), ''pin'' or ''gso''.&lt;br /&gt;
For example:&lt;br /&gt;
  suzprepare --datadir /eu/X-ray/Suzaku/data/7/704063010 --predir `pwd`/ngc3783&lt;br /&gt;
In the extraction directory ''prepdir'' a subdirectory named ''reprocessed'' is created, where the event- and calibration-files are saved.&lt;br /&gt;
&lt;br /&gt;
== CALDB version ==&lt;br /&gt;
It is recommened to remember which version (which is a date-string) of the calibration database (CALDB) you've used for data preparation (you might want to add this information to your paper). You can use the following command to get the version installed at the '''date of calling''' this command:&lt;br /&gt;
  find $CALDB/data/suzaku/*/caldb.indx -print -exec readlink {} \;&lt;br /&gt;
That will print out the filename (with the version included) for the HXD, XIS, XRT (X-ray telescopes focusing onto the XISs), and XRS. If you haven't wrote down the versions right when you've extracted the data, it is more complicated to find out which versions were used. In that case you can match the different versions available in&lt;br /&gt;
  ls $CALDB/data/suzaku/*/index&lt;br /&gt;
against the creation date of your ''reprocessed''-directory.&lt;br /&gt;
&lt;br /&gt;
===== XIS =====&lt;br /&gt;
&lt;br /&gt;
==== Correcting the Attitude ====&lt;br /&gt;
&lt;br /&gt;
[[File:suz_extr_att.png|thumb|500px]]&lt;br /&gt;
The Attitude of the satellite is not known precisely, which causes the XIS-images to show an &amp;quot;image crater&amp;quot; or even two images of the source (see picture on the right). Therefore, a script named [http://space.mit.edu/CXC/software/suzaku/aeatt.html aeattcor2] was developed to correct the satellites attitude by using an image of the source. This tool is already included in the ''xisextract'' extraction script.&lt;br /&gt;
&lt;br /&gt;
[[File:suz_extr_att_region.png|thumb|500px]]&lt;br /&gt;
To correct the attitude using ''xisextract'' one needs to create a regionfile (by using, e.g., DS9) in WCS-coordinates containing a '''single''' and '''simple''' circle marking the source (see picture on the left). The radius of the circle should be around 90 arcsec. As an image, we open one of the cleaned event files ae{obsid}xi*_cl.evt located in the ''reprocessed'' directory. Furthermore, its worth to have a look on the unfiltered events *_uf.evt in case the filtered image looks weird. Here, we name the regionfile ''att_src.reg'' and save it in the ''prepdir'' directory.&lt;br /&gt;
&lt;br /&gt;
Now, we call ''xisextract'' for the first time to use the region created before for correcting the attitude:&lt;br /&gt;
  xisextract --prepdir ... --full --xis=N --attitude --srcreg=.../att_src.reg&lt;br /&gt;
&lt;br /&gt;
Providing the --full option will cause ''xisextract'' to extract a full image of the source (without any spectra or lightcurves). This will create the subdirectory ''full'' or ''full.att'' (in case of corrrecting the attitude as described here) in the ''prepdir'' direcotry. The --xis option has to be set to the number of the XIS (0-3), which means one has to execute the above command for all XISs. If --attitude is given, the script calles ''aeattcor2'' with the region file given with --srcreg. If successful, a folder called ''reprocessed.att'' will be created, which contains the corrected attitude and event files. If one looks on the *_sky.img images located within ''full.att'', the image creater should be suppressed or the two sources should have merged. Note that depending on the level of the wrong attitude the result might not be fully satisfying.&lt;br /&gt;
&lt;br /&gt;
'''Important note:''' in case the attitude correction fails the XISs were probably operated in the so-called burst mode. You can check the FITS header of the eventfiles to check on the clock mode (''normal'' or ''burst''):&lt;br /&gt;
  fkeyprint reprocessed/ae{obsid}xi*_cl.evt CLK_MODE&lt;br /&gt;
The burst mode causes a huge number of GTIs, which ''aeattcor2'' cannot handle. There is a workaround available which you can find below the next paragraph.&lt;br /&gt;
&lt;br /&gt;
== with aeattcor2 directly ==&lt;br /&gt;
For completeness and debugging purposes the attitude can be corrected directly using the ''aeattcor2'' tool:&lt;br /&gt;
  aeattcor2 attitude corrected_attitude events region&lt;br /&gt;
The old attitude file ae{obsid}.att (as created by ''suzprepare'') can be found in the ''reprocessed'' directory. The tool has to be called for at least one event file (e.g., that of XIS3 in 3x3 readout mode) to get a corrected attitude file. The region has to be the same as described above.&lt;br /&gt;
&lt;br /&gt;
=== Burst Mode ===&lt;br /&gt;
&lt;br /&gt;
If the XISs were operated in burst mode, an articifial dead time during each frame is introduced to reduce pile-up (for more detail see the [http://www.astro.isas.jaxa.jp/suzaku/doc/suzaku_td/node10.html#fig:xisoptfig Technical Manual]), which results in one GTI per frame. For instance given an observation with 40 ks total exposure time, operated in 1/4 window + 1 s burst option (exposure per frame is 2 s, from which 1 s is deadtime), the number of GTIs are around 40 ks / 2 s = 20000. That will cause ''aeattcor2'' to crash.&lt;br /&gt;
&lt;br /&gt;
Thus, in order to correct the attitude, we have to reduce the number of GTIs drastically. This can be achieved by using the --sloppygti option during the call of ''suzprepare'':&lt;br /&gt;
  suzprepare --datadir ... --prepdir ... --xis --sloppygti&lt;br /&gt;
Note, that we're providing the --xis options here. It's recommended to set the ''prepdir'' to another directory since the events during the deadtime are not supposed to account for a spectrum of lightcurve, of course.&lt;br /&gt;
&lt;br /&gt;
Once the data are prepared, proceed with the attitude correction as described above. As soon as there are attitude files for each XIS and mode, copy them to your original ''prepdir'' directory. There, run ''xisextract'' to correct the attitude, but provide the attitude files you've just got using the sloppy GTIs:&lt;br /&gt;
  xisextract --prepdir ... --full --xis=N --attitude --srcreg=.../att_src.reg --attitudefile ...&lt;br /&gt;
Note that you still need to set the source region, but since an attitude file is already given the call to ''aeattcor2'' will be skipped and the events are corrected using the given file instead.&lt;br /&gt;
&lt;br /&gt;
Finally, you may delete the ''prepdir'' directory of the --sloppygti preparation (and only '''that''').&lt;br /&gt;
&lt;br /&gt;
==== Source and Background Regions ====&lt;br /&gt;
&lt;br /&gt;
[[File:suz_extr_pilup.png|thumb|500px]]&lt;br /&gt;
Creating a source region for each XIS and read-out mode is more complicated due to pile-up. If two photons hit a pixel of the CCD at the same frame, they cannot be distinguished. During the read-out they look like a single photon with the sum of theire energies. Thus, a piled-up spectrum appears to be harder and flux in the soft energy range (&amp;lt; 5 keV) is missing (compare Figure on the right).&lt;br /&gt;
&lt;br /&gt;
To handle pile-up correctly, one has to estimate the probability for pile-up (the pile-up fraction) in each pixel for each XIS and mode. The resulting pile-up maps (of the source) are then used to create the extraction regions.&lt;br /&gt;
&lt;br /&gt;
The pile-up estimation is done by ''xisextract'' as well, which calls ''pileest'' internally. You can skip this call if you give the --nopileup option during the --full call to ''xisextract''. That means as soon as you have extracted the full images of the XIS you've automatically got the pile-up maps. They are located in the ''reprocessed.att'' directory and are named ae{obsid}xiN_*_pileup.img&lt;br /&gt;
There are pile-up maps for each XIS and mode, and you have to create source and background regions avoiding pile-up for all. Thus, the region filenames have to include the XIS and mode, of course.&lt;br /&gt;
&lt;br /&gt;
[[File:suz_extr_pilup_contour.png|thumb|500px]] Once you have opened a pile-up map with, e.g., DS9 the pixel value now represents the pile-up fraction instead of the number of counts. The easiest source region shape to take pile-up into account is an annulus with an outer radius of 90 arcsec. It's strongly recommended to use the same outer radius for '''all''' XIS and modes to get stable cross-calibration factors! The inner radius has to be determined such that within that radius the pile-up fraction is meanly below a certain value. Here, we suggest to skip regions with more than '''4%''' pile-up.&amp;lt;br \&amp;gt;&lt;br /&gt;
To speed up the determination of the inner radius, you can add the 4% (or whatever) contour to the image shown in DS9. Therefore, select the &amp;quot;Contour Parameters&amp;quot; item in the &amp;quot;Analysis&amp;quot; menue. In the new window, add the 0.04 level to the list on the right, delete all other levels, and set the smoothness to zero. After a click on &amp;quot;Apply&amp;quot; a contour will be drawn representing 4% pile-up fraction (see the black line in the example on the left). Now, it is easier to create the source region (see the example below).&lt;br /&gt;
&lt;br /&gt;
For the background regions no pile-up has to be considered (hopefully), such that their shape may be simple circles. Just move them to the borders of the chip or to another area outside of '''all''' sources.&lt;br /&gt;
&lt;br /&gt;
Save both, the source and background regions, as separate files. For example, xis3_3x3_src.reg and xis3_3x3_bkg.reg, respectively.&lt;br /&gt;
&lt;br /&gt;
[[File:suz_extr_src_reg.png|thumb|500px]][[File:suz_extr_bkg_reg.png|thumb|500px]]&amp;lt;br \&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Extracting spectra and lightcurves ====&lt;br /&gt;
&lt;br /&gt;
Once you have created source and background regions for each XIS and mode, the extraction of spectra and lightcurves are just calls to ''xisextract'':&lt;br /&gt;
  xisextract --prepdir ... --name name_of_subdirectory --xis=N --mode MxM --srcreg src_region_file --bkgreg bkg_region_file --attitude&lt;br /&gt;
Here, the --name specifies the subdirectoy to be created in the ''prepdir'' directory. In there, there will be additional directories created for each XIS, named xisN (N=0-3). Because there is a source and background region for each XIS and mode you have to specify those as well. The --attitude option tell ''xisextract'' to use the attitude corrected eventfiles as available in the ''reprocessed.att'' directory.&lt;br /&gt;
&lt;br /&gt;
By default, ''xisextract'' creates spectra and lightcurves. Since the ARF for each XIS has to be simulated (which may take some time), you may skip the ARF-generation or the spectrum extraction by providing --noarf or --nospe, respectively. If you add the --nolc option no lightcurve is extracted as well. The time resolution of the lightcurve can be set with the --dt option (the default is 100 s). The smallest time resolution is determined by the read-out mode. See the ''xisextract'' help for details and more options.&lt;br /&gt;
&lt;br /&gt;
==== Adding Modi ====&lt;br /&gt;
&lt;br /&gt;
After having extracted the data, there will be spectra for each XIS and mode. You should __not__ add the spectra of the individual XIS (due to different responses). Instead, analyse the spectra simultaneously. But you may add the spectra of the available modi for each XIS, resulting in one single spectra per XIS. You can achieve that using the ''phaadd'' command:&lt;br /&gt;
  phaadd --nousegti --backscaltol=0.1 /full_path_to_new_merged_spectrum_basename /full_path_to_xisN_mode1.pha /full_path_to_xisN_mode2.pha &lt;br /&gt;
You have to skip the creation of a single GTI file and in most cases you have to specify the tolerance of the background scaling factor as well.&lt;br /&gt;
&lt;br /&gt;
===== PIN and GSO =====&lt;br /&gt;
&lt;br /&gt;
Unlike the XISx the PIN and GSO have no imaging capabilities. Thus, creating the source and background regions is not possible, which simplifies the extraction. One of the disadvantages is, however, that the __background is not measurable__ during an observation! Like for the PCA on [[satext:rxte|RXTE]], the non X-ray background ([http://www.astro.isas.jaxa.jp/suzaku/doc/suzaku_td/node12.html#SECTION001250000000000000000 NXB ]) as caused by the detector itself is simulated instead. For PIN, there are [[http://heasarc.gsfc.nasa.gov/docs/suzaku/analysis/abc/node10.html#SECTION001051000000000000000|two different versions]] available: the //tuned// (the default in the //hxdextract// extraction script, see below) and ''quick'' simulated backgrounds. There are [http://heasarc.gsfc.nasa.gov/docs/suzaku/analysis/abc/node10.html#SECTION001071000000000000000 multiple NX background] versions for GSO available as well (the default is 2.6 currently).&lt;br /&gt;
Furthermore, a so-called cosmic X-ray background ([http://heasarc.gsfc.nasa.gov/docs/suzaku/analysis/abc/node10.html CXB]) is added to the simulated PIN background, based on a model by [(:biblio:Boldt84a)]. For HXD the CXB is assumed to be negligible.&lt;br /&gt;
&lt;br /&gt;
Since the instrumental settings of PIN changed in the past and might still be changed, we have to select the corresppnding [http://heasarc.gsfc.nasa.gov/docs/suzaku/analysis/abc/node10.html#SECTION001053000000000000000 PIN response epoch] matching our observation of interest. The current [http://www.astro.isas.jaxa.jp/suzaku/analysis/hxd/gsoarf2/ ARF version 20120526] of the GSO was calibrated on the crab pulsar. Fortunately, the ''hxdextract'' already uses this ARF and it calls ''hxdpinxbpi'' with the CALDB option, such that the correct PIN response for a particular observation is used as well.  &lt;br /&gt;
&lt;br /&gt;
All in all, to extract the HXD-spectra and -lightcurves including the correct backgrounds and responses, simply call&lt;br /&gt;
  hxdextract --prepdir ... --name name_of_subdirectory --all&lt;br /&gt;
Like for ''xisextract'', this will create the subdirectoy specified by --name within the ''prepdir'' directory. Furthermore, there will be subdirectories for the PIN and GSO data. Instead of extracting data from both instruments as indicated by the --all option you can specify those detectors separately.&amp;lt;br \&amp;gt;&lt;br /&gt;
'''Note''': the file of the PIN and GSO spectra are named ''ae_hxd_pin_sr.pi'' and ''ae_hxd_gso_sr.pi'', respectively. The spectra are consistent, however, with PHAII files.&lt;br /&gt;
 &lt;br /&gt;
To include the PIN response epoch in your paper, just look into the header of the PIN spectrum. For instance if ''hxdextract'' was called with --name=spectrum try&lt;br /&gt;
  fkeyprint spectrum/pin/ae_hxd_pin_sr.pi RESPFILE&lt;br /&gt;
This might results in &amp;quot;ae_hxd_pinxinome11_20110601.rsp&amp;quot;, thus its epoch 11 (e11) introduced in 2011/06/01. Please note that the response file also depends on the pointing of the satellite, which can be either the XIS- (xinom) or PIN nominal position (pinnom). These two different pointings are also available for the GSO response file.&lt;br /&gt;
&lt;br /&gt;
===== Data Reduction Section =====&lt;br /&gt;
&lt;br /&gt;
Besides the used energy ranges and signal-to-noise ratio or channel grouping, you should consider to explain the following points in the data reduction section of your paper (adopted and translated from an email by Katja Pottschmidt):&lt;br /&gt;
&lt;br /&gt;
''&amp;quot;To mention the used background versions...&amp;quot;'' (concerning PIN and GSO) ''&amp;quot;... sounds reasonable. Furthermore, it's typical to mention the shape and size of the XIS regions. Have you applied the attitude correction? What are the criteria for pile-up reduction? Is the PIN spectrum corrected for CXB (should be done by the scripts automatically)? Which PIN response did you use and which CALDB versions for the XRT (=the XIS mirrors), XIS, and HXD?&amp;quot;''&lt;br /&gt;
&lt;br /&gt;
[[Category:Data Extraction]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Suzaku&amp;diff=710</id>
		<title>Suzaku</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Suzaku&amp;diff=710"/>
		<updated>2018-04-11T12:40:36Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: Created page with &amp;quot;====== Suzaku Data Extraction ======  Suzaku consists of four detectors: * four XISs (X-ray Imaging Spectrometer, 0-3), useable energy range 1-9 keV * PIN, useable energy rang...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====== Suzaku Data Extraction ======&lt;br /&gt;
&lt;br /&gt;
Suzaku consists of four detectors:&lt;br /&gt;
* four XISs (X-ray Imaging Spectrometer, 0-3), useable energy range 1-9 keV&lt;br /&gt;
* PIN, useable energy range 12-60 keV&lt;br /&gt;
* GSO, useable energy range 57-300 keV&lt;br /&gt;
* XRS (X-ray Spectrometer), not useable since it failed after launch&lt;br /&gt;
PIN and GSO are mounted together within the HXD (Hard X-ray Detector). Unfortunately, XIS2 was hit by a micro meteorite in [http://www.astro.isas.jaxa.jp/suzaku/news/2006/1123/ 2006 November] and can no longer be used for analysis. A similar event happened to XIS0 in [http://www.astro.isas.jaxa.jp/suzaku/news/2009/0702/ July 2009], but the damage is much less such that data is still useable. Also note that XIS1 is back illuminated, while the other ones are front illuminated (causing a difference in the background level).&amp;lt;br \&amp;gt;&lt;br /&gt;
You might visit the [http://www.astro.isas.jaxa.jp/suzaku/news/ Suzaku News for Researches] to stay up to date about the current status of the satellite and instruments. For a detailed description please have a look on the [http://www.astro.isas.jaxa.jp/suzaku/doc/ Suzaku Documents], where you can also find the [http://www.astro.isas.jaxa.jp/suzaku/doc/suzaku_td/ Technical Description]. The extraction scripts introduced below are written by Laura Barragan, Joern Wilms, Felix Fuerst, et al. and basically follow the [http://heasarc.gsfc.nasa.gov/docs/suzaku/analysis/abc/abc.html Suzaku ABC Guide].&lt;br /&gt;
&lt;br /&gt;
Until some calibrations problems around the Si- and Au-edges are solved, the useable energy range of the XIS has to be modified slightly. According to [(:biblio:Nowak11a)] the following energy ranges should be ignored for all XIS:&lt;br /&gt;
  ignore_en(xis_datasets, 1.72, 1.88);&lt;br /&gt;
  ignore_en(xis_datasets, 2.19, 2.37);&lt;br /&gt;
For the back-illuminated XIS1, [(:biblio:Kuehnel13a)] had to exclude the energy range between both edges (1.88-2.19 keV) as well to get a consistent description compared to XIS0 and XIS3.&lt;br /&gt;
&lt;br /&gt;
===== Preparing the data =====&lt;br /&gt;
&lt;br /&gt;
First, apply the newest calibration to the rawdata:&lt;br /&gt;
  suzprepare --datadir path_to_raw_data --prepdir path_to_extraction --all&lt;br /&gt;
Thereby, ''datadir'' specifies the raw data directory, which you can find by, e.g., using the [[satext:findobs|findobs]] script. The ''prepdir'' argument sets the extraction directory and the last one tells the script to prepare the data for all instruments listed above. Other parameters are ''xisN'' with the XIS number N (0-3), ''pin'' or ''gso''.&lt;br /&gt;
For example:&lt;br /&gt;
  suzprepare --datadir /eu/X-ray/Suzaku/data/7/704063010 --predir `pwd`/ngc3783&lt;br /&gt;
In the extraction directory ''prepdir'' a subdirectory named ''reprocessed'' is created, where the event- and calibration-files are saved.&lt;br /&gt;
&lt;br /&gt;
== CALDB version ==&lt;br /&gt;
It is recommened to remember which version (which is a date-string) of the calibration database (CALDB) you've used for data preparation (you might want to add this information to your paper). You can use the following command to get the version installed at the '''date of calling''' this command:&lt;br /&gt;
  find $CALDB/data/suzaku/*/caldb.indx -print -exec readlink {} \;&lt;br /&gt;
That will print out the filename (with the version included) for the HXD, XIS, XRT (X-ray telescopes focusing onto the XISs), and XRS. If you haven't wrote down the versions right when you've extracted the data, it is more complicated to find out which versions were used. In that case you can match the different versions available in&lt;br /&gt;
  ls $CALDB/data/suzaku/*/index&lt;br /&gt;
against the creation date of your ''reprocessed''-directory.&lt;br /&gt;
&lt;br /&gt;
===== XIS =====&lt;br /&gt;
&lt;br /&gt;
==== Correcting the Attitude ====&lt;br /&gt;
&lt;br /&gt;
[[File:suz_extr_att.png|thumb|500px]]&lt;br /&gt;
The Attitude of the satellite is not known precisely, which causes the XIS-images to show an &amp;quot;image crater&amp;quot; or even two images of the source (see picture on the right). Therefore, a script named [http://space.mit.edu/CXC/software/suzaku/aeatt.html aeattcor2] was developed to correct the satellites attitude by using an image of the source. This tool is already included in the ''xisextract'' extraction script.&lt;br /&gt;
&lt;br /&gt;
[[File:suz_extr_att_region.png|thumb|500px]]&lt;br /&gt;
To correct the attitude using ''xisextract'' one needs to create a regionfile (by using, e.g., DS9) in WCS-coordinates containing a '''single''' and '''simple''' circle marking the source (see picture on the left). The radius of the circle should be around 90 arcsec. As an image, we open one of the cleaned event files ae{obsid}xi*_cl.evt located in the ''reprocessed'' directory. Furthermore, its worth to have a look on the unfiltered events *_uf.evt in case the filtered image looks weird. Here, we name the regionfile ''att_src.reg'' and save it in the ''prepdir'' directory.&lt;br /&gt;
&lt;br /&gt;
Now, we call ''xisextract'' for the first time to use the region created before for correcting the attitude:&lt;br /&gt;
  xisextract --prepdir ... --full --xis=N --attitude --srcreg=.../att_src.reg&lt;br /&gt;
&lt;br /&gt;
Providing the --full option will cause ''xisextract'' to extract a full image of the source (without any spectra or lightcurves). This will create the subdirectory ''full'' or ''full.att'' (in case of corrrecting the attitude as described here) in the ''prepdir'' direcotry. The --xis option has to be set to the number of the XIS (0-3), which means one has to execute the above command for all XISs. If --attitude is given, the script calles ''aeattcor2'' with the region file given with --srcreg. If successful, a folder called ''reprocessed.att'' will be created, which contains the corrected attitude and event files. If one looks on the *_sky.img images located within ''full.att'', the image creater should be suppressed or the two sources should have merged. Note that depending on the level of the wrong attitude the result might not be fully satisfying.&lt;br /&gt;
&lt;br /&gt;
'''Important note:''' in case the attitude correction fails the XISs were probably operated in the so-called burst mode. You can check the FITS header of the eventfiles to check on the clock mode (''normal'' or ''burst''):&lt;br /&gt;
  fkeyprint reprocessed/ae{obsid}xi*_cl.evt CLK_MODE&lt;br /&gt;
The burst mode causes a huge number of GTIs, which ''aeattcor2'' cannot handle. There is a workaround available which you can find below the next paragraph.&lt;br /&gt;
&lt;br /&gt;
== with aeattcor2 directly ==&lt;br /&gt;
For completeness and debugging purposes the attitude can be corrected directly using the ''aeattcor2'' tool:&lt;br /&gt;
  aeattcor2 attitude corrected_attitude events region&lt;br /&gt;
The old attitude file ae{obsid}.att (as created by ''suzprepare'') can be found in the ''reprocessed'' directory. The tool has to be called for at least one event file (e.g., that of XIS3 in 3x3 readout mode) to get a corrected attitude file. The region has to be the same as described above.&lt;br /&gt;
&lt;br /&gt;
=== Burst Mode ===&lt;br /&gt;
&lt;br /&gt;
If the XISs were operated in burst mode, an articifial dead time during each frame is introduced to reduce pile-up (for more detail see the [http://www.astro.isas.jaxa.jp/suzaku/doc/suzaku_td/node10.html#fig:xisoptfig Technical Manual]), which results in one GTI per frame. For instance given an observation with 40 ks total exposure time, operated in 1/4 window + 1 s burst option (exposure per frame is 2 s, from which 1 s is deadtime), the number of GTIs are around 40 ks / 2 s = 20000. That will cause ''aeattcor2'' to crash.&lt;br /&gt;
&lt;br /&gt;
Thus, in order to correct the attitude, we have to reduce the number of GTIs drastically. This can be achieved by using the --sloppygti option during the call of ''suzprepare'':&lt;br /&gt;
  suzprepare --datadir ... --prepdir ... --xis --sloppygti&lt;br /&gt;
Note, that we're providing the --xis options here. It's recommended to set the ''prepdir'' to another directory since the events during the deadtime are not supposed to account for a spectrum of lightcurve, of course.&lt;br /&gt;
&lt;br /&gt;
Once the data are prepared, proceed with the attitude correction as described above. As soon as there are attitude files for each XIS and mode, copy them to your original ''prepdir'' directory. There, run ''xisextract'' to correct the attitude, but provide the attitude files you've just got using the sloppy GTIs:&lt;br /&gt;
  xisextract --prepdir ... --full --xis=N --attitude --srcreg=.../att_src.reg --attitudefile ...&lt;br /&gt;
Note that you still need to set the source region, but since an attitude file is already given the call to ''aeattcor2'' will be skipped and the events are corrected using the given file instead.&lt;br /&gt;
&lt;br /&gt;
Finally, you may delete the ''prepdir'' directory of the --sloppygti preparation (and only '''that''').&lt;br /&gt;
&lt;br /&gt;
==== Source and Background Regions ====&lt;br /&gt;
&lt;br /&gt;
[[File:suz_extr_pilup.png|thumb|500px]]&lt;br /&gt;
Creating a source region for each XIS and read-out mode is more complicated due to pile-up. If two photons hit a pixel of the CCD at the same frame, they cannot be distinguished. During the read-out they look like a single photon with the sum of theire energies. Thus, a piled-up spectrum appears to be harder and flux in the soft energy range (&amp;lt; 5 keV) is missing (compare Figure on the right).&lt;br /&gt;
&lt;br /&gt;
To handle pile-up correctly, one has to estimate the probability for pile-up (the pile-up fraction) in each pixel for each XIS and mode. The resulting pile-up maps (of the source) are then used to create the extraction regions.&lt;br /&gt;
&lt;br /&gt;
The pile-up estimation is done by ''xisextract'' as well, which calls ''pileest'' internally. You can skip this call if you give the --nopileup option during the --full call to ''xisextract''. That means as soon as you have extracted the full images of the XIS you've automatically got the pile-up maps. They are located in the ''reprocessed.att'' directory and are named ae{obsid}xiN_*_pileup.img&lt;br /&gt;
There are pile-up maps for each XIS and mode, and you have to create source and background regions avoiding pile-up for all. Thus, the region filenames have to include the XIS and mode, of course.&lt;br /&gt;
&lt;br /&gt;
[[File:suz_extr_pilup_contour.png|thumb|500px]] Once you have opened a pile-up map with, e.g., DS9 the pixel value now represents the pile-up fraction instead of the number of counts. The easiest source region shape to take pile-up into account is an annulus with an outer radius of 90 arcsec. It's strongly recommended to use the same outer radius for '''all''' XIS and modes to get stable cross-calibration factors! The inner radius has to be determined such that within that radius the pile-up fraction is meanly below a certain value. Here, we suggest to skip regions with more than '''4%''' pile-up.&amp;lt;br \&amp;gt;&lt;br /&gt;
To speed up the determination of the inner radius, you can add the 4% (or whatever) contour to the image shown in DS9. Therefore, select the &amp;quot;Contour Parameters&amp;quot; item in the &amp;quot;Analysis&amp;quot; menue. In the new window, add the 0.04 level to the list on the right, delete all other levels, and set the smoothness to zero. After a click on &amp;quot;Apply&amp;quot; a contour will be drawn representing 4% pile-up fraction (see the black line in the example on the left). Now, it is easier to create the source region (see the example below).&lt;br /&gt;
&lt;br /&gt;
For the background regions no pile-up has to be considered (hopefully), such that their shape may be simple circles. Just move them to the borders of the chip or to another area outside of '''all''' sources.&lt;br /&gt;
&lt;br /&gt;
Save both, the source and background regions, as separate files. For example, xis3_3x3_src.reg and xis3_3x3_bkg.reg, respectively.&lt;br /&gt;
&lt;br /&gt;
[[File:suz_extr_src_reg.png|thumb|500px]][[File:suz_extr_bkg_reg.png|thumb|500px]]&amp;lt;br \&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Extracting spectra and lightcurves ====&lt;br /&gt;
&lt;br /&gt;
Once you have created source and background regions for each XIS and mode, the extraction of spectra and lightcurves are just calls to ''xisextract'':&lt;br /&gt;
  xisextract --prepdir ... --name name_of_subdirectory --xis=N --mode MxM --srcreg src_region_file --bkgreg bkg_region_file --attitude&lt;br /&gt;
Here, the --name specifies the subdirectoy to be created in the ''prepdir'' directory. In there, there will be additional directories created for each XIS, named xisN (N=0-3). Because there is a source and background region for each XIS and mode you have to specify those as well. The --attitude option tell ''xisextract'' to use the attitude corrected eventfiles as available in the ''reprocessed.att'' directory.&lt;br /&gt;
&lt;br /&gt;
By default, ''xisextract'' creates spectra and lightcurves. Since the ARF for each XIS has to be simulated (which may take some time), you may skip the ARF-generation or the spectrum extraction by providing --noarf or --nospe, respectively. If you add the --nolc option no lightcurve is extracted as well. The time resolution of the lightcurve can be set with the --dt option (the default is 100 s). The smallest time resolution is determined by the read-out mode. See the ''xisextract'' help for details and more options.&lt;br /&gt;
&lt;br /&gt;
==== Adding Modi ====&lt;br /&gt;
&lt;br /&gt;
After having extracted the data, there will be spectra for each XIS and mode. You should __not__ add the spectra of the individual XIS (due to different responses). Instead, analyse the spectra simultaneously. But you may add the spectra of the available modi for each XIS, resulting in one single spectra per XIS. You can achieve that using the ''phaadd'' command:&lt;br /&gt;
  phaadd --nousegti --backscaltol=0.1 /full_path_to_new_merged_spectrum_basename /full_path_to_xisN_mode1.pha /full_path_to_xisN_mode2.pha &lt;br /&gt;
You have to skip the creation of a single GTI file and in most cases you have to specify the tolerance of the background scaling factor as well.&lt;br /&gt;
&lt;br /&gt;
===== PIN and GSO =====&lt;br /&gt;
&lt;br /&gt;
Unlike the XISx the PIN and GSO have no imaging capabilities. Thus, creating the source and background regions is not possible, which simplifies the extraction. One of the disadvantages is, however, that the __background is not measurable__ during an observation! Like for the PCA on [[satext:rxte|RXTE]], the non X-ray background ([http://www.astro.isas.jaxa.jp/suzaku/doc/suzaku_td/node12.html#SECTION001250000000000000000 NXB ]) as caused by the detector itself is simulated instead. For PIN, there are [[http://heasarc.gsfc.nasa.gov/docs/suzaku/analysis/abc/node10.html#SECTION001051000000000000000|two different versions]] available: the //tuned// (the default in the //hxdextract// extraction script, see below) and ''quick'' simulated backgrounds. There are [http://heasarc.gsfc.nasa.gov/docs/suzaku/analysis/abc/node10.html#SECTION001071000000000000000 multiple NX background] versions for GSO available as well (the default is 2.6 currently).&lt;br /&gt;
Furthermore, a so-called cosmic X-ray background ([http://heasarc.gsfc.nasa.gov/docs/suzaku/analysis/abc/node10.html CXB]) is added to the simulated PIN background, based on a model by [(:biblio:Boldt84a)]. For HXD the CXB is assumed to be negligible.&lt;br /&gt;
&lt;br /&gt;
Since the instrumental settings of PIN changed in the past and might still be changed, we have to select the corresppnding [http://heasarc.gsfc.nasa.gov/docs/suzaku/analysis/abc/node10.html#SECTION001053000000000000000 PIN response epoch] matching our observation of interest. The current [http://www.astro.isas.jaxa.jp/suzaku/analysis/hxd/gsoarf2/ ARF version 20120526] of the GSO was calibrated on the crab pulsar. Fortunately, the ''hxdextract'' already uses this ARF and it calls ''hxdpinxbpi'' with the CALDB option, such that the correct PIN response for a particular observation is used as well.  &lt;br /&gt;
&lt;br /&gt;
All in all, to extract the HXD-spectra and -lightcurves including the correct backgrounds and responses, simply call&lt;br /&gt;
  hxdextract --prepdir ... --name name_of_subdirectory --all&lt;br /&gt;
Like for ''xisextract'', this will create the subdirectoy specified by --name within the ''prepdir'' directory. Furthermore, there will be subdirectories for the PIN and GSO data. Instead of extracting data from both instruments as indicated by the --all option you can specify those detectors separately.&amp;lt;br \&amp;gt;&lt;br /&gt;
'''Note''': the file of the PIN and GSO spectra are named ''ae_hxd_pin_sr.pi'' and ''ae_hxd_gso_sr.pi'', respectively. The spectra are consistent, however, with PHAII files.&lt;br /&gt;
 &lt;br /&gt;
To include the PIN response epoch in your paper, just look into the header of the PIN spectrum. For instance if ''hxdextract'' was called with --name=spectrum try&lt;br /&gt;
  fkeyprint spectrum/pin/ae_hxd_pin_sr.pi RESPFILE&lt;br /&gt;
This might results in &amp;quot;ae_hxd_pinxinome11_20110601.rsp&amp;quot;, thus its epoch 11 (e11) introduced in 2011/06/01. Please note that the response file also depends on the pointing of the satellite, which can be either the XIS- (xinom) or PIN nominal position (pinnom). These two different pointings are also available for the GSO response file.&lt;br /&gt;
&lt;br /&gt;
===== Data Reduction Section =====&lt;br /&gt;
&lt;br /&gt;
Besides the used energy ranges and signal-to-noise ratio or channel grouping, you should consider to explain the following points in the data reduction section of your paper (adopted and translated from an email by Katja Pottschmidt):&lt;br /&gt;
&lt;br /&gt;
&amp;quot;//To mention the used background versions...//&amp;quot; (concerning PIN and GSO) &amp;quot;//... sounds reasonable. Furthermore, it's typical to mention the shape and size of the XIS regions. Have you applied the attitude correction? What are the criteria for pile-up reduction? Is the PIN spectrum corrected for CXB (should be done by the scripts automatically)? Which PIN response did you use and which CALDB versions for the XRT (=the XIS mirrors), XIS, and HXD? //&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[[Category:Data Extraction]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Nustar&amp;diff=693</id>
		<title>Nustar</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Nustar&amp;diff=693"/>
		<updated>2018-04-11T12:01:47Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: Created page with &amp;quot;====== NuSTAR data extraction ======  '''Preparation:''' This step unpacks the data of both FPM to the specified 'prepdir'. The example observation is of Mrk 335.  &amp;lt;pre&amp;gt; #!/bi...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====== NuSTAR data extraction ======&lt;br /&gt;
&lt;br /&gt;
'''Preparation:''' This step unpacks the data of both FPM to the specified 'prepdir'. The example observation is of Mrk 335.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/csh&lt;br /&gt;
   &lt;br /&gt;
set revolution = '6'&lt;br /&gt;
set obsid = '60001041005'&lt;br /&gt;
set datadir = /eu/X-ray/NuSTAR/data/$revolution/$obsid&lt;br /&gt;
set prepdir = /userdata/data/$user/whereever/you/want&lt;br /&gt;
&lt;br /&gt;
nuprepare --datadir=$datadir --prepdir=$prepdir --all&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Spectrum and Lightcurve Extraction:'''&lt;br /&gt;
Now you can take a look at the raw images in prepdir/reprocessed/nu-obsid-A-or-B-01_cl.evt using ''ds9''. Create a region by clicking at the source and choose a circular region between 50 and 120&amp;lt;nowiki&amp;gt;''&amp;lt;/nowiki&amp;gt; radius centered on the source. You can save the coordinates under Region-&amp;gt;Save Regions... as .reg-file use the default coordinate system.&amp;lt;br /&amp;gt;&lt;br /&gt;
Choose and save another region for the background spectrum that does not contain any sources and make it as large as possible. Be careful that it is still within NuSTAR's FOV.&amp;lt;br /&amp;gt;&lt;br /&gt;
Now we can extract the spectrum using nuextract:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#!/bin/csh&lt;br /&gt;
   &lt;br /&gt;
set revolution = '6'&lt;br /&gt;
set obsid = '60001041005'&lt;br /&gt;
set prepdir = /userdata/data/$user/whereever/you/want&lt;br /&gt;
&lt;br /&gt;
set name = extraction_a&lt;br /&gt;
set bkg = $prepdir/reprocessed/fpma_bkg.reg&lt;br /&gt;
set src = $prepdir/reprocessed/fpma_src.reg&lt;br /&gt;
&lt;br /&gt;
nuextract --prepdir=$prepdir --name=$name --srcreg=$src --bkgreg=$bkg --fpm='A'&lt;br /&gt;
&lt;br /&gt;
set name = extraction_b&lt;br /&gt;
set bkg = $prepdir/reprocessed/fpmb_bkg.reg&lt;br /&gt;
set src = $prepdir/reprocessed/fpmb_src.reg&lt;br /&gt;
&lt;br /&gt;
nuextract --prepdir=$prepdir --name=$name --srcreg=$src --bkgreg=$bkg --fpm='B'&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For time- or energy-limited extractions take a look at:&lt;br /&gt;
 nuextract --help&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Version information =====&lt;br /&gt;
&lt;br /&gt;
In order to find out the version of the NuSTARDAS and CALDB your data were extracted with, you can use the following commands:&lt;br /&gt;
&lt;br /&gt;
  fdump &amp;lt;fits_file_of_interest&amp;gt; page=no | grep -i nustardas&lt;br /&gt;
  fdump &amp;lt;fits_file_of_interest&amp;gt; page=no | grep -i caldb&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Data Extraction]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Chandra&amp;diff=692</id>
		<title>Chandra</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Chandra&amp;diff=692"/>
		<updated>2018-04-11T11:50:43Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====== Chandra ======&lt;br /&gt;
&lt;br /&gt;
===== HETG =====&lt;br /&gt;
&lt;br /&gt;
As of Aug 2014, the old Chandra HETG extraction scripts by Manfred are deprecated. They were good for Ciao Versions up to 4.2. Ciao 4.3 already has a bug that does not cause error messages with this script but whose bug fix is not implemented. On top of that a lot has changed. We have newer extraction scripts working with Ciao-4.6 that should be much easier to maintain with future changes to data preparation with Ciao, as the data preparation is now based on ''chandra_repro''. &lt;br /&gt;
&lt;br /&gt;
Data preparation and data extraction are two separate steps, i.e., the data only needs to be prepared / reprocessed once (making sure the newest and most appropriate CALDB information is used for each observation), but then can be used for extration of spectra, lightcurves, and images multiple times, e.g., with different GTIs. The scripts can be found at:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
/data/system/software/scripts/chandrascripts/&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
and are called ''chandraprepare'' and ''gratingsextract''. Calling the scripts with no option or with ''--help'' will print a description of available options / arguments to STDOUT. &lt;br /&gt;
&lt;br /&gt;
==== Caveats ====&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
The scripts currently have issues with data in CC mode. &lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
If there are multiple event1 files in the archive directory, the script will exit with a warning.&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
Correct use of multi-event1 file observation is pending implementation. Talk to the Remeis Chandra-point of contact. &lt;br /&gt;
&lt;br /&gt;
==== chandraprepare ====&lt;br /&gt;
Example bash script to call chandraprepare (update the Ciao version if applicable):&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/bash&lt;br /&gt;
&lt;br /&gt;
. /data/system/software/chandra/ciao-4.6/ciao-4.6/bin/ciao.bash&lt;br /&gt;
&lt;br /&gt;
export CHANDRATOOLS=/data/system/software/scripts/chandrascripts&lt;br /&gt;
&lt;br /&gt;
chandraprepare=${CHANDRATOOLS}/chandraprepare&lt;br /&gt;
&lt;br /&gt;
cdata=/eu/X-ray/Chandra/archive/${obsid}/&lt;br /&gt;
obsid=1600&lt;br /&gt;
datadir=${cdata}/${obsid}&lt;br /&gt;
&lt;br /&gt;
${chandraprepare} --datadir=${datadir} --prepdir=test${obsid}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== gratingsextract ====&lt;br /&gt;
Example bash script to call gratingsextract (update the Ciao version if applicable):&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/bash&lt;br /&gt;
&lt;br /&gt;
. /data/system/software/chandra/ciao-4.6/ciao-4.6/bin/ciao.bash&lt;br /&gt;
&lt;br /&gt;
export CHANDRATOOLS=/data/system/software/scripts/chandrascripts&lt;br /&gt;
&lt;br /&gt;
extract=${CHANDRATOOLS}/gratingsextract&lt;br /&gt;
&lt;br /&gt;
obsid=1600&lt;br /&gt;
name=full&lt;br /&gt;
&lt;br /&gt;
${extract} --prepdir=${obsid} --name=${name} --heg --meg --order=-1,1 --dt=25.5 --energyband=500,1500,3000,10000&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Loading data in ISIS ====&lt;br /&gt;
The above scripts create individual files for each arm/order, even for lightcurves. While the old Manfred-scripts wrote loadscripts to ease loading the data in ISIS, the new script do not provide ''loaddata.sl'' scripts anymore. The naming scheme for the extracted data changed slightly and is now generic enough to allow for common load functions for HETG data. Talk to Natalie for functions that easily load spectral data (preserving the order established by the old extraction scripts to allow for compatibility with old isis ''par'' files), individual lightcurves and the sum over lightcurves.&lt;br /&gt;
&lt;br /&gt;
Eventually, these function will make it into the ''isisscripts''.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== LETG =====&lt;br /&gt;
&lt;br /&gt;
Theoretically, the new scripts described above can handle LETG observations. However, this is largely untested.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== ACIS-I =====&lt;br /&gt;
Global scripts are yet missing.&lt;br /&gt;
&lt;br /&gt;
[[Category:Data Extraction]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Integral&amp;diff=690</id>
		<title>Integral</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Integral&amp;diff=690"/>
		<updated>2018-04-11T11:49:22Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: Created page with &amp;quot; ====== Quick Look Analysis ======  http://isdc.unige.ch/heavens/  How does the INTEGRAL analysis software work in general? http://www.isdc.unige.ch/integral/download/osa/doc/...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== Quick Look Analysis ======&lt;br /&gt;
&lt;br /&gt;
http://isdc.unige.ch/heavens/&lt;br /&gt;
&lt;br /&gt;
How does the INTEGRAL analysis software work in general?&lt;br /&gt;
http://www.isdc.unige.ch/integral/download/osa/doc/10.0/osa_um_ibis/node27.html&lt;br /&gt;
&lt;br /&gt;
====== INTEGRAL Scripts ======&lt;br /&gt;
&lt;br /&gt;
Can be found under&lt;br /&gt;
&lt;br /&gt;
/data/system/software/scripts/intscripts/&lt;br /&gt;
&lt;br /&gt;
on remeis machines. If you want/need an introduction, talk to Tobi. Also, someone may want to write a few examples. At some points. [VG: not me]&lt;br /&gt;
&lt;br /&gt;
==== How to create mosaics ====&lt;br /&gt;
&lt;br /&gt;
First make a list of scws you want to add to a mosaic, i.e., a &amp;quot;dol-file&amp;quot; dol.txt:&lt;br /&gt;
  /scratch1/beuchert/integral/scw_extr/obs/066200340010/scw/066200340010.001/swg_ibis.fits&lt;br /&gt;
  /scratch1/beuchert/integral/scw_extr/obs/066200350010/scw/066200350010.001/swg_ibis.fits&lt;br /&gt;
  /scratch1/beuchert/integral/scw_extr/obs/066200360010/scw/066200360010.001/swg_ibis.fits&lt;br /&gt;
Then prepare the directory where the mosaic shall be built in, i.e., set the env. variables to allow INT_mosa_ibis to find indices etc.:&lt;br /&gt;
  cd /some/path/&lt;br /&gt;
  ln -s /virgo/b/INTEGRAL/aux/&lt;br /&gt;
  ln -s /virgo/b/INTEGRAL/idx/&lt;br /&gt;
  ln -s /virgo/b/INTEGRAL/ic/&lt;br /&gt;
  ln -s /virgo/b/INTEGRAL/scw/&lt;br /&gt;
  ln -s /virgo/b/INTEGRAL/cat/&lt;br /&gt;
  mkdir /some/path/obs/&lt;br /&gt;
  &lt;br /&gt;
  INT_mosa_ibis --obsgrp=/path/to/all/extracted/scws/ --destin=/path/to/the/prepared/directory/obs/mosa_og/ --dol=&amp;quot;dol.txt&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== abbreviations =====&lt;br /&gt;
http://www.isdc.unige.ch/integral/support/glossary&lt;br /&gt;
&lt;br /&gt;
* '''DAL''' The Data Access Layer (DAL) is a software library used to manipulate (create, write, read and manage) scientific data. &lt;br /&gt;
* '''DOL''' The Data Object Location (DOL) specifies the location of a DAL object, both by the FITS file name and its extension. For instance, /isdc/dev/xxx.fits[2] is a DOL, while xxx.fits is simply the name of a FITS file. &lt;br /&gt;
&lt;br /&gt;
===== Known Issues =====&lt;br /&gt;
In general: check first http://www.isdc.unige.ch/integral/support/faq for the error code you get&lt;br /&gt;
&lt;br /&gt;
=== Mosaicing using custom DOLs ===&lt;br /&gt;
If you want to create a mosaic using DOL (Data Object Location) files, sometimes the building interrupts with errors like a Fortran Runtime error (http://www.isdc.unige.ch/integral/support/faq.cgi?SOFT-051) or errors like:&lt;br /&gt;
&lt;br /&gt;
  Using and copying first SCW &amp;gt;&amp;gt;/scratch1/beuchert/integral/scw_extr/obs/125400400010/scw/125400400010.001/swg_ibis.fits&lt;br /&gt;
  &amp;lt;&amp;lt;&lt;br /&gt;
  Log_0  :  100 elements opened.&lt;br /&gt;
  Log_0  :  100 elements attached.&lt;br /&gt;
  Error_1: Can not update the index.&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
  Error_1: Can not close the element&lt;br /&gt;
or &lt;br /&gt;
  Error_2: DAL_READ_ERROR : error reading from FITS file&lt;br /&gt;
etc.&lt;br /&gt;
&lt;br /&gt;
'''Solutions:'''&lt;br /&gt;
# Somehow corrupted scws? Collect sets of two scws and create Mosaics based on those. Like that it is easy to enclose corrupted scws.&lt;br /&gt;
# An error -2004 (DAL_FILE_NOT_ACCESSIBLE) often results because one of your groups is corrupted. Before restarting the analysis, make a ``dal_clean'', which should be able to do an automatic repair. If it does not work try a ``dal_verify'' to see what is corrupted. Or you can try to open your group (or child group) with fv and look for a file pointed by the group that does not exists. Most of the time removing the line with this wrong file in the group table is fixing your problem.&lt;br /&gt;
&lt;br /&gt;
The latter:&lt;br /&gt;
first create an observation group out of your dol-list of scws.&lt;br /&gt;
Creating observation groups is also the canonical way of extracting INTEGRAL/IBIS data.&lt;br /&gt;
Before doing that, the soft links as noted above have to be set in the directory.&lt;br /&gt;
Then:&lt;br /&gt;
  cd path/to/dir/with/softlinks/&lt;br /&gt;
  og_create idxSwg=dol.txt ogid=isgri_gc baseDir=&amp;quot;./&amp;quot; instrument=IBIS&lt;br /&gt;
  ls obs/isgri_gc/&lt;br /&gt;
Repair the observation group and included indices/links with &lt;br /&gt;
  dal_clean inDOL=&amp;quot;obs/isgri_gc/og_ibis.fits&amp;quot; chatty=&amp;quot;4&amp;quot; checkExt=&amp;quot;1&amp;quot;&lt;br /&gt;
Now INT_mosa_ibis should work again on the scws in dol.txt&lt;br /&gt;
&lt;br /&gt;
[[Category:Data Extraction]]&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
	<entry>
		<id>https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Chandra&amp;diff=689</id>
		<title>Chandra</title>
		<link rel="alternate" type="text/html" href="https://www.sternwarte.uni-erlangen.de/wiki/index.php?title=Chandra&amp;diff=689"/>
		<updated>2018-04-11T11:36:49Z</updated>

		<summary type="html">&lt;p&gt;Ballhausen: Created page with &amp;quot;  Category:Data Extraction  ====== Chandra ======  ===== HETG =====  As of Aug 2014, the old Chandra HETG extraction scripts by Manfred are deprecated. They were good for...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Data Extraction]]&lt;br /&gt;
&lt;br /&gt;
====== Chandra ======&lt;br /&gt;
&lt;br /&gt;
===== HETG =====&lt;br /&gt;
&lt;br /&gt;
As of Aug 2014, the old Chandra HETG extraction scripts by Manfred are deprecated. They were good for Ciao Versions up to 4.2. Ciao 4.3 already has a bug that does not cause error messages with this script but whose bug fix is not implemented. On top of that a lot has changed. We have newer extraction scripts working with Ciao-4.6 that should be much easier to maintain with future changes to data preparation with Ciao, as the data preparation is now based on ''chandra_repro''. &lt;br /&gt;
&lt;br /&gt;
Data preparation and data extraction are two separate steps, i.e., the data only needs to be prepared / reprocessed once (making sure the newest and most appropriate CALDB information is used for each observation), but then can be used for extration of spectra, lightcurves, and images multiple times, e.g., with different GTIs. The scripts can be found at:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
/data/system/software/scripts/chandrascripts/&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
and are called ''chandraprepare'' and ''gratingsextract''. Calling the scripts with no option or with ''--help'' will print a description of available options / arguments to STDOUT. &lt;br /&gt;
&lt;br /&gt;
==== Caveats ====&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
The scripts currently have issues with data in CC mode. &lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
If there are multiple event1 files in the archive directory, the script will exit with a warning.&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
Correct use of multi-event1 file observation is pending implementation. Talk to the Remeis Chandra-point of contact. &lt;br /&gt;
&lt;br /&gt;
==== chandraprepare ====&lt;br /&gt;
Example bash script to call chandraprepare (update the Ciao version if applicable):&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/bash&lt;br /&gt;
&lt;br /&gt;
. /data/system/software/chandra/ciao-4.6/ciao-4.6/bin/ciao.bash&lt;br /&gt;
&lt;br /&gt;
export CHANDRATOOLS=/data/system/software/scripts/chandrascripts&lt;br /&gt;
&lt;br /&gt;
chandraprepare=${CHANDRATOOLS}/chandraprepare&lt;br /&gt;
&lt;br /&gt;
cdata=/eu/X-ray/Chandra/archive/${obsid}/&lt;br /&gt;
obsid=1600&lt;br /&gt;
datadir=${cdata}/${obsid}&lt;br /&gt;
&lt;br /&gt;
${chandraprepare} --datadir=${datadir} --prepdir=test${obsid}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== gratingsextract ====&lt;br /&gt;
Example bash script to call gratingsextract (update the Ciao version if applicable):&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/bash&lt;br /&gt;
&lt;br /&gt;
. /data/system/software/chandra/ciao-4.6/ciao-4.6/bin/ciao.bash&lt;br /&gt;
&lt;br /&gt;
export CHANDRATOOLS=/data/system/software/scripts/chandrascripts&lt;br /&gt;
&lt;br /&gt;
extract=${CHANDRATOOLS}/gratingsextract&lt;br /&gt;
&lt;br /&gt;
obsid=1600&lt;br /&gt;
name=full&lt;br /&gt;
&lt;br /&gt;
${extract} --prepdir=${obsid} --name=${name} --heg --meg --order=-1,1 --dt=25.5 --energyband=500,1500,3000,10000&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Loading data in ISIS ====&lt;br /&gt;
The above scripts create individual files for each arm/order, even for lightcurves. While the old Manfred-scripts wrote loadscripts to ease loading the data in ISIS, the new script do not provide ''loaddata.sl'' scripts anymore. The naming scheme for the extracted data changed slightly and is now generic enough to allow for common load functions for HETG data. Talk to Natalie for functions that easily load spectral data (preserving the order established by the old extraction scripts to allow for compatibility with old isis ''par'' files), individual lightcurves and the sum over lightcurves.&lt;br /&gt;
&lt;br /&gt;
Eventually, these function will make it into the ''isisscripts''.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== LETG =====&lt;br /&gt;
&lt;br /&gt;
Theoretically, the new scripts described above can handle LETG observations. However, this is largely untested.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== ACIS-I =====&lt;br /&gt;
Global scripts are yet missing.&lt;/div&gt;</summary>
		<author><name>Ballhausen</name></author>
	</entry>
</feed>