Job tagging/notation

johnbot1 · October 8, 2021, 5:29pm

Basic question here. I have a user that runs many Jupyter Lab jobs concurrently but it’s becoming difficult to keep track of his tasks/purpose for each app launch. Is there a way to tag/notate the running jobs? My solution for him at the moment would be to copy the Jupyter app into his /dev and change the manifest based on usage but that seems clumsy. Perhaps there’s a form entry that would be useful that I’m missing.

John

jeff.ohrstrom · October 18, 2021, 2:25pm

If the user is a developer then they can change the job name, perhaps dynamically.

The user could drop an info.md.erb file in the root of the dev project and add notes to the card.

Here’s how we use this feature to add instructions to our Rstudio app about how to load modules into the app.

github.com

OSC/bc_osc_rstudio_server/blob/master/info.md.erb

### Importing modules with R
**Import module function**

```
source(file.path(Sys.getenv("LMOD_PKG"), "init/R"))
```

**Load system module**

```
module("load", "blast")
```

**Load custom module**

```
module("use", "~/local/share/lmodfiles")
module("load", "MyModuleA")
```

system · April 16, 2022, 2:26pm

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Job Name Change between 1.7 and 1.8? Get Help	3	468	March 14, 2022
Tracking usage with ondemand_exporter Get Help question	2	102	September 23, 2024
Adding a Job Label Field in Job Composer form Feature Requests and Roadmap Discussion	1	409	March 27, 2023
Interactive "module avail" button in form.yml and Job Viewer Feature Requests and Roadmap Discussion feature-request	24	797	March 8, 2024
RStudio job URL is wrong Get Help question	10	34	July 15, 2024

Job tagging/notation

Related topics