Remeis-Wiki - User contributions [en]

PhD Hat Caro

2025-08-28T09:44:44Z

Nekrasov: /* Ideas for Caro's PhD hat go here! */

[[Category:internal]]
=Ideas for Caro's PhD hat go here! =

- obviously something with steam locomotives, maybe get a small paper version for the hat?

- Slurm queue printout?

- something about tea, teapots (e.g. a metric of a teapot?)
(can be merged with her pottery hobby, maybe a coffee mug?)

- a open fire with a turnable Nico figure above the flame

- rotating fish and brainrot memes

- DPREAO president including laws, Kim Jung Un meme, battle and war with anti-dpreao coalition

- a hammock maybe as a tassel?

- a little banana pizza?

- wanted signs for slurm offenders with a nerf stuck on it (USE 4GB RAM MACHINES)

- french press / fancy coffee

PhD Hat Caro

2025-08-27T13:07:02Z

Nekrasov: /* Ideas for Caro's PhD hat go here! */

Xmm

2025-08-12T10:06:15Z

Nekrasov: /* Data */

== Data ==

Always use the remeis archives at /eu/X-ray/XMM/data/ instead of downloading observation files yourself. You can search for the data of an observation by typing something like '''find /eu/X-ray/xmm/data/????/obsID/odf -type d''' - replacing obsID with your observation ID.
If the observation you want to analyze is not in the archives: contact the XMM admin (Outdated: ~~Jonathan Knies~~, ~~Amy Joyce~~ ??Esin Gulbahar?? and the observation will be downloaded for you.

Note (as of 12.08.2025): since xmmsas version 22 we cannot run it natively on the cluster. Instead, we have a docker image for this. Otherwise, downgrade xmmsas to version 21 "module load xmmsas/21" if you want to use the algorithm below.

== XMM EPIC Data Extraction ==

After the system was updated from Ubuntu 11 to Ubuntu 12 a problem occured with the function "dssetattr" inside the "epchain".
This function can set/add an attribute to the HDU (Header/Data Unit).
The solution is to call
''''source $SOFTDIR/sas_init.csh''''
at the beginning of each script in order to initialize SAS inside your script.

A little example script:

#!/bin/csh
source $SOFTDIR/sas_init.csh # initialize the SAS software
set xmmscripts = ${XMMTOOLS} # make sure the proper xmmscripts are loaded

set obsid = '0147190101'
set datadir = /eu/X-ray/XMM/data/????/$obsid/odf

${xmmscripts}/xmmprepare --datadir=$datadir --prepdir=$obsid --pn # prepare the data
${xmmscripts}/xmmextract --prepdir=$obsid --pn --full # full extraction of the chip
${xmmscripts}/xmmextract --prepdir=$obsid --pn --srcreg=src.fits --bkgreg=bkg.fits # source and background extraction of the chip

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).

The xmmscripts need the region files to be fits files. You can convert them via
ds9tocxc outset=outfilename.fits < infilename.reg

For simple extractions of point sources creating region files is not necessary, you can just give the position of the source and background region as well as their extraction radii with the "--ra", "--dec" and "--bkgra", "--bkgdec" arguments.

"xmmextract" is a very powerful script, use its "--help" argument to get a list of all arguments.

Further important points:

# If your observation includes sub-observations, choose one of them. Do this with "onlyexp=1" not "onlyexp=PNU001" for example.
# 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:

example:

#!/bin/csh
${XMMTOOLS}/xmmprepare --datadir=/eu/X-ray/XMM/data/2290/0679780201/odf/
--prepdir=./test --pn --analysisdate=2014-01-11T01:05:00.000

== XMM OM Data Extraction ==

For extracting the data of the Optical Monitor (OM) onboard XMM, there exist three tools which do this automatically: ''omichain'', ''omfchain'' and ''omgchain''.
"i" stands for image mode, "f" for fast mode and "g" 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.
If you want to extract your images you first have to set some paths:

$source $SOFTDIR/sas_init.csh
$setenv SAS_ODF path_to_your_data #normally /eu/X-ray/XMM/data/rev/ObsID/odf/
$cifbuild
$setenv SAS_CCF ccf.cif
$odfingest
$setenv SAS_ODF `ls -1 *SUM.SAS`

After this you can run

$omichain #or omfchain, omgchain

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.
At the end you should have several images (<code>*IMAGE*</code>), region files (<code>*REGION*</code>) and source lists (<code>*SWSRLI*</code>) for the OM exposures and filters. The nomenclatur for the files are:

* IOOOOOOOOOODDUEEETTTTTTSXXX.FFF or POOOOOOOOOODDUEEETTTTTTSXXX.FFF (for PPS product files)
* OOOOOOOOOO = XMM-ObsID (10 characters)
* DD = Data source idetifier (here OM)
* U = exposure flag (S = sched, U = unsched, X = not aplicable)
* EEE = exposure number within the instrument observation (3 characters)
* TTTTTT = product type (6 characters)
* S = 0 or data subset number/character
* XXX = source number or slew step number (3 characters)
* FFF = file format (3 characters)

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.
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.

Then check the detector images (<code>P*IMAGE_*000.FIT</code>) 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 (<code>*REGION*000.ASC</code>, e.g. <code>P0090050801OMS006IMAGE_0000.FIT</code> -> ''I0090050801OMS006REGION0000.ASC</code>) and identify the number of your source.

[[File:image_region.jpeg|thumb]]

Look into the source list for your exposure (<code>P*SWSRLI*.FIT</code>) and note the SRC_ID in the last column. Open the combined source list (<code>*COMBO*</code>) and search for your SRC_ID. Here you can find all the magnitudes and fluxes of your source for the different filters.

== Choosing correct XMM-EPIC filter ==

Choosing the correct EPIC filter for your observation depends on the
visual magnitudes of the other objects (usually stars) in the EPIC
field of view.

The XMM user's handbook (sect. 3.3.6;
http://xmm.esac.esa.int/external/xmm_user_support/documentation/uhb/epicfilters.html) recommends:

Thick filter: suppress up to magnitudes of -2 to -1 (pn), or +1 to +4 (mos)

Medium filter: if there is nothing above magnitude ~ 6 to 9

Thin filter: for point sources that are 12 mag fainter than thick filter limitations

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.

Use the United States Naval Observatory catalog at
http://www.nofs.navy.mil/data/fchpix/ to find the stars within a 9'
radius.

At that website, enter your R.A. and Decl., and for the output file
options in the left column, unclick everything except RA,DEC,
magnitude, and offset from center. Then click 'retrieve data' in the
right column.

Next window: Click on "USNO B1.0 Star List" to download a gzipped
ASCII file with typically hundreds of rows/stars for lines of sight
away from the Galactic Plane (or many thousands of rows/stars for
lines of sight in the Galactic Plane).

Example file: See /home/markowitz/proposals/xmm2014/GS1826USNO for a
Galactic XRB, GS1826, located in the Galactic Bulge (optically-crowded
fields).

The star list is ordered by R.A., and but you can then re-order the ASCII list
by magnitude, e.g.,

cat GS1826USNO | grep -v '#' | awk '{print $7 " " $12}' | sort -g > starlist_sortB
cat GS1826USNO | grep -v '#' | awk '{print $8 " " $12}' | sort -g > starlist_sortR

since the B and R magnitudes are columns 7 and 8, and distance from the center
of f.o.v. (in arcsec) is column 12

Ignore the rows with zero magnitudes; a zero means unmeasured flux.

For these example files, e.g., /home/markowitz/proposals/xmm2014/starlist_sortB
we see that the brightest B- and R-band magnitudes are 10.0-10.3, including some
objects that are only 3-5' from the center, and at least one that's only 1.2'
from the center, so one cannot use the thin epic filter; one must use
the MEDIUM filter for all three EPIC cameras.

== XMM ESAS ==

If you are interested in diffuse X-ray emission it is recommended to use the XMM-Newton Extended Source Analysis Software.
The manual can be found at [https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html] with very detailed step-by-step instructions.

==== Working with XMM ESAS in the remeis environment ====

Before you start with the data analysis you have to source the SAS init via '''source $SOFTDIR/sas_init.csh'''.
Since you will need this every time you start a new terminal it is recommended to add an alias to your .cshrc in your home directory, e.g. '''alias setsas 'source $SOFTDIR/sas_init.csh''''.

First you have to find out the observation data path in the archives, which can be done by typing '''find /eu/X-ray/xmm/data/????/obsID/odf -type d''', where you replace obsID with your desired observation.
Next, you have to set up the environment variables for the SAS tasks to function properly.

Create an analysis directory somewhere in your userdata (usually one analyzed observation has > 1 GB so don't use your home).
Set the following environment variables:

setenv SAS_ODF DIR - where DIR is the observation data path from above.
setenv SAS_CCF ANALYSIS_DIR/ccf.cif - where ANALYSIS_DIR is your directory for the analysis (on userdata), you have to add '/ccf.cif' to this path. This will create the ccf.cif file in your directory when running cifbuild
setenv CALDB_ESAS /userdata/data/knies/XMM/CALDB_ESAS (*)
* You need additional calibration files for ESAS. The latest version can be found at /userdata/data/knies/XMM/CALDB_ESAS. Please use this directory instead of downloading it again to safe disk space.

Next you have to run the basic tasks to prepare the data, but with some different options since we are working in the remeis environment:

cifbuild withccfpath=no analysisdate=now category=XMMCCF calindexset=$SAS_CCF fullpath=yes
odfingest outdir=ANALYSIS_DIR

''Important'': you can't move your files after running these steps or you will get errors.

After odfingest is finished there should be a file ending with "SUM.SAS" in your directory. Note the filename and re-set the SAS_ODF variable:

setenv SAS_ODF ANALYSIS_DIR/*SUM.SAS - replace *SUM.SAS with the filename in your directory

After this step you can follow the ESAS manual normally, starting with [https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html#SECTION00082000000000000000].
Note that you have to do cifbuild and odfingest only once (and also when SAS was updated) but you have to set the environment variables each time you open a new terminal.
You can make a small shell script which you can execute each time before you continue your analysis to speed this up, e.g.:

#!/bin/tcsh -f
source $SOFTDIR/sas_init.csh
setenv SAS_ODF ANALYSIS_DIR/*SUM.SAS
setenv SAS_CCF ANALYSIS_DIR/ccf.cif
setenv CALDB_ESAS /userdata/data/knies/XMM/CALDB_ESAS

Replace the directories etc. like shown above, make your script executable with chmod +x scriptfile and then execute it with ./scriptfile.

[[Category:Data Extraction]]

Xmm

2025-08-12T10:05:33Z

Nekrasov: /* Data */

== Data ==

Always use the remeis archives at /eu/X-ray/XMM/data/ instead of downloading observation files yourself. You can search for the data of an observation by typing something like '''find /eu/X-ray/xmm/data/????/obsID/odf -type d''' - replacing obsID with your observation ID.
If the observation you want to analyze is not in the archives: contact the XMM admin (Outdated: [[User:Nekrasov|Nekrasov]] ([[User talk:Nekrasov|talk]])Jonathan Knies[[User:Nekrasov|Nekrasov]] ([[User talk:Nekrasov|talk]]), [[User:Nekrasov|Nekrasov]] ([[User talk:Nekrasov|talk]])Amy Joyce[[User:Nekrasov|Nekrasov]] ([[User talk:Nekrasov|talk]])) ??Esin Gulbahar?? and the observation will be downloaded for you.

Note (as of 12.08.2025): since xmmsas version 22 we cannot run it natively on the cluster. Instead, we have a docker image for this. Otherwise, downgrade xmmsas to version 21 "module load xmmsas/21" if you want to use the algorithm below.

== XMM EPIC Data Extraction ==

After the system was updated from Ubuntu 11 to Ubuntu 12 a problem occured with the function "dssetattr" inside the "epchain".
This function can set/add an attribute to the HDU (Header/Data Unit).
The solution is to call
''''source $SOFTDIR/sas_init.csh''''
at the beginning of each script in order to initialize SAS inside your script.

A little example script:

#!/bin/csh
source $SOFTDIR/sas_init.csh # initialize the SAS software
set xmmscripts = ${XMMTOOLS} # make sure the proper xmmscripts are loaded

set obsid = '0147190101'
set datadir = /eu/X-ray/XMM/data/????/$obsid/odf

${xmmscripts}/xmmprepare --datadir=$datadir --prepdir=$obsid --pn # prepare the data
${xmmscripts}/xmmextract --prepdir=$obsid --pn --full # full extraction of the chip
${xmmscripts}/xmmextract --prepdir=$obsid --pn --srcreg=src.fits --bkgreg=bkg.fits # source and background extraction of the chip

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).

The xmmscripts need the region files to be fits files. You can convert them via
ds9tocxc outset=outfilename.fits < infilename.reg

For simple extractions of point sources creating region files is not necessary, you can just give the position of the source and background region as well as their extraction radii with the "--ra", "--dec" and "--bkgra", "--bkgdec" arguments.

"xmmextract" is a very powerful script, use its "--help" argument to get a list of all arguments.

Further important points:

# If your observation includes sub-observations, choose one of them. Do this with "onlyexp=1" not "onlyexp=PNU001" for example.
# 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:

example:

#!/bin/csh
${XMMTOOLS}/xmmprepare --datadir=/eu/X-ray/XMM/data/2290/0679780201/odf/
--prepdir=./test --pn --analysisdate=2014-01-11T01:05:00.000

== XMM OM Data Extraction ==

For extracting the data of the Optical Monitor (OM) onboard XMM, there exist three tools which do this automatically: ''omichain'', ''omfchain'' and ''omgchain''.
"i" stands for image mode, "f" for fast mode and "g" 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.
If you want to extract your images you first have to set some paths:

$source $SOFTDIR/sas_init.csh
$setenv SAS_ODF path_to_your_data #normally /eu/X-ray/XMM/data/rev/ObsID/odf/
$cifbuild
$setenv SAS_CCF ccf.cif
$odfingest
$setenv SAS_ODF `ls -1 *SUM.SAS`

After this you can run

$omichain #or omfchain, omgchain

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.
At the end you should have several images (<code>*IMAGE*</code>), region files (<code>*REGION*</code>) and source lists (<code>*SWSRLI*</code>) for the OM exposures and filters. The nomenclatur for the files are:

* IOOOOOOOOOODDUEEETTTTTTSXXX.FFF or POOOOOOOOOODDUEEETTTTTTSXXX.FFF (for PPS product files)
* OOOOOOOOOO = XMM-ObsID (10 characters)
* DD = Data source idetifier (here OM)
* U = exposure flag (S = sched, U = unsched, X = not aplicable)
* EEE = exposure number within the instrument observation (3 characters)
* TTTTTT = product type (6 characters)
* S = 0 or data subset number/character
* XXX = source number or slew step number (3 characters)
* FFF = file format (3 characters)

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.
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.

Then check the detector images (<code>P*IMAGE_*000.FIT</code>) 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 (<code>*REGION*000.ASC</code>, e.g. <code>P0090050801OMS006IMAGE_0000.FIT</code> -> ''I0090050801OMS006REGION0000.ASC</code>) and identify the number of your source.

[[File:image_region.jpeg|thumb]]

Look into the source list for your exposure (<code>P*SWSRLI*.FIT</code>) and note the SRC_ID in the last column. Open the combined source list (<code>*COMBO*</code>) and search for your SRC_ID. Here you can find all the magnitudes and fluxes of your source for the different filters.

== Choosing correct XMM-EPIC filter ==

Choosing the correct EPIC filter for your observation depends on the
visual magnitudes of the other objects (usually stars) in the EPIC
field of view.

The XMM user's handbook (sect. 3.3.6;
http://xmm.esac.esa.int/external/xmm_user_support/documentation/uhb/epicfilters.html) recommends:

Thick filter: suppress up to magnitudes of -2 to -1 (pn), or +1 to +4 (mos)

Medium filter: if there is nothing above magnitude ~ 6 to 9

Thin filter: for point sources that are 12 mag fainter than thick filter limitations

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.

Use the United States Naval Observatory catalog at
http://www.nofs.navy.mil/data/fchpix/ to find the stars within a 9'
radius.

At that website, enter your R.A. and Decl., and for the output file
options in the left column, unclick everything except RA,DEC,
magnitude, and offset from center. Then click 'retrieve data' in the
right column.

Next window: Click on "USNO B1.0 Star List" to download a gzipped
ASCII file with typically hundreds of rows/stars for lines of sight
away from the Galactic Plane (or many thousands of rows/stars for
lines of sight in the Galactic Plane).

Example file: See /home/markowitz/proposals/xmm2014/GS1826USNO for a
Galactic XRB, GS1826, located in the Galactic Bulge (optically-crowded
fields).

The star list is ordered by R.A., and but you can then re-order the ASCII list
by magnitude, e.g.,

cat GS1826USNO | grep -v '#' | awk '{print $7 " " $12}' | sort -g > starlist_sortB
cat GS1826USNO | grep -v '#' | awk '{print $8 " " $12}' | sort -g > starlist_sortR

since the B and R magnitudes are columns 7 and 8, and distance from the center
of f.o.v. (in arcsec) is column 12

Ignore the rows with zero magnitudes; a zero means unmeasured flux.

For these example files, e.g., /home/markowitz/proposals/xmm2014/starlist_sortB
we see that the brightest B- and R-band magnitudes are 10.0-10.3, including some
objects that are only 3-5' from the center, and at least one that's only 1.2'
from the center, so one cannot use the thin epic filter; one must use
the MEDIUM filter for all three EPIC cameras.

== XMM ESAS ==

If you are interested in diffuse X-ray emission it is recommended to use the XMM-Newton Extended Source Analysis Software.
The manual can be found at [https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html] with very detailed step-by-step instructions.

==== Working with XMM ESAS in the remeis environment ====

Before you start with the data analysis you have to source the SAS init via '''source $SOFTDIR/sas_init.csh'''.
Since you will need this every time you start a new terminal it is recommended to add an alias to your .cshrc in your home directory, e.g. '''alias setsas 'source $SOFTDIR/sas_init.csh''''.

First you have to find out the observation data path in the archives, which can be done by typing '''find /eu/X-ray/xmm/data/????/obsID/odf -type d''', where you replace obsID with your desired observation.
Next, you have to set up the environment variables for the SAS tasks to function properly.

Create an analysis directory somewhere in your userdata (usually one analyzed observation has > 1 GB so don't use your home).
Set the following environment variables:

setenv SAS_ODF DIR - where DIR is the observation data path from above.
setenv SAS_CCF ANALYSIS_DIR/ccf.cif - where ANALYSIS_DIR is your directory for the analysis (on userdata), you have to add '/ccf.cif' to this path. This will create the ccf.cif file in your directory when running cifbuild
setenv CALDB_ESAS /userdata/data/knies/XMM/CALDB_ESAS (*)
* You need additional calibration files for ESAS. The latest version can be found at /userdata/data/knies/XMM/CALDB_ESAS. Please use this directory instead of downloading it again to safe disk space.

Next you have to run the basic tasks to prepare the data, but with some different options since we are working in the remeis environment:

cifbuild withccfpath=no analysisdate=now category=XMMCCF calindexset=$SAS_CCF fullpath=yes
odfingest outdir=ANALYSIS_DIR

''Important'': you can't move your files after running these steps or you will get errors.

After odfingest is finished there should be a file ending with "SUM.SAS" in your directory. Note the filename and re-set the SAS_ODF variable:

setenv SAS_ODF ANALYSIS_DIR/*SUM.SAS - replace *SUM.SAS with the filename in your directory

After this step you can follow the ESAS manual normally, starting with [https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html#SECTION00082000000000000000].
Note that you have to do cifbuild and odfingest only once (and also when SAS was updated) but you have to set the environment variables each time you open a new terminal.
You can make a small shell script which you can execute each time before you continue your analysis to speed this up, e.g.:

#!/bin/tcsh -f
source $SOFTDIR/sas_init.csh
setenv SAS_ODF ANALYSIS_DIR/*SUM.SAS
setenv SAS_CCF ANALYSIS_DIR/ccf.cif
setenv CALDB_ESAS /userdata/data/knies/XMM/CALDB_ESAS

Replace the directories etc. like shown above, make your script executable with chmod +x scriptfile and then execute it with ./scriptfile.

[[Category:Data Extraction]]

Xmm

2025-08-12T10:02:28Z

Nekrasov: /* Data */

== Data ==

Always use the remeis archives at /eu/X-ray/XMM/data/ instead of downloading observation files yourself. You can search for the data of an observation by typing something like '''find /eu/X-ray/xmm/data/????/obsID/odf -type d''' - replacing obsID with your observation ID.
If the observation you want to analyze is not in the archives: contact the XMM admin (Outdated: {{strikethrough|Jonathan Knies}}, {{strikethrough|Amy Joyce}}) ??Esin Gulbahar?? and the observation will be downloaded for you.

Note (as of 12.08.2025): since xmmsas version 22 we cannot run it natively on the cluster. Instead, we have a docker image for this. Otherwise, downgrade xmmsas to version 21 "module load xmmsas/21" if you want to use the algorithm below.

== XMM EPIC Data Extraction ==

After the system was updated from Ubuntu 11 to Ubuntu 12 a problem occured with the function "dssetattr" inside the "epchain".
This function can set/add an attribute to the HDU (Header/Data Unit).
The solution is to call
''''source $SOFTDIR/sas_init.csh''''
at the beginning of each script in order to initialize SAS inside your script.

A little example script:

#!/bin/csh
source $SOFTDIR/sas_init.csh # initialize the SAS software
set xmmscripts = ${XMMTOOLS} # make sure the proper xmmscripts are loaded

set obsid = '0147190101'
set datadir = /eu/X-ray/XMM/data/????/$obsid/odf

${xmmscripts}/xmmprepare --datadir=$datadir --prepdir=$obsid --pn # prepare the data
${xmmscripts}/xmmextract --prepdir=$obsid --pn --full # full extraction of the chip
${xmmscripts}/xmmextract --prepdir=$obsid --pn --srcreg=src.fits --bkgreg=bkg.fits # source and background extraction of the chip

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).

The xmmscripts need the region files to be fits files. You can convert them via
ds9tocxc outset=outfilename.fits < infilename.reg

For simple extractions of point sources creating region files is not necessary, you can just give the position of the source and background region as well as their extraction radii with the "--ra", "--dec" and "--bkgra", "--bkgdec" arguments.

"xmmextract" is a very powerful script, use its "--help" argument to get a list of all arguments.

Further important points:

# If your observation includes sub-observations, choose one of them. Do this with "onlyexp=1" not "onlyexp=PNU001" for example.
# 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:

example:

#!/bin/csh
${XMMTOOLS}/xmmprepare --datadir=/eu/X-ray/XMM/data/2290/0679780201/odf/
--prepdir=./test --pn --analysisdate=2014-01-11T01:05:00.000

== XMM OM Data Extraction ==

For extracting the data of the Optical Monitor (OM) onboard XMM, there exist three tools which do this automatically: ''omichain'', ''omfchain'' and ''omgchain''.
"i" stands for image mode, "f" for fast mode and "g" 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.
If you want to extract your images you first have to set some paths:

$source $SOFTDIR/sas_init.csh
$setenv SAS_ODF path_to_your_data #normally /eu/X-ray/XMM/data/rev/ObsID/odf/
$cifbuild
$setenv SAS_CCF ccf.cif
$odfingest
$setenv SAS_ODF `ls -1 *SUM.SAS`

After this you can run

$omichain #or omfchain, omgchain

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.
At the end you should have several images (<code>*IMAGE*</code>), region files (<code>*REGION*</code>) and source lists (<code>*SWSRLI*</code>) for the OM exposures and filters. The nomenclatur for the files are:

* IOOOOOOOOOODDUEEETTTTTTSXXX.FFF or POOOOOOOOOODDUEEETTTTTTSXXX.FFF (for PPS product files)
* OOOOOOOOOO = XMM-ObsID (10 characters)
* DD = Data source idetifier (here OM)
* U = exposure flag (S = sched, U = unsched, X = not aplicable)
* EEE = exposure number within the instrument observation (3 characters)
* TTTTTT = product type (6 characters)
* S = 0 or data subset number/character
* XXX = source number or slew step number (3 characters)
* FFF = file format (3 characters)

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.
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.

Then check the detector images (<code>P*IMAGE_*000.FIT</code>) 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 (<code>*REGION*000.ASC</code>, e.g. <code>P0090050801OMS006IMAGE_0000.FIT</code> -> ''I0090050801OMS006REGION0000.ASC</code>) and identify the number of your source.

[[File:image_region.jpeg|thumb]]

Look into the source list for your exposure (<code>P*SWSRLI*.FIT</code>) and note the SRC_ID in the last column. Open the combined source list (<code>*COMBO*</code>) and search for your SRC_ID. Here you can find all the magnitudes and fluxes of your source for the different filters.

== Choosing correct XMM-EPIC filter ==

Choosing the correct EPIC filter for your observation depends on the
visual magnitudes of the other objects (usually stars) in the EPIC
field of view.

The XMM user's handbook (sect. 3.3.6;
http://xmm.esac.esa.int/external/xmm_user_support/documentation/uhb/epicfilters.html) recommends:

Thick filter: suppress up to magnitudes of -2 to -1 (pn), or +1 to +4 (mos)

Medium filter: if there is nothing above magnitude ~ 6 to 9

Thin filter: for point sources that are 12 mag fainter than thick filter limitations

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.

Use the United States Naval Observatory catalog at
http://www.nofs.navy.mil/data/fchpix/ to find the stars within a 9'
radius.

At that website, enter your R.A. and Decl., and for the output file
options in the left column, unclick everything except RA,DEC,
magnitude, and offset from center. Then click 'retrieve data' in the
right column.

Next window: Click on "USNO B1.0 Star List" to download a gzipped
ASCII file with typically hundreds of rows/stars for lines of sight
away from the Galactic Plane (or many thousands of rows/stars for
lines of sight in the Galactic Plane).

Example file: See /home/markowitz/proposals/xmm2014/GS1826USNO for a
Galactic XRB, GS1826, located in the Galactic Bulge (optically-crowded
fields).

The star list is ordered by R.A., and but you can then re-order the ASCII list
by magnitude, e.g.,

cat GS1826USNO | grep -v '#' | awk '{print $7 " " $12}' | sort -g > starlist_sortB
cat GS1826USNO | grep -v '#' | awk '{print $8 " " $12}' | sort -g > starlist_sortR

since the B and R magnitudes are columns 7 and 8, and distance from the center
of f.o.v. (in arcsec) is column 12

Ignore the rows with zero magnitudes; a zero means unmeasured flux.

For these example files, e.g., /home/markowitz/proposals/xmm2014/starlist_sortB
we see that the brightest B- and R-band magnitudes are 10.0-10.3, including some
objects that are only 3-5' from the center, and at least one that's only 1.2'
from the center, so one cannot use the thin epic filter; one must use
the MEDIUM filter for all three EPIC cameras.

== XMM ESAS ==

If you are interested in diffuse X-ray emission it is recommended to use the XMM-Newton Extended Source Analysis Software.
The manual can be found at [https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html] with very detailed step-by-step instructions.

==== Working with XMM ESAS in the remeis environment ====

Before you start with the data analysis you have to source the SAS init via '''source $SOFTDIR/sas_init.csh'''.
Since you will need this every time you start a new terminal it is recommended to add an alias to your .cshrc in your home directory, e.g. '''alias setsas 'source $SOFTDIR/sas_init.csh''''.

First you have to find out the observation data path in the archives, which can be done by typing '''find /eu/X-ray/xmm/data/????/obsID/odf -type d''', where you replace obsID with your desired observation.
Next, you have to set up the environment variables for the SAS tasks to function properly.

Create an analysis directory somewhere in your userdata (usually one analyzed observation has > 1 GB so don't use your home).
Set the following environment variables:

setenv SAS_ODF DIR - where DIR is the observation data path from above.
setenv SAS_CCF ANALYSIS_DIR/ccf.cif - where ANALYSIS_DIR is your directory for the analysis (on userdata), you have to add '/ccf.cif' to this path. This will create the ccf.cif file in your directory when running cifbuild
setenv CALDB_ESAS /userdata/data/knies/XMM/CALDB_ESAS (*)
* You need additional calibration files for ESAS. The latest version can be found at /userdata/data/knies/XMM/CALDB_ESAS. Please use this directory instead of downloading it again to safe disk space.

Next you have to run the basic tasks to prepare the data, but with some different options since we are working in the remeis environment:

cifbuild withccfpath=no analysisdate=now category=XMMCCF calindexset=$SAS_CCF fullpath=yes
odfingest outdir=ANALYSIS_DIR

''Important'': you can't move your files after running these steps or you will get errors.

After odfingest is finished there should be a file ending with "SUM.SAS" in your directory. Note the filename and re-set the SAS_ODF variable:

setenv SAS_ODF ANALYSIS_DIR/*SUM.SAS - replace *SUM.SAS with the filename in your directory

After this step you can follow the ESAS manual normally, starting with [https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html#SECTION00082000000000000000].
Note that you have to do cifbuild and odfingest only once (and also when SAS was updated) but you have to set the environment variables each time you open a new terminal.
You can make a small shell script which you can execute each time before you continue your analysis to speed this up, e.g.:

#!/bin/tcsh -f
source $SOFTDIR/sas_init.csh
setenv SAS_ODF ANALYSIS_DIR/*SUM.SAS
setenv SAS_CCF ANALYSIS_DIR/ccf.cif
setenv CALDB_ESAS /userdata/data/knies/XMM/CALDB_ESAS

Replace the directories etc. like shown above, make your script executable with chmod +x scriptfile and then execute it with ./scriptfile.

[[Category:Data Extraction]]

Xmm

2025-08-12T09:56:17Z

Nekrasov: /* Data */

== Data ==

Always use the remeis archives at /eu/X-ray/XMM/data/ instead of downloading observation files yourself. You can search for the data of an observation by typing something like '''find /eu/X-ray/xmm/data/????/obsID/odf -type d''' - replacing obsID with your observation ID.
If the observation you want to analyze is not in the archives: contact the XMM admin (Outdated: ~~Jonathan Knies~~, ~~Amy Joyce~~) ??Esin Gulbahar?? and the observation will be downloaded for you.

Note (as of 12.08.2025): since xmmsas version 22 we cannot run it natively on the cluster. Instead, we have a docker image for this. Otherwise, downgrade xmmsas to version 21 "module load xmmsas/21" if you want to use the algorithm below.

== XMM EPIC Data Extraction ==

After the system was updated from Ubuntu 11 to Ubuntu 12 a problem occured with the function "dssetattr" inside the "epchain".
This function can set/add an attribute to the HDU (Header/Data Unit).
The solution is to call
''''source $SOFTDIR/sas_init.csh''''
at the beginning of each script in order to initialize SAS inside your script.

A little example script:

#!/bin/csh
source $SOFTDIR/sas_init.csh # initialize the SAS software
set xmmscripts = ${XMMTOOLS} # make sure the proper xmmscripts are loaded

set obsid = '0147190101'
set datadir = /eu/X-ray/XMM/data/????/$obsid/odf

${xmmscripts}/xmmprepare --datadir=$datadir --prepdir=$obsid --pn # prepare the data
${xmmscripts}/xmmextract --prepdir=$obsid --pn --full # full extraction of the chip
${xmmscripts}/xmmextract --prepdir=$obsid --pn --srcreg=src.fits --bkgreg=bkg.fits # source and background extraction of the chip

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).

The xmmscripts need the region files to be fits files. You can convert them via
ds9tocxc outset=outfilename.fits < infilename.reg

For simple extractions of point sources creating region files is not necessary, you can just give the position of the source and background region as well as their extraction radii with the "--ra", "--dec" and "--bkgra", "--bkgdec" arguments.

"xmmextract" is a very powerful script, use its "--help" argument to get a list of all arguments.

Further important points:

# If your observation includes sub-observations, choose one of them. Do this with "onlyexp=1" not "onlyexp=PNU001" for example.
# 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:

example:

#!/bin/csh
${XMMTOOLS}/xmmprepare --datadir=/eu/X-ray/XMM/data/2290/0679780201/odf/
--prepdir=./test --pn --analysisdate=2014-01-11T01:05:00.000

== XMM OM Data Extraction ==

For extracting the data of the Optical Monitor (OM) onboard XMM, there exist three tools which do this automatically: ''omichain'', ''omfchain'' and ''omgchain''.
"i" stands for image mode, "f" for fast mode and "g" 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.
If you want to extract your images you first have to set some paths:

$source $SOFTDIR/sas_init.csh
$setenv SAS_ODF path_to_your_data #normally /eu/X-ray/XMM/data/rev/ObsID/odf/
$cifbuild
$setenv SAS_CCF ccf.cif
$odfingest
$setenv SAS_ODF `ls -1 *SUM.SAS`

After this you can run

$omichain #or omfchain, omgchain

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.
At the end you should have several images (<code>*IMAGE*</code>), region files (<code>*REGION*</code>) and source lists (<code>*SWSRLI*</code>) for the OM exposures and filters. The nomenclatur for the files are:

* IOOOOOOOOOODDUEEETTTTTTSXXX.FFF or POOOOOOOOOODDUEEETTTTTTSXXX.FFF (for PPS product files)
* OOOOOOOOOO = XMM-ObsID (10 characters)
* DD = Data source idetifier (here OM)
* U = exposure flag (S = sched, U = unsched, X = not aplicable)
* EEE = exposure number within the instrument observation (3 characters)
* TTTTTT = product type (6 characters)
* S = 0 or data subset number/character
* XXX = source number or slew step number (3 characters)
* FFF = file format (3 characters)

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.
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.

Then check the detector images (<code>P*IMAGE_*000.FIT</code>) 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 (<code>*REGION*000.ASC</code>, e.g. <code>P0090050801OMS006IMAGE_0000.FIT</code> -> ''I0090050801OMS006REGION0000.ASC</code>) and identify the number of your source.

[[File:image_region.jpeg|thumb]]

Look into the source list for your exposure (<code>P*SWSRLI*.FIT</code>) and note the SRC_ID in the last column. Open the combined source list (<code>*COMBO*</code>) and search for your SRC_ID. Here you can find all the magnitudes and fluxes of your source for the different filters.

== Choosing correct XMM-EPIC filter ==

Choosing the correct EPIC filter for your observation depends on the
visual magnitudes of the other objects (usually stars) in the EPIC
field of view.

The XMM user's handbook (sect. 3.3.6;
http://xmm.esac.esa.int/external/xmm_user_support/documentation/uhb/epicfilters.html) recommends:

Thick filter: suppress up to magnitudes of -2 to -1 (pn), or +1 to +4 (mos)

Medium filter: if there is nothing above magnitude ~ 6 to 9

Thin filter: for point sources that are 12 mag fainter than thick filter limitations

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.

Use the United States Naval Observatory catalog at
http://www.nofs.navy.mil/data/fchpix/ to find the stars within a 9'
radius.

At that website, enter your R.A. and Decl., and for the output file
options in the left column, unclick everything except RA,DEC,
magnitude, and offset from center. Then click 'retrieve data' in the
right column.

Next window: Click on "USNO B1.0 Star List" to download a gzipped
ASCII file with typically hundreds of rows/stars for lines of sight
away from the Galactic Plane (or many thousands of rows/stars for
lines of sight in the Galactic Plane).

Example file: See /home/markowitz/proposals/xmm2014/GS1826USNO for a
Galactic XRB, GS1826, located in the Galactic Bulge (optically-crowded
fields).

The star list is ordered by R.A., and but you can then re-order the ASCII list
by magnitude, e.g.,

cat GS1826USNO | grep -v '#' | awk '{print $7 " " $12}' | sort -g > starlist_sortB
cat GS1826USNO | grep -v '#' | awk '{print $8 " " $12}' | sort -g > starlist_sortR

since the B and R magnitudes are columns 7 and 8, and distance from the center
of f.o.v. (in arcsec) is column 12

Ignore the rows with zero magnitudes; a zero means unmeasured flux.

For these example files, e.g., /home/markowitz/proposals/xmm2014/starlist_sortB
we see that the brightest B- and R-band magnitudes are 10.0-10.3, including some
objects that are only 3-5' from the center, and at least one that's only 1.2'
from the center, so one cannot use the thin epic filter; one must use
the MEDIUM filter for all three EPIC cameras.

== XMM ESAS ==

If you are interested in diffuse X-ray emission it is recommended to use the XMM-Newton Extended Source Analysis Software.
The manual can be found at [https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html] with very detailed step-by-step instructions.

==== Working with XMM ESAS in the remeis environment ====

Before you start with the data analysis you have to source the SAS init via '''source $SOFTDIR/sas_init.csh'''.
Since you will need this every time you start a new terminal it is recommended to add an alias to your .cshrc in your home directory, e.g. '''alias setsas 'source $SOFTDIR/sas_init.csh''''.

First you have to find out the observation data path in the archives, which can be done by typing '''find /eu/X-ray/xmm/data/????/obsID/odf -type d''', where you replace obsID with your desired observation.
Next, you have to set up the environment variables for the SAS tasks to function properly.

Create an analysis directory somewhere in your userdata (usually one analyzed observation has > 1 GB so don't use your home).
Set the following environment variables:

setenv SAS_ODF DIR - where DIR is the observation data path from above.
setenv SAS_CCF ANALYSIS_DIR/ccf.cif - where ANALYSIS_DIR is your directory for the analysis (on userdata), you have to add '/ccf.cif' to this path. This will create the ccf.cif file in your directory when running cifbuild
setenv CALDB_ESAS /userdata/data/knies/XMM/CALDB_ESAS (*)
* You need additional calibration files for ESAS. The latest version can be found at /userdata/data/knies/XMM/CALDB_ESAS. Please use this directory instead of downloading it again to safe disk space.

Next you have to run the basic tasks to prepare the data, but with some different options since we are working in the remeis environment:

cifbuild withccfpath=no analysisdate=now category=XMMCCF calindexset=$SAS_CCF fullpath=yes
odfingest outdir=ANALYSIS_DIR

''Important'': you can't move your files after running these steps or you will get errors.

After odfingest is finished there should be a file ending with "SUM.SAS" in your directory. Note the filename and re-set the SAS_ODF variable:

setenv SAS_ODF ANALYSIS_DIR/*SUM.SAS - replace *SUM.SAS with the filename in your directory

After this step you can follow the ESAS manual normally, starting with [https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html#SECTION00082000000000000000].
Note that you have to do cifbuild and odfingest only once (and also when SAS was updated) but you have to set the environment variables each time you open a new terminal.
You can make a small shell script which you can execute each time before you continue your analysis to speed this up, e.g.:

#!/bin/tcsh -f
source $SOFTDIR/sas_init.csh
setenv SAS_ODF ANALYSIS_DIR/*SUM.SAS
setenv SAS_CCF ANALYSIS_DIR/ccf.cif
setenv CALDB_ESAS /userdata/data/knies/XMM/CALDB_ESAS

Replace the directories etc. like shown above, make your script executable with chmod +x scriptfile and then execute it with ./scriptfile.

[[Category:Data Extraction]]

Xmm

2025-08-11T13:11:08Z

Nekrasov: /* Data */

== Data ==

Always use the remeis archives at /eu/X-ray/XMM/data/ instead of downloading observation files yourself. You can search for the data of an observation by typing something like '''find /eu/X-ray/xmm/data/????/obsID/odf -type d''' - replacing obsID with your observation ID.
If the observation you want to analyze is not in the archives: contact the XMM admin (Jonathan Knies - !outdated person!) and the observation will be downloaded for you.

== XMM EPIC Data Extraction ==

After the system was updated from Ubuntu 11 to Ubuntu 12 a problem occured with the function "dssetattr" inside the "epchain".
This function can set/add an attribute to the HDU (Header/Data Unit).
The solution is to call
''''source $SOFTDIR/sas_init.csh''''
at the beginning of each script in order to initialize SAS inside your script.

A little example script:

#!/bin/csh
source $SOFTDIR/sas_init.csh # initialize the SAS software
set xmmscripts = ${XMMTOOLS} # make sure the proper xmmscripts are loaded

set obsid = '0147190101'
set datadir = /eu/X-ray/XMM/data/????/$obsid/odf

${xmmscripts}/xmmprepare --datadir=$datadir --prepdir=$obsid --pn # prepare the data
${xmmscripts}/xmmextract --prepdir=$obsid --pn --full # full extraction of the chip
${xmmscripts}/xmmextract --prepdir=$obsid --pn --srcreg=src.fits --bkgreg=bkg.fits # source and background extraction of the chip

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).

