OpenOnDemand - Revision history

Nathanrwells: /* Creating python virtual environments */

2025-04-03T19:27:57Z

Creating python virtual environments

← Older revision		Revision as of 14:27, 3 April 2025
Line 141:		Line 141:
	NAME="testing_ondemand_virtualenv"		NAME="testing_ondemand_virtualenv"
	VIRTUAL_ENV="/homes/mozes/virtualenvs/testing_ondemand_jupyter"		VIRTUAL_ENV="/homes/mozes/virtualenvs/testing_ondemand_jupyter"
	MODULES="jupyter_python/3.8.6-TensorFlow-2.4.1"		MODULES="jupyter_python/3.10.4-TensorFlow-2.11.0"

	# of course, you should provide your own name and path to the virtual environment. Please don't put spaces in the name.		# of course, you should provide your own name and path to the virtual environment. Please don't put spaces in the name.

Nathanrwells: /* Creating python virtual environments */

2025-04-03T18:00:52Z

Creating python virtual environments

← Older revision		Revision as of 13:00, 3 April 2025
Line 122:		Line 122:

	# Load the version you would like (ideally you use a jupyter_python module for this, otherwise the virtual environment itself will have to have a decent amount of jupyter libraries installed into it)		# Load the version you would like (ideally you use a jupyter_python module for this, otherwise the virtual environment itself will have to have a decent amount of jupyter libraries installed into it)
	module load jupyter_python/3.8.6-TensorFlow-2.4.1		module load jupyter_python/3.10.4-TensorFlow-2.11.0

	# If you'd like to see what libraries this actually loaded, you can check it with the following:		# If you'd like to see what libraries this actually loaded, you can check it with the following:

Nathanrwells: /* Creating python virtual environments */

2025-04-03T17:59:50Z

Creating python virtual environments

← Older revision		Revision as of 12:59, 3 April 2025
Line 119:		Line 119:

	# Then we can list the jupyter_python modules so we can use them to create the virtual environment:		# Then we can list the jupyter_python modules so we can use them to create the virtual environment:
	module ~~list~~ jupyter_python		module avail jupyter_python

	# Load the version you would like (ideally you use a jupyter_python module for this, otherwise the virtual environment itself will have to have a decent amount of jupyter libraries installed into it)		# Load the version you would like (ideally you use a jupyter_python module for this, otherwise the virtual environment itself will have to have a decent amount of jupyter libraries installed into it)

Daveturner: /* Creating python virtual environments */

2025-02-25T04:37:28Z

Creating python virtual environments

← Older revision		Revision as of 23:37, 24 February 2025
Line 146:		Line 146:
	</syntaxhighlight>		</syntaxhighlight>
	Once you start a new jupyter session it should list the new kernel option that uses your virtual environment.		Once you start a new jupyter session it should list the new kernel option that uses your virtual environment.
	From the ==Jupyter== page with the ==Files== menu chosen you should find your kernel under the ==New==		From the '''Jupyter''' page with the '''Files''' menu chosen you should find your kernel under the '''New'''
	menu on the top right.		menu on the top right.

Daveturner: /* Extra Python libraries */

2025-02-25T04:33:11Z

Extra Python libraries

← Older revision		Revision as of 23:33, 24 February 2025
Line 96:		Line 96:
	Julia support will come, but will need each user to set it up individually. There is currently a large bug centered around Julia, CentOS/RHEL, and our shared filesystem (Ceph).		Julia support will come, but will need each user to set it up individually. There is currently a large bug centered around Julia, CentOS/RHEL, and our shared filesystem (Ceph).

	===== ~~Extra Python~~ libraries =====		===== Installing python libraries =====
	~~====== Without extra setup ======~~
	You may need to install extra python libraries to use with your Jupyter Python kernels. For instance, this is how you'd install tobler		You may need to install extra python libraries to use with your Jupyter Python kernels. For instance, this is how you'd install tobler from within a Jupyter Notebook:
	<syntaxhighlight lang=python>		<syntaxhighlight lang=python>
	!pip install --user tobler		!pip install --user tobler
Line 109:		Line 109:
	</syntaxhighlight>		</syntaxhighlight>

	=====~~= With~~ python virtual environments ======		===== Creating python virtual environments =====
	~~Sometimes it is useful~~ to ~~have separation between your various projects~~, ~~for instance being able to use multiple versions of~~ a ~~python library in different projects~~.		You can create separate python virtual libraries for each project to keep the libraries separate for each.
			Each virtual environment can be created using the commands below in a terminal on Beocat, or you can
			precede each with an exclamation point and issue them from within a Jupyter notebook.

	~~You can setup a virtual environment (or many) for use with our Jupyter environment.~~
	<syntaxhighlight lang=bash>		<syntaxhighlight lang=bash>
	# First we'll activate the ability to use the ondemand modules:		# First we'll activate the ability to use the ondemand modules:
	module use /opt/beocat/ondemand_modules		module use /opt/beocat/ondemand_modules

	# Then we can list the jupyter_python modules (so we can use them to create the virtual environment)		# Then we can list the jupyter_python modules so we can use them to create the virtual environment:
	module list jupyter_python		module list jupyter_python

	# Load the version you would like (ideally you use a jupyter_python module for this, otherwise the virtual environment itself will have to have a decent amount of jupyter libraries installed into it		# Load the version you would like (ideally you use a jupyter_python module for this, otherwise the virtual environment itself will have to have a decent amount of jupyter libraries installed into it)
	module load jupyter_python/3.8.6-TensorFlow-2.4.1		module load jupyter_python/3.8.6-TensorFlow-2.4.1

