UMIACS - User contributions [en]

AddingUMIACSCertificateAuthority

2024-01-08T15:57:12Z

Osalami: /* Safari and Google Chrome (macOS) */

===Introduction===

When you visit webpages encrypted with SSL, you may be presented with a warning about the site's security certificate not being trusted. These are normally important screens to pay attention to on the internet as a whole and UMIACS goes to great lengths to maintain a secure environment for our users. However, it is not cost effective to provide commercial certs for all our public facing certificates. In order to keep costs down we provide a UMIACS CA (certificate authority) that enables your web browser to trust our secure webpages. The following steps explain how to import this certificate based on your preferred web browser.

===Windows===

For most Windows browsers (Chrome, Firefox, Edge and Internet Explorer), certificate authorities are handled by Windows itself. These are the steps required to accept the certificate:

* Click [https://wiki.umiacs.umd.edu/umiacs/images/7/7d/CA-cert.crt UMIACS Certificate Authority] to download the file.
* Open the file and click "Install Certificate".
*; [[File:UMIACSCA1.png]]
* In the dialog box opened, click "Next".
* Choose "Place all certificates in the following store".
* Choose "Browse", in the dialog box opened, Choose "Trusted Root Certification Authorities" and click "Ok".
*; [[File:UMIACSCA2.png]]
* Click "Next" and then "Finish".
* If you get a Security Warning asking if you want to install this certificate, click "Yes".
*; [[File:UMIACSCA3.png]]
* You should receive a success message similar to the following:
*; [[File:UMIACSCA4.png]]
* You may need to restart your browser for the change to take effect.

===Safari and Google Chrome (macOS)===

For most macOS browsers (excluding Firefox), certificate authorities are handled by macOS itself. This process requires administrator access. If you do not have administrator access and you are using a UMIACS-supported Mac, please contact [[HelpDesk|Staff]]. Otherwise, here are the steps required to accept the certificate:

* Click [https://wiki.umiacs.umd.edu/umiacs/images/7/7d/CA-cert.crt UMIACS Certificate Authority] to download the file.
* Open Keychain Access (Located in the Others group in Launchpad)
* Go to the Systems > Certificates
* Open the UMIACS Certificate Authority file by double-clicking it (should be located in your downloads folder).
* Enter your administrator password or use your fingerprint on the dialog box that appears.
[[Image:KeychainAcces1.png|500px]]
* Right-click the certificate that was just added and select the "Get Info" section.
[[Image:KeychainAccess2.png|500px]]
* Select "Always Trust" option in the "When using this certificate" dropdown ("Trust" > "When using this certificate" > "Always Trust")
* Close the certificate and keychain access window.
* Enter the administrator credentials to add this certificate for all users of the system
[[Image:KeychainAccess3.png|500px]]
* You may need to restart your browser for the change to take effect.

===Other Browsers (Unix)===

If you are using a browser other than Firefox in Unix, the process is more complicated than the above methods and may depend on your particular Unix distribution. If you need assistance with this please contact [[HelpDesk|UMIACS Staff]].

File:KeychainAccess3.png

2024-01-08T15:47:42Z

Osalami:

File:KeychainAccess2.png

2024-01-08T15:47:08Z

Osalami:

File:KeychainAcces1.png

2024-01-08T15:46:36Z

Osalami:

Network/Troubleshooting/DNS

2024-01-08T15:19:19Z

Osalami:

We have experienced a number of issues in the past with home internet providers not correctly handling DNS resolution for UMIACS hostnames. This can affect connectivity to UMIACS.

In the face of this, here are a few last-resort options for bypassing problematic DNS services.

===[http://en.wikipedia.org/wiki/Google_Public_DNS Google DNS]===
IP Addresses:
* 8.8.8.8
* 8.8.4.4

===[http://en.wikipedia.org/wiki/OpenDNS OpenDNS]===
IP Addresses:
* 208.67.222.222
* 208.67.220.220
* 208.67.222.220
* 208.67.220.222

==How to change your default DNS servers==
* '''Windows:'''
::# Go to Control Panel -> Network and Internet -> Network and Sharing Center.
::# Click "Change adapter settings" on the left.
::# Right click on the network adapter you're using, choose "Properties" from the context menu.
::# Select "Internet Protocol Version 4 (TCP/IPv4)" and click on the "Properties" button.
::# If not selected, choose "Use the following DNS server addresses:"
::# Enter the public DNS addresses you desire to use.
::# Click OK, and close the remaining windows.

* '''macOS:''' System Settings > Network > Wi-Fi/Ethernet > Details > DNS

* '''Linux:''' Edit your /etc/resolv.conf file and change the IP addresses after "nameserver" to any of those listed above.

==Manual Lookup==
If you are having problems getting to UMIACS hosts, you can use our name servers to resolve those specific host names and then connect using the IP addresses you lookup. Our name servers are 128.8.120.19, 128.8.120.50, and 128.8.132.75. To use this information to get the IP address of the host somehost.umiacs.umd.edu, you would use the command <code>nslookup somehost.umiacs.umd.edu 128.8.120.19</code>, from a Windows, macOS, or Linux command prompt / terminal.

Network/VPN

2024-01-08T15:10:56Z

Osalami:

{{Note | As of August 14th 2022, Pulse Secure Client has been rebranded as Ivanti Secure Access Client. Please follow this link for more information on this - [[Network/VPN/Ivanti|Ivanti Secure Access Client]]. }}

A virtual private network (VPN) extends a private network across a public network, and enables users to send and receive data across shared or public networks as if their computing devices were directly connected to the private network. UMIACS currently provides VPN access through a [https://www.pulsesecure.net/ Pulse Secure] SSL VPN.

Please note that enrollment in our [[MFA]] is mandatory to connect using the UMIACS VPN. Enrollment steps can be found [[Duo | here]].

==Getting Connected==
Once connected to the VPN you can use the [[Remote_Desktop| Remote Desktop client]] to access a Windows machine, as well as access a number of other non-public UMIACS resources.

===Client Setup===
* '''Operating Systems:'''
:* [[Network/VPN/Windows|Configuring a Windows VPN Connection]]
:* [[Network/VPN/macOS|Configuring a macOS VPN Connection]]
:* [[Network/VPN/Ubuntu|Configuring an Ubuntu VPN Connection]]
* '''Mobile Devices:'''
:* [[Network/VPN/Mobile | Configuring a Mobile (iOS/Android) device]]

===VPN Troubleshooting===
* [[Network/VPN/Troubleshooting|Troubleshoot common VPN issues]]

===Multi-Factor Authentication===
* [[Network/VPN/MFA | Configuring Multi-Factor authentication]]

FTP/macOS/Finder

2024-01-04T21:11:53Z

Osalami:

[[FTP]] services can be accessed from supported machines running macOS. This is a guide on how to access the UMIACS FTP service using macOS Finder.

==Opening up macOS Finder==
To open up macOS Finder, click on the macOS Finder icon on the dock at the bottom of your desktop.
[[Image:OS X Dock.png|thumb|left|700px|The Finder icon is highlighted with a red square]]
 

==Accessing the public folder==
The owner of the public folder can publish and modify files from a supported machine. External collaborators can only download files published by the owner.

===Access as an owner===
First, bring up the address bar in macOS Finder by pressing Command + Shift + G.
[[Image:OS X Finder Path Empty.png|thumb|left|700px|Bring up the "go to the folder"]]
 
In order to access your public folder,
type in the following into the address bar of Finder:
<pre>/fs/ftp/pub/<username> - where <username> should be replaced with your username</pre>
[[Image:OS X FTP Pub Path.png|thumb|left|600px|Enter the path to access the pub folder]]
 

===Access as a collaborator===
External collaborators can access the public folders through the Finder's "Connect to Server" feature. The "Connect to Server" window can be opened by pressing <kbd>Command + K</kbd> on your keyboard.
[[Image:OS X Open Finder Connect.png|thumb|left|600px|Open the "Connect to Server" window]]
 
Then, enter the following address into the server address bar and then click on the "Connect" button.
<pre>ftp://ftp.umiacs.umd.edu/pub/<username> - where <username> should be replaced with the desired collaborator's username</pre>
[[Image:OS X Finder Connect Address.png|thumb|left|600px|Enter the path to access the public folder]]
 
After that you will be prompted with a window where you should choose to connect as a guest and then click "Connect" once more.
[[Image:FTPGuest.png|thumb|left|600px|Select Guest]]
 
[[Image:FTPConnect.png|thumb|left|600px|Click Connect]]

File:FTPConnect.png

2024-01-04T21:11:35Z

Osalami:

File:FTPGuest.png

2024-01-04T21:10:36Z

Osalami:

File:OS X Finder Select Guest.png

2024-01-04T21:07:19Z

Osalami: Osalami reverted File:OS X Finder Select Guest.png to an old version

File:OS X Finder Select Guest.png

2024-01-04T21:06:51Z

Osalami: Osalami reverted File:OS X Finder Select Guest.png to an old version

File:OS X Finder Connect Guest.png

2024-01-04T21:04:03Z

Osalami: Osalami uploaded a new version of File:OS X Finder Connect Guest.png

File:OS X Finder Select Guest.png

2024-01-04T21:03:46Z

Osalami: Osalami uploaded a new version of File:OS X Finder Select Guest.png

File:OS X Finder Connect Address.png

2024-01-04T21:03:19Z

Osalami: Osalami uploaded a new version of File:OS X Finder Connect Address.png

File:OS X Open Finder Connect.png

2024-01-04T21:02:43Z

Osalami: Osalami uploaded a new version of File:OS X Open Finder Connect.png

File:OS X FTP Pub Path.png

2024-01-04T21:00:21Z

Osalami: Osalami uploaded a new version of File:OS X FTP Pub Path.png

File:OS X Finder Path Empty.png

2024-01-04T20:59:13Z

Osalami: Osalami uploaded a new version of File:OS X Finder Path Empty.png

File:Screenshot 2024-01-04 at 2.58.31 PM.png

2024-01-04T20:58:42Z

Osalami:

Creating service admin user on macOS

2024-01-04T19:24:30Z

Osalami: Updating Images and Directions for Sonoma

When taking an Apple product to the [https://it.umd.edu/terrapin-tech Terrapin Tech store], it is critical that you create a Service Admin User on your computer before having it serviced. The technicians at the store require an admin user name and password, and if the pre-existing password is the same as your UMIACS domain login password, revealing it to the technicians would represent a security vulnerability. To remedy this, you must create a new temporary user account with administrator privileges that the technicians can use to service your machine.

==Creating the new account==
* Make sure you are logged in to an administrator account on your MacBook.
# Navigate to System Preferences. (Click on the Apple Logo at the top lefthand side of the screen, and select "System Preferences" from the dropdown menu.)
# From the System Preferences menu, select "Users and Groups" .
# On the righthand side of the screen where it lists the users currently on the machine, click on the 'Add User' button.
# By default, the new account will be set to a Standard account. Select the "New User" dropdown menu and choose "Administrator" from the list.
#: [[Image:AdminSonoma1.png|400px]]
# The new user's full name should be "Service Admin," and the account name should be "serviceadmin".
# The password is up to you, so long as it's not the same as your UMIACS account password or your UMD Directory ID password.
#: [[Image:AdminSonoma.png|400px]]
# Select "Create User".

When prompted by the Terrapin Tech sore, you should give this account's credentials to the technician, '''not''' your UMIACS account credentials. Once the service is completed, the account can be deleted.

File:AdminSonoma1.png

2024-01-04T19:23:20Z

Osalami:

File:AdminSonoma.png

2024-01-04T19:20:45Z

Osalami:

Creating service admin user on OSX

2024-01-04T16:58:24Z

Osalami: Osalami moved page Creating service admin user on OSX to Creating service admin user on macOS: OSX is now macOS

#REDIRECT [[Creating service admin user on macOS]]

Creating service admin user on macOS

2024-01-04T16:58:24Z

Osalami: Osalami moved page Creating service admin user on OSX to Creating service admin user on macOS: OSX is now macOS

When taking an Apple product to the [https://it.umd.edu/terrapin-tech Terrapin Tech store], it is critical that you create a Service Admin User on your computer before having it serviced. The technicians at the store require an admin user name and password, and if the pre-existing password is the same as your UMIACS domain login password, revealing it to the technicians would represent a security vulnerability. To remedy this, you must create a new temporary user account with administrator privileges that the technicians can use to service your machine.

==Creating the new account==
* Make sure you are logged in to an administrator account on your MacBook.
# Navigate to System Preferences. (Click on the Apple Logo at the top lefthand side of the screen, and select "System Preferences" from the dropdown menu.)
# From the System Preferences menu, select "Users and Groups" .
# At the bottom left corner of the window, click the lock to allow changes to your settings. It will most likely require your password to make changes.
# On the lefthand side of the screen where it lists the users currently on the machine, click on the '+' button to add a new user.
# By default, the new account will be set to a Standard account. Select the "New Account" dropdown menu and choose "Administrator" from the list.
#: [[Image:Administrator.png|400px]]
# The new user's full name should be "Service Admin," and the account name should be "serviceadmin".
# The password is up to you, so long as it's not the same as your UMIACS account password or your UMD Directory ID password.
#: [[Image:CompletedUserAccount.png|400px]]
# Select "Create User".

When prompted by the Terrapin Tech sore, you should give this account's credentials to the technician, '''not''' your UMIACS account credentials. Once the service is completed, the account can be deleted.

Nexus/Vulcan

2023-10-02T19:41:15Z

Osalami: Adding UVG as a dataset in vulcan-datasets per UMIACS-119082

The [https://wiki.umiacs.umd.edu/cfar/index.php/Vulcan Vulcan] standalone cluster's compute nodes have folded into [[Nexus]] as of the scheduled [[MonthlyMaintenanceWindow | maintenance window]] for August 2023 (Thursday 08/17/2023, 5-8pm).

The Nexus cluster already has a large pool of compute resources made possible through leftover funding for the [[Iribe | Brendan Iribe Center]]. Details on common nodes already in the cluster (Tron partition) can be found [[Nexus/Tron | here]].

The Vulcan cluster's standalone submission nodes <code>vulcansub00.umiacs.umd.edu</code> and <code>vulcansub01.umiacs.umd.edu</code> were retired on Thursday, September 21st, 2023 during that month's maintenance window (5-8pm). Please use <code>nexusvulcan00.umiacs.umd.edu</code> and <code>nexusvulcan01.umiacs.umd.edu</code> for any general purpose Vulcan compute needs.

Please [[HelpDesk | contact staff]] with any questions or concerns.

==Usage==
The Nexus cluster submission nodes that are allocated to Vulcan are <code>nexusvulcan00.umiacs.umd.edu</code> and <code>nexusvulcan01.umiacs.umd.edu</code>.

All partitions, QoSes, and account names from the standalone Vulcan cluster have been moved over to Nexus. However, please note that <code>vulcan-</code> is prepended to all of the values that were present in the standalone Vulcan cluster to distinguish them from existing values in Nexus. The lone exception is the base account that was named <code>vulcan</code> in the standalone cluster (it is also named just <code>vulcan</code> in Nexus).

Here are some before/after examples of job submission with various parameters:

{| class="wikitable"
! Standalone Vulcan cluster submission command
! Nexus cluster submission command
|-
|<code>srun --partition=dpart --qos=medium --account=abhinav --gres=gpu:rtxa4000:2 --pty bash</code>
|<code>srun --partition=vulcan-dpart --qos=vulcan-medium --account=vulcan-abhinav --gres=gpu:rtxa4000:2 --pty bash</code>
|-
|<code>srun --partition=cpu --qos=cpu --pty bash</code>
|<code>srun --partition=vulcan-cpu --qos=vulcan-cpu --account=vulcan --pty bash</code>
|-
|<code>srun --partition=scavenger --qos=scavenger --account=vulcan --gres=gpu:4 --pty bash</code>
|<code>srun --partition=vulcan-scavenger --qos=vulcan-scavenger --account=vulcan --gres=gpu:4 --pty bash</code>
|}

Vulcan users (exclusively) can schedule non-interruptible jobs on Vulcan nodes with any non-scavenger job parameters. Please note that the <code>vulcan-dpart</code> partition has a <code>GrpTRES</code> limit of 100% of the available cores/RAM on all vulcan## in aggregate nodes plus 50% of the available cores/RAM on legacy## nodes in aggregate, so your job may need to wait if all available cores/RAM (or GPUs) are in use. It also has a max submission limit of 500 jobs per user simultaneously so as to not overload the cluster. This is codified by the partition QoS named '''vulcan'''.

Please note that the Vulcan compute nodes are also in the institute-wide <code>scavenger</code> partition in Nexus. Vulcan users still have scavenging priority over these nodes via the <code>vulcan-scavenger</code> partition (i.e., all <code>vulcan-</code> partition jobs (other than <code>vulcan-scavenger</code>) can preempt both <code>vulcan-scavenger</code> and <code>scavenger</code> partition jobs, and <code>vulcan-scavenger</code> partition jobs can preempt <code>scavenger</code> partition jobs).

==Nodes==
There are currently 45 [[Nexus/Vulcan/GPUs | GPU nodes]] available running a mixture of NVIDIA RTX A6000, NVIDIA RTX A5000, NVIDIA RTX A4000, NVIDIA Quadro P6000, NVIDIA GeForce GTX 1080 Ti, NVIDIA GeForce RTX 2080 Ti, and NVIDIA Tesla P100 cards. There are also 2 CPU-only nodes available.

All nodes are scheduled with the [[SLURM]] resource manager.

==Partitions==
There are three partitions available to general Vulcan [[SLURM]] users. You must specify a partition when submitting your job.

* '''vulcan-dpart''' - This is the default partition. Job allocations are guaranteed.
* '''vulcan-scavenger''' - This is the alternate partition that allows jobs longer run times and more resources but is preemptable when jobs in other <code>vulcan-</code> partitions are ready to be scheduled.
* '''vulcan-cpu''' - This partition is for CPU focused jobs. Job allocations are guaranteed.

There are a few additional partitions available to subsets of Vulcan users based on specific requirements.

==Accounts==
Vulcan has a base SLURM account <code>vulcan</code> which has a modest number of guaranteed billing resources available to all cluster users at any given time. Other faculty that have invested in Vulcan compute infrastructure have an additional account provided to their sponsored accounts on the cluster, which provides a number of guaranteed billing resources corresponding to the amount that they invested.

If you do not specify an account when submitting your job, you will receive the <code>vulcan</code> account. If your faculty sponsor has their own account, it is recommended to use that account for job submission.

The current faculty accounts are:
* vulcan-abhinav
* vulcan-djacobs
* vulcan-jbhuang
* vulcan-lsd
* vulcan-metzler
* vulcan-rama
* vulcan-ramani
* vulcan-yaser
* vulcan-zwicker

<pre>
$ sacctmgr show account format=account%20,description%30,organization%10
Account Descr Org
-------------------- ------------------------------ ----------
... ... ...
vulcan vulcan vulcan
vulcan-abhinav vulcan - abhinav shrivastava vulcan
vulcan-djacobs vulcan - david jacobs vulcan
vulcan-jbhuang vulcan - jia-bin huang vulcan
vulcan-lsd vulcan - larry davis vulcan
vulcan-metzler vulcan - chris metzler vulcan
vulcan-rama vulcan - rama chellappa vulcan
vulcan-ramani vulcan - ramani duraiswami vulcan
vulcan-yaser vulcan - yaser yacoob vulcan
vulcan-zwicker vulcan - matthias zwicker vulcan
... ... ...
</pre>

Faculty can manage this list of users via our [https://intranet.umiacs.umd.edu/directory/secgroup/ Directory application] in the Security Groups section. The security group that controls access has the prefix <code>vulcan_</code> and then the faculty username. It will also list <code>slurm://nexusctl.umiacs.umd.edu</code> as the associated URI.

You can check your account associations by running the '''show_assoc''' command to see the accounts you are associated with. Please [[HelpDesk | contact staff]] and include your faculty member in the conversation if you do not see the appropriate association.

<pre>
$ show_assoc
User Account MaxJobs GrpTRES QOS
---------- ---------------- ------- ------------- --------------------------------------------------------------------------------
... ... ... ...
abhinav abhinav 48 vulcan-cpu,vulcan-default,vulcan-high,vulcan-medium,vulcan-scavenger
abhinav vulcan 48 vulcan-cpu,vulcan-default,vulcan-medium,vulcan-scavenger
... ... ... ...
</pre>

You can also see the total number of Track-able Resources (TRES) allowed for each account by running the following command. Please make sure you give the appropriate account that you are looking for. As shown below, there is a concurrent limit of 64 total GPUs for all users not in a contributing faculty group.

<pre>
$ sacctmgr show assoc account=vulcan format=user,account,qos,grptres
User Account QOS GrpTRES
---------- ---------- -------------------- -------------
vulcan gres/gpu=64
... ...
</pre>

==QoS==
You need to decide the QOS to submit with which will set a certain number of restrictions to your job. If you do not specify a QoS when submitting your job using the <code>--qos</code> parameter, you will receive the '''vulcan-default''' QoS assuming you are using a Vulcan account.

The following <code>sacctmgr</code> command will list the current QOS. Either the <code>vulcan-default</code>, <code>vulcan-medium</code>, or <code>vulcan-high</code> QOS is required for the vulcan-dpart partition. Please note that only faculty accounts (see above) have access to the <code>vulcan-high</code> QoS.

The following example will show you the current limits that the QOS have. The output is truncated to show only relevant Vulcan QoS.
<pre>
$ show_qos
Name MaxWall MaxTRES MaxJobsPU MaxTRESPU
-------------------- ----------- ------------------------------ --------- ------------------------------
...
vulcan-cpu 2-00:00:00 cpu=1024,mem=4T 4
vulcan-default 7-00:00:00 cpu=4,gres/gpu=1,mem=32G 2
vulcan-exempt 7-00:00:00 cpu=32,gres/gpu=8,mem=256G 2
vulcan-high 1-12:00:00 cpu=16,gres/gpu=4,mem=128G 2
vulcan-janus 3-00:00:00 cpu=32,gres/gpu=10,mem=256G
vulcan-medium 3-00:00:00 cpu=8,gres/gpu=2,mem=64G 2
vulcan-sailon 3-00:00:00 cpu=32,gres/gpu=8,mem=256G gres/gpu=48
vulcan-scavenger 3-00:00:00 cpu=32,gres/gpu=8,mem=256G
...

$ show_partition_qos
Name MaxSubmitPU MaxTRESPU GrpTRES
-------------------- ----------- ------------------------------ --------------------
...
vulcan 500 cpu=1760,mem=15824G
vulcan-scavenger 500
...
</pre>

==Storage==
Vulcan has the following storage available. Please also review UMIACS [[LocalDataStorage | Local Data Storage]] policies including any volume that is labeled as scratch.

Vulcan users can also request [[Nexus#Project_Allocations | Nexus project allocations]].

===Home Directory===
You have 30GB of storage available at <code>/nfshomes/<username></code>. It has both [[Snapshots]] and [[TSM | Backups]] available if need be.

Home directories are intended to store personal or configuration files only. We encourage users to not share any data in their home directory.

===Scratch Directories===
Scratch data has no data protection including no snapshots and the data is not backed up. There are two types of scratch directories in the Vulcan compute infrastructure:
* Network scratch directory
* Local scratch directories

====Network Scratch Directory====
You are allocated 300GB of scratch space via NFS from <code>/vulcanscratch/$username</code>. '''It is not backed up or protected in any way.''' This directory is '''automounted''' so you will need to <code>cd</code> into the directory or request/specify a fully qualified file path to access this.

You may request a temporary increase of up to 500GB total space for a maximum of 120 days without any faculty approval by contacting [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu]. Once the temporary increase period is over, you will be contacted and given a one-week window of opportunity to clean and secure your data before staff will forcibly remove data to get your space back under 300GB. If you need space beyond 500GB or for longer than 120 days, you will need faculty approval and/or a project directory.

This file system is available on all submission, data management, and computational nodes within the cluster.

====Local Scratch Directories====
Each computational node that you can schedule compute jobs on has one or more local scratch directories. These are always named <code>/scratch0</code>, <code>/scratch1</code>, etc. These are almost always more performant than any other storage available to the job. However, you must stage their data within the confine of their job and stage the data out before the end of their job.

These local scratch directories have a tmpwatch job which will '''delete unaccessed data after 90 days''', scheduled via maintenance jobs to run once a month at 1am. Different nodes will run the maintenance jobs on different days of the month to ensure the cluster is still highly available at all times. Please make sure you secure any data you write to these directories at the end of your job.

===Datasets===
We have read-only dataset storage available at <code>/fs/vulcan-datasets</code>. If there are datasets that you would like to see curated and available, please see [[Datasets | this page]].

The following is the list of datasets available:
{| class="wikitable"
! Dataset
! Path
|-
| 3D-FRONT
| /fs/vulcan-datasets/3d-front
|-
| 3D-FUTURE
| /fs/vulcan-datasets/3d-future
|-
| Action Genome
| /fs/vulcan-datasets/AG
|-
| ActivityNet
| /fs/vulcan-datasets/ActivityNet
|-
| CATER
| /fs/vulcan-datasets/CATER
|-
| COVID-DA
| /fs/vulcan-datasets/COVID-DA
|-
| CelebA
| /fs/vulcan-datasets/CelebA
|-
| CelebA-HQ
| /fs/vulcan-datasets/CelebA-HQ
|-
| CelebAMask-HQ
| /fs/vulcan-datasets/CelebAMask-HQ
|-
| Charades
| /fs/vulcan-datasets/Charades
|-
| CharadesEgo
| /fs/vulcan-datasets/CharadesEgo
|-
| CIFAR10
| /fs/vulcan-datasets/cifar-10-python
|-
| CIFAR100
| /fs/vulcan-datasets/cifar-100-python
|-
| CityScapes
| /fs/vulcan-datasets/cityscapes
|-
| COCO
| /fs/vulcan-datasets/coco
|-
| Conceptual Captions
| /fs/vulcan-datasets/conceptual_captions
|-
| CUB
| /fs/vulcan-datasets/CUB
|-
| DeepFashion
| /fs/vulcan-datasets/DeepFashion
|-
| Digits
| /fs/vulcan-datasets/digits_full
|-
| Edges2handbags
| /fs/vulcan/datasets/edges2handbags
|-
| Edges2shoes
| /fs/vulcan/datasets/edges2shoes
|-
| EGTEA
| /fs/vulcan/datasets/EGTEA
|-
| emnist
| /fs/vulcan-datasets/emnist
|-
| EPIC Kitchens 2018
| /fs/vulcan-datasets/Epics-kitchen-2018
|-
| EPIC Kitchens 2020
| /fs/vulcan-datasets/EPIC-Kitchens-2020
|-
| Facades
| /fs/vulcan/datasets/facades
|-
| from_games (GTA5)
| /fs/vulcan-datasets/from_games
|-
| FFHQ
| /fs/vulcan-datasets/ffhq-dataset
|-
| FineGym
| /fs/vulcan-datasets/FineGym
|-
| Google Landmarks Dataset v2
| /fs/vulcan-datasets/google-landmark-v2
|-
| HAA500
| /fs/vulcan-datasets/haa500
|-
| HICO
| /fs/vulcan-datasets/HICO
|-
| HMDB51
| /fs/vulcan-datasets/HMDB51
|-
| Honda_100h
| /fs/vulcan-datasets/honda_100h
|-
| HPatches
| /fs/vulcan-datasets/HPatches
|-
| Human3.6M
| /fs/vulcan-datasets/human3.6
|-
| IM2GPS (test only)
| /fs/vulcan-datasets/im2gps
|-
| ImageNet
| /fs/vulcan-datasets/imagenet
|-
| iNaturalist Dataset 2021
| /fs/vulcan-datasets/inat_comp_2021
|-
| InteriorNet
| /fs/vulcan-datasets/InteriorNet
|-
| Kinetics-400
| /fs/vulcan-datasets/Kinetics-400
|-
| Labelled Faces in the Wild
| /fs/vulcan-datasets/lfw
|-
| LibriSpeech
| /fs/vulcan-datasets/LibriSpeech
|-
| LSUN
| /fs/vulcan-datasets/LSUN
|-
| LVIS
| /fs/vulcan-datasets/LVIS
|-
| Maps
| /fs/vulcan-datasets/maps
|-
| Matterport3D
| /fs/vulcan-datasets/Matterport3D
|-
| MegaDepth
| /fs/vulcan-datasets/MegaDepth
|-
| MineRL
| /fs/vulcan-datasets/MineRL
|-
| Mini-ImageNet
| /fs/vulcan-datasets/miniImagenet
|-
| MIT Indoor
| /fs/vulcan-datasets/mit_indoor
|-
| MIT Places
| /fs/vulcan-datasets/mit_places
|-
| Multi-PIE Face
| /fs/vulcan-datasets/multipie
|-
| Night2day
| /fs/vulcan-datasets/night2day
|-
| ObjectNet3D
| /fs/vulcan-datasets/ObjectNet3D
|-
| Occluded Video Instance Segmentation
| /fs/vulcan-datasets/ovis-2021
|-
| Office
| /fs/vulcan-datasets/office
|-
| Office-Home
| /fs/vulcan-datasets/office_home
|-
| omniglot
| /fs/vulcan-datasets/omniglot
|-
| OOPS
| /fs/vulcan-datasets/OOPS
|-
| OpenImagesv4
| /fs/vulcan-datasets/OpenImagesv4
|-
| PartNet
| /fs/vulcan-datasets/PartNet
|-
| Pascal VOC
| /fs/vulcan-datasets/pascal_voc
|-
| PIC (HOI-A)
| /fs/vulcan-datasets/PIC
|-
| PubLayNet
| /fs/vulcan-datasets/PubLayNet
|-
| Replica
| /fs/vulcan-datasets/Replica
|-
| ScanNet
| /fs/vulcan-datasets/ScanNet
|-
| ShapeNetCore.v2
| /fs/vulcan-datasets/ShapeNetCore.v2
|-
| Something-Something-V1
| /fs/vulcan-datasets/SomethingV1
|-
| Something-Something-V2
| /fs/vulcan-datasets/SomethingV2
|-
| SYNTHIA-RAND-CITYSCAPES
| /fs/vulcan-datasets/SYNTHIA-RAND-CITYSCAPES
|-
| TAPOS
| /fs/vulcan-datasets/TAPOS
|-
| Tiny ImageNet
| /fs/vulcan-datasets/tiny_imagenet
|-
| Tumblr GIF Description
| /fs/vulcan-datasets/TGIF
|-
| Thingi10K
| /fs/vulcan-datasets/Thingi10K
|-
| UCF101
| /fs/vulcan-datasets/UCF101
|-
| UVG
| /fs/vulcan-datasets/UVG
|-
| VirtualHomes
| /fs/vulcan-datasets/VirtualHomes
|-
| visda17
| /fs/vulcan-datasets/visda17
|-
| visda17_openset
| /fs/vulcan-datasets/VISDA
|-
| visda19
| /fs/vulcan-datasets/visda
|-
| Visual Genome
| /fs/vulcan-datasets/VG
|-
| Visual Relationship Detection
| /fs/vulcan-datasets/VRD
|-
| VOCdevkit
| /fs/vulcan-datasets/VOCdevkit
|-
| VoxCeleb2
| /fs/vulcan-datasets/VoxCeleb2
|-
| WILDS
| /fs/vulcan-datasets/WILDS
|-
| xView2
| /fs/vulcan-datasets/xView2
|-
| YCB Object Models
| /fs/vulcan-datasets/YCB
|-
| YouTube8M
| /fs/vulcan-datasets/YouTube8M
|-
| YouTubeVIS-2019
| /fs/vulcan-datasets/YouTubeVIS-2019
|-
| YouTubeVIS-2021
| /fs/vulcan-datasets/YouTubeVIS-2021
|}

===Project Storage===
Users within the Vulcan compute infrastructure can request project based allocations for up to 10TB for up to 180 days by [https://wiki.umiacs.umd.edu/umiacs/index.php/HelpDesk contacting staff] with approval from the Vulcan faculty manager (Dr. Shrivastava). These allocations will be available from <code>/fs/vulcan-projects</code> under a name that you provide when you request the allocation. Near the end of the allocation period, staff will contact you and ask if you would like to renew the allocation for up to another 180 days (requires re-approval from Dr. Shrivastava). If you are no longer in need of the storage allocation, you will need to relocate all desired data within two weeks of the end of the allocation period. Staff will then remove the allocation. If you do not respond to staff's request by the end of the allocation period, staff will make the allocation temporarily inaccessible. If you do respond asking for renewal but the original faculty approver does not respond within two weeks of the end of the allocation period, staff will also make the allocation temporarily inaccessible. If one month from the end of the allocation period is reached without both you and the faculty approver responding, staff will remove the allocation.

This data, by default, will be backed up nightly and have a limited snapshot schedule (1 daily snapshot). Upon request, staff can both exclude the data from backups and/or disable snapshots on the project storage volume. We currently have 100TB total to support these projects which includes the snapshot data for this volume.

===Object Storage===
All Vulcan users can request project allocations in the [https://obj.umiacs.umd.edu/obj/help UMIACS Object Store]. Please email staff@umiacs.umd.edu with a short project name and the amount of storage you will need to get started.

An example on how to use the umobj command line utilities can be found [https://wiki.umiacs.umd.edu/umiacs/index.php/UMobj/Example here]. A full set of documentation for the utilities can be found on the [https://gitlab.umiacs.umd.edu/staff/umobj/blob/master/README.md#umobj umobj Gitlab page].

==Migration==
===Home Directories===
The [[Nexus]] uses [[NFShomes]] home directories - if your UMIACS account was created before February 22nd, 2023, you were using <code>/cfarhomes/<username></code> as your home directory on the standalone Vulcan cluster. While <code>/cfarhomes</code> is available on Nexus, your shell initialization scripts from it will not automatically load. Please copy over anything you need to your <code>/nfshomes/<username></code> directory at your earliest convenience, as <code>/cfarhomes</code> will be retired in a two phase process:
* Fri 11/17/2023, 5pm: cfarhomes directories are made read-only
* Thu 12/21/2023, 5-8pm ([[MonthlyMaintenanceWindow |monthly maintenance window]]): cfarhomes directories are taken offline

MacOSPrinting

2023-05-21T03:54:00Z

Osalami:

__NOTOC__
We support printing from user managed macOS 11.x or later machines.

'''Note: You must be on a UMIACS network directly or connected to the [[VPN]] in order to print.'''

=System Settings=
To start, open your System Settings from the Dock or Applications folder. Once you have opened it, click '''Printers & Scanners'''.

[[Image:Ventura_Print00.png|300px]]

=Print & Fax=
On the '''Printers & Scanners''' page, create a new local printer by clicking the '''Add Printer, Scanner, or Fax...''' button that is below the printer list.

=Add Printer=
This will bring up the Add Printer dialog.

'''Note:''' If you just want basic printing, use the steps below. If you would like to enable all the advanced options for the printer, jump over this section to '''"Enabling Advanced Printer Options"'''.

* Jump over to the '''IP''' tab
* Set Protocol to '''Internet Printing Protocol - IPP'''
* Set Address to '''print.umiacs.umd.edu'''
* Set the Queue to printers/queue; in this example for cps432-3208 it would be '''printers/cps432-3208'''. You have to make sure the queue is prefixed by '''printers/'''. For clarification, the queue is typically the printer name.
* Set Name to the name of the printer you are trying to use. This makes it easily Identifiable in your list of printers.
* It will always select '''Generic Postscript Printer'''. If you need to access the more advanced features of a queue/printer or you were '''not able to print by choosing Generic Postscript Printer''', you will need to take extra steps, please see the Advanced section at the bottom of this page.
* Select Add
* You will be asked about enabling duplex. If you know the printer has the option, which is true for most of our printers, go ahead and enable it. Then hit OK. If you're not sure, just leave it disabled. You can always enable it after the queue is added.

[[Image:AddPrinter_BigSur.png]]

You should now be able to print to this printer/queue from any macOS print menu.

=Enabling Advanced Printer Features=
Some printers may have features not accessible with the default drivers provided above. If this is the case, follow the guide below to identify, and install your print drivers from their manufacturer.

'''Note:''' If you already installed the printer with generic drivers, you will need to highlight the printer and click '''-''', before attempting to add it again. You may also need a system update to get the latest drivers from Apple, if your printer does not have software drivers listed in the next steps.

'''Step 1:''' Locate your printers name and search for its Make and Model here: http://print.umiacs.umd.edu/printers/

'''Step 2:''' Follow the '''Add Printer''' steps above until you get to '''Generic Postscript Printer'''. Select '''Software''', then '''Add'''.

[[Image:SelectSoftware_BigSur.png]]

'''Step 3:''' A window labeled "Printer Software" will now pop up. Scroll through the list to find your specific make and model of printer. Click on it, and hit Ok.

'''NOTE''': If you cannot find the printer's make and model and need Advanced Printing Features, try downloading the drivers from Apple's [https://support.apple.com/kb/dl1888?locale=en_US| website] and reinstalling the printer from step 1.

[[Image:PrinterSoftware_BigSur.png]]

'''Step 4:''' Click Add on the next window and it should install your printer's software suite. You should have a list of options (if they are available) that looks similar this:

[[Image:InstallOptions_BigSur.png]]

'''Final Step:''' Enable the Options you wish to use, Click '''OK'''. You should now be able to print to this printer/queue from any macOS print menu.

=Printing With Stapler=
For print jobs using the stapler, follow the guide below. Printers with staplers are located in Iribe, in rooms 3149, 3208, 4149, 4208, and 5208.

To add/ connect to a printer with stapling capabilities:

'''Step 1:''' Follow the "Enabling Advanced Printer Features" guide until you reach Step 4.

'''Step 2:''' In the window that appears labeled "Setting up [your printer name]" set "HP 3-Bin Stapler/Stacker" to "Mailbox Mode".

[[Image:Mailbox_Mode.png|500px|]]

'''Step 3:''' Select "OK" in the bottom right corner.

'''To Print:''' To complete the print job using the stapler once the printer has been added:

'''Step 1:''' In Preview, when trying to print, select the "Show Details" button in the bottom left corner.

[[Image:Show_Settings.png|500px|]]

'''Step 2:''' In the middle right, where it says "Preview," select "Printer Features" instead of "Preview".

[[Image:Printer_Features.png|500px|]]

'''Step 3:''' Set "Feature Sets" to "Finishing".

[[Image:Finishing.png|500px|]]

'''Step 4:''' A "Staple" dropdown list will appear at the bottom of the window. Select your preferred staple option.

[[Image:Staple.png|500px|]]

'''Step 5:''' Press "Print" in the bottom right corner.

=Printing Stored Jobs=
'''Pre-requisite:''' Requires [[MacOSPrinting#Enabling_Advanced_Printer_Features | advanced print features]] to be enabled.
If you are printing a sensitive document and do not want the printer to print it right away, you can configure a stored job. The stored job lets you hold a print job until you enter a PIN to release the job. You can configure a stored job following the instructions below:

# Go to File > Print or Press Command + P to open the Printer menu.
# Select the printer where you want to send the print job.
# Click the dropdown list under Copies & Pages and select '''Job Storage'''.
#:[[File:Step03.png|400px]]
# From the Mode dropdown list, select '''Personal Job''' (or '''Stored Job''' if you want to share the document with others).
#:[[File:Step04.png|400px]]
# Leave the username to default or specify a custom username.
# Check the box '''Use PIN to Print''' and enter a 4-digit number. Hit '''Print'''.
#:[[File:Step06.png|400px]]

'''To print the stored jobs:'''
# From the Home screen of the printer tap on '''Print from Job Storage''' (or '''Print''' > '''Print from Job Storage''').
# In the '''Stored Job to Print''' screen, select the name of the folder where the job is stored. By default, the name of the folder will be your username unless you customized it earlier.
# Select the name of the document and enter the PIN.
# Hit '''Print'''.

MacOSPrinting

2023-05-21T03:51:55Z

Osalami:

__NOTOC__
We support printing from user managed macOS 11.x or later machines.

'''Note: You must be on a UMIACS network directly or connected to the [[VPN]] in order to print.'''

=System Settings=
To start, open your System Settings from the Dock or Applications folder. Once you have opened it, click '''Printers & Scanners'''.

[[Image:Ventura_Print00.png|300px]]

=Print & Fax=
On the '''Printers & Scanners''' page, create a new local printer by clicking the '''Add Printer, Scanner, or Fax...''' button that is below the printer list.

=Add Printer=
This will bring up the Add Printer dialog.

'''Note:''' If you just want basic printing, use the steps below. If you would like to enable all the advanced options for the printer, jump over this section to '''"Enabling Advanced Printer Options"'''.

* Jump over to the '''IP''' tab
* Set Protocol to '''Internet Printing Protocol - IPP'''
* Set Address to '''print.umiacs.umd.edu'''
* Set the Queue to printers/queue; in this example for cps432-3208 it would be '''printers/cps432-3208'''. You have to make sure the queue is prefixed by '''printers/'''. For clarification, the queue is typically the printer name.
* Set Name to the name of the printer you are trying to use. This makes it easily Identifiable in your list of printers.
* It will always select '''Generic Postscript Printer'''. If you need to access the more advanced features of a queue/printer or you were '''not able to print by choosing Generic Postscript Printer''', you will need to take extra steps, please see the Advanced section at the bottom of this page.
* Select Add
* You will be asked about enabling duplex. If you know the printer has the option, which is true for most of our printers, go ahead and enable it. Then hit OK. If you're not sure, just leave it disabled. You can always enable it after the queue is added.

[[Image:AddPrinter_BigSur.png]]

You should now be able to print to this printer/queue from any macOS print menu.

=Enabling Advanced Printer Features=
Some printers may have features not accessible with the default drivers provided above. If this is the case, follow the guide below to identify, and install your print drivers from their manufacturer.

'''Note:''' If you already installed the printer with generic drivers, you will need to highlight the printer and click '''-''', before attempting to add it again. You may also need a system update to get the latest drivers from Apple, if your printer does not have software drivers listed in the next steps.

'''Step 1:''' Locate your printers name and search for its Make and Model here: http://print.umiacs.umd.edu/printers/

'''Step 2:''' Follow the '''Add Printer''' steps above until you get to '''Generic Postscript Printer'''. Select '''Software''', then '''Add'''.

[[Image:SelectSoftware_BigSur.png]]

'''Step 3:''' A window labeled "Printer Software" will now pop up. Scroll through the list to find your specific make and model of printer. Click on it, and hit Ok.

'''NOTE''': If you cannot find the printer's make and model, try downloading the drivers from Apple's [https://support.apple.com/kb/dl1888?locale=en_US| website] and reinstalling the printer from step 1.

[[Image:PrinterSoftware_BigSur.png]]

'''Step 4:''' Click Add on the next window and it should install your printer's software suite. You should have a list of options (if they are available) that looks similar this:

[[Image:InstallOptions_BigSur.png]]

'''Final Step:''' Enable the Options you wish to use, Click '''OK'''. You should now be able to print to this printer/queue from any macOS print menu.

=Printing With Stapler=
For print jobs using the stapler, follow the guide below. Printers with staplers are located in Iribe, in rooms 3149, 3208, 4149, 4208, and 5208.

To add/ connect to a printer with stapling capabilities:

'''Step 1:''' Follow the "Enabling Advanced Printer Features" guide until you reach Step 4.

'''Step 2:''' In the window that appears labeled "Setting up [your printer name]" set "HP 3-Bin Stapler/Stacker" to "Mailbox Mode".

[[Image:Mailbox_Mode.png|500px|]]

'''Step 3:''' Select "OK" in the bottom right corner.

'''To Print:''' To complete the print job using the stapler once the printer has been added:

'''Step 1:''' In Preview, when trying to print, select the "Show Details" button in the bottom left corner.

[[Image:Show_Settings.png|500px|]]

'''Step 2:''' In the middle right, where it says "Preview," select "Printer Features" instead of "Preview".

[[Image:Printer_Features.png|500px|]]

'''Step 3:''' Set "Feature Sets" to "Finishing".

[[Image:Finishing.png|500px|]]

'''Step 4:''' A "Staple" dropdown list will appear at the bottom of the window. Select your preferred staple option.

[[Image:Staple.png|500px|]]

'''Step 5:''' Press "Print" in the bottom right corner.

=Printing Stored Jobs=
'''Pre-requisite:''' Requires [[MacOSPrinting#Enabling_Advanced_Printer_Features | advanced print features]] to be enabled.
If you are printing a sensitive document and do not want the printer to print it right away, you can configure a stored job. The stored job lets you hold a print job until you enter a PIN to release the job. You can configure a stored job following the instructions below:

# Go to File > Print or Press Command + P to open the Printer menu.
# Select the printer where you want to send the print job.
# Click the dropdown list under Copies & Pages and select '''Job Storage'''.
#:[[File:Step03.png|400px]]
# From the Mode dropdown list, select '''Personal Job''' (or '''Stored Job''' if you want to share the document with others).
#:[[File:Step04.png|400px]]
# Leave the username to default or specify a custom username.
# Check the box '''Use PIN to Print''' and enter a 4-digit number. Hit '''Print'''.
#:[[File:Step06.png|400px]]

'''To print the stored jobs:'''
# From the Home screen of the printer tap on '''Print from Job Storage''' (or '''Print''' > '''Print from Job Storage''').
# In the '''Stored Job to Print''' screen, select the name of the folder where the job is stored. By default, the name of the folder will be your username unless you customized it earlier.
# Select the name of the document and enter the PIN.
# Hit '''Print'''.

MacOSPrinting

2023-05-21T03:51:15Z

Osalami: /* Enabling Advanced Printer Features */

__NOTOC__
We support printing from user managed macOS 11.x or later machines.

'''Note: You must be on a UMIACS network directly or connected to the [[VPN]] in order to print.'''

=System Settings=
To start, open your System Settings from the Dock or Applications folder. Once you have opened it, click '''Printers & Scanners'''.

[[Image:Ventura_Print00.png|300px]]

=Print & Fax=
On the '''Printers & Scanners''' page, create a new local printer by clicking the '''Add Printer, Scanner, or Fax...''' button that is below the printer list.

=Add Printer=
This will bring up the Add Printer dialog.

'''Note:''' If you just want basic printing, use the steps below. If you would like to enable all the advanced options for the printer, jump over this section to '''"Enabling Advanced Printer Options"'''.

* Jump over to the '''IP''' tab
* Set Protocol to '''Internet Printing Protocol - IPP'''
* Set Address to '''print.umiacs.umd.edu'''
* Set the Queue to printers/queue; in this example for cps432-3208 it would be '''printers/cps432-3208'''. You have to make sure the queue is prefixed by '''printers/'''. For clarification, the queue is typically the printer name.
* Set Name to the name of the printer you are trying to use. This makes it easily Identifiable in your list of printers.
* It will always select '''Generic Postscript Printer'''. If you need to access the more advanced features of a queue/printer or you were '''not able to print by choosing Generic Postscript Printer''', you will need to take extra steps, please see the Advanced section at the bottom of this page.
* Select Add
* You will be asked about enabling duplex. If you know the printer has the option, which is true for most of our printers, go ahead and enable it. Then hit OK. If you're not sure, just leave it disabled. You can always enable it after the queue is added.

[[Image:AddPrinter_BigSur.png]]

You should now be able to print to this printer/queue from any macOS print menu.

=Enabling Advanced Printer Features=
Some printers may have features not accessible with the default drivers provided above. If this is the case, follow the guide below to identify, and install your print drivers from their manufacturer.

'''Note:''' If you already installed the printer with generic drivers, you will need to highlight the printer and click '''-''', before attempting to add it again. You may also need a system update to get the latest drivers from Apple, if your printer does not have software drivers listed in the next steps.

'''Step 1:''' Locate your printers name and search for its Make and Model here: http://print.umiacs.umd.edu/printers/

'''Step 2:''' Follow the '''Add Printer''' steps above until you get to '''Generic Postscript Printer'''. Select '''Software''', then '''Add'''.

[[Image:SelectSoftware_BigSur.png]]

'''Step 3:''' A window labeled "Printer Software" will now pop up. Scroll through the list to find your specific make and model of printer. Click on it, and hit Ok.

'''NOTE''': If you cannot find the printer's make and model, try downloading the drivers from Apple's [https://support.apple.com/kb/dl1888?locale=en_US| website] and reinstalling the printer

[[Image:PrinterSoftware_BigSur.png]]

'''Step 4:''' Click Add on the next window and it should install your printer's software suite. You should have a list of options (if they are available) that looks similar this:

[[Image:InstallOptions_BigSur.png]]

'''Final Step:''' Enable the Options you wish to use, Click '''OK'''. You should now be able to print to this printer/queue from any macOS print menu.

=Printing With Stapler=
For print jobs using the stapler, follow the guide below. Printers with staplers are located in Iribe, in rooms 3149, 3208, 4149, 4208, and 5208.

To add/ connect to a printer with stapling capabilities:

'''Step 1:''' Follow the "Enabling Advanced Printer Features" guide until you reach Step 4.

'''Step 2:''' In the window that appears labeled "Setting up [your printer name]" set "HP 3-Bin Stapler/Stacker" to "Mailbox Mode".

[[Image:Mailbox_Mode.png|500px|]]

'''Step 3:''' Select "OK" in the bottom right corner.

'''To Print:''' To complete the print job using the stapler once the printer has been added:

'''Step 1:''' In Preview, when trying to print, select the "Show Details" button in the bottom left corner.

[[Image:Show_Settings.png|500px|]]

'''Step 2:''' In the middle right, where it says "Preview," select "Printer Features" instead of "Preview".

[[Image:Printer_Features.png|500px|]]

'''Step 3:''' Set "Feature Sets" to "Finishing".

[[Image:Finishing.png|500px|]]

'''Step 4:''' A "Staple" dropdown list will appear at the bottom of the window. Select your preferred staple option.

[[Image:Staple.png|500px|]]

'''Step 5:''' Press "Print" in the bottom right corner.

=Printing Stored Jobs=
'''Pre-requisite:''' Requires [[MacOSPrinting#Enabling_Advanced_Printer_Features | advanced print features]] to be enabled.
If you are printing a sensitive document and do not want the printer to print it right away, you can configure a stored job. The stored job lets you hold a print job until you enter a PIN to release the job. You can configure a stored job following the instructions below:

# Go to File > Print or Press Command + P to open the Printer menu.
# Select the printer where you want to send the print job.
# Click the dropdown list under Copies & Pages and select '''Job Storage'''.
#:[[File:Step03.png|400px]]
# From the Mode dropdown list, select '''Personal Job''' (or '''Stored Job''' if you want to share the document with others).
#:[[File:Step04.png|400px]]
# Leave the username to default or specify a custom username.
# Check the box '''Use PIN to Print''' and enter a 4-digit number. Hit '''Print'''.
#:[[File:Step06.png|400px]]

'''To print the stored jobs:'''
# From the Home screen of the printer tap on '''Print from Job Storage''' (or '''Print''' > '''Print from Job Storage''').
# In the '''Stored Job to Print''' screen, select the name of the folder where the job is stored. By default, the name of the folder will be your username unless you customized it earlier.
# Select the name of the document and enter the PIN.
# Hit '''Print'''.

SSH/Keys

2023-05-21T02:57:50Z

Osalami:

SSH can utilize public key encryption to authenticate and authorize users. This can be considered more secure especially if you secure your private key with a pass-phrase. The keys themselves are not susceptible to brute force attacks like normal passwords over SSH are.

==Overview==
;Prerequisites
#If using batch clusters (e.g. [[SLURM]]) please read [[SSH/Keys#Batch clusters | Batch clusters]] prior to creating a new key.
#Determine your OS (and if Windows, what you will be using to create the key)
#*Windows
#**Git Bash: follow instructions for Linux/MacOS/Bash and Git Bash (for Windows)
#**PuTTY: follow instructions for Windows (and PuTTY subsections)
#**TTSSH2: follow instructions for Windows (and TTSSH2 subsections)
#**[[BashForWindows10 | Windows Subsystem for Linux (WSL)]]: follow instructions for 'Linux/MacOS/Bash and Git Bash (for Windows)'
#*Linux: follow instructions for 'Linux/MacOS/Bash and Git Bash (for Windows)'
#*MacOS: follow instructions for 'Linux/MacOS/Bash and Git Bash (for Windows)'
;Steps
#[[SSH/Keys#Create and store the key pair | Create and store the key pair]]
#[[SSH/Keys#Copy the public key | Copy the public key]]
#If Windows, [[SSH/Keys#Adding Keys to SSH Clients (Windows Only) | Adding Keys to SSH Clients (Windows Only)]]
;Additional Considerations
#The [[SSH/Keys#SSH Agents | SSH Agents]] section is not a required component of creating and using an SSH key, but can be very useful if you choose to create a password to protect your SSH key, but find yourself needing to enter that password many times in a session. [[SSH/Keys#SSH Agents | SSH Agents]] allow you to temporarily use your SSH key without a password for a set period of time. Please see the [[SSH/Keys#SSH Agents | SSH Agents]] section for more information.

==Create and store the key pair==

The first step is to generate a key which will create two files filled with long strings of characters. A public key file that you may distribute to any machine you want to use it on and a private key that needs to be kept secure. '''Allowing anyone to read this private key will compromise the security of the key and could allow someone to access any resources secured by this key without your consent.''' There are a number of different key types but <code>rsa</code> is the most compatible.

===Windows===
;Git Bash
:See [[SSH/Keys#Linux.2FMacOS.2FBash_and_Git_Bash_.28for_Windows.29 | Linux/MacOS/Bash and Git Bash (for Windows)]]
;PuTTY
# Click on the start menu and search for PuTTYgen. Open the application
# Verify that you are attempting to create an "SSH2 RSA" key by clicking on the appropriate box
# Click generate and follow the instructions for generating your keys
# Add passphrase if wanted and save both the public and private keys
;TTSSH2
# Open the application
# Cancel the first box
# Go to setup on the menu bar and go to SSH KeyGenerator
# Click generate and follow the instructions for generating your key
# Add passphrase if wanted and save both the public and private keys

===Linux/MacOS/Bash and Git Bash (for Windows)===
;Create a new key with a password
You can run the command <code>ssh-keygen -t rsa</code> to generate the new public and private key. It will prompt you for a file to create the private key and then for the public key append <code>.pub</code> extension and store it in the same directory. Pressing enter at the passphrase step twice will create a key without a pass-phrase.

Note: If you change the file in which to save the key, please ensure that it still starts with 'id', such as 'id_umiacs_rsa'.

Example: <pre>
-bash-4.2$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa):
Created directory '/home/username/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.
The key fingerprint is:
32:bf:db:74:1b:7e:d7:c6:4b:b5:6f:a8:82:55:3f:bf username@localhost.localdomain
The key's randomart image is:
+--[ RSA 2048]----+
| |
| |
| |
| . |
| o S . . .|
| + . o o|
| .o. o B.|
| .+.o o+ O|
| o...+o E+|
+-----------------+
</pre>

;Create a new key without a password
You can simplify the existing example above by telling it you do not want a pass-phrase and can run the command <code>ssh-keygen -t rsa -N ""</code>.

Note: If you change the file in which to save the key, please ensure that it still starts with 'id', such as 'id_umiacs_rsa'.

Example: <pre>
-bash-4.2$ ssh-keygen -t rsa -N ""
Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa):
Created directory '/home/username/.ssh'.
Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.
The key fingerprint is:
ff:7a:99:28:fc:63:d6:10:44:4c:2e:68:76:44:76:7a username@localhost.localdomain
The key's randomart image is:
+--[ RSA 2048]----+
| .+++ |
| + +o |
| + +.E |
| o . o. |
| S . |
| .. |
| . .+ o |
| o =.= |
| =o+. |
+-----------------+
</pre>

;Modify permissions
Modify the permissions of your <tt>.ssh</tt> directory as well as the private key file that you just created with <tt>chmod</tt>.

<pre>
chmod 700 ~/.ssh
chmod 600 ~/.ssh/id_rsa
</pre>

If you named your file something other than id_rsa, change <tt>id_rsa</tt> to the name of the file.

==Copy the public key==
Once you have a generated a key pair you will want to add it to one or more computers to allow you to access them.

===Windows===
For Windows hosts you can use [http://winscp.net/eng/download.php WinSCP] to copy the public key file onto a remote host. The root file system for the Bash Subsystem for Windows is located under C:\Users\username>\AppData\Local\lxss\

===Linux/MacOS/Bash and Git Bash (for Windows)===
This can be done with the <code>ssh-copy-id</code> command and it will prompt you the first time for your current password ('''NOT your pass-phrase'''). You can replace localhost with any other hostname you want to copy the key to. You can also specify a alternate user or identity file if you need to, please <code>man ssh-copy-id</code> for more information within your terminal. This command will ensure that not only it copies your key but secures the file so that no one can tamper and add additional authorized keys to the file on the remote host.

Example: <pre>
-bash-4.2$ ssh-copy-id localhost
/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
username@localhost's password:

Number of key(s) added: 1

Now try logging into the machine, with: "ssh 'localhost'"
and check to make sure that only the key(s) you wanted were added.
</pre>

==Adding Keys to SSH Clients (Windows Only)==
;PuTTY
# Open PuTTY and enter the Fully Qualified Domain Name for the host you wish to connect to.
# Go to the Connections tab on the side panel and click on the data subsection.
# Under data enter your default user into the first box. (Auto-login Username)
# Go to the SSH section of the side panel and then go to the Auth Section.
# Under Auth click on the browse and navigate to the saved private key.
# Go back to session on the side panel and save your settings by typing in a name in saved sessions pressing the save button.
;TTSSH2
# Open the application.
# Cancel the first box.
# Go to setup on the menu bar and go to SSH Authentication.
# Enter your username, Click on the option labeled "Use RSA ... key to log in", then use the private key button located next to this line to navigate to your private key file, and click Ok.

==Batch clusters==
Our [[SLURM]] clusters process jobs in batch and require the ability to SSH without entering a password. When creating a key for use with [[SLURM]], follow the above instructions for creating keys without passwords.

After creating this key pair please make sure you follow the [[SSH/Keys#Copy_the_public_key | copy the public key]] instructions above to <code>localhost</code>. This will ensure that your key will be usable on all the cluster nodes since they have a shared home directory.

==SSH Agents==
While it is very useful to protect your SSH key pair with a pass-phrase it can very time consuming to re-type the pass-phrase over and over. SSH provides a agent that runs in the background and allow you add a key(s) to it with a time limit that they will be unlocked for.

<pre>
ssh-agent bash
ssh-add -t $TIME
</pre>

The time specified by <code>-t</code> is specified in seconds.

Example:
(The following would start a bash shell with passwordless SSH active for 30 minutes.)
<pre>
ssh-agent bash
ssh-add -t 1800
</pre>

You will be prompted for your passphrase and, when entered correctly, you will be able to SSH without entering a password. You can check what keys are load when you are running inside a ssh-agent by using the command <code>ssh-add -l</code>.

Example: <pre>
bash-4.2$ ssh-add -l
2048 ee:83:10:c8:2f:2c:17:5e:ef:80:42:7e:ff:75:9e:53 /home/username/.ssh/id_rsa (RSA)
</pre>

NFShomes

2023-05-21T02:51:47Z

Osalami:

===/nfshomes===
Automounted [[NFS]] file system that houses users' [[Nexus]] home directories. This file system has regular backups with our [[TSM]] service and has [[Snapshots]] for easy user restores.

Found on supported [[OSSupport#UNIX | UNIX]] and [[OSSupport#MacOS | MacOS]] systems as (substituting $username with your UMIACS username)

/nfshomes/$username

If you need additional access you can mount this file system using [[CIFS]] from many operating systems (including Windows) by accessing it as (substituting $username with your UMIACS username)

\\data.isilon.umiacs.umd.edu\nfshomes\$username

[[CIFS]] access is limited to machines in the domain. Please use the [[VPN]] if you need access from outside UMIACS networks (including the wireless).