Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
PyCharm OOD
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
RC Data Science
community-ood-sandbox
PyCharm OOD
Commits
dbc5c2ca
Commit
dbc5c2ca
authored
2 months ago
by
Matthew K Defenderfer
Browse files
Options
Downloads
Patches
Plain Diff
remove all jupyter material from the readme
parent
93ba65c2
Branches
main
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+1
-75
1 addition, 75 deletions
README.md
with
1 addition
and
75 deletions
README.md
+
1
−
75
View file @
dbc5c2ca
# Batch Connect - JupyterLab
# Batch Connect - PyCharm


An example Batch Connect app that launches a JupyterLab within a
batch job.
## Prerequisites
This Batch Connect app requires the following software be installed on the
**compute nodes**
that the batch job is intended to run on (
**NOT**
the
OnDemand node):
-
[
JupyterLab
](
http://jupyterlab.readthedocs.io/en/latest/
)
3.2.1 (earlier
versions are untested but may work for you)
-
[
OpenSSL
](
https://www.openssl.org/
)
1.0.1+ (used to hash the JupyterLab
server password)
**Optional**
software:
-
[
Lmod
](
https://www.tacc.utexas.edu/research-development/tacc-projects/lmod
)
6.
0.1+ or any other
`module purge`
and
`module load <modules>`
based CLI
used to load appropriate environments within the batch job before launching
the JupyterLab.
## Install
These are command line only installation directions.
We start by downloading a zipped package of this code. This allows us to start
with a fresh directory that has no git history as we will be building off of
this.
```
sh
# Download the zip from the GitHub page
wget https://github.com/uabrc/ood_jupyterlab/archive/master.tar.gz
# Create a catchy directory
mkdir
my_jupyterlab_app
# Unzip the downloaded file into this directory
tar
xzvf master.tar.gz
-C
my_jupyterlab_app
--strip-components
=
1
# Change the working directory to this new directory
cd
my_jupyterlab_app
```
From here you will make any modifications to the code that you would like and
version your changes in your own repository:
```
sh
# Version our app by making a new Git repository
git init
#
# Make all your code changes while testing them in the OnDemand Dashboard
#
# ...
#
# Add the files to the Git repository
git add
--all
# Commit the staged files to the Git repository
git commit
-m
"my first commit"
```
## Contributing
1.
Fork it ( https://github.com/OSC/bc_example_jupyter/fork )
2.
Create your feature branch (
`git checkout -b my-new-feature`
)
3.
Commit your changes (
`git commit -am 'Add some feature'`
)
4.
Push to the branch (
`git push origin my-new-feature`
)
5.
Create a new Pull Request
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment