Remeis-Wiki - User contributions [en]

Welcome Newbies

2025-08-27T08:53:40Z

Collischon: /* Important information for PhD */

Welcome to Remeis-Observatory! Here are some relevant infos for everyone joining.

=Presence at the observatory and important meeting dates=
In general, in order to ensure that there are sufficient scientific interactions, all observatory members (BSc, MSc, PhD) are expected to be physically present at the observatory for three days per week. You can ask for permission to work from home during the remaining days. Due to insurance reasons this request needs to be made in writing and formally approved by your supervisor. You are also expected to attend the weekly group meetings in person.

{| class="wikitable"
|-
| Stellar Astronomy || Prof. Ulrich Heber || Monday || 04:00 pm
|-
| Multiwavelength Astronomy || Prof. Manami Sasaki || Friday || 10:00 am
|-
| X-ray Astronomy || Prof. Joern Wilms || Tuesday || 10:00 am
|}

On Tuesdays at 11:30\,am there is also the Astronomy Journal Club, where new papers from astronomy are presented in a friendly environment (https://www.sternwarte.uni-erlangen.de/wiki/index.php/Litclub).
All observatory members are expected to give at least one presentation per year in the club.

In addition there are weekly meetings for different projects, some of them as telephone conferences with other working groups, which are based inside or outside of Germany.

For work in Erlangen, the observatory has a large and very nice office in the ECAP building available. We recommend getting in touch with the other frequent users and joining the ECAP chat (https://chat.ecap.work/, login with your IDM account). It is also possible to join other groups for lunch (Caro can put you in touch with the neutrino people upon request).

All observatory members (BSc, MSc, PhD, ...) are expected to help with the student labs, typically four weeks each in March/early April and in September/October. This implies that you know you experiment and work on it well before the actual lab course. Student members will be remunerated for their help during the lab. You need to talk to your supervisor well in advance should you think about not being available during this time. In general, such requests for leave will only be accepted under extraordinary, job-related circumstances.

=Illness=

If you are ill - even if it is only a cold - talk to your supervisor and work from home. If you are seriously ill for more than two days, go to a Doctor and get a sick leave notice ("Krankschreibung"). Please inform Edith about this such that she can inform the personnel department that they can trigger the download of the sick leave notice. Do not believe your Dr. if they claim that this will happen automatically. We ''need'' to be informed by you!

=Safety=
Contact person: Ingo

The observatory is in general a very safe place to work. Nevertheless there are a few things you need to keep in mind. Once per year we have a safety instruction (attending is mandatory). Upon joining the institute you should watch the video of the last safety instruction at https://www.sternwarte.uni-erlangen.de/internal-area/internal-area-howto/.

=Webpages & email lists=
Contact person: Jakob, Max, Nico

The observatory's webpage is www.sternwarte.uni-erlangen.de, where you can also log in with your user name and password to get access to the internal part of the page and edit your user profile. You will also find useful information in our own Remeis-Wiki. A list of the e-mail lists should help to find the right contact person in case of problems. To be added to e-mail lists, you must contact the e-mail list admin (Max Lorenz).

{| class="wikitable"
|-
| ECAP (+ Observatory) || ecapmail@physik.uni-erlangen.de
|-
| Observatory || all@sternwarte.uni-erlangen.de
|-
| Multiwavelength Group || astro-multi@lists.fau.de
|-
| Stellar Group || stellar@sternwarte.uni-erlangen.de
|-
| X-ray Group || xray@sternwarte.uni-erlangen.de
|-
| Admins || admin@sternwarte.uni-erlangen.de
|-
| Telescope users || astro-observing@lists.fau.de
|-
| Social Media Team || astro-outreach@lists.fau.de
|}

In addition, we also have a Slack channel for quick queries and discussions within the group. You can join the same by asking someone in the group for an invite link.

Our observatory is also active on Social Media and has a Twitter (@DrRemeis) as well as an Instagram Account (@drremeis).

=The Remeis Cluster=
Contact person: admin@sternwarte.uni-erlangen.de

For your work at the observatory, you are provided with a desk and a computer, and access to our cluster for complex calculations. There are a few important things to consider: Data that should not be lost under any circumstances (e.g., scripts, theses) should be saved in your /home directory. Note, however, that the space available there is only a few GB. If you exceed your maximum storage limit, you will receive e-mails from the system. Do not ignore them. /home is backed up daily, and old data are kept for up to one year. Contact the admins if you need access to that. A folder under /userdata/data is also available for storage and meant for reproducible simulations/evaluation/data. There is no backup for /userdata, but failure is unlikely (RAID). While the storage there is very large, please use it sparingly nevertheless. If you want to run one or more time-consuming calculations, please use [[slurm]] (more information in the Remeis wiki). Please be aware that your workstation is part of a computing cluster. Switching off the computer or any other hardware modifications are not permitted. Your computer stays on 24/7, please log out when you leave such that others can use it while you are not there. If you have any problems, please contact the admins.

=Telescopes=
Contact person: Philipp W., Steven, Jakob, Martin

The observatory owns 40cm and 50cm reflector telescopes (in the domes). They are used for observations and experiments in the lab course and also during guided tours. If you are interested in using the telescopes in your free time, e.g., for astro photography, you can receive instructions on how to use them. You should also sign up on the email list for telescope users.

=Important information for PhD=
The information listed below is relevant for all new PhDs:
* The first person to discuss your questions with is your PhD advisor. They should all be aware of the formalities and requirements.
* The legal framework is well described in the Promotionsordnung of FAU and of the NatFak, and there is also a handout on the overall formalities that you will have to be aware of. All of these materials can be found at https://www.nat.fau.de/forschung/forschende/promotion/.
This page also contains a list of Frequently Asked Questions (top right part of the page), including many of the general questions that are asked concerning the formalities of the PhD, especially also in relation to cumulative theses.
* The specific framework within the Department of Physics is described in the Ausfuehrungsbestimmungen of the Department. Your advisors have a copy, and you can also access them directly by joining the studon group "Infos fuer Promovierende", https://www.studon.fau.de/studon/goto.php?target=grp_2684505. The group password is Promotion_Physik . The most important thing here is that these regulations explain the requirements for the (literal or paraphrased) inclusion of text from publication in the thesis manuscript as well as the procedure for preparing cumulative theses (i.e., get in contact with the Department more than a year before the planned submission in order to get an informal approval that your publication plan would result in something that is likely to be considered to be acceptable as a thesis).
* Templates for the top pages of theses according to the corporate design are available at https://www.intern.fau.de/kommunikation-und-marke/vorlagen/abschlussarbeiten/
* If you are close to submitting your thesis: Contrary to statements of the forms available on Docdaten and some rumors among people pursuing a PhD, you can start the procedure to initiate the doctoral procedure approximately four weeks BEFORE submitting the thesis. For this you only need your CV, a copy of your ID (yes, you are permitted by German law to give a copy of your ID to somebody else), the signed application form (available on DocDaten), and a complete and current list of your publications. The advantage of starting this process early is that at the time of submission of your thesis the referees have already been decided, which can save a few weeks of time. There is flexibility in when you submit this, if you think you need four weeks and it really takes five weeks until you can submit the thesis, this will not cause any problems.

DocDaten: https://www.docdaten.fau.de/gs/ - register ASAP. More important information can also be found at: https://www.fau.eu/graduate-centre/doctoral-degrees/ .

* For handing in the thesis at Freyeslebenstrasse 1: go to the entrance on the right as viewed from the road (not the one at the round building), second floor, hallway to the northwest. The office of doctoral affairs is behind the second glass door to the right (also counting the glass door to enter the hallway), room 02.4274

=Commuting from Erlangen=
==Carpool==
Contact person: Max, Nico

We coordinate commuting for the carpool via the app "MyCarpoolApp", which is available on Android and iOS. We use a group account with the name "Remeis Reloaded". The access password is Sternwartstr. 7 . By using "change user" in the menu you can create your user account. The fuel costs are shared equally by everybody in the car. In addition to the fuel costs there is a rate of 2.50€ per car per ride, which is also shared equally by everybody. This is used to reduce the driver's additional costs, like maintenance and such.

==Public transport==
On average there are two trains per hour between Bamberg and Erlangen. If you walk all the way from the Station to the observatory it will take you about 30\,minutes, but there is also a bus connection.
Bus line 901, for example, serves both the train station and the two nearest stops to the observatory (``Schranne'' and ``Schulplatz'').

=Lunch=
The observatory kitchen is equipped with an induction stove, a microwave, and tableware. You can store food in the fridge, but it is important everything has your name on it and that you clean out your old things every now and then.
Put dirty dishes in the dish washer, run it if it is full, and empty it out if you come to the kitchen and the cleaning cycle has finished. Some observatory members walk downtown for their lunch (mostly at about 12:30 pm), while the rest of them meet in the kitchen on the first floor at around noon.

=Coffee=
Contact person: Steven

In the kitchen on the first floor you'll find a Jura E60 coffee maker. If you need coffee, simply add your name to the list above the machine. Our coffee maker only makes coffee or espresso. There is also a separate milk frother in that kitchen. If you notice that we are almost out of coffee or milk, please tell the contact person or (even better) get some yourself and get reimbursed by the contact person. Please note that the coffee machine may only be used for making coffee, please use the kettle for making hot water.

=Remeis community=
Contact person: almost everybody

There is a unique community at the observatory, not only within the individual working groups, but also across the board. Special events are, e.g., the Christmas Party, Skiing in January, Canoeing in the summer and the FRANCI-Meeting with the ECAP and the Astronomy Group from Wuerzburg. Now and then, we organize evenings to watch movies, trips to the cinema, restaurants and bars in Bamberg or Erlangen. That does not happen automatically though and everybody (you too) can get involved. In the summertime there is a pool in the observatory's big garden and we regularly do barbecues. If you like cake you can join our Whatsapp group for cake orders. On their birthday most of the Remeis people bring a cake to share with everybody.

=Sponsoring association and guided tours=
Contact person: Ingo, Nico

The sponsoring association of Dr. Karl Remeis Observatory supports our observatory in preserving its historical collections and public relations. A big part of these public relations are guided tours, which are offered monthly and also on demand. If you are interested in spreading your enthusiasm for Astronomy and Astrophysics, you should a) become a member of the sponsoring association and
b) join our guided tours team! You will get paid by the sponsoring association for giving tours.

[[Category:Internal]][[Category:Current Members]]

Welcome Newbies

2025-08-27T08:39:09Z

Collischon: /* Important information for PhD */

Welcome to Remeis-Observatory! Here are some relevant infos for everyone joining.

=Presence at the observatory and important meeting dates=
In general, in order to ensure that there are sufficient scientific interactions, all observatory members (BSc, MSc, PhD) are expected to be physically present at the observatory for three days per week. You can ask for permission to work from home during the remaining days. Due to insurance reasons this request needs to be made in writing and formally approved by your supervisor. You are also expected to attend the weekly group meetings in person.

{| class="wikitable"
|-
| Stellar Astronomy || Prof. Ulrich Heber || Monday || 04:00 pm
|-
| Multiwavelength Astronomy || Prof. Manami Sasaki || Friday || 10:00 am
|-
| X-ray Astronomy || Prof. Joern Wilms || Tuesday || 10:00 am
|}

On Tuesdays at 11:30\,am there is also the Astronomy Journal Club, where new papers from astronomy are presented in a friendly environment (https://www.sternwarte.uni-erlangen.de/wiki/index.php/Litclub).
All observatory members are expected to give at least one presentation per year in the club.

In addition there are weekly meetings for different projects, some of them as telephone conferences with other working groups, which are based inside or outside of Germany.

For work in Erlangen, the observatory has a large and very nice office in the ECAP building available. We recommend getting in touch with the other frequent users and joining the ECAP chat (https://chat.ecap.work/, login with your IDM account). It is also possible to join other groups for lunch (Caro can put you in touch with the neutrino people upon request).

All observatory members (BSc, MSc, PhD, ...) are expected to help with the student labs, typically four weeks each in March/early April and in September/October. This implies that you know you experiment and work on it well before the actual lab course. Student members will be remunerated for their help during the lab. You need to talk to your supervisor well in advance should you think about not being available during this time. In general, such requests for leave will only be accepted under extraordinary, job-related circumstances.

=Illness=

If you are ill - even if it is only a cold - talk to your supervisor and work from home. If you are seriously ill for more than two days, go to a Doctor and get a sick leave notice ("Krankschreibung"). Please inform Edith about this such that she can inform the personnel department that they can trigger the download of the sick leave notice. Do not believe your Dr. if they claim that this will happen automatically. We ''need'' to be informed by you!

=Safety=
Contact person: Ingo

The observatory is in general a very safe place to work. Nevertheless there are a few things you need to keep in mind. Once per year we have a safety instruction (attending is mandatory). Upon joining the institute you should watch the video of the last safety instruction at https://www.sternwarte.uni-erlangen.de/internal-area/internal-area-howto/.

=Webpages & email lists=
Contact person: Jakob, Max, Nico

The observatory's webpage is www.sternwarte.uni-erlangen.de, where you can also log in with your user name and password to get access to the internal part of the page and edit your user profile. You will also find useful information in our own Remeis-Wiki. A list of the e-mail lists should help to find the right contact person in case of problems. To be added to e-mail lists, you must contact the e-mail list admin (Max Lorenz).

{| class="wikitable"
|-
| ECAP (+ Observatory) || ecapmail@physik.uni-erlangen.de
|-
| Observatory || all@sternwarte.uni-erlangen.de
|-
| Multiwavelength Group || astro-multi@lists.fau.de
|-
| Stellar Group || stellar@sternwarte.uni-erlangen.de
|-
| X-ray Group || xray@sternwarte.uni-erlangen.de
|-
| Admins || admin@sternwarte.uni-erlangen.de
|-
| Telescope users || astro-observing@lists.fau.de
|-
| Social Media Team || astro-outreach@lists.fau.de
|}

In addition, we also have a Slack channel for quick queries and discussions within the group. You can join the same by asking someone in the group for an invite link.

Our observatory is also active on Social Media and has a Twitter (@DrRemeis) as well as an Instagram Account (@drremeis).

=The Remeis Cluster=
Contact person: admin@sternwarte.uni-erlangen.de

For your work at the observatory, you are provided with a desk and a computer, and access to our cluster for complex calculations. There are a few important things to consider: Data that should not be lost under any circumstances (e.g., scripts, theses) should be saved in your /home directory. Note, however, that the space available there is only a few GB. If you exceed your maximum storage limit, you will receive e-mails from the system. Do not ignore them. /home is backed up daily, and old data are kept for up to one year. Contact the admins if you need access to that. A folder under /userdata/data is also available for storage and meant for reproducible simulations/evaluation/data. There is no backup for /userdata, but failure is unlikely (RAID). While the storage there is very large, please use it sparingly nevertheless. If you want to run one or more time-consuming calculations, please use [[slurm]] (more information in the Remeis wiki). Please be aware that your workstation is part of a computing cluster. Switching off the computer or any other hardware modifications are not permitted. Your computer stays on 24/7, please log out when you leave such that others can use it while you are not there. If you have any problems, please contact the admins.

=Telescopes=
Contact person: Philipp W., Steven, Jakob, Martin

The observatory owns 40cm and 50cm reflector telescopes (in the domes). They are used for observations and experiments in the lab course and also during guided tours. If you are interested in using the telescopes in your free time, e.g., for astro photography, you can receive instructions on how to use them. You should also sign up on the email list for telescope users.

=Important information for PhD=
The information listed below is relevant for all new PhDs:
* The first person to discuss your questions with is your PhD advisor. They should all be aware of the formalities and requirements.
* The legal framework is well described in the Promotionsordnung of FAU and of the NatFak, and there is also a handout on the overall formalities that you will have to be aware of. All of these materials can be found at https://www.nat.fau.de/forschung/forschende/promotion/.
This page also contains a list of Frequently Asked Questions (top right part of the page), including many of the general questions that are asked concerning the formalities of the PhD, especially also in relation to cumulative theses.
* The specific framework within the Department of Physics is described in the Ausfuehrungsbestimmungen of the Department. Your advisors have a copy, and you can also access them directly by joining the studon group "Infos fuer Promovierende", https://www.studon.fau.de/studon/goto.php?target=grp_2684505. The group password is Promotion_Physik . The most important thing here is that these regulations explain the requirements for the (literal or paraphrased) inclusion of text from publication in the thesis manuscript as well as the procedure for preparing cumulative theses (i.e., get in contact with the Department more than a year before the planned submission in order to get an informal approval that your publication plan would result in something that is likely to be considered to be acceptable as a thesis).
* Templates for the top pages of theses according to the corporate design are available at https://www.intern.fau.de/kommunikation-und-marke/vorlagen/abschlussarbeiten/
* If you are close to submitting your thesis: Contrary to statements of the forms available on Docdaten and some rumors among people pursuing a PhD, you can start the procedure to initiate the doctoral procedure approximately four weeks BEFORE submitting the thesis. For this you only need your CV, a copy of your ID (yes, you are permitted by German law to give a copy of your ID to somebody else), the signed application form (available on DocDaten), and a complete and current list of your publications. The advantage of starting this process early is that at the time of submission of your thesis the referees have already been decided, which can save a few weeks of time. There is flexibility in when you submit this, if you think you need four weeks and it really takes five weeks until you can submit the thesis, this will not cause any problems.

DocDaten: https://www.docdaten.fau.de/gs/ - register ASAP. More important information can also be found at: https://www.fau.eu/graduate-centre/doctoral-degrees/ .

* For handing in the thesis at Freyeslebenstrasse 2: go to the entrance on the right as viewed from the road (not the one at the round building), second floor, hallway to the northwest. The office of doctoral affairs is behind the second glass door to the right (also counting the glass door to enter the hallway), room 02.4274

=Commuting from Erlangen=
==Carpool==
Contact person: Max, Nico

We coordinate commuting for the carpool via the app "MyCarpoolApp", which is available on Android and iOS. We use a group account with the name "Remeis Reloaded". The access password is Sternwartstr. 7 . By using "change user" in the menu you can create your user account. The fuel costs are shared equally by everybody in the car. In addition to the fuel costs there is a rate of 2.50€ per car per ride, which is also shared equally by everybody. This is used to reduce the driver's additional costs, like maintenance and such.

==Public transport==
On average there are two trains per hour between Bamberg and Erlangen. If you walk all the way from the Station to the observatory it will take you about 30\,minutes, but there is also a bus connection.
Bus line 901, for example, serves both the train station and the two nearest stops to the observatory (``Schranne'' and ``Schulplatz'').

=Lunch=
The observatory kitchen is equipped with an induction stove, a microwave, and tableware. You can store food in the fridge, but it is important everything has your name on it and that you clean out your old things every now and then.
Put dirty dishes in the dish washer, run it if it is full, and empty it out if you come to the kitchen and the cleaning cycle has finished. Some observatory members walk downtown for their lunch (mostly at about 12:30 pm), while the rest of them meet in the kitchen on the first floor at around noon.

=Coffee=
Contact person: Steven

In the kitchen on the first floor you'll find a Jura E60 coffee maker. If you need coffee, simply add your name to the list above the machine. Our coffee maker only makes coffee or espresso. There is also a separate milk frother in that kitchen. If you notice that we are almost out of coffee or milk, please tell the contact person or (even better) get some yourself and get reimbursed by the contact person. Please note that the coffee machine may only be used for making coffee, please use the kettle for making hot water.

=Remeis community=
Contact person: almost everybody

There is a unique community at the observatory, not only within the individual working groups, but also across the board. Special events are, e.g., the Christmas Party, Skiing in January, Canoeing in the summer and the FRANCI-Meeting with the ECAP and the Astronomy Group from Wuerzburg. Now and then, we organize evenings to watch movies, trips to the cinema, restaurants and bars in Bamberg or Erlangen. That does not happen automatically though and everybody (you too) can get involved. In the summertime there is a pool in the observatory's big garden and we regularly do barbecues. If you like cake you can join our Whatsapp group for cake orders. On their birthday most of the Remeis people bring a cake to share with everybody.

=Sponsoring association and guided tours=
Contact person: Ingo, Nico

The sponsoring association of Dr. Karl Remeis Observatory supports our observatory in preserving its historical collections and public relations. A big part of these public relations are guided tours, which are offered monthly and also on demand. If you are interested in spreading your enthusiasm for Astronomy and Astrophysics, you should a) become a member of the sponsoring association and
b) join our guided tours team! You will get paid by the sponsoring association for giving tours.