The xmmscripts need the region files to be fits files. You can convert them via
ds9tocxc outset=outfilename.fits < infilename.reg

For simple extractions of point sources creating region files is not necessary, you can just give the position of the source and background region as well as their extraction radii with the "--ra", "--dec" and "--bkgra", "--bkgdec" arguments.

"xmmextract" is a very powerful script, use its "--help" argument to get a list of all arguments.

Further important points:

# If your observation includes sub-observations, choose one of them. Do this with "onlyexp=1" not "onlyexp=PNU001" for example.
# 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:

example:

#!/bin/csh
${XMMTOOLS}/xmmprepare --datadir=/eu/X-ray/XMM/data/2290/0679780201/odf/
--prepdir=./test --pn --analysisdate=2014-01-11T01:05:00.000

== XMM OM Data Extraction ==

For extracting the data of the Optical Monitor (OM) onboard XMM, there exist three tools which do this automatically: ''omichain'', ''omfchain'' and ''omgchain''.
"i" stands for image mode, "f" for fast mode and "g" 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.
If you want to extract your images you first have to set some paths:

$source $SOFTDIR/sas_init.csh
$setenv SAS_ODF path_to_your_data #normally /eu/X-ray/XMM/data/rev/ObsID/odf/
$cifbuild
$setenv SAS_CCF ccf.cif
$odfingest
$setenv SAS_ODF `ls -1 *SUM.SAS`

After this you can run

$omichain #or omfchain, omgchain

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.
At the end you should have several images (<code>*IMAGE*</code>), region files (<code>*REGION*</code>) and source lists (<code>*SWSRLI*</code>) for the OM exposures and filters. The nomenclatur for the files are:

* IOOOOOOOOOODDUEEETTTTTTSXXX.FFF or POOOOOOOOOODDUEEETTTTTTSXXX.FFF (for PPS product files)
* OOOOOOOOOO = XMM-ObsID (10 characters)
* DD = Data source idetifier (here OM)
* U = exposure flag (S = sched, U = unsched, X = not aplicable)
* EEE = exposure number within the instrument observation (3 characters)
* TTTTTT = product type (6 characters)
* S = 0 or data subset number/character
* XXX = source number or slew step number (3 characters)
* FFF = file format (3 characters)

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.
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.

Then check the detector images (<code>P*IMAGE_*000.FIT</code>) 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 (<code>*REGION*000.ASC</code>, e.g. <code>P0090050801OMS006IMAGE_0000.FIT</code> -> ''I0090050801OMS006REGION0000.ASC</code>) and identify the number of your source.

[[File:image_region.jpeg|thumb]]

Look into the source list for your exposure (<code>P*SWSRLI*.FIT</code>) and note the SRC_ID in the last column. Open the combined source list (<code>*COMBO*</code>) and search for your SRC_ID. Here you can find all the magnitudes and fluxes of your source for the different filters.

== Choosing correct XMM-EPIC filter ==

Choosing the correct EPIC filter for your observation depends on the
visual magnitudes of the other objects (usually stars) in the EPIC
field of view.

The XMM user's handbook (sect. 3.3.6;
http://xmm.esac.esa.int/external/xmm_user_support/documentation/uhb/epicfilters.html) recommends:

Thick filter: suppress up to magnitudes of -2 to -1 (pn), or +1 to +4 (mos)

Medium filter: if there is nothing above magnitude ~ 6 to 9

Thin filter: for point sources that are 12 mag fainter than thick filter limitations

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.

Use the United States Naval Observatory catalog at
http://www.nofs.navy.mil/data/fchpix/ to find the stars within a 9'
radius.

At that website, enter your R.A. and Decl., and for the output file
options in the left column, unclick everything except RA,DEC,
magnitude, and offset from center. Then click 'retrieve data' in the
right column.

Next window: Click on "USNO B1.0 Star List" to download a gzipped
ASCII file with typically hundreds of rows/stars for lines of sight
away from the Galactic Plane (or many thousands of rows/stars for
lines of sight in the Galactic Plane).

Example file: See /home/markowitz/proposals/xmm2014/GS1826USNO for a
Galactic XRB, GS1826, located in the Galactic Bulge (optically-crowded
fields).

The star list is ordered by R.A., and but you can then re-order the ASCII list
by magnitude, e.g.,

cat GS1826USNO | grep -v '#' | awk '{print $7 " " $12}' | sort -g > starlist_sortB
cat GS1826USNO | grep -v '#' | awk '{print $8 " " $12}' | sort -g > starlist_sortR

since the B and R magnitudes are columns 7 and 8, and distance from the center
of f.o.v. (in arcsec) is column 12

Ignore the rows with zero magnitudes; a zero means unmeasured flux.

For these example files, e.g., /home/markowitz/proposals/xmm2014/starlist_sortB
we see that the brightest B- and R-band magnitudes are 10.0-10.3, including some
objects that are only 3-5' from the center, and at least one that's only 1.2'
from the center, so one cannot use the thin epic filter; one must use
the MEDIUM filter for all three EPIC cameras.

== XMM ESAS ==

If you are interested in diffuse X-ray emission it is recommended to use the XMM-Newton Extended Source Analysis Software.
The manual can be found at [https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html] with very detailed step-by-step instructions.

==== Working with XMM ESAS in the remeis environment ====

Before you start with the data analysis you have to source the SAS init via '''source $SOFTDIR/sas_init.csh'''.
Since you will need this every time you start a new terminal it is recommended to add an alias to your .cshrc in your home directory, e.g. '''alias setsas 'source $SOFTDIR/sas_init.csh''''.

First you have to find out the observation data path in the archives, which can be done by typing '''find /eu/X-ray/xmm/data/????/obsID/odf -type d''', where you replace obsID with your desired observation.
Next, you have to set up the environment variables for the SAS tasks to function properly.

