Areinhar at 14:25, 7 July 2026

2026-07-07T14:25:17Z

← Older revision		Revision as of 14:25, 7 July 2026
Line 5:		Line 5:
	[[Category:PSC]]		[[Category:PSC]]

	~~= General =~~		There are multiple ways to run python on the server. To be the most productive coder, it’s important to understand how virtual environments can help product reproducibility and stability of your analysis ([[Python_virtual_environments\|Python virtual environments]]) and how to keep running jobs even when you are not connected to the server ([[Terminal_multiplexers\|Terminal Multiplexers]]). If you’re less aware than you’d like, we encourage you to visit either of these pages. General Linux commands and getting connected & passing files between you and the server can all be found on our [[Linux_and_department_servers\|Linux and the department server page]].

	There are multiple ways to run python on the server. ~~In order to~~ be the most productive coder, it’s important to understand how virtual environments can help product reproducibility and stability of your analysis ([[Python_virtual_environments\|Python virtual environments]]) and how to keep running jobs even when you are not connected to the server ([[Terminal_multiplexers\|Terminal Multiplexers]]). If you’re less aware than you’d like, we encourage you to visit either of these pages. General Linux commands and getting connected & passing files between you and the server can all be found on our [[Linux_and_department_servers\|Linux and the department server ~~wiki~~]].

	== Submitting jobs via the command line ==		== Submitting jobs via the command line ==

Ajshen at 02:23, 30 June 2026

2026-06-30T02:23:05Z

← Older revision		Revision as of 02:23, 30 June 2026
Line 1:		Line 1:

	[[Category:IDEs]]		[[Category:IDEs]]
	[[Category:Department ~~Services~~]]		[[Category:Department Servers]]
	[[Category:Wright Cluster]]		[[Category:Wright Cluster]]
	[[Category:PSC]]		[[Category:PSC]]

Ajshen at 03:27, 29 June 2026

2026-06-29T03:27:18Z

← Older revision		Revision as of 03:27, 29 June 2026
Line 1:		Line 1:

	~~ ~~		[[Category:IDEs]]
			[[Category:Department Services]]
			[[Category:Wright Cluster]]
			[[Category:PSC]]

	= General =		= General =

Skipper: Created page with " = General = There are multiple ways to run python on the server. In order to be the most productive coder, it’s important to understand how virtual environments ca..."

2024-03-29T23:59:15Z

Created page with " = General = There are multiple ways to run python on the server. In order to be the most productive coder, it’s important to understand how virtual environments ca..."

New page

 

= General =

There are multiple ways to run python on the server. In order to be the most productive coder, it’s important to understand how virtual environments can help product reproducibility and stability of your analysis ([[Python_virtual_environments|Python virtual environments]]) and how to keep running jobs even when you are not connected to the server ([[Terminal_multiplexers|Terminal Multiplexers]]). If you’re less aware than you’d like, we encourage you to visit either of these pages. General Linux commands and getting connected & passing files between you and the server can all be found on our [[Linux_and_department_servers|Linux and the department server wiki]].

== Submitting jobs via the command line ==

Before saving a code, you can start up python with a <code>ipython</code> or <code>python</code> call to the command line (possibly after activating a virtual environment). This will give you an interactive terminal to test python code out.

Beyond this iterative coding / explorative approach, you may find that writing up complex analysis that requires running a large number of lines of code (without having to manually run) large jobs that you’d like to run on a server, a common approach is to write a <code>.py</code> file to be run all at once, which can be done follows:
<syntaxhighlight lang="bash">ipython filename.py
python filename.py</syntaxhighlight>

Especially when it comes to code run on the server, it’s possible that you’d like to take in a few non-fixed parameters when you run your file. This can be done through the following approach (and is also documented in a tutorial: [https://www.geeksforgeeks.org/how-to-use-sys-argv-in-python/ geeksforgeeks]).

In your python file (<code>filename.py</code>) (often at the top) you deal with arguments passed in from the command line:
<syntaxhighlight lang="python">import sys

input_arguments = sys.argv
arg1 = int(sys.argv[1]) # the first argument (sys.argv[0]) is the filename.
arg2 = sys.argv[2]
...</syntaxhighlight>

If you then ran the following in the command line:
<syntaxhighlight lang="bash">ipython filename.py 1000 happy
python filename.py 1000 happy</syntaxhighlight>

You’d then find the lines below <code>arg2 = sys.argv[2]</code> would have <code>arg1 = 1000</code> (an integer), and <code>arg2 = "happy"</code>. Note that all parameters are pasted through as strings.

=== interactive <code>ipython</code>/<code>python</code> ===

Especially since you’ll be doing more of these command line running of files, if you are not 100% sure your code will run as expected or would like to be able to manipulate some of the objects you’ve made after run your file you can run your scripts interactively. If the script fails (or just when it ends), you’ll obtain an interactive ipython / python output. Below are two examples of how to do so (just use the <code>-i</code> command).
<syntaxhighlight lang="bash">ipython -i filename.py 1001 sad
python -i filename.py 1001 sad</syntaxhighlight>

= Jupyter notebooks via a server =

You can still run jupyter notebooks from a server, which can be useful with large data sets, need for more computing power, or just the desire to not have your personal computer’s cores being taxed. Starting a jupyter notebook from the server is pretty simple, and we outline how to below ([https://coderwall.com/p/ohk6cg/remote-access-to-ipython-notebooks-via-ssh coderwall] is has a good resource).

<ol start="1" style="list-style-type: decimal;">
<li>The first step is to initialize the notebook server just like you would on your own computer. On your remote server do:
<syntaxhighlight lang="bash">remote_server$ jupyter notebook --no-browser --port=8889</syntaxhighlight>

Note that you should think about be running this code after a <code>screen</code> or <code>tmux</code> call so it lasts even if you close / lose connection to the the connection that ran this call.
</li>
<li>Then on your local machine, you can run:</li>
<syntaxhighlight lang="bash">local$ ssh -N -f -L localhost:8888:localhost:8889 user_id@remote_server</syntaxhighlight>
<li>Finally, you can return to the server terminal you launched the jupyter notebook from and you’ll see something like:</li>
<syntaxhighlight lang="bash">Copy/paste this URL into your browser when you connect for the first time,
to login with a token:
http://localhost:8889/?token=13cc54b4a3e13877cb07211346a363f9147a8cf2109263f1&token=13cc54b4a3e13877cb07211346a363f9147a8cf2109263f1
</syntaxhighlight>
<li>Copy this address but substitute <code>8889</code> with <code>8888</code> on your local machine’s web server.</li>
<li>start coding</li>
</ol>

Python on the server - Revision history

Areinhar at 14:25, 7 July 2026

Ajshen at 02:23, 30 June 2026

Ajshen at 03:27, 29 June 2026

Skipper: Created page with " = General = There are multiple ways to run python on the server. In order to be the most productive coder, it’s important to understand how virtual environments ca..."