Line 144:		Line 145:
	# of course, you should provide your own name and path to the virtual environment. Please don't put spaces in the name.		# of course, you should provide your own name and path to the virtual environment. Please don't put spaces in the name.
	</syntaxhighlight>		</syntaxhighlight>
	Once you start a new jupyter session it should list the new kernel option that uses your virtual environment		Once you start a new jupyter session it should list the new kernel option that uses your virtual environment.
			From the ==Jupyter== page with the ==Files== menu chosen you should find your kernel under the ==New==
			menu on the top right.

	=====~~= With~~ conda ======		===== Installing libraries with conda =====
	Conda environments should automatically show up if ''conda'' is in the PATH. For them to function properly, they will need at least the ipykernel library installed into them.		Conda environments should automatically show up if ''conda'' is in the PATH. For them to function properly, they will need at least the ipykernel library installed into them.

Daveturner: /* OpenOnDemand */

2025-02-07T05:04:50Z

OpenOnDemand

← Older revision		Revision as of 00:04, 7 February 2025
Line 5:		Line 5:
	interactivity.		interactivity.

	One of the greatest benefits of this system is remote access to large machines for computational tasks, without the need for utilizing a ~~commnand~~-line interface that is difficult to learn.		One of the greatest benefits of this system is remote access to large machines for computational tasks, without the need for utilizing a command-line interface that is difficult to learn.

	Our installation is available at https://ondemand.beocat.ksu.edu		Our installation is available at https://ondemand.beocat.ksu.edu

Mozes: /* With conda */

2024-05-31T19:20:13Z

With conda

← Older revision		Revision as of 14:20, 31 May 2024
Line 147:		Line 147:

	====== With conda ======		====== With conda ======
	Conda environments should automatically show up if ''conda'' is in the PATH.		Conda environments should automatically show up if ''conda'' is in the PATH. For them to function properly, they will need at least the ipykernel library installed into them.

			conda install -c conda-forge ipykernel

	==== Beocat Desktop ====		==== Beocat Desktop ====

Mozes: /* With virtualenv */

2024-04-05T20:42:12Z

With virtualenv

← Older revision		Revision as of 15:42, 5 April 2024
Line 109:		Line 109:
	</syntaxhighlight>		</syntaxhighlight>

	====== With ~~virtualenv~~ ======		====== With python virtual environments ======
	Sometimes it is useful to have separation between your various projects, for instance being able to use multiple versions of a python library in different projects.		Sometimes it is useful to have separation between your various projects, for instance being able to use multiple versions of a python library in different projects.

Line 117:		Line 117:
	module use /opt/beocat/ondemand_modules		module use /opt/beocat/ondemand_modules

	# Then we can list the jupyter_python modules (so we can use them to create the ~~virtualenv~~		# Then we can list the jupyter_python modules (so we can use them to create the virtual environment)
	module list jupyter_python		module list jupyter_python

	# Load the version you would like (ideally you use a jupyter_python module for this, otherwise the ~~virtualenv~~ itself will have to have a decent amount of jupyter libraries installed into it		# Load the version you would like (ideally you use a jupyter_python module for this, otherwise the virtual environment itself will have to have a decent amount of jupyter libraries installed into it
	module load jupyter_python/3.8.6-TensorFlow-2.4.1		module load jupyter_python/3.8.6-TensorFlow-2.4.1

Line 127:		Line 127:

	# We'll create a virtual environment (activate it and install any libraries you need.		# We'll create a virtual environment (activate it and install any libraries you need.
	~~virtualenv~~ --system-site-packages /homes/mozes/virtualenvs/testing_ondemand_jupyter		python -m venv --system-site-packages /homes/mozes/virtualenvs/testing_ondemand_jupyter
	. /homes/mozes/virtualenvs/testing_ondemand_jupyter/bin/activate		. /homes/mozes/virtualenvs/testing_ondemand_jupyter/bin/activate
	pip install # insert needed libraries here		pip install # insert needed libraries here
Line 144:		Line 144:
	# of course, you should provide your own name and path to the virtual environment. Please don't put spaces in the name.		# of course, you should provide your own name and path to the virtual environment. Please don't put spaces in the name.
	</syntaxhighlight>		</syntaxhighlight>
	Once you start a new jupyter session it should list the new kernel option that uses your ~~virtualenv~~		Once you start a new jupyter session it should list the new kernel option that uses your virtual environment

	====== With conda ======		====== With conda ======

Mozes: /* With virtualenv */

2023-07-24T16:17:05Z

With virtualenv

← Older revision		Revision as of 11:17, 24 July 2023
Line 115:		Line 115:
	<syntaxhighlight lang=bash>		<syntaxhighlight lang=bash>
	# First we'll activate the ability to use the ondemand modules:		# First we'll activate the ability to use the ondemand modules:
	module use ondemand_modules		module use /opt/beocat/ondemand_modules

	# Then we can list the jupyter_python modules (so we can use them to create the virtualenv		# Then we can list the jupyter_python modules (so we can use them to create the virtualenv

Mozes: /* File Management */

2023-04-19T18:09:43Z

File Management

← Older revision		Revision as of 13:09, 19 April 2023
Line 17:		Line 17:

	[[File:Ood Files Launch.png\|The OpenOnDemand File management application]]		[[File:Ood Files Launch.png\|The OpenOnDemand File management application]]

			If you're looking for a way to get your files into and out of OneDrive, Google Drive, other cloud providers you may be interested in taking a look at our documentation for [[Onedrive Data Transfer]]

	=== Job Management ===		=== Job Management ===