Quick linksYou can find my list of publications here.You will find everything about the data-reduction tool p3d here. About my work and skillsI work with projects ranging from theory and modeling, observations, to writing tools for data reduction and data analysis. Here follows a brief summary of my work:
More information related to meUseful computing-related informationIf your remote machine is behind a thick firewall it is necessary to use an ssh tunnel when logging in or copying a file from that machine. Here is some information on how to do that. I use the following notation: RUSER is your login name on the remote machine, you do not have to use it if it is the same as on your local machine; MACHINE is the name of your remote machine (for example: star.aip.de); DMZ is the name of the remote login computer (for example: starport.aip.de), which is not the same computer as your remote machine; I use the port number 50809, you may use any other port, if necessary; <file> is the name of the file you want to transfer, with the full path if it is not available in the current directory; <path> is the path on the remote machine.
At first, from your local machine, open an ssh tunnel using the following command: ssh -l RUSER -L 50809:MACHINE:22 DMZ Now you can log on to the remote machine from your local computer using (add the -X or -Y flag if you need to be able to open X-applications from your remote machine – yes, in this case X11 forwarding needs to be switched on at the remote machine): ssh -p 50809 -l RUSER localhost If you instead need to copy one or several files to or from the remote machine you can use (yes, change the order of <file> and RUSER@localhost:<path> if you want to copy the file(s) the other way): scp -P 50809 -p <file> RUSER@localhost:<path> In fact, it is better to use rsync since it can continue an interrupted transfer without starting from scratch (it is also possible to continue an interrupted scp-transfer using this approach): rsync --partial --progress --rsh="ssh -p 50809 -l RUSER" <file> localhost:<path> The procedure is very similar if you want to use vnc to connect to computer behind a firewall using a remote login machine. At first, make sure that you have started the vnc server on your remote MACHINE using a command such as the following: vncserver -geometry 1280x1024 Thereafter, from your local machine, open an ssh port forwarding tunnel using the following command (assuming that you will use port 5901): ssh -l RUSER -N -f -L 5901:MACHINE:5901 DMZ Finally, start the vnc session on your local machine: vncviewer localhost:1 Good luck!
Astronomy Picture of the Day (follow link for all details):
|