Create an analysis directory somewhere in your userdata (usually one analyzed observation has > 1 GB so don't use your home).
Set the following environment variables:

setenv SAS_ODF DIR - where DIR is the observation data path from above.
setenv SAS_CCF ANALYSIS_DIR/ccf.cif - where ANALYSIS_DIR is your directory for the analysis (on userdata), you have to add '/ccf.cif' to this path. This will create the ccf.cif file in your directory when running cifbuild
setenv CALDB_ESAS /userdata/data/knies/XMM/CALDB_ESAS (*)
* You need additional calibration files for ESAS. The latest version can be found at /userdata/data/knies/XMM/CALDB_ESAS. Please use this directory instead of downloading it again to safe disk space.

Next you have to run the basic tasks to prepare the data, but with some different options since we are working in the remeis environment:

cifbuild withccfpath=no analysisdate=now category=XMMCCF calindexset=$SAS_CCF fullpath=yes
odfingest outdir=ANALYSIS_DIR

''Important'': you can't move your files after running these steps or you will get errors.

After odfingest is finished there should be a file ending with "SUM.SAS" in your directory. Note the filename and re-set the SAS_ODF variable:

setenv SAS_ODF ANALYSIS_DIR/*SUM.SAS - replace *SUM.SAS with the filename in your directory

After this step you can follow the ESAS manual normally, starting with [https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html#SECTION00082000000000000000].
Note that you have to do cifbuild and odfingest only once (and also when SAS was updated) but you have to set the environment variables each time you open a new terminal.
You can make a small shell script which you can execute each time before you continue your analysis to speed this up, e.g.:

#!/bin/tcsh -f
source $SOFTDIR/sas_init.csh
setenv SAS_ODF ANALYSIS_DIR/*SUM.SAS
setenv SAS_CCF ANALYSIS_DIR/ccf.cif
setenv CALDB_ESAS /userdata/data/knies/XMM/CALDB_ESAS

Replace the directories etc. like shown above, make your script executable with chmod +x scriptfile and then execute it with ./scriptfile.

[[Category:Data Extraction]]

Travel

2025-05-13T14:19:39Z

Nekrasov: /* Application for business travel */

[[Category:Internal]]

This page documents how to apply for business travel and hand in the reimbursement with the online tool accessible through [https://www.mitarbeiterservice.bayern.de/ authega]. This requires you to have an account set up. If you sign up for the first time you will be send a letter (! yes, physical letter, this can take some days) with information for the login. For further logins it is best to use a certificate file with a password.

Once logged in you can access the travel management (Reisekostenmanagement, RMS) and enter the necessary information there. Certain numbers are tied to the observatory and will always be the same, they are documented below. '''Note:''' When selecting the institution (Beschäftigungsbehöde) do '''not''' use the Remeis-Observatory or any other smaller body. Instead use the general FAU entry with the number '''1519016'''! In the field '''Kapitel''' enter '''1519'''!

More information for the general setup are in the [[:Media:introduction_bayrms.pdf|introductory slides]] (this is the German version, see below for additional guidance in English).

In order to receive documents per email you need to sign the [[:Media:Bayrms_data_protection.pdf|data protection waiver]] (in German!) and hand it in (in paper form!).

== Application for business travel ==

Some notes on filling in these forms:

=== Travel days (Reisetage) ===
On each day, you need to input the start and end of your "business".
If you are, say attending a conference starting Monday at 2 PM and ending on a Friday at noon, your times should look like this:
* Monday: Start at 14:00, end at '''23:59'''
* Tue-Thur: Start at '''0:00''', end at '''23:59'''
* Fri: Start at '''0:00''', end at 12:00

The point here being that you are still there "on business" even outside the main conference hours. Weekends are also part of the trip, if the conference is more than one week long, so this is not "private time" in this form ((c) - Joern)

(NB: There are still discussions between the administration and Joern about this)

=== Meals ===
If food is provided by hotel/conference and you do not pay for it extra - make the corresponding mark in the day

=== Mitzeichner (Signatory, in the very end of the form) ===
This needs to be your boss, who will then forward it to P6.

=== Mitreisende ===
Only employees of Bavaria (e.g., if you drive from work with someone)

=== Hotel costs ===
It is good if you have some proof why you have taken this particular option. Get some documentation (e.g., print web-page with costs) at the moment of booking, which would display other possible options in this hotel or in other hotels around.

If you travel with family, you will not be reimbursed for the difference between the single room and the room you've taken (e.g., double).

=== Reimbursement in advance ===
If you need to be reimbursed in advance. After approval of the trip, print the trip summary and talk to Edith.

== Handing in reimbursement ==

== List of project funds ==

Below is a list of project funds that you travel might be payed from. '''Before submitting your reimbursement form ask your supervisor what project to use! Every time!'''

{| class="wikitable" style="margin:auto"
|+ Project numbers
|-
! Name !! Erweiterung !! Titel !! AWK !! Kostenstelle
|-
| DLR 50 OR 2309 (VF-ULX) || 7401 171 || 547 41 || || 1415151100
|-
| DLR 50 OO 2417 (THESEUS) || 7401 182 || 547 41 || || 1415151100
|-
| DLR 50 OR 2410 (VF-XMM Aafia) || 7401 186 || 547 41 || || 1415151100
|-
| DLR 50 QR 2503 (eROSITA) || 7401 188 || 547 41 || || 1415151100
|-
| DLR 50 QR 2508 (ATHENA) || 7401 191 || 547 41 || || 1415151100
|-
| DLR 50 OO 2507 (AXIS) || 7401 196 || 547 41 || || 1415151100
|-
| || || || ||
|-
| DFG WI 1860/17-2 (eRO STEP 1, P5) || 7458 208 || 547 41 || || 1415151100
|-
| DFG WI 1860/19-1 (eRO STEP 1, P6) || 7458 046 || 547 41 || || 1415151100
|-
| DFG WI 1860/20-1 (FOR 5195, P2) || 7458 065 || 547 41 || || 1415151100
|-
| DFG WI 1860/21-1 (eRO STEP 2, P7) || 7458 209 || 547 41 || || 1415151100
|-
| || || || ||
|-
| DFG overhead WI bis 2022 || 5002344 || 547 40 || PPS || 1415151100
|-
| DFG overhead WI ab 2023 || 150234 || 547 40 || PPS || 1415151100
|-
| || || || ||
|-
| ESA (DALI) || 7402 745 || 547 41 || || 1415151100
|-
| Wlms Altprojekte || 7402 304 || 547 41 || || 1415151100
|-
| ETI Förderung || 5500 245 || 547 41 || || 1415151100
|-
| || || || ||
|-
| DFG SA 2131/13-2 (eRO STEP 2, P1) || 7458 204 || 547 41 || || 1415150013
|-
| DFG SA 2131/14-2 (eRO STEP 2, P2) || 7458 205 || 547 41 || || 1415150013
|-
| DFG SA 2131/15-2 (eRO STEP 2, TP Z) || 7458 206 || 547 41 || || 1415150013
|-
| DFG SA 2131/18-1 (eROSITA Galaxien) || 7458 168 || 547 41 || || 1415150013
|-
| || || || ||
|-
| DFG overhead SA (Altprojekte) || 7459 704 || 547 41 || || 1415150013
|-
| DFG overhead SA bis 2022 || 5002391 || 547 40 || PPS || 1415150013
|-
| DFG overhead SA ab 2023 || 0150178 || 547 40 || PPS || 1415150013
|-
| || || || ||
|-
| DFG SA 4388/2-1 (Saeedi) || 7458 207 || 547 41 || || 1415150013
|-
| DFG MA 11073/1-1 (Mayer) || 7458 221 || 547 41 || || 1415150013
|-
| DFG HE 1356/70-2 (Heber) || 7458 225 || 547 41 || || 1415150000
|-
| || || || ||
|-
| 73er Titel || 061 000-6 || 547 40 || FuL || 1415150000
|-
| 72er Titel || 806 3141 || 547 41 || || 1415150000
|}

Additionally you need to specify the kind of expense (Kostenart): 685000. If the AWK is empty in the table above, do not put anything in the '''Info 1''' field. Otherwise add the given symbol.

== English information ==

Here are some PDFs you might find helpful to navigate through the German landscape of bureaucracy.

Some [[:Media:Additional_information_BayRMS.pdf|additional information]] in Englisch

The [[:Media:Bayrms_eng_data_protection.pdf|data protection waiver]] (you still have to sign the German one!)

The [[:Media:Bayrms_eng_introduction_slides.pdf|introduction slides]]

A [[:Media:Bayrms_glossary.pdf|glossary]] to match English and German terms. (REALLY HELPFUL, CONTAINS INFORMATION TO INSERT)

== ''OUTDATED!'' Business and private travels ==

If you intend to combine a business trip with a vacation to save money or just because of the occasion, you need to observe a couple of issues:

* first of all, combining business and private travel is in principle nothing that the university likes
* you *need* to get the private travel authorized on the travel request form, i.e. you need to state *both* on travel request form
* obviously you will not get any reimbursement for the private part of your trip, or any extra expenses arising from your vacation
* to get reimbursement for your business part of the trip, you need to document what the business part alone would have cost. In detail this means that you need to document:
* fictitious cost of flights/train tickets/rental car/etc for the business part of the trip
* fictitious cost of flights/train tickets/etc to and from the business destination of the trip
* nevertheless you also obviously need to state your actual cost (flight tickets etc).
* the university will reimburse you only the *lesser* of your actual cost and the fictitious cost!\\ This means that if your flight would have cost 1000 Eur, but because you stayed longer for private reasons (i.e. over the weekend) and the actual flight is cheaper like 700 Eur, the university will only reimburse you 700 Eur.

Furthermore apart from the reimbursement by the university, you have also to consider the taxes: the fiscal authorities might consider such a combination of business and private trip entirely private and therefore the reimbursement as additional income. So far,
this has never happened in Bamberg to Jörns knowledge, but in principle tax
regulations state that for a trip to count as a business trip, the
business portion must outbalance the private portion. To give an
example: a 3d observing run in Australia followed by a 2 week vacation
there would probably not be seen as a business related trip (even if it
was!), even though the university would reimburse you for your flights
and the 3d per diem.
((Based on a FAQ Email sent by Jörn to allusers on April 4, 2011))

Travel

2025-05-13T14:07:40Z

Nekrasov: /* English information */

[[Category:Internal]]

This page documents how to apply for business travel and hand in the reimbursement with the online tool accessible through [https://www.mitarbeiterservice.bayern.de/ authega]. This requires you to have an account set up. If you sign up for the first time you will be send a letter (! yes, physical letter, this can take some days) with information for the login. For further logins it is best to use a certificate file with a password.

Once logged in you can access the travel management (Reisekostenmanagement, RMS) and enter the necessary information there. Certain numbers are tied to the observatory and will always be the same, they are documented below. '''Note:''' When selecting the institution (Beschäftigungsbehöde) do '''not''' use the Remeis-Observatory or any other smaller body. Instead use the general FAU entry with the number '''1519016'''! In the field '''Kapitel''' enter '''1519'''!

More information for the general setup are in the [[:Media:introduction_bayrms.pdf|introductory slides]] (this is the German version, see below for additional guidance in English).

In order to receive documents per email you need to sign the [[:Media:Bayrms_data_protection.pdf|data protection waiver]] (in German!) and hand it in (in paper form!).

== Application for business travel ==

Some notes on filling in these forms:

=== Travel days (Reisetage) ===
On each day, you need to input the start and end of your "business".
If you are, say attending a conference starting Monday at 2 PM and ending on a Friday at noon, your times should look like this:
* Monday: Start at 14:00, end at '''23:59'''
* Tue-Thur: Start at '''0:00''', end at '''23:59'''
* Fri: Start at '''0:00''', end at 12:00

The point here being that you are still there "on business" even outside the main conference hours.

(NB: There are still discussions between the administration and Joern about this)

=== Mitzeichner (Signatory) ===
This needs to be your boss, who will then forward it to P6.

== Handing in reimbursement ==

== List of project funds ==

Below is a list of project funds that you travel might be payed from. '''Before submitting your reimbursement form ask your supervisor what project to use! Every time!'''

{| class="wikitable" style="margin:auto"
|+ Project numbers
|-
! Name !! Erweiterung !! Titel !! AWK !! Kostenstelle
|-
| DLR 50 OR 2309 (VF-ULX) || 7401 171 || 547 41 || || 1415151100
|-
| DLR 50 OO 2417 (THESEUS) || 7401 182 || 547 41 || || 1415151100
|-
| DLR 50 OR 2410 (VF-XMM Aafia) || 7401 186 || 547 41 || || 1415151100
|-
| DLR 50 QR 2503 (eROSITA) || 7401 188 || 547 41 || || 1415151100
|-
| DLR 50 QR 2508 (ATHENA) || 7401 191 || 547 41 || || 1415151100
|-
| DLR 50 OO 2507 (AXIS) || 7401 196 || 547 41 || || 1415151100
|-
| || || || ||
|-
| DFG WI 1860/17-2 (eRO STEP 1, P5) || 7458 208 || 547 41 || || 1415151100
|-
| DFG WI 1860/19-1 (eRO STEP 1, P6) || 7458 046 || 547 41 || || 1415151100
|-
| DFG WI 1860/20-1 (FOR 5195, P2) || 7458 065 || 547 41 || || 1415151100
|-
| DFG WI 1860/21-1 (eRO STEP 2, P7) || 7458 209 || 547 41 || || 1415151100
|-
| || || || ||
|-
| DFG overhead WI bis 2022 || 5002344 || 547 40 || PPS || 1415151100
|-
| DFG overhead WI ab 2023 || 150234 || 547 40 || PPS || 1415151100
|-
| || || || ||
|-
| ESA (DALI) || 7402 745 || 547 41 || || 1415151100
|-
| Wlms Altprojekte || 7402 304 || 547 41 || || 1415151100
|-
| ETI Förderung || 5500 245 || 547 41 || || 1415151100
|-
| || || || ||
|-
| DFG SA 2131/13-2 (eRO STEP 2, P1) || 7458 204 || 547 41 || || 1415150013
|-
| DFG SA 2131/14-2 (eRO STEP 2, P2) || 7458 205 || 547 41 || || 1415150013
|-
| DFG SA 2131/15-2 (eRO STEP 2, TP Z) || 7458 206 || 547 41 || || 1415150013
|-
| DFG SA 2131/18-1 (eROSITA Galaxien) || 7458 168 || 547 41 || || 1415150013
|-
| || || || ||
|-
| DFG overhead SA (Altprojekte) || 7459 704 || 547 41 || || 1415150013
|-
| DFG overhead SA bis 2022 || 5002391 || 547 40 || PPS || 1415150013
|-
| DFG overhead SA ab 2023 || 0150178 || 547 40 || PPS || 1415150013
|-
| || || || ||
|-
| DFG SA 4388/2-1 (Saeedi) || 7458 207 || 547 41 || || 1415150013
|-
| DFG MA 11073/1-1 (Mayer) || 7458 221 || 547 41 || || 1415150013
|-
| DFG HE 1356/70-2 (Heber) || 7458 225 || 547 41 || || 1415150000
|-
| || || || ||
|-
| 73er Titel || 061 000-6 || 547 40 || FuL || 1415150000
|-
| 72er Titel || 806 3141 || 547 41 || || 1415150000
|}

Additionally you need to specify the kind of expense (Kostenart): 685000. If the AWK is empty in the table above, do not put anything in the '''Info 1''' field. Otherwise add the given symbol.

== English information ==

Here are some PDFs you might find helpful to navigate through the German landscape of bureaucracy.

Some [[:Media:Additional_information_BayRMS.pdf|additional information]] in Englisch

The [[:Media:Bayrms_eng_data_protection.pdf|data protection waiver]] (you still have to sign the German one!)

The [[:Media:Bayrms_eng_introduction_slides.pdf|introduction slides]]

A [[:Media:Bayrms_glossary.pdf|glossary]] to match English and German terms. (REALLY HELPFUL, CONTAINS INFORMATION TO INSERT)

== ''OUTDATED!'' Business and private travels ==

If you intend to combine a business trip with a vacation to save money or just because of the occasion, you need to observe a couple of issues:

* first of all, combining business and private travel is in principle nothing that the university likes
* you *need* to get the private travel authorized on the travel request form, i.e. you need to state *both* on travel request form
* obviously you will not get any reimbursement for the private part of your trip, or any extra expenses arising from your vacation
* to get reimbursement for your business part of the trip, you need to document what the business part alone would have cost. In detail this means that you need to document:
* fictitious cost of flights/train tickets/rental car/etc for the business part of the trip
* fictitious cost of flights/train tickets/etc to and from the business destination of the trip
* nevertheless you also obviously need to state your actual cost (flight tickets etc).
* the university will reimburse you only the *lesser* of your actual cost and the fictitious cost!\\ This means that if your flight would have cost 1000 Eur, but because you stayed longer for private reasons (i.e. over the weekend) and the actual flight is cheaper like 700 Eur, the university will only reimburse you 700 Eur.

Furthermore apart from the reimbursement by the university, you have also to consider the taxes: the fiscal authorities might consider such a combination of business and private trip entirely private and therefore the reimbursement as additional income. So far,
this has never happened in Bamberg to Jörns knowledge, but in principle tax
regulations state that for a trip to count as a business trip, the
business portion must outbalance the private portion. To give an
example: a 3d observing run in Australia followed by a 2 week vacation
there would probably not be seen as a business related trip (even if it
was!), even though the university would reimburse you for your flights
and the 3d per diem.
((Based on a FAQ Email sent by Jörn to allusers on April 4, 2011))

Guided Tours and Public Outreach

2024-06-20T09:59:46Z

Nekrasov: /* Giving a tour */

On this pages you can find all information needed to guide a tour through our observatory for public people.

At least, that's the aim of this page, so please add information if you think its missing!

= Platform =

'''The following is important:''' 
Tours are officially '''organized''' by the [http://foerderverein-sternwarte-bamberg.de Foerderverein of the observatory], but '''operated''' by the observatory staff to be insured through the university!

The main platform for the general public is [http://foerderverein-sternwarte-bamberg.de/fuehrungen http://foerderverein-sternwarte-bamberg.de/fuehrungen].

Here, tours can be ordered in two different ways:
* single persons and smaller groups can directly book public and regular guided tours via our webform at https://www.sternwarte.uni-erlangen.de/guided-tours/
* larger groups may directly ask for a tour at a separate date either by email to [mailto:fuehrungen@foerderverein-sternwarte-bamberg.de fuehrungen@foerderverein-sternwarte-bamberg.de] or by phone. The email address is a forwarding to a certain person of the mailing list (see below).

The source code of the webform for booking a public tour can be found in the GIT repository at 
[https://www.sternwarte.uni-erlangen.de/gitlab/webmaster/guided-tours https://www.sternwarte.uni-erlangen.de/gitlab/webmaster/guided-tours]. 
All pushes to the master branch are automatically deployed at the official URL above!

== Mailing List / Current "staff" ==

All people interested in giving guided tours are member of the mailing list 
[mailto:astro-fuehrungen@lists.fau.de astro-fuehrungen@lists.fau.de] 
Please '''do not share''' this address with anybody outside of the observatory!
If you're not on the list but interested in giving tours, just ask Max to add you :-)

New tours without a guide yet are usually announced via this list. See [[Mailing lists]] for the list administrator.

In charge of organization:
* Katrin

Currently, the following people give tours on a regular basis:
* Steven
* Christian
* Aafia
* Amy
* Philipp T.
* Alexey
* Katharina

= Tip policy =

The group is informed beforehand about the rule of tip.
For the guides the following applies for the money you get during the tour:
During the week (Monday till Friday) the factor for the donation, which goes directly to the Foerderverein, is 1/3 (33%), the rest (2/3) is your personal tip.
For weekend tours (Saturday, Sunday) the factor for the donation is 1/4 (25%).

Make sure to hand in the donations immediately after your tour. Put the money on Ingos desk with a note stating which tour you gave, how much you received and how many people were there.

= Offering Tours =

At some point you're perhaps asked to give a tour or if it is possible to have one on a specific date. The latter might occur if Edith is out of her office and her telephone is redirected. In those cases you should know ''and'' check following things:
* '''Who is asking''' for a tour? If you're on the phone ask for a name and write down the phone number where the person can be called!
* The '''number of people should be between 15 and 25'''. Of course, the boundary conditions depend on the person guiding the tour. In a case of doubt, ask the guide or, if none is found yet, you simply can't promise that there will be a tour! In that case you may offer to look for a guide giving the tour anyway (and call the person back), but again don't make any promises! A list of people offering tours can be found below.
* What is the '''average age of the persons attending''' the tour? That's an important point since the content of a tour differs between children and adults, of course. Furthermore some guides have favorite age groups!
* Carefully check the '''date and time of the tour'''!
** It's most likely to find a guide if the weekday of a tour is '''between Monday and Thursday'''. Friday might work if it is before noon, otherwise people might be on the way into the weekend. In all other cases you may offer to look for a guide giving the tour anyway (see the point about the group size above).
** Make sure that there is '''no tour scheduled already'''! For that look into our online calendar (the link can be found below) and on the whiteboard in the copying machine office.
** Related to the last point ensure that there is '''no lab course''' running at the date! The lab course is also marked in our online calendar.
** Usually, a tour will take '''about 1.5 to 2 hours'''.
* Clarify the '''costs for a tour''' beforehand!! Unfortunately, we are '''not allowed to ask for money''' for giving a tour! The only way for getting money is to tell the people that they are welcomed to '''donate money to the [http://foerderverein-sternwarte-bamberg.de/| Foerderverein der Sternwarte]'''. In nearly every case the people or the one asking for a tour will pay something. A rule of thumb is that '''every person donates 3 EUR''' (for children 2 EUR are alright as well). __For your ears only__: 1 EUR per attended person of the donated money will be transferred to the Förderverein (the current treasurer is Ingo, leave the money on his desk with a short note stating the number of people and what kind of a tour this was), the rest is for the guide! There will be a contact phone-number available, best would be to call the contacts-person before the tour to tell them these infos...
* '''Observing with our telescopes''' is possible, of course, but only in case of '''night and cloudless weather'''! No kidding, some people are not aware of these facts... ("The day is too bright to see stars.", "I'm sorry, we can't look trough the clouds.", "The weather forecast is too uncertain, we can't promise.") Please check if someone else has already signed in for one of the telescopes on the day/night of the guided tour! '''IMPORTANT:''' Be aware that you are not allowed to operate the telescopes on you own, there ALWAYS has to be at least a second person around. To assure that, you either have to have a second person from the observatory present (at least in the main building) or you have to set up AND disassemble everything while the people from the tour are there. Otherwise no observations are allowed to take place!
* If all the above points are clarified '''mark the tour''' in our [https://www.sternwarte.uni-erlangen.de/calendar/ online calendar] and the whiteboard in the copying machine office. You have to be at a machine at the observatory to have access to the online calendar (to be more precisely: you're machine has to have an internal IP-address). The entry into the online calendar, besides the date and time, should include "for whom is the tour and the group size, contact person and phone number, name of the guide giving the tour". The whiteboard template is as follows: "date, for whom is the tour, time, guide"

= Giving a tour =

Each tour has several stations, where you can show things or talk to the people. Useful information and experiences about that is listed below. It might be helpful as well to read the article about [[intern:popular_science:start|popular science]] in case you want or have to (if somebody asks) explain scientific aspects.

Note that there is also a separate page about guided tour stations: https://www.sternwarte.uni-erlangen.de/wiki/index.php/Guided_tour_stations

== Preparation ==

'''Before the tour'''
* Shut the doors of all offices in the main building (at least on the ground level) for several reasons: people are not allowed to walk in there and some of us are still working there during tours!
* Remove the northern hemisphere from the model of the inner solar system located in the entrance hall (you may put it into the Knigge room)
* Switch the lights on you need:
** entrance hall
** meteorite showcase (switch is on the right next to it)
** hallway to the meridian building; here are multiple switches
*** main light: right next to the door of the hallway or the backdoor of the main building (labeled "Meridian")
*** info panels: on the opposite wall to the door next to the blue cupboard
*** showcases and Blinkkomparator: in the cutout box up the few stairs on the right wall close to the library, labeled "Linke Steckdosen"
* In case of observations
** make sure that you are '''never''' alone in the domes! There always have to be at least two people present.
** carry the needed oculars into the domes (for observations with the naked eye, the 40cm telescope is strongly recommended)
** do __not__ open the domes (first, it might start raining while nobody is there, and it's more fun for you to let the people do it)
** do __not__ remove the dust covers of the telescopes (wait until the dome has been opened)
** read the [[remeis:start|guide how to operate the telescopes and mountings]]
** after observing: shut down the telescope mounting, put the dust covers back on and close the domes
* In case of showing nice pictures
** make sure enough chairs are available
** switch on the beamer in the library, log into the machine and start your presentation, picture-viewer, ...

'''After the tour'''
* Switch the lights off
* Logout of the used machines and switch the beamer off
* Put on the dust covers of the telescopes in the hallway
* Protect the photo plates on the Blinkkomparator from getting dusty
* '''Move the entry from the whiteboard''' in the copying machine office '''to the list attached to the pin-board''' next to it

== Material and Presentations ==
*Collected information valuable for guided tours: ''/data/media/presentations_for_guided_tours'' and ''/userdata/data/beuchert/work/teaching/guidedtour/presentation/guidedtour.pdf''

*A merger of (picture/video) presentations given at guided tours: ''/userdata/data/beuchert/work/teaching/guidedtour/presentation/guidedtour.odp''

*and according videos in ''/userdata/data/beuchert/work/teaching/guidedtour/presentation/videos/''

*Research and activities at Remeis from the radio to the gamma-rays (Tobi Beuchert): ''/data/media/presentations_for_guided_tours/Andrea_tour_material/observations_allwavelength_remeisresearch_beuchert.pdf''

*A presentation showing the astrophotography done at the observatory: ''/data/media/slideshow_astrophotographie/optische_Quellen.pdf''

*A video tour with Joern: ''/data/media/presentations_for_guided_tours/Joerns_example_tour''

*A video tour with Uli (only hallway): ''/data/media/presentations_for_guided_tours/Ulis_example_tour_hall_2019''

*A complete tour by Sebastian Müller: ''/data/media/presentations_for_guided_tours/Sebastians_example_tour''

*Presentations for tours by Andrea Gokus: ''/data/media/presentations_for_guided_tours/Andrea_tour_material'' Contains presentations about the solar system (solar_system.pdf), neutrinos (neutrino_talk.pdf), overview of different objet types (impressions_universe.pdf)

*Andreas tour notes: ''/data/media/presentations_for_guided_tours/Andrea_tour_material/Sternwarten_Fuehrungsnotizen.pdf''

*Amys tour notes: ''/data/media/presentations_for_guided_tours/Guided_Tour_Information_Amy.pdf''

*Tobis tour notes: ''/userdata/data/beuchert/work/teaching/guidedtour/presentation/guidedtour.pdf''

*Information on clocks: ''/data/media/history/2009-01_KlassikUhren_Poehlmann_Max_Ort.pdf''

*Information on history of the observatory and the collection: ''/data/media/history/AstronomischeSammlung.pdf''

*History of the observatory (Litten): ''/data/media/history/Litten-1.pdf'' ''/data/media/history/Litten-2.pdf''

*Last will of Dr. Karl Remeis: ''/data/media/history/Testament_Karl_Remeis.pdf''

*Die Remeis-Sternwarte zu Bamberg 1889-1939, E. Zinner: [https://articles.adsabs.harvard.edu/cgi-bin/nph-iarticle_query?1939VeBam...4....1Z&data_type=PDF_HIGH&whole_paper=YES&type=PRINTER&filetype=.pdf ADS]

== Picture presentation ==

There are different modes for the beamer (e.g. presentation, videos, graphics etc.) which result in a different appearance of the images. Make sure to select a presentation mode in which the pictures appear in an appropriate brightness on the screen. (I think "graphics" was a good one).

== Telescopes in the domes ==
It's nice to show the main mirror to the people so that they can see themselves. To do so, just turn down the telescope in declination. This is only possible for the 40cm as the 50cm-Mount has a mechanical stop.

Sometimes people want to know what we do with the tiny, little telescopes attached on the side of the big ones. Those are guiding-scopes. You can attach a camera to them and let it take pictures of one star. If the star moves (what it shouldn't do) a correction signal is sent to the mount to compensate the movement of the star. Stars can "move" in an image for example due to impreciseness of the mount.

The (dusty) plate in front of the 40cm mirror is called "Schmid-Platte". It is used to improve the imaging of the telescope and to correct several errors of the mirrors like coma and field-curvature. As it is very sensitive to scratching, it won't be cleaned and left dusty. But the dust has hardly any effect on the images as it lays far outside of the focusplane. The optical design is similar to a Ritchey-Chrétien type regarding the capability, but has a spherical main mirror, an aspherical secondary mirror and a lens-corrector (=Schmidt-plate). The price of the telescope and the mount is roughly about 25.000€ altogether.

The 50cm doesn't have a Schmid-Platte but a corrector (lenses) placed in the OAZ. It has an elliptical main mirror and a spherical secondary mirror (Corrected Dall Kirkham). The price of the telescope and the mount is roughly about 65.000€. The secondary mirror is, compared to the size of the main mirror, significantly larger than the 40cm-sec. mirror. This results in a better luminosity an a larger, flat-field which is important for taking images. We can achieve tracking accuracies of about 10min without guiding.

== Monthly public tours ==
NOTE: even if there is already someone listed for a tour, please enter you availability

!! UPDATE: for now no public tours will be offered, so you can ignore this table for now !!

{| class="wikitable"
! Date
! Language
! Time
! Type
! Available Guides
! Backup

|-
| 2024/--/--
| German
| 6 pm
| normal tour
| -
| -

|-
| 2024/--/--
| English
| 6 pm
| normal tour
| -
| -

|-
| 2024/--/--
| German
| 6 pm
| Tour for children
| -
| -

|}

== Tours looking for a guide ==
ATTENTION: tours are not sorted by the date of the tour, but the time when they were requested

NOTE: please enter you availability even if there is already another name listed.

{| class="wikitable"
! Date
! Language
! Time
! Organizer
! Additional information
! # People
! Observing
! Available Guides

|-
| 2024/08/01
| German
| 9am-12pm or 1pm-3pm
| Sommerferienprogramm Schlüsselfeld
| kids age 6 - 11
| ~12 kids and 2 adults
| no
|

|-
| 2024/06/21 or 2024/06/28
| German
| evening
| Doncheva
| 5 kids (age 8) + 3 to 5 adults
| ~10 people
| yes
|

|-
| 2024/11/05
| German
| 5 pm
| Lebenshilfe Bamberg
| some people with slight mental disabilities
| 50 - 60 adults
| yes (some of them, small group)
|

|}

== Observing ==

[[Category:Guided-tours]]
[[Category:Internal]]

PhD hat for Ole

2024-01-29T11:32:09Z

Nekrasov: /* Travels: */

[[Category:Internal]]

Date of defense: 20th of February 2024

Thesis here: https://www.sternwarte.uni-erlangen.de/~koenig/Koenig_Dissertation.pdf

== Science: ==
* Cyg X-1 NICER timing paper
** Model of Cyg X-1 with Photon trajectories
** Model of NICER as cheese grinder

* eROSITA NOVA paper
** Eye of Sauron
** Evil smile plot

==> Which of these is gonna be the center piece?

* SIXTE Athena simulations
**Perseus Cluster with WFI

* Should we try to make comics of Paul the X-ray photon to go around the hat?

== Hobby: ==
* Climbing: Ole-figurine hanging on rope as a tassel, also bouldering holds around the hat
* Remeis Skiing: Digging for lost ski --> Maybe he can find the lost ski on one of his astrophysical objects?
* A mountain with one side cliff for climbing and another side for skiing (or above)
* Some references to observatory pool and barbecues
* Wind surfing?
* Books: LOTR, ...?
* Motorbike
* Running

== Others: ==
* Guided tours (& also for kids)
* Lab course: Azimuth experiment

=== Travels: ===
* Train to ESAC Madrid
* Yosemite, Alps, Frankenjura, Caucasus
* Visit of CAltech
* Lots of talks after Nature paper

=== Specific incidents: ===
* ...

=== Memes & Images: ===
* ...
Alexey: He has a peaked cap from California with name "Mishka" written in russian letters ("Мишка") on it, which also means "a small bear/ Bärchen" in russian. Could this be played out somehow?

PhD hat for Ole

2024-01-29T11:31:27Z

Nekrasov: /* Memes & Images: */

[[Category:Internal]]

Date of defense: 20th of February 2024

Thesis here: https://www.sternwarte.uni-erlangen.de/~koenig/Koenig_Dissertation.pdf

== Science: ==
* Cyg X-1 NICER timing paper
** Model of Cyg X-1 with Photon trajectories
** Model of NICER as cheese grinder

* eROSITA NOVA paper
** Eye of Sauron
** Evil smile plot

==> Which of these is gonna be the center piece?

* SIXTE Athena simulations
**Perseus Cluster with WFI

* Should we try to make comics of Paul the X-ray photon to go around the hat?

== Hobby: ==
* Climbing: Ole-figurine hanging on rope as a tassel, also bouldering holds around the hat
* Remeis Skiing: Digging for lost ski --> Maybe he can find the lost ski on one of his astrophysical objects?
* A mountain with one side cliff for climbing and another side for skiing (or above)
* Some references to observatory pool and barbecues
* Wind surfing?
* Books: LOTR, ...?
* Motorbike
* Running

== Others: ==
* Guided tours (& also for kids)
* Lab course: Azimuth experiment

=== Travels: ===
* Train to ESAC Madrid
* Yosemite, Alps, Frankenjura
* Visit of CAltech
* Lots of talks after Nature paper

=== Specific incidents: ===
* ...

=== Memes & Images: ===
* ...
Alexey: He has a peaked cap from California with name "Mishka" written in russian letters ("Мишка") on it, which also means "a small bear/ Bärchen" in russian. Could this be played out somehow?

Guided Tours and Public Outreach

2023-10-30T13:50:23Z

Nekrasov: /* Mailing List / Current "staff" */

On this pages you can find all information needed to guide a tour through our observatory for public people.

At least, that's the aim of this page, so please add information if you think its missing!

= Platform =

'''The following is important:''' 
Tours are officially '''organized''' by the [http://foerderverein-sternwarte-bamberg.de Foerderverein of the observatory], but '''operated''' by the observatory staff to be insured through the university!

The main platform for the general public is [http://foerderverein-sternwarte-bamberg.de/fuehrungen http://foerderverein-sternwarte-bamberg.de/fuehrungen].

Here, tours can be ordered in two different ways:
* single persons and smaller groups can directly book public and regular guided tours via our webform at https://www.sternwarte.uni-erlangen.de/guided-tours/
* larger groups may directly ask for a tour at a separate date either by email to [mailto:fuehrungen@foerderverein-sternwarte-bamberg.de fuehrungen@foerderverein-sternwarte-bamberg.de] or by phone. The email address is a forwarding to a certain person of the mailing list (see below).

The source code of the webform for booking a public tour can be found in the GIT repository at 
[https://www.sternwarte.uni-erlangen.de/gitlab/webmaster/guided-tours https://www.sternwarte.uni-erlangen.de/gitlab/webmaster/guided-tours]. 
All pushes to the master branch are automatically deployed at the official URL above!

== Mailing List / Current "staff" ==

All people interested in giving guided tours are member of the mailing list 
[mailto:astro-fuehrungen@lists.fau.de astro-fuehrungen@lists.fau.de] 
Please '''do not share''' this address with anybody outside of the observatory!
If you're not on the list but interested in giving tours, just ask Max to add you :-)

New tours without a guide yet are usually announced via this list. See [[Mailing lists]] for the list administrator.

In charge of organization:
* Katrin

Currently, the following people give tours on a regular basis:
* Dominic
* Ole
* Steven
* Christian
* Aafia
* Amy
* Julia
* Philipp T.
* Alexey

= Tip policy =

The group is informed beforehand about the rule of tip.
For the guides the following applies for the money you get during the tour:
During the week (Monday till Friday) the factor for the donation, which goes directly to the Foerderverein, is 1/3 (33%), the rest (2/3) is your personal tip.
For weekend tours (Saturday, Sunday) the factor for the donation is 1/4 (25%).

Make sure to hand in the donations immediately after your tour. Put the money on Ingos desk with a note stating which tour you gave, how much you received and how many people were there.

= Offering Tours =

At some point you're perhaps asked to give a tour or if it is possible to have one on a specific date. The latter might occur if Edith is out of her office and her telephone is redirected. In those cases you should know ''and'' check following things:
* '''Who is asking''' for a tour? If you're on the phone ask for a name and write down the phone number where the person can be called!
* The '''number of people should be between 15 and 25'''. Of course, the boundary conditions depend on the person guiding the tour. In a case of doubt, ask the guide or, if none is found yet, you simply can't promise that there will be a tour! In that case you may offer to look for a guide giving the tour anyway (and call the person back), but again don't make any promises! A list of people offering tours can be found below.
* What is the '''average age of the persons attending''' the tour? That's an important point since the content of a tour differs between children and adults, of course. Furthermore some guides have favorite age groups!
* Carefully check the '''date and time of the tour'''!
** It's most likely to find a guide if the weekday of a tour is '''between Monday and Thursday'''. Friday might work if it is before noon, otherwise people might be on the way into the weekend. In all other cases you may offer to look for a guide giving the tour anyway (see the point about the group size above).
** Make sure that there is '''no tour scheduled already'''! For that look into our online calendar (the link can be found below) and on the whiteboard in the copying machine office.
** Related to the last point ensure that there is '''no lab course''' running at the date! The lab course is also marked in our online calendar.
** Usually, a tour will take '''about 1.5 to 2 hours'''.
* Clarify the '''costs for a tour''' beforehand!! Unfortunately, we are '''not allowed to ask for money''' for giving a tour! The only way for getting money is to tell the people that they are welcomed to '''donate money to the [http://foerderverein-sternwarte-bamberg.de/| Foerderverein der Sternwarte]'''. In nearly every case the people or the one asking for a tour will pay something. A rule of thumb is that '''every person donates 3 EUR''' (for children 2 EUR are alright as well). __For your ears only__: 1 EUR per attended person of the donated money will be transferred to the Förderverein (the current treasurer is Ingo, leave the money on his desk with a short note stating the number of people and what kind of a tour this was), the rest is for the guide! There will be a contact phone-number available, best would be to call the contacts-person before the tour to tell them these infos...
* '''Observing with our telescopes''' is possible, of course, but only in case of '''night and cloudless weather'''! No kidding, some people are not aware of these facts... ("The day is too bright to see stars.", "I'm sorry, we can't look trough the clouds.", "The weather forecast is too uncertain, we can't promise.") Please check if someone else has already signed in for one of the telescopes on the day/night of the guided tour!
* If all the above points are clarified '''mark the tour''' in our [https://www.sternwarte.uni-erlangen.de/calendar/ online calendar] and the whiteboard in the copying machine office. You have to be at a machine at the observatory to have access to the online calendar (to be more precisely: you're machine has to have an internal IP-address). The entry into the online calendar, besides the date and time, should include "for whom is the tour and the group size, contact person and phone number, name of the guide giving the tour". The whiteboard template is as follows: "date, for whom is the tour, time, guide"

= Giving a tour =

Each tour has several stations, where you can show things or talk to the people. Useful information and experiences about that is listed below. It might be helpful as well to read the article about [[intern:popular_science:start|popular science]] in case you want or have to (if somebody asks) explain scientific aspects.

== Preparation ==

'''Before the tour'''
* Shut the doors of all offices in the main building (at least on the ground level) for several reasons: people are not allowed to walk in there and some of us are still working there during tours!
* Remove the northern hemisphere from the model of the inner solar system located in the entrance hall (you may put it into the Knigge room)
* Switch the lights on you need:
** entrance hall
** meteorite showcase (switch is on the right next to it)
** hallway to the meridian building; here are multiple switches
*** main light: right next to the door of the hallway or the backdoor of the main building (labeled "Meridian")
*** info panels: on the opposite wall to the door next to the blue cupboard
*** showcases and Blinkkomparator: in the cutout box up the few stairs on the right wall close to the library, labeled "Linke Steckdosen"
* In case of observations
** carry the needed oculars into the domes (for observations with the naked eye, the 40cm telescope is strongly recommended)
** do __not__ open the domes (first, it might start raining while nobody is there, and it's more fun for you to let the people do it)
** do __not__ remove the dust covers of the telescopes (wait until the dome has been opened)
** read the [[remeis:start|guide how to operate the telescopes and mountings]]
* In case of showing nice pictures
** make sure enough chairs are available
** switch on the beamer in the library, log into the machine and start your presentation, picture-viewer, ...

'''After the tour'''
* Switch the lights off
* Shut down the telescope mounting, put the dust covers back on and close the domes
* Logout of the used machines and switch the beamer off
* Put on the dust covers of the telescopes in the hallway
* Protect the photo plates on the Blinkkomparator from getting dusty
* '''Move the entry from the whiteboard''' in the copying machine office '''to the list attached to the pin-board''' next to it

== Material and Presentations ==
*Collected information valuable for guided tours: ''/data/media/presentations_for_guided_tours'' and ''/userdata/data/beuchert/work/teaching/guidedtour/presentation/guidedtour.pdf''

*A merger of (picture/video) presentations given at guided tours: ''/userdata/data/beuchert/work/teaching/guidedtour/presentation/guidedtour.odp''

*and according videos in ''/userdata/data/beuchert/work/teaching/guidedtour/presentation/videos/''

*Research and activities at Remeis from the radio to the gamma-rays (Tobi Beuchert): ''/data/media/presentations_for_guided_tours/Andrea_tour_material/observations_allwavelength_remeisresearch_beuchert.pdf''

*A presentation showing the astrophotography done at the observatory: ''/data/media/slideshow_astrophotographie/optische_Quellen.pdf''

*A video tour with Joern: ''/data/media/presentations_for_guided_tours/Joerns_example_tour''

*A video tour with Uli (only hallway): ''/data/media/presentations_for_guided_tours/Ulis_example_tour_hall_2019''

*A complete tour by Sebastian Müller: ''/data/media/presentations_for_guided_tours/Sebastians_example_tour''

*Presentations for tours by Andrea Gokus: ''/data/media/presentations_for_guided_tours/Andrea_tour_material'' Contains presentations about the solar system (solar_system.pdf), neutrinos (neutrino_talk.pdf), overview of different objet types (impressions_universe.pdf)

*Andreas tour notes: ''/data/media/presentations_for_guided_tours/Andrea_tour_material/Sternwarten_Fuehrungsnotizen.pdf''

*Amys tour notes: ''/data/media/presentations_for_guided_tours/Guided_Tour_Information_Amy.pdf''

*Tobis tour notes: ''/userdata/data/beuchert/work/teaching/guidedtour/presentation/guidedtour.pdf''

*Information on clocks: ''/data/media/history/2009-01_KlassikUhren_Poehlmann_Max_Ort.pdf''

*Information on history of the observatory and the collection: ''/data/media/history/AstronomischeSammlung.pdf''

*History of the observatory (Litten): ''/data/media/history/Litten-1.pdf'' ''/data/media/history/Litten-2.pdf''

*Last will of Dr. Karl Remeis: ''/data/media/history/Testament_Karl_Remeis.pdf''

*Die Remeis-Sternwarte zu Bamberg 1889-1939, E. Zinner: [https://articles.adsabs.harvard.edu/cgi-bin/nph-iarticle_query?1939VeBam...4....1Z&data_type=PDF_HIGH&whole_paper=YES&type=PRINTER&filetype=.pdf ADS]

== Picture presentation ==

There are different modes for the beamer (e.g. presentation, videos, graphics etc.) which result in a different appearance of the images. Make sure to select a presentation mode in which the pictures appear in an appropriate brightness on the screen. (I think "graphics" was a good one).

== Telescopes in the domes ==
It's nice to show the main mirror to the people so that they can see themselves. To do so, just turn down the telescope in declination. This is only possible for the 40cm as the 50cm-Mount has a mechanical stop.

Sometimes people want to know what we do with the tiny, little telescopes attached on the side of the big ones. Those are guiding-scopes. You can attach a camera to them and let it take pictures of one star. If the star moves (what it shouldn't do) a correction signal is sent to the mount to compensate the movement of the star. Stars can "move" in an image for example due to impreciseness of the mount.

The (dusty) plate in front of the 40cm mirror is called "Schmid-Platte". It is used to improve the imaging of the telescope and to correct several errors of the mirrors like coma and field-curvature. As it is very sensitive to scratching, it won't be cleaned and left dusty. But the dust has hardly any effect on the images as it lays far outside of the focusplane. The optical design is similar to a Ritchey-Chrétien type regarding the capability, but has a spherical main mirror, an aspherical secondary mirror and a lens-corrector (=Schmidt-plate). The price of the telescope and the mount is roughly about 25.000€ altogether.

The 50cm doesn't have a Schmid-Platte but a corrector (lenses) placed in the OAZ. It has an elliptical main mirror and a spherical secondary mirror (Corrected Dall Kirkham). The price of the telescope and the mount is roughly about 65.000€. The secondary mirror is, compared to the size of the main mirror, significantly larger than the 40cm-sec. mirror. This results in a better luminosity an a larger, flat-field which is important for taking images. We can achieve tracking accuracies of about 10min without guiding.

== Monthly public tours ==
NOTE: even if there is already someone listed for a tour, please enter you availability

{| class="wikitable"
! Date
! Language
! Time
! Type
! Available Guides
! Backup

|-
| 2023/11/07
| English
| 6 pm
| normal tour
| Aafia
| Katharina

|-
| 2023/11/14
| German
| 6 pm
| Tour for children
|
| Katharina

|-
| 2023/11/28
| German
| 6 pm
| normal tour
| Katharina
| Philipp

|-
| 2023/12/05
| English
| 6 pm
| normal tour
| Federico
| Philipp, Katharina

|-
| 2023/12/12
| German
| 6 pm
| Tour for children
|
|

|-
| 2023/12/19
| German
| 6 pm
| normal tour
|
| Philipp

|}

== Tours looking for a guide ==
ATTENTION: tours are not sorted by the date of the tour, but the time when they were requested

NOTE: please enter you availability even if there is already another name listed.

{| class="wikitable"
! Date
! Language
! Time
! Organizer
! Additional information
! # People
! Observing
! Available Guides

|-
| 2024/01/19
| German
| start between 6pm and 7pm
| Diakonie Kulmbach
| activity for people with mental disabilities
| ~ 10 adults
| yes
|

|-
| 2023/11/04
| German
| start around 6:30pm
| Julia Schlosser
|
| 12 - 15 adults
| yes
|

|}

== Observing ==

[[Category:Internal]]

Common Practices at Remeis

2023-07-26T12:35:32Z

Nekrasov: /* Common Practices at Remeis */

== Common Practices at Remeis ==

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''We try to be as flexible as possible, and I trust that you are adults and do not exploit the system. A minimum time for coordination in the group and knowing what everybody is doing is necessary. This time is the group meeting, and for this reason you have to be there and you should be prepared to discuss what you're doing there. If you do something else on the side, this is also fine, but it should not negatively impact on your research. It is on you to be able to manage your different tasks, and the expectation is that research has to come first.''

=== Working Times ===

'''Added by a request of J. Wilms on 2016 June 15'''

Is is expected that you are in the office in Bamberg for at least ~3 days per week. Although we have flexible working times, arriving at 10 a.m. latest is a good practice to ensure significant overlap with your colleagues.

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''working from home or Erlangen is ok (except for [...] [the group meetings]), but [...] [your supervisor] and the people you're working with directly need to know where you are. This means that you need to be reachable by email or phone, and you need to be working. As a rule of thumb: BSc-, MSc-, and PhD-thesis work is the equivalent to a full time job, irrespective of what your contracts say. Full time means 40+ hours per week. If you're working on the side this is fine - you know that we try to be supportive here - but this does not mean that you should subtract off the time you're making money from the time you're spending on your research, which - I repeat myself - should keep you busy equivalent to a full time job. If you find that you cannot manage this schedule when working from home, then I strongly suggest that you go to the office.''

''Due to the international nature of our work, it is to be expected that you have to be able to attend telecons after 18:00.''

=== Illness & Vacation ===

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''if you are ill, always(!) notify Edith, [...] [your supervisor], *and* the people you're working with (i.e., all BSc/MSc students also have a PhD student as point of contact and (s)he should also know).''

''if you plan to go on vacation, talk to [...] [your supervisor] first. [...] [We] will usually say yes, but there are some times you should avoid not being here, especially times before project deadlines, proposal deadlines, and the lab courses. This applies to everybody in the group.''

''once your vacation has been approved or if you're going to a conference, put down the dates of your absence on the white board next to the xerox machine.''

=== X-ray Group Meeting ===

'''From an E-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''group meeting starts Tuesdays, 10:00. The presence of everybody in the group (hiwis, BSc, MSc, PhD, postdocs) is *mandatory*. The only reason not to show up is if you're ill or if you have a lecture. In this case, please let me know. Do not assume I remember because you told me two weeks ago...''

=== Remeis Calendar ===

There is a calendar with the schedule of Remeis events, tours, visiting persons etc. It is very useful for newbies to have it nearby:
https://www.sternwarte.uni-erlangen.de/calendar/month.php

Don't forget to sign-in with your remeis account, otherwise you will see only the public part.

=== AstroLab ===

Twise a year there is an event when students from the uni come to the observatory and make their lab work. People from the observatory guide and help the students. The lab course takes about a month (usually September and March - see the Remeis Calendar), and people are supposed to participate and should be present and available during that time. In general, it is expected that you neither take vacations nor go to conferences during the lab.

=== Journal Club ===

Incomplete [[intern:litclub|list of past Literature Clubs]]

'''From an e-mail by M. Oertel on 2016 June 14 to the X-ray gang'''

''[...] assume that *everybody currently working in the xray-group is participating*.''

''Litclub is always (except during lab) on Tuesdays at 11:30 after the [X-ray] group-meeting. On every Monday I randomly choose someone for the next Litclub. There's a list of astronomy-papers which I will then send to you and you choose one (ideally not strongly correlated to your current work) and prepare a ~10 minute summary-talk. The talk will be in English. You don't have to understand everything they did in the paper, you just have to explain the central idea. One of the main aspects is to practice fast-paper-reading-and-understanding, therefore it has to be on a short notice (meaning Monday morning). This is also to prevent you from spending a few days on preparing. If you come across any interesting paper you think could fit (even if you haven't read it) please send a link to me so that I can add it to the list. You can decline when I ask you on Mondays but please only do so if you have a deadline (proposal or thesis...)/are sick...''

''It really is a good opportunity to practice giving talks, summarizing content and also it is a nice get-together for discussing interesting astro-stuff''

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''Your attendance and active participation is very strongly suggested. It is good for you.''

'''Update - Jun 2022: LitClub is back!'''

Follow this page for relevant details: [[Litclub]]

=== PhD-Hat and -Celebration tradition ===

[[intern:phd_hat_list|List of future PhDs]]

'''From an e-mail by M. Kuehnel in 2016 June 14 to almost everybody'''

''[...] this tradition is not alive in every institute. From my personal experience I know places where PhDs just defend and vanish without getting a hat, party, or anything personal from the colleagues. This is not how your 3+ years should end.''

''We have the tradition at our institute that every PhD candidate gets a self-made hat after having defended her or his thesis. Also, a big party is organized for her or his after the defence. It is a common agreement that the hat and the party is *mainly build and organized by all other PhD students*. Of course, also contributions from bachelor or master students are very well welcomed, too. Thus, it is very much appreciate (if not expected) that /everybody/ contributes and not only a few. It is not expected, however, to spent hours, even ~20 minutes are enough (for, e.g., searching and printing a picture, which is supposed to be put on the hat).''

''The main organization of the hat building process and the party is traditionally done by the PhD student, which is supposed to finish her or his PhD next. [...] This person is''
* ''the initiator of the hat building process and the organization of the party by, e.g., writing emails to everybody (expect to the PhD candidate, of course) in the first place. Creating a wiki-page for the hat might be useful here as well.''
* ''not expected to do all the work, but rather delegate the different tasks and keep the overview, i.e., is the main contact in case of questions. Here, the contribution of everybody is needed to complete all tasks! Here, quasi-regular meetings scheduled by the responsible person have been helpful.''
* ''trying to keep everybody updated and informed about, e.g., the hat status or the defence date. As you see, nobody needs to be afraid of this job.''

''Furthermore (and here we are really privileged), our PhD supervisor sponsors the party and hat with a certain amount. The usual case in other institutes is that the PhD candidate her- or himself pays for the party! Note that often the sponsoring is not sufficient for all expenses. In the past, this was solved in an uncomplicated way by either "basst scho" ("it's fine") from the people who had small expenses (like for the hat) or by the main organizer [...].''

=== Dishwasher Etiquette ===

'''From an e-mail by S. Falkner in 2016 August 29 to everybody'''

[''Please follow the following guideline to avoid a messy kitchen, frustrated Coworkers and unnecessary excessive use of the dishwasher:] ''

In case the dishwasher is full, check if it is clean

(YES): Has it just finished and still hot?
* (YES): Open it completely for cooling and every one too see.
* (NO): Empty it COMPLETELY and put your dirty dishes in and check if there is other dirty stuff to put in!
(NO): Can you make some room for your stuff?
* (YES): Perfect, now you can start it if there is really no more room.
* (NO): Start it and EITHER clean your dishes in the sink (and do not just throw it in their) OR wait till the dishwasher is done and put it in then!.

In case the dishwasher is not full, please do a quick check if the dishes look clean:

(YES): Empty it COMPLETELY and put your dirty dishes in and check if there is other dirty stuff to put in! Especially on Monday mornings it may happen that the dishwasher is only half full but clean as someone was nice and turned it on Friday afternoon, such that the dishwasher doesn't grow to life over the weekend.

(NO): Put your stuff in and ask yourself if it is Friday afternoon and no one else around any more?
* (YES): Start the dishwasher
* (NO): You may wait until you leave

In general it would be nice if all could care more about the kitchen. If
everyone would do care it would not be necessary for some of us to clean
up quite a mess, but only a little bit for all of us.

[[Category:Current Members]][[Category:internal]]

Common Practices at Remeis

2023-07-26T12:29:28Z

Nekrasov: /* AstroLab */

== Common Practices at Remeis ==

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''We try to be as flexible as possible, and I trust that you are adults and do not exploit the system. A minimum time for coordination in the group and knowing what everybody is doing is necessary. This time is the group meeting, and for this reason you have to be there and you should be prepared to discuss what you're doing there. If you do something else on the side, this is also fine, but it should not negatively impact on your research. It is on you to be able to manage your different tasks, and the expectation is that research has to come first.''

=== Working Times ===

'''Added by a request of J. Wilms on 2016 June 15'''

Is is expected that you are in the office in Bamberg for at least ~3 days per week. Although we have flexible working times, arriving at 10 a.m. latest is a good practice to ensure significant overlap with your colleagues.

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''working from home or Erlangen is ok (except for [...] [the group meetings]), but [...] [your supervisor] and the people you're working with directly need to know where you are. This means that you need to be reachable by email or phone, and you need to be working. As a rule of thumb: BSc-, MSc-, and PhD-thesis work is the equivalent to a full time job, irrespective of what your contracts say. Full time means 40+ hours per week. If you're working on the side this is fine - you know that we try to be supportive here - but this does not mean that you should subtract off the time you're making money from the time you're spending on your research, which - I repeat myself - should keep you busy equivalent to a full time job. If you find that you cannot manage this schedule when working from home, then I strongly suggest that you go to the office.''

''Due to the international nature of our work, it is to be expected that you have to be able to attend telecons after 18:00.''

=== Illness & Vacation ===

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''if you are ill, always(!) notify Edith, [...] [your supervisor], *and* the people you're working with (i.e., all BSc/MSc students also have a PhD student as point of contact and (s)he should also know).''

''if you plan to go on vacation, talk to [...] [your supervisor] first. [...] [We] will usually say yes, but there are some times you should avoid not being here, especially times before project deadlines, proposal deadlines, and the lab courses. This applies to everybody in the group.''

''once your vacation has been approved or if you're going to a conference, put down the dates of your absence on the white board next to the xerox machine.''

=== X-ray Group Meeting ===

'''From an E-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''group meeting starts Tuesdays, 10:00. The presence of everybody in the group (hiwis, BSc, MSc, PhD, postdocs) is *mandatory*. The only reason not to show up is if you're ill or if you have a lecture. In this case, please let me know. Do not assume I remember because you told me two weeks ago...''

=== Remeis Calendar ===

There is a calendar with the schedule of Remeis events, tours, visiting persons etc. It is very useful for newbies to have it nearby:
https://www.sternwarte.uni-erlangen.de/calendar/month.php

Don't forget to sign-up, otherwise you will see only the public part.

=== AstroLab ===

Twise a year there is an event when students from the uni come to the observatory and make their lab work. People from the observatory guide and help the students. The lab course takes about a month (usually September and March - see the Remeis Calendar), and people are supposed to participate and should be present and available during that time. In general, it is expected that you neither take vacations nor go to conferences during the lab.

=== Journal Club ===

Incomplete [[intern:litclub|list of past Literature Clubs]]

'''From an e-mail by M. Oertel on 2016 June 14 to the X-ray gang'''

''[...] assume that *everybody currently working in the xray-group is participating*.''

''Litclub is always (except during lab) on Tuesdays at 11:30 after the [X-ray] group-meeting. On every Monday I randomly choose someone for the next Litclub. There's a list of astronomy-papers which I will then send to you and you choose one (ideally not strongly correlated to your current work) and prepare a ~10 minute summary-talk. The talk will be in English. You don't have to understand everything they did in the paper, you just have to explain the central idea. One of the main aspects is to practice fast-paper-reading-and-understanding, therefore it has to be on a short notice (meaning Monday morning). This is also to prevent you from spending a few days on preparing. If you come across any interesting paper you think could fit (even if you haven't read it) please send a link to me so that I can add it to the list. You can decline when I ask you on Mondays but please only do so if you have a deadline (proposal or thesis...)/are sick...''

''It really is a good opportunity to practice giving talks, summarizing content and also it is a nice get-together for discussing interesting astro-stuff''

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''Your attendance and active participation is very strongly suggested. It is good for you.''

'''Update - Jun 2022: LitClub is back!'''

Follow this page for relevant details: [[Litclub]]

=== PhD-Hat and -Celebration tradition ===

[[intern:phd_hat_list|List of future PhDs]]

'''From an e-mail by M. Kuehnel in 2016 June 14 to almost everybody'''

''[...] this tradition is not alive in every institute. From my personal experience I know places where PhDs just defend and vanish without getting a hat, party, or anything personal from the colleagues. This is not how your 3+ years should end.''

''We have the tradition at our institute that every PhD candidate gets a self-made hat after having defended her or his thesis. Also, a big party is organized for her or his after the defence. It is a common agreement that the hat and the party is *mainly build and organized by all other PhD students*. Of course, also contributions from bachelor or master students are very well welcomed, too. Thus, it is very much appreciate (if not expected) that /everybody/ contributes and not only a few. It is not expected, however, to spent hours, even ~20 minutes are enough (for, e.g., searching and printing a picture, which is supposed to be put on the hat).''

''The main organization of the hat building process and the party is traditionally done by the PhD student, which is supposed to finish her or his PhD next. [...] This person is''
* ''the initiator of the hat building process and the organization of the party by, e.g., writing emails to everybody (expect to the PhD candidate, of course) in the first place. Creating a wiki-page for the hat might be useful here as well.''
* ''not expected to do all the work, but rather delegate the different tasks and keep the overview, i.e., is the main contact in case of questions. Here, the contribution of everybody is needed to complete all tasks! Here, quasi-regular meetings scheduled by the responsible person have been helpful.''
* ''trying to keep everybody updated and informed about, e.g., the hat status or the defence date. As you see, nobody needs to be afraid of this job.''

''Furthermore (and here we are really privileged), our PhD supervisor sponsors the party and hat with a certain amount. The usual case in other institutes is that the PhD candidate her- or himself pays for the party! Note that often the sponsoring is not sufficient for all expenses. In the past, this was solved in an uncomplicated way by either "basst scho" ("it's fine") from the people who had small expenses (like for the hat) or by the main organizer [...].''

=== Dishwasher Etiquette ===

'''From an e-mail by S. Falkner in 2016 August 29 to everybody'''

[''Please follow the following guideline to avoid a messy kitchen, frustrated Coworkers and unnecessary excessive use of the dishwasher:] ''

In case the dishwasher is full, check if it is clean

(YES): Has it just finished and still hot?
* (YES): Open it completely for cooling and every one too see.
* (NO): Empty it COMPLETELY and put your dirty dishes in and check if there is other dirty stuff to put in!
(NO): Can you make some room for your stuff?
* (YES): Perfect, now you can start it if there is really no more room.
* (NO): Start it and EITHER clean your dishes in the sink (and do not just throw it in their) OR wait till the dishwasher is done and put it in then!.

In case the dishwasher is not full, please do a quick check if the dishes look clean:

(YES): Empty it COMPLETELY and put your dirty dishes in and check if there is other dirty stuff to put in! Especially on Monday mornings it may happen that the dishwasher is only half full but clean as someone was nice and turned it on Friday afternoon, such that the dishwasher doesn't grow to life over the weekend.

(NO): Put your stuff in and ask yourself if it is Friday afternoon and no one else around any more?
* (YES): Start the dishwasher
* (NO): You may wait until you leave

In general it would be nice if all could care more about the kitchen. If
everyone would do care it would not be necessary for some of us to clean
up quite a mess, but only a little bit for all of us.

[[Category:Current Members]][[Category:internal]]

Common Practices at Remeis

2023-07-26T12:28:45Z

Nekrasov: /* Common Practices at Remeis */

== Common Practices at Remeis ==

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''We try to be as flexible as possible, and I trust that you are adults and do not exploit the system. A minimum time for coordination in the group and knowing what everybody is doing is necessary. This time is the group meeting, and for this reason you have to be there and you should be prepared to discuss what you're doing there. If you do something else on the side, this is also fine, but it should not negatively impact on your research. It is on you to be able to manage your different tasks, and the expectation is that research has to come first.''

=== Working Times ===

'''Added by a request of J. Wilms on 2016 June 15'''

Is is expected that you are in the office in Bamberg for at least ~3 days per week. Although we have flexible working times, arriving at 10 a.m. latest is a good practice to ensure significant overlap with your colleagues.

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''working from home or Erlangen is ok (except for [...] [the group meetings]), but [...] [your supervisor] and the people you're working with directly need to know where you are. This means that you need to be reachable by email or phone, and you need to be working. As a rule of thumb: BSc-, MSc-, and PhD-thesis work is the equivalent to a full time job, irrespective of what your contracts say. Full time means 40+ hours per week. If you're working on the side this is fine - you know that we try to be supportive here - but this does not mean that you should subtract off the time you're making money from the time you're spending on your research, which - I repeat myself - should keep you busy equivalent to a full time job. If you find that you cannot manage this schedule when working from home, then I strongly suggest that you go to the office.''

''Due to the international nature of our work, it is to be expected that you have to be able to attend telecons after 18:00.''

=== Illness & Vacation ===

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''if you are ill, always(!) notify Edith, [...] [your supervisor], *and* the people you're working with (i.e., all BSc/MSc students also have a PhD student as point of contact and (s)he should also know).''

''if you plan to go on vacation, talk to [...] [your supervisor] first. [...] [We] will usually say yes, but there are some times you should avoid not being here, especially times before project deadlines, proposal deadlines, and the lab courses. This applies to everybody in the group.''

''once your vacation has been approved or if you're going to a conference, put down the dates of your absence on the white board next to the xerox machine.''

=== X-ray Group Meeting ===

'''From an E-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''group meeting starts Tuesdays, 10:00. The presence of everybody in the group (hiwis, BSc, MSc, PhD, postdocs) is *mandatory*. The only reason not to show up is if you're ill or if you have a lecture. In this case, please let me know. Do not assume I remember because you told me two weeks ago...''

=== Remeis Calendar ===

There is a calendar with the schedule of Remeis events, tours, visiting persons etc. It is very useful for newbies to have it nearby:
https://www.sternwarte.uni-erlangen.de/calendar/month.php

Don't forget to sign-up, otherwise you will see only the public part.

=== AstroLab ===

Twise a year there is an event when students from the uni come to the observatory and make their lab work. People from the observatory guide and help the students. The lab course takes about a month (usually September and March - see the Remeis Calendar), and people are supposed to participate and should be present and available during that time. In general, it is expected that you neither take vacations nor go to conferences.

=== Journal Club ===

Incomplete [[intern:litclub|list of past Literature Clubs]]

'''From an e-mail by M. Oertel on 2016 June 14 to the X-ray gang'''

''[...] assume that *everybody currently working in the xray-group is participating*.''

''Litclub is always (except during lab) on Tuesdays at 11:30 after the [X-ray] group-meeting. On every Monday I randomly choose someone for the next Litclub. There's a list of astronomy-papers which I will then send to you and you choose one (ideally not strongly correlated to your current work) and prepare a ~10 minute summary-talk. The talk will be in English. You don't have to understand everything they did in the paper, you just have to explain the central idea. One of the main aspects is to practice fast-paper-reading-and-understanding, therefore it has to be on a short notice (meaning Monday morning). This is also to prevent you from spending a few days on preparing. If you come across any interesting paper you think could fit (even if you haven't read it) please send a link to me so that I can add it to the list. You can decline when I ask you on Mondays but please only do so if you have a deadline (proposal or thesis...)/are sick...''

''It really is a good opportunity to practice giving talks, summarizing content and also it is a nice get-together for discussing interesting astro-stuff''

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''Your attendance and active participation is very strongly suggested. It is good for you.''

'''Update - Jun 2022: LitClub is back!'''

Follow this page for relevant details: [[Litclub]]

=== PhD-Hat and -Celebration tradition ===

[[intern:phd_hat_list|List of future PhDs]]

'''From an e-mail by M. Kuehnel in 2016 June 14 to almost everybody'''

''[...] this tradition is not alive in every institute. From my personal experience I know places where PhDs just defend and vanish without getting a hat, party, or anything personal from the colleagues. This is not how your 3+ years should end.''

''We have the tradition at our institute that every PhD candidate gets a self-made hat after having defended her or his thesis. Also, a big party is organized for her or his after the defence. It is a common agreement that the hat and the party is *mainly build and organized by all other PhD students*. Of course, also contributions from bachelor or master students are very well welcomed, too. Thus, it is very much appreciate (if not expected) that /everybody/ contributes and not only a few. It is not expected, however, to spent hours, even ~20 minutes are enough (for, e.g., searching and printing a picture, which is supposed to be put on the hat).''

''The main organization of the hat building process and the party is traditionally done by the PhD student, which is supposed to finish her or his PhD next. [...] This person is''
* ''the initiator of the hat building process and the organization of the party by, e.g., writing emails to everybody (expect to the PhD candidate, of course) in the first place. Creating a wiki-page for the hat might be useful here as well.''
* ''not expected to do all the work, but rather delegate the different tasks and keep the overview, i.e., is the main contact in case of questions. Here, the contribution of everybody is needed to complete all tasks! Here, quasi-regular meetings scheduled by the responsible person have been helpful.''
* ''trying to keep everybody updated and informed about, e.g., the hat status or the defence date. As you see, nobody needs to be afraid of this job.''

''Furthermore (and here we are really privileged), our PhD supervisor sponsors the party and hat with a certain amount. The usual case in other institutes is that the PhD candidate her- or himself pays for the party! Note that often the sponsoring is not sufficient for all expenses. In the past, this was solved in an uncomplicated way by either "basst scho" ("it's fine") from the people who had small expenses (like for the hat) or by the main organizer [...].''

=== Dishwasher Etiquette ===

'''From an e-mail by S. Falkner in 2016 August 29 to everybody'''

[''Please follow the following guideline to avoid a messy kitchen, frustrated Coworkers and unnecessary excessive use of the dishwasher:] ''

In case the dishwasher is full, check if it is clean

(YES): Has it just finished and still hot?
* (YES): Open it completely for cooling and every one too see.
* (NO): Empty it COMPLETELY and put your dirty dishes in and check if there is other dirty stuff to put in!
(NO): Can you make some room for your stuff?
* (YES): Perfect, now you can start it if there is really no more room.
* (NO): Start it and EITHER clean your dishes in the sink (and do not just throw it in their) OR wait till the dishwasher is done and put it in then!.

In case the dishwasher is not full, please do a quick check if the dishes look clean:

(YES): Empty it COMPLETELY and put your dirty dishes in and check if there is other dirty stuff to put in! Especially on Monday mornings it may happen that the dishwasher is only half full but clean as someone was nice and turned it on Friday afternoon, such that the dishwasher doesn't grow to life over the weekend.

(NO): Put your stuff in and ask yourself if it is Friday afternoon and no one else around any more?
* (YES): Start the dishwasher
* (NO): You may wait until you leave

In general it would be nice if all could care more about the kitchen. If
everyone would do care it would not be necessary for some of us to clean
up quite a mess, but only a little bit for all of us.

[[Category:Current Members]][[Category:internal]]

Common Practices at Remeis

2023-07-26T12:19:06Z

Nekrasov: /* Remeis Calendar */

== Common Practices at Remeis ==

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''We try to be as flexible as possible, and I trust that you are adults and do not exploit the system. A minimum time for coordination in the group and knowing what everybody is doing is necessary. This time is the group meeting, and for this reason you have to be there and you should be prepared to discuss what you're doing there. If you do something else on the side, this is also fine, but it should not negatively impact on your research. It is on you to be able to manage your different tasks, and the expectation is that research has to come first.''

=== Working Times ===

'''Added by a request of J. Wilms on 2016 June 15'''

Is is expected that you are in the office in Bamberg for at least ~3 days per week. Although we have flexible working times, arriving at 10 a.m. latest is a good practice to ensure significant overlap with your colleagues.

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''working from home or Erlangen is ok (except for [...] [the group meetings]), but [...] [your supervisor] and the people you're working with directly need to know where you are. This means that you need to be reachable by email or phone, and you need to be working. As a rule of thumb: BSc-, MSc-, and PhD-thesis work is the equivalent to a full time job, irrespective of what your contracts say. Full time means 40+ hours per week. If you're working on the side this is fine - you know that we try to be supportive here - but this does not mean that you should subtract off the time you're making money from the time you're spending on your research, which - I repeat myself - should keep you busy equivalent to a full time job. If you find that you cannot manage this schedule when working from home, then I strongly suggest that you go to the office.''

''Due to the international nature of our work, it is to be expected that you have to be able to attend telecons after 18:00.''

=== Illness & Vacation ===

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''if you are ill, always(!) notify Edith, [...] [your supervisor], *and* the people you're working with (i.e., all BSc/MSc students also have a PhD student as point of contact and (s)he should also know).''

''if you plan to go on vacation, talk to [...] [your supervisor] first. [...] [We] will usually say yes, but there are some times you should avoid not being here, especially times before project deadlines, proposal deadlines, and the lab courses. This applies to everybody in the group.''

''once your vacation has been approved or if you're going to a conference, put down the dates of your absence on the white board next to the xerox machine.''

=== X-ray Group Meeting ===

'''From an E-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''group meeting starts Tuesdays, 10:00. The presence of everybody in the group (hiwis, BSc, MSc, PhD, postdocs) is *mandatory*. The only reason not to show up is if you're ill or if you have a lecture. In this case, please let me know. Do not assume I remember because you told me two weeks ago...''

=== Remeis Calendar ===

There is a calendar with the schedule of Remeis events, tours, visiting persons etc. It is very useful for newbies to have it nearby:
https://www.sternwarte.uni-erlangen.de/calendar/month.php

Don't forget to sign-up, otherwise you will see only the public part.

=== Journal Club ===

Incomplete [[intern:litclub|list of past Literature Clubs]]

'''From an e-mail by M. Oertel on 2016 June 14 to the X-ray gang'''

''[...] assume that *everybody currently working in the xray-group is participating*.''

''Litclub is always (except during lab) on Tuesdays at 11:30 after the [X-ray] group-meeting. On every Monday I randomly choose someone for the next Litclub. There's a list of astronomy-papers which I will then send to you and you choose one (ideally not strongly correlated to your current work) and prepare a ~10 minute summary-talk. The talk will be in English. You don't have to understand everything they did in the paper, you just have to explain the central idea. One of the main aspects is to practice fast-paper-reading-and-understanding, therefore it has to be on a short notice (meaning Monday morning). This is also to prevent you from spending a few days on preparing. If you come across any interesting paper you think could fit (even if you haven't read it) please send a link to me so that I can add it to the list. You can decline when I ask you on Mondays but please only do so if you have a deadline (proposal or thesis...)/are sick...''

''It really is a good opportunity to practice giving talks, summarizing content and also it is a nice get-together for discussing interesting astro-stuff''

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''Your attendance and active participation is very strongly suggested. It is good for you.''

'''Update - Jun 2022: LitClub is back!'''

Follow this page for relevant details: [[Litclub]]

=== PhD-Hat and -Celebration tradition ===

[[intern:phd_hat_list|List of future PhDs]]

'''From an e-mail by M. Kuehnel in 2016 June 14 to almost everybody'''

''[...] this tradition is not alive in every institute. From my personal experience I know places where PhDs just defend and vanish without getting a hat, party, or anything personal from the colleagues. This is not how your 3+ years should end.''

''We have the tradition at our institute that every PhD candidate gets a self-made hat after having defended her or his thesis. Also, a big party is organized for her or his after the defence. It is a common agreement that the hat and the party is *mainly build and organized by all other PhD students*. Of course, also contributions from bachelor or master students are very well welcomed, too. Thus, it is very much appreciate (if not expected) that /everybody/ contributes and not only a few. It is not expected, however, to spent hours, even ~20 minutes are enough (for, e.g., searching and printing a picture, which is supposed to be put on the hat).''

''The main organization of the hat building process and the party is traditionally done by the PhD student, which is supposed to finish her or his PhD next. [...] This person is''
* ''the initiator of the hat building process and the organization of the party by, e.g., writing emails to everybody (expect to the PhD candidate, of course) in the first place. Creating a wiki-page for the hat might be useful here as well.''
* ''not expected to do all the work, but rather delegate the different tasks and keep the overview, i.e., is the main contact in case of questions. Here, the contribution of everybody is needed to complete all tasks! Here, quasi-regular meetings scheduled by the responsible person have been helpful.''
* ''trying to keep everybody updated and informed about, e.g., the hat status or the defence date. As you see, nobody needs to be afraid of this job.''

''Furthermore (and here we are really privileged), our PhD supervisor sponsors the party and hat with a certain amount. The usual case in other institutes is that the PhD candidate her- or himself pays for the party! Note that often the sponsoring is not sufficient for all expenses. In the past, this was solved in an uncomplicated way by either "basst scho" ("it's fine") from the people who had small expenses (like for the hat) or by the main organizer [...].''

=== Dishwasher Etiquette ===

'''From an e-mail by S. Falkner in 2016 August 29 to everybody'''

[''Please follow the following guideline to avoid a messy kitchen, frustrated Coworkers and unnecessary excessive use of the dishwasher:] ''

In case the dishwasher is full, check if it is clean

(YES): Has it just finished and still hot?
* (YES): Open it completely for cooling and every one too see.
* (NO): Empty it COMPLETELY and put your dirty dishes in and check if there is other dirty stuff to put in!
(NO): Can you make some room for your stuff?
* (YES): Perfect, now you can start it if there is really no more room.
* (NO): Start it and EITHER clean your dishes in the sink (and do not just throw it in their) OR wait till the dishwasher is done and put it in then!.

In case the dishwasher is not full, please do a quick check if the dishes look clean:

(YES): Empty it COMPLETELY and put your dirty dishes in and check if there is other dirty stuff to put in! Especially on Monday mornings it may happen that the dishwasher is only half full but clean as someone was nice and turned it on Friday afternoon, such that the dishwasher doesn't grow to life over the weekend.

(NO): Put your stuff in and ask yourself if it is Friday afternoon and no one else around any more?
* (YES): Start the dishwasher
* (NO): You may wait until you leave

In general it would be nice if all could care more about the kitchen. If
everyone would do care it would not be necessary for some of us to clean
up quite a mess, but only a little bit for all of us.

[[Category:Current Members]][[Category:internal]]

Common Practices at Remeis

2023-07-26T12:18:32Z

Nekrasov: /* Common Practices at Remeis */

== Common Practices at Remeis ==

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''We try to be as flexible as possible, and I trust that you are adults and do not exploit the system. A minimum time for coordination in the group and knowing what everybody is doing is necessary. This time is the group meeting, and for this reason you have to be there and you should be prepared to discuss what you're doing there. If you do something else on the side, this is also fine, but it should not negatively impact on your research. It is on you to be able to manage your different tasks, and the expectation is that research has to come first.''

=== Working Times ===

'''Added by a request of J. Wilms on 2016 June 15'''

Is is expected that you are in the office in Bamberg for at least ~3 days per week. Although we have flexible working times, arriving at 10 a.m. latest is a good practice to ensure significant overlap with your colleagues.

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''working from home or Erlangen is ok (except for [...] [the group meetings]), but [...] [your supervisor] and the people you're working with directly need to know where you are. This means that you need to be reachable by email or phone, and you need to be working. As a rule of thumb: BSc-, MSc-, and PhD-thesis work is the equivalent to a full time job, irrespective of what your contracts say. Full time means 40+ hours per week. If you're working on the side this is fine - you know that we try to be supportive here - but this does not mean that you should subtract off the time you're making money from the time you're spending on your research, which - I repeat myself - should keep you busy equivalent to a full time job. If you find that you cannot manage this schedule when working from home, then I strongly suggest that you go to the office.''

''Due to the international nature of our work, it is to be expected that you have to be able to attend telecons after 18:00.''

=== Illness & Vacation ===

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''if you are ill, always(!) notify Edith, [...] [your supervisor], *and* the people you're working with (i.e., all BSc/MSc students also have a PhD student as point of contact and (s)he should also know).''

''if you plan to go on vacation, talk to [...] [your supervisor] first. [...] [We] will usually say yes, but there are some times you should avoid not being here, especially times before project deadlines, proposal deadlines, and the lab courses. This applies to everybody in the group.''

''once your vacation has been approved or if you're going to a conference, put down the dates of your absence on the white board next to the xerox machine.''

=== X-ray Group Meeting ===

'''From an E-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''group meeting starts Tuesdays, 10:00. The presence of everybody in the group (hiwis, BSc, MSc, PhD, postdocs) is *mandatory*. The only reason not to show up is if you're ill or if you have a lecture. In this case, please let me know. Do not assume I remember because you told me two weeks ago...''

=== Remeis Calendar ===

''There is a calendar with the schedule of Remeis events, tours, visiting persons etc. It is very useful for newbies to have it nearby:
https://www.sternwarte.uni-erlangen.de/calendar/month.php''

''Don't forget to sign-up, otherwise you will see only the public part.''

=== Journal Club ===

Incomplete [[intern:litclub|list of past Literature Clubs]]

'''From an e-mail by M. Oertel on 2016 June 14 to the X-ray gang'''

''[...] assume that *everybody currently working in the xray-group is participating*.''

''Litclub is always (except during lab) on Tuesdays at 11:30 after the [X-ray] group-meeting. On every Monday I randomly choose someone for the next Litclub. There's a list of astronomy-papers which I will then send to you and you choose one (ideally not strongly correlated to your current work) and prepare a ~10 minute summary-talk. The talk will be in English. You don't have to understand everything they did in the paper, you just have to explain the central idea. One of the main aspects is to practice fast-paper-reading-and-understanding, therefore it has to be on a short notice (meaning Monday morning). This is also to prevent you from spending a few days on preparing. If you come across any interesting paper you think could fit (even if you haven't read it) please send a link to me so that I can add it to the list. You can decline when I ask you on Mondays but please only do so if you have a deadline (proposal or thesis...)/are sick...''

''It really is a good opportunity to practice giving talks, summarizing content and also it is a nice get-together for discussing interesting astro-stuff''

'''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang'''

''Your attendance and active participation is very strongly suggested. It is good for you.''

'''Update - Jun 2022: LitClub is back!'''

Follow this page for relevant details: [[Litclub]]

=== PhD-Hat and -Celebration tradition ===

[[intern:phd_hat_list|List of future PhDs]]

'''From an e-mail by M. Kuehnel in 2016 June 14 to almost everybody'''

''[...] this tradition is not alive in every institute. From my personal experience I know places where PhDs just defend and vanish without getting a hat, party, or anything personal from the colleagues. This is not how your 3+ years should end.''

''We have the tradition at our institute that every PhD candidate gets a self-made hat after having defended her or his thesis. Also, a big party is organized for her or his after the defence. It is a common agreement that the hat and the party is *mainly build and organized by all other PhD students*. Of course, also contributions from bachelor or master students are very well welcomed, too. Thus, it is very much appreciate (if not expected) that /everybody/ contributes and not only a few. It is not expected, however, to spent hours, even ~20 minutes are enough (for, e.g., searching and printing a picture, which is supposed to be put on the hat).''

''The main organization of the hat building process and the party is traditionally done by the PhD student, which is supposed to finish her or his PhD next. [...] This person is''
* ''the initiator of the hat building process and the organization of the party by, e.g., writing emails to everybody (expect to the PhD candidate, of course) in the first place. Creating a wiki-page for the hat might be useful here as well.''
* ''not expected to do all the work, but rather delegate the different tasks and keep the overview, i.e., is the main contact in case of questions. Here, the contribution of everybody is needed to complete all tasks! Here, quasi-regular meetings scheduled by the responsible person have been helpful.''
* ''trying to keep everybody updated and informed about, e.g., the hat status or the defence date. As you see, nobody needs to be afraid of this job.''

''Furthermore (and here we are really privileged), our PhD supervisor sponsors the party and hat with a certain amount. The usual case in other institutes is that the PhD candidate her- or himself pays for the party! Note that often the sponsoring is not sufficient for all expenses. In the past, this was solved in an uncomplicated way by either "basst scho" ("it's fine") from the people who had small expenses (like for the hat) or by the main organizer [...].''

=== Dishwasher Etiquette ===

'''From an e-mail by S. Falkner in 2016 August 29 to everybody'''

[''Please follow the following guideline to avoid a messy kitchen, frustrated Coworkers and unnecessary excessive use of the dishwasher:] ''

In case the dishwasher is full, check if it is clean

(YES): Has it just finished and still hot?
* (YES): Open it completely for cooling and every one too see.
* (NO): Empty it COMPLETELY and put your dirty dishes in and check if there is other dirty stuff to put in!
(NO): Can you make some room for your stuff?
* (YES): Perfect, now you can start it if there is really no more room.
* (NO): Start it and EITHER clean your dishes in the sink (and do not just throw it in their) OR wait till the dishwasher is done and put it in then!.

In case the dishwasher is not full, please do a quick check if the dishes look clean:

(YES): Empty it COMPLETELY and put your dirty dishes in and check if there is other dirty stuff to put in! Especially on Monday mornings it may happen that the dishwasher is only half full but clean as someone was nice and turned it on Friday afternoon, such that the dishwasher doesn't grow to life over the weekend.

(NO): Put your stuff in and ask yourself if it is Friday afternoon and no one else around any more?
* (YES): Start the dishwasher
* (NO): You may wait until you leave

In general it would be nice if all could care more about the kitchen. If
everyone would do care it would not be necessary for some of us to clean
up quite a mess, but only a little bit for all of us.

[[Category:Current Members]][[Category:internal]]

Slurm

2023-07-17T10:12:34Z

Nekrasov: /* Quick users tutorial */

[[Category:Slurm]]

= About =

In order to spread the workload of scientific computations on our compute nodes the resource manager SLURM is used.

From [https://slurm.schedmd.com/overview.html official SLURM website]:

''Slurm is an open source, fault-tolerant, and highly scalable cluster management and job scheduling system for large and small Linux clusters. Slurm requires no kernel modifications for its operation and is relatively self-contained. As a cluster workload manager, Slurm has three key functions. First, it allocates exclusive and/or non-exclusive access to resources (compute nodes) to users for some duration of time so they can perform work. Second, it provides a framework for starting, executing, and monitoring work (normally a parallel job) on the set of allocated nodes. Finally, it arbitrates contention for resources by managing a queue of pending work.''
[[File:entities_slurm.gif|frame|Different entities of Slurm]]
From [https://slurm.schedmd.com/overview.html official SLURM website]:

''SLURM manages the cluster in partitions, which are a set of compute nodes. Note, that partitions may overlap, e.g. one compute node may be in two or more partitions. A node is a physical computer which provides consumable resources: CPUs and Memory. A CPU does not necessarily have to be a physical processor but is more like a virtual CPU to run one single task on. A dual core with hyper threading technology, for instance, would show up as a node with 4 CPUs consisting of two cores with the capability of running two threads on each core. Physical memory is defined in MB.''

The following partitions exist in the current setup:

* remeis: default partition, all machines, timelimit: 7days
* erosita: only available for selected people involved in the project, timelimit: infinite
* debug: very high priority partition for software development, timelimit: 1h

= Quick users tutorial =

This tutorial will give you a quick overview over the most important commands. The [https://slurm.schedmd.com/overview.html official SLURM website] provides more detailed information.

Important information about running jobs with remeis cluster for the first time: you need to write an email to the administrators to give you permission.

== Get cluster status ==
In order to get an overview of the cluster, type
<pre>
sinfo
</pre>
This command offers a variety of options how to format the output. In order to get a detailed output while focusing on the nodes rather than the partitions, type
<pre>
sinfo -N -l
</pre>
An overview over the available partitions can be shown with
<pre>
scontrol show partition
</pre>
an the current queued and running jobs can be displayed using
<pre>
squeue
</pre>

== Executing a job in real-time ==
In order to allocate for instance 1 CPUs and 100MB of memory for real-time work, type
<pre>
salloc --mem-per-cpu=100 -n1 bash
</pre>
Your bash is now connected to the compute nodes. In order to execute a script use the srun-command
<pre>
srun my_script.sh
</pre>
Each srun-command you execute now is interpreted as a job step. The currently running job step of submitted jobs can be displayed using
<pre>
squeue -s
</pre>

You can also start a job by simply use the srun command and specify your requirements. In the following case, srun will allocate 100MB of memory and 1 CPU(s) for 1 task, only for the duration of execution.
<pre>
srun --mem-per-cpu=100 -n1 my_script.sh
</pre>
If resources are available your job will start immediately.

== Submitting a job for later execution ==

The most convenient way is to submit a job script for later execution. The top part of the script contains scheduling information for SLURM, the more information you provide here, the better.

First of all, a job name is specified, followed by a maximum time. If your job exceeds this time, it will be killed. However, do not overestimate too much because short jobs might start earlier. Acceptable time formats include "minutes", "minutes:seconds", "hours:minutes:seconds", "days-hours", "days-hours:minutes" and "days-hours:minutes:seconds". The output file is set to be test-job(jobID).out and the partition to run the job on is "remeis".
The sbatch-script itself will not initiate any job but only allocate the resources. The ''ntasks'' and ''mem-per-cpu'' options advise the SLURM controller that job steps run within the allocation will launch a maximum of number tasks and to provide for sufficient resources.

The ''srun'' commands in the job script launch the job steps. The example below thus consists of two job steps. Each of the ''srun'' commands may have own requirements concerning memory any may also spawn less tasks than given in the header of the script file. However, the values in the header may never be exceeded!
<pre>
#!/bin/bash
#SBATCH --job-name my_first_job
#SBATCH --time 05:00
#SBATCH --output test-job_%A_%a.out
#SBATCH --error test-job_%A_%a.err
#SBATCH --partition=remeis
#SBATCH --ntasks=4
#SBATCH --mem-per-cpu=100
srun -l my_script1.sh
srun -l my_script2.sh
</pre>
The ''-l'' parameter of ''srun'' will print the task number in front of a line of stdout/err. You can submit this script by saving it in a file, e.g. ''my_first_job.slurm'', and sumitting it using
<pre>
cepheus:~> sbatch my_first_job.slurm
Submitted batch job 144
</pre>

You can check the estimated starting time of your job using
<pre>
squeue --start
</pre>

== Submitting a job array ==

In order to submit a array of jobs with the same requirements you have to modify your script file.
The script above is going to spawn 4 jobs each consisting of one srun command. Note the presence of the new environment variable ''${SLURM_ARRAY_TASK_ID}'' which might be useful for your work. In this example we start an isis-script with different input values. You can also simply use different scripts.
<pre>
#!/bin/bash
#SBATCH --partition remeis
#SBATCH --job-name important_job
#SBATCH --ntasks=1
#SBATCH --time 00:05:00
#SBATCH --output /home/dauser/tmp/jobscript_beta.%A_%a.out
#SBATCH --error /home/dauser/tmp/jobscript_beta.%A_%a.err
#SBATCH --array 0-3

cd /home/user/script/

COMMAND[0]="./sim_script.sl 0.00"
COMMAND[1]="./sim_script.sl 0.10"
COMMAND[2]="./sim_script.sl 0.20"
COMMAND[3]="./sim_script.sl 0.30"

srun /usr/bin/nice -n +19 ${COMMAND[$SLURM_ARRAY_TASK_ID]}
</pre>
Note that it is often much better not to hard code the parameters of your job in the batch script, but to move that logic into the simulation script:
<pre>
#!/bin/bash
#SBATCH --partition remeis
#SBATCH --job-name important_job
#SBATCH --ntasks=1
#SBATCH --time 00:05:00
#SBATCH --output /home/dauser/tmp/jobscript_beta.%A_%a.out
#SBATCH --error /home/dauser/tmp/jobscript_beta.%A_%a.err
#SBATCH --array 0-3

cd /home/user/script/
srun /usr/bin/nice -n +19 ./script --param=${SLURM_ARRAY_TASK_ID}
</pre>
In this case, the script will use the command line parameter param to identify what is to be done (all programming languages have ways to access command line parameters, for isis, you might want to take a look at the cmdopt tool, for perl use Getopt::Long, for C use getopt or getopt_long in the Gnu C library, for python use the argparse module).

As above, this code might be saved in a file, for example ''job.slurm'' can be executed using
<pre>
sbatch job.slurm
</pre>

If you need a specific machine to run your job on, you can use
<pre>
#SBATCH --nodelist=leo,draco
</pre>
If you have a job with high I/O and/or traffic on the network you can limit the number of jobs running simultaneously (to 2 in this example) by
<pre>
#SBATCH --array 0-3%2
</pre>
SLURM will only allocate resources on the given nodes. However, if all nodes in 'nodelist' cannot fulfill the job requirements, SLURM will also allocate other machines.

If you would like to cancel jobs 1, 2 and 3 from job array 20 use
<pre>
scancel 20_[1-3]
</pre>
Note that you might have to escape the brackets when using the above command, e.g.,
<pre>
tcsh:~> scancel 20_\[1-3\]
</pre>
If you want to cancel the whole array, ''scancel'' works as usual
<pre>
scancel 20
</pre>
Note, there is also the option to modify requirements of single jobs later using ''scontrol update job=101_1 ...''.

If you have jobs which are dependent on the result of others or if you want a more detailed description concerning job arrays you can find it in the official SLURM manual: [[https://slurm.schedmd.com/job_array.html]]

== Submitting a job array where each command needs to change into a different directory ==

In order to allow each command of the job array to change into an individual directory (as opposed to all into the same directory as above), modify the script as follows:
<pre>
#!/bin/bash
#SBATCH --partition remeis
#SBATCH --job-name important_job
#SBATCH --ntasks=1
#SBATCH --time 00:05:00
#SBATCH --output /home/dauser/tmp/jobscript_beta.%A_%a.out
#SBATCH --error /home/dauser/tmp/jobscript_beta.%A_%a.err
#SBATCH --array 0-3

DIR[0]="/home/user/dir1"
DIR[1]="/home/user/dir2"
DIR[2]="/userdata/user/dir3"
DIR[3]="/userdata/user/dir4"

cd ${DIR[$SLURM_ARRAY_TASK_ID]}

COMMAND[0]="./sim_script.sl 0.00"
COMMAND[1]="./sim_script.sl 0.10"
COMMAND[2]="./sim_script.sl 0.20"
COMMAND[3]="./sim_script.sl 0.30"

srun /usr/bin/nice -n +19 ${COMMAND[$SLURM_ARRAY_TASK_ID]}
</pre>
This also works with paths relative to the directory where the slurm script was submitted.

As also discussed above, as an alternative you might want to move the logic concerning the working directories and parameters into your script.

== Submitting a job array with varying number of tasks ==

This is not really a job "array". But to execute multiple jobs with different number of tasks one can use multiple
srun calls chained with an '&'. This will submit the jobs at once but allow one to specify job parameters individually
for each job.

Example: Simultaneous fit of multiple datasets with different functions

<syntaxhighlight lang="bash" line='line'>
#!/bin/bash
#SBATCH --job-name my_simultaneous_fit_%n
#SBATCH --time 05:00
#SBATCH --output test-job_%A_%a.out
#SBATCH --error test-job_%A_%a.err
#SBATCH --partition=remeis
#SBATCH --mem-per-cpu=100
srun -l my_complicated_fit.sh 2 --ntasks=2 & # my_complicated_fit fits 2 line centers -> needs 2 tasks
srun -l my_complicated_fit.sh 4 --ntasks=4 # my_complicated_fit fits 4 line centers -> needs 4 tasks
</syntaxhighlight>

== Temporary files on a local disk, aka scratch ==
Often computational tasks need to write temporary files, which can be written to a disk local to the computer the job is running on. This disk is mostly called "scratch" disk. In the case of the remeis observatory every user can freely create a directory inside the /scratch1 directory. It is very useful to first create a directory with your own user name, such as /scratch1/weber/ and then create an appropriate subdirectory there for a given job.

It is very important that each job cleans up after itself, otherwise the scratch disk will just run full and cause problems for yourself and everybody else. You can use ansible like this to run a command on every coputer:
<pre>
ansible all -a "/your/command/here" -l
</pre>
Ansible does not accept wildcards in the command so it makes sense to create a script in your home directory which does the cleanup and can then be run on all computers using ansible after all your jobs are done.

== Graphical jobs (srun.x11) ==
Not all applications run only on the commandline. Slurm does not support graphical applications natively but there is a wrapper script available which allocates the resources on the cluster and then provides a [[screen]] session inside a running [[SSH|SSH-session]] to the host where the resources have been allocated on. For example
<pre>
[12:06]weber@lynx:~$ srun.x11
</pre>
results in a new shell :
<pre>
[12:06]weber@messier15:~$
</pre>

which forwards the window if you start a graphical program for example
<pre>
[12:06]weber@messier15:~$ kate
</pre>
would open the text editor [[https://de.wikipedia.org/wiki/Kate_(KDE) kate]]. However, this only uses the standard resources set for the remeis partition. If you have other requirements you can also specify these in exactly the same way as for ''srun'':
<pre>
[12:06]weber@lynx:~$ srun.x11 --mem=2G
</pre>
would allocate 2GB of memory for the application.

== Using the ''erosita'' partition (serpens)==

If you are allowed to use the eRosita Partition, contact the admin list. Once your username is added to the list of privileged users, you just have to add
<pre>
#SBATCH --partition=erosita
#SBATCH --account=erosita
</pre>
to your jobfiles.

== Other useful commands ==

* ''sstat'' Real-time status information of your running jobs

* ''sattach <jobid.stepid>'' Attach to stdI/O of one of your running jobs

* ''scancel [OPTIONS...] [job_id[_array_id][.step_id]] [job_id[_array_id][.step_id]...]'' Cancel the execution of one of your job arrays/jobs/job steps.

* ''scontrol'' Administration tool, you can for example use this to modify the requirements of your jobs. You can for exaple show your jobs ''show jobs'' or update the time limit ''update JobId= TimeLimit=2''.

* ''smap'' graphically view information about Slurm jobs, partitions, and set configurations parameters.

* ''sview'' graphical user interface for those who prefer clicking over typing. X-Server required.

= SLURM and MPI =
== About MPI ==
MPI (the Message Passing Interface) makes it possible to run parallel processes on CPUs of different hosts. To do so it uses TCP packets to communicate via the normal network connection. Some tasks can profit a lot of using more cores for computation.
At Remeis MPICH2 is used for initialisation of MPI tasks which is well supported within Slurm. The process manager is called '''pmi2''' and is set as default for srun. If an older MPI process manager is needed, for example for older MPI applications used in '''torque''', it can be set with
<pre>
#SBATCH --mpi=
</pre>
in the submission script.
<pre>
srun --mpi=list
</pre>
provides a list of supported MPI process managers.

The implementation of MPI for SLang/ISIS is called '''SLMPI'''.

== Best practice for MPI tasks ==

The usage of MPI might cause continuously high network traffic especially on the host which holds the master process. Please consider this when deciding which nodes are used for the job. It's a good idea to provide servers (e.g. leo or lupus) with the ''--nodelist='' option one of which is then used to hold the master process since nobody is sitting in front of it and trying to use a browser. Additional nodes are allocated automatically by Slurm if required to fit the ''--ntasks'' / ''-n'' option.

MPI jobs depend on all allocated nodes to be up and running properly, so I'd like to use this opportunity to remind about shutting down/rebooting PCs on your own without any permission can abort a whole MPI job.

== Requirements and Tips ==
To use MPI obviously the application or function used should support MPI. Examples range from programs written in C using some MPI features and compiled with the ''mpicc'' compiler to common ISIS-functions such as ''mpi_emcee'' or ''mpi_fit_pars''.

Keep in mind that everything in the compiled programs/scripts which is not an MPI compatible function is executed on each node on its own. For example in ISIS with ''-n 20'':
<pre>
fit_counts;
</pre>
would fit the defined function to the dataset 20 times at once. That's not very helpful so think about which tasks should be performed in the actual MPI process. Special care has to be taken if something has to be saved as a file. Consider:
<pre>
save_par("test.par");
</pre>
with ''-n 20''. This would save the current fit parameters to '''test.par''' in the working directory 20 times at exactly the same time. This might be helpful if the file is needed on the scratch disk of each node, but doing this on for example ''/userdata'' can cause serious trouble. The function ''mpi_master_only'' can be used to perform a user defined task in an MPI job only once. Best way is to only submit an MPI job to Slurm which only contains actual MPI functions. If some models in ISIS are used which output something to stdout or stderr while loading these messages are also generated 20 times since it's loaded in each process individually.

== Usage ==
If the job is a valid MPI process then the submission works exactly like for any other job:
<pre>
#!/bin/bash
#SBATCH --job-name my_first_mpi_job
#SBATCH ...
#SBATCH --ntasks=20
cd /my/working/dir
srun /usr/bin/nice -n +15 ./my_mpi_script
</pre>
It might be necessary to set a higher memory usage than for the according non MPI job since some applications try to limit the network traffic by just copying the required data to each node in the first place.

Also make sure that if it is necessary to specify the number of child processes in the application itself, set it to the same as with the ''--ntasks'' / ''-n'' option in the submission. An example would be the ''num_slaves'' qualifier in ''mpi_emcee''.

Note that the ''srun'' command does not contain ''mpiexec'' or ''mpirun'' which were used in older versions of MPI to launch the processes. The processes manager ''pmi2'' is built into Slurm and makes it possible that Slurm itself can initialize the network communication with the ''srun'' command only.

Of course it's also possible to run the MPI process directly from the commandline. As an example let's have a look at the calculation of pi with the MPI program ''cpi''. The program comes with the source code of MPICH2 and is compiled in the ''check'' rule. It's located in
<pre>
/data/system/software/mpich/mpich-3.2/examples
</pre>
To run the calculation in 10 parallel processes directly from the commandline use:
<pre>
[1:11]weber@lynx:/data/system/software/mpich/mpich-3.2/examples> srun -n 10 ./cpi
Process 0 of 10 is on aquarius
Process 1 of 10 is on ara
Process 6 of 10 is on asterion
Process 2 of 10 is on ara
Process 8 of 10 is on asterion
Process 7 of 10 is on asterion
Process 3 of 10 is on aranea
Process 5 of 10 is on aranea
Process 4 of 10 is on aranea
Process 9 of 10 is on cancer
pi is approximately 3.1415926544231256, Error is 0.0000000008333325
wall clock time = 0.010601
</pre>
As we can see Slurm launched 10 processes distributed to aquarius, ara, asterion, aranea and cancer. Keep in mind that running MPI interactively doesn't really make sense. The best way to go is to write a submission script like explained above and let Slurm handle the initialisation.

PhD hat Ekaterina

2023-06-09T09:36:16Z

Nekrasov:

Early start, but we will forget all of this again if not wrote down!

<ol>
<li>Burning things (especially if this gets your proposals through)</li>
<li>
CoC DM, of the most unorganized and untalented investigators out there
[[File:HaH.jpg|200px|thumb|left]]</li>
<li>"Drop your pants and show me the accreting millisecond pulsar!" </li>
<li> "Oomka" the de-stress bear. </li>
<li> "Have you considered a neutron star?" </li>
<li> Thesis writing on the beach </li>
<li> "We need modelling here!" "call him!" "Don't have his number...and a restraining order..."</li>
<li> Plan B: Renting skis in Alps</li>
<li> Club for Katya for the Xmag zoom room</li>
<li> Kraut! -- for sausage in Poetry for Neanderthals </li>
<li> There HAS to be a Cthulhu, right? I will crochet one, if everyone's happy with that. [AZ] </li>
<li> "Hallo wie gehts?" -> slapping meme "NO GERMAN" [SH] </li>
<li> Meme: participating in the Stanford Experiment instead of separate pre-exercises [SH] </li>
<li> Pic: Wilhelm Tell in the garden [SH] </li>
<li> Pic: Grim Reaper in the garden during the lab [SH] </li>
<li> No PhD without MSc, so I would add the emblem of the Faculty of Physics (MSU - Katya's alma mater) - the emblem is very simple - the square root of factorial \sqrt{\,!}, e.g. https://www.pngegg.com/en/png-eyszt - we could make not exactly that picture, but something referring to that. "Remember your roots" [AN] </li>
</ol>

[[Category:Internal]]

Skivergnuegen 2023

2023-01-13T16:56:29Z

Nekrasov: /* Fahrer */

'''Remeis Skifahren 2023''' The same procedure as every year ;-)
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.

[[File:154854 silvretta-montafon-panorama.jpeg|right|700px]]

== Allgemeine Infos ==

*Ferienwohnung(en):
**Wir kommen wieder unter im [https://www.grandau.at/montafon/zimmer/ferienhaus-enzian Haus Enzian] des [https://www.grandau.at/ Sporthotels Grandau].
**Adresse des Sporthotel: Montafonerstraße 274a, 6791 St. Gallenkirch, Österreich. Unsere Unterkünfte liegen im Türkeiweg.

*Skigebiet: Montafon (Vorarlberg)
**Skigebiet Karte: https://winter.intermaps.com/montafon?lang=de
**Skipass Preise: https://www.silvretta-montafon.at/de/onlineshop/ticket-uebersicht
**Wer nicht alle 7 Tage Skifahren möchte: Es gibt Angebote wie z.B. 5 aus 6, mit einem solchen Skipass kann man innerhalb von 6 Tagen an 5 beliebigen Tagen skifahren.

*Skiverleih: [http://www.sportharry.at/ Sport Harry], direkt an der Talstation.

== Unterkunft ==
=== Aufteilung ===

Dieses Jahr gibt es nur die Hütte mit folgenden Zimmern (wir sind insgesamt 14, also bleiben keine Plätze frei).

{| class="wikitable"
! scope="col" | Zimmer
! scope="col" | Insassen
|-
! scope="row" | 2-er
| Amy, Aafia

|-
! scope="row" | 3-er
| Jakob, Max, Katya
|-
! scope="row" | 4-er
| Eva, Steffen, Flo, Christian
|-
! scope="row" | 5-er
| Basti, Philipp, Ole, Alex
|}

== Fahrer ==
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.

'''Auf der Suche nach einer Mitfahrgelegenheit: '''

{| class="wikitable"
! scope="col" | Fahrer
! scope="col" | # Plätze
! scope="col" | Anreise
! scope="col" | Mitfahrer Anreise
! scope="col" | Abreise
! scope="col" | Mitfahrer Abreise
! scope="col" | Skimitnahme
! scope="col" | Kommentar
|-
|Eva
|0(3)
|Samstag
|Steffen+Christian
|Samstag?
|Steffen+Christian
|eigene ja
|Auto ist voll
|-
|Max
|0(3)
|Samstag (from Arlberg)
|Jakob+Katya
|Samstag
|Jakob+Katya
|eigene ja
|Auto ist voll
|-
|Basti
|2(2)
|Sunday (early morning)
|
|Friday (lunch time)
|
|Ja
|I will be at the airport NUE (alternative meeting point would be Nuremberg trainstation)
|-
|Johannes
|3
|Saturday from Munich
|?
|Saturday until Crailsheim
|?
|Ja
|on the way to Montafon I could pick up people and material in Munich. On the way back I could take people to Crailsheim station (direct train to Nürnberg). Decision about skiing on Saturday and therefore leave time in Montafon dependent on local conditions.
|-

|-

|-

|-
|}

== Schwarzes Brett ==

=== Essen ===
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.

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.

'''Essenplan:'''
*Samstag: Spaghetti Bolognese + veg. Bolognese
*Sonntag: Käse Spätzle
*Montag: Burritos
*Dienstag: Risotto
*Mittwoch: Gulasch
*Donnerstag: Kartoffeln mit Kräuter-Quark
*Freitag: Dal mit Reis (od. Curry mit Suesskartoffeln )

Einkaufsliste von 2022 (letztes Jahr): https://docs.google.com/document/d/166b_mIXxmoAgcv1upIGremd_36E1fmwwxsQADP2uEv8/

@Christian: Vegane Option entwender selbst mitbringen oder hier mit reinschreiben (falls man die einfach bekommt)

=== Alkohol/Party ===

Stiegl (Johannes)

=== Spiele ===

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:

''* Secret Hitler (Johannes)''

=== Sonstiges ===

=== Alternativprogramm ===
* Rodeln (http://www.montafon.at/de/urlaubswelten/echte_naturliebhaber/rodeln)
* Schneeschuhwandern (http://www.montafon.at/schneeschuhwanderungen)
* Therme (http://www.montafon.at/schwimmen), z.B. http://www.aqua-dome.at/de (ca. 130km entfernt!)

[[Category:Internal]]

Skivergnuegen 2023

2023-01-13T16:55:52Z

Nekrasov: /* Unterkunft */

'''Remeis Skifahren 2023''' The same procedure as every year ;-)
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.

[[File:154854 silvretta-montafon-panorama.jpeg|right|700px]]

== Allgemeine Infos ==

*Ferienwohnung(en):
**Wir kommen wieder unter im [https://www.grandau.at/montafon/zimmer/ferienhaus-enzian Haus Enzian] des [https://www.grandau.at/ Sporthotels Grandau].
**Adresse des Sporthotel: Montafonerstraße 274a, 6791 St. Gallenkirch, Österreich. Unsere Unterkünfte liegen im Türkeiweg.

*Skigebiet: Montafon (Vorarlberg)
**Skigebiet Karte: https://winter.intermaps.com/montafon?lang=de
**Skipass Preise: https://www.silvretta-montafon.at/de/onlineshop/ticket-uebersicht
**Wer nicht alle 7 Tage Skifahren möchte: Es gibt Angebote wie z.B. 5 aus 6, mit einem solchen Skipass kann man innerhalb von 6 Tagen an 5 beliebigen Tagen skifahren.

*Skiverleih: [http://www.sportharry.at/ Sport Harry], direkt an der Talstation.

== Unterkunft ==
=== Aufteilung ===

Dieses Jahr gibt es nur die Hütte mit folgenden Zimmern (wir sind insgesamt 14, also bleiben keine Plätze frei).

{| class="wikitable"
! scope="col" | Zimmer
! scope="col" | Insassen
|-
! scope="row" | 2-er
| Amy, Aafia

|-
! scope="row" | 3-er
| Jakob, Max, Katya
|-
! scope="row" | 4-er
| Eva, Steffen, Flo, Christian
|-
! scope="row" | 5-er
| Basti, Philipp, Ole, Alex
|}

== Fahrer ==
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.

'''Auf der Suche nach einer Mitfahrgelegenheit: '''

{| class="wikitable"
! scope="col" | Fahrer
! scope="col" | # Plätze
! scope="col" | Anreise
! scope="col" | Mitfahrer Anreise
! scope="col" | Abreise
! scope="col" | Mitfahrer Abreise
! scope="col" | Skimitnahme
! scope="col" | Kommentar
|-
|Eva
|0(3)
|Samstag
|Steffen+Christian
|Samstag?
|Steffen+Christian
|eigene ja
|Auto ist voll
|-
|Max
|0(3)
|Samstag (from Arlberg)
|Jakob+Katya
|Samstag
|Jakob+Katya
|eigene ja
|Auto ist voll
|-
|Basti
|1(2)
|Sunday (early morning)
|Alexey
|Friday (lunch time)
|Alexey
|Ja
|I will be at the airport NUE (alternative meeting point would be Nuremberg trainstation)
|-
|Johannes
|3
|Saturday from Munich
|?
|Saturday until Crailsheim
|?
|Ja
|on the way to Montafon I could pick up people and material in Munich. On the way back I could take people to Crailsheim station (direct train to Nürnberg). Decision about skiing on Saturday and therefore leave time in Montafon dependent on local conditions.
|-

|-

|-

|-
|}

== Schwarzes Brett ==

=== Essen ===
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.

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.

'''Essenplan:'''
*Samstag: Spaghetti Bolognese + veg. Bolognese
*Sonntag: Käse Spätzle
*Montag: Burritos
*Dienstag: Risotto
*Mittwoch: Gulasch
*Donnerstag: Kartoffeln mit Kräuter-Quark
*Freitag: Dal mit Reis (od. Curry mit Suesskartoffeln )

Einkaufsliste von 2022 (letztes Jahr): https://docs.google.com/document/d/166b_mIXxmoAgcv1upIGremd_36E1fmwwxsQADP2uEv8/

@Christian: Vegane Option entwender selbst mitbringen oder hier mit reinschreiben (falls man die einfach bekommt)

=== Alkohol/Party ===

Stiegl (Johannes)

=== Spiele ===

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:

''* Secret Hitler (Johannes)''

=== Sonstiges ===

=== Alternativprogramm ===
* Rodeln (http://www.montafon.at/de/urlaubswelten/echte_naturliebhaber/rodeln)
* Schneeschuhwandern (http://www.montafon.at/schneeschuhwanderungen)
* Therme (http://www.montafon.at/schwimmen), z.B. http://www.aqua-dome.at/de (ca. 130km entfernt!)

[[Category:Internal]]

Skivergnuegen 2023

2023-01-08T13:09:58Z

Nekrasov: /* Fahrer */

'''Remeis Skifahren 2023''' The same procedure as every year ;-)
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.

[[File:154854 silvretta-montafon-panorama.jpeg|right|700px]]

== Allgemeine Infos ==

*Ferienwohnung(en):
**Wir kommen wieder unter im [https://www.grandau.at/montafon/zimmer/ferienhaus-enzian Haus Enzian] des [https://www.grandau.at/ Sporthotels Grandau].
**Adresse des Sporthotel: Montafonerstraße 274a, 6791 St. Gallenkirch, Österreich. Unsere Unterkünfte liegen im Türkeiweg.

*Skigebiet: Montafon (Vorarlberg)
**Skigebiet Karte: https://winter.intermaps.com/montafon?lang=de
**Skipass Preise: https://www.silvretta-montafon.at/de/onlineshop/ticket-uebersicht
**Wer nicht alle 7 Tage Skifahren möchte: Es gibt Angebote wie z.B. 5 aus 6, mit einem solchen Skipass kann man innerhalb von 6 Tagen an 5 beliebigen Tagen skifahren.

*Skiverleih: [http://www.sportharry.at/ Sport Harry], direkt an der Talstation.

== Unterkunft ==
=== Aufteilung ===

Dieses Jahr gibt es nur die Hütte mit folgenden Zimmern (wir sind insgesamt 14, also bleiben keine Plätze frei).

{| class="wikitable"
! scope="col" | Zimmer
! scope="col" | Insassen
|-
! scope="row" | 2-er
| Amy, Aafia

|-
! scope="row" | 3-er
| Jakob, Max, Katya
|-
! scope="row" | 4-er
| Eva, Steffen, Flo, Christian
|-
! scope="row" | 5-er
| Basti, Philipp
|}

== Fahrer ==
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.

'''Auf der Suche nach einer Mitfahrgelegenheit: '''

{| class="wikitable"
! scope="col" | Fahrer
! scope="col" | # Plätze
! scope="col" | Anreise
! scope="col" | Mitfahrer Anreise
! scope="col" | Abreise
! scope="col" | Mitfahrer Abreise
! scope="col" | Skimitnahme
! scope="col" | Kommentar
|-
|Eva
|0(3)
|Samstag
|Steffen+Christian
|Samstag?
|Steffen+Christian
|eigene ja
|Auto ist voll
|-
|Max
|0(3)
|Samstag (from Arlberg)
|Jakob+Katya
|Samstag
|Jakob+Katya
|eigene ja
|Auto ist voll
|-
|Basti
|1(2)
|Sunday (early morning)
|Alexey
|Friday (lunch time)
|Alexey
|Ja
|I will be at the airport NUE (alternative meeting point would be Nuremberg trainstation)
|-

|-

|-

|-
|}

== Schwarzes Brett ==

=== Essen ===
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.

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.

'''Essenplan:'''
*Samstag: Spaghetti Bolognese + veg. Bolognese
*Sonntag: Käse Spätzle
*Montag: Burritos
*Dienstag: Risotto
*Mittwoch: Gulasch
*Donnerstag: Kartoffeln mit Kräuter-Quark
*Freitag: Dal mit Reis (od. Curry mit Suesskartoffeln )

Einkaufsliste von 2022 (letztes Jahr): https://docs.google.com/document/d/166b_mIXxmoAgcv1upIGremd_36E1fmwwxsQADP2uEv8/

@Christian: Vegane Option entwender selbst mitbringen oder hier mit reinschreiben (falls man die einfach bekommt)

=== Alkohol/Party ===

=== Spiele ===

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:

''* Spiele hier eintragen''

=== Sonstiges ===

=== Alternativprogramm ===
* Rodeln (http://www.montafon.at/de/urlaubswelten/echte_naturliebhaber/rodeln)
* Schneeschuhwandern (http://www.montafon.at/schneeschuhwanderungen)
* Therme (http://www.montafon.at/schwimmen), z.B. http://www.aqua-dome.at/de (ca. 130km entfernt!)

[[Category:Internal]]