[[Category:Internal]][[Category:Current Members]]

Slurm

2025-08-26T09:40:46Z

Collischon: /* About */

[[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: 7 days
* erosita: only available for selected people involved in the project, timelimit: 7 days
* dlr: only available for selected people involved in the project, timelimit: 7 days
* gpu: available to anyone to run jobs on a GPU, can also be used for CPU jobs if remeis is full and there is no GPU job (--partition=remeis,gpu), timelimit: 24 hours
* 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=1
#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 submitting 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.

Slurm

2025-08-26T09:40:15Z

Collischon: /* About */

[[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: 7 days
* erosita: only available for selected people involved in the project, timelimit: 7 days
* dlr: only available for selected people involved in the project, timelimit: 7 days
* gpu: available to anyone to run jobs on a GPU, can also be used for CPU jobs if remeis is full and there is no GPU job, timelimit: 24 hours
* 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=1
#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 submitting 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.

Welcome Newbies

2025-08-26T09:37:38Z

Collischon: /* The Remeis Cluster */

Welcome to Remeis-Observatory! Here are some relevant infos for everyone joining.

=Presence at the observatory and important meeting dates=
In general, in order to ensure that there are sufficient scientific interactions, all observatory members (BSc, MSc, PhD) are expected to be physically present at the observatory for three days per week. You can ask for permission to work from home during the remaining days. Due to insurance reasons this request needs to be made in writing and formally approved by your supervisor. You are also expected to attend the weekly group meetings in person.

{| class="wikitable"
|-
| Stellar Astronomy || Prof. Ulrich Heber || Monday || 04:00 pm
|-
| Multiwavelength Astronomy || Prof. Manami Sasaki || Friday || 10:00 am
|-
| X-ray Astronomy || Prof. Joern Wilms || Tuesday || 10:00 am
|}

On Tuesdays at 11:30\,am there is also the Astronomy Journal Club, where new papers from astronomy are presented in a friendly environment (https://www.sternwarte.uni-erlangen.de/wiki/index.php/Litclub).
All observatory members are expected to give at least one presentation per year in the club.

In addition there are weekly meetings for different projects, some of them as telephone conferences with other working groups, which are based inside or outside of Germany.

For work in Erlangen, the observatory has a large and very nice office in the ECAP building available. We recommend getting in touch with the other frequent users and joining the ECAP chat (https://chat.ecap.work/, login with your IDM account). It is also possible to join other groups for lunch (Caro can put you in touch with the neutrino people upon request).

All observatory members (BSc, MSc, PhD, ...) are expected to help with the student labs, typically four weeks each in March/early April and in September/October. This implies that you know you experiment and work on it well before the actual lab course. Student members will be remunerated for their help during the lab. You need to talk to your supervisor well in advance should you think about not being available during this time. In general, such requests for leave will only be accepted under extraordinary, job-related circumstances.

=Illness=

If you are ill - even if it is only a cold - talk to your supervisor and work from home. If you are seriously ill for more than two days, go to a Doctor and get a sick leave notice ("Krankschreibung"). Please inform Edith about this such that she can inform the personnel department that they can trigger the download of the sick leave notice. Do not believe your Dr. if they claim that this will happen automatically. We ''need'' to be informed by you!

=Safety=
Contact person: Ingo

The observatory is in general a very safe place to work. Nevertheless there are a few things you need to keep in mind. Once per year we have a safety instruction (attending is mandatory). Upon joining the institute you should watch the video of the last safety instruction at https://www.sternwarte.uni-erlangen.de/internal-area/internal-area-howto/.

=Webpages & email lists=
Contact person: Jakob, Max, Nico

The observatory's webpage is www.sternwarte.uni-erlangen.de, where you can also log in with your user name and password to get access to the internal part of the page and edit your user profile. You will also find useful information in our own Remeis-Wiki. A list of the e-mail lists should help to find the right contact person in case of problems. To be added to e-mail lists, you must contact the e-mail list admin (Max Lorenz).

{| class="wikitable"
|-
| ECAP (+ Observatory) || ecapmail@physik.uni-erlangen.de
|-
| Observatory || all@sternwarte.uni-erlangen.de
|-
| Multiwavelength Group || astro-multi@lists.fau.de
|-
| Stellar Group || stellar@sternwarte.uni-erlangen.de
|-
| X-ray Group || xray@sternwarte.uni-erlangen.de
|-
| Admins || admin@sternwarte.uni-erlangen.de
|-
| Telescope users || astro-observing@lists.fau.de
|-
| Social Media Team || astro-outreach@lists.fau.de
|}

In addition, we also have a Slack channel for quick queries and discussions within the group. You can join the same by asking someone in the group for an invite link.

Our observatory is also active on Social Media and has a Twitter (@DrRemeis) as well as an Instagram Account (@drremeis).

=The Remeis Cluster=
Contact person: admin@sternwarte.uni-erlangen.de

For your work at the observatory, you are provided with a desk and a computer, and access to our cluster for complex calculations. There are a few important things to consider: Data that should not be lost under any circumstances (e.g., scripts, theses) should be saved in your /home directory. Note, however, that the space available there is only a few GB. If you exceed your maximum storage limit, you will receive e-mails from the system. Do not ignore them. /home is backed up daily, and old data are kept for up to one year. Contact the admins if you need access to that. A folder under /userdata/data is also available for storage and meant for reproducible simulations/evaluation/data. There is no backup for /userdata, but failure is unlikely (RAID). While the storage there is very large, please use it sparingly nevertheless. If you want to run one or more time-consuming calculations, please use [[slurm]] (more information in the Remeis wiki). Please be aware that your workstation is part of a computing cluster. Switching off the computer or any other hardware modifications are not permitted. Your computer stays on 24/7, please log out when you leave such that others can use it while you are not there. If you have any problems, please contact the admins.

=Telescopes=
Contact person: Philipp W., Steven, Jakob, Martin

The observatory owns 40cm and 50cm reflector telescopes (in the domes). They are used for observations and experiments in the lab course and also during guided tours. If you are interested in using the telescopes in your free time, e.g., for astro photography, you can receive instructions on how to use them. You should also sign up on the email list for telescope users.

=Important information for PhD=
The information listed below is relevant for all new PhDs:
* The first person to discuss your questions with is your PhD advisor. They should all be aware of the formalities and requirements.
* The legal framework is well described in the Promotionsordnung of FAU and of the NatFak, and there is also a handout on the overall formalities that you will have to be aware of. All of these materials can be found at https://www.nat.fau.de/forschung/forschende/promotion/.
This page also contains a list of Frequently Asked Questions (top right part of the page), including many of the general questions that are asked concerning the formalities of the PhD, especially also in relation to cumulative theses.
* The specific framework within the Department of Physics is described in the Ausfuehrungsbestimmungen of the Department. Your advisors have a copy, and you can also access them directly by joining the studon group "Infos fuer Promovierende", https://www.studon.fau.de/studon/goto.php?target=grp_2684505. The group password is Promotion_Physik . The most important thing here is that these regulations explain the requirements for the (literal or paraphrased) inclusion of text from publication in the thesis manuscript as well as the procedure for preparing cumulative theses (i.e., get in contact with the Department more than a year before the planned submission in order to get an informal approval that your publication plan would result in something that is likely to be considered to be acceptable as a thesis).
* Templates for the top pages of theses according to the corporate design are available at https://www.intern.fau.de/kommunikation-und-marke/vorlagen/abschlussarbeiten/
* If you are close to submitting your thesis: Contrary to statements of the forms available on Docdaten and some rumors among people pursuing a PhD, you can start the procedure to initiate the doctoral procedure approximately four weeks BEFORE submitting the thesis. For this you only need your CV, a copy of your ID (yes, you are permitted by German law to give a copy of your ID to somebody else), the signed application form (available on DocDaten), and a complete and current list of your publications. The advantage of starting this process early is that at the time of submission of your thesis the referees have already been decided, which can save a few weeks of time. There is flexibility in when you submit this, if you think you need four weeks and it really takes five weeks until you can submit the thesis, this will not cause any problems.

DocDaten: https://www.docdaten.fau.de/gs/ - register ASAP. More important information can also be found at: https://www.fau.eu/graduate-centre/doctoral-degrees/ .

=Commuting from Erlangen=
==Carpool==
Contact person: Max, Nico

We coordinate commuting for the carpool via the app "MyCarpoolApp", which is available on Android and iOS. We use a group account with the name "Remeis Reloaded". The access password is Sternwartstr. 7 . By using "change user" in the menu you can create your user account. The fuel costs are shared equally by everybody in the car. In addition to the fuel costs there is a rate of 2.50€ per car per ride, which is also shared equally by everybody. This is used to reduce the driver's additional costs, like maintenance and such.

==Public transport==
On average there are two trains per hour between Bamberg and Erlangen. If you walk all the way from the Station to the observatory it will take you about 30\,minutes, but there is also a bus connection.
Bus line 901, for example, serves both the train station and the two nearest stops to the observatory (``Schranne'' and ``Schulplatz'').

=Lunch=
The observatory kitchen is equipped with an induction stove, a microwave, and tableware. You can store food in the fridge, but it is important everything has your name on it and that you clean out your old things every now and then.
Put dirty dishes in the dish washer, run it if it is full, and empty it out if you come to the kitchen and the cleaning cycle has finished. Some observatory members walk downtown for their lunch (mostly at about 12:30 pm), while the rest of them meet in the kitchen on the first floor at around noon.

=Coffee=
Contact person: Steven

In the kitchen on the first floor you'll find a Jura E60 coffee maker. If you need coffee, simply add your name to the list above the machine. Our coffee maker only makes coffee or espresso. There is also a separate milk frother in that kitchen. If you notice that we are almost out of coffee or milk, please tell the contact person or (even better) get some yourself and get reimbursed by the contact person. Please note that the coffee machine may only be used for making coffee, please use the kettle for making hot water.

=Remeis community=
Contact person: almost everybody

There is a unique community at the observatory, not only within the individual working groups, but also across the board. Special events are, e.g., the Christmas Party, Skiing in January, Canoeing in the summer and the FRANCI-Meeting with the ECAP and the Astronomy Group from Wuerzburg. Now and then, we organize evenings to watch movies, trips to the cinema, restaurants and bars in Bamberg or Erlangen. That does not happen automatically though and everybody (you too) can get involved. In the summertime there is a pool in the observatory's big garden and we regularly do barbecues. If you like cake you can join our Whatsapp group for cake orders. On their birthday most of the Remeis people bring a cake to share with everybody.

=Sponsoring association and guided tours=
Contact person: Ingo, Nico

The sponsoring association of Dr. Karl Remeis Observatory supports our observatory in preserving its historical collections and public relations. A big part of these public relations are guided tours, which are offered monthly and also on demand. If you are interested in spreading your enthusiasm for Astronomy and Astrophysics, you should a) become a member of the sponsoring association and
b) join our guided tours team! You will get paid by the sponsoring association for giving tours.

[[Category:Internal]][[Category:Current Members]]

Welcome Newbies

2025-08-26T09:33:22Z

Collischon: /* Sponsoring association and guided tours */

Welcome to Remeis-Observatory! Here are some relevant infos for everyone joining.

=Presence at the observatory and important meeting dates=
In general, in order to ensure that there are sufficient scientific interactions, all observatory members (BSc, MSc, PhD) are expected to be physically present at the observatory for three days per week. You can ask for permission to work from home during the remaining days. Due to insurance reasons this request needs to be made in writing and formally approved by your supervisor. You are also expected to attend the weekly group meetings in person.

{| class="wikitable"
|-
| Stellar Astronomy || Prof. Ulrich Heber || Monday || 04:00 pm
|-
| Multiwavelength Astronomy || Prof. Manami Sasaki || Friday || 10:00 am
|-
| X-ray Astronomy || Prof. Joern Wilms || Tuesday || 10:00 am
|}

On Tuesdays at 11:30\,am there is also the Astronomy Journal Club, where new papers from astronomy are presented in a friendly environment (https://www.sternwarte.uni-erlangen.de/wiki/index.php/Litclub).
All observatory members are expected to give at least one presentation per year in the club.

In addition there are weekly meetings for different projects, some of them as telephone conferences with other working groups, which are based inside or outside of Germany.

For work in Erlangen, the observatory has a large and very nice office in the ECAP building available. We recommend getting in touch with the other frequent users and joining the ECAP chat (https://chat.ecap.work/, login with your IDM account). It is also possible to join other groups for lunch (Caro can put you in touch with the neutrino people upon request).

All observatory members (BSc, MSc, PhD, ...) are expected to help with the student labs, typically four weeks each in March/early April and in September/October. This implies that you know you experiment and work on it well before the actual lab course. Student members will be remunerated for their help during the lab. You need to talk to your supervisor well in advance should you think about not being available during this time. In general, such requests for leave will only be accepted under extraordinary, job-related circumstances.

=Illness=

If you are ill - even if it is only a cold - talk to your supervisor and work from home. If you are seriously ill for more than two days, go to a Doctor and get a sick leave notice ("Krankschreibung"). Please inform Edith about this such that she can inform the personnel department that they can trigger the download of the sick leave notice. Do not believe your Dr. if they claim that this will happen automatically. We ''need'' to be informed by you!

=Safety=
Contact person: Ingo

The observatory is in general a very safe place to work. Nevertheless there are a few things you need to keep in mind. Once per year we have a safety instruction (attending is mandatory). Upon joining the institute you should watch the video of the last safety instruction at https://www.sternwarte.uni-erlangen.de/internal-area/internal-area-howto/.

=Webpages & email lists=
Contact person: Jakob, Max, Nico

The observatory's webpage is www.sternwarte.uni-erlangen.de, where you can also log in with your user name and password to get access to the internal part of the page and edit your user profile. You will also find useful information in our own Remeis-Wiki. A list of the e-mail lists should help to find the right contact person in case of problems. To be added to e-mail lists, you must contact the e-mail list admin (Max Lorenz).

{| class="wikitable"
|-
| ECAP (+ Observatory) || ecapmail@physik.uni-erlangen.de
|-
| Observatory || all@sternwarte.uni-erlangen.de
|-
| Multiwavelength Group || astro-multi@lists.fau.de
|-
| Stellar Group || stellar@sternwarte.uni-erlangen.de
|-
| X-ray Group || xray@sternwarte.uni-erlangen.de
|-
| Admins || admin@sternwarte.uni-erlangen.de
|-
| Telescope users || astro-observing@lists.fau.de
|-
| Social Media Team || astro-outreach@lists.fau.de
|}

In addition, we also have a Slack channel for quick queries and discussions within the group. You can join the same by asking someone in the group for an invite link.

Our observatory is also active on Social Media and has a Twitter (@DrRemeis) as well as an Instagram Account (@drremeis).

=The Remeis Cluster=
Contact person: admin@sternwarte.uni-erlangen.de

For your work at the observatory, you are provided with a desk and a computer, and access to our cluster for complex calculations. There are a few important things to consider: Data that should not be lost under any circumstances (e.g., scripts, theses) should be saved in your /home directory. Note, however, that the space available there is only a few GB. If you exceed your maximum storage limit, you will receive e-mails from the system. Do not ignore them. /home is backed up daily, and old data are kept for up to one year. Contact the admins if you need access to that. A folder under /userdata/data is also available for storage and meant for reproducible simulations/evaluation/data. There is no backup for /userdata, but failure is unlikely (RAID). While the storage there is very large, please use it sparingly nevertheless. If you want to run one or more time-consuming calculations, please use SLURM (more information in the Remeis wiki). Please be aware that your workstation is part of a computing cluster. Switching off the computer or any other hardware modifications are not permitted. Your computer stays on 24/7, please log out when you leave such that others can use it while you are not there. If you have any problems, please contact the admins.

=Telescopes=
Contact person: Philipp W., Steven, Jakob, Martin

The observatory owns 40cm and 50cm reflector telescopes (in the domes). They are used for observations and experiments in the lab course and also during guided tours. If you are interested in using the telescopes in your free time, e.g., for astro photography, you can receive instructions on how to use them. You should also sign up on the email list for telescope users.

=Important information for PhD=
The information listed below is relevant for all new PhDs:
* The first person to discuss your questions with is your PhD advisor. They should all be aware of the formalities and requirements.
* The legal framework is well described in the Promotionsordnung of FAU and of the NatFak, and there is also a handout on the overall formalities that you will have to be aware of. All of these materials can be found at https://www.nat.fau.de/forschung/forschende/promotion/.
This page also contains a list of Frequently Asked Questions (top right part of the page), including many of the general questions that are asked concerning the formalities of the PhD, especially also in relation to cumulative theses.
* The specific framework within the Department of Physics is described in the Ausfuehrungsbestimmungen of the Department. Your advisors have a copy, and you can also access them directly by joining the studon group "Infos fuer Promovierende", https://www.studon.fau.de/studon/goto.php?target=grp_2684505. The group password is Promotion_Physik . The most important thing here is that these regulations explain the requirements for the (literal or paraphrased) inclusion of text from publication in the thesis manuscript as well as the procedure for preparing cumulative theses (i.e., get in contact with the Department more than a year before the planned submission in order to get an informal approval that your publication plan would result in something that is likely to be considered to be acceptable as a thesis).
* Templates for the top pages of theses according to the corporate design are available at https://www.intern.fau.de/kommunikation-und-marke/vorlagen/abschlussarbeiten/
* If you are close to submitting your thesis: Contrary to statements of the forms available on Docdaten and some rumors among people pursuing a PhD, you can start the procedure to initiate the doctoral procedure approximately four weeks BEFORE submitting the thesis. For this you only need your CV, a copy of your ID (yes, you are permitted by German law to give a copy of your ID to somebody else), the signed application form (available on DocDaten), and a complete and current list of your publications. The advantage of starting this process early is that at the time of submission of your thesis the referees have already been decided, which can save a few weeks of time. There is flexibility in when you submit this, if you think you need four weeks and it really takes five weeks until you can submit the thesis, this will not cause any problems.

DocDaten: https://www.docdaten.fau.de/gs/ - register ASAP. More important information can also be found at: https://www.fau.eu/graduate-centre/doctoral-degrees/ .

=Commuting from Erlangen=
==Carpool==
Contact person: Max, Nico

We coordinate commuting for the carpool via the app "MyCarpoolApp", which is available on Android and iOS. We use a group account with the name "Remeis Reloaded". The access password is Sternwartstr. 7 . By using "change user" in the menu you can create your user account. The fuel costs are shared equally by everybody in the car. In addition to the fuel costs there is a rate of 2.50€ per car per ride, which is also shared equally by everybody. This is used to reduce the driver's additional costs, like maintenance and such.

==Public transport==
On average there are two trains per hour between Bamberg and Erlangen. If you walk all the way from the Station to the observatory it will take you about 30\,minutes, but there is also a bus connection.
Bus line 901, for example, serves both the train station and the two nearest stops to the observatory (``Schranne'' and ``Schulplatz'').

=Lunch=
The observatory kitchen is equipped with an induction stove, a microwave, and tableware. You can store food in the fridge, but it is important everything has your name on it and that you clean out your old things every now and then.
Put dirty dishes in the dish washer, run it if it is full, and empty it out if you come to the kitchen and the cleaning cycle has finished. Some observatory members walk downtown for their lunch (mostly at about 12:30 pm), while the rest of them meet in the kitchen on the first floor at around noon.

=Coffee=
Contact person: Steven

In the kitchen on the first floor you'll find a Jura E60 coffee maker. If you need coffee, simply add your name to the list above the machine. Our coffee maker only makes coffee or espresso. There is also a separate milk frother in that kitchen. If you notice that we are almost out of coffee or milk, please tell the contact person or (even better) get some yourself and get reimbursed by the contact person. Please note that the coffee machine may only be used for making coffee, please use the kettle for making hot water.

=Remeis community=
Contact person: almost everybody

There is a unique community at the observatory, not only within the individual working groups, but also across the board. Special events are, e.g., the Christmas Party, Skiing in January, Canoeing in the summer and the FRANCI-Meeting with the ECAP and the Astronomy Group from Wuerzburg. Now and then, we organize evenings to watch movies, trips to the cinema, restaurants and bars in Bamberg or Erlangen. That does not happen automatically though and everybody (you too) can get involved. In the summertime there is a pool in the observatory's big garden and we regularly do barbecues. If you like cake you can join our Whatsapp group for cake orders. On their birthday most of the Remeis people bring a cake to share with everybody.

=Sponsoring association and guided tours=
Contact person: Ingo, Nico

The sponsoring association of Dr. Karl Remeis Observatory supports our observatory in preserving its historical collections and public relations. A big part of these public relations are guided tours, which are offered monthly and also on demand. If you are interested in spreading your enthusiasm for Astronomy and Astrophysics, you should a) become a member of the sponsoring association and
b) join our guided tours team! You will get paid by the sponsoring association for giving tours.

[[Category:Internal]][[Category:Current Members]]

Welcome Newbies

2025-08-26T08:51:15Z

Collischon: /* Important information for PhD */

Welcome to Remeis-Observatory! Here are some relevant infos for everyone joining.

=Presence at the observatory and important meeting dates=
In general, in order to ensure that there are sufficient scientific interactions, all observatory members (BSc, MSc, PhD) are expected to be physically present at the observatory for three days per week. You can ask for permission to work from home during the remaining days. Due to insurance reasons this request needs to be made in writing and formally approved by your supervisor. You are also expected to attend the weekly group meetings in person.

{| class="wikitable"
|-
| Stellar Astronomy || Prof. Ulrich Heber || Monday || 04:00 pm
|-
| Multiwavelength Astronomy || Prof. Manami Sasaki || Friday || 10:00 am
|-
| X-ray Astronomy || Prof. Joern Wilms || Tuesday || 10:00 am
|}

On Tuesdays at 11:30\,am there is also the Astronomy Journal Club, where new papers from astronomy are presented in a friendly environment (https://www.sternwarte.uni-erlangen.de/wiki/index.php/Litclub).
All observatory members are expected to give at least one presentation per year in the club.

In addition there are weekly meetings for different projects, some of them as telephone conferences with other working groups, which are based inside or outside of Germany.

For work in Erlangen, the observatory has a large and very nice office in the ECAP building available. We recommend getting in touch with the other frequent users and joining the ECAP chat (https://chat.ecap.work/, login with your IDM account). It is also possible to join other groups for lunch (Caro can put you in touch with the neutrino people upon request).

All observatory members (BSc, MSc, PhD, ...) are expected to help with the student labs, typically four weeks each in March/early April and in September/October. This implies that you know you experiment and work on it well before the actual lab course. Student members will be remunerated for their help during the lab. You need to talk to your supervisor well in advance should you think about not being available during this time. In general, such requests for leave will only be accepted under extraordinary, job-related circumstances.

=Illness=

If you are ill - even if it is only a cold - talk to your supervisor and work from home. If you are seriously ill for more than two days, go to a Doctor and get a sick leave notice ("Krankschreibung"). Please inform Edith about this such that she can inform the personnel department that they can trigger the download of the sick leave notice. Do not believe your Dr. if they claim that this will happen automatically. We ''need'' to be informed by you!

=Safety=
Contact person: Ingo

The observatory is in general a very safe place to work. Nevertheless there are a few things you need to keep in mind. Once per year we have a safety instruction (attending is mandatory). Upon joining the institute you should watch the video of the last safety instruction at https://www.sternwarte.uni-erlangen.de/internal-area/internal-area-howto/.

=Webpages & email lists=
Contact person: Jakob, Max, Nico

The observatory's webpage is www.sternwarte.uni-erlangen.de, where you can also log in with your user name and password to get access to the internal part of the page and edit your user profile. You will also find useful information in our own Remeis-Wiki. A list of the e-mail lists should help to find the right contact person in case of problems. To be added to e-mail lists, you must contact the e-mail list admin (Max Lorenz).

{| class="wikitable"
|-
| ECAP (+ Observatory) || ecapmail@physik.uni-erlangen.de
|-
| Observatory || all@sternwarte.uni-erlangen.de
|-
| Multiwavelength Group || astro-multi@lists.fau.de
|-
| Stellar Group || stellar@sternwarte.uni-erlangen.de
|-
| X-ray Group || xray@sternwarte.uni-erlangen.de
|-
| Admins || admin@sternwarte.uni-erlangen.de
|-
| Telescope users || astro-observing@lists.fau.de
|-
| Social Media Team || astro-outreach@lists.fau.de
|}

In addition, we also have a Slack channel for quick queries and discussions within the group. You can join the same by asking someone in the group for an invite link.

Our observatory is also active on Social Media and has a Twitter (@DrRemeis) as well as an Instagram Account (@drremeis).

=The Remeis Cluster=
Contact person: admin@sternwarte.uni-erlangen.de

For your work at the observatory, you are provided with a desk and a computer, and access to our cluster for complex calculations. There are a few important things to consider: Data that should not be lost under any circumstances (e.g., scripts, theses) should be saved in your /home directory. Note, however, that the space available there is only a few GB. If you exceed your maximum storage limit, you will receive e-mails from the system. Do not ignore them. /home is backed up daily, and old data are kept for up to one year. Contact the admins if you need access to that. A folder under /userdata/data is also available for storage and meant for reproducible simulations/evaluation/data. There is no backup for /userdata, but failure is unlikely (RAID). While the storage there is very large, please use it sparingly nevertheless. If you want to run one or more time-consuming calculations, please use SLURM (more information in the Remeis wiki). Please be aware that your workstation is part of a computing cluster. Switching off the computer or any other hardware modifications are not permitted. Your computer stays on 24/7, please log out when you leave such that others can use it while you are not there. If you have any problems, please contact the admins.

=Telescopes=
Contact person: Philipp W., Steven, Jakob, Martin

The observatory owns 40cm and 50cm reflector telescopes (in the domes). They are used for observations and experiments in the lab course and also during guided tours. If you are interested in using the telescopes in your free time, e.g., for astro photography, you can receive instructions on how to use them. You should also sign up on the email list for telescope users.

=Important information for PhD=
The information listed below is relevant for all new PhDs:
* The first person to discuss your questions with is your PhD advisor. They should all be aware of the formalities and requirements.
* The legal framework is well described in the Promotionsordnung of FAU and of the NatFak, and there is also a handout on the overall formalities that you will have to be aware of. All of these materials can be found at https://www.nat.fau.de/forschung/forschende/promotion/.
This page also contains a list of Frequently Asked Questions (top right part of the page), including many of the general questions that are asked concerning the formalities of the PhD, especially also in relation to cumulative theses.
* The specific framework within the Department of Physics is described in the Ausfuehrungsbestimmungen of the Department. Your advisors have a copy, and you can also access them directly by joining the studon group "Infos fuer Promovierende", https://www.studon.fau.de/studon/goto.php?target=grp_2684505. The group password is Promotion_Physik . The most important thing here is that these regulations explain the requirements for the (literal or paraphrased) inclusion of text from publication in the thesis manuscript as well as the procedure for preparing cumulative theses (i.e., get in contact with the Department more than a year before the planned submission in order to get an informal approval that your publication plan would result in something that is likely to be considered to be acceptable as a thesis).
* Templates for the top pages of theses according to the corporate design are available at https://www.intern.fau.de/kommunikation-und-marke/vorlagen/abschlussarbeiten/
* If you are close to submitting your thesis: Contrary to statements of the forms available on Docdaten and some rumors among people pursuing a PhD, you can start the procedure to initiate the doctoral procedure approximately four weeks BEFORE submitting the thesis. For this you only need your CV, a copy of your ID (yes, you are permitted by German law to give a copy of your ID to somebody else), the signed application form (available on DocDaten), and a complete and current list of your publications. The advantage of starting this process early is that at the time of submission of your thesis the referees have already been decided, which can save a few weeks of time. There is flexibility in when you submit this, if you think you need four weeks and it really takes five weeks until you can submit the thesis, this will not cause any problems.

DocDaten: https://www.docdaten.fau.de/gs/ - register ASAP. More important information can also be found at: https://www.fau.eu/graduate-centre/doctoral-degrees/ .

=Commuting from Erlangen=
==Carpool==
Contact person: Max, Nico

We coordinate commuting for the carpool via the app "MyCarpoolApp", which is available on Android and iOS. We use a group account with the name "Remeis Reloaded". The access password is Sternwartstr. 7 . By using "change user" in the menu you can create your user account. The fuel costs are shared equally by everybody in the car. In addition to the fuel costs there is a rate of 2.50€ per car per ride, which is also shared equally by everybody. This is used to reduce the driver's additional costs, like maintenance and such.

==Public transport==
On average there are two trains per hour between Bamberg and Erlangen. If you walk all the way from the Station to the observatory it will take you about 30\,minutes, but there is also a bus connection.
Bus line 901, for example, serves both the train station and the two nearest stops to the observatory (``Schranne'' and ``Schulplatz'').

=Lunch=
The observatory kitchen is equipped with an induction stove, a microwave, and tableware. You can store food in the fridge, but it is important everything has your name on it and that you clean out your old things every now and then.
Put dirty dishes in the dish washer, run it if it is full, and empty it out if you come to the kitchen and the cleaning cycle has finished. Some observatory members walk downtown for their lunch (mostly at about 12:30 pm), while the rest of them meet in the kitchen on the first floor at around noon.

=Coffee=
Contact person: Steven

In the kitchen on the first floor you'll find a Jura E60 coffee maker. If you need coffee, simply add your name to the list above the machine. Our coffee maker only makes coffee or espresso. There is also a separate milk frother in that kitchen. If you notice that we are almost out of coffee or milk, please tell the contact person or (even better) get some yourself and get reimbursed by the contact person. Please note that the coffee machine may only be used for making coffee, please use the kettle for making hot water.

=Remeis community=
Contact person: almost everybody

There is a unique community at the observatory, not only within the individual working groups, but also across the board. Special events are, e.g., the Christmas Party, Skiing in January, Canoeing in the summer and the FRANCI-Meeting with the ECAP and the Astronomy Group from Wuerzburg. Now and then, we organize evenings to watch movies, trips to the cinema, restaurants and bars in Bamberg or Erlangen. That does not happen automatically though and everybody (you too) can get involved. In the summertime there is a pool in the observatory's big garden and we regularly do barbecues. If you like cake you can join our Whatsapp group for cake orders. On their birthday most of the Remeis people bring a cake to share with everybody.

=Sponsoring association and guided tours=
Contact person: Ingo, Nico
The sponsoring association of Dr. Karl Remeis Observatory supports our observatory in preserving its historical collections and public relations. A big part of these public relations are guided tours, which are offered monthly and also on demand. If you are interested in spreading your enthusiasm for Astronomy and Astrophysics, you should a) become a member of the sponsoring association and
b) join our guided tours team! You will get paid by the sponsoring association for giving tours.

[[Category:Internal]][[Category:Current Members]]

Welcome Newbies

2025-08-26T07:30:20Z

Collischon:

Welcome to Remeis-Observatory! Here are some relevant infos for everyone joining.

=Presence at the observatory and important meeting dates=
In general, in order to ensure that there are sufficient scientific interactions, all observatory members (BSc, MSc, PhD) are expected to be physically present at the observatory for three days per week. You can ask for permission to work from home during the remaining days. Due to insurance reasons this request needs to be made in writing and formally approved by your supervisor. You are also expected to attend the weekly group meetings in person.

{| class="wikitable"
|-
| Stellar Astronomy || Prof. Ulrich Heber || Monday || 04:00 pm
|-
| Multiwavelength Astronomy || Prof. Manami Sasaki || Friday || 10:00 am
|-
| X-ray Astronomy || Prof. Joern Wilms || Tuesday || 10:00 am
|}

On Tuesdays at 11:30\,am there is also the Astronomy Journal Club, where new papers from astronomy are presented in a friendly environment (https://www.sternwarte.uni-erlangen.de/wiki/index.php/Litclub).
All observatory members are expected to give at least one presentation per year in the club.

In addition there are weekly meetings for different projects, some of them as telephone conferences with other working groups, which are based inside or outside of Germany.

For work in Erlangen, the observatory has a large and very nice office in the ECAP building available. We recommend getting in touch with the other frequent users and joining the ECAP chat (https://chat.ecap.work/, login with your IDM account). It is also possible to join other groups for lunch (Caro can put you in touch with the neutrino people upon request).

All observatory members (BSc, MSc, PhD, ...) are expected to help with the student labs, typically four weeks each in March/early April and in September/October. This implies that you know you experiment and work on it well before the actual lab course. Student members will be remunerated for their help during the lab. You need to talk to your supervisor well in advance should you think about not being available during this time. In general, such requests for leave will only be accepted under extraordinary, job-related circumstances.

=Illness=

If you are ill - even if it is only a cold - talk to your supervisor and work from home. If you are seriously ill for more than two days, go to a Doctor and get a sick leave notice ("Krankschreibung"). Please inform Edith about this such that she can inform the personnel department that they can trigger the download of the sick leave notice. Do not believe your Dr. if they claim that this will happen automatically. We ''need'' to be informed by you!

=Safety=
Contact person: Ingo

The observatory is in general a very safe place to work. Nevertheless there are a few things you need to keep in mind. Once per year we have a safety instruction (attending is mandatory). Upon joining the institute you should watch the video of the last safety instruction at https://www.sternwarte.uni-erlangen.de/internal-area/internal-area-howto/.

=Webpages & email lists=
Contact person: Jakob, Max, Nico

The observatory's webpage is www.sternwarte.uni-erlangen.de, where you can also log in with your user name and password to get access to the internal part of the page and edit your user profile. You will also find useful information in our own Remeis-Wiki. A list of the e-mail lists should help to find the right contact person in case of problems. To be added to e-mail lists, you must contact the e-mail list admin (Max Lorenz).

{| class="wikitable"
|-
| ECAP (+ Observatory) || ecapmail@physik.uni-erlangen.de
|-
| Observatory || all@sternwarte.uni-erlangen.de
|-
| Multiwavelength Group || astro-multi@lists.fau.de
|-
| Stellar Group || stellar@sternwarte.uni-erlangen.de
|-
| X-ray Group || xray@sternwarte.uni-erlangen.de
|-
| Admins || admin@sternwarte.uni-erlangen.de
|-
| Telescope users || astro-observing@lists.fau.de
|-
| Social Media Team || astro-outreach@lists.fau.de
|}

In addition, we also have a Slack channel for quick queries and discussions within the group. You can join the same by asking someone in the group for an invite link.

Our observatory is also active on Social Media and has a Twitter (@DrRemeis) as well as an Instagram Account (@drremeis).

=The Remeis Cluster=
Contact person: admin@sternwarte.uni-erlangen.de

For your work at the observatory, you are provided with a desk and a computer, and access to our cluster for complex calculations. There are a few important things to consider: Data that should not be lost under any circumstances (e.g., scripts, theses) should be saved in your /home directory. Note, however, that the space available there is only a few GB. If you exceed your maximum storage limit, you will receive e-mails from the system. Do not ignore them. /home is backed up daily, and old data are kept for up to one year. Contact the admins if you need access to that. A folder under /userdata/data is also available for storage and meant for reproducible simulations/evaluation/data. There is no backup for /userdata, but failure is unlikely (RAID). While the storage there is very large, please use it sparingly nevertheless. If you want to run one or more time-consuming calculations, please use SLURM (more information in the Remeis wiki). Please be aware that your workstation is part of a computing cluster. Switching off the computer or any other hardware modifications are not permitted. Your computer stays on 24/7, please log out when you leave such that others can use it while you are not there. If you have any problems, please contact the admins.

=Telescopes=
Contact person: Philipp W., Steven, Jakob, Martin

The observatory owns 40cm and 50cm reflector telescopes (in the domes). They are used for observations and experiments in the lab course and also during guided tours. If you are interested in using the telescopes in your free time, e.g., for astro photography, you can receive instructions on how to use them. You should also sign up on the email list for telescope users.

=Important information for PhD=
The information listed below is based on Joerns E-mail from 2023-03-09 and is relevant for all new PhDs:
* The first person to discuss your questions with is your PhD advisor. They should all be aware of the formalities and requirements.
* The legal framework is well described in the Promotionsordnung of FAU and of the NatFak, and there is also a handout on the overall formalities that you will have to be aware of. All of these materials can be found at https://www.nat.fau.de/forschung/forschende/promotion/.
This page also contains a list of Frequently Asked Questions (top right part of the page), including many of the general questions that are asked concerning the formalities of the PhD, especially also in relation to cumulative theses.
* The specific framework within the Department of Physics is described in the Ausfuehrungsbestimmungen of the Department. Your advisors have a copy, and you can also access them directly by joining the studon group "Infos fuer Promovierende", https://www.studon.fau.de/studon/goto.php?target=grp_2684505. The group password is Promotion_Physik . The most important thing here is that these regulations explain the requirements for the (literal or paraphrased) inclusion of text from publication in the thesis manuscript as well as the procedure for preparing cumulative theses (i.e., get in contact with the Department more than a year before the planned submission in order to get an informal approval that your publication plan would result in something that is likely to be considered to be acceptable as a thesis).
* If you are close to submitting your thesis: Contrary to statements of the forms available on Docdaten and some rumors among people pursuing a PhD, you can start the procedure to initiate the doctoral procedure approximately four weeks BEFORE submitting the thesis. For this you only need your CV, a copy of your ID (yes, you are permitted by German law to give a copy of your ID to somebody else), the signed application form (available on DocDaten), and a complete and current list of your publications. The advantage of starting this process early is that at the time of submission of your thesis the referees have already been decided, which can save a few weeks of time. There is flexibility in when you submit this, if you think you need four weeks and it really takes five weeks until you can submit the thesis, this will not cause any problems.

DocDaten: https://www.docdaten.fau.de/gs/ - register ASAP. More important information can also be found at: https://www.fau.eu/graduate-centre/doctoral-degrees/ .

=Commuting from Erlangen=
==Carpool==
Contact person: Max, Nico

We coordinate commuting for the carpool via the app "MyCarpoolApp", which is available on Android and iOS. We use a group account with the name "Remeis Reloaded". The access password is Sternwartstr. 7 . By using "change user" in the menu you can create your user account. The fuel costs are shared equally by everybody in the car. In addition to the fuel costs there is a rate of 2.50€ per car per ride, which is also shared equally by everybody. This is used to reduce the driver's additional costs, like maintenance and such.

==Public transport==
On average there are two trains per hour between Bamberg and Erlangen. If you walk all the way from the Station to the observatory it will take you about 30\,minutes, but there is also a bus connection.
Bus line 901, for example, serves both the train station and the two nearest stops to the observatory (``Schranne'' and ``Schulplatz'').

=Lunch=
The observatory kitchen is equipped with an induction stove, a microwave, and tableware. You can store food in the fridge, but it is important everything has your name on it and that you clean out your old things every now and then.
Put dirty dishes in the dish washer, run it if it is full, and empty it out if you come to the kitchen and the cleaning cycle has finished. Some observatory members walk downtown for their lunch (mostly at about 12:30 pm), while the rest of them meet in the kitchen on the first floor at around noon.

=Coffee=
Contact person: Steven

In the kitchen on the first floor you'll find a Jura E60 coffee maker. If you need coffee, simply add your name to the list above the machine. Our coffee maker only makes coffee or espresso. There is also a separate milk frother in that kitchen. If you notice that we are almost out of coffee or milk, please tell the contact person or (even better) get some yourself and get reimbursed by the contact person. Please note that the coffee machine may only be used for making coffee, please use the kettle for making hot water.

=Remeis community=
Contact person: almost everybody

There is a unique community at the observatory, not only within the individual working groups, but also across the board. Special events are, e.g., the Christmas Party, Skiing in January, Canoeing in the summer and the FRANCI-Meeting with the ECAP and the Astronomy Group from Wuerzburg. Now and then, we organize evenings to watch movies, trips to the cinema, restaurants and bars in Bamberg or Erlangen. That does not happen automatically though and everybody (you too) can get involved. In the summertime there is a pool in the observatory's big garden and we regularly do barbecues. If you like cake you can join our Whatsapp group for cake orders. On their birthday most of the Remeis people bring a cake to share with everybody.

=Sponsoring association and guided tours=
Contact person: Ingo, Nico
The sponsoring association of Dr. Karl Remeis Observatory supports our observatory in preserving its historical collections and public relations. A big part of these public relations are guided tours, which are offered monthly and also on demand. If you are interested in spreading your enthusiasm for Astronomy and Astrophysics, you should a) become a member of the sponsoring association and
b) join our guided tours team! You will get paid by the sponsoring association for giving tours.

[[Category:Internal]][[Category:Current Members]]

Welcome Newbies

2025-08-25T12:03:12Z

Collischon: Created page with " Welcome to Remeis-Observatory! Here are some relevant infos for everyone joining. =Presence at the observatory and important meeting dates= In general, in order to ensure th..."

Welcome to Remeis-Observatory! Here are some relevant infos for everyone joining.

=Presence at the observatory and important meeting dates=
In general, in order to ensure that there are sufficient scientific interactions, all observatory members (BSc, MSc, PhD) are expected to be physically present at the observatory for three days per week. You can ask for permission to work from home during the remaining days. Due to insurance reasons this request needs to be made in writing and formally approved by your supervisor. You are also expected to attend the weekly group meetings in person.

{| class="wikitable"
|-
| Stellar Astronomy || Prof. Ulrich Heber || Monday || 04:00 pm
|-
| Multiwavelength Astronomy || Prof. Manami Sasaki || Friday || 10:00 am
|-
| X-ray Astronomy || Prof. Joern Wilms || Tuesday || 10:00 am
|}

On Tuesdays at 11:30\,am there is also the Astronomy Journal Club, where new papers from astronomy are presented in a friendly environment (https://www.sternwarte.uni-erlangen.de/wiki/index.php/Litclub).
All observatory members are expected to give at least one presentation per year in the club.

In addition there are weekly meetings for different projects, some of them as telephone conferences with other working groups, which are based inside or outside of Germany.

For work in Erlangen, the observatory has a large and very nice office in the ECAP building available. We recommend getting in touch with the other frequent users and joining the ECAP chat (\https://chat.ecap.work/, login with your IDM account). It is also possible to join other groups for lunch (Caro can put you in touch with the neutrino people upon request).

All observatory members (BSc, MSc, PhD, ...) are expected to help with the student labs, typically four weeks each in March/early April and in September/October. This implies that you know you experiment and work on it well before the actual lab course. Student members will be remunerated for their help during the lab. You need to talk to your supervisor well in advance should you think about not being available during this time. In general, such requests for leave will only be accepted under extraordinary, job-related circumstances.

=Illness=

If you are ill -- even if it is only a cold -- talk to your supervisor and work from home. If you are seriously ill for more than two days, go to a Doctor and get a sick leave notice ("Krankschreibung"). Please inform Edith about this such that she can inform the personnel department that they can trigger the download of the sick leave notice. Do not believe your Dr. if they claim that this will happen automatically. We ''need'' to be informed by you!

=Safety=
Contact person: Ingo

The observatory is in general a very safe place to work. Nevertheless there are a few things you need to keep in mind. Once per year we have a safety instruction (attending is mandatory). Upon joining the institute you should watch the video of the last safety instruction at https://www.sternwarte.uni-erlangen.de/internal-area/internal-area-howto/.

=Webpages & email lists=
Contact person: Jakob, Max, Nico

The observatory's webpage is www.sternwarte.uni-erlangen.de, where you can also log in with your user name and password to get access to the internal part of the page and edit your user profile. You will also find useful information in our own Remeis-Wiki at \url{https://www.sternwarte.uni-erlangen.de/wiki}. A list of the e-mail lists should help to find the right contact person in case of problems. To be added to e-mail lists, you must contact the e-mail list admin (Max Lorenz).

{| class="wikitable"
|-
| ECAP (+ Observatory) || ecapmail@physik.uni-erlangen.de
|-
| Observatory || all@sternwarte.uni-erlangen.de
|-
| Multiwavelength Group || astro-multi@lists.fau.de
|-
| Stellar Group || stellar@sternwarte.uni-erlangen.de
|-
| X-ray Group || xray@sternwarte.uni-erlangen.de
|-
| Admins || admin@sternwarte.uni-erlangen.de
|-
| Telescope users || astro-observing@lists.fau.de
|-
| Social Media Team || astro-outreach@lists.fau.de
|}

In addition, we also have a Slack channel for quick queries and discussions within the group. You can join the same by asking someone in the group for an invite link.

Our observatory is also active on Social Media and has a Twitter (@DrRemeis) as well as an Instagram Account (@drremeis).

=The Remeis Cluster=
Contact person: admin@sternwarte.uni-erlangen.de

For your work at the observatory, you are provided with a desk and a computer, and access to our cluster for complex calculations. There are a few important things to consider: Data that should not be lost under any circumstances (e.g., scripts, theses) should be saved in your /home directory. Note, however, that the space available there is only a few GB. If you exceed your maximum storage limit, you will receive e-mails from the system. Do not ignore them. /home is backed up daily, and old data are kept for up to one year. Contact the admins if you need access to that. A folder under /userdata/data is also available for storage and meant for reproducible simulations/evaluation/data. There is no backup for /userdata, but failure is unlikely (RAID). While the storage there is very large, please use it sparingly nevertheless. If you want to run one or more time-consuming calculations, please use SLURM (more information in the Remeis wiki). Please be aware that your workstation is part of a computing cluster. Switching off the computer or any other hardware modifications are not permitted. Your computer stays on 24/7, please log out when you leave such that others can use it while you are not there. If you have any problems, please contact the admins.

=Telescopes=
Contact person: Philipp W., Steven, Jakob, Martin

The observatory owns 40cm and 50cm reflector telescopes (in the domes). They are used for observations and experiments in the lab course and also during guided tours. If you are interested in using the telescopes in your free time, e.g., for astro photography, you can receive instructions on how to use them. You should also sign up on the email list for telescope users.

=Important information for PhD=
The information listed below is based on J\"orns E-mail from 2023-03-09 and is relevant for all new PhDs:
* The first person to discuss your questions with is your PhD advisor. They should all be aware of the formalities and requirements.
* The legal framework is well described in the Promotionsordnung of FAU and of the NatFak, and there is also a handout on the overall formalities that you will have to be aware of. All of these materials can be found at https://www.nat.fau.de/forschung/forschende/promotion/.
This page also contains a list of Frequently Asked Questions (top right part of the page), including many of the general questions that are asked concerning the formalities of the PhD, especially also in relation to cumulative theses.
* The specific framework within the Department of Physics is described in the Ausfuehrungsbestimmungen of the Department. Your advisors have a copy, and you can also access them directly by joining the studon group "Infos fuer Promovierende", https://www.studon.fau.de/studon/goto.php?target=grp_2684505. The group password is Promotion_Physik . The most important thing here is that these regulations explain the requirements for the (literal or paraphrased) inclusion of text from publication in the thesis manuscript as well as the procedure for preparing cumulative theses (i.e., get in contact with the Department more than a year before the planned submission in order to get an informal approval that your publication plan would result in something that is likely to be considered to be acceptable as a thesis).
* If you are close to submitting your thesis: Contrary to statements of the forms available on Docdaten and some rumors among people pursuing a PhD, you can start the procedure to initiate the doctoral procedure approximately four weeks BEFORE submitting the thesis. For this you only need your CV, a copy of your ID (yes, you are permitted by German law to give a copy of your ID to somebody else), the signed application form (available on DocDaten), and a complete and current list of your publications. The advantage of starting this process early is that at the time of submission of your thesis the referees have already been decided, which can save a few weeks of time. There is flexibility in when you submit this, if you think you need four weeks and it really takes five weeks until you can submit the thesis, this will not cause any problems.

DocDaten: https://www.docdaten.fau.de/gs/ - register ASAP. More important information can also be found at: https://www.fau.eu/graduate-centre/doctoral-degrees/ .

=Commuting from Erlangen=
==Carpool==
Contact person: Max, Nico

We coordinate commuting for the carpool via the app "MyCarpoolApp", which is available on Android and iOS. We use a group account with the name "Remeis Reloaded". The access password is Sternwartstr. 7 . By using "change user" in the menu you can create your user account. The fuel costs are shared equally by everybody in the car. In addition to the fuel costs there is a rate of 2.50€ per car per ride, which is also shared equally by everybody. This is used to reduce the driver's additional costs, like maintenance and such.

==Public transport==
On average there are two trains per hour between Bamberg and Erlangen. If you walk all the way from the Station to the observatory it will take you about 30\,minutes, but there is also a bus connection.
Bus line 901, for example, serves both the train station and the two nearest stops to the observatory (``Schranne'' and ``Schulplatz'').

=Lunch=
The observatory kitchen is equipped with an induction stove, a microwave, and tableware. You can store food in the fridge, but it is important everything has your name on it and that you clean out your old things every now and then.
Put dirty dishes in the dish washer, run it if it is full, and empty it out if you come to the kitchen and the cleaning cycle has finished. Some observatory members walk downtown for their lunch (mostly at about 12:30 pm), while the rest of them meet in the kitchen on the first floor at around noon.

=Coffee=
Contact person: Steven

In the kitchen on the first floor you'll find a Jura E60 coffee maker. If you need coffee, simply add your name to the list above the machine. Our coffee maker only makes coffee or espresso. There is also a separate milk frother in that kitchen. If you notice that we are almost out of coffee or milk, please tell the contact person or (even better) get some yourself and get reimbursed by the contact person. Please note that the coffee machine may only be used for making coffee, please use the kettle for making hot water.

=Remeis community=
Contact person: almost everybody

There is a unique community at the observatory, not only within the individual working groups, but also across the board. Special events are, e.g., the Christmas Party, Skiing in January, Canoeing in the summer and the FRANCI-Meeting with the ECAP and the Astronomy Group from Wuerzburg. Now and then, we organize evenings to watch movies, trips to the cinema, restaurants and bars in Bamberg or Erlangen. That does not happen automatically though and everybody (you too) can get involved. In the summertime there is a pool in the observatory's big garden and we regularly do barbecues. If you like cake you can join our Whatsapp group for cake orders. On their birthday most of the Remeis people bring a cake to share with everybody.

=Sponsoring association and guided tours=
Contact person: Ingo, Katrin
The sponsoring association of Dr. Karl Remeis Observatory supports our observatory in preserving its historical collections and public relations. A big part of these public relations are guided tours, which are offered monthly and also on demand. If you are interested in spreading your enthusiasm for Astronomy and Astrophysics, you should a) become a member of the sponsoring association and
b) join our guided tours team! Tour groups are expected to tip.

[[Category:Internal]][[Category:Current Members]]

How to BBQ

2025-05-14T13:16:34Z

Collischon: Create how to BBQ

== How to use the BBQ ==

Setting up the BBQ with a proper charcoal fire has often proven a bit tricky. In order not to embarrass yourself in front of the hungry masses, here are the steps to follow and what to look out for.

* Make sure the equipment is there. Everything (starter chimney, leather gloves, matches, leftover charcoal briquettes and wood-wax-based fire starter ("Grillanzuender") ) should be in the meridian basement opposite of the door.
* Buy more charcoal or starter if the storage is low. Using paper to start does not work. Briquettes are better than regular charcoal due to increased ventilation and they will burn longer.
* The chimney needs additional air to be able to enter from below. Prepare a BBQ grate, either the main one or the small round one with a bit of air underneath.
* On the BBQ grate from above, place starter cubes (3 should work). Fill the chimney with coal to the top (not over it), set the starter on fire and place the chimney on top.
* Once the coal on the top starts burning, the chimney can be emptied onto the BBQ.
* For more than about 6 people, fill and fire up the chimney again to make sure there is enough coal burning

There are a few things to look out for:
* You may notice too late that there is no starter left. So have we. Paper will smoke and block its own oxygen before burning properly, so just go and buy some
* If the chimney does not pull enough air, make sure it is placed on a grate, as stated above
* In dry times, keep a bit of water ready next to the grill - we have managed to spill burning coal on the grass in the past. Watering cans should be in the workshop

[[Category:Current Members]]

PhD hat for Ole

2024-01-31T13:00:05Z

Collischon:

[[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 on Crete?
* Books: LOTR, ...?
* Motorbike
* Running: Marathon relay with MPE in Munich

== Others: ==
* Guided tours (& also for kids)
* Lab course: Azimuth experiment
* One of the few regulars at ECAP office

=== 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 Dominic

2024-01-09T09:30:52Z

Collischon:

[[Category:Internal]]
'''Info'''

'''Hat:'''

30x30cm platform (top), 15cm tube (base) Umfang: ??cm -> Steven

'''General:'''
*social media
*insta walk
*Bernreuther Dominic Social Media (BDSM) → Steven
*tours and desperate wish to find a new guide planetarium half globe with clay planets → Aafia
*CCD
*FRANCI (logo) → Steven
*Christmass party (wok)
*2bros and scam
*V2 rocket → Steven
*car ford ka → knunchkugle (spherical car)

'''science:'''

*training → lightbulbe
*Machine learning → pins colored representing layers of neural network connected with strings → Jonathan,Ole
*Bscan (actual Bee ) → Amy
*Bscam (Bubble Scanning Algorith [Module] Music) → Federico drive
*B - scam (scam emails) → Caro (/home/collischon/Documents/scammails.txt)
*bubble plastic with pictures of SNR → Jonathan
*soap bubbles as a tassle → Ole
*barcode scanner → Philipp
*blazar image (in the kitchen) → Steven

'''Personal:'''
*Remeis coint (crypto currency) → Philipp
*?girlfriend has mushrooms he don't?
*mushroom picture, many mushrooms find the SNR (?)
*singing metal (tiny microphone)
*or playing metal (mini instruments) →
*container houses
*tiny houses around the word
*mountain bike
*motor bike (suzuki (susi)) mini models, probably 1st gen (1999—2002) SV650
*whiskey
*limoncello → paper bottle with bright yellow
*riesen (big riesen packed in another big riesen) (bunch of riesen that are found insted of the bubble) → Martin
*(horrible)chicken at the Rewe
[[Category:Internal]]

PhD Hat Dominic

2023-11-22T08:59:21Z

Collischon:

[[Category:Internal]]
'''Info'''

'''Hat:'''

30x30cm platform (top), 15cm tube (base) Umfang: ??cm -> Steven

'''General:'''
*social media
*insta walk
*Bernreuther Dominic Social Media (BDSM) → Steven
*tours and desperate wish to find a new guide planetarium half globe with clay planets → Aafia
*CCD
*FRANCI (logo) → Steven
*Christmass party (wok)
*2bros and scam
*V2 rocket → Steven
*car ford ka → knunchkugle (spherical car)

'''science:'''

*training → lightbulbe
*Machine learning → pins colored representing layers of neural network connected with strings → Jonathan,Ole
*Bscan (actual Bee ) → Amy
*Bscam (Bubble Scanning Algorith [Module] Music) → Federico drive
*B - scam (scam emails) → Caro
*bubble plastic with pictures of SNR → Jonathan
*soap bubbles as a tassle → Ole
*barcode scanner → Philipp
*blazar image (in the kitchen) → Steven

'''Personal:'''
*Remeis coint (crypto currency) → Philipp
*?girlfriend has mushrooms he don't?
*mushroom picture, many mushrooms find the SNR (?)
*singing metal (tiny microphone)
*or playing metal (mini instruments) →
*container houses
*tiny houses around the word
*mountain bike
*motor bike (suzuki (susi)) mini models, probably 1st gen (1999—2002) SV650
*whiskey
*limoncello → paper bottle with bright yellow
*riesen (big riesen packed in another big riesen) (bunch of riesen that are found insted of the bubble) → Martin
*(horrible)chicken at the Rewe
[[Category:Internal]]