Remeis-Wiki - User contributions [en]

Admin

2026-02-03T20:55:59Z

Lorenz:

===== Remeis Admin-Page =====

This page is only internally visible to the Admins.

Things which need to be documented:
* Ansible
* Updates (using unattended-upgrades)
* Puppet
* Storage volumes (raids, filesystems, oddities, etc.)

==== Lab Course ====

* Before the lab course:
** check the PCs in the Meridian building:
*** they should all be functional, broken ones should be replaced
*** in total we should have about 10 computers available for the students
** [[setup prakti|Setup the prakti accounts]]
* [[Computer_Introduction|Introduction to Computers/Linux for Lab Students ]]

==== Serendipitous Issues ====

* [[Login Problems|Typical login problems]]
* [[Unmet Dependencies|''unmet dependencies'' issue in apt-get]]
* [[Overflow Filesystem|overflow file system]]

==== Add new Users ====
* Go to the remeis internal homepage -> admin -> LDAP
* Fill out the necessary fields, including a valid email address. If possible, also fill out the fields for room and telephone number.
* Log into LDAP ( https://www.sternwarte.uni-erlangen.de/phpldapadmin/), go to import and copy the text of the previous step. '''Important''': if the user is external, "current" in the first line has to be changed to "external"
* set the password of the user: Use the LDAP query <code>ldappasswd -H ldap://cygnus.internal -x -D "cn=admin,dc=sternwarte,dc=uni-erlangen,dc=de" -W -S "uid={USERNAME},ou=current,ou=People,dc=sternwarte,dc=uni-erlangen,dc=de"</code> while obviously adjusting the LDAP dn.
* log in as ubuntuadmin on libra and create the home directory like that: <code>sudo mkdir /exports/disk1/{USERNAME} && sudo chown {USERNAME}:remeis /exports/disk1/{USERNAME}</code>
* Set the quota (on libra), using a prototype which has normal quota <code>sudo edquota -p [prototype] [username]</code> (normal Quota is 8GB softlimit and 12GB hardlimit; it can be manually edited/shown with edquota -u user)
* Add the default cshrc to /home/username/.cshrc
* If desired (in most cases), create a folder for the user at ''/userdata/data/username'' and adjust the permissions with <code>sudo chown username:remeis /userdata/data/username</code>
* Send Email to admin about the new user

==== Running Software / Updates / Setups ====

In this section a selection of services and their current configuration is described.

* [[CUPS| CUPS]] (Printing Service)
* [[Virtual Boxes| Virtual Boxes]]

[[Category:Admin]]

LDAP

2025-09-11T18:17:51Z

Lorenz:

[[Category:Admin]]
= LDAP =
The LDAP server at Remeis is running on vela. The service itself is called ''slapd''. A backup LDAP server is running on libra.

Every interaction with the ''slapd'' requires root access.

== Where LDAP is used ==
LDAP is not only used for the authentication to login into the variety of machines at Remeis. Also a lot of other services/scripts use ldap:

* This wiki
* The internal webpage
* [[GitLab]]
* [[#phpLDAPadmin|phpLDAPadmin]]
* The <code>who_takes_the_minutes.pl</code> script of the X-ray group
* The ''cgnotifier'' for the [[cgroups]]

== Configuration ==

=== Config files ===
The main LDAP configuration file is <code>/etc/ldap.conf</code>. Note that this is not the default location for the configuration file. Therefore the defaults for the slapd are changed in <code>/etc/default/slapd</code>, see the entry <code>SLAPD_CONF</code>. The <code>/etc/ldap.conf</code> is also present on all the clients and specifies via IP-Address which LDAP server to contact for authentication. The LDAP requests are then handled on taurus by the ''slapd'' which is configured via <code>/etc/ldap/slapd.conf</code>.

=== phpLDAPadmin ===
phpLDAPadmin is a web interface based on [https://de.wikipedia.org/wiki/PHP PHP] which allows simple modifications to the directory for example to [[:Category:Admin#Add new Users|add new users]] or change group memberships. It is accessible via the [https://www.sternwarte.uni-erlangen.de/intern/phpldapadmin/ internal webpages] and only out of the network at the Remeis observatory.

==== Configuration of phpLADPadmin ====
The configuration files for phpLDAPadmin are located in <code>/etc/phpldapadmin/</code> on the webserver, in this case [[cetus]]. The important file is <code>config.php</code> which holds information about which LDAP servers can be queried, in this case [[taurus]].

== Starting/Stopping the service ==
The slapd can be stopped via [https://de.wikipedia.org/wiki/Systemd systemd]:
<pre>
systemctl stop slapd
</pre>
'''Important:''' If you do so no authentication on the whole cluster is possible anymore. You can not open a new shell on any host until you start the service again!

Starting the ''slapd'':
<pre>
systemctl start slapd
</pre>
You also can have a look at the output produced by the running service via
<pre>
systemctl status slapd
</pre>

== Database ==
The [https://en.wikipedia.org/wiki/Berkeley_DB Berkeley DB] containing all the active directory information is located at <code>/var/lib/ldap</code>. Files in this directory must not be touched manually in any way. The only secure way to see the content of the database is by using ''slapcat''. For example
<pre>
slapcat -f /etc/ldap/slapd.conf
</pre>
will show all entries of the database.

== Backup ==
Each night the database is dumped to <code>/data/system/backup/ldap/</code> via a cronjob in <code>/etc/cron.d/ldap_backup</code>. Also a tarball of the ''slapd'' and <code>ldap.conf</code> is created there. All backups older than 14 days are deleted.

== Migration ==

See also https://serverfault.com/questions/730088/how-to-migrate-ldap-database-schema-configuration-to-other-machine

=== Step 1: Export configuration trees and database ===

'''From old provider (`vela`)'''
<pre>
sudo slapcat -n 0 -l ldap_config_vela.ldif
sudo slapcat -n 1 -l ldap_data_vela.ldif
</pre>

'''From old consumer (`libra`)'''
<pre>
sudo slapcat -n 0 -l ldap_config_libra.ldif
</pre>

=== Step 2: Save certificates ===

'''vela:'''
<pre>
/etc/ssl/certs/openldap.pem
/etc/ldap/grus_slapd_cert.pem
/etc/ldap/grus_slapd_key.pem
</pre>

'''libra:'''
<pre>
/etc/ssl/certs/openldap.pem
/etc/ldap/phoenix_slapd_cert.pem
/etc/ldap/phoenix_slapd_key.pem
</pre>

=== Step 3: Set up new provider ===

'''Install packages'''
<pre>
sudo apt install slapd ldap-utils
</pre>

'''Stop slapd and remove existing configuration and data'''
<pre>
sudo systemctl stop slapd
sudo rm -rf /etc/ldap/slapd.d/*
sudo rm -rf /var/lib/ldap/*
</pre>

'''Import configuration and data'''
<pre>
sudo slapadd -n 0 -F /etc/ldap/slapd.d -l /path/to/ldap_config_vela.ldif
sudo slapadd -n 1 -l /path/to/ldap_data_vela.ldif
</pre>

'''Set ownership of /etc/ldap/slapd.d and /var/lib/ldap to openldap'''

'''Restore certificates'''
<pre>
lrwxrwxrwx 1 root root 45 Jul 10 2023 /etc/ssl/certs/openldap.pem -> /usr/local/share/ca-certificates/openldap.pem
-rw-r--r-- 1 root root 1614 Jul 10 2023 /etc/ldap/grus_slapd_cert.pem
-rw-r----- 1 root openldap 8170 Jul 10 2023 /etc/ldap/grus_slapd_key.pem
</pre>

'''Start slapd'''
<pre>
sudo systemctl start slapd
</pre>

'''Verify'''
<pre>
ldapsearch -H ldap://localhost -x -b dc=sternwarte,dc=uni-erlangen,dc=de
</pre>

=== Step 4: Set up new consumer for replication ===

'''Install packages'''
<pre>
sudo apt install slapd ldap-utils
</pre>

'''Stop slapd and remove existing configuration and data'''
<pre>
sudo systemctl stop slapd
sudo rm -rf /etc/ldap/slapd.d/*
sudo rm -rf /var/lib/ldap/*
</pre>

'''Import configuration'''
<pre>
sudo slapadd -n 0 -F /etc/ldap/slapd.d -l /path/to/ldap_config_libra.ldif
</pre>

'''Set ownership of /etc/ldap/slapd.d and /var/lib/ldap to openldap'''

'''Restore certificates''' (guess other r permission on key is wrong currently)
<pre>
lrwxrwxrwx 1 root root 45 May 13 2023 /etc/ssl/certs/openldap.pem -> /usr/local/share/ca-certificates/openldap.crt
-rw-r--r-- 1 root root 1619 Jul 11 2023 /etc/ldap/phoenix_slapd_cert.pem
-rw-r--r-- 1 root root 8180 Jul 11 2023 /etc/ldap/phoenix_slapd_key.pem
</pre>

'''Start slapd'''
<pre>
sudo systemctl start slapd
</pre>

'''Check replication'''
<pre>
journalctl -fu slapd
</pre>

'''Verify'''
<pre>
ldapsearch -H ldap://localhost -x -b dc=sternwarte,dc=uni-erlangen,dc=de
</pre>

=== Step 5: Check dependent services ===

* ldap backup
* Wiki
* Internal webpage
* Gitlab
* phpLDAPadmin (web interface)
* `who_takes_the_minutes`

LDAP

2025-09-11T18:17:25Z

Lorenz:

[[Category:Admin]]
= LDAP =
The LDAP server at Remeis is running on vela. The service itself is called ''slapd''. A backup LDAP server is running on libra.

Every interaction with the ''slapd'' requires root access.

== Where LDAP is used ==
LDAP is not only used for the authentication to login into the variety of machines at Remeis. Also a lot of other services/scripts use ldap:

* This wiki
* The internal webpage
* [[GitLab]]
* [[#phpLDAPadmin|phpLDAPadmin]]
* The <code>who_takes_the_minutes.pl</code> script of the X-ray group
* The ''cgnotifier'' for the [[cgroups]]

== Configuration ==

=== Config files ===
The main LDAP configuration file is <code>/etc/ldap.conf</code>. Note that this is not the default location for the configuration file. Therefore the defaults for the slapd are changed in <code>/etc/default/slapd</code>, see the entry <code>SLAPD_CONF</code>. The <code>/etc/ldap.conf</code> is also present on all the clients and specifies via IP-Address which LDAP server to contact for authentication. The LDAP requests are then handled on taurus by the ''slapd'' which is configured via <code>/etc/ldap/slapd.conf</code>.

=== phpLDAPadmin ===
phpLDAPadmin is a web interface based on [https://de.wikipedia.org/wiki/PHP PHP] which allows simple modifications to the directory for example to [[:Category:Admin#Add new Users|add new users]] or change group memberships. It is accessible via the [https://www.sternwarte.uni-erlangen.de/intern/phpldapadmin/ internal webpages] and only out of the network at the Remeis observatory.

==== Configuration of phpLADPadmin ====
The configuration files for phpLDAPadmin are located in <code>/etc/phpldapadmin/</code> on the webserver, in this case [[cetus]]. The important file is <code>config.php</code> which holds information about which LDAP servers can be queried, in this case [[taurus]].

== Starting/Stopping the service ==
The slapd can be stopped via [https://de.wikipedia.org/wiki/Systemd systemd]:
<pre>
systemctl stop slapd
</pre>
'''Important:''' If you do so no authentication on the whole cluster is possible anymore. You can not open a new shell on any host until you start the service again!

Starting the ''slapd'':
<pre>
systemctl start slapd
</pre>
You also can have a look at the output produced by the running service via
<pre>
systemctl status slapd
</pre>

== Database ==
The [https://en.wikipedia.org/wiki/Berkeley_DB Berkeley DB] containing all the active directory information is located at <code>/var/lib/ldap</code>. Files in this directory must not be touched manually in any way. The only secure way to see the content of the database is by using ''slapcat''. For example
<pre>
slapcat -f /etc/ldap/slapd.conf
</pre>
will show all entries of the database.

== Backup ==
Each night the database is dumped to <code>/data/system/backup/ldap/</code> via a cronjob in <code>/etc/cron.d/ldap_backup</code>. Also a tarball of the ''slapd'' and <code>ldap.conf</code> is created there. All backups older than 14 days are deleted.

== Migration ==

See also https://serverfault.com/questions/730088/how-to-migrate-ldap-database-schema-configuration-to-other-machine

=== Step 1: Export configuration trees and database ===

'''From old provider (`vela`)'''
<pre>
sudo slapcat -n 0 -l ldap_config_vela.ldif
sudo slapcat -n 1 -l ldap_data_vela.ldif
</pre>

'''From old consumer (`libra`)'''
<pre>
sudo slapcat -n 0 -l ldap_config_libra.ldif
</pre>

=== Step 2: Save certificates ===

'''vela:'''
<pre>
/etc/ssl/certs/openldap.pem
/etc/ldap/grus_slapd_cert.pem
/etc/ldap/grus_slapd_key.pem
</pre>

'''libra:'''
<pre>
/etc/ssl/certs/openldap.pem
/etc/ldap/phoenix_slapd_cert.pem
/etc/ldap/phoenix_slapd_key.pem
</pre>

=== Step 3: Set up new provider ===

'''Install packages'''
<pre>
sudo apt install slapd ldap-utils
</pre>

'''Stop slapd and remove existing configuration and data'''
<pre>
sudo systemctl stop slapd
sudo rm -rf /etc/ldap/slapd.d/*
sudo rm -rf /var/lib/ldap/*
</pre>

'''Import configuration and data'''
<pre>
sudo slapadd -n 0 -F /etc/ldap/slapd.d -l /path/to/ldap_config_vela.ldif
sudo slapadd -n 1 -l /path/to/ldap_data_vela.ldif
</pre>

'''Set ownership of /etc/ldap/slapd.d and /var/lib/ldap to openldap'''

'''Restore certificates'''
<pre>
lrwxrwxrwx 1 root root 45 Jul 10 2023 /etc/ssl/certs/openldap.pem -> /usr/local/share/ca-certificates/openldap.pem
-rw-r--r-- 1 root root 1614 Jul 10 2023 /etc/ldap/grus_slapd_cert.pem
-rw-r----- 1 root openldap 8170 Jul 10 2023 /etc/ldap/grus_slapd_key.pem
</pre>

'''Start slapd'''
<pre>
sudo systemctl start slapd
</pre>

'''Verify'''
<pre>
ldapsearch -H ldap://localhost -x -b dc=sternwarte,dc=uni-erlangen,dc=de
</pre>

=== Step 4: Set up new consumer for replication ===

'''Install packages'''
<pre>
sudo apt install slapd ldap-utils
</pre>

'''Stop slapd and remove existing configuration and data'''
<pre>
sudo systemctl stop slapd
sudo rm -rf /etc/ldap/slapd.d/*
sudo rm -rf /var/lib/ldap/*
</pre>

'''Import configuration'''
<pre>
sudo slapadd -n 0 -F /etc/ldap/slapd.d -l /path/to/ldap_config_libra.ldif
</pre>

'''Set ownership of /etc/ldap/slapd.d and /var/lib/ldap to openldap'''

'''Restore certificates''' (guess other r permission on key is a wrong currently)
<pre>
lrwxrwxrwx 1 root root 45 May 13 2023 /etc/ssl/certs/openldap.pem -> /usr/local/share/ca-certificates/openldap.crt
-rw-r--r-- 1 root root 1619 Jul 11 2023 /etc/ldap/phoenix_slapd_cert.pem
-rw-r--r-- 1 root root 8180 Jul 11 2023 /etc/ldap/phoenix_slapd_key.pem
</pre>

'''Start slapd'''
<pre>
sudo systemctl start slapd
</pre>

'''Check replication'''
<pre>
journalctl -fu slapd
</pre>

'''Verify'''
<pre>
ldapsearch -H ldap://localhost -x -b dc=sternwarte,dc=uni-erlangen,dc=de
</pre>

=== Step 5: Check dependent services ===

* ldap backup
* Wiki
* Internal webpage
* Gitlab
* phpLDAPadmin (web interface)
* `who_takes_the_minutes`

LDAP

2025-09-11T15:41:43Z

Lorenz:

[[Category:Admin]]
= LDAP =
The LDAP server at Remeis is running on vela. The service itself is called ''slapd''. A backup LDAP server is running on libra.

Every interaction with the ''slapd'' requires root access.

== Where LDAP is used ==
LDAP is not only used for the authentication to login into the variety of machines at Remeis. Also a lot of other services/scripts use ldap:

* This wiki
* The internal webpage
* [[GitLab]]
* [[#phpLDAPadmin|phpLDAPadmin]]
* The <code>who_takes_the_minutes.pl</code> script of the X-ray group
* The ''cgnotifier'' for the [[cgroups]]

== Configuration ==

=== Config files ===
The main LDAP configuration file is <code>/etc/ldap.conf</code>. Note that this is not the default location for the configuration file. Therefore the defaults for the slapd are changed in <code>/etc/default/slapd</code>, see the entry <code>SLAPD_CONF</code>. The <code>/etc/ldap.conf</code> is also present on all the clients and specifies via IP-Address which LDAP server to contact for authentication. The LDAP requests are then handled on taurus by the ''slapd'' which is configured via <code>/etc/ldap/slapd.conf</code>.

=== phpLDAPadmin ===
phpLDAPadmin is a web interface based on [https://de.wikipedia.org/wiki/PHP PHP] which allows simple modifications to the directory for example to [[:Category:Admin#Add new Users|add new users]] or change group memberships. It is accessible via the [https://www.sternwarte.uni-erlangen.de/intern/phpldapadmin/ internal webpages] and only out of the network at the Remeis observatory.

==== Configuration of phpLADPadmin ====
The configuration files for phpLDAPadmin are located in <code>/etc/phpldapadmin/</code> on the webserver, in this case [[cetus]]. The important file is <code>config.php</code> which holds information about which LDAP servers can be queried, in this case [[taurus]].

== Starting/Stopping the service ==
The slapd can be stopped via [https://de.wikipedia.org/wiki/Systemd systemd]:
<pre>
systemctl stop slapd
</pre>
'''Important:''' If you do so no authentication on the whole cluster is possible anymore. You can not open a new shell on any host until you start the service again!

Starting the ''slapd'':
<pre>
systemctl start slapd
</pre>
You also can have a look at the output produced by the running service via
<pre>
systemctl status slapd
</pre>

== Database ==
The [https://en.wikipedia.org/wiki/Berkeley_DB Berkeley DB] containing all the active directory information is located at <code>/var/lib/ldap</code>. Files in this directory must not be touched manually in any way. The only secure way to see the content of the database is by using ''slapcat''. For example
<pre>
slapcat -f /etc/ldap/slapd.conf
</pre>
will show all entries of the database.

== Backup ==
Each night the database is dumped to <code>/data/system/backup/ldap/</code> via a cronjob in <code>/etc/cron.d/ldap_backup</code>. Also a tarball of the ''slapd'' and <code>ldap.conf</code> is created there. All backups older than 14 days are deleted.

== Migration ==

See also https://serverfault.com/questions/730088/how-to-migrate-ldap-database-schema-configuration-to-other-machine

=== Step 1: Export configuration trees and database ===

'''From old provider (`vela`)'''
<pre>
sudo slapcat -n 0 -l ldap_config_vela.ldif
sudo slapcat -n 1 -l ldap_data_vela.ldif
</pre>

'''From old consumer (`libra`)'''
<pre>
sudo slapcat -n 0 -l ldap_config_libra.ldif
</pre>

=== Step 2: Save certificates ===

'''vela:'''
<pre>
/etc/ssl/certs/openldap.pem
/etc/ldap/grus_slapd_cert.pem
/etc/ldap/grus_slapd_key.pem
</pre>

'''libra:'''
<pre>
/etc/ssl/certs/openldap.pem
/etc/ldap/phoenix_slapd_cert.pem
/etc/ldap/phoenix_slapd_key.pem
</pre>

=== Step 3: Set up new provider ===

'''Install packages'''
<pre>
sudo apt install slapd ldap-utils
</pre>

'''Stop slapd and remove existing configuration and data'''
<pre>
sudo systemctl stop slapd
sudo rm -rf /etc/ldap/slapd.d/*
sudo rm -rf /var/lib/ldap/*
</pre>

'''Import configuration and data'''
<pre>
sudo slapadd -n 0 -F /etc/ldap/slapd.d -l /path/to/ldap_config_vela.ldif
sudo slapadd -n 1 -l /path/to/ldap_data_vela.ldif
</pre>

'''Set ownership of /etc/ldap/slapd.d and /var/lib/ldap to openldap'''

'''Restore certificates'''
<pre>
lrwxrwxrwx 1 root root 45 Jul 10 2023 /etc/ssl/certs/openldap.pem -> /usr/local/share/ca-certificates/openldap.pem
-rw-r--r-- 1 root root 1614 Jul 10 2023 /etc/ldap/grus_slapd_cert.pem
-rw-r----- 1 root openldap 8170 Jul 10 2023 /etc/ldap/grus_slapd_key.pem
</pre>

'''Start slapd'''
<pre>
sudo systemctl start slapd
</pre>

'''Verify'''
<pre>
ldapsearch -H ldap://localhost -x -b dc=sternwarte,dc=uni-erlangen,dc=de
</pre>

=== Step 4: Set up new consumer for replication ===

'''Install packages'''
<pre>
sudo apt install slapd ldap-utils
</pre>

'''Stop slapd and remove existing configuration and data'''
<pre>
sudo systemctl stop slapd
sudo rm -rf /etc/ldap/slapd.d/*
sudo rm -rf /var/lib/ldap/*
</pre>

'''Import configuration'''
<pre>
sudo slapadd -n 0 -F /etc/ldap/slapd.d -l /path/to/ldap_config_libra.ldif
</pre>

'''Set ownership of /etc/ldap/slapd.d and /var/lib/ldap to openldap'''

'''Restore certificates'''
<pre>
lrwxrwxrwx 1 root root 45 May 13 2023 /etc/ssl/certs/openldap.pem -> /usr/local/share/ca-certificates/openldap.crt
-rw-r--r-- 1 root root 1619 Jul 11 2023 /etc/ldap/phoenix_slapd_cert.pem
-rw-r--r-- 1 root root 8180 Jul 11 2023 /etc/ldap/phoenix_slapd_key.pem
</pre>

'''Start slapd'''
<pre>
sudo systemctl start slapd
</pre>

'''Check replication'''
<pre>
journalctl -fu slapd
</pre>

'''Verify'''
<pre>
ldapsearch -H ldap://localhost -x -b dc=sternwarte,dc=uni-erlangen,dc=de
</pre>

=== Step 5: Check dependent services ===

* ldap backup
* Wiki
* Internal webpage
* Gitlab
* phpLDAPadmin (web interface)
* `who_takes_the_minutes`

LDAP

2025-06-28T13:20:47Z

Lorenz:

[[Category:Admin]]
= LDAP =
The LDAP server at Remeis is running on vela. The service itself is called ''slapd''. A backup LDAP server is running on libra.

Every interaction with the ''slapd'' requires root access.

== Where LDAP is used ==
LDAP is not only used for the authentication to login into the variety of machines at Remeis. Also a lot of other services/scripts use ldap:

* This wiki
* The internal webpage
* [[GitLab]]
* [[#phpLDAPadmin|phpLDAPadmin]]
* The <code>who_takes_the_minutes.pl</code> script of the X-ray group
* The ''cgnotifier'' for the [[cgroups]]

== Configuration ==

=== Config files ===
The main LDAP configuration file is <code>/etc/ldap.conf</code>. Note that this is not the default location for the configuration file. Therefore the defaults for the slapd are changed in <code>/etc/default/slapd</code>, see the entry <code>SLAPD_CONF</code>. The <code>/etc/ldap.conf</code> is also present on all the clients and specifies via IP-Address which LDAP server to contact for authentication. The LDAP requests are then handled on taurus by the ''slapd'' which is configured via <code>/etc/ldap/slapd.conf</code>.

=== phpLDAPadmin ===
phpLDAPadmin is a web interface based on [https://de.wikipedia.org/wiki/PHP PHP] which allows simple modifications to the directory for example to [[:Category:Admin#Add new Users|add new users]] or change group memberships. It is accessible via the [https://www.sternwarte.uni-erlangen.de/intern/phpldapadmin/ internal webpages] and only out of the network at the Remeis observatory.

==== Configuration of phpLADPadmin ====
The configuration files for phpLDAPadmin are located in <code>/etc/phpldapadmin/</code> on the webserver, in this case [[cetus]]. The important file is <code>config.php</code> which holds information about which LDAP servers can be queried, in this case [[taurus]].

== Starting/Stopping the service ==
The slapd can be stopped via [https://de.wikipedia.org/wiki/Systemd systemd]:
<pre>
systemctl stop slapd
</pre>
'''Important:''' If you do so no authentication on the whole cluster is possible anymore. You can not open a new shell on any host until you start the service again!

Starting the ''slapd'':
<pre>
systemctl start slapd
</pre>
You also can have a look at the output produced by the running service via
<pre>
systemctl status slapd
</pre>

== Database ==
The [https://en.wikipedia.org/wiki/Berkeley_DB Berkeley DB] containing all the active directory information is located at <code>/var/lib/ldap</code>. Files in this directory must not be touched manually in any way. The only secure way to see the content of the database is by using ''slapcat''. For example
<pre>
slapcat -f /etc/ldap/slapd.conf
</pre>
will show all entries of the database.

== Backup ==
Each night the database is dumped to <code>/data/system/backup/ldap/</code> via a cronjob in <code>/etc/cron.d/ldap_backup</code>. Also a tarball of the ''slapd'' and <code>ldap.conf</code> is created there. All backups older than 14 days are deleted.

== Migration ==

See also https://serverfault.com/questions/730088/how-to-migrate-ldap-database-schema-configuration-to-other-machine

=== Step 1: Export configuration trees and database ===

'''From old provider (`vela`)'''
<pre>
sudo slapcat -n 0 -l ldap_config_vela.ldif
sudo slapcat -n 1 -l ldap_data_vela.ldif
</pre>

'''From old consumer (`libra`)'''
<pre>
sudo slapcat -n 0 -l ldap_config_libra.ldif
</pre>

=== Step 2: Save certificates ===

'''vela:'''
<pre>
/etc/ssl/certs/openldap.pem
/etc/ldap/grus_slapd_cert.pem
/etc/ldap/grus_slapd_key.pem
</pre>

'''libra:'''
<pre>
/etc/ssl/certs/openldap.pem
/etc/ldap/grus_slapd_cert.pem
/etc/ldap/grus_slapd_key.pem
</pre>

=== Step 3: Set up new provider ===

'''Install packages'''
<pre>
sudo apt install slapd ldap-utils
</pre>

'''Stop slapd and remove existing configuration and data'''
<pre>
sudo systemctl stop slapd
sudo rm -rf /etc/ldap/slapd.d/*
sudo rm -rf /var/lib/ldap/*
</pre>

'''Import configuration and data'''
<pre>
sudo slapadd -n 0 -F /etc/ldap/slapd.d -l /path/to/ldap_config_vela.ldif
sudo slapadd -n 1 -l /path/to/ldap_data_vela.ldif
</pre>

'''Set ownership of /etc/ldap/slapd.d and /var/lib/ldap to openldap'''

'''Restore certificates'''
<pre>
lrwxrwxrwx 1 root root 45 Jul 10 2023 /etc/ssl/certs/openldap.pem -> /usr/local/share/ca-certificates/openldap.pem
-rw-r--r-- 1 root root 1614 Jul 10 2023 /etc/ldap/grus_slapd_cert.pem
-rw-r----- 1 root openldap 8170 Jul 10 2023 /etc/ldap/grus_slapd_key.pem
</pre>

'''Start slapd'''
<pre>
sudo systemctl start slapd
</pre>

'''Verify'''
<pre>
ldapsearch -H ldap://localhost -x -b dc=sternwarte,dc=uni-erlangen,dc=de
</pre>

=== Step 4: Set up new consumer for replication ===

'''Install packages'''
<pre>
sudo apt install slapd ldap-utils
</pre>

'''Stop slapd and remove existing configuration and data'''
<pre>
sudo systemctl stop slapd
sudo rm -rf /etc/ldap/slapd.d/*
sudo rm -rf /var/lib/ldap/*
</pre>

'''Import configuration'''
<pre>
sudo slapadd -n 0 -F /etc/ldap/slapd.d -l /path/to/ldap_config_libra.ldif
</pre>

'''Set ownership of /etc/ldap/slapd.d and /var/lib/ldap to openldap'''

'''Restore certificates'''
<pre>
lrwxrwxrwx 1 root root 45 May 13 2023 /etc/ssl/certs/openldap.pem -> /usr/local/share/ca-certificates/openldap.crt
-rw-r--r-- 1 root root 1619 Jul 11 2023 /etc/ldap/phoenix_slapd_cert.pem
-rw-r--r-- 1 root root 8180 Jul 11 2023 /etc/ldap/phoenix_slapd_key.pem
</pre>

'''Start slapd'''
<pre>
sudo systemctl start slapd
</pre>

'''Check replication'''
<pre>
journalctl -fu slapd
</pre>

'''Verify'''
<pre>
ldapsearch -H ldap://localhost -x -b dc=sternwarte,dc=uni-erlangen,dc=de
</pre>

=== Step 5: Check dependent services ===

* ldap backup
* Wiki
* Internal webpage
* Gitlab
* phpLDAPadmin (web interface)
* `who_takes_the_minutes`

Admin

2024-02-28T15:10:18Z

Lorenz:

===== Remeis Admin-Page =====

This page is only internally visible to the Admins.

==== Lab Course ====

* Before the lab course:
** check the PCs in the Meridian building:
*** they should all be functional, broken ones should be replaced
*** in total we should have about 10 computers available for the students
** [[setup prakti|Setup the prakti accounts]]
* [[Computer_Introduction|Introduction to Computers/Linux for Lab Students ]]

==== Serendipitous Issues ====

* [[Login Problems|Typical login problems]]
* [[Unmet Dependencies|''unmet dependencies'' issue in apt-get]]
* [[Overflow Filesystem|overflow file system]]

==== Add new Users ====
* Go to the remeis internal homepage -> admin -> LDAP
* Fill out the necessary fields, including a valid email address. If possible, also fill out the fields for room and telephone number.
* Log into LDAP ( https://www.sternwarte.uni-erlangen.de/phpldapadmin/), go to import and copy the text of the previous step. '''Important''': if the user is external, "current" in the first line has to be changed to "external"
* set the password of the user: Use the LDAP query <code>ldappasswd -H ldap://vela -x -D "cn=admin,dc=sternwarte,dc=uni-erlangen,dc=de" -W -S "uid={USERNAME},ou=current,ou=People,dc=sternwarte,dc=uni-erlangen,dc=de"</code> while obviously adjusting the LDAP dn.
* log in as ubuntuadmin on libra and create the home directory like that: <code>sudo mkdir /exports/disk1/{USERNAME} && sudo chown {USERNAME}:remeis /exports/disk1/{USERNAME}</code>
* Set the quota (on libra), using a prototype which has normal quota <code>sudo edquota -p [prototype] [username]</code> (normal Quota is 8GB softlimit and 12GB hardlimit; it can be manually edited/shown with edquota -u user)
* Add the default cshrc to /home/username/.cshrc
* If desired (in most cases), create a folder for the user at ''/userdata/data/username'' and adjust the permissions with <code>sudo chown username:remeis /userdata/data/username</code>
* Send Email to admin about the new user

==== Running Software / Updates / Setups ====

In this section a selection of services and their current configuration is described.

* [[CUPS| CUPS]] (Printing Service)
* [[Virtual Boxes| Virtual Boxes]]

[[Category:Admin]]

Setup prakti accounts

2023-08-25T11:39:59Z

Lorenz:

[[Category:Admin]]

==== Setup prakti accounts ====

Shortly '''before''' a new lab course begins, initialize the prakti accounts:
* login as ubuntuadmin on the home server libra: <pre>ssh ubuntuadmin@libra</pre>
* become root: <pre>sudo su</pre>
* go to /exports/disk1/praktikum/intern/setup
* run the script setup: <pre>./setup</pre> This script will rsync the template prakti directory to the 21 prakti home directories. It will also remove anything from the prakti home directories not present in the template
* login as ubuntuadmin on libra and set new passwords for the prakti accounts:
** create a new random password, e.g. using http://passwordsgenerator.net/
** set the password: <pre>ldappasswd -H ldap://vela -x -D "cn=admin,dc=sternwarte,dc=uni-erlangen,dc=de" -W -S "uid=USERNAME,ou=Praktikum,ou=People,dc=sternwarte,dc=uni-erlangen,dc=de"</pre> while adjusting USERNAME to the corresponding prakti account.
** note the password in a file
** do the above for all prakti accounts (as many as needed). Use different passwords for every account.
** notify all users at remeis that the accounts have been setup and include the new passwords

'''After''' a block of the lab course is finished, you need to backup the accounts:
* get confirmation from Jörn, Uli, or Manami that all students are finished and the reports have been submitted.
* get the PDFs of the final protocols of each group and save them in <pre>/home/praktikum/intern/protocols_archive/</pre>
* backup the prakti accounts:
** login as ubuntuadmin on the home server libra
** become root
** rsync the prakti accounts to your PC, e.g.,<pre>rsync -av /exports/disk1/praktikum/prakti* kreykenbohm@orion:/scratch1/DVD-Burner</pre>
** check how much disk space is used by the accounts.
** if more than ~4 GB are used, remove unneeded files from the prakti accounts, i.e. firefox/chrome caches, Download folders etc.
** also add the final protocols of each group to the backup
** get as many blank DVDs as needed
** backup the accounts to the DVDs, e.g. using Xfburn
** label the DVDs appropriately (year, spring/fall, block, and disk number (if applicable))
** get jewel cases for the DVDs from the closet in the server room
** store the DVDs in closet to the right in the meeting room

'''Note''': the timing is especially important between the first and second block of a lab course. You have very little time to get confirmation that all groups of the first block are finished, back up all accounts, and initialize the accounts for the second block. Sometimes (if some students are not finished in time) the setup can only be done in the morning of the day when the next block begins...

'''Note''': in some rare cases a group does not finish before the next block begins. In this case do '''not''' initialize all accounts using the setup script, but keep the account of the delayed group and only initialze the other accounts.

Setup prakti accounts

2023-08-24T10:41:37Z

Lorenz:

[[Category:Admin]]

==== Setup prakti accounts ====

Shortly '''before''' a new lab course begins, initialize the prakti accounts:
* login as ubuntuadmin on the home server libra: <pre>ssh ubuntuadmin@libra</pre>
* become root: <pre>sudo su</pre>
* go to /exports/disk1/praktikum/intern/setup
* run the script setup: <pre>./setup</pre> This script will rsync the template prakti directory to the 21 prakti home directories. It will also remove anything from the prakti home directories not present in the template
* login as ubuntuadmin on libra and set new passwords for the prakti accounts:
** create a new random password, e.g. using http://passwordsgenerator.net/
** set the password: <pre>ldappasswd -H ldap://grus -x -D "cn=admin,dc=sternwarte,dc=uni-erlangen,dc=de" -W -S "uid=USERNAME,ou=Praktikum,ou=People,dc=sternwarte,dc=uni-erlangen,dc=de"</pre> while adjusting USERNAME to the corresponding prakti account.
** note the password in a file
** do the above for all prakti accounts (as many as needed). Use different passwords for every account.
** notify all users at remeis that the accounts have been setup and include the new passwords

'''After''' a block of the lab course is finished, you need to backup the accounts:
* get confirmation from Jörn, Uli, or Manami that all students are finished and the reports have been submitted.
* get the PDFs of the final protocols of each group and save them in <pre>/home/praktikum/intern/protocols_archive/</pre>
* backup the prakti accounts:
** login as ubuntuadmin on the home server libra
** become root
** rsync the prakti accounts to your PC, e.g.,<pre>rsync -av /exports/disk1/praktikum/prakti* kreykenbohm@orion:/scratch1/DVD-Burner</pre>
** check how much disk space is used by the accounts.
** if more than ~4 GB are used, remove unneeded files from the prakti accounts, i.e. firefox/chrome caches, Download folders etc.
** also add the final protocols of each group to the backup
** get as many blank DVDs as needed
** backup the accounts to the DVDs, e.g. using Xfburn
** label the DVDs appropriately (year, spring/fall, block, and disk number (if applicable))
** get jewel cases for the DVDs from the closet in the server room
** store the DVDs in closet to the right in the meeting room

'''Note''': the timing is especially important between the first and second block of a lab course. You have very little time to get confirmation that all groups of the first block are finished, back up all accounts, and initialize the accounts for the second block. Sometimes (if some students are not finished in time) the setup can only be done in the morning of the day when the next block begins...

'''Note''': in some rare cases a group does not finish before the next block begins. In this case do '''not''' initialize all accounts using the setup script, but keep the account of the delayed group and only initialze the other accounts.

Admin

2023-08-14T13:36:53Z

Lorenz:

===== Remeis Admin-Page =====

This page is only internally visible to the Admins.

==== Lab Course ====

* Before the lab course:
** check the PCs in the Meridian building:
*** they should all be functional, broken ones should be replaced
*** in total we should have about 10 computers available for the students
** [[setup prakti|Setup the prakti accounts]]
* [[Computer_Introduction|Introduction to Computers/Linux for Lab Students ]]

==== Serendipitous Issues ====

* [[Login Problems|Typical login problems]]
* [[Unmet Dependencies|''unmet dependencies'' issue in apt-get]]
* [[Overflow Filesystem|overflow file system]]

==== Add new Users ====
* Go to the remeis internal homepage -> admin -> LDAP
* Fill out the necessary fields, including a valid email address. If possible, also fill out the fields for room and telephone number.
* Log into LDAP ( https://www.sternwarte.uni-erlangen.de/phpldapadmin/), go to import and copy the text of the previous step. '''Important''': if the user is external, "current" in the first line has to be changed to "external"
* set the password of the user: Use the LDAP query <code>ldappasswd -H ldap://vela -x -D "cn=admin,dc=sternwarte,dc=uni-erlangen,dc=de" -W -S "uid={USERNAME},ou=current,ou=People,dc=sternwarte,dc=uni-erlangen,dc=de"</code> while obviously adjusting the LDAP dn.
* log in as ubuntuadmin on libra and create the home directory like that: <code>sudo mkdir /exports/disk1/{USERNAME} && sudo chown {USERNAME}:remeis /exports/disk1/{USERNAME}</code>
* Set the quota (on libra), using a prototype which has normal quota <code>sudo edquota -p [prototype] [username]</code> (normal Quota is 8GB softlimit and 12GB hardlimit; it can be manually edited/shown with edquota -u user)
* Add the file for automatic forwarding of system emails: <code>/home/username/.forward</code> which should just contain the mail address of the new user
* Add the default cshrc to /home/username/.cshrc
* If desired (in most cases), create a folder for the user at ''/userdata/data/username'' and adjust the permissions with <code>sudo chown username:remeis /userdata/data/username</code>
* Send Email to admin about the new user

==== Running Software / Updates / Setups ====

In this section a selection of services and their current configuration is described.

* [[CUPS| CUPS]] (Printing Service)
* [[Virtual Boxes| Virtual Boxes]]

[[Category:Admin]]

Skivergnuegen 2023

2022-12-31T15:11:56Z

Lorenz:

'''Remeis Skifahren 2023''' The same procedure as every year ;-)
Hier werden die wichtigsten organisatorischen Dinge festgehalten. Jeder darf hier gerne editieren; wer keinen Account für das Wiki hat, muss sich bitte an jemanden wenden, der Zugang hat.

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

== Allgemeine Infos ==

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

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

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

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

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

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

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

== Fahrer ==
Fahrer können sich hier eintragen und Eckdaten angeben. Diejenige, die mitfahren möchten, sprechen sich mit den Fahrern ab und tragen sich ebenfalls ein. Klärt bitte auch die Gepäcklage, ggf. kann ein anderer Fahrer z.B. Skiausrüstung mitnehmen.

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

{| class="wikitable"
! scope="col" | Fahrer
! scope="col" | # Plätze
! scope="col" | Anreise
! scope="col" | Mitfahrer Anreise
! scope="col" | Abreise
! scope="col" | Mitfahrer Abreise
! scope="col" | Skimitnahme
! scope="col" | Kommentar
|-
|Eva
|0(3)
|Samstag
|Steffen+Christian
|Samstag?
|Steffen+Christian
|eigene ja
|Auto ist voll
|-
|Max
|0(3)
|Samstag
|Jakob+Katya
|Samstag
|Jakob+Katya
|eigene ja
|Auto ist voll
|-

|-

|-

|-

|-
|}

== Schwarzes Brett ==

=== Essen ===
Hier gibt's den Essensplan, soweit übernommen von den letzten Jahren. Da wir sehr viele Leute sind, sollten wir wieder vorab grob planen, was wir kochen wollen. Wir können einige Dinge in Deutschland besorgen und mitnehmen, es gib aber auch einen nahe gelegen Supermarkt. Generelle Dinge, wie z.B. Gewürze oder Aufstriche für Frühstücksbrötchen könnte man auch mitbringen.

Wer Kochvorschläge oder andere Ideen hat, gerne unten eintragen und kommentieren. Bedenkt, dass die Zubereitung (relativ) einfach sein sollte. Da sich die Liste in den letzten Jahren gut bewaehrt hat, behalten wir sie bei, aber die Reihenfolge/Tage kann man sicher noch hin und her bewegen. Einige (wenige) Sachen müssen wir dann manchmal trotzdem noch beim Spar kaufen, da ja auch der Kühlschrank nur begrenzt Platz hat.

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

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

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

=== Alkohol/Party ===

=== Spiele ===

Immer lustig sind gemeinsame Spieleabende. Also, wer im Besitz von Gesellschaftsspielen ist, bringt diese gerne mit! Um eine Übersicht zu bekommen auch bitte hier eintragen:

''* Spiele hier eintragen''

=== Sonstiges ===

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

[[Category:Internal]]

Category:Admin

2022-04-26T10:29:18Z

Lorenz:

[[Category:Admin]]

===== Remeis Admin-Page =====

This page is only internally visible to the Admins.

==== Lab Course ====

* Before the lab course:
** check the PCs in the Meridian building:
*** they should all be functional, broken ones should be replaced
*** in total we should have about 10 computers available for the students
** [[setup prakti|Setup the prakti accounts]]
* [[Computer_Introduction|Introduction to Computers/Linux for Lab Students ]]

==== Serendipitous Issues ====

* [[Login Problems|Typical login problems]]
* [[Unmet Dependencies|''unmet dependencies'' issue in apt-get]]
* [[Overflow Filesystem|overflow file system]]

==== Add new Users ====
* Go to the remeis internal homepage -> admin -> LDAP
* Fill out the necessary fields, including a valid email address. If possible, also fill out the fields for room and telephone number.
* Log into LDAP ( https://www.sternwarte.uni-erlangen.de/phpldapadmin/), go to import and copy the text of the previous step. '''Important''': if the user is external, "current" in the first line has to be changed to "external"
* set the password of the user: Use the LDAP query <code>ldappasswd -H ldap://grus -x -D "cn=admin,dc=sternwarte,dc=uni-erlangen,dc=de" -W -S "uid={USERNAME},ou=current,ou=People,dc=sternwarte,dc=uni-erlangen,dc=de"</code> while obviously adjusting the LDAP dn.
* log in as ubuntuadmin on taurus and create the home directory like that: <code>sudo mkdir /exports/disk1/{USERNAME} && sudo chown {USERNAME}:remeis /exports/disk1/{USERNAME}</code>
* Set the quota (on taurus), using a prototype which has normal quota <code>sudo edquota -p [prototype] [username]</code> (normal Quota is 8GB softlimit and 12GB hardlimit; it can be manually edited/shown with edquota -u user)
* Add the file for automatic forwarding of system emails: <code>/home/username/.forward</code> which should just contain the mail address of the new user
* Add the default cshrc to /home/username/.cshrc
* If desired (in most cases), create a folder for the user at ''/userdata/data/username'' and adjust the permissions with <code>sudo chown username:remeis /userdata/data/username</code>
* Send Email to admin about the new user

==== Running Software / Updates / Setups ====

In this section a selection of services and their current configuration is described.

* [[CUPS| CUPS]] (Printing Service)
* [[Virtual Boxes| Virtual Boxes]]

Category:Admin

2022-04-26T10:27:01Z

Lorenz:

[[Category:Admin]]

===== Remeis Admin-Page =====

This page is only internally visible to the Admins.

==== Lab Course ====

* Before the lab course:
** check the PCs in the Meridian building:
*** they should all be functional, broken ones should be replaced
*** in total we should have about 10 computers available for the students
** [[setup prakti|Setup the prakti accounts]]
* [[Computer_Introduction|Introduction to Computers/Linux for Lab Students ]]

==== Serendipitous Issues ====

* [[Login Problems|Typical login problems]]
* [[Unmet Dependencies|''unmet dependencies'' issue in apt-get]]
* [[Overflow Filesystem|overflow file system]]

==== Add new Users ====
* Go to the remeis internal homepage -> admin -> LDAP
* Fill out the necessary fields, including a valid email address. If possible, also fill out the fields for room and telephone number.
* Log into LDAP ( https://www.sternwarte.uni-erlangen.de/phpldapadmin/), go to import and copy the text of the previous step. '''Important''': if the user is external, "current" in the first line has to be changed to "external"
* set the password of the user: Use the LDAP query <code>ldappasswd -H ldap://grus -x -D "cn=admin,dc=sternwarte,dc=uni-erlangen,dc=de" -W -S "uid={USERNAME},ou=current,ou=People,dc=sternwarte,dc=uni-erlangen,dc=de"</code> while obviously adjusting the LDAP dn.
* log in as ubuntuadmin on taurus and create the home directory like that: <code>sudo mkdir /exports/disk1/{USERNAME} && sudo chown {USERNAME}:remeis /exports/disk1/{USERNAME}</code>
* Set the quota (on taurus), using a prototype which has normal quota <code>sudo edquota -p [prototype] [username]</code> (normal Quota is 8GB softlimit and 12GB hardlimit; it can be manually edited/shown with edquota -u user)
* Add the file for automatic forwarding of system emails: <code>/home/username/.forward</code> which should just contain the mail address of the new user
* if desired (in most cases), create a folder for the user at ''/userdata/data/username'' and adjust the permissions with <code>sudo chown username:remeis /userdata/data/username</code>
* send Email to admin about the new user

==== Running Software / Updates / Setups ====

In this section a selection of services and their current configuration is described.

* [[CUPS| CUPS]] (Printing Service)
* [[Virtual Boxes| Virtual Boxes]]

Skivergnuegen 2022

2022-01-13T11:18:44Z

Lorenz: /* Fahrer */

'''Remeis Skifahren 2022''' The same procedure as every year ;-)
Hier werden die wichtigsten organisatorischen Dinge festgehalten. Jeder darf hier gerne editieren; wer keinen Account für das Wiki hat, muss sich bitte an jemanden wenden, der Zugang hat.

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

== Allgemeine Infos ==

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

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

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

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

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

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

|-
! scope="row" | 3-er
| Thomas
|-
! scope="row" | 4-er
|
|-
! scope="row" | 5-er
| Eva, Steffen, Nela, Ohle, Flo?
|}

== Fahrer ==
Fahrer können sich hier eintragen und Eckdaten angeben. Diejenige, die mitfahren möchten, sprechen sich mit den Fahrern ab und tragen sich ebenfalls ein. Klärt bitte auch die Gepäcklage, ggf. kann ein anderer Fahrer z.B. Skiausrüstung mitnehmen.

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

{| class="wikitable"
! scope="col" | Fahrer
! scope="col" | # Plätze
! scope="col" | Anreise
! scope="col" | Mitfahrer Anreise
! scope="col" | Abreise
! scope="col" | Mitfahrer Abreise
! scope="col" | Skimitnahme
! scope="col" | Kommentar
|-
|Eva
|0(3)
|Samstag
|Steffen+Christian
|Samstag?
|Steffen+Christian
|eigene ja
|Auto is voll
|-
|Johannes
|1+x(2+x?)
|Samstag
|
|Samstag?
|
|ja
|Mietwagen, daher noch x Plätze mehr möglich
|-
|Flo
|3(4)
|Samstag
|
|Samstag?
|
|ja
|fährt von Minga
|-
|Max
|4
|Samstag
|Katya, Jakob, Philipp
|Samstag?
|Katya, Jakob, Philipp
|ja
|voll, fährt von Erlangen
|-
|}

== Schwarzes Brett ==

=== Essen ===
Hier gibt's den Essensplan, soweit übernommen von den letzten Jahren. Da wir sehr viele Leute sind, sollten wir wieder vorab grob planen, was wir kochen wollen. Wir können einige Dinge in Deutschland besorgen und mitnehmen, es gib aber auch einen nahe gelegen Supermarkt. Generelle Dinge, wie z.B. Gewürze oder Aufstriche für Frühstücksbrötchen könnte man auch mitbringen.

Wer Kochvorschläge oder andere Ideen hat, gerne unten eintragen und kommentieren. Bedenkt, dass die Zubereitung (relativ) einfach sein sollte. Da sich die Liste in den letzten Jahren gut bewaehrt hat, behalten wir sie bei, aber die Reihenfolge/Tage kann man sicher noch hin und her bewegen. Einige (wenige) Sachen müssen wir dann manchmal trotzdem noch beim Spar kaufen, da ja auch der Kühlschrank nur begrenzt Platz hat.

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

Einkaufsliste hier: https://docs.google.com/document/d/166b_mIXxmoAgcv1upIGremd_36E1fmwwxsQADP2uEv8/

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

=== Alkohol/Party ===

=== Spiele ===

Immer lustig sind gemeinsame Spieleabende. Also, wer im Besitz von Gesellschaftsspielen ist, bringt diese gerne mit! Um eine Übersicht zu bekommen auch bitte hier eintragen:

''* Spiele hier eintragen''

=== Sonstiges ===

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

[[Category:Internal]]

Setup prakti accounts

2021-04-09T13:31:47Z

Lorenz:

[[Category:Admin]]

==== Setup prakti accounts ====

Shortly '''before''' a new lab course begins, initialize the prakti accounts:
* login as ubuntuadmin on the home server taurus: <pre>ssh ubuntuadmin@taurus</pre>
* become root: <pre>sudo su</pre>
* go to /exports/disk1/praktikum/intern/setup
* run the script setup: <pre>./setup</pre> This script will rsync the template prakti directory to the 21 prakti home directories. It will also remove anything from the prakti home directories not present in the template
* login as ubuntuadmin on taurus and set new passwords for the prakti accounts:
** create a new random password, e.g. using http://passwordsgenerator.net/
** set the password: <pre>ldappasswd -H ldap://grus -x -D "cn=admin,dc=sternwarte,dc=uni-erlangen,dc=de" -W -S "uid=USERNAME,ou=Praktikum,ou=People,dc=sternwarte,dc=uni-erlangen,dc=de"</pre> while adjusting USERNAME to the corresponding prakti account.
** note the password in a file
** do the above for all prakti accounts (as many as needed). Use different passwords for every account.
** notify all users at remeis that the accounts have been setup and include the new passwords

'''After''' a block of the lab course is finished, you need to backup the accounts:
* get confirmation from Jörn, Uli, or Manami that all students are finished and the reports have been submitted.
* get the PDFs of the final protocols of each group and save them in <pre>/home/praktikum/intern/protocols_archive/</pre>
* backup the prakti accounts:
** login as ubuntuadmin on the home server taurus
** become root
** rsync the prakti accounts to your PC, e.g.,<pre>rsync -av /exports/disk1/praktikum/prakti* kreykenbohm@orion:/scratch1/DVD-Burner</pre>
** check how much disk space is used by the accounts.
** if more than ~4 GB are used, remove unneeded files from the prakti accounts, i.e. firefox/chrome caches, Download folders etc.
** also add the final protocols of each group to the backup
** get as many blank DVDs as needed
** backup the accounts to the DVDs, e.g. using Xfburn
** label the DVDs appropriately (year, spring/fall, block, and disk number (if applicable))
** get jewel cases for the DVDs from the closet in the server room
** store the DVDs in closet to the right in the meeting room

'''Note''': the timing is especially important between the first and second block of a lab course. You have very little time to get confirmation that all groups of the first block are finished, back up all accounts, and initialize the accounts for the second block. Sometimes (if some students are not finished in time) the setup can only be done in the morning of the day when the next block begins...

'''Note''': in some rare cases a group does not finish before the next block begins. In this case do '''not''' initialize all accounts using the setup script, but keep the account of the delayed group and only initialze the other accounts.

Setup prakti accounts

2021-04-09T12:21:04Z

Lorenz:

[[Category:Admin]]

==== Setup prakti accounts ====

Shortly '''before''' a new lab course begins, initialize the prakti accounts:
* login as ubuntuadmin on the home server taurus: <pre>ssh ubuntuadmin@taurus</pre>
* become root: <pre>sudo su</pre>
* go to /exports/disk1/praktikum/intern/setup
* run the script setup: <pre>./setup</pre> This script will rsync the template prakti directory to the 21 prakti home directories. It will also remove anything from the prakti home directories not present in the template
* login as ubuntuadmin on taurus and set new passwords for the prakti accounts:
** create a new random password, e.g. using http://passwordsgenerator.net/
** set the password: <pre>ldappasswd -H ldap://grus -x -D "cn=admin,dc=sternwarte,dc=uni-erlangen,dc=de" -W -S "uid=USERNAME,ou=Praktikum,ou=People,dc=sternwarte,dc=uni-erlangen,dc=de"</pre> while adjusting USERNAME to the corresponding prakti account.
** note the password in a file
** do the above for all prakti accounts (as many as needed). Use different passwords for every account.
** notify all users at remeis that the accounts have been setup and include the new passwords

'''After''' a block of the lab course is finished, you need to backup the accounts:
* get confirmation from Jörn, Uli, or Manami that all students are finished and the reports have been submitted.
* backup the prakti accounts:
** login as ubuntuadmin on the home server taurus
** become root
** rsync the prakti accounts to your PC, e.g.,<pre>rsync -av /exports/disk1/praktikum/prakti* kreykenbohm@orion:/scratch1/DVD-Burner</pre>
** check how much disk space is used by the accounts.
** if more than ~4 GB are used, remove unneeded files from the prakti accounts, i.e. firefox/chrome caches, Download folders etc.
** get the PDFs of the final protocols of each group and add them to the backup
** get as many blank DVDs as needed
** backup the accounts to the DVDs, e.g. using Xfburn
** label the DVDs appropriately (year, spring/fall, block, and disk number (if applicable))
** get jewel cases for the DVDs from the closet in the server room
** store the DVDs in closet to the right in the meeting room

'''Note''': the timing is especially important between the first and second block of a lab course. You have very little time to get confirmation that all groups of the first block are finished, back up all accounts, and initialize the accounts for the second block. Sometimes (if some students are not finished in time) the setup can only be done in the morning of the day when the next block begins...

'''Note''': in some rare cases a group does not finish before the next block begins. In this case do '''not''' initialize all accounts using the setup script, but keep the account of the delayed group and only initialze the other accounts.

Setup prakti accounts

2021-04-09T10:07:01Z

Lorenz:

[[Category:Admin]]

==== Setup prakti accounts ====

Shortly '''before''' a new lab course begins, initialize the prakti accounts:
* login as ubuntuadmin on the home server taurus: <pre>ssh ubuntuadmin@taurus</pre>
* become root: <pre>sudo su</pre>
* go to /home/praktikum/intern/setup
* run the script setup: <pre>./setup</pre> This script will rsync the template prakti directory to the 7 prakti home directories. It will also remove anything from the prakti home directories not present in the template
* login as ubuntuadmin on taurus and set new passwords for the prakti accounts:
** create a new random password, e.g. using http://passwordsgenerator.net/
** set the password: <pre>sudo passwd prakti1</pre>
** note the password in a file
** do the above for all prakti accounts (use different passwords for every account)
** notify all users at remeis that the accounts have been setup and include the new passwords

'''After''' a block of the lab course is finished, you need to backup the accounts:
* get confirmation from Jörn, Uli, or Manami that all students are finished and the reports have been submitted.
* backup the prakti accounts:
** login as ubuntuadmin on the home server taurus
** become root
** rsync the prakti accounts to your PC, e.g.,<pre>rsync -av /exports/disk1/praktikum/prakti* kreykenbohm@orion:/scratch1/DVD-Burner</pre>
** check how much disk space is used by the accounts.
** if more than ~4 GB are used, remove unneeded files from the prakti accounts, i.e. firefox/chrome caches, Download folders etc.
** get the PDFs of the final protocols of each group and add them to the backup
** get as many blank DVDs as needed
** backup the accounts to the DVDs, e.g. using k3b
** label the DVDs appropriately (year, spring/fall, block, and disk number (if applicable))
** get jewel cases for the DVDs from the closet in the server room
** store the DVDs in closet to the right in the meeting room

'''Note''': the timing is especially important between the first and second block of a lab course. You have very little time to get confirmation that all groups of the first block are finished, back up all accounts, and initialize the accounts for the second block. Sometimes (if some students are not finished in time) the setup can only be done in the morning of the day when the next block begins...

'''Note''': in some rare cases a group does not finish before the next block begins. In this case do '''not''' initialize all accounts using the setup script, but keep the account of the delayed group and only initialze the other accounts.

Setup prakti accounts

2021-04-08T12:24:38Z

Lorenz:

[[Category:Admin]]

==== Setup prakti accounts ====

Shortly '''before''' a new lab course begins, initialize the prakti accounts:
* login as ubuntuadmin on the home server taurus: <pre>ssh ubuntuadmin@taurus</pre>
* become root: <pre>sudo su</pre>
* go to /home/praktikum/intern/setup
* run the script setup: <pre>./setup</pre> This script will rsync the template prakti directory to the 7 prakti home directories. It will also remove anything from the prakti home directories not present in the template
* login as ubuntuadmin on taurus and set new passwords for the prakti accounts:
** create a new random password, e.g. using http://passwordsgenerator.net/
** set the password: <pre>sudo passwd prakti1</pre>
** note the password in a file
** do the above for all prakti accounts (use different passwords for every account)
** notify all users at remeis that the accounts have been setup and include the new passwords

'''After''' a block of the lab course is finished, you need to backup the accounts:
* get confirmation from Jörn, Uli, or Manami that all students are finished and the reports have been submitted.
* backup the prakti accounts:
** login as ubuntuadmin on the home server taurus
** become root
** rsync the prakti accounts to your PC, e.g.,<pre>rsync -av /exports/disk1/praktikum/prakti* kreykenbohm@orion:/scratch1/DVD-Burner</pre>
** check how much disk space is used by the accounts.
** if more than ~4 GB are used, remove unneeded files from the prakti accounts, i.e. firefox/chrome caches, Download folders etc.
** get as many blank DVDs as needed
** backup the accounts to the DVDs, e.g. using k3b
** label the DVDs appropriately (year, spring/fall, block, and disk number (if applicable))
** get jewel cases for the DVDs from the closet in the server room
** store the DVDs in closet to the right in the meeting room

'''Note''': the timing is especially important between the first and second block of a lab course. You have very little time to get confirmation that all groups of the first block are finished, back up all accounts, and initialize the accounts for the second block. Sometimes (if some students are not finished in time) the setup can only be done in the morning of the day when the next block begins...

'''Note''': in some rare cases a group does not finish before the next block begins. In this case do '''not''' initialize all accounts using the setup script, but keep the account of the delayed group and only initialze the other accounts.

PhD hat Simon

2021-02-05T13:55:45Z

Lorenz:

Simon's defense is planned in a few weeks.

Biggest problem: How to gather all things to put on the hat.
Idea: People that commute between Bamberg & Erlangen (or pass Erlangen) can deliver things. (Max, Jakob, Ralf, ...)

'''Work things''':
* The "Slurm Snail"
* Photo from Astroplate III conference dinner with Simon, Aakash and David
* HV-stars (maybe one holding a beer??)
* "Blue Giants" in Andromeda
* Guided tours and VHS courses [Ralf]
* Observing (and vacation) in Chile [Ralf]
* violent typing [Ralf]
* Search and replace with a stapler [I have maybe a photo Eugenia]
* Star catalogue query tool

'''Private things''':
* Spruz label
* Bierwanderung (A map of a path with breweries? Maybe the "certificate" with stamps?)
* Whiskey tastings [Ralf]
* Seminars on Fluid Dynamics [Ralf]
* Chartreuse
* Beer brewing
* Skiing? (Skier paper model, artificial snow)

[[Category:Internal]]

Category:Admin

2020-10-23T13:46:53Z

Lorenz:

[[Category:Admin]]

===== Remeis Admin-Page =====

This page is only internally visible to the Admins.

==== Lab Course ====

* Before the lab course:
** check the PCs in the Meridian building:
*** they should all be functional, broken ones should be replaced
*** in total we should have about 10 computers available for the students
** [[setup prakti|Setup the prakti accounts]]
* [[Computer_Introduction|Introduction to Computers/Linux for Lab Students ]]

==== Serendipitous Issues ====

* [[Login Problems|Typical login problems]]
* [[Unmet Dependencies|''unmet dependencies'' issue in apt-get]]
* [[Overflow Filesystem|overflow file system]]

==== Add new Users ====
* Go to the remeis internal homepage -> admin -> LDAP
* Fill out the necessary fields, including a valid email address. If possible, also fill out the fields for room and telephone number.
* Log into LDAP ( https://www.sternwarte.uni-erlangen.de/phpldapadmin/), go to import and copy the text of the previous step. '''Important''': if the user is external, "current" in the first line has to be changed to "external"
* set the password of the user: Use the LDAP query <code>ldappasswd -H ldap://grus -x -D "cn=admin,dc=sternwarte,dc=uni-erlangen,dc=de" -W -S "uid={USERNAME},ou=current,ou=People,dc=sternwarte,dc=uni-erlangen,dc=de"</code> while obviously adjusting the LDAP dn.
* log in as ubuntuadmin on taurus and create the home directory like that: <code>sudo mkdir /exports/disk1/{USERNAME} && sudo chown {USERNAME}:remeis /exports/disk1/{USERNAME}</code>
* Set the quota (on taurus), using a prototype which has normal quota <code>sudo edquota -p [prototype] [username]</code> (normal Quota is 8GB softlimit and 12GB hardlimit; it can be manually edited/shown with edquota -u user)
* Add the file for automatic forwarding of system emails: <code>~/.forward</code> which should just contain the mail address of the new user
* if desired (in most cases), create a folder for the user at ''/userdata/data/[username]'' and adjust the permissions with <code>sudo chown username:remeis username</code>
* send Email to admin about the new user

==== Running Software / Updates / Setups ====

In this section a selection of services and their current configuration is described.

* [[CUPS| CUPS]] (Printing Service)
* [[Virtual Boxes| Virtual Boxes]]

Category:Admin

2020-10-20T10:06:45Z

Lorenz: /* Add new Users */

[[Category:Admin]]

===== Remeis Admin-Page =====

This page is only internally visible to the Admins.

==== Lab Course ====

* Before the lab course:
** check the PCs in the Meridian building:
*** they should all be functional, broken ones should be replaced
*** in total we should have about 10 computers available for the students
** [[setup prakti|Setup the prakti accounts]]
* [[Computer_Introduction|Introduction to Computers/Linux for Lab Students ]]

==== Serendipitous Issues ====

* [[Login Problems|Typical login problems]]
* [[Unmet Dependencies|''unmet dependencies'' issue in apt-get]]
* [[Overflow Filesystem|overflow file system]]

==== Add new Users ====
* Go to the remeis internal homepage -> admin -> LDAP
* Fill out the necessary fields, including a valid email address. If possible, also fill out the fields for room and telephone number.
* Log into LDAP ( https://www.sternwarte.uni-erlangen.de/intern/phpldapadmin/), go to import and copy the text of the previous step. '''Important''': if the user is external, "current" in the first line has to be changed to "external"
* set the password of the user: Use the LDAP query <code>ldappasswd -H ldap://grus -x -D "cn=admin,dc=sternwarte,dc=uni-erlangen,dc=de" -W -S "uid={USERNAME},ou=current,ou=People,dc=sternwarte,dc=uni-erlangen,dc=de"</code> while obviously adjusting the LDAP dn.
* log in as ubuntuadmin on taurus and create the home directory like that: <code>sudo mkdir /exports/disk1/{USERNAME} && sudo chown {USERNAME}:remeis /exports/disk1/{USERNAME}</code>
* Set the quota (on taurus), using a prototype which has normal quota <code>sudo edquota -p [prototype] [username]</code> (normal Quota is 8GB softlimit and 12GB hardlimit; it can be manually edited/shown with edquota -u user)
* Add the file for automatic forwarding of system emails: <code>~/.forward</code> which should just contain the mail address of the new user
* if desired (in most cases), create a folder for the user at ''/userdata/data/[username]'' and adjust the permissions with <code>sudo chown username:remeis username</code>
* send Email to admin about the new user

==== Running Software / Updates / Setups ====

In this section a selection of services and their current configuration is described.

* [[CUPS| CUPS]] (Printing Service)
* [[Virtual Boxes| Virtual Boxes]]

Category:Admin

2020-10-20T10:06:33Z

Lorenz: /* Add new Users */

[[Category:Admin]]

===== Remeis Admin-Page =====

This page is only internally visible to the Admins.

==== Lab Course ====

* Before the lab course:
** check the PCs in the Meridian building:
*** they should all be functional, broken ones should be replaced
*** in total we should have about 10 computers available for the students
** [[setup prakti|Setup the prakti accounts]]
* [[Computer_Introduction|Introduction to Computers/Linux for Lab Students ]]

==== Serendipitous Issues ====

* [[Login Problems|Typical login problems]]
* [[Unmet Dependencies|''unmet dependencies'' issue in apt-get]]
* [[Overflow Filesystem|overflow file system]]

==== Add new Users ====
* Go to the remeis internal homepage -> admin -> LDAP
* Fill out the necessary fields, including a valid email address. If possible, also fill out the fields for room and telephone number.
* Log into LDAP ( https://www.sternwarte.uni-erlangen.de/intern/phpldapadmin/), go to import and copy the text of the previous step. '''Important''': if the user is external, "current" in the first line has to be changed to "external"

* set the password of the user: Use the LDAP query <code>ldappasswd -H ldap://grus -x -D "cn=admin,dc=sternwarte,dc=uni-erlangen,dc=de" -W -S "uid={USERNAME},ou=current,ou=People,dc=sternwarte,dc=uni-erlangen,dc=de"</code> while obviously adjusting the LDAP dn.
* log in as ubuntuadmin on taurus and create the home directory like that: <code>sudo mkdir /exports/disk1/{USERNAME} && sudo chown {USERNAME}:remeis /exports/disk1/{USERNAME}</code>
* Set the quota (on taurus), using a prototype which has normal quota <code>sudo edquota -p [prototype] [username]</code> (normal Quota is 8GB softlimit and 12GB hardlimit; it can be manually edited/shown with edquota -u user)
* Add the file for automatic forwarding of system emails: <code>~/.forward</code> which should just contain the mail address of the new user
* if desired (in most cases), create a folder for the user at ''/userdata/data/[username]'' and adjust the permissions with <code>sudo chown username:remeis username</code>
* send Email to admin about the new user

==== Running Software / Updates / Setups ====

In this section a selection of services and their current configuration is described.

* [[CUPS| CUPS]] (Printing Service)
* [[Virtual Boxes| Virtual Boxes]]

X2Go Remote Desktop

2020-04-24T09:46:57Z

Lorenz:

A remote desktop connection allows you to work with the full desktop, but remotely from home. Currently all desktop computers at Remeis support a remote desktop connection with '''X2Go'''.

=== Installation ===

All you need to do is to install the X2Go Client on your laptop, available for Linux, Mac, and Windows. This page shows how to do this: [https://wiki.x2go.org/doku.php/doc:installation:x2goclient X2Go Client Download and Installation]

=== Usage ===

Start the X2Go Client an click on "New Session"

In the client software you have to specify the following things:
* Host: <desktop-computer>.sternwarte.uni-erlangen.de (fill in <desktop-computer> with the machine you typically use when working at the observatory)
* Login: your remeis username
* Session type: XFCE
* if you have ssh-keys installed, you can also check the box with "try auto login"

This could then look like the following (in case of user dauser on host corona):

[[File:x2goclient_session_example.png|800px]]

Save the session, type in the session name into "Session", click enter and type in your password. This will launch the XFCE environment on the Remeis machine.

[[Category:Working Remotely]]

Setup prakti accounts

2019-08-22T14:42:59Z

Lorenz: /* Setup prakti accounts */

[[Category:Admin]]

==== Setup prakti accounts ====

Shortly '''before''' a new lab course begins, initialize the prakti accounts:
* login as ubuntuadmin on the home server taurus: <pre>ssh ubuntuadmin@taurus</pre>
* become root: <pre>sudo su</pre>
* go to /home/praktikum/intern/setup
* run the script setup: <pre>./setup</pre> This script will rsync the template prakti directory to the 7 prakti home directories. It will also remove anything from the prakti home directories not present in the template
* login as ubuntuadmin on taurus and set new passwords for the prakti accounts:
** create a new random password, e.g. using http://passwordsgenerator.net/
** set the password: <pre>sudo passwd prakti1</pre>
** note the password in a file
** do the above for all prakti accounts (use different passwords for every account)
** notify all users at remeis that the accounts have been setup and include the new passwords

'''After''' a block of the lab course is finished, you need to backup the accounts:
* get confirmation from Jörn, Uli, or Manami that all students are finished and the reports have been submitted.
* backup the prakti accounts:
** login as ubuntuadmin on the home server taurus
** become root
** rsync the prakti accounts to your PC, e.g.,<pre>rsync -av /home/praktikum/prakti* kreykenbohm@orion:/scratch1/DVD-Burner</pre>
** check how much disk space is used by the accounts.
** if more than ~4 GB are used, remove unneeded files from the prakti accounts, i.e. firefox/chrome caches, Download folders etc.
** get as many blank DVDs as needed
** backup the accounts to the DVDs, e.g. using k3b
** label the DVDs appropriately (year, spring/fall, block, and disk number (if applicable))
** get jewel cases for the DVDs from the closet in the server room
** store the DVDs in closet to the right in the meeting room

'''Note''': the timing is especially important between the first and second block of a lab course. You have very little time to get confirmation that all groups of the first block are finished, back up all accounts, and initialize the accounts for the second block. Sometimes (if some students are not finished in time) the setup can only be done in the morning of the day when the next block begins...

'''Note''': in some rare cases a group does not finish before the next block begins. In this case do '''not''' initialize all accounts using the setup script, but keep the account of the delayed group and only initialze the other accounts.

Setup prakti accounts

2019-08-22T14:41:06Z

Lorenz:

[[Category:Admin]]

==== Setup prakti accounts ====

Shortly '''before''' a new lab course begins, initialize the prakti accounts:
* login as ubuntuadmin on the home server taurus: <pre>ssh ubuntuadmin@taurus</pre>
* become root: <pre>sudo su</pre>
* go to /home/praktikum/intern/setup
* run the script setup: <pre>./setup</pre> This script will rsync the template prakti directory to the 7 prakti home directories. It will also remove anything from the prakti home directories not present in the template
* set new passwords for the prakti accounts:
** create a new random password, e.g. using http://passwordsgenerator.net/
** set the password: <pre>sudo passwd prakti1</pre>
** note the password in a file
** do the above for all prakti accounts (use different passwords for every account)
** notify all users at remeis that the accounts have been setup and include the new passwords

'''After''' a block of the lab course is finished, you need to backup the accounts:
* get confirmation from Jörn, Uli, or Manami that all students are finished and the reports have been submitted.
* backup the prakti accounts:
** login as ubuntuadmin on the home server taurus
** become root
** rsync the prakti accounts to your PC, e.g.,<pre>rsync -av /home/praktikum/prakti* kreykenbohm@orion:/scratch1/DVD-Burner</pre>
** check how much disk space is used by the accounts.
** if more than ~4 GB are used, remove unneeded files from the prakti accounts, i.e. firefox/chrome caches, Download folders etc.
** get as many blank DVDs as needed
** backup the accounts to the DVDs, e.g. using k3b
** label the DVDs appropriately (year, spring/fall, block, and disk number (if applicable))
** get jewel cases for the DVDs from the closet in the server room
** store the DVDs in closet to the right in the meeting room

'''Note''': the timing is especially important between the first and second block of a lab course. You have very little time to get confirmation that all groups of the first block are finished, back up all accounts, and initialize the accounts for the second block. Sometimes (if some students are not finished in time) the setup can only be done in the morning of the day when the next block begins...

'''Note''': in some rare cases a group does not finish before the next block begins. In this case do '''not''' initialize all accounts using the setup script, but keep the account of the delayed group and only initialze the other accounts.

PhD hat for Maria

2019-05-16T09:07:54Z

Lorenz: /* building plan */

== PhD Hat for Maria ==

====== list of ideas ======

* colored hair
* shoes and socks of different color
* kids as little thesis helpers
* card/board games
* wiskey

* line measurements (remeis intern poll)
* timing analysis (power spectra)
* constellations

== building plan ==

====== Private ======

* firefighter
** firetruck with hose as tassel : Paper model + cord + nozzle ('''**Max**''')
** a beeper with button to start alarm (Jakob takes a look at this)
* Cycling from Erlangen to Remeis
** ESTW smokestack + canal leading to observatory + bike (with trailer) + figure (maybe fierfighter figure by playmobile?) with colored hair and shoes of different color ('''**Basti**''')
* whiskey (ardberg supernova)

====== Work ======

* Cyg X-1 (Draft Idea: build BH + Clumpy wind {clumps are sheep shaped} [wool & LEDS?] + accretion disk also sheep but colored wool?)
** BH as half sphere (styrofoam size of a tennis ball) ('''**Max**''')
** accretion disk made of colored wool ('''**Katya**''')
** clumpy wind: wool sheep on wire [similar like [https://i.pinimg.com/originals/3a/1e/e8/3a1ee866215e17f927e184652dc9a895.jpg Shaun das /Schaf]] ('''**Andrea**''')
* extended work on paper: LightCurve with words/day or git commits/day (get git repo) ('''**Christian**''')
* Web admin: extensive fights with WordPress -> small print for the side of the hat ('''**Matthias**''')
* CCD lab instructor: best of CCD protocols printout [ccd protocol layout]
* Teilchenweltvermittler (-> little "alien" particle stickers for the side of the hat; Images: /home/falkner/work/PhDhat)
* first-aider @ remeis: first-aid kit & defibrillator ('''**Max**''')

[[Category:Internal]]

PhD hat for Maria

2019-05-14T14:33:55Z

Lorenz: /* Work */

== PhD Hat for Maria ==

====== list of ideas ======

* colored hair
* shoes and socks of different color
* kids as little thesis helpers
* card/board games
* wiskey

* line measurements (remeis intern poll)
* timing analysis (power spectra)
* constellations

== building plan ==

====== Private ======

* firefighter
** firetruck with hose as tassel : Paper model + cord + nozzle ('''**Max**''')
** a beeper with button to start alarm
* Cycling from Erlangen to Remeis
** ESTW smokestack + canal leading to observatory + bike (with trailer) + figure (maybe fierfighter figure by playmobile?) with colored hair and shoes of different color ('''**Basti**''')
* whiskey (ardberg supernova)

====== Work ======

* Cyg X-1 (Draft Idea: build BH + Clumpy wind {clumps are sheep shaped} [wool & LEDS?] + accretion disk also sheep but colored wool?)
** BH as half sphere (styrofoam size of a tennis ball) ('''**Max**''')
** accretion disk made of colored wool ('''**Katya**''')
** clumpy wind: wool sheep on wire [similar like [https://i.pinimg.com/originals/3a/1e/e8/3a1ee866215e17f927e184652dc9a895.jpg Shaun das /Schaf]] ('''**Andrea**''')
* extended work on paper: LightCurve with words/day or git commits/day (get git repo) ('''**Christian**''')
* Web admin: extensive fights with WordPress -> small print for the side of the hat ('''**Matthias**''')
* CCD lab instructor: best of CCD protocols printout [ccd protocol layout]
* Teilchenweltvermittler (-> little "alien" particle stickers for the side of the hat; Images: /home/falkner/work/PhDhat)
* first-aider @ remeis: first-aid kit & defibrillator ('''**Max**''')

[[Category:Internal]]

PhD hat for Maria

2019-05-14T14:08:24Z

Lorenz: /* Work */

== PhD Hat for Maria ==

====== list of ideas ======

* colored hair
* shoes and socks of different color
* kids as little thesis helpers
* card/board games
* wiskey

* line measurements (remeis intern poll)
* timing analysis (power spectra)
* constellations

== building plan ==

====== Private ======

* firefighter
** firetruck with hose as tassel : Paper model + cord + nozzle ('''**Max**''')
** a beeper with button to start alarm
* Cycling from Erlangen to Remeis
** ESTW smokestack + canal leading to observatory + bike (with trailer) + figure (maybe fierfighter figure by playmobile?) with colored hair and shoes of different color ('''**Basti**''')
* whiskey (ardberg supernova)

====== Work ======

* Cyg X-1 (Draft Idea: build BH + Clumpy wind {clumps are sheep shaped} [wool & LEDS?] + accretion disk also sheep but colored wool?)
** BH as half sphere (styrofoam size of a tennis ball) ('''**Max**''')
** accretion disk made of colored wool
** clumpy wind: wool sheep on wire [similar like [https://i.pinimg.com/originals/3a/1e/e8/3a1ee866215e17f927e184652dc9a895.jpg Shaun das /Schaf]] ('''**Andrea**''')
* extended work on paper: LightCurve with words/day or git commits/day (get git repo) ('''**Christian**''')
* Web admin: extensive fights with WordPress -> small print for the side of the hat ('''**Matthias**''')
* CCD lab instructor: best of CCD protocols printout [ccd protocol layout]
* Teilchenweltvermittler (-> little "alien" particle stickers for the side of the hat; Images: /home/falkner/work/PhDhat)
* first-aider @ remeis: first-aid kit & defibrillator ('''**Max**''')

[[Category:Internal]]

Category:Admin

2018-10-19T08:36:28Z

Lorenz:

[[Category:Admin]]

===== Remeis Admin-Page =====

This page is only internally visible to the Admins.

==== Lab Course ====

* Before the lab course:
** check the PCs in the Meridian building:
*** they should all be functional, broken ones should be replaced
*** in total we should have about 10 computers available for the students
** [[setup prakti|Setup the prakti accounts]]
* [[Computer_Introduction|Introduction to Computers/Linux for Lab Students ]]

==== Serendipitous Issues ====

* [[Login Problems|Typical login problems]]
* [[Unmet Dependencies|''unmet dependencies'' issue in apt-get]]
* [[Overflow Filesystem|overflow file system]]

==== Add new Users ====
* Go to the remeis internal homepage -> admin -> LDAP
* Fill out the necessary fields, including a valid email address. If possible, also fill out the fields for room and telephone number.
* Log into LDAP, go to import and copy the text of the previous step. '''Important''': if the user is external, "current" in the first line has to be changed to "external"
* set the password of the user on taurus: <code>sudo passwd [username]</code>
* log in: <code>ssh username@taurus</code>
* currently only for X-ray group members: activate the X-ray scripts in the .cshrc
* Set the quota (on taurus), using a prototype which has normal quota <code>sudo edquota -p [prototype] [username]</code> (normal Quota is 8GB softlimit and 12GB hardlimit; it can be manually edited/shown with edquota -u user)
* if desired (in most cases), create a folder for the user at ''/userdata/data/[username]'' and adjust the permissions with <code>sudo chown username:remeis username</code>
* send Email to admin about the new user

==== Running Software / Updates / Setups ====

In this section a selection of services and their current configuration is described.

* [[CUPS| CUPS]] (Printing Service)
* [[Virtual Boxes| Virtual Boxes]]

Category:Internal

2018-05-02T11:58:06Z

Lorenz:

This page (and all other pages in the namespace 'intern') can only be viewed when logged-in.

=== Administrative stuff ===

* '''[[Ocotber 24th: Open House]]'''

* [[Common Practices at Remeis]]

==== Travels ====

* [[How to combine business and private travel]]

=== Lab course ===

[[How the lab manuals are structured and how you can edit them]]

[[Planning page for the 40cm imaging experiment]]

[[Planning page for the CCD lab ]]

[[Tables to fill in dates and comments for every group]]

[[Location of the lab equipment]]

[[What to mention in the computer introduction]]

=== Lit Club ===
[[List of Literature Club Talks]]

=== Hardware ===

[[List of servers in the Remeis Cluster]]

=== Mac Minis ===

Here are some short information about the Mac Minis in Erlangen:
* Link to the ecap wiki (works only in erlangen or in bamberg) - https://doku.ecap.physik.uni-erlangen.de/
* When you login in the keyboard layout will always be english
* The size of your $HOME directory is limited to 20 GB - only store files here, which cannot be reproduced e.g. scripts, etc..
* Store all the other stuff in /local/scratch
* Following programs will be installed on our Mac Minis:
**ISIS
**IDL
**HEADAS(FTOOLS)
**DS9
=== eROSITA ===

* [[eROSITA - Bamberg]]
* [[Coding standards]]
* [[Needed functions and libraries]]
* [[Q&A]]
* [[Preprocessing]]
* [[TODO]]
* [[fpipe-Treffen Tübingen 28.10.2010]]
* [[length of datatypes in C]]

=== TANAMI ===

* '''[[TANAMI| TANAMI - Start]]'''
* '''[[TANAMI - public]]'''

=== Proposals ===

When submitting a proposal for satellite observations usually a list of earlier successful proposals is added. To make it easier to find those relevant for the individual observatory and the scientific aim of the current proposal, [[Proposals| here]] is a list of proposals our group was involved in. Please include title, PI/CoIs, cycle and publications based on the observation.

=== Public Outreach ===

* In general, [mailto:Katharina.Leiter@physik.uni-wuerzburg.de Katha Leiter] is the responsible person for outreach in the group of M. Kadler in Wuerzburg. You may want to talk to her.
* Guided Tours and Public Outreach at Remeis
** [[Guided Tours and Public Outreach | general informations and knowledge base]] for guides
** [http://www.sternwarte.uni-erlangen.de/intern/Kalender/index.php online calender] - where the tours have to be listed in addition to the whiteboad in the copymachine office
** [[available presentation and videos]]
* [[popular science]] - how to explain "what we do" and physical phenomena to the public

=== Miscellaneous ===

[[cinema | Movie schedule for the Remeis Movie Club]]

[[phd_hat_list | List of future PhD's for hat matters]]

[[RCL]]

[[Remeis Gardening]]

PhD hat for Victoria

2018-05-02T11:28:06Z

Lorenz:

=== What to put on the hat (and who is building the parts) ===

* Victoria's Head size: still to be measured!
* Base hat construction: Sebastian

==== The hat ====

* Tassel (Quaste): coffee beans and coins '''(Maria)'''
* illuminated IBIS coded mask on top (switched on by the tassel?) '''(Fritz, Tommy)'''
* Cygnus in soft AND hard state '''(Andreas, Matthias)'''
* RXTE observing PSDs, Spectra and Count-Rate '''()'''
* IBIS mask connected with hard state via polarization
* RXTE-ASM lightcurve around the hat '''(Natalie)'''
* train around the hat, missing car (Zugabteil) '''(Maria, Natalie)'''
* Dublin story: closed door with toilet and pillow '''(Tobi)'''
* lab protocol with pop-up-dragon '''(Matthias)'''
* books and vegetables
* Marvel hero(s)
* VHS logo

==== Brainstorming ====

* coffee-machine
* "dragon" (what the lab-students used to call her)
* bare-feet
* books
* vegetable box
* comics (she is a big fan of them, e.g. the MARVEL stuff?)
* Cygnus X-1 (her main studied source)
* timing analysis (mainly with RXTE, Fourier transforms, PSDs, etc.)
* INTEGRAL (annoying analysis problems, coded masks)
* contributed to X-ray polarization (perhaps combine some cinema polarization glasses with some X-ray images, such as of some bones)
* LitClub

==== Other ideas ====

* should we try to seriously establish a Nachpruefung

[[Category:Internal]]

PhD hat for Victoria

2018-05-02T11:27:00Z

Lorenz: Created page with "=== What to put on the hat (and who is building the parts) === * Victoria's Head size: still to be measured! * Base hat construction: Sebastian ==== The hat ==== * Tassel (..."

=== What to put on the hat (and who is building the parts) ===

* Victoria's Head size: still to be measured!
* Base hat construction: Sebastian

==== The hat ====

* Tassel (Quaste): coffee beans and coins **(Maria)**
* illuminated IBIS coded mask on top (switched on by the tassel?) **(Fritz, Tommy)**
* Cygnus in soft AND hard state **(Andreas, Matthias)**
* RXTE observing PSDs, Spectra and Count-Rate **()**
* IBIS mask connected with hard state via polarization
* RXTE-ASM lightcurve around the hat **(Natalie)**
* train around the hat, missing car (Zugabteil) **(Maria, Natalie)**
* Dublin story: closed door with toilet and pillow **(Tobi)**
* lab protocol with pop-up-dragon **(Matthias)**
* books and vegetables
* Marvel hero(s)
* VHS logo

==== Brainstorming ====

* coffee-machine
* "dragon" (what the lab-students used to call her)
* bare-feet
* books
* vegetable box
* comics (she is a big fan of them, e.g. the MARVEL stuff?)
* Cygnus X-1 (her main studied source)
* timing analysis (mainly with RXTE, Fourier transforms, PSDs, etc.)
* INTEGRAL (annoying analysis problems, coded masks)
* contributed to X-ray polarization (perhaps combine some cinema polarization glasses with some X-ray images, such as of some bones)
* LitClub

==== Other ideas ====

* should we try to seriously establish a Nachpruefung

[[Category:Internal]]

SRT

2018-05-02T11:23:00Z

Lorenz: Created page with "For general instructions about how to use the SRTs see the page in the Remeis Wiki: The Small Radio Telescope (SRT) == Maintenance == === Mechanics..."

For general instructions about how to use the SRTs see the page in the Remeis Wiki: [[Small_Radio_Telescope|The Small Radio Telescope (SRT)]]

== Maintenance ==
=== Mechanics ===
Both of the SRTs need some service from time to time. Apparently there should always be enough grease on the inner part of the elevation arm otherwise it gets stuck. Therefore it is necessary to apply some about each month. At this opportunity all other joints and the cables should be checked too. Since in the last years there was water accumulated in the big black box of the mount as well as in the box at the end of the elevation arm these should be opened sometimes to check if those are dry.
=== Cronjobs ===
The PCs controlling the SRTs are cygnus for SRT1 and musca for SRT2. Both of them have a cronjob running which moves the telescopes every day at 12:30 around each axis. Two times the elevation and one time the right azimuth. This whole procedure takes about 25 minutes to finish. It does not matter if the software controlling the telescopes is running or not. The cronjobs cancel at their own if the software is detected to be running. Of course, if one telescope is pointing to azimuth 358° then it takes about 5 minutes until it is ready for operation again.
== Software ==
Up to this point only the old software written in Java works properly.
=== Commands ===
* '''srt''' starts the software on cygnus for SRT1 via X-window-forwarding
* '''srt1''' starts the software on cygnus for SRT1 via X-window-forwarding
* '''srt2''' starts the software on musca for SRT2 via X-window-forwarding
* '''srt_start''' starts the Java software on the locally used machine
<pre>/data/system/software/IBMJava2-142/bin/java -cp $dir srt 0 </pre>
essentially is the real part of Java which runs the interface as the class '''srt''' in
<pre>/data/system/software/IBMJava2-142/</pre>
It searches for the used serial port of the PC. If another instance of the program is running the software will not start.
Of course it is not possible to use use one telescope for two sessions. If the software is started and another group is using it there will be an error on the command line which shows the username of who is using it.

[[Category:Internal]]

RCL

2018-05-02T11:09:31Z

Lorenz: Created page with "=== RCL - internal information === There might be password protection on some RCL pages. These credentials should allow you to login: Username: remeis Password: Dr. Karl..."

=== RCL - internal information ===

There might be password protection on some RCL pages. These credentials should allow you to login:

Username: remeis

Password: Dr. Karl

[[Category:Internal]]

Poster

2018-05-02T11:07:28Z

Lorenz:

=== Printing Posters in Erlangen ===

[[File:Postersubmission.png|300px|thumb|right]]

If you want your poster to be printed at the RRZE, login to this [https://www.sso.uni-erlangen.de/simplesaml/module.php/core/loginuserpass.php?AuthState=_1c65b177aa8e6fd132551452235e366ebc2933dc77%3Ahttps%3A%2F%2Fwww.sso.uni-erlangen.de%2Fsimplesaml%2Fsaml2%2Fidp%2FSSOService.php%3Fspentityid%3Dhttps%253A%252F%252Fwww.poster.rrze.uni-erlangen.de%252Fsimplesaml%252Fmodule.php%252Fsaml%252Fsp%252Fmetadata.php%252Fdefault-sp%26cookieTime%3D1466692391%26RelayState%3Dhttps%253A%252F%252Fwww.poster.rrze.uni-erlangen.de%252Fupload%252Fcustomer.shtml website] with your FAU account, use "Dr. Karl Remeis Observatory & ECAP" as institution and "MPAI000" as customer ID.

Then follow the instructions.

See also
https://www.poster.rrze.uni-erlangen.de/welcome

[[Category:Internal]]

Poster

2018-05-02T11:05:19Z

Lorenz:

=== Printing Posters in Erlangen ===

If you want your poster to be printed at the RRZE, login to this [https://www.sso.uni-erlangen.de/simplesaml/module.php/core/loginuserpass.php?AuthState=_1c65b177aa8e6fd132551452235e366ebc2933dc77%3Ahttps%3A%2F%2Fwww.sso.uni-erlangen.de%2Fsimplesaml%2Fsaml2%2Fidp%2FSSOService.php%3Fspentityid%3Dhttps%253A%252F%252Fwww.poster.rrze.uni-erlangen.de%252Fsimplesaml%252Fmodule.php%252Fsaml%252Fsp%252Fmetadata.php%252Fdefault-sp%26cookieTime%3D1466692391%26RelayState%3Dhttps%253A%252F%252Fwww.poster.rrze.uni-erlangen.de%252Fupload%252Fcustomer.shtml website] with your FAU account, use "Dr. Karl Remeis Observatory & ECAP" as institution and "MPAI000" as customer ID.

Then follow the instructions.

See also
https://www.poster.rrze.uni-erlangen.de/welcome

[[Category:Internal]]

Poster

2018-05-02T11:02:27Z

Lorenz: /* Printing Posters in Erlangen */

Poster

2018-05-02T10:57:46Z

Lorenz:

Poster

2018-05-02T10:56:47Z

Lorenz: Created page with "=== Printing Posters in Erlangen === If you want your poster to be printed at the RRZE, login to this [https://www.sso.uni-erlangen.de/simplesaml/module.php/core/loginuserpas..."

=== Printing Posters in Erlangen ===

If you want your poster to be printed at the RRZE, login to this [https://www.sso.uni-erlangen.de/simplesaml/module.php/core/loginuserpass.php?AuthState=_1c65b177aa8e6fd132551452235e366ebc2933dc77%3Ahttps%3A%2F%2Fwww.sso.uni-erlangen.de%2Fsimplesaml%2Fsaml2%2Fidp%2FSSOService.php%3Fspentityid%3Dhttps%253A%252F%252Fwww.poster.rrze.uni-erlangen.de%252Fsimplesaml%252Fmodule.php%252Fsaml%252Fsp%252Fmetadata.php%252Fdefault-sp%26cookieTime%3D1466692391%26RelayState%3Dhttps%253A%252F%252Fwww.poster.rrze.uni-erlangen.de%252Fupload%252Fcustomer.shtml website]
[[Category:Internal]] with your FAU account, use "Dr. Karl Remeis Observatory & ECAP" as institution and "MPAI000" as customer ID.

Then follow the instructions.

See also
https://www.poster.rrze.uni-erlangen.de/welcome

ISIS introduction for the new bachelor students

2018-04-12T14:26:41Z

Lorenz: Created page with "== ISIS introduction for the new bachelor students == === General language features === * arrays ** operators & mathematical functions ** <code>where</code> * structs === P..."

== ISIS introduction for the new bachelor students ==

=== General language features ===
* arrays
** operators & mathematical functions
** <code>where</code>
* structs

=== Plotting with ISIS ===
* <code>[o][h]plot</code>
* <code>{x,y}label</code>, <code>title</code>
* <code>{x,y}range</code>, <code>{x,y}log</code>
* <code>color</code>, <code>linestyle</code>, <code>connect_points</code>, <code>pointstyle</code>
* <code>multiplot</code>

=== Data analysis ===
* FITS files
* histograms

=== Fitting with ISIS ===
* <code>load_data</code>
* <code>group</code>, <code>group_data</code>, <code>rebin_data</code>
* <code>[x]notice[_en]</code>
* <code>fit_fun</code>, <code>set_par</code>, <code>edit_par</code>
* <code>fit_counts</code>
* <code>define_counts</code>

[[Category:Isis / Slang]]

Parallel Error Calculation using MPI and SLmpi

2018-04-12T14:19:33Z

Lorenz: Created page with "=== Parallel Error Calculation with MPI and SLmpi === * For interactive error calculation in isis you can use <code>conf</code> or <code>conf_loop</code> (using Isis_Slaves.n..."

=== Parallel Error Calculation with MPI and SLmpi ===

* For interactive error calculation in isis you can use <code>conf</code> or <code>conf_loop</code> (using Isis_Slaves.num_slaves+1 cores on the host machine).
* Fast possibility: <code>mpi_fit_pars</code>. It's a routine in the isisscripts, which uses MPI to calculate the confidence intervals in parallel on different machines.

* Requirements:
*# SLmpi installed: [http://www.sternwarte.uni-erlangen.de/git.public/?p=slmpi.git http://www.sternwarte.uni-erlangen.de/git.public/?p=slmpi.git]
*# A Portable Batch System (PBS), e.g., Torque (see [[torque:start|Torque]] for an Introduction)
*# the Remeis-isisscripts [http://www.sternwarte.uni-erlangen.de/git.public/?p=isisscripts http://www.sternwarte.uni-erlangen.de/git.public/?p=isisscripts]

* Create an isisscript to be submitted via PBS:
*# load and group data, load best fit model
*# call <code>result = mpi_fit_pars([pars]);</code>
*# if you have the isisscripts you can store everything in a fits-file via <code>fits_save_fit(filename,result)</code>

* How to start the Job on the Remeis Cluster?
** Create a job-file with mpi-Option (e.g. by <code>qsub_array -p %%--%%mpi file.com</code>)
** the Command File <code>file.com</code> contains the list of scripts to be executed.
** Set nodes to the number of free parameters. (See below for an example).

<pre>
#!/bin/bash
#PBS -S /bin/bash -V
#PBS -t 0-0\%10000
#PBS -l nodes=11
#PBS -l walltime=03:00:00
#PBS -N file.com
#PBS -o example_script.out
#PBS -e example_script.err
cd /home/user/datadir
COMMAND[0]="mpiexec isis-script example_script.sl"
/usr/bin/nice -n +15 ${COMMAND[$PBS_ARRAYID]}
</pre>

[[Category:Isis / Slang]]

Self-value management

2018-04-12T14:03:50Z

Lorenz: Created page with "'''This page is under construction''' Although the code below is very short (52 lines), its advantages are enormous. Thus, the explanation takes a while and is not written y..."

'''This page is under construction'''

Although the code below is very short (52 lines), its advantages are enormous. Thus, the explanation takes a while and is not written yet ;-)

It combines
* [[isis:structfun|structures with functions]] and
* [[isis:functionnest|function nesting]]
to prevent values to be calculated multiple times (e.g. cosine of an angle). This is especially very helpful for more complex codes, in which there are many 'shared' values, as the user only has to think about it once when setting up the '''svm-object'''. Afterwards the '''svm-object''' does all the work on its one!

* '''NOTES:'''
** Runtime is around twice as slow as compared to same code coded straight forward, which is due to the function calling!

<pre>
private define define_retrun_function( return_fields ){
if(typeof(return_fields) != Array_Type) return_fields = [return_fields];

variable f;
foreach f ( return_fields )
eval(sprintf("private define return_%s(obj) { return obj.data.%s; };", f, f));
}

private define define_calculation_function( field, execute ){
if(typeof(field) != Array_Type) field = [field];

variable tempfun = "";
variable f,ff;
foreach f (field){
tempfun += sprintf("private define calculate_%s(obj) {", f);
tempfun += sprintf("(%s) = %s;", strjoin("obj.data."+field, ","), execute);
foreach ff (field)
tempfun += sprintf("obj.%s = &return_%s;", ff, ff);
tempfun += sprintf("return obj.data.%s;", f);
tempfun += "}";
eval(tempfun);
}
}

private define reset_fields( obj ){
variable fieldnames = get_struct_field_names( obj.data );
variable f;
foreach f (fieldnames){
set_struct_field( obj, f, eval(sprintf("&calculate_%s", f)));
set_struct_field( obj.data, f, NULL );
}
}

define object_init() {
variable fieldnames = [ "sint","cost","fun" ];
define_retrun_function( fieldnames );
define_calculation_function(["sint","cost"], "sincos(obj.input.theta)");
define_calculation_function( "fun", "obj.cost()+obj.sint()");

% Actual object
variable obj = struct_combine(struct{
data = struct_combine(fieldnames), % Storage for field values
input = struct{ theta = 0. },
reset = &reset_fields
},fieldnames); % Adding defined fields

% Initialize object fields with pointers to calulating functions
reset_fields( obj );

return obj;
}

</pre>

Now, let's have a look on the output of the following commands:
<pre>
isis> variable a = object_init;
isis> print(a);
{data=Struct_Type with 3 fields,
input=Struct_Type with 1 fields,
sint=&calculate_sint,
cost=&calculate_cost,
fun=&calculate_fun}
isis> a.fun();
1.0
isis> print(a);
{data=Struct_Type with 3 fields,
input=Struct_Type with 1 fields,
sint=&return_sint,
cost=&return_cost,
fun=&return_fun}
isis>
</pre>

[[Category:Isis / Slang]]

References to variables

2018-04-12T13:58:10Z

Lorenz: Created page with "=== References to variables === (after an email by Manfred) This should explain difference between modifying an array (which is passed by reference into functions) and creati..."

=== References to variables ===
(after an email by Manfred)

This should explain difference between modifying an array (which
is passed by reference into functions) and creating a new array (whose
scope is only local to your functions and will therefore be
garbage-collected after the function has exited).

Whenever you modify only elements of an array a, i.e., when you use
<pre>
a[where(a>2)] +=1;
</pre>
or
<pre>
a[*] +=1;
</pre>
the reference to the array as a whole is not changed, which means that
you really modify the original array.

Whenever you assign a new value to the entire variable `a', i.e. for
<pre>
a += 1;
</pre>
which is just an abbreviation for
<pre>
a = a + 1;
</pre>
or when you make an explict copy:
<pre>
a = @a;
</pre>
you lose the reference to the original array.
It doesn't matter that your new value happens to again be an array,
whose values are closely related to the original array...

Therefore, if you plan on modifying an array that was passed to the function through a qualifier, make sure you actually make a copy of the array
<pre>
variable tim = @qualifier("tim",[0.,0.]);
</pre>
such that changes are not passed on to the array outside the function. Otherwise, you might be in for an unpleasant surprise.

Dereferencing a reference to a variable or function (the qualifier function in this example) would be:
<pre>
variable qref = &qualifier;
variable bla = (@qref)("tim",[0,0]);
</pre>

The fact that reassigning entire arrays requires the creation of a new
array, followed by -- if there are no further references to the original
one -- garbage-collection of the old array (i.e. freeing its memory), is
the reason why building up arrays in loops is, though convenient, so
slow (for sufficiently large N) compared to building up lists, and
should therefore be avoided:
<pre>
variable a = Double_Type[0];
_for i (0, N) a = [a, f(i)]; % creates a new
</pre>
vs.
<pre>
variable l = {};
_for i (0, N) list_append(l, f(i)); % work on one list
variable a = list_to_array(l);
</pre>

(If you're interested, see a crux:~hanke/array_copy for a live demo of
the O(n^2) slowdown of `a=[a,f(i)]'.)

[[Category:Isis / Slang]]

Ternary operator ?

2018-04-12T13:53:20Z

Lorenz: Created page with "The ternary operator can be used to asign values to a variable depending on a condition: <pre> variable myvariable = condition ? value_if_true : value_if_false </pre> This is..."

The ternary operator can be used to asign values to a variable depending on a condition:
<pre>
variable myvariable = condition ? value_if_true : value_if_false
</pre>
This is equivalent to
<pre>
variable myvariable;
if (condition)
myvariable = value_if_true;
else
myvariable = value_if_false;
</pre>
As you can see, using the ternary operator results in very concise code. It communicates that one (''and only one'') variable is assigned and thus prevents errors like unintentionally using different variables in the two branches of the if-else-statement. However, the ternary operator might confuse people not familiar with it.

Note:
There are a ''few'' cases, where the ternary operator seems to be slower than using an if condition. The reason is, so far, unknown and might be related to the underlying CPU-architecture and/or compiler, which has been used to compile S-Lang. In most cases, however, there is no difference in runtime or even a gain in speed when using the ternary operator. Especially if you run code on several machines in parallel, the ternary operator is the method of choice.

Anyway, you may use this code to check which way is faster on ''your'' machine.
<pre>
variable Tif=0, Ttern=0, n, N=1000, i, iMax=1000000, b;
_for n (0, N-1)
{
tic; _for i (0, iMax) if (i==0) b=5; else b=7 ; Tif +=toc;
tic; _for i (0, iMax) b = (i==0 ? 5 : 7); Ttern+=toc;
}
vmessage("T[if] = %.2fs, T[tern] = %.2fs", Tif, Ttern);
</pre>

Since the evaluation of both the if-statement and the ternary-operator
is probably anyways very fast compared to your other calculations,
you might also want to try this (minimally more expensive) example:
<pre>
variable Tif=0, Ttern=0, n, N=1000, i, iMax=1000000, b;
_for n (0, N-1)
{
tic; _for i (0, iMax) if (i==0) b=sin(i); else b=cos(i) ; Tif +=toc;
tic; _for i (0, iMax) b = (i==0 ? sin(i) : cos(i)); Ttern+=toc;
}
vmessage("T[if] = %.2fs, T[tern] = %.2fs", Tif, Ttern);
</pre>

[[Category:Isis / Slang]]

Iterating over an array - three different for-loops

2018-04-12T13:48:21Z

Lorenz: Created page with "=== for === The traditional C-like for-loop is defined as follows: <pre> for (initialization; condition; increment/decrement) { statement; } </pre> This is very general, jus..."

=== for ===
The traditional C-like for-loop is defined as follows:
<pre>
for (initialization; condition; increment/decrement) {
statement;
}
</pre>
This is very general, just because nearly everything is possible! The three required expressions may contain any code and may not contain numbers: \\
<pre>
words = ["hello", "hi", "welcome", "me", "you", "they", "meet", "talk", "email"];
for (sentence = ""; urand() < .9; sentence += words[int(urand*length(words))] + " ") {
print(sentence);
}
</pre>
As you can see, the traditional for-loop is extremely flexible. But for the sake of speed! That is because the three expression are evaluated during each iteration!

=== _for ===
As soon as you like to loop over integer numbers (for instance over the indices of an array) you don't need the above flexibility. Thus, you should use another for-loop, which is defined for this purpose only (see also the [http://www.jedsoft.org/slang/doc/html/slang-8.html#ss8.3 S-Lang manual]):
<pre>
_for variable (start, end, increment/decrement) {
statement;
}
</pre>
For instance:
<pre>
_for i (0, length(myarray)-1, 1) {
print(myarray[i]);
}
</pre>

Since S-Lang pre2.3.0-75, it is possible to omit <code>1</code> as the third argument of the <code>_for</code> statement, reducing the above example to
<pre>
_for i (0, length(myarray)-1) {
print(myarray[i]);
}
</pre>

=== foreach ===
The last possibility to iterate through an array is to use the foreach-loop (in case you don't need the position of the element within the array). The following example is equivalent to the above one:
<pre>
foreach value (myarray) {
print(value);
}
</pre>

[[Category:Isis / Slang]]

Changing qualifiers before passing them on

2018-04-12T13:36:10Z

Lorenz:

== changing qualifiers before passing them on ==

In S-Lang (and thus also isis) it is possible to pass options to functions as qualifiers rather than arguments. This is useful, e.g., if you only want to specify certain options sometimes and use a predefined value else.

Defining a function, qualifiers can be used as (from the [[http://pulsar.sternwarte.uni-erlangen.de/hanke/science/X-ray/ISIS/cgi/help.cgi?subj=qualifier|S-Lang help for "qualifier"]])LINK DOES NOT EXIST ANYMORE?
:
<pre>
define echo (text)
{
variable fp = qualifier ("out", stdout);
() = fputs (text, fp);
}
echo ("hello"); % writes hello to stdout
echo ("hello"; out=stderr); % writes hello to stderr
</pre>
To pass a bunch of qualifiers as a single struct instead of comma separated set of name-value pairs, you need to let the parser know that you are using a structure-valued argument. Use a double semicolon to do so:
<pre>
variable quals = struct{ out=stderr };
echo("hello";; quals);
</pre>
Sometimes it is just useful to switch the behavior of a function via a qualifier without a value (or the <code>NULL</code> value) by just checking for its existence via <code>qualifier_exists("qualifier_name")</code> (again from the S-Lang help):
<pre>
define echo (text)
{
variable fp = stdout;
if (qualifier_exists ("use_stderr"))
fp = stderr;
() = fputs (text, fp);
}
echo ("hello"; use_stderr); % writes hello to stderr
</pre>
Qualifiers can also be passed on from one function to another function that is called in the definition: <code>__qualifiers()</code> returns the active set of qualifiers as a structure. You can just use it directly with a double semicolon to pass the qualifiers as shown above:
<pre>
define line_segment (x0, y0, x1, y1)
{
moveto (x0, y0);
lineto (x1, y1 ;; __qualifiers());
}
</pre>

So any qualifier specified in <code>line_segment</code> is directly passed to <code>lineto</code>.

But what if you want to modify some of the qualifiers first? Just use [[http://pulsar.sternwarte.uni-erlangen.de/hanke/science/X-ray/ISIS/cgi/help.cgi?subj=struct_combine|struct_combine]] (or the equivalent dereference operator) and take advantage of the facts that
* it is NULL-safe and
* more than one structure may have the same field name, in which case the value is given by the last structure:
<pre>
define get_pixel_array(dat, gainf, range)
{
variable pix = qualifier("pixel", [0:31]);
variable arr = Struct_Type[length(pix)];
variable i;
_for i(0, length(arr)-1)
arr[i] = vtoen(dat, gainf, range;; struct { @__qualifiers(), pixel=[pix[i]] });
return arr;
}
</pre>
More complicated solution: <del>Just save the structure returned by the function <nowiki>__qualifiers()</nowiki> into a variable, change/add/remove fields in that structure and then pass the new structure on. But be careful not to produce errors if no qualifier is used:</del>
<pre>
define get_pixel_array(dat, gainf, range)
{
variable pix = qualifier("pixel",[0:31:1]);
variable arr = Struct_Type[length(pix)];
variable i;

variable qual = __qualifiers();
if (typeof(qual) == Null_Type){ % if there are no qualifiers, there also is no struct
qual = struct{pixel};
}else if (struct_field_exists(qual,"pixel") == 0){
qual=struct_combine(qual, "pixel");
}

_for i(0,length(arr)-1,1)
{
qual.pixel=[pix[i]];
arr[i] = vtoen(dat,gainf,range;; qual);
}
return arr;
}
</pre>
Usually, it would probably be easier to change the original function but for example in this case for just a quick trouble shooting, I did not want to mess around with my function <code>vtoen</code>, which usually takes the qualifier <code>pixel</code> to know which pixels to sum up after gain correction. However, if you want an array of all individual pixels instead, i.e., loop through the entries in <code>pixel</code> while leaving other qualifiers untouched, the presented option is a quick workaround to still be able to access the other possible qualifiers (as, e.g., time or flag filtering).

If you want to look at how the <code>struct</code> for qualifiers looks like, you can do:
<pre>
define qual(){ return __qualifiers(); }
variable test = qual(;noval, someval=1, anarray=["a","b"]);
print(test);
</pre>

[[Category:Isis / Slang]]

Changing qualifiers before passing them on

2018-04-12T13:30:08Z

Lorenz: Created page with "== changing qualifiers before passing them on == In S-Lang (and thus also isis) it is possible to pass options to functions as qualifiers rather than arguments. This is usefu..."

== changing qualifiers before passing them on ==

In S-Lang (and thus also isis) it is possible to pass options to functions as qualifiers rather than arguments. This is useful, e.g., if you only want to specify certain options sometimes and use a predefined value else.

Defining a function, qualifiers can be used as (from the [[http://pulsar.sternwarte.uni-erlangen.de/hanke/science/X-ray/ISIS/cgi/help.cgi?subj=qualifier|S-Lang help for ''qualifier'']]):
<pre>
define echo (text)
{
variable fp = qualifier ("out", stdout);
() = fputs (text, fp);
}
echo ("hello"); % writes hello to stdout
echo ("hello"; out=stderr); % writes hello to stderr
</pre>
To pass a bunch of qualifiers as a single struct instead of comma separated set of name-value pairs, you need to let the parser know that you are using a structure-valued argument. Use a double semicolon to do so:
<pre>
variable quals = struct{ out=stderr };
echo("hello";; quals);
</pre>
Sometimes it is just useful to switch the behavior of a function via a qualifier without a value (or the <code>NULL</code> value) by just checking for its existence via <code>qualifier_exists("qualifier_name")</code> (again from the S-Lang help):
<pre>
define echo (text)
{
variable fp = stdout;
if (qualifier_exists ("use_stderr"))
fp = stderr;
() = fputs (text, fp);
}
echo ("hello"; use_stderr); % writes hello to stderr
</pre>
Qualifiers can also be passed on from one function to another function that is called in the definition: <code>__qualifiers()</code> returns the active set of qualifiers as a structure. You can just use it directly with a double semicolon to pass the qualifiers as shown above:
<pre>
define line_segment (x0, y0, x1, y1)
{
moveto (x0, y0);
lineto (x1, y1 ;; __qualifiers());
}
</pre>

So any qualifier specified in <code>line_segment</code> is directly passed to <code>lineto</code>.

But what if you want to modify some of the qualifiers first? Just use [[http://pulsar.sternwarte.uni-erlangen.de/hanke/science/X-ray/ISIS/cgi/help.cgi?subj=struct_combine|struct_combine]] (or the equivalent dereference operator) and take advantage of the facts that
* it is NULL-safe and
* more than one structure may have the same field name, in which case the value is given by the last structure:
<pre>
define get_pixel_array(dat, gainf, range)
{
variable pix = qualifier("pixel", [0:31]);
variable arr = Struct_Type[length(pix)];
variable i;
_for i(0, length(arr)-1)
arr[i] = vtoen(dat, gainf, range;; struct { @__qualifiers(), pixel=[pix[i]] });
return arr;
}
</pre>
More complicated solution: <del>Just save the structure returned by the function <nowiki>__qualifiers()</nowiki> into a variable, change/add/remove fields in that structure and then pass the new structure on. But be careful not to produce errors if no qualifier is used:</del>
<pre>
define get_pixel_array(dat, gainf, range)
{
variable pix = qualifier("pixel",[0:31:1]);
variable arr = Struct_Type[length(pix)];
variable i;

variable qual = __qualifiers();
if (typeof(qual) == Null_Type){ % if there are no qualifiers, there also is no struct
qual = struct{pixel};
}else if (struct_field_exists(qual,"pixel") == 0){
qual=struct_combine(qual, "pixel");
}

_for i(0,length(arr)-1,1)
{
qual.pixel=[pix[i]];
arr[i] = vtoen(dat,gainf,range;; qual);
}
return arr;
}
</pre>
Usually, it would probably be easier to change the original function but for example in this case for just a quick trouble shooting, I did not want to mess around with my function <code>vtoen</code>, which usually takes the qualifier <code>pixel</code> to know which pixels to sum up after gain correction. However, if you want an array of all individual pixels instead, i.e., loop through the entries in <code>pixel</code> while leaving other qualifiers untouched, the presented option is a quick workaround to still be able to access the other possible qualifiers (as, e.g., time or flag filtering).

If you want to look at how the <code>struct</code> for qualifiers looks like, you can do:
<pre>
define qual(){ return __qualifiers(); }
variable test = qual(;noval, someval=1, anarray=["a","b"]);
print(test);
</pre>

[[Category:Isis / Slang]]

List of servers in the Remeis Cluster

2018-04-12T10:50:59Z

Lorenz: Created page with "== Server on the Remeis Cluster == Here you can find an overview of our servers and what pieces of software and services are running on each of them. '''crux''' * LDAP * Web..."

== Server on the Remeis Cluster ==

Here you can find an overview of our servers and what pieces of software and services are running on each of them.

'''crux'''
* LDAP
* Web
* DNS
* DHCP
* NTP
* /data
* git
* Mail
* Backup (von /data)
* Ubuntu-Mirror
* MySQL

'''leo'''
* /userdata
* 2 Vboxes: auriga: print & hydrus: web
* cronjobs
* torque server + client
* Randomnumber-Server

'''phoenix'''
* /home
* Backup (von /home)
* /ixo
* cronjobs
* quota

'''grus'''
* /eu
* cronjobs

'''draco'''
* /loft
* VBox: openproject
* MySQL
* cronjob

'''virgo'''
* /virgoabc

'''serpens'''
* usage only for erosita project
* web (erosita)

[[Category:Internal]]

How to use the Remeis cluster

2018-04-12T10:01:58Z

Lorenz: /* ssh-keys */

== How To use the Remeis Cluster ==

The Cluster of the Remeis obsveratory is designed to make all ressources available for easy usage. Nevertheless, there are a few important things one has to know in order to use the cluster properly. In the following the most important information will be listed. Other questions or problems with the system or software sould be directed to [mailto:admins@sternwarte.uni-erlangen.de admins@sternwarte.uni-erlangen.de].

=== Performing Computations ===

* The servers ''crux'', ''grus'', and ''phoenix'' should not be used for computations at all.
* Computations and extractions on the Cluster should be submitted via '''torque'''. Information on how to use it can be found [[torque:start|here]].
* Also [[torque:start#interactive_jobs|interactive sessions]] can be started via '''torque'''.

=== The Data-Storage System ===

* '''/userdata:''' Extracted data like images or spectra or other space consuming stuff or stuff which can re recreated/downloaded again should be put there. /userdata is a RAID6 system, i.e. two disks can fail simultaneously w/o data loss --> your data is safe on /userdata! However, there is NO backup of userdata, as /userdata is too big to be backuped simply. And there is no quota on /userdata.

* '''/home:''' This is the place for self-developped software, scripts, documents, TeX files, diploma/phd/... theses, papers, spreadsheets, etc. /home is also a RAID system, i.e. more than one disk may fail w/o data loss. Furthermore, /home is backedup every night to TWO different disks (in two machines) AND once a week on an external disk that is stored outside the observatory for the worst case (fire etc). It therefore does not make sense to create your own private backups on local scratch disks etc. /home, however, is quite small (1 TB for all the institute); we therefore have a quota of about 10GB per user. It is no problem to get more space, if you can't move stuff around anymore, just drop an Email to the admins. On the other hand, you don't have to fill your quota completely! To check your quota you can use the ''quota'' command on crux, like
ssh crux quota -s -f /home

* '''/scratch:''' For temporary or otherwise not very important data. You should not store anything important on /scratch!! The scratch disks are NOT backedup and the scratch disks are not fail safe, i.e. if a scratch disk is broken (which happens regularly), your data is GONE.

* '''Satellite Data:''' We already have archives for most satellite raw data (applies mostly to the X-ray people). So please do not download any raw data yourself, but talk to the person in charge of a specific mission. You can find out who is responsible by executing <code>showSatelliteContacts</code> in the shell.

=== Logging into Remeis ===

==== Remote Login ====

===== Using ssh =====
You can log-in via ssh simply by
ssh -X <username>@<host>.sternwarte.uni-erlangen.de

===== Using the NX-Client =====

If you need a graphics interface, it might be worth to use the <code>nxclient</code> to connect to the Remeis Cluster. The corresponding <code>nxserver</code> is installed on (almost) all machines. In order to use it you have to [http://www.nomachine.com/download.php download] it and follow the Connection-Wizard to connect on a host. Always use the same machine, as only a limited number of total connections is allowed on each machine. This works for Linux, Mac OSX, and even Windows.

===== Hosts =====
Host names are generally the constellation names, e.g., <code>norma</code> or <code>leo</code>. All available hosts can be found in the shell variable <code>$RemeisHosts</code>. The servers (<code>crux</code>, <code>grus</code>, and <code>phoenix</code>) should not be used.

==== Connecting without password and short hostnames ====

Sick of always typing <code>user@myfavouritehost.sternwarte.uni-erlangen.de</code> and always having to enter your password when switching machines inside inside the Remeis Cluster? The follwing setup will make your life easier.

===== Config-File =====

In the file <code>~/.ssh/config</code> you can set up the configuration for ssh. A few things are really useful.
# activate compression, might lead to a faster connection
Compression yes
# do X11 forwarding by default, i.e., the option "-X" is
# always set when using "ssh"
forwardX11 yes

In order to define a short-cut for a host, you have to add the following information to the ''~/.ssh/config''
# the short-name you want to call the host (most useful is the general name of the machine
Host=pulsar
# now define user and host such that ''<User>@<Hostname>'' is the correct adress
Hostname=pulsar.sternwarte.uni-erlangen.de
User=YourUsername

===== ssh-keys =====

If you setup the ssh-keys properly, you can login via ssh without entering a password. This isn't only nice to have, but if you use [[torque:start|Torque]], this is mandatory. A detailed description can be found [[SSH-Keys|here]].

=== Setting the Default Options/Software ===

Each new account is equipped with a sample file at ''~/.cshrc'', which is loaded on every start of the terminal. Hence, this defines your options, i.e., the software available, short-cuts, your favourite editor, and so on. Commonly useful options are activated by default. In addition, there are a few additional features, which are commented out by default but still very useful for most users.

# set your favourite text editor to be used by default; important, e.g., if you want to use GIT
setenv EDITOR jed

# activate the X-ray software (HEADAS, satellite extraction scripts, ...)
source $SOFTDIR/softwarescript_Xray.csh

More information on the TC shell and how to configure it can be found [[csh:start|here]].

[[Category:Current Members]]

How to use the Remeis cluster

2018-04-12T09:53:49Z

Lorenz: Created page with "== How To use the Remeis Cluster == The Cluster of the Remeis obsveratory is designed to make all ressources available for easy usage. Nevertheless, there are a few important..."

== How To use the Remeis Cluster ==

The Cluster of the Remeis obsveratory is designed to make all ressources available for easy usage. Nevertheless, there are a few important things one has to know in order to use the cluster properly. In the following the most important information will be listed. Other questions or problems with the system or software sould be directed to [mailto:admins@sternwarte.uni-erlangen.de admins@sternwarte.uni-erlangen.de].

=== Performing Computations ===

* The servers ''crux'', ''grus'', and ''phoenix'' should not be used for computations at all.
* Computations and extractions on the Cluster should be submitted via '''torque'''. Information on how to use it can be found [[torque:start|here]].
* Also [[torque:start#interactive_jobs|interactive sessions]] can be started via '''torque'''.

=== The Data-Storage System ===

* '''/userdata:''' Extracted data like images or spectra or other space consuming stuff or stuff which can re recreated/downloaded again should be put there. /userdata is a RAID6 system, i.e. two disks can fail simultaneously w/o data loss --> your data is safe on /userdata! However, there is NO backup of userdata, as /userdata is too big to be backuped simply. And there is no quota on /userdata.

* '''/home:''' This is the place for self-developped software, scripts, documents, TeX files, diploma/phd/... theses, papers, spreadsheets, etc. /home is also a RAID system, i.e. more than one disk may fail w/o data loss. Furthermore, /home is backedup every night to TWO different disks (in two machines) AND once a week on an external disk that is stored outside the observatory for the worst case (fire etc). It therefore does not make sense to create your own private backups on local scratch disks etc. /home, however, is quite small (1 TB for all the institute); we therefore have a quota of about 10GB per user. It is no problem to get more space, if you can't move stuff around anymore, just drop an Email to the admins. On the other hand, you don't have to fill your quota completely! To check your quota you can use the ''quota'' command on crux, like
ssh crux quota -s -f /home

* '''/scratch:''' For temporary or otherwise not very important data. You should not store anything important on /scratch!! The scratch disks are NOT backedup and the scratch disks are not fail safe, i.e. if a scratch disk is broken (which happens regularly), your data is GONE.

* '''Satellite Data:''' We already have archives for most satellite raw data (applies mostly to the X-ray people). So please do not download any raw data yourself, but talk to the person in charge of a specific mission. You can find out who is responsible by executing <code>showSatelliteContacts</code> in the shell.

=== Logging into Remeis ===

==== Remote Login ====

===== Using ssh =====
You can log-in via ssh simply by
ssh -X <username>@<host>.sternwarte.uni-erlangen.de

===== Using the NX-Client =====

If you need a graphics interface, it might be worth to use the <code>nxclient</code> to connect to the Remeis Cluster. The corresponding <code>nxserver</code> is installed on (almost) all machines. In order to use it you have to [http://www.nomachine.com/download.php download] it and follow the Connection-Wizard to connect on a host. Always use the same machine, as only a limited number of total connections is allowed on each machine. This works for Linux, Mac OSX, and even Windows.

===== Hosts =====
Host names are generally the constellation names, e.g., <code>norma</code> or <code>leo</code>. All available hosts can be found in the shell variable <code>$RemeisHosts</code>. The servers (<code>crux</code>, <code>grus</code>, and <code>phoenix</code>) should not be used.

==== Connecting without password and short hostnames ====

Sick of always typing <code>user@myfavouritehost.sternwarte.uni-erlangen.de</code> and always having to enter your password when switching machines inside inside the Remeis Cluster? The follwing setup will make your life easier.

===== Config-File =====

In the file <code>~/.ssh/config</code> you can set up the configuration for ssh. A few things are really useful.
# activate compression, might lead to a faster connection
Compression yes
# do X11 forwarding by default, i.e., the option "-X" is
# always set when using "ssh"
forwardX11 yes

In order to define a short-cut for a host, you have to add the following information to the ''~/.ssh/config''
# the short-name you want to call the host (most useful is the general name of the machine
Host=pulsar
# now define user and host such that ''<User>@<Hostname>'' is the correct adress
Hostname=pulsar.sternwarte.uni-erlangen.de
User=YourUsername

===== ssh-keys =====

If you setup the ssh-keys properly, you can login via ssh without entering a password. This isn't only nice to have, but if you use [[torque:start|Torque]], this is mandatory. A detailed description can be found [[ssh-keys:start|here]]

=== Setting the Default Options/Software ===

Each new account is equipped with a sample file at ''~/.cshrc'', which is loaded on every start of the terminal. Hence, this defines your options, i.e., the software available, short-cuts, your favourite editor, and so on. Commonly useful options are activated by default. In addition, there are a few additional features, which are commented out by default but still very useful for most users.

# set your favourite text editor to be used by default; important, e.g., if you want to use GIT
setenv EDITOR jed

# activate the X-ray software (HEADAS, satellite extraction scripts, ...)
source $SOFTDIR/softwarescript_Xray.csh

More information on the TC shell and how to configure it can be found [[csh:start|here]].

[[Category:Current Members]]

Common Practices at Remeis

2018-04-12T09:08:02Z

Lorenz: Created page with "== Common Practices at Remeis == '''From an e-mail by J. Wilms on 2016 June 14 to the X-ray gang''' ''We try to be as flexible as possible, and I trust that you are adults a..."

== Common Practices at Remeis ==

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

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

=== Working Times ===

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

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

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

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

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

=== Illness & Vacation ===

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

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

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

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

=== X-ray Group Meeting ===

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

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

=== Journal Club ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Dishwasher Etiquette ===

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

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

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

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

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

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

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

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

[[Category:Current Members]]