https://wiki.umiacs.umd.edu/umiacs/api.php?action=feedcontributions&user=Liam&feedformat=atomUMIACS - User contributions [en]2024-03-29T07:19:18ZUser contributionsMediaWiki 1.39.6https://wiki.umiacs.umd.edu/umiacs/index.php?title=ClassAccounts&diff=9396ClassAccounts2020-09-21T22:15:20Z<p>Liam: </p>
<hr />
<div>UMIACS Class Accounts are currently intended to support classes being sponsored by the [[CML|Center for Machine Learning]].<br />
<br />
You will be notified by email that you have an account to redeem. If you have not received an email, please contact your TA. Once you do perform the redemption of your account you will need to wait until you get a confirmation email that your account has been installed. This is done in batch once a day on days that the University is open for business.<br />
<br />
Once notified that your account has been installed you can access the following class submission host(s) using [[SSH]] with your assigned username and the password you provided:<br />
<br />
<pre><br />
class.umiacs.umd.edu<br />
</pre><br />
<br />
You may not run computational jobs on this submission host and you must schedule your jobs with the [[SLURM]] workload manager. You can also find out more with the public documentation for the [https://slurm.schedmd.com/quickstart.html Slurm Workload Manager].<br />
<br />
You will need to note the following information that class accounts only have access to the following and you may be required to explicitly set each of these in your submission parameters.<br />
<br />
* Partition - <code>class</code><br />
* Account - <code>class</code><br />
* QoS - <code>default</code><br />
<br />
Any questions or issues with the cluster must be first made through your TA.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Jekyll&diff=9392Jekyll2020-09-21T14:54:46Z<p>Liam: </p>
<hr />
<div>[https://jekyllrb.com/ Jekyll] is a blog-aware, static site generator. Rather that relying on a server<br />
side scripting language and a database, as many CMS solutions often do,<br />
Jekyll allows you to quickly deploy your site to any web tree that can serve<br />
static files (perfect for the [[OBJbox | Object Store]]!). Jekyll provides a templating<br />
language and data format that allows you to design your site using HTML, CSS,<br />
and Javascript and then render in the site's content. This separation of<br />
design and content allows for easy editing and reuse of your own custom<br />
desgin templates and those made by others. When ready to update the content,<br />
Jekyll compiles your templates and content files into full HTML!<br />
<br />
A great example of a Jekyll-generated site is the [https://intranet.umiacs.umd.edu/ UMIACS Intranet page]!<br />
<br />
==Getting Started==<br />
These instructions are taken from the official Jekyll [https://jekyllrb.com/docs/ quickstart guide].<br />
# Install all the [https://jekyllrb.com/docs/installation/ prerequisites] to run Jekyll.<br />
# Install the jekyll and bundler gems. <pre>gem install jekyll bundler</pre><br />
# Create a new Jekyll site at ./mysite (use a better name of your choosing). <pre>jekyll new mysite</pre><br />
# Change into your new directory. <pre>cd mysite</pre><br />
# Build the site and make it available on a local server. <pre>bundle exec jekyll serve</pre><br />
# Browse to http://localhost:4000<br />
<br />
==Publishing a Jekyll Site==<br />
We have instructions to get started [https://gitlab.umiacs.umd.edu/docker/jekyll-builder here] on how to publish your site to the Object Store. It can be configured to publish automatically every time you push updates to [[GitLab]].</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Jekyll&diff=9391Jekyll2020-09-21T14:53:23Z<p>Liam: </p>
<hr />
<div>[https://jekyllrb.com/ Jekyll] is a blog-aware, static site generator. Rather that relying on a server<br />
side scripting language and a database, as many CMS solutions often do,<br />
Jekyll allows you to quickly deploy your site to any web tree that can serve<br />
static files (perfect for the [[OBJbox | Object Store]]!). Jekyll provides a templating<br />
language and data format that allows you to design your site using HTML, CSS,<br />
and Javascript and then render in the site's content. This separation of<br />
design and content allows for easy editing and reuse of your own custom<br />
desgin templates and those made by others. When ready to update the content,<br />
Jekyll compiles your templates and content files into full HTML!<br />
<br />
A great example of a Jekyll-generated site is the [https://intranet.umiacs.umd.edu/ UMIACS Intranet page]!<br />
<br />
==Getting Started==<br />
These instructions are taken from the official Jekyll [https://jekyllrb.com/docs/ quickstart guide].<br />
# Install all the [https://jekyllrb.com/docs/installation/ prerequisites] to run Jekyll.<br />
# Install the jekyll and bundler gems. <pre>gem install jekyll bundler</pre><br />
# Create a new Jekyll site at ./myblog. <pre>jekyll new myblog</pre><br />
# Change into your new directory. <pre>cd myblog</pre><br />
# Build the site and make it available on a local server. <pre>bundle exec jekyll serve</pre><br />
# Browse to http://localhost:4000<br />
<br />
==Publishing a Jekyll Site==<br />
We have instructions to get started [https://gitlab.umiacs.umd.edu/docker/jekyll-builder here] on how to publish your site to the Object Store. It can be configured to publish automatically every time you push updates to [[GitLab]].</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=OBJ&diff=9390OBJ2020-09-19T02:54:18Z<p>Liam: /* Getting Started */</p>
<hr />
<div>= UMIACS Object Store =<br />
An object store is a web-based storage solution focused on reliability, scalability and security. It is best suited for public content storage/distribution, archiving data or secure data sharing between users. Our Object Storage can be used through the [https://obj.umiacs.umd.edu/obj web interface], the command line [[UMobj]] utilities, third-party graphical [[S3Clients | clients]], and even programmatically using many popular programming languages. We support a subset of the Amazon Simple Storage Services [http://docs.aws.amazon.com/AmazonS3/latest/API/Welcome.html (S3) API], built around a technology called [http://ceph.com/ Ceph].<br />
<br />
= Getting Started =<br />
UMIACS users are allocated 50GB of storage. Faculty are allocated 1TB. To get started, [https://obj.umiacs.umd.edu/obj log in] and you will be redirected to the initial help page. You can also find the link from our https://intranet.umiacs.umd.edu site as "OBJbox Object Store".</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Jekyll&diff=9365Jekyll2020-09-04T14:52:34Z<p>Liam: Created page with "Jekyll is a blog-aware, static site generator. Rather that relying on a server side scripting language and a database, as many CMS solutions often do, Jekyll allows you to qui..."</p>
<hr />
<div>Jekyll is a blog-aware, static site generator. Rather that relying on a server<br />
side scripting language and a database, as many CMS solutions often do,<br />
Jekyll allows you to quickly deploy your site to any web tree that can serve<br />
static files (perfect for the Object Store!). Jekyll provides a templating<br />
language and data format that allows you to design your site using HTML, CSS,<br />
and Javascript and then render in the site's content. This separation of<br />
design and content allows for easy editing and reuse of your own custom<br />
desgin templates and those made by others. When ready to update the content,<br />
Jekyll compiles your templates and content files into full HTML!<br />
<br />
A great example of a Jekyll-generated site is the UMIACS Intranet page!<br />
<br />
==Create a Jekyll Site==<br />
We have a template with instructions to get started [https://gitlab.umiacs.umd.edu/docker/jekyll-builder here].</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=UMobj&diff=9290UMobj2020-06-17T15:58:19Z<p>Liam: </p>
<hr />
<div>The UMobj suite of utilities provide command-line access to the UMIACS Object Store. UMobj is preinstalled on all UMIACS-supported linux machines.<br />
<br />
==When to use UMobj==<br />
Use umobj if:<br />
* you have a large number of files to upload (hundreds or thousands of files)<br />
* you are uploading large files (files greater than 4GB in size)<br />
<br />
==Supported object storage clusters==<br />
* https://obj.umiacs.umd.edu/obj<br />
<br />
==Setup==<br />
We highly recommend setting a few environmental variables containing your credentials for<br />
convenience. When logged into the Object Store web interface (see list above), you can<br />
find these credentials on the user page. E.g. https://obj.umiacs.umd.edu/obj/user/<br />
<br />
For example, if you use the <tt>bash</tt> shell, you can add something like the following to your<br />
<tt>.bashrc</tt> or <tt>.bash_profile</tt>.<br />
<br />
<pre><br />
export OBJ_ACCESS_KEY_ID="31sdfadDFAHFDN+344qOEIS"<br />
export OBJ_SECRET_ACCESS_KEY="NDSMK3233adfahadflkkPDSH092DSJKDKDJKFDLSFLNK"<br />
export OBJ_SERVER="obj.umiacs.umd.edu"<br />
</pre><br />
<br />
Or in tcsh you can do the following or add it into your <tt>.tcshrc</tt>.<br />
<br />
<pre><br />
setenv OBJ_ACCESS_KEY_ID "31sdfadDFAHFDN+344qOEIS"<br />
setenv OBJ_SECRET_ACCESS_KEY "NDSMK3233adfahadflkkPDSH092DSJKDKDJKFDLSFLNK"<br />
setenv OBJ_SERVER "obj.umiacs.umd.edu"<br />
</pre><br />
<br />
==Detailed Usage==<br />
<br />
For an example of how to use UMobj, please see [[ UMobj/Example ]].<br />
<br />
For complete usage information, please see the [[GitLab]] page for [https://gitlab.umiacs.umd.edu/staff/umobj/blob/master/README.md#umobj umobj].</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Services&diff=9289Services2020-06-12T20:43:50Z<p>Liam: </p>
<hr />
<div>UMIACS provides a wide range of services in order to help further the research of it's members. The categories listed below serve as a general grouping, as services not specifically mentioned in a category may be available.<br />
<br />
==UMIACS Service Categories==<br />
<br />
<br />
<br />
;[[Services/Compute | Computational Resources]] <br />
: Workstations, Laptops, HPC, Virtualization<br />
;[[Services/CommonPool | Common-Pool Resources]]<br />
: OpenLab Cluster<br />
;[[Services/Data | Data Storage and Backup]] <br />
: Services to assist with data management and distribution<br />
;[[Services/EMail | Electronic Mail]]<br />
: Locally hosted E-Mail services.<br />
;[[Services/EquipmentLoans | Equipment Loans]]<br />
: Laptops, Projectors, Data Storage<br />
;[[Services/Logistics | Logistics]] <br />
: Ordering, Procurement, Receiving<br />
;[[Services/OnSite | On-Site Services]]<br />
: Network Access, Printing<br />
;[[Services/Support | Technical Support]] <br />
:Hardware and OS support<br />
;[[Services/Collaboration | Web-based Collaborative Tools]] <br />
: Revision Control, Data Sharing<br />
;[[Services/Web | Web Hosting]]<br />
:User Webspace, Lab Webspace, Project Pages</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Services/Support&diff=9288Services/Support2020-06-12T20:43:09Z<p>Liam: </p>
<hr />
<div>UMIACS provides hardware and operating system (OS) support for university-owned systems across its various labs and centers. <br />
<br />
== Hardware Services==<br />
* In-warranty hardware diagnostic and replacement<br />
* Hardware Integration<br />
<br />
==Operating System Services==<br />
* OS Deployment and integration with other UMIACS Services<br />
* Security Updates<br />
* Backups<br />
* University-Licensed Software<br />
<br />
==Contact UMIACS Technical Support==<br />
{|<br />
|'''Mail: ''' <br />
|staff@umiacs.umd.edu<br />
|-<br />
|'''Phone: ''' <br />
|[tel:+13014051775 (301) 405-1775]<br />
|-<br />
|'''Help Desk: ''' <br />
|3109 Iribe Center<br />
|}</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=HelpDesk&diff=9287HelpDesk2020-06-12T20:41:40Z<p>Liam: /* How to Contact Support */</p>
<hr />
<div>The UMIACS Help Desk provides Technical Support and Equipment procurement.<br />
<br />
; Help Desk Location<br />
: 3109 Brendan Iribe Center for Computer Science and Engineering<br />
; Virtual Help Desk Hours during COVID-19<br />
: 9:00am - 5:00pm Monday - Friday. (Excluding University Holidays)<br />
<br />
==How to Contact Support==<br />
; Email<br />
: [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu]<br />
; Telephone<br />
: [tel:+13014051775 (301) 405-1775]<br />
; [[Jira | JIRA Request Tracker]]</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=AlternativePickup&diff=9286AlternativePickup2020-06-12T20:40:40Z<p>Liam: </p>
<hr />
<div>==Overview==<br />
In response to the University entering phase 1 of reopening, the UMIACS Technical Staff will be offering contactless curbside pickup for items you have ordered through staff or pickup / drop-off of items you have loaned out from us or need to give to us for service. We are providing this during the hours of 11am-2pm M-F at the circle in parking lot GG1 behind the A.V. Williams building.<br />
<br />
==Procedure==<br />
Please let us know that you want to pick up or drop something off by [[HelpDesk | contacting staff]] and letting us acknowledge and confirm your request '''before''' coming on-campus. We will not be able to service you if you arrive without letting us know beforehand.<br />
<br />
Please provide in your initial request:<br />
* Your name<br />
* What you are looking to pick up or drop off. Note: For large or heavy items, we may request that they only be picked up using car transportation to prevent accidental damage while being carried off on foot.<br />
* If applicable, the color, make, and model of vehicle that you are planning on stopping by in<br />
* The rough 15-minute window that you are planning on stopping by in<br />
<br />
During pickup:<br />
* '''Please ensure you have a photo ID.''' Staff will be checking for ID before handing off any items.<br />
* '''If picking up on foot''':<br />
** Call the Help Desk at [tel:+13014051775 (301) 405-1775] when you are physically next to the circle in parking lot GG1 behind AVW.<br />
** We will bring out your items on a sanitized cart. We will verify your ID and have you take the items off the cart. <br />
* '''If picking up with a car''':<br />
** Call the Help Desk at [tel:+13014051775 (301) 405-1775] when you are physically parked in the circle in parking lot GG1 behind AVW.<br />
** We will bring out your items on a sanitized cart. When staff arrives, please stay in your vehicle. <br />
** We will verify your ID and then ask that you ''open your trunk or side door'', and place the items in your vehicle.<br />
<br />
==Map==<br />
[[File:Curbside_pickup.png]]<br />
<br />
'''From the main entrance to campus (off US Rt. 1):'''<br />
# Make your first right to turn onto Paint Branch Drive.<br />
# Continue straight past the Brendan Iribe Center and Wind Tunnel buildings on your right.<br />
# Continue straight at the stop sign at Stadium Drive and straight past the Engineering Annex and A.V. Williams buildings on your right.<br />
# Make a right at the stop sign immediately past A.V. Williams to enter lot GG1.<br />
# Follow the path through the parking lot to reach the circle behind the A.V. Williams building.<br />
<br />
'''From the Paint Branch Drive entrance (off MD Rt. 193):'''<br />
# Continue straight past the Xfinity Center and recreational fields as well as parking lots RR2 and XX1 on your right.<br />
# Continue straight at the stop sign at Regents Drive and straight past the Biomolecular Sciences and A. James Clark Hall buildings on your right.<br />
# Make a left at the stop sign immediately past A. James Clark Hall to enter lot GG1.<br />
# Follow the path through the parking lot to reach the circle behind the A.V. Williams building.<br />
<br />
For a full campus map, please visit https://maps.umd.edu/map/.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=AlternativePickup&diff=9285AlternativePickup2020-06-12T20:35:37Z<p>Liam: </p>
<hr />
<div>==Overview==<br />
In response to the University entering phase 1 of reopening, the UMIACS Technical Staff will be offering contactless curbside pickup for items you have ordered through staff or pickup / drop-off of items you have loaned out from us or need to give to us for service. We are providing this during the hours of 11am-2pm M-F at the circle in parking lot GG1 behind the A.V. Williams building.<br />
<br />
==Procedure==<br />
Please let us know that you want to pick up or drop something off by [[HelpDesk | contacting staff]] and letting us acknowledge and confirm your request '''before''' coming on-campus. We will not be able to service you if you arrive without letting us know beforehand.<br />
<br />
Please provide in your initial request:<br />
* Your name<br />
* What you are looking to pick up or drop off. Note: For large or heavy items, we may request that they only be picked up using car transportation to prevent accidental damage while being carried off on foot.<br />
* If applicable, the color, make, and model of vehicle that you are planning on stopping by in<br />
* The rough 15-minute window that you are planning on stopping by in<br />
<br />
During pickup:<br />
* '''Please ensure you have a photo ID.''' Staff will be checking for ID before handing off any items.<br />
* '''If picking up on foot''':<br />
** Call the Help Desk at 301-405-1775 when you are physically next to the circle in parking lot GG1 behind AVW.<br />
** We will bring out your items on a sanitized cart. We will verify your ID and have you take the items off the cart. <br />
* '''If picking up with a car''':<br />
** Call the Help Desk at 301-405-1775 when you are physically parked in the circle in parking lot GG1 behind AVW.<br />
** We will bring out your items on a sanitized cart. When staff arrives, please stay in your vehicle. <br />
** We will verify your ID and then ask that you ''open your trunk or side door'', and place the items in your vehicle.<br />
<br />
==Map==<br />
[[File:Curbside_pickup.png]]<br />
<br />
'''From the main entrance to campus (off US Rt. 1):'''<br />
# Make your first right to turn onto Paint Branch Drive.<br />
# Continue straight past the Brendan Iribe Center and Wind Tunnel buildings on your right.<br />
# Continue straight at the stop sign at Stadium Drive and straight past the Engineering Annex and A.V. Williams buildings on your right.<br />
# Make a right at the stop sign immediately past A.V. Williams to enter lot GG1.<br />
# Follow the path through the parking lot to reach the circle behind the A.V. Williams building.<br />
<br />
'''From the Paint Branch Drive entrance (off MD Rt. 193):'''<br />
# Continue straight past the Xfinity Center and recreational fields as well as parking lots RR2 and XX1 on your right.<br />
# Continue straight at the stop sign at Regents Drive and straight past the Biomolecular Sciences and A. James Clark Hall buildings on your right.<br />
# Make a left at the stop sign immediately past A. James Clark Hall to enter lot GG1.<br />
# Follow the path through the parking lot to reach the circle behind the A.V. Williams building.<br />
<br />
For a full campus map, please visit https://maps.umd.edu/map/.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=AlternativePickup&diff=9284AlternativePickup2020-06-12T20:27:04Z<p>Liam: </p>
<hr />
<div>==Overview==<br />
In response to the University entering phase 1 of reopening, the UMIACS Technical Staff will be offering contactless curbside pickup for items you have ordered through staff or pickup / drop-off of items you have loaned out from us or need to give to us for service. We are providing this during the hours of 11am-2pm M-F at the circle in parking lot GG1 behind the A.V. Williams building.<br />
<br />
==Procedure==<br />
Please let us know that you want to pick up or drop something off by [[HelpDesk | contacting staff]] and letting us acknowledge and confirm your request '''before''' coming on-campus. We will not be able to service you if you arrive without letting us know beforehand.<br />
<br />
Please provide in your initial request:<br />
* Your name<br />
* What you are looking to pick up or drop off<br />
* If applicable, the color, make, and model of vehicle that you are planning on stopping by in<br />
* The rough 15-minute window that you are planning on stopping by in<br />
<br />
During pickup:<br />
* '''Please ensure you have a photo ID.''' Staff will be checking for ID before handing off any items.<br />
* '''If picking up on foot''':<br />
** Call the Help Desk at 301-405-1775 when you are physically next to the circle in parking lot GG1 behind AVW.<br />
** We will bring out your items on a sanitized cart. We will verify your ID and have you take the items off the cart. <br />
* '''If picking up with a car''':<br />
** Call the Help Desk at 301-405-1775 when you are physically parked in the circle in parking lot GG1 behind AVW.<br />
** We will bring out your items on a sanitized cart. When staff arrives, please stay in your vehicle. <br />
** We will verify your ID and then ask that you ''open your trunk or side door'', and place the items in your vehicle.<br />
<br />
==Map==<br />
[[File:Curbside_pickup.png]]<br />
<br />
'''From the main entrance to campus (off US Rt. 1):'''<br />
# Make your first right to turn onto Paint Branch Drive.<br />
# Continue straight past the Brendan Iribe Center and Wind Tunnel buildings on your right.<br />
# Continue straight at the stop sign at Stadium Drive and straight past the Engineering Annex and A.V. Williams buildings on your right.<br />
# Make a right at the stop sign immediately past A.V. Williams to enter lot GG1.<br />
# Follow the path through the parking lot to reach the circle behind the A.V. Williams building.<br />
<br />
'''From the Paint Branch Drive entrance (off MD Rt. 193):'''<br />
# Continue straight past the Xfinity Center and recreational fields as well as parking lots RR2 and XX1 on your right.<br />
# Continue straight at the stop sign at Regents Drive and straight past the Biomolecular Sciences and A. James Clark Hall buildings on your right.<br />
# Make a left at the stop sign immediately past A. James Clark Hall to enter lot GG1.<br />
# Follow the path through the parking lot to reach the circle behind the A.V. Williams building.<br />
<br />
For a full campus map, please visit https://maps.umd.edu/map/.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=AlternativePickup&diff=9283AlternativePickup2020-06-12T20:21:56Z<p>Liam: </p>
<hr />
<div>==Overview==<br />
In response to the University entering phase 1 of reopening, the UMIACS Technical Staff will be offering contactless curbside pickup for items you have ordered through staff or pickup / drop-off of items you have loaned out from us or need to give to us for service. We are providing this during the hours of 11am-2pm M-F at the circle in parking lot GG1 behind the A.V. Williams building.<br />
<br />
==Procedure==<br />
Please let us know that you want to pick up or drop something off by [[HelpDesk | contacting staff]] and letting us acknowledge and confirm your request '''before''' coming on-campus. We will not be able to service you if you arrive without letting us know beforehand.<br />
<br />
Please provide in your initial request:<br />
* Your name<br />
* What you are looking to pick up or drop off<br />
* If applicable, the color, make, and model of vehicle that you are planning on stopping by in<br />
* The rough 15-minute window that you are planning on stopping by in<br />
<br />
During pickup:<br />
* '''Please ensure you have a photo ID.''' Staff will be checking for ID before handing any items off.<br />
* Call the Help Desk at 301-405-1775 when you are physically parked or otherwise waiting in the circle in parking lot GG1 behind AVW.<br />
* We will bring out your items on a sanitized cart. When staff arrives, please stay in your vehicle. <br />
* We will verify your ID and then ask that you open your trunk or side door, and place the items in your vehicle.<br />
<br />
==Map==<br />
[[File:Curbside_pickup.png]]<br />
<br />
'''From the main entrance to campus (off US Rt. 1):'''<br />
# Make your first right to turn onto Paint Branch Drive.<br />
# Continue straight past the Brendan Iribe Center and Wind Tunnel buildings on your right.<br />
# Continue straight at the stop sign at Stadium Drive and straight past the Engineering Annex and A.V. Williams buildings on your right.<br />
# Make a right at the stop sign immediately past A.V. Williams to enter lot GG1.<br />
# Follow the path through the parking lot to reach the circle behind the A.V. Williams building.<br />
<br />
'''From the Paint Branch Drive entrance (off MD Rt. 193):'''<br />
# Continue straight past the Xfinity Center and recreational fields as well as parking lots RR2 and XX1 on your right.<br />
# Continue straight at the stop sign at Regents Drive and straight past the Biomolecular Sciences and A. James Clark Hall buildings on your right.<br />
# Make a left at the stop sign immediately past A. James Clark Hall to enter lot GG1.<br />
# Follow the path through the parking lot to reach the circle behind the A.V. Williams building.<br />
<br />
For a full campus map, please visit https://maps.umd.edu/map/.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=AlternativePickup&diff=9282AlternativePickup2020-06-12T20:20:27Z<p>Liam: /* Procedure */</p>
<hr />
<div>==Overview==<br />
In response to the University entering phase 1 of reopening, the UMIACS Technical Staff will be offering curbside pickup for items you have ordered through staff or pickup / drop-off of items you have loaned out from us or need to give to us for service. We are providing this during the hours of 11am-2pm M-F at the circle in parking lot GG1 behind the A.V. Williams building.<br />
<br />
==Procedure==<br />
Please let us know that you want to pick up or drop something off by [[HelpDesk | contacting staff]] and letting us acknowledge and confirm your request '''before''' coming on-campus. We will not be able to service you if you arrive without letting us know beforehand.<br />
<br />
Please provide in your initial request:<br />
* Your name<br />
* What you are looking to pick up or drop off<br />
* If applicable, the color, make, and model of vehicle that you are planning on stopping by in<br />
* The rough 15-minute window that you are planning on stopping by in<br />
<br />
During pickup:<br />
* '''Please ensure you have a photo ID.''' Staff will be checking for ID before handing any items off.<br />
* Call the Help Desk at 301-405-1775 when you are physically parked or otherwise waiting in the circle in parking lot GG1 behind AVW.<br />
* We will bring out your items on a sanitized cart. When staff arrives, please stay in your vehicle. <br />
* We will verify your ID and then ask that you open your trunk or side door, and place the items in your vehicle.<br />
<br />
==Map==<br />
[[File:Curbside_pickup.png]]<br />
<br />
'''From the main entrance to campus (off US Rt. 1):'''<br />
# Make your first right to turn onto Paint Branch Drive.<br />
# Continue straight past the Brendan Iribe Center and Wind Tunnel buildings on your right.<br />
# Continue straight at the stop sign at Stadium Drive and straight past the Engineering Annex and A.V. Williams buildings on your right.<br />
# Make a right at the stop sign immediately past A.V. Williams to enter lot GG1.<br />
# Follow the path through the parking lot to reach the circle behind the A.V. Williams building.<br />
<br />
'''From the Paint Branch Drive entrance (off MD Rt. 193):'''<br />
# Continue straight past the Xfinity Center and recreational fields as well as parking lots RR2 and XX1 on your right.<br />
# Continue straight at the stop sign at Regents Drive and straight past the Biomolecular Sciences and A. James Clark Hall buildings on your right.<br />
# Make a left at the stop sign immediately past A. James Clark Hall to enter lot GG1.<br />
# Follow the path through the parking lot to reach the circle behind the A.V. Williams building.<br />
<br />
For a full campus map, please visit https://maps.umd.edu/map/.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=AlternativePickup&diff=9281AlternativePickup2020-06-12T20:19:50Z<p>Liam: /* Procedure */</p>
<hr />
<div>==Overview==<br />
In response to the University entering phase 1 of reopening, the UMIACS Technical Staff will be offering curbside pickup for items you have ordered through staff or pickup / drop-off of items you have loaned out from us or need to give to us for service. We are providing this during the hours of 11am-2pm M-F at the circle in parking lot GG1 behind the A.V. Williams building.<br />
<br />
==Procedure==<br />
Please let us know that you want to pick up or drop something off by [[HelpDesk | contacting staff]] and letting us acknowledge and confirm your request '''before''' coming on-campus. We will not be able to service you if you arrive without letting us know beforehand.<br />
<br />
Please provide in your initial request:<br />
* Your name<br />
* What you are looking to pick up or drop off<br />
* If applicable, the color, make, and model of vehicle that you are planning on stopping by in<br />
* The rough 15-minute window that you are planning on stopping by in<br />
<br />
During pickup:<br />
* '''Please ensure you have a photo ID.''' Staff will be checking for ID before handing any items off.<br />
* Call the Help Desk at 301-405-1775 when you are physically parked in the circle in parking lot GG1 behind AVW.<br />
* We will bring out your items on a sanitized cart. When staff arrives, please stay in your vehicle. <br />
* We will verify your ID and then ask that you open your trunk or side door, and place the items in your vehicle.<br />
<br />
==Map==<br />
[[File:Curbside_pickup.png]]<br />
<br />
'''From the main entrance to campus (off US Rt. 1):'''<br />
# Make your first right to turn onto Paint Branch Drive.<br />
# Continue straight past the Brendan Iribe Center and Wind Tunnel buildings on your right.<br />
# Continue straight at the stop sign at Stadium Drive and straight past the Engineering Annex and A.V. Williams buildings on your right.<br />
# Make a right at the stop sign immediately past A.V. Williams to enter lot GG1.<br />
# Follow the path through the parking lot to reach the circle behind the A.V. Williams building.<br />
<br />
'''From the Paint Branch Drive entrance (off MD Rt. 193):'''<br />
# Continue straight past the Xfinity Center and recreational fields as well as parking lots RR2 and XX1 on your right.<br />
# Continue straight at the stop sign at Regents Drive and straight past the Biomolecular Sciences and A. James Clark Hall buildings on your right.<br />
# Make a left at the stop sign immediately past A. James Clark Hall to enter lot GG1.<br />
# Follow the path through the parking lot to reach the circle behind the A.V. Williams building.<br />
<br />
For a full campus map, please visit https://maps.umd.edu/map/.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=PythonVirtualEnv&diff=9239PythonVirtualEnv2020-05-25T14:37:08Z<p>Liam: /* Activating the VirtualEnv */</p>
<hr />
<div>A virtual environment is an isolated working copy of Python, which allows you to work on specific projects without affecting others. It creates an environment that has its own installation directories and that does not share libraries with other virtualenv environments (and optionally doesn’t access the globally-installed libraries either).<br />
<br />
==Basic Usage==<br />
The following steps outline how to create a virtual environment using the system Python. Please note that Python virtual environments are not relocatable after being installed, so consider the install location carefully. Home directories may have [[Quota | quotas]] that are not suited for very large environments.<br />
<br />
====Creating the virtual environment on Python 3====<br />
Python 3 on [[RHEL7]] comes with the virtualenv module built in. If you are on [[Ubuntu]], please contact [[HelpDesk | UMIACS Staff]] to install venv on your machine.<br />
<pre><br />
$ python3 -m venv env<br />
</pre><br />
<br />
====Creating the virtual environment on Python 2 (deprecated)====<br />
<pre><br />
$ git clone https://github.com/pypa/virtualenv.git<br />
$ python virtualenv/virtualenv.py env<br />
New python executable in env/bin/python<br />
Installing setuptools.............done.<br />
</pre><br />
<br />
====Activating the VirtualEnv====<br />
You will need to use the 'source' command to load it into your shell environment every time you open a new shell.<br />
<pre><br />
$ source env/bin/activate<br />
</pre><br />
<br />
{{Note|<b>Note:</b> tcsh/csh shell users should run <code>source env/bin/activate.csh</code> instead.}}<br />
<br />
We also suggest the first thing you do is to ensure you have an updated version of pip installed in your environment. Make sure you have sourced your environment, and then run the following:<br />
<br />
<pre><br />
$ pip install --upgrade pip<br />
</pre><br />
<br />
In bash and tcsh, the environment can be deactivated by typing <code>deactivate</code><br />
<br />
====Installing Python Modules====<br />
Once you have created your virtual environment and sourced it, you can install additional modules using the 'pip' command.<br />
<br />
<pre><br />
$ pip install nose<br />
Collecting nose<br />
Downloading nose-1.3.7-py3-none-any.whl (154 kB)<br />
|████████████████████████████████| 154 kB 12.5 MB/s<br />
Installing collected packages: nose<br />
Successfully installed nose-1.3.7<br />
</pre><br />
<br />
====Listing installed Python Modules====<br />
<pre><br />
(env)$ pip freeze<br />
nose==1.3.7<br />
</pre><br />
<br />
====Uninstalling Python Modules====<br />
'pip' can also be used to remove a module from the environment.<br />
<pre><br />
$ pip uninstall nose<br />
Found existing installation: nose 1.3.7<br />
Uninstalling nose-1.3.7:<br />
Would remove:<br />
/nfshomes/liam/env/bin/nosetests<br />
/nfshomes/liam/env/bin/nosetests-3.4<br />
/nfshomes/liam/env/lib/python3.7/site-packages/nose-1.3.7.dist-info/*<br />
/nfshomes/liam/env/lib/python3.7/site-packages/nose/*<br />
/nfshomes/liam/env/man/man1/nosetests.1<br />
Proceed (y/n)? y<br />
Successfully uninstalled nose-1.3.7<br />
</pre><br />
<br />
===Switching between virtual environments===<br />
To switch between different environments, simply deactivate your current virtual environment, and source another.<br />
<pre><br />
(env)$ which python<br />
~/env/bin/python<br />
<br />
(env)$ deactivate <br />
<br />
$ source my-other-env/bin/activate<br />
<br />
(my-other-env)$ which python<br />
~/my-other-env/bin/python<br />
</pre><br />
<br />
==Using a different Python version==<br />
To create a virtual environment that uses a version of python that is different than the system default, create the virtualenv with your target version of Python. This could be a Python build we provide via [[Modules]], or one you've built yourself. Virtualenv will pick up the first python version it finds in your $PATH, or you can direct it to a specific location with the "--python" flag.<br />
<br />
<pre><br />
$ module load Python3<br />
<br />
$ which python3<br />
/opt/local/stow/Python3-3.8.1/bin/python3<br />
</pre><br />
<br />
'''Important:''' virtualenv will include any modules listed in your PYTHONPATH when initializing the virtual environment. To ensure a vanilla environment, it might be a good idea to verify your PYTHONPATH is empty.<br />
<br />
<pre><br />
$ echo $PYTHONPATH<br />
<br />
</pre><br />
<br />
<pre><br />
$ python3 -m venv env36<br />
<br />
$ source env36/bin/activate<br />
(env36) $ which python<br />
~/env36/bin/python<br />
</pre></div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=EmailMigration&diff=9210EmailMigration2020-05-12T14:29:08Z<p>Liam: fix typo</p>
<hr />
<div>UMIACS will be winding down its mailbox [[Email]] services by June 30th 2020 to comply with the UMD [https://umd.service-now.com/itsupport?id=kb_article_view&sysparm_article=KB0015077 Institutional Email] standard. This includes both our Exchange and IMAP [[Email]] service offerings.<br />
<br />
==Procedure==<br />
The Division of IT is handling the migration for some individuals that currently forward their UMD mail to their UMIACS mailbox. We sent an email to all users that are covered by this on May 1st 2020 with the subject line "UMIACS Email Migration".<br />
<br />
===If you received this email===<br />
'''Your UMIACS email will begin forwarding to your UMD mailbox at 9am on May 26th 2020.'''<br />
<br />
# Reply to the email by May 15th 2020 if you would like your UMIACS mailbox to be included on the list to be imported into UMD's Gmail system by the Division of IT and/or if you would like an archive of your UMIACS mailbox.<br />
# Begin checking new email at your UMD Gmail mailbox after May 26th 2020 at 9am.<br />
<br />
===If you did not receive this email===<br />
Follow the steps [[EmailMigration/SelfMigration | here]] to update your forwarding address to either your @umd.edu email address if you have one, or another address you would like to receive your UMIACS email at if you do not, no later than June 1st 2020.<br />
<br />
==FAQ==<br />
<br />
===How do I login to the UMD Gmail system?===<br />
You can access your email through a browser by visiting https://mail.google.com/a/umd.edu/. You should be able to log into this right now with your <code>username@umd.edu</code> email address to confirm that you have access. No email will show up in this interface until your migration has been performed.<br />
<br />
If you already have a personal Gmail/Google account logged in, you may need to add a new Google account for your @umd.edu account. You can find out how to do this by reading [https://support.google.com/accounts/answer/1721977?co=GENIE.Platform%3DDesktop&hl=en Google documentation] on this topic. The article also provides information on how to switch accounts.<br />
<br />
===What is the timeline for these migrations?===<br />
We notified everyone about the timeline for these migrations on May 1st 2020. You will need to notify UMIACS Technical Staff by May 15th if you want the Division of IT to migrate your existing email mailboxes to the UMD Gmail system as part of the email migration. The default will be to not migrate your mailbox if you do not reply affirmatively.<br />
<br />
Migrations will begin on May 26th 2020.<br />
<br />
===What happens during my migration if I am being handled by the Division of IT?===<br />
* On May 26th 2020 we will modify your email forward in UMIACS to be your @g.umd.edu (UMD Gmail) address at 9am. This will ensure that there is no mail loop (instead of @umd.edu which still may forward to your @umiacs.umd.edu address) and will immediately divert any new email to the UMD Gmail system. We will then notify you at your @umiacs.umd.edu address (which should show up in your @g.umd.edu mailbox) that the forward is in place. You will be receiving and may start sending and replying to new email in the UMD Gmail system as soon as you receive this notification.<br />
* If you have chosen to migrate your mailboxes, we will immediately make a mail archive of your mailboxes (depending on the size of your mailboxes this could take some time).<br />
* We will then notify DivIT that your forward is now in place. DivIT will then update your @umd.edu forward to your @g.umd.edu forward and start the import of your mailboxes if provided. This process of importing your existing email may take some time. DivIT will notify you when it is complete.<br />
<br />
'''During this process you will still be able to log into your existing UMIACS email system and interact with your existing emails. However you will no longer receive any new emails into your UMIACS mailboxes.'''<br />
<br />
===Should I migrate my existing email mailboxes to the UMD Gmail?===<br />
You will be given a choice as part of the migration to have your existing mailbox migrated to the UMD Gmail platform or not. There are a few things to consider when making this decision.<br />
<br />
First, UMD Gmail can not hold export controlled data. Since export control regulations have changed several times since emails have been stored on UMIACS servers, we cannot provide a blanket guarantee that moving all emails into Google will be compliant with federal regulations, and we ask that you make this determination separately before requesting the transfer of your emails.<br />
<br />
Second, you may have a very large hierarchical folder arrangement for your messages. Gmail only supports labels. If you have a deep hierarchical arrangement of folders, this may not translate the way you expect into Gmail's web interface and may decrease performance of the page load. You can see Google's documentation of this [https://support.google.com/mail/answer/118708?co=GENIE.Platform%3DDesktop&hl=en here].<br />
<br />
===Can I use my current desktop client to read email with UMD Gmail?===<br />
The Division of IT only explicitly supports the [https://mail.google.com/a/umd.edu/ web based] offering.<br />
<br />
===What will happen to my email stored at UMIACS after June 30th 2020?===<br />
We will be archiving all user mailboxes into our long term [[Archives|archives]]. You may request a copy of your email as part of the migration process and we will provide it in an archive format that you may import into a local mail client for offline use.<br />
<br />
Archives will be provided in the format that they were archived in. The formats will be [https://en.wikipedia.org/wiki/Personal_Storage_Table PST] for Exchange users and [https://en.wikipedia.org/wiki/Mbox MBOX] for IMAP users.<br />
<br />
===Can people still send email to my @umiacs.umd.edu address?===<br />
Yes. Once the migration is completed, any email to @umiacs.umd.edu will be forwarded to your @umd.edu UMD Gmail address.<br />
<br />
===Can I still send email as my @umiacs.umd.edu address from UMD Gmail?===<br />
Yes. You will need to set up your @umiacs.umd.edu address on your UMD mailbox as a mail alias by following Google's documentation of this [https://support.google.com/mail/answer/22370?hl=en here]. Our SMTP server is smtp.umiacs.umd.edu.<br />
<br />
===What if I forward my email to another service? Will I be impacted?===<br />
Users with accounts in UMIACS that can be identified as having an appointment at the University of Maryland will be required to have their UMIACS Email forward point to their @umd.edu email address by June 30th 2020. Users without an appointment at the University of Maryland will be required to forward their email to an address of their choosing.<br />
<br />
===What about any mailing lists or mail aliases in UMIACS?===<br />
Mailing lists and mail aliases will continue to operate as they do currently in UMIACS.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Printing&diff=9166Printing2020-05-02T20:37:22Z<p>Liam: </p>
<hr />
<div>==Printing==<br />
===OS-specific printing guides===<br />
* [[WindowsPrinting | Windows Printing Guide]]<br />
* [[OSXPrinting | macOS Printing Guide]]<br />
* [[CUPS | Linux Printing Guide (RHEL and Ubuntu)]]<br />
* [[UbuntuPrinting | Self-supported Ubuntu Printing Guide]]<br />
<br />
If you are printing from a wireless network or non-UMIACS network, you will need to first connect to the UMIACS [[VPN]]. Afterwards, follow the above instructions for your operating system.<br />
<br />
===Other Printing Pages===<br />
* [[PrinterQueueNaming | Selecting A Print Queue (Color/Driver)]]<br />
* [[UNIXPrinting | Legacy UNIX Printing Guide (Linux and Solaris)]]<br />
* [[UMIACS Public Printers]]<br />
* [[PrinterTroubleshooting | Printer troubleshooting]]</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Archives&diff=9165Archives2020-05-02T20:36:53Z<p>Liam: </p>
<hr />
<div>=UMIACS Archives=<br />
When UMIACS archives data we hold onto the archive for a period of 5 years.<br />
<br />
In general, we archive the following:<br />
<br />
* the primary drive from hosts with persistent local data (Windows, macOS)<br />
* accounts that are archived and deleted (including metadata, network home directory/directories, and GitLab repositories)<br />
* mailboxes that no longer receive mail (i.e. the forward address that used to go to the mailbox has changed)<br />
<br />
We may not archive the following:<br />
<br />
* tmp and scratch directories (as discussed on our page about [[LocalDataStorage |data storage]])<br />
* external drives that were attached to a machine<br />
* Data that migrated forward to a new machine<br />
* Data that was handed off into the care of the end-user or PI<br />
* Data from drives that failed and was not under backup protection, that is unavailable for us to archive<br />
* Data from self-supported machines</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Archives&diff=9153Archives2020-04-30T01:22:55Z<p>Liam: </p>
<hr />
<div>=UMIACS Archives=<br />
<br />
When UMIACS archives data we hold onto the archive for a period of 5 years.<br />
<br />
We archive the following:<br />
<br />
* hosts with persistent local data (Windows, macOS)<br />
* accounts that are archived and deleted (including metadata, network home directory and GitLab)</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=EmailMigration&diff=9121EmailMigration2020-04-28T01:26:37Z<p>Liam: </p>
<hr />
<div>UMIACS will be winding down its mailbox Email services by June 30th 2020 to comply with the UMD [https://umd.service-now.com/itsupport?id=kb_article_view&sysparm_article=KB0015077 Institutional Email] standard. This includes both our Exchange and IMAP service offerings.<br />
<br />
== FAQ ==<br />
<br />
* '''Can I use my current desktop client to read email with UMD Gmail?''' - The Division of IT only explicitly supports the [https://mail.google.com/a/umd.edu/ web based] offering. <br />
<br />
* '''Should I migrate my existing email mailboxes to the UMD Gmail?''' - Users will be given an option as part of the migration to have their existing mailboxes migrated to the UMD Gmail platform. There are a number of things to consider. First UMD Gmail can not hold export controlled data. Since export control regulations have changed several times since emails have been stored on UMIACS servers, we cannot provide a blanket guarantee that moving all emails into Google will be compliant with federal regulations, and we ask that each of you make this determination separately before requesting the transfer of your emails. Second many users have a very hierarchical folder arrangement for their messages. Gmail only supports tags and if you have a deep hierarchical arrangement of folders this may not translate well into Gmail's web interface.<br />
<br />
* '''What will happen with emails stored at UMIACS after June 30th 2020?''' - We will be archiving all user mailboxes into our long term archives for a minimum of 10 years. Users may request a copy of their emails as part of the migration progress and we will provide it in an archive format that users may import into their local mail clients for offline use.<br />
<br />
* '''What if I forward my email to another service? Will I be impacted?''' - Users with accounts in UMIACS that can be identified as having an appointment at the University of Maryland will be required to have their UMIACS Email forward point to their @umd.edu email address by June 30th 2020. Users without an appointment at the University of Maryland will be allowed to forward their email to an address of their choosing.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Duo&diff=9111Duo2020-04-22T21:58:18Z<p>Liam: </p>
<hr />
<div>[https://www.duo.com Duo] is the multi-factor authentication ([[MFA]]) solution for both UMD centralized information technology resources (DivIT) and UMIACS local resources. Multi-factor solutions ensure that you have something you know (i.e. your password) and something you have (phone/tablet/token). This ensures that phishing and other attempts to secure your password do not result in an account compromise and protect you and your data from unauthorized access.<br />
<br />
<b>Enrollment is discrete and must be done for both UMD (if you have a UMD appointment) and UMIACS individually</b>. You can enroll the same phone for both of these services, but not the same token (if you use a token for UMD already). The UMIACS Single Sign-On and our [[VPN]] require Duo authentication. <br />
<br />
[[File:duo_login.png|400px|thumb|left|Duo Login Prompt]]<br />
<br />
==Enrollment==<br />
Please refer to Duo's [https://guide.duo.com/enrollment Enrollment] guide which has comprehensive information on how to enroll your devices. The recommended place at UMIACS to sign in to enroll is our [https://intranet.umiacs.umd.edu/directory/auth/login Directory application].<br />
<br />
We encourage users to enroll with their smart phone as it provides the most seamless experience. We also support iOS/Android Tablets, landlines, and U2F [https://fidoalliance.org/certification/fido-certified-products/ FIDO] authenticator tokens (though these do not work with our VPN or MFA SSH services).<br />
<br />
==Management==<br />
Users can manage their UMIACS Duo settings as part of the required login to the [https://intranet.umiacs.umd.edu/directory/info Directory Application]. Please follow the Duo guide for [https://guide.duo.com/manage-devices Managing Devices] when you see the Duo login prompt.<br />
<br />
We suggest users register using a mobile phone or tablet that is always in your personal possession. If/When you upgrade or dispose of your currently registered phone/tablet please consider enrolling your new device before getting rid of your old device. Activation of your new device will require you to successfully authenticate with a currently registered device. If you no longer have the device but have kept the mobile phone number registered you can select <b>Call Me</b> to have Duo call you to authenticate your session to manage/enroll your devices. If you do not have access to your previous device(s) or the phone number you will need to contact [mailto:staff@umiacs.umd.edu UMIACS staff] for assistance.<br />
<br />
==Offline Use==<br />
<br />
<gallery mode="packed-hover" widths=260px heights=260px style="float:right;"><br />
Image:duo_offline1.png|Duo Offline One-Time Code<br />
Image:duo_offline2.png|Entering Your Code<br />
</gallery><br />
<br />
For use when phone data or calls are not available there are 2 options. <br />
<br />
Users may use the Duo App on their phone or tablet—without any internet connection—to generate one-time codes that will allow them to authenticate to Duo. This code will be the input for the secondary login screen for the VPN or the <code>passcode</code> option in the Duo pane of web authentication. To get a code from the app, open the app and tap on the entry labeled "Duo-protected UMIACS." This will present a 6 digit passcode.<br />
<br />
Alternatively, hardware tokens can be used with Duo. Hardware tokens must be enrolled by the Technical staff, so if you are interested in procuring a hardware token for use with Duo, please contact staff@umiacs.umd.edu<br />
<br />
==Services==<br />
The following UMIACS services are secured with our Duo MFA solution.<br />
<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
* [[GitLab]]<br />
* [[Jira]]<br />
* [[OBJbox | Object Storage]]<br />
* [[VPN]]<br />
* [https://intranet.umiacs.umd.edu/directory Directory]<br />
* [https://intranet.umiacs.umd.edu/requests Requests]<br />
</div><br />
<br />
==FAQ==<br />
;I can no longer clone HTTPS Git repositories in [[GitLab]]. How do I work around this?<br />
: Since we require more than just your username/password to log into [[GitLab]] you can not use your UMIACS credentials directly for accessing HTTPS Git repositories. We encourage users to setup [https://gitlab.umiacs.umd.edu/help/ssh/README.md#ssh SSH] keys instead but if you have a case where you need to use HTTPS you can use a [https://gitlab.umiacs.umd.edu/help/user/profile/personal_access_tokens.md Personal Access Token] to accomplish this. Ensure when you create the token that you are selecting it has <code>API</code> scope. You would then use your username and then the token as the password. Treat this token as a personal secret as it is sufficient to act as your account within Gitlab.<br />
<br />
;How do I authenticate with a Token?<br />
: We only currently support YubiKey tokens for our Duo deployment. You can follow the instructions from [https://guide.duo.com/tokens Yubico] just remember you will need to tap the YubiKey once you select the '''Enter a Passcode''' field. It will create a pass code (will look something like ''kffuastenhldrhfhadafdarivuntddugrvjvllddjjuget'') and send a return.<br />
<br />
__NOTOC__</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Duo&diff=9104Duo2020-04-22T18:37:17Z<p>Liam: </p>
<hr />
<div>[https://www.duo.com Duo] is the multi-factor authentication ([[MFA]]) solution for both UMD centralized information technology resources (DivIT) and UMIACS local resources. Multi-factor solutions ensure that you have something you know (i.e. your password) and something you have (phone/tablet/token). This ensures that phishing and other attempts to secure your password do not result in an account compromise and protect you and your data from unauthorized access.<br />
<br />
<b>Enrollment is discrete and must be done for both UMD (if you have a UMD appointment) and UMIACS individually</b>. You can enroll the same phone for both of these services, but not the same token (if you use a token for UMD already). The UMIACS Single Sign-On and our [[VPN]] require Duo authentication. <br />
<br />
[[File:duo_login.png|400px|thumb|left|Duo Login Prompt]]<br />
<br />
==Enrollment==<br />
Please refer to Duo's [https://guide.duo.com/enrollment Enrollment] guide which has comprehensive information on how to enroll your devices. The recommended place at UMIACS to sign in to enroll is our [https://intranet.umiacs.umd.edu/directory/auth/login Directory application].<br />
<br />
We encourage users to enroll with their smart phone as it provides the most seamless experience. We also support iOS/Android Tablets, landlines, and U2F [https://fidoalliance.org/certification/fido-certified-products/ FIDO] authenticator tokens (though these do not work with our VPN or MFA SSH services).<br />
<br />
==Management==<br />
Users can manage their UMIACS Duo settings as part of the required login to the [https://intranet.umiacs.umd.edu/directory/info Directory Application]. Please follow the Duo guide for [https://guide.duo.com/manage-devices Managing Devices] when you see the Duo login prompt.<br />
<br />
We suggest users register using a mobile phone or tablet that is always in your personal possession. If/When you upgrade or dispose of your currently registered phone/tablet please consider enrolling your new device before getting rid of your old device. Activation of your new device will require you to successfully authenticate with a currently registered device. If you no longer have the device but have kept the mobile phone number registered you can select <b>Call Me</b> to have Duo call you to authenticate your session to manage/enroll your devices. If you do not have access to your previous device(s) or the phone number you will need to contact [mailto:staff@umiacs.umd.edu UMIACS staff] for assistance.<br />
<br />
==Offline Use==<br />
[[File:duo_offline.png|200px|thumb|right|Duo Offline One-Time Code]]<br />
For use when phone data or calls are not available there are 2 options. <br />
<br />
Users may use the Duo App on their phone or tablet—without any internet connection—to generate one-time codes that will allow them to authenticate to Duo. This code will be the input for the secondary login screen for the VPN or the <code>passcode</code> option in the Duo pane of web authentication. To get a code from the app, open the app and tap on the entry labeled "Duo-protected UMIACS." This will present a 6 digit passcode.<br />
<br />
Alternatively, hardware tokens can be used with Duo. Hardware tokens must be enrolled by the Technical staff, so if you are interested in procuring a hardware token for use with Duo, please contact staff@umiacs.umd.edu<br />
<br />
==Services==<br />
The following UMIACS services are secured with our Duo MFA solution.<br />
<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
* [[GitLab]]<br />
* [[Jira]]<br />
* [[OBJbox | Object Storage]]<br />
* [[VPN]]<br />
* [https://intranet.umiacs.umd.edu/directory Directory]<br />
* [https://intranet.umiacs.umd.edu/requests Requests]<br />
</div><br />
<br />
==FAQ==<br />
;I can no longer clone HTTPS Git repositories in [[GitLab]]. How do I work around this?<br />
: Since we require more than just your username/password to log into [[GitLab]] you can not use your UMIACS credentials directly for accessing HTTPS Git repositories. We encourage users to setup [https://gitlab.umiacs.umd.edu/help/ssh/README.md#ssh SSH] keys instead but if you have a case where you need to use HTTPS you can use a [https://gitlab.umiacs.umd.edu/help/user/profile/personal_access_tokens.md Personal Access Token] to accomplish this. Ensure when you create the token that you are selecting it has <code>API</code> scope. You would then use your username and then the token as the password. Treat this token as a personal secret as it is sufficient to act as your account within Gitlab.<br />
<br />
;How do I authenticate with a Token?<br />
: We only currently support YubiKey tokens for our Duo deployment. You can follow the instructions from [https://guide.duo.com/tokens Yubico] just remember you will need to tap the YubiKey once you select the '''Enter a Passcode''' field. It will create a pass code (will look something like ''kffuastenhldrhfhadafdarivuntddugrvjvllddjjuget'') and send a return.<br />
<br />
__NOTOC__</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Duo&diff=9102Duo2020-04-22T18:20:33Z<p>Liam: /* Offline Use */</p>
<hr />
<div>[https://www.duo.com Duo] is the multi-factor authentication ([[MFA]]) solution for both UMD centralized information technology resources (DivIT) and UMIACS local resources. Multi-factor solutions ensure that you have something you know (i.e. your password) and something you have (phone/tablet/token). This ensures that phishing and other attempts to secure your password do not result in an account compromise and protect you and your data from unauthorized access.<br />
<br />
<b>Enrollment is discrete and must be done for both UMD (if you have a UMD appointment) and UMIACS individually</b>. You can enroll the same phone for both of these services, but not the same token (if you use a token for UMD already). The UMIACS Single Sign-On and our [[VPN]] require Duo authentication. <br />
<br />
[[File:duo_login.png|400px|thumb|left|Duo Login Prompt]]<br />
<br />
==Enrollment==<br />
Please refer to Duo's [https://guide.duo.com/enrollment Enrollment] guide which has comprehensive information on how to enroll your devices. The recommended place at UMIACS to sign in to enroll is our [https://intranet.umiacs.umd.edu/directory/auth/login Directory application].<br />
<br />
We encourage users to enroll with their smart phone as it provides the most seamless experience. We also support iOS/Android Tablets, landlines, and U2F [https://fidoalliance.org/certification/fido-certified-products/ FIDO] authenticator tokens (though these do not work with our VPN or MFA SSH services).<br />
<br />
==Management==<br />
Users can manage their UMIACS Duo settings as part of the required login to the [https://intranet.umiacs.umd.edu/directory/info Directory Application]. Please follow the Duo guide for [https://guide.duo.com/manage-devices Managing Devices] when you see the Duo login prompt.<br />
<br />
We suggest users register using a mobile phone or tablet that is always in your personal possession. If/When you upgrade or dispose of your currently registered phone/tablet please consider enrolling your new device before getting rid of your old device. Activation of your new device will require you to successfully authenticate with a currently registered device. If you no longer have the device but have kept the mobile phone number registered you can select <b>Call Me</b> to have Duo call you to authenticate your session to manage/enroll your devices. If you do not have access to your previous device(s) or the phone number you will need to contact [mailto:staff@umiacs.umd.edu UMIACS staff] for assistance.<br />
<br />
[[File:duo_offline.png|200px|thumb|left|Duo Offline One-Time Code]]<br />
<br />
==Offline Use==<br />
For use when phone data or calls are not available there are 2 options. <br />
<br />
Users may use the Duo App on their phone or tablet—without any internet connection—to generate one-time codes that will allow them to authenticate to Duo. This code will be the input for the secondary login screen for the VPN or the <code>passcode</code> option in the Duo pane of web authentication. To get a code from the app, open the app and tap on the entry labeled "Duo-protected UMIACS." This will present a 6 digit passcode.<br />
<br />
Alternatively, hardware tokens can be used with Duo. Hardware tokens must be enrolled by the Technical staff, so if you are interested in procuring a hardware token for use with Duo, please contact staff@umiacs.umd.edu<br />
<br />
==Services==<br />
The following UMIACS services are secured with our Duo MFA solution.<br />
<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
* [[GitLab]]<br />
* [[Jira]]<br />
* [[OBJbox | Object Storage]]<br />
* [[VPN]]<br />
* [https://intranet.umiacs.umd.edu/directory Directory]<br />
* [https://intranet.umiacs.umd.edu/requests Requests]<br />
</div><br />
<br />
==FAQ==<br />
;I can no longer clone HTTPS Git repositories in [[GitLab]]. How do I work around this?<br />
: Since we require more than just your username/password to log into [[GitLab]] you can not use your UMIACS credentials directly for accessing HTTPS Git repositories. We encourage users to setup [https://gitlab.umiacs.umd.edu/help/ssh/README.md#ssh SSH] keys instead but if you have a case where you need to use HTTPS you can use a [https://gitlab.umiacs.umd.edu/help/user/profile/personal_access_tokens.md Personal Access Token] to accomplish this. Ensure when you create the token that you are selecting it has <code>API</code> scope. You would then use your username and then the token as the password. Treat this token as a personal secret as it is sufficient to act as your account within Gitlab.<br />
<br />
;How do I authenticate with a Token?<br />
: We only currently support YubiKey tokens for our Duo deployment. You can follow the instructions from [https://guide.duo.com/tokens Yubico] just remember you will need to tap the YubiKey once you select the '''Enter a Passcode''' field. It will create a pass code (will look something like ''kffuastenhldrhfhadafdarivuntddugrvjvllddjjuget'') and send a return.<br />
<br />
__NOTOC__</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Duo&diff=9101Duo2020-04-22T18:20:03Z<p>Liam: /* Offline Use */</p>
<hr />
<div>[https://www.duo.com Duo] is the multi-factor authentication ([[MFA]]) solution for both UMD centralized information technology resources (DivIT) and UMIACS local resources. Multi-factor solutions ensure that you have something you know (i.e. your password) and something you have (phone/tablet/token). This ensures that phishing and other attempts to secure your password do not result in an account compromise and protect you and your data from unauthorized access.<br />
<br />
<b>Enrollment is discrete and must be done for both UMD (if you have a UMD appointment) and UMIACS individually</b>. You can enroll the same phone for both of these services, but not the same token (if you use a token for UMD already). The UMIACS Single Sign-On and our [[VPN]] require Duo authentication. <br />
<br />
[[File:duo_login.png|400px|thumb|left|Duo Login Prompt]]<br />
<br />
==Enrollment==<br />
Please refer to Duo's [https://guide.duo.com/enrollment Enrollment] guide which has comprehensive information on how to enroll your devices. The recommended place at UMIACS to sign in to enroll is our [https://intranet.umiacs.umd.edu/directory/auth/login Directory application].<br />
<br />
We encourage users to enroll with their smart phone as it provides the most seamless experience. We also support iOS/Android Tablets, landlines, and U2F [https://fidoalliance.org/certification/fido-certified-products/ FIDO] authenticator tokens (though these do not work with our VPN or MFA SSH services).<br />
<br />
==Management==<br />
Users can manage their UMIACS Duo settings as part of the required login to the [https://intranet.umiacs.umd.edu/directory/info Directory Application]. Please follow the Duo guide for [https://guide.duo.com/manage-devices Managing Devices] when you see the Duo login prompt.<br />
<br />
We suggest users register using a mobile phone or tablet that is always in your personal possession. If/When you upgrade or dispose of your currently registered phone/tablet please consider enrolling your new device before getting rid of your old device. Activation of your new device will require you to successfully authenticate with a currently registered device. If you no longer have the device but have kept the mobile phone number registered you can select <b>Call Me</b> to have Duo call you to authenticate your session to manage/enroll your devices. If you do not have access to your previous device(s) or the phone number you will need to contact [mailto:staff@umiacs.umd.edu UMIACS staff] for assistance.<br />
<br />
[[File:duo_offline.png|200px|thumb|left|Duo Offline One-Time Code]]<br />
<br />
==Offline Use==<br />
For use when phone data or calls are not available there are 2 options. <br />
<br />
Users may use the Duo App on their phone or tablet—without any internet connection—to generate one-time codes that will allow them to authenticate to Duo. This code will be the input for the secondary login screen for the VPN or the <code>passcode</code> option in the Duo pane of web authentication. To get a code from the app, open the app and tap on the entry labeled "<tt>Duo-protected UMIACS</tt>." This will present a 6 digit passcode.<br />
<br />
Alternatively, hardware tokens can be used with Duo. Hardware tokens must be enrolled by the Technical staff, so if you are interested in procuring a hardware token for use with Duo, please contact staff@umiacs.umd.edu<br />
<br />
==Services==<br />
The following UMIACS services are secured with our Duo MFA solution.<br />
<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
* [[GitLab]]<br />
* [[Jira]]<br />
* [[OBJbox | Object Storage]]<br />
* [[VPN]]<br />
* [https://intranet.umiacs.umd.edu/directory Directory]<br />
* [https://intranet.umiacs.umd.edu/requests Requests]<br />
</div><br />
<br />
==FAQ==<br />
;I can no longer clone HTTPS Git repositories in [[GitLab]]. How do I work around this?<br />
: Since we require more than just your username/password to log into [[GitLab]] you can not use your UMIACS credentials directly for accessing HTTPS Git repositories. We encourage users to setup [https://gitlab.umiacs.umd.edu/help/ssh/README.md#ssh SSH] keys instead but if you have a case where you need to use HTTPS you can use a [https://gitlab.umiacs.umd.edu/help/user/profile/personal_access_tokens.md Personal Access Token] to accomplish this. Ensure when you create the token that you are selecting it has <code>API</code> scope. You would then use your username and then the token as the password. Treat this token as a personal secret as it is sufficient to act as your account within Gitlab.<br />
<br />
;How do I authenticate with a Token?<br />
: We only currently support YubiKey tokens for our Duo deployment. You can follow the instructions from [https://guide.duo.com/tokens Yubico] just remember you will need to tap the YubiKey once you select the '''Enter a Passcode''' field. It will create a pass code (will look something like ''kffuastenhldrhfhadafdarivuntddugrvjvllddjjuget'') and send a return.<br />
<br />
__NOTOC__</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Duo&diff=9100Duo2020-04-22T18:16:47Z<p>Liam: /* Offline Use */</p>
<hr />
<div>[https://www.duo.com Duo] is the multi-factor authentication ([[MFA]]) solution for both UMD centralized information technology resources (DivIT) and UMIACS local resources. Multi-factor solutions ensure that you have something you know (i.e. your password) and something you have (phone/tablet/token). This ensures that phishing and other attempts to secure your password do not result in an account compromise and protect you and your data from unauthorized access.<br />
<br />
<b>Enrollment is discrete and must be done for both UMD (if you have a UMD appointment) and UMIACS individually</b>. You can enroll the same phone for both of these services, but not the same token (if you use a token for UMD already). The UMIACS Single Sign-On and our [[VPN]] require Duo authentication. <br />
<br />
[[File:duo_login.png|400px|thumb|left|Duo Login Prompt]]<br />
<br />
==Enrollment==<br />
Please refer to Duo's [https://guide.duo.com/enrollment Enrollment] guide which has comprehensive information on how to enroll your devices. The recommended place at UMIACS to sign in to enroll is our [https://intranet.umiacs.umd.edu/directory/auth/login Directory application].<br />
<br />
We encourage users to enroll with their smart phone as it provides the most seamless experience. We also support iOS/Android Tablets, landlines, and U2F [https://fidoalliance.org/certification/fido-certified-products/ FIDO] authenticator tokens (though these do not work with our VPN or MFA SSH services).<br />
<br />
==Management==<br />
Users can manage their UMIACS Duo settings as part of the required login to the [https://intranet.umiacs.umd.edu/directory/info Directory Application]. Please follow the Duo guide for [https://guide.duo.com/manage-devices Managing Devices] when you see the Duo login prompt.<br />
<br />
We suggest users register using a mobile phone or tablet that is always in your personal possession. If/When you upgrade or dispose of your currently registered phone/tablet please consider enrolling your new device before getting rid of your old device. Activation of your new device will require you to successfully authenticate with a currently registered device. If you no longer have the device but have kept the mobile phone number registered you can select <b>Call Me</b> to have Duo call you to authenticate your session to manage/enroll your devices. If you do not have access to your previous device(s) or the phone number you will need to contact [mailto:staff@umiacs.umd.edu UMIACS staff] for assistance.<br />
<br />
[[File:duo_offline.png|200px|thumb|left|Duo Offline One-Time Code]]<br />
<br />
==Offline Use==<br />
For use when phone data or calls are not available there are 2 options. <br />
<br />
For users with the Duo app installed on their phone or tablet they can use the app—without any internet connection—to generate a one time code that can be used to authenticate to Duo. This will be the secondary login for the VPN or the passcode option in the Duo pane of web authentication. To get this code from the app, open the app and tap on the entry labeled Duo-protected UMIACS. This will expand that item in the list to include a 6 digit passcode.<br />
<br />
Alternatively, hardware tokens can be used with Duo. Hardware tokens must be enrolled by the Technical staff, so if you are interested in procuring a hardware token for use with Duo, please contact staff@umiacs.umd.edu<br />
<br />
==Services==<br />
The following UMIACS services are secured with our Duo MFA solution.<br />
<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
* [[GitLab]]<br />
* [[Jira]]<br />
* [[OBJbox | Object Storage]]<br />
* [[VPN]]<br />
* [https://intranet.umiacs.umd.edu/directory Directory]<br />
* [https://intranet.umiacs.umd.edu/requests Requests]<br />
</div><br />
<br />
==FAQ==<br />
;I can no longer clone HTTPS Git repositories in [[GitLab]]. How do I work around this?<br />
: Since we require more than just your username/password to log into [[GitLab]] you can not use your UMIACS credentials directly for accessing HTTPS Git repositories. We encourage users to setup [https://gitlab.umiacs.umd.edu/help/ssh/README.md#ssh SSH] keys instead but if you have a case where you need to use HTTPS you can use a [https://gitlab.umiacs.umd.edu/help/user/profile/personal_access_tokens.md Personal Access Token] to accomplish this. Ensure when you create the token that you are selecting it has <code>API</code> scope. You would then use your username and then the token as the password. Treat this token as a personal secret as it is sufficient to act as your account within Gitlab.<br />
<br />
;How do I authenticate with a Token?<br />
: We only currently support YubiKey tokens for our Duo deployment. You can follow the instructions from [https://guide.duo.com/tokens Yubico] just remember you will need to tap the YubiKey once you select the '''Enter a Passcode''' field. It will create a pass code (will look something like ''kffuastenhldrhfhadafdarivuntddugrvjvllddjjuget'') and send a return.<br />
<br />
__NOTOC__</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Duo&diff=9099Duo2020-04-22T18:14:48Z<p>Liam: </p>
<hr />
<div>[https://www.duo.com Duo] is the multi-factor authentication ([[MFA]]) solution for both UMD centralized information technology resources (DivIT) and UMIACS local resources. Multi-factor solutions ensure that you have something you know (i.e. your password) and something you have (phone/tablet/token). This ensures that phishing and other attempts to secure your password do not result in an account compromise and protect you and your data from unauthorized access.<br />
<br />
<b>Enrollment is discrete and must be done for both UMD (if you have a UMD appointment) and UMIACS individually</b>. You can enroll the same phone for both of these services, but not the same token (if you use a token for UMD already). The UMIACS Single Sign-On and our [[VPN]] require Duo authentication. <br />
<br />
[[File:duo_login.png|400px|thumb|left|Duo Login Prompt]]<br />
<br />
==Enrollment==<br />
Please refer to Duo's [https://guide.duo.com/enrollment Enrollment] guide which has comprehensive information on how to enroll your devices. The recommended place at UMIACS to sign in to enroll is our [https://intranet.umiacs.umd.edu/directory/auth/login Directory application].<br />
<br />
We encourage users to enroll with their smart phone as it provides the most seamless experience. We also support iOS/Android Tablets, landlines, and U2F [https://fidoalliance.org/certification/fido-certified-products/ FIDO] authenticator tokens (though these do not work with our VPN or MFA SSH services).<br />
<br />
==Management==<br />
Users can manage their UMIACS Duo settings as part of the required login to the [https://intranet.umiacs.umd.edu/directory/info Directory Application]. Please follow the Duo guide for [https://guide.duo.com/manage-devices Managing Devices] when you see the Duo login prompt.<br />
<br />
We suggest users register using a mobile phone or tablet that is always in your personal possession. If/When you upgrade or dispose of your currently registered phone/tablet please consider enrolling your new device before getting rid of your old device. Activation of your new device will require you to successfully authenticate with a currently registered device. If you no longer have the device but have kept the mobile phone number registered you can select <b>Call Me</b> to have Duo call you to authenticate your session to manage/enroll your devices. If you do not have access to your previous device(s) or the phone number you will need to contact [mailto:staff@umiacs.umd.edu UMIACS staff] for assistance.<br />
<br />
[[File:duo_offline.png|200px|thumb|left|Duo Offline One-Time Code]]<br />
<br />
==Offline Use==<br />
For use when phone data or calls are not available there are 2 options. <br />
<br />
For people with the Duo app installed on their phone or tablet they can use the app, without any internet connection to generate a one time code that can be used to authenticate to Duo. This will be the secondary login for the VPN or the passcode option in the Duo pane of web authentication. To get this code from the app, open the app and tap on the entry labeled Duo-protected UMIACS. This will expand that item in the list to include a 6 digit passcode.<br />
<br />
Alternatively hardware tokens can be used with Duo. Hardware tokens must be enrolled by the Technical staff, so if you are interested in procuring a hardware token for use with Duo, please contact staff@umiacs.umd.edu<br />
<br />
==Services==<br />
The following UMIACS services are secured with our Duo MFA solution.<br />
<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
* [[GitLab]]<br />
* [[Jira]]<br />
* [[OBJbox | Object Storage]]<br />
* [[VPN]]<br />
* [https://intranet.umiacs.umd.edu/directory Directory]<br />
* [https://intranet.umiacs.umd.edu/requests Requests]<br />
</div><br />
<br />
==FAQ==<br />
;I can no longer clone HTTPS Git repositories in [[GitLab]]. How do I work around this?<br />
: Since we require more than just your username/password to log into [[GitLab]] you can not use your UMIACS credentials directly for accessing HTTPS Git repositories. We encourage users to setup [https://gitlab.umiacs.umd.edu/help/ssh/README.md#ssh SSH] keys instead but if you have a case where you need to use HTTPS you can use a [https://gitlab.umiacs.umd.edu/help/user/profile/personal_access_tokens.md Personal Access Token] to accomplish this. Ensure when you create the token that you are selecting it has <code>API</code> scope. You would then use your username and then the token as the password. Treat this token as a personal secret as it is sufficient to act as your account within Gitlab.<br />
<br />
;How do I authenticate with a Token?<br />
: We only currently support YubiKey tokens for our Duo deployment. You can follow the instructions from [https://guide.duo.com/tokens Yubico] just remember you will need to tap the YubiKey once you select the '''Enter a Passcode''' field. It will create a pass code (will look something like ''kffuastenhldrhfhadafdarivuntddugrvjvllddjjuget'') and send a return.<br />
<br />
__NOTOC__</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=File:Duo_offline.png&diff=9098File:Duo offline.png2020-04-22T18:06:11Z<p>Liam: Liam uploaded a new version of File:Duo offline.png</p>
<hr />
<div>== Summary ==<br />
Duo offline code example, IOS</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=UpdatingMozillaSoftware&diff=9093UpdatingMozillaSoftware2020-04-22T14:42:50Z<p>Liam: fix broken file link.</p>
<hr />
<div>__FORCETOC__<br />
Like most applications, it is important to keep your browser and email clients up-to-date to combat security flaws and gain new functionality. The instructions on this page should help you update Mozilla Firefox and Thunderbird.<br />
<br />
You can also find installers and documentation for the latest versions of Firefox and Thunderbird here:<br />
*Firefox: http://www.getfirefox.com<br />
*Thunderbird: http://www.getthunderbird.com<br />
<br />
== Determining the Installed Version ==<br />
<br />
You can find out what version of Firefox or Thunderbird you have installed on you computer by opening up the application and choosing:<br />
*"Help > About Mozilla [application]" from the menu bar on Windows<br />
*"Firefox > About [application]" from the menu bar on macOS<br />
where [application] is either "Firefox" or "Thunderbird".<br />
<br />
== Updating Mozilla Firefox (Windows & Mac) ==<br />
*By default Mozilla Firefox will automatically update by itself. If it is currently disabled it can be enable with the following steps:<br />
#First navigate to options (Windows) or preferences (Mac).<br />
#Once in the options (Windows) or preferences (Mac) you navigate to the Firefox Updates section<br />
#*Once in the Firefox Updates section you will see an option to “Automatically install updates”. If this is not already enabled it is recommended to enable this.<br />
<br />
''Click on pictures to enlarge them''<br />
<br style="clear: both" /><br />
[[Image:windows-firefox1.png|thumb|left|300pxx300px|Step 1: Navigate to options (Windows)]]<br />
[[Image:mac-firefox1.png|thumb|300px|Step 1: Navigate to preferences (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-firefox2.png|thumb|left|300px|Step 2: Navigate to advanced tab (Windows)]]<br />
[[Image:mac-firefox2.png|thumb|300px|Step 2: Navigate to Firefox Updates (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-firefox3.png|thumb|left|300px|Step 3: Navigate to updates (Windows)]]<br />
[[Image:mac-firefox3.png|thumb|300px|Step 3: Navigate to Automatic Updates (Mac)]]<br />
<br style="clear: both" /><br />
<br />
*If you do not want to have Mozilla Firefox auto-update you can check manually for updates with the following steps:<br />
#First navigate to options (Windows) or preferences (Mac).<br />
#Navigate to the Firefox Updates section (Windows and Mac)<br />
#If an update is available click “Update to “Version”’ Button (Windows and Mac)<br />
#Click “Restart to Update” button (Windows and Mac)<br />
<br />
''Click on pictures to enlarge them''<br />
<br style="clear: both" /><br />
[[Image:windows-firefox4.png|thumb|left|300pxx300px|Step 1: Navigate to Help (Windows)]]<br />
[[Image:windows-firefox5.png|thumb|left|300pxx300px|Step 2: Navigate to about Firefox (Windows)]]<br />
[[Image:mac-firefox4.png|thumb|300px|Step 1: Navigate to Preferences (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-firefox6.png|thumb|left|300px|Step 3: Click “Check for Updates” button (Windows)]]<br />
[[Image:mac-firefox2.png|thumb|300px|Step 2: Navigate to Firefox Updates (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-firefox7.png|thumb|left|300px|Step 4: Click “Update to “Version’” button (Windows)]]<br />
[[Image:mac-firefox6.png|thumb|300px|Step 3:Click “Check for Updates” button (Mac)]]<br />
[[Image:windows-firefox8.png|thumb|left|300px|Step 5: Click “Restart to Update" button (Windows)]]<br />
[[Image:mac-firefox7.png|thumb|300px|Step 4:Click “Restart to Update" button (Mac)]]<br />
<br style="clear: both" /><br />
<br />
== Updating Mozilla Thunderbird (Windows & Mac) ==<br />
*By default Mozilla Thunderbird will automatically update by itself. If it is currently disabled it can be enable with the following steps.<br />
#First navigate to options->options(Windows) or preferences(Mac).<br />
#Once in the options(Windows) or preferences(Mac) you navigate to the advanced tab.<br />
#Once on the advanced Tab you navigate to Updates.<br />
#*Once in the updates tab you will see an option to “Automatically install updates”. If this is not already enabled it is recommended to enable this.<br />
<br />
''Click on pictures to enlarge them''<br />
<br style="clear: both" /><br />
[[Image:windows-thunderbird1.png|thumb|left|300px|Step 2: Navigate to options->options (Windows)]]<br />
[[Image:mac-thunderbird1.png|thumb|300px|Step 1: Navigate to preferences (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-thunderbird2.png|thumb|left|300px|Step 2: Navigate to advanced tab (Windows)]]<br />
[[Image:mac-thunderbird2.png|thumb|300px|Step 2: Navigate to advanced tab (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-thunderbird3.png|thumb|left|300px|Step 3: Navigate to updates(Windows)]]<br />
[[Image:mac-thunderbird3.png|thumb|300px|Step 3: Navigate to updates (Mac)]]<br />
<br style="clear: both" /><br />
<br />
*If you do not want to have Mozilla Thunderbird auto-update you can check manually for updates with the following steps:<br />
#First navigate to help->about Thunderbird (Windows) and about Thunderbird (Mac).<br />
#Click the check for updates button (Windows and Mac).<br />
#Click “Update & Restart” button (Windows) and “Restart to Update” button (Mac).<br />
<br />
''Click on pictures to enlarge them''<br />
<br style="clear: both" /><br />
[[Image:windows-Thunderbird4.png|thumb|left|300px|Step 1: Navigate to Help (Windows)]]<br />
[[Image:windows-Thunderbird5.png|thumb|left|300px|Step 2: Navigate to about Thunderbird (Windows)]]<br />
[[Image:mac-Thunderbird1.png|thumb|300px|Step 1: Navigate to Preferences (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-thunderbird6.png|thumb|left|300px|Step 3: Click “Check for Updates” button (Windows)]]<br />
[[Image:mac-thunderbird2.png|thumb|300px|Step 2: Navigate to Advanced Tab (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-thunderbird7.png|thumb|left|300px|Step 4: Click “Update & Restart" button (Windows)]]<br />
[[Image:mac-thunderbird6.png|thumb|300px|Step 3: Navigate to Updates (Mac)]]<br />
[[Image:mac-thunderbird4.png|thumb|300px|Step 4: Click on "Check for Updates" button (Mac)]]<br />
[[Image:mac-thunderbird5.png|thumb|300px|Step 5: Click on "Restart to update Thunderbird" button (Mac)]]<br />
<br style="clear: both" /><br />
<br />
== Troubleshooting ==<br />
If for some reason Firefox or Thunderbird refuses to update using the methods described above, please stop by the [[HelpDesk]] and have a technician assist you.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Podman&diff=9082Podman2020-04-21T17:48:43Z<p>Liam: /* GPUs */</p>
<hr />
<div>[https://podman.io/ Podman] is a daemonless container engine alternative to [https://www.docker.com/ Docker]. We don't support Docker in many of our environments as it grants trivial administrative control over the host the Docker daemon runs on. While Podman has the ability to run containers in user namespaces. This means that for every user name space in the kernel you create the processes within it will map to a new uid/gid range. For example if you are root in your container you will not be uid 0 outside the container you will be uid 4294000000.<br />
<br />
We still believe that [[Singularity]] is the best option for running containerized workloads on our clustered based resources. Podman is a good option for developing the containers to be run via [[Singularity]] or building a deliverable for a funding agency. Therefore we will be only providing podman on workstations and standalone servers that individuals ask for. <br />
<br />
== Getting Started ==<br />
<br />
To get started there are a few things that users need to configure.<br />
<br />
First run the '''podman''' command. If it says command not found or that you get an ERRO like the one below about no subuid ranges please contact staff@umiacs.umd.edu with the error and the host that you are using. We will need to do some steps to setup the host you want ready.<br />
<br />
<pre><br />
[derek@zerus:~ ] $ podman<br />
ERRO[0000] cannot find mappings for user derek: No subuid ranges found for user "derek" in /etc/subuid<br />
Error: missing command 'podman COMMAND'<br />
Try 'podman --help' for more information.<br />
</pre><br />
<br />
=== Storage ===<br />
Containers are made up of layers for the image and these are stored in the graphroot setting of <code>~/.config/containers/storage.conf</code> which by default will be in your home directory. With our home directories being available over NFS there is an issue[https://www.redhat.com/sysadmin/rootless-podman-nfs] that due to the user name space mapping described above you will not be able to access your home directory when you are building the layers.<br />
<br />
You need to update the <code>graphroot</code> setting to a local directory on the host. The file <code>~/.config/containers/storage.conf</code> may not exist until you run <code>podman</code> the first time. <br />
<br />
<pre><br />
[storage]<br />
driver = "vfs"<br />
runroot = "/tmp/run-2174"<br />
graphroot = "/scratch1/derek/.local/share/containers/storage"<br />
...<br />
</pre><br />
<br />
== GPUs ==<br />
Running Podman with the local Nvidia GPUs requires some additional configuration steps that staff has to add to any individual host that runs Podman. This includes ensuring the <tt>nvidia-container-runtime</tt> package is installed.<br />
<br />
For example you can run <code>nvidia-smi</code> from within the official Nvidia CUDA containers with a command like this:<br />
<br />
<pre><br />
$ podman run --rm --hooks-dir=/usr/share/containers/oci/hooks.d docker.io/nvidia/cuda nvidia-smi<br />
Thu Apr 16 18:47:04 2020<br />
+-----------------------------------------------------------------------------+<br />
| NVIDIA-SMI 440.44 Driver Version: 440.44 CUDA Version: 10.2 |<br />
|-------------------------------+----------------------+----------------------+<br />
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |<br />
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |<br />
|===============================+======================+======================|<br />
| 0 GeForce GTX TIT... Off | 00000000:03:00.0 Off | N/A |<br />
| 22% 40C P8 14W / 250W | 142MiB / 12212MiB | 1% Default |<br />
+-------------------------------+----------------------+----------------------+<br />
| 1 GeForce GTX TIT... Off | 00000000:04:00.0 Off | N/A |<br />
| 22% 34C P8 15W / 250W | 1MiB / 12212MiB | 1% Default |<br />
+-------------------------------+----------------------+----------------------+<br />
<br />
+-----------------------------------------------------------------------------+<br />
| Processes: GPU Memory |<br />
| GPU PID Type Process name Usage |<br />
|=============================================================================|<br />
+-----------------------------------------------------------------------------+<br />
</pre><br />
<br />
== Example ==<br />
To build your own image you can start from an example we have https://gitlab.umiacs.umd.edu/derek/gpudocker.<br />
<br />
First clone the repository, change directory and build the image with podman.<br />
<pre><br />
git clone https://gitlab.umiacs.umd.edu/derek/gpudocker.git<br />
cd gpudocker<br />
podman build -t gpudocker .<br />
</pre><br />
<br />
Then you can run the test script to verify. Notice that we pass the local directory <code>test</code> as a path into the image so we can run a script. This can also be useful for your data output data as well as if you write anywhere else in the container it will not be available outside the container.<br />
<pre><br />
$ podman run --volume `pwd`/test:/mnt --hooks-dir=/usr/share/containers/oci/hooks.d gpudocker python3 /mnt/test_torch.py<br />
GPU found 0: GeForce GTX 1080 Ti<br />
tensor([[0.3479, 0.6594, 0.5791],<br />
[0.6065, 0.3415, 0.9328],<br />
[0.9117, 0.3541, 0.9050],<br />
[0.6611, 0.5361, 0.3212],<br />
[0.8574, 0.5116, 0.7021]])<br />
</pre></div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Singularity&diff=9063Singularity2020-04-20T15:24:00Z<p>Liam: </p>
<hr />
<div>[https://sylabs.io/docs/ Singularity] is a container platform that doesn't elevate the privileges of a user running the container. This is important as UMIACS runs many multi-tenant computer systems and doesn't provide administrative control to users in them.<br />
<br />
You can find out what the current version is that we provide by running the '''singularity''' command. If this says <tt>command not found</tt> please contact staff and we will ensure that the software is available on the host you are looking for.<br />
<br />
<pre><br />
$ singularity --version<br />
singularity version 3.4.2-1.1.el7<br />
</pre><br />
<br />
Singularity can run a variety of images including its own format and Docker images. To create images you however need to have administrative rights and therefore you will need to do this on a host that you have access to (laptop or personal desktop).<br />
<br />
If you are going to pull large images you may run out of space in your home directory so we suggest you run the following commands to setup a alternate cache directory.<br />
<br />
<pre><br />
export WORKDIR=/scatch0/derek<br />
export SINGULARITY_CACHEDIR=${WORKDIR}/.cache<br />
mkdir -p $SINGULARITY_CACHEDIR<br />
</pre><br />
<br />
We do suggest you pull images down into an intermediate file ('''SIF''' file) as you can then not have to worry about re-caching the image. <br />
<br />
<pre><br />
$ singularity pull cuda10.2.sif docker://nvidia/cuda:10.2-devel<br />
INFO: Converting OCI blobs to SIF format<br />
INFO: Starting build...<br />
Getting image source signatures<br />
Copying blob sha256:7ddbc47eeb70dc7f08e410a6667948b87ff3883024eb41478b44ef9a81bf400c<br />
25.45 MiB / 25.45 MiB [====================================================] 0s<br />
Copying blob sha256:c1bbdc448b7263673926b8fe2e88491e5083a8b4b06ddfabf311f2fc5f27e2ff<br />
34.53 KiB / 34.53 KiB [====================================================] 0s<br />
Copying blob sha256:8c3b70e3904492c753652606df4726430426f42ea56e06ea924d6fea7ae162a1<br />
845 B / 845 B [============================================================] 0s<br />
Copying blob sha256:45d437916d5781043432f2d72608049dcf74ddbd27daa01a25fa63c8f1b9adc4<br />
162 B / 162 B [============================================================] 0s<br />
Copying blob sha256:d8f1569ddae616589c5a2dabf668fadd250ee9d89253ef16f0cb0c8a9459b322<br />
6.88 MiB / 6.88 MiB [======================================================] 0s<br />
Copying blob sha256:902fc5ce82298797e09dc1b28ed942da3892a354321725fad6955ee651557e98<br />
9.00 MiB / 9.00 MiB [======================================================] 0s<br />
Copying blob sha256:ae1bb79c5cfc1c10948684c3a2964ec7444b19cae7edc487aa474804336b52c1<br />
184 B / 184 B [============================================================] 0s<br />
Copying blob sha256:fa6605c8fe7a3779c56b4768ac46738f160f005067f22c03e3cf5e87ad5d19d0<br />
674.37 MiB / 674.37 MiB [==================================================] 8s<br />
Copying blob sha256:0508a679d3397b66fdf6cd56db9a99e2b7af5a8519e9f9534d2dff07779f2482<br />
783.58 MiB / 783.58 MiB [=================================================] 10s<br />
Copying config sha256:44b5f1390c8715653c6488b3cb4fbee875c30cacadc827b2b4372b18318b2fa0<br />
7.28 KiB / 7.28 KiB [======================================================] 0s<br />
Writing manifest to image destination<br />
Storing signatures<br />
2020/04/14 11:52:55 info unpack layer: sha256:7ddbc47eeb70dc7f08e410a6667948b87ff3883024eb41478b44ef9a81bf400c<br />
2020/04/14 11:52:56 info unpack layer: sha256:c1bbdc448b7263673926b8fe2e88491e5083a8b4b06ddfabf311f2fc5f27e2ff<br />
2020/04/14 11:52:56 info unpack layer: sha256:8c3b70e3904492c753652606df4726430426f42ea56e06ea924d6fea7ae162a1<br />
2020/04/14 11:52:56 info unpack layer: sha256:45d437916d5781043432f2d72608049dcf74ddbd27daa01a25fa63c8f1b9adc4<br />
2020/04/14 11:52:56 info unpack layer: sha256:d8f1569ddae616589c5a2dabf668fadd250ee9d89253ef16f0cb0c8a9459b322<br />
2020/04/14 11:52:57 info unpack layer: sha256:902fc5ce82298797e09dc1b28ed942da3892a354321725fad6955ee651557e98<br />
2020/04/14 11:52:57 info unpack layer: sha256:ae1bb79c5cfc1c10948684c3a2964ec7444b19cae7edc487aa474804336b52c1<br />
2020/04/14 11:52:57 info unpack layer: sha256:fa6605c8fe7a3779c56b4768ac46738f160f005067f22c03e3cf5e87ad5d19d0<br />
2020/04/14 11:53:14 info unpack layer: sha256:0508a679d3397b66fdf6cd56db9a99e2b7af5a8519e9f9534d2dff07779f2482<br />
INFO: Creating SIF file...<br />
INFO: Build complete: cuda10.2.sif<br />
</pre><br />
<br />
Now you can run the local image with the '''run''' command or start a shell with the '''shell''' command. Please note that if you are in an environment with GPUs and you want to access them inside the container you do need to specify the '''--nv''' flag.<br />
<br />
<pre><br />
$ singularity run --nv cuda10.2.sif nvidia-smi -L<br />
GPU 0: GeForce GTX 1080 Ti (UUID: GPU-9ee980c3-8746-08dd-8e14-82fbaf88367e)<br />
</pre><br />
<br />
==Example==<br />
<br />
We have a [https://gitlab.umiacs.umd.edu/derek/gpudocker gpudocker] example workflow using our [[GitLab]] as a docker registry. You can for the repository and further customize this to your needs. The workflow is that you have a local laptop or desktop you can run Docker on to create the image, tag it and and push it to the repository. Then you pull the image down onto one of our workstations/clusters and run with your data. <br />
<br />
<pre><br />
$ singularity pull gpudocker.sif docker://registry.umiacs.umd.edu/derek/gpudocker<br />
INFO: Converting OCI blobs to SIF format<br />
INFO: Starting build...<br />
Getting image source signatures<br />
Copying blob sha256:7ddbc47eeb70dc7f08e410a6667948b87ff3883024eb41478b44ef9a81bf400c<br />
25.45 MiB / 25.45 MiB [====================================================] 2s<br />
Copying blob sha256:c1bbdc448b7263673926b8fe2e88491e5083a8b4b06ddfabf311f2fc5f27e2ff<br />
34.53 KiB / 34.53 KiB [====================================================] 0s<br />
Copying blob sha256:8c3b70e3904492c753652606df4726430426f42ea56e06ea924d6fea7ae162a1<br />
845 B / 845 B [============================================================] 0s<br />
Copying blob sha256:45d437916d5781043432f2d72608049dcf74ddbd27daa01a25fa63c8f1b9adc4<br />
162 B / 162 B [============================================================] 0s<br />
Copying blob sha256:d8f1569ddae616589c5a2dabf668fadd250ee9d89253ef16f0cb0c8a9459b322<br />
6.88 MiB / 6.88 MiB [======================================================] 0s<br />
Copying blob sha256:85386706b02069c58ffaea9de66c360f9d59890e56f58485d05c1a532ca30db1<br />
8.05 MiB / 8.05 MiB [======================================================] 1s<br />
Copying blob sha256:ee9b457b77d047ff322858e2de025e266ff5908aec569560e77e2e4451fc23f4<br />
184 B / 184 B [============================================================] 0s<br />
Copying blob sha256:be4f3343ecd31ebf7ec8809f61b1d36c2c2f98fc4e63582401d9108575bc443a<br />
656.83 MiB / 656.83 MiB [=================================================] 28s<br />
Copying blob sha256:30b4effda4fdab95ec4eba8873f86e7574c2edddf4dc5df8212e3eda1545aafa<br />
782.81 MiB / 782.81 MiB [=================================================] 37s<br />
Copying blob sha256:b6f46848806c8750a68edc4463bf146ed6c3c4af18f5d3f23281dcdfb1c65055<br />
100.58 MiB / 100.58 MiB [==================================================] 5s<br />
Copying blob sha256:44845dc671f759820baac0376198141ca683f554bb16a177a3cfe262c9e368ff<br />
1.47 GiB / 1.47 GiB [====================================================] 1m4s<br />
Copying config sha256:1b2e5b7b99af9d797ef6fbd091a6a2c6a30e519e31a74f5e9cacb4c8c462d6ed<br />
7.56 KiB / 7.56 KiB [======================================================] 0s<br />
Writing manifest to image destination<br />
Storing signatures<br />
2020/04/14 12:21:17 info unpack layer: sha256:7ddbc47eeb70dc7f08e410a6667948b87ff3883024eb41478b44ef9a81bf400c<br />
2020/04/14 12:21:18 info unpack layer: sha256:c1bbdc448b7263673926b8fe2e88491e5083a8b4b06ddfabf311f2fc5f27e2ff<br />
2020/04/14 12:21:18 info unpack layer: sha256:8c3b70e3904492c753652606df4726430426f42ea56e06ea924d6fea7ae162a1<br />
2020/04/14 12:21:18 info unpack layer: sha256:45d437916d5781043432f2d72608049dcf74ddbd27daa01a25fa63c8f1b9adc4<br />
2020/04/14 12:21:18 info unpack layer: sha256:d8f1569ddae616589c5a2dabf668fadd250ee9d89253ef16f0cb0c8a9459b322<br />
2020/04/14 12:21:18 info unpack layer: sha256:85386706b02069c58ffaea9de66c360f9d59890e56f58485d05c1a532ca30db1<br />
2020/04/14 12:21:18 info unpack layer: sha256:ee9b457b77d047ff322858e2de025e266ff5908aec569560e77e2e4451fc23f4<br />
2020/04/14 12:21:18 info unpack layer: sha256:be4f3343ecd31ebf7ec8809f61b1d36c2c2f98fc4e63582401d9108575bc443a<br />
2020/04/14 12:21:35 info unpack layer: sha256:30b4effda4fdab95ec4eba8873f86e7574c2edddf4dc5df8212e3eda1545aafa<br />
2020/04/14 12:21:55 info unpack layer: sha256:b6f46848806c8750a68edc4463bf146ed6c3c4af18f5d3f23281dcdfb1c65055<br />
2020/04/14 12:21:58 info unpack layer: sha256:44845dc671f759820baac0376198141ca683f554bb16a177a3cfe262c9e368ff<br />
INFO: Creating SIF file...<br />
INFO: Build complete: gpudocker.sif<br />
</pre><br />
<br />
<pre><br />
$ singularity run --nv gpudocker.sif python3 -c 'from __future__ import print_function; import torch; print(torch.cuda.current_device()); x = torch.rand(5, 3); print(x)'<br />
0<br />
tensor([[0.5299, 0.9827, 0.7858],<br />
[0.2044, 0.6783, 0.2606],<br />
[0.0538, 0.4272, 0.9361],<br />
[0.1980, 0.2654, 0.4160],<br />
[0.1680, 0.8407, 0.0509]])<br />
</pre></div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=LabFacilities&diff=9061LabFacilities2020-04-18T04:27:04Z<p>Liam: </p>
<hr />
<div>* [[CBCB | Center for Bioinformatics and Computational Biology]] ([http://www.cbcb.umd.edu CBCB]) <br />
* Center for Digital International Government ([http://www.umiacs.umd.edu/research/CDIG CDIG]) <br />
* Center for Automation Research ([http://www.cfar.umd.edu/ CfAR])<br />
* Center for Health-related Informatics and Bioimaging ([http://www.chib.umd.edu/ CHIB]) <br />
* Computational Linguistics and Information Processing ([https://wiki.umiacs.umd.edu/clip/index.php/Main_Page CLIP]) <br />
* Center for Machine Learning ([https://ml.umd.edu CML])<br />
* Computer Vision Laboratory ([http://www.cfar.umd.edu/cvl/ CVL]) <br />
* Distributed Systems Software Laboratory ([http://www.cs.umd.edu/projects/dssl DSSL]) <br />
* Fraunhofer Center at Maryland ([https://www.cese.fraunhofer.org/ FCMD])<br />
* Human Computer Interaction Laboratory ([http://hcil.umd.edu/ HCIL]) <br />
* Graphics and Visual Informatics Laboratory ([http://www.cs.umd.edu/gvil/ GVIL])<br />
* Language and Media processing laboratory ([http://lamp.cfar.umd.edu/ LAMP])<br />
* Laboratory for Parallel and Distributed Computing ([http://www.umiacs.umd.edu/labs/parallel/index.htm LPDC])<br />
* Laboratory for Telecommunication Sciences ([http://www.ltsnet.net/ LTS])<br />
* Lab for Broadband Mobile Communications ([http://www.umiacs.umd.edu/research/maxwell/ MAXWell])<br />
* Maryland Cybersecurity Center ([http://cyber.umd.edu/ MC2])<br />
* [[OpenLAB]]<br />
* Joint Center for Quantum Information and Computer Science ([https://quics.umd.edu/ QUICS])<br />
* National Socio-Environmental Synthesis Center ([https://www.sesync.org/ SESYNC])</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=LabFacilities&diff=9060LabFacilities2020-04-18T04:25:56Z<p>Liam: </p>
<hr />
<div>* Center for Adcanced Study of Language ([https://www.casl.umd.edu/ CASL]) <br />
* [[CBCB | Center for Bioinformatics and Computational Biology]] ([http://www.cbcb.umd.edu CBCB]) <br />
* Center for Digital International Government ([http://www.umiacs.umd.edu/research/CDIG CDIG]) <br />
* Center for Automation Research ([http://www.cfar.umd.edu/ CfAR])<br />
* Center for Health-related Informatics and Bioimaging ([http://www.chib.umd.edu/ CHIB]) <br />
* Computational Linguistics and Information Processing ([https://wiki.umiacs.umd.edu/clip/index.php/Main_Page CLIP]) <br />
* Center for Machine Learning ([https://ml.umd.edu CML])<br />
* Computer Vision Laboratory ([http://www.cfar.umd.edu/cvl/ CVL]) <br />
* Distributed Systems Software Laboratory ([http://www.cs.umd.edu/projects/dssl DSSL]) <br />
* Fraunhofer Center at Maryland ([https://www.cese.fraunhofer.org/ FCMD])<br />
* Human Computer Interaction Laboratory ([http://hcil.umd.edu/ HCIL]) <br />
* Graphics and Visual Informatics Laboratory ([http://www.cs.umd.edu/gvil/ GVIL])<br />
* Language and Media processing laboratory ([http://lamp.cfar.umd.edu/ LAMP])<br />
* Laboratory for Parallel and Distributed Computing ([http://www.umiacs.umd.edu/labs/parallel/index.htm LPDC])<br />
* Laboratory for Telecommunication Sciences ([http://www.ltsnet.net/ LTS])<br />
* Lab for Broadband Mobile Communications ([http://www.umiacs.umd.edu/research/maxwell/ MAXWell])<br />
* Maryland Cybersecurity Center ([http://cyber.umd.edu/ MC2])<br />
* [[OpenLAB]]<br />
* Joint Center for Quantum Information and Computer Science ([https://quics.umd.edu/ QUICS])<br />
* National Socio-Environmental Synthesis Center ([https://www.sesync.org/ SESYNC])</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Accounts&diff=9024Accounts2020-04-03T03:58:27Z<p>Liam: </p>
<hr />
<div>This page outlines the various account types at UMIACS and their management methods.<br />
<br />
'''Do not share any UMIACS-affiliated account for any purpose. Action may be taken against your account if you do so.'''<br />
<br />
==UMIACS Account==<br />
A traditional UMIACS account consists of the following components:<br />
; [[ActiveDirectory | Active Directory Account]]<br />
: Provides access to UMIACS-supported computers, email, secgroup controlled resources, web services, and the VPN.<br />
; [[Jira | Jira Account]]<br />
: Provides access to the JIRA Request Tracker. Please note that it is possible to set a separate password for this account, at which point it will no longer be synced from your Active Directory Account. Changing your Jira password DOES NOT change your Active Directory Account password.<br />
<br />
==Guest / Collaborator Account==<br />
; [[Accounts/Collaborator | Collaborator Accounts]]<br />
: Sponsored account to provide temporary access to UMIACS Web Services for non-UMIACS collaborators.<br />
<br />
==Request a UMIACS account==<br />
Fill out the account request form located at the [https://intranet.umiacs.umd.edu/requests/accounts/new UMIACS Account Request webapp]. Please note that for the PI field you will be entering your PI/Professor/Sponsor's account name here at UMIACS. Also indicate any labs you are a member of in the notes field to speed up access to your lab's resources. <br />
<br />
Once the form is submitted, it will send an email with a link to verify your email address. You must click this link to verify your email address before the system will send email to your PI to review the account request. Accounts can take anywhere from a few hours to a day for installation, depending on how quickly your PI approves your account.<br />
<br />
==Password Requirements==<br />
We have the following policies in regards to our [[ActiveDirectory]] passwords:<br />
* Minimum Password Length : 8 Characters (more is allowed)<br />
* Minimum Character Classes : 3 Character Classes<br />
** English uppercase characters (A - Z)<br />
** English lowercase characters (a - z)<br />
** Base 10 digits (0 - 9)<br />
** Non-alphanumeric (For example: !, $, #, or %)<br />
** Unicode characters<br />
* Password cannot contain (or match a substring of 3+ sequential characters) of your username or any part of your first or last name.<br />
* Password was not previously used in last 5 passwords.<br />
* Password has not been [[CompromisedPasswordFiltering | compromised]] in a known data breach.<br />
<br />
It is your responsibility to secure your password. Please try to choose a strong password and use secure protocols.<br />
<br />
==Changing account password==<br />
===If you know your current password===<br />
* The [https://intranet.umiacs.umd.edu/password UMIACS Password Web Application] can be used to change the password for UMIACS and UMIACS Collaborator accounts.<br />
<br />
===If you do not know your current password===<br />
* [https://intranet.umiacs.umd.edu/password/forgot Reset your password], you will be required to have already registered a mobile phone number and alternate E-mail address in our [https://intranet.umiacs.umd.edu/directory/directory/info/ Directory Application].<br />
** UMIACS Collaborator Accounts can always be reset by the sponsor in our [https://intranet.umiacs.umd.edu/requests/accounts/collaborators/ Requests Application].<br />
* Stop by the UMIACS Help Desk in room 3109 Iribe Center with a photo ID.<br />
* If you are unable to physically stop by the UMIACS Help Desk, you can have your Account sponsor (PI) stop by the UMIACS Help Desk to reset the password on your behalf. The account sponsor will then be responsible to conveying the password to you in a secure manner. (i.e. Telephone, where they could identify you by voice)<br />
<br />
==All Accounts Related Pages==<br />
{{Special:PrefixIndex/Accounts/}}</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Python&diff=8898Python2020-02-13T02:26:19Z<p>Liam: /* Python Environment */</p>
<hr />
<div>Python is a widely used general-purpose, high-level programming language.<br />
<br />
<br />
== Python Versions ==<br />
Most modern *NIX distributions ship with a system version of Python. If the system version is not sufficient, there are multiple versions of Python available via [[Modules | GNU Modules]]. If you find that you need a version of Python that is not currently available through GNU Modules, you can always build it from [https://www.python.org/downloads/ source].<br />
<br />
If you are using Windows, you can install your required version of Python without Administrator credentials. Please see the [[WindowsPython | Windows Python page]]<br />
<br />
== Python Environment ==<br />
Python utilizes a variable called 'PYTHONPATH', which is similar to the PATH variable used in many shells. The PYTHONPATH variable tells the Python interpreter where to look to find modules.<br />
To view your python path:<br />
<pre>bash:~$ python -c 'import sys; print sys.path'</pre><br />
You can add directories to your PYTHONPATH either through your shell, or in your Python code itself:<br />
<pre>bash:~$ PYTHONPATH=$PYTHONPATH:/location/to/directory<br />
<br />
...or...<br />
<br />
>>> sys.path.append('/location/to/directory')</pre><br />
<br />
== Installing Modules ==<br />
While some of the Versions of Python available in GNU modules provide a default set of modules pre-installed, you may wish to install your own. Typically you will not have access to the global Python install location, so you will have to install modules using an alternative method.<br />
<br />
==== Unix/Linux Alternate Module Installation====<br />
<br />
===== 'User' scheme=====<br />
The user scheme allows a user to install the module into the site ''userbase'' (<code>python -c 'import site; print site.USER_BASE'</code>). This file location is included in the PYTHONPATH by default.<br />
<pre>bash:~$ python setup.py install --user</pre><br />
<br />
====='Prefix' scheme=====<br />
The prefix scheme allows a user to install a module into a location of their choice. '''Please note:''' This location will need to be added to the PYTHONPATH in order for the module to be found by the Python interpreter. <br />
<pre>bash:~$ python setup.py install --prefix="/path/to/location"</pre><br />
<br />
=====[[PythonVirtualEnv | Python Virtual Environment]]=====<br />
A Python Virtual Environment is an isolated working copy of Python which allows you to work on a specific project without worry of affecting other projects. For more information on setting up a virtualenv, please see the [[PythonVirtualEnv| Python Virtual Environment]] page.<br />
==== Windows Alternate Module Installation:====<br />
<br />
=====Prefix Scheme=====<br />
Python on windows has a simpler layout, and as such the prefix scheme has traditionally been used to install additional packages into a separate location.<br />
<pre>python setup.py install --prefix="\Temp\Python"</pre></div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=PythonVirtualEnv&diff=8897PythonVirtualEnv2020-02-13T02:13:53Z<p>Liam: </p>
<hr />
<div>A virtual environment is an isolated working copy of Python, which allows you to work on specific projects without affecting others. It creates an environment that has its own installation directories and that does not share libraries with other virtualenv environments (and optionally doesn’t access the globally-installed libraries either).<br />
<br />
==Basic Usage==<br />
The following steps outline how to create a virtual environment using the system Python.<br />
<br />
====Creating the virtual environment on Python 3====<br />
Python 3 comes with the virtualenv module built in.<br />
<pre><br />
$ python3 -m venv env<br />
</pre><br />
<br />
====Creating the virtual environment on Python 2 (deprecated)====<br />
<pre><br />
$ git clone https://github.com/pypa/virtualenv.git<br />
$ python virtualenv/virtualenv.py env<br />
New python executable in env/bin/python<br />
Installing setuptools.............done.<br />
</pre><br />
<br />
====Activating the VirtualEnv====<br />
You will need to use the 'source' command to load it into your shell environment.<br />
<pre><br />
$ source env/bin/activate<br />
</pre><br />
<br />
{{Note|<b>Note:</b> tcsh/csh shell users should run <code>source env/bin/activate.csh</code> instead.}}<br />
<br />
We also suggest the first thing you do is to ensure you have an updated version of pip installed in your environment. Make sure you have sourced your environment, and then run the following:<br />
<br />
<pre><br />
$ pip install --upgrade pip<br />
</pre><br />
<br />
In bash and tcsh, the environment can be deactivated by typing <code>deactivate</code><br />
<br />
====Installing Python Modules====<br />
Once you have created your virtual environment and sourced it, you can install additional modules using the 'pip' command.<br />
<br />
<pre><br />
$ pip install nose<br />
Collecting nose<br />
Downloading nose-1.3.7-py3-none-any.whl (154 kB)<br />
|████████████████████████████████| 154 kB 12.5 MB/s<br />
Installing collected packages: nose<br />
Successfully installed nose-1.3.7<br />
</pre><br />
<br />
====Listing installed Python Modules====<br />
<pre><br />
(env)$ pip freeze<br />
nose==1.3.7<br />
</pre><br />
<br />
====Uninstalling Python Modules====<br />
'pip' can also be used to remove a module from the environment.<br />
<pre><br />
$ pip uninstall nose<br />
Found existing installation: nose 1.3.7<br />
Uninstalling nose-1.3.7:<br />
Would remove:<br />
/nfshomes/liam/env/bin/nosetests<br />
/nfshomes/liam/env/bin/nosetests-3.4<br />
/nfshomes/liam/env/lib/python3.7/site-packages/nose-1.3.7.dist-info/*<br />
/nfshomes/liam/env/lib/python3.7/site-packages/nose/*<br />
/nfshomes/liam/env/man/man1/nosetests.1<br />
Proceed (y/n)? y<br />
Successfully uninstalled nose-1.3.7<br />
</pre><br />
<br />
===Switching between virtual environments===<br />
To switch between different environments, simply deactivate your current virtual environment, and source another.<br />
<pre><br />
(env)$ which python<br />
~/env/bin/python<br />
<br />
(env)$ deactivate <br />
<br />
$ source my-other-env/bin/activate<br />
<br />
(my-other-env)$ which python<br />
~/my-other-env/bin/python<br />
</pre><br />
<br />
==Using a different Python version==<br />
To create a virtual environment that uses a version of python that is different than the system default, create the virtualenv with your target version of Python. This could be a Python build we provide via [[Modules]], or one you've built yourself. Virtualenv will pick up the first python version it finds in your $PATH, or you can direct it to a specific location with the "--python" flag.<br />
<br />
<pre><br />
$ module load Python3<br />
<br />
$ which python3<br />
/opt/local/stow/Python3-3.8.1/bin/python3<br />
</pre><br />
<br />
'''Important:''' virtualenv will include any modules listed in your PYTHONPATH when initializing the virtual environment. To ensure a vanilla environment, it might be a good idea to verify your PYTHONPATH is empty.<br />
<br />
<pre><br />
$ echo $PYTHONPATH<br />
<br />
</pre><br />
<br />
<pre><br />
$ python3 -m venv env36<br />
<br />
$ source env36/bin/activate<br />
(env36) $ which python<br />
~/env36/bin/python<br />
</pre></div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=PythonVirtualEnv&diff=8896PythonVirtualEnv2020-02-13T02:13:20Z<p>Liam: /* Activating the VirtualEnv */</p>
<hr />
<div>A virtual environment is an isolated working copy of Python, which allows you to work on specific projects without affecting others. It creates an environment that has its own installation directories and that does not share libraries with other virtualenv environments (and optionally doesn’t access the globally-installed libraries either).<br />
<br />
==Basic Usage==<br />
The following steps outline how to create a virtual environment using the system Python.<br />
<br />
====Creating the virtual environment on Python 3====<br />
Python 3 comes with the virtualenv module built in.<br />
<pre><br />
$ python3 -m venv env<br />
</pre><br />
<br />
====Creating the virtual environment on Python 2 (deprecated)====<br />
<pre><br />
$ git clone https://github.com/pypa/virtualenv.git<br />
$ python virtualenv/virtualenv.py env<br />
New python executable in env/bin/python<br />
Installing setuptools.............done.<br />
</pre><br />
<br />
====Activating the VirtualEnv====<br />
You will need to use the 'source' command to load it into your shell environment.<br />
<pre><br />
$ source env/bin/activate<br />
</pre><br />
<br />
{{Note|tcsh/csh shell users should run <code>source env/bin/activate.csh</code> instead.}}<br />
<br />
We also suggest the first thing you do is to ensure you have an updated version of pip installed in your environment. Make sure you have sourced your environment, and then run the following:<br />
<br />
<pre><br />
$ pip install --upgrade pip<br />
</pre><br />
<br />
In bash and tcsh, the environment can be deactivated by typing <code>deactivate</code><br />
<br />
====Installing Python Modules====<br />
Once you have created your virtual environment and sourced it, you can install additional modules using the 'pip' command.<br />
<br />
<pre><br />
$ pip install nose<br />
Collecting nose<br />
Downloading nose-1.3.7-py3-none-any.whl (154 kB)<br />
|████████████████████████████████| 154 kB 12.5 MB/s<br />
Installing collected packages: nose<br />
Successfully installed nose-1.3.7<br />
</pre><br />
<br />
====Listing installed Python Modules====<br />
<pre><br />
(env)$ pip freeze<br />
nose==1.3.7<br />
</pre><br />
<br />
====Uninstalling Python Modules====<br />
'pip' can also be used to remove a module from the environment.<br />
<pre><br />
$ pip uninstall nose<br />
Found existing installation: nose 1.3.7<br />
Uninstalling nose-1.3.7:<br />
Would remove:<br />
/nfshomes/liam/env/bin/nosetests<br />
/nfshomes/liam/env/bin/nosetests-3.4<br />
/nfshomes/liam/env/lib/python3.7/site-packages/nose-1.3.7.dist-info/*<br />
/nfshomes/liam/env/lib/python3.7/site-packages/nose/*<br />
/nfshomes/liam/env/man/man1/nosetests.1<br />
Proceed (y/n)? y<br />
Successfully uninstalled nose-1.3.7<br />
</pre><br />
<br />
===Switching between virtual environments===<br />
To switch between different environments, simply deactivate your current virtual environment, and source another.<br />
<pre><br />
(env)$ which python<br />
~/env/bin/python<br />
<br />
(env)$ deactivate <br />
<br />
$ source my-other-env/bin/activate<br />
<br />
(my-other-env)$ which python<br />
~/my-other-env/bin/python<br />
</pre><br />
<br />
==Using a different Python version==<br />
To create a virtual environment that uses a version of python that is different than the system default, create the virtualenv with your target version of Python. This could be a Python build we provide via [[Modules]], or one you've built yourself. Virtualenv will pick up the first python version it finds in your $PATH, or you can direct it to a specific location with the "--python" flag.<br />
<br />
<pre><br />
$ module load Python3<br />
<br />
$ which python3<br />
/opt/local/stow/Python3-3.8.1/bin/python3<br />
</pre><br />
<br />
'''Important:''' virtualenv will include any modules listed in your PYTHONPATH when initializing the virtual environment. To ensure a vanilla environment, it might be a good idea to verify your PYTHONPATH is empty.<br />
<br />
<pre><br />
$ echo $PYTHONPATH<br />
<br />
</pre><br />
<br />
<pre><br />
$ python3 -m venv env36<br />
<br />
$ source env36/bin/activate<br />
(env36) $ which python<br />
~/env36/bin/python<br />
</pre></div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=PythonVirtualEnv&diff=8886PythonVirtualEnv2020-02-10T15:54:39Z<p>Liam: </p>
<hr />
<div>A virtual environment is an isolated working copy of Python, which allows you to work on specific projects without affecting others. It creates an environment that has its own installation directories and that does not share libraries with other virtualenv environments (and optionally doesn’t access the globally-installed libraries either).<br />
<br />
==Basic Usage==<br />
The following steps outline how to create a virtual environment using the system Python.<br />
<br />
====Creating the virtual environment on Python 3====<br />
Python 3 comes with the virtualenv module built in.<br />
<pre><br />
$ python3 -m venv env<br />
</pre><br />
<br />
====Creating the virtual environment on Python 2 (deprecated)====<br />
<pre><br />
$ git clone https://github.com/pypa/virtualenv.git<br />
$ python virtualenv/virtualenv.py env<br />
New python executable in env/bin/python<br />
Installing setuptools.............done.<br />
</pre><br />
<br />
====Activating the VirtualEnv====<br />
You will need to use the 'source' command to load it into your shell environment.<br />
<pre><br />
$ source env/bin/activate<br />
</pre><br />
<br />
We also suggest the first thing you do is to ensure you have an updated version of pip installed in your environment. Make sure you have sourced your environment, and then run the following:<br />
<br />
<pre><br />
$ pip install --upgrade pip<br />
</pre><br />
<br />
In bash and tcsh, the environment can be deactivated by typing <code>deactivate</code><br />
<br />
====Installing Python Modules====<br />
Once you have created your virtual environment and sourced it, you can install additional modules using the 'pip' command.<br />
<br />
<pre><br />
$ pip install nose<br />
Collecting nose<br />
Downloading nose-1.3.7-py3-none-any.whl (154 kB)<br />
|████████████████████████████████| 154 kB 12.5 MB/s<br />
Installing collected packages: nose<br />
Successfully installed nose-1.3.7<br />
</pre><br />
<br />
====Listing installed Python Modules====<br />
<pre><br />
(env)$ pip freeze<br />
nose==1.3.7<br />
</pre><br />
<br />
====Uninstalling Python Modules====<br />
'pip' can also be used to remove a module from the environment.<br />
<pre><br />
$ pip uninstall nose<br />
Found existing installation: nose 1.3.7<br />
Uninstalling nose-1.3.7:<br />
Would remove:<br />
/nfshomes/liam/env/bin/nosetests<br />
/nfshomes/liam/env/bin/nosetests-3.4<br />
/nfshomes/liam/env/lib/python3.7/site-packages/nose-1.3.7.dist-info/*<br />
/nfshomes/liam/env/lib/python3.7/site-packages/nose/*<br />
/nfshomes/liam/env/man/man1/nosetests.1<br />
Proceed (y/n)? y<br />
Successfully uninstalled nose-1.3.7<br />
</pre><br />
<br />
===Switching between virtual environments===<br />
To switch between different environments, simply deactivate your current virtual environment, and source another.<br />
<pre><br />
(env)$ which python<br />
~/env/bin/python<br />
<br />
(env)$ deactivate <br />
<br />
$ source my-other-env/bin/activate<br />
<br />
(my-other-env)$ which python<br />
~/my-other-env/bin/python<br />
</pre><br />
<br />
==Using a different Python version==<br />
To create a virtual environment that uses a version of python that is different than the system default, create the virtualenv with your target version of Python. This could be a Python build we provide via [[Modules]], or one you've built yourself. Virtualenv will pick up the first python version it finds in your $PATH, or you can direct it to a specific location with the "--python" flag.<br />
<br />
<pre><br />
$ module load Python3<br />
<br />
$ which python3<br />
/opt/local/stow/Python3-3.8.1/bin/python3<br />
</pre><br />
<br />
'''Important:''' virtualenv will include any modules listed in your PYTHONPATH when initializing the virtual environment. To ensure a vanilla environment, it might be a good idea to verify your PYTHONPATH is empty.<br />
<br />
<pre><br />
$ echo $PYTHONPATH<br />
<br />
</pre><br />
<br />
<pre><br />
$ python3 -m venv env36<br />
<br />
$ source env36/bin/activate<br />
(env36) $ which python<br />
~/env36/bin/python<br />
</pre></div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=PythonVirtualEnv&diff=8885PythonVirtualEnv2020-02-07T23:54:29Z<p>Liam: /* Creating the virtual environment (Python 3) */</p>
<hr />
<div>A virtual environment is an isolated working copy of Python, which allows you to work on specific projects without affecting others. It creates an environment that has its own installation directories and that does not share libraries with other virtualenv environments (and optionally doesn’t access the globally-installed libraries either).<br />
<br />
While virtualenv should be installed on <I>most</I> UMIACS supported machines, the source can be downloaded from the project's GitHub: https://github.com/pypa/virtualenv<br />
<br />
==Basic Usage==<br />
The following steps outline how to create a virtual environment using the system Python.<br />
<br />
====Creating the virtual environment (Python 2)====<br />
<pre><br />
$ git clone https://github.com/pypa/virtualenv.git<br />
$ python virtualenv/virtualenv.py env<br />
New python executable in env/bin/python<br />
Installing setuptools.............done.<br />
<br />
$ source env/bin/activate<br />
<br />
(env)$ which python<br />
~/env/bin/python<br />
</pre><br />
<br />
====Creating the virtual environment (Python 3)====<br />
Python 3 comes with the virtualenv module built in.<br />
<pre><br />
$ python3 -m venv env<br />
</pre><br />
<br />
We also suggest the first thing you do is to ensure you have an updated version of pip installed in your environment. Make sure you have sourced your environment, and then run the following.<br />
<br />
<pre><br />
$ pip install --upgrade pip<br />
</pre><br />
<br />
You will notice that once you have created your virtual environment, you will need to use the 'source' command to load it into your environment. In bash and tcsh, the environment can be deactivated by typing <code>deactivate</code><br />
<br />
====Installing Python Modules====<br />
Once you have created your virtual environment and sourced it, you can install additional modules using the 'pip' command.<br />
<br />
<pre><br />
(env)$ pip install nose<br />
Downloading/unpacking nose<br />
Downloading nose-1.3.3.tar.gz (274Kb): 274Kb downloaded<br />
Running setup.py egg_info for package nose<br />
<br />
...output omitted for brevity...<br />
<br />
Successfully installed nose<br />
Cleaning up...<br />
(env)$ <br />
</pre><br />
<br />
====Listing installed Python Modules====<br />
<pre><br />
(env)$ pip freeze<br />
nose==1.3.3<br />
</pre><br />
====Uninstalling Python Modules====<br />
'pip' can also be used to remove a module from the environment.<br />
<pre><br />
(env)$ pip uninstall nose<br />
Uninstalling nose:<br />
/chimerahomes/sabobbin/env/bin/nosetests<br />
/chimerahomes/sabobbin/env/bin/nosetests-2.4<br />
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose<br />
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose-1.3.3-py2.4.egg-info<br />
/chimerahomes/sabobbin/env/man/man1/nosetests.1<br />
Proceed (y/n)? y<br />
Successfully uninstalled nose<br />
</pre><br />
<br />
===Switching between virtual environments===<br />
To switch between different environments, simply deactivate your current virtual environment, and source the other.<br />
<pre><br />
(env)$ which python<br />
~/env/bin/python<br />
<br />
(env)$ deactivate <br />
<br />
$ source env2.7/bin/activate<br />
<br />
(env2.7)$ which python<br />
~/env2.7/bin/python<br />
</pre><br />
<br />
==Using a different python version==<br />
To create a virtual environment that uses a version of python that is different then the system default, simply create the virtualenv with your target version of Python. This could be a Python build we provide via [[Modules]], or one you've built yourself. Virtualenv will pick up the first python version it finds in your $PATH, or you can direct it to a specific location with the "--python" flag.<br />
<br />
<pre><br />
$ module load Python<br />
<br />
$ which python<br />
/usr/local/stow/python-2.7.2/bin/python<br />
</pre><br />
'''Important:''' virtualenv will include any modules listed in your PYTHONPATH when initializing the virtual environment. To ensure a vanilla environment, it might be a good idea to verify your PYTHONPATH is empty.<br />
<pre><br />
$ echo $PYTHONPATH<br />
/usr/local/stow/python-commonmodules-2.7.2.0/lib/python2.7/site-packages<br />
<br />
$ PYTHONPATH=''<br />
</pre><br />
<pre><br />
$ /usr/local/stow/virtualenv-1.5.1/virtualenv.py env2.7<br />
New python executable in env2.7/bin/python<br />
Installing setuptools....................done.<br />
<br />
$ source env2.7/bin/activate<br />
(env2.7)$ which python<br />
~/env2.7/bin/python<br />
</pre></div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=PythonVirtualEnv&diff=8884PythonVirtualEnv2020-02-07T23:54:09Z<p>Liam: </p>
<hr />
<div>A virtual environment is an isolated working copy of Python, which allows you to work on specific projects without affecting others. It creates an environment that has its own installation directories and that does not share libraries with other virtualenv environments (and optionally doesn’t access the globally-installed libraries either).<br />
<br />
While virtualenv should be installed on <I>most</I> UMIACS supported machines, the source can be downloaded from the project's GitHub: https://github.com/pypa/virtualenv<br />
<br />
==Basic Usage==<br />
The following steps outline how to create a virtual environment using the system Python.<br />
<br />
====Creating the virtual environment (Python 2)====<br />
<pre><br />
$ git clone https://github.com/pypa/virtualenv.git<br />
$ python virtualenv/virtualenv.py env<br />
New python executable in env/bin/python<br />
Installing setuptools.............done.<br />
<br />
$ source env/bin/activate<br />
<br />
(env)$ which python<br />
~/env/bin/python<br />
</pre><br />
<br />
====Creating the virtual environment (Python 3)====<br />
Python 3 comes with the virtualenv module built in.<br />
<pre><br />
opensub03:~ $ python3 -m venv env<br />
</pre><br />
<br />
We also suggest the first thing you do is to ensure you have an updated version of pip installed in your environment. Make sure you have sourced your environment, and then run the following.<br />
<br />
<pre><br />
pip install --upgrade pip<br />
</pre><br />
<br />
You will notice that once you have created your virtual environment, you will need to use the 'source' command to load it into your environment. In bash and tcsh, the environment can be deactivated by typing <code>deactivate</code><br />
<br />
====Installing Python Modules====<br />
Once you have created your virtual environment and sourced it, you can install additional modules using the 'pip' command.<br />
<br />
<pre><br />
(env)$ pip install nose<br />
Downloading/unpacking nose<br />
Downloading nose-1.3.3.tar.gz (274Kb): 274Kb downloaded<br />
Running setup.py egg_info for package nose<br />
<br />
...output omitted for brevity...<br />
<br />
Successfully installed nose<br />
Cleaning up...<br />
(env)$ <br />
</pre><br />
<br />
====Listing installed Python Modules====<br />
<pre><br />
(env)$ pip freeze<br />
nose==1.3.3<br />
</pre><br />
====Uninstalling Python Modules====<br />
'pip' can also be used to remove a module from the environment.<br />
<pre><br />
(env)$ pip uninstall nose<br />
Uninstalling nose:<br />
/chimerahomes/sabobbin/env/bin/nosetests<br />
/chimerahomes/sabobbin/env/bin/nosetests-2.4<br />
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose<br />
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose-1.3.3-py2.4.egg-info<br />
/chimerahomes/sabobbin/env/man/man1/nosetests.1<br />
Proceed (y/n)? y<br />
Successfully uninstalled nose<br />
</pre><br />
<br />
===Switching between virtual environments===<br />
To switch between different environments, simply deactivate your current virtual environment, and source the other.<br />
<pre><br />
(env)$ which python<br />
~/env/bin/python<br />
<br />
(env)$ deactivate <br />
<br />
$ source env2.7/bin/activate<br />
<br />
(env2.7)$ which python<br />
~/env2.7/bin/python<br />
</pre><br />
<br />
==Using a different python version==<br />
To create a virtual environment that uses a version of python that is different then the system default, simply create the virtualenv with your target version of Python. This could be a Python build we provide via [[Modules]], or one you've built yourself. Virtualenv will pick up the first python version it finds in your $PATH, or you can direct it to a specific location with the "--python" flag.<br />
<br />
<pre><br />
$ module load Python<br />
<br />
$ which python<br />
/usr/local/stow/python-2.7.2/bin/python<br />
</pre><br />
'''Important:''' virtualenv will include any modules listed in your PYTHONPATH when initializing the virtual environment. To ensure a vanilla environment, it might be a good idea to verify your PYTHONPATH is empty.<br />
<pre><br />
$ echo $PYTHONPATH<br />
/usr/local/stow/python-commonmodules-2.7.2.0/lib/python2.7/site-packages<br />
<br />
$ PYTHONPATH=''<br />
</pre><br />
<pre><br />
$ /usr/local/stow/virtualenv-1.5.1/virtualenv.py env2.7<br />
New python executable in env2.7/bin/python<br />
Installing setuptools....................done.<br />
<br />
$ source env2.7/bin/activate<br />
(env2.7)$ which python<br />
~/env2.7/bin/python<br />
</pre></div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=PythonVirtualEnv&diff=8883PythonVirtualEnv2020-02-07T23:52:18Z<p>Liam: </p>
<hr />
<div>A virtual environment is an isolated working copy of Python, which allows you to work on specific projects without affecting others. It creates an environment that has its own installation directories and that does not share libraries with other virtualenv environments (and optionally doesn’t access the globally-installed libraries either).<br />
<br />
While virtualenv should be installed on <I>most</I> UMIACS supported machines, the source can be downloaded from the project's GitHub: https://github.com/pypa/virtualenv<br />
<br />
==Basic Usage==<br />
The following steps outline how to create a virtual environment using the system Python.<br />
<br />
====Creating the virtual environment (Python 2)====<br />
<pre><br />
-bash-3.2$ git clone https://github.com/pypa/virtualenv.git<br />
-bash-3.2$ python virtualenv/virtualenv.py env<br />
New python executable in env/bin/python<br />
Installing setuptools.............done.<br />
<br />
-bash-3.2$ source env/bin/activate<br />
<br />
(env)-bash-3.2$ which python<br />
~/env/bin/python<br />
</pre><br />
<br />
====Creating the virtual environment (Python 3)====<br />
Python 3 comes with the virtualenv module built in.<br />
<pre><br />
opensub03:~ $ python3 -m venv env<br />
</pre><br />
<br />
We also suggest the first thing you do is to ensure you have an updated version of pip installed in your environment. Make sure you have sourced your environment, and then run the following.<br />
<br />
<pre><br />
pip install --upgrade pip<br />
</pre><br />
<br />
You will notice that once you have created your virtual environment, you will need to use the 'source' command to load it into your environment. In bash and tcsh, the environment can be deactivated by typing <code>deactivate</code><br />
<br />
====Installing Python Modules====<br />
Once you have created your virtual environment and sourced it, you can install additional modules using the 'pip' command.<br />
<br />
<pre><br />
(env)-bash-3.2$ pip install nose<br />
Downloading/unpacking nose<br />
Downloading nose-1.3.3.tar.gz (274Kb): 274Kb downloaded<br />
Running setup.py egg_info for package nose<br />
<br />
...output omitted for brevity...<br />
<br />
Successfully installed nose<br />
Cleaning up...<br />
(env)-bash-3.2$ <br />
</pre><br />
<br />
====Listing installed Python Modules====<br />
<pre><br />
(env)-bash-3.2$ pip freeze<br />
nose==1.3.3<br />
</pre><br />
====Uninstalling Python Modules====<br />
'pip' can also be used to remove a module from the environment.<br />
<pre><br />
(env)-bash-3.2$ pip uninstall nose<br />
Uninstalling nose:<br />
/chimerahomes/sabobbin/env/bin/nosetests<br />
/chimerahomes/sabobbin/env/bin/nosetests-2.4<br />
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose<br />
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose-1.3.3-py2.4.egg-info<br />
/chimerahomes/sabobbin/env/man/man1/nosetests.1<br />
Proceed (y/n)? y<br />
Successfully uninstalled nose<br />
</pre><br />
<br />
===Switching between virtual environments===<br />
To switch between different environments, simply deactivate your current virtual environment, and source the other.<br />
<pre><br />
(env)-bash-3.2$ which python<br />
~/env/bin/python<br />
<br />
(env)-bash-3.2$ deactivate <br />
<br />
-bash-3.2$ source env2.7/bin/activate<br />
<br />
(env2.7)-bash-3.2$ which python<br />
~/env2.7/bin/python<br />
</pre><br />
<br />
==Using a different python version==<br />
To create a virtual environment that uses a version of python that is different then the system default, simply create the virtualenv with your target version of Python. This could be a Python build we provide via [[Modules]], or one you've built yourself. Virtualenv will pick up the first python version it finds in your $PATH, or you can direct it to a specific location with the "--python" flag.<br />
<br />
<pre><br />
-bash-3.2$ module load Python<br />
<br />
-bash-3.2$ which python<br />
/usr/local/stow/python-2.7.2/bin/python<br />
</pre><br />
'''Important:''' virtualenv will include any modules listed in your PYTHONPATH when initializing the virtual environment. To ensure a vanilla environment, it might be a good idea to verify your PYTHONPATH is empty.<br />
<pre><br />
-bash-3.2$ echo $PYTHONPATH<br />
/usr/local/stow/python-commonmodules-2.7.2.0/lib/python2.7/site-packages<br />
<br />
-bash-3.2$ PYTHONPATH=''<br />
</pre><br />
<pre><br />
-bash-3.2$ /usr/local/stow/virtualenv-1.5.1/virtualenv.py env2.7<br />
New python executable in env2.7/bin/python<br />
Installing setuptools....................done.<br />
<br />
-bash-3.2$ source env2.7/bin/activate<br />
(env2.7)-bash-3.2$ which python<br />
~/env2.7/bin/python<br />
</pre></div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=PythonVirtualEnv&diff=8882PythonVirtualEnv2020-02-07T23:48:25Z<p>Liam: </p>
<hr />
<div>A virtual environment is an isolated working copy of Python, which allows you to work on specific projects without affecting others. It creates an environment that has its own installation directories and that does not share libraries with other virtualenv environments (and optionally doesn’t access the globally-installed libraries either).<br />
<br />
While virtualenv should be installed on <I>most</I> UMIACS supported machines, the source can be downloaded from the project's GitHub: https://github.com/pypa/virtualenv<br />
<br />
==Basic Usage==<br />
The following steps outline how to create a virtual environment using the system Python.<br />
''Please note the that following examples were done using RHEL5. Please adjust the commands to reflect the OS you are on.''<br />
<br />
====Creating the virtual environment (example)====<br />
<pre><br />
-bash-3.2$ git clone https://github.com/pypa/virtualenv.git<br />
-bash-3.2$ python virtualenv/virtualenv.py env<br />
New python executable in env/bin/python<br />
Installing setuptools.............done.<br />
<br />
-bash-3.2$ source env/bin/activate<br />
<br />
(env)-bash-3.2$ which python<br />
~/env/bin/python<br />
</pre><br />
<br />
We also suggest the first thing you do is to ensure you have an updated version of pip installed in your environment. Make sure you have sourced your environment, and then run the following.<br />
<br />
<pre><br />
pip install --upgrade pip<br />
</pre><br />
<br />
You will notice that once you have created your virtual environment, you will need to use the 'source' command to load it into your environment. In bash and tcsh, the environment can be deactivated by typing <code>deactivate</code><br />
<br />
====Installing Python Modules====<br />
Once you have created your virtual environment and sourced it, you can install additional modules using the 'pip' command.<br />
<br />
<pre><br />
(env)-bash-3.2$ pip install nose<br />
Downloading/unpacking nose<br />
Downloading nose-1.3.3.tar.gz (274Kb): 274Kb downloaded<br />
Running setup.py egg_info for package nose<br />
<br />
...output omitted for brevity...<br />
<br />
Successfully installed nose<br />
Cleaning up...<br />
(env)-bash-3.2$ <br />
</pre><br />
<br />
====Listing installed Python Modules====<br />
<pre><br />
(env)-bash-3.2$ pip freeze<br />
nose==1.3.3<br />
</pre><br />
====Uninstalling Python Modules====<br />
'pip' can also be used to remove a module from the environment.<br />
<pre><br />
(env)-bash-3.2$ pip uninstall nose<br />
Uninstalling nose:<br />
/chimerahomes/sabobbin/env/bin/nosetests<br />
/chimerahomes/sabobbin/env/bin/nosetests-2.4<br />
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose<br />
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose-1.3.3-py2.4.egg-info<br />
/chimerahomes/sabobbin/env/man/man1/nosetests.1<br />
Proceed (y/n)? y<br />
Successfully uninstalled nose<br />
</pre><br />
<br />
===Switching between virtual environments===<br />
To switch between different environments, simply deactivate your current virtual environment, and source the other.<br />
<pre><br />
(env)-bash-3.2$ which python<br />
~/env/bin/python<br />
<br />
(env)-bash-3.2$ deactivate <br />
<br />
-bash-3.2$ source env2.7/bin/activate<br />
<br />
(env2.7)-bash-3.2$ which python<br />
~/env2.7/bin/python<br />
</pre><br />
<br />
==Using a different python version==<br />
To create a virtual environment that uses a version of python that is different then the system default, simply create the virtualenv with your target version of Python. This could be a Python build we provide via [[Modules]], or one you've built yourself. Virtualenv will pick up the first python version it finds in your $PATH, or you can direct it to a specific location with the "--python" flag.<br />
<br />
<pre><br />
-bash-3.2$ module load Python<br />
<br />
-bash-3.2$ which python<br />
/usr/local/stow/python-2.7.2/bin/python<br />
</pre><br />
'''Important:''' virtualenv will include any modules listed in your PYTHONPATH when initializing the virtual environment. To ensure a vanilla environment, it might be a good idea to verify your PYTHONPATH is empty.<br />
<pre><br />
-bash-3.2$ echo $PYTHONPATH<br />
/usr/local/stow/python-commonmodules-2.7.2.0/lib/python2.7/site-packages<br />
<br />
-bash-3.2$ PYTHONPATH=''<br />
</pre><br />
<pre><br />
-bash-3.2$ /usr/local/stow/virtualenv-1.5.1/virtualenv.py env2.7<br />
New python executable in env2.7/bin/python<br />
Installing setuptools....................done.<br />
<br />
-bash-3.2$ source env2.7/bin/activate<br />
(env2.7)-bash-3.2$ which python<br />
~/env2.7/bin/python<br />
</pre></div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=OpenCVVersions&diff=8872OpenCVVersions2020-01-30T21:24:03Z<p>Liam: </p>
<hr />
<div>== WIN32 ==<br />
These directions are for 64-bit systems<br />
First, we install OpenCV<br />
# Download the desired version of OpenCV from [https://opencv.org/releases/ here]<br />
# Double click the downloaded executable to install, and select <code> run</code> at the prompt<br />
# Choose a home directory as installation location home directory as shown below, where "username" is the actual username.<br />
# Click extract, to install OpenCV files<br />
#* [[File: Install_location.png|400px]]<br />
#** Click to enlarge<br />
==== Without CUDA ====<br />
<ol><br />
The path to the folder you extracted is from here on refered to as ''{OPENCV}''<br />
</ol><br />
Next, we setup environmental variables<br />
#Navigate to <code>Control Panel</code> -> <code>System and Security</code> -> <code>System</code><br />
# Select <code>Advanced system settings</code> from the sidebar<br />
# In the <code>Advanced</code> tab click the <code>Environment Variables...</code> button<br />
# Check if a Variable called <code>Path</code> exists in the list of user variables (the top variables)<br />
#* If it exists, click edit to edit the variable, and add a semicolon, then the following to the end of the Path value <code>''{OPENCV}''\build\x64\vc10\bin</code> <br />
<!---#** vc10 should be replaced with vc11 or vc12 depending on the version of visual studio installed In this case: --><br />
#* If it does not, press the New button and set the variable name to <code>Path</code> and the value to the path to your opencv directory (''{OPENCV}'')<br />
<br />
==== Visual Studio Project Set-Up ====<br />
# Go to Project -> Properties<br />
#* Configuration Properties -> C/C++ -> General<br />
#** Additional Include Directories...add: '''{OPENCV}''\build\include;'<br />
#* Configuration Properties -> VC++ Directories<br />
#** Executable Directories...add: '''{OPENCV}''\build\x64\vc10\bin;'<br />
#** Library Directories...add: '''{OPENCV}''\build\x64\vc10\lib;''{OPENCV}''\build\x64\vc10\staticlib;'<br />
<br />
==== More Information ====<br />
* For using OpenCV with Visiual Studio; http://docs.opencv.org/doc/tutorials/introduction/windows_install/windows_install.html#windows-installation<br />
* For using OpenCV with CUDA; http://blog.cuvilib.com/2011/03/22/how-to-build-opencv-2-2-with-gpu-cuda-on-windows-7/</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=8870Main Page2020-01-23T21:24:02Z<p>Liam: </p>
<hr />
<div>==Announcements==<br />
Please see our [https://intranet.umiacs.umd.edu intranet] page for announcements.<br />
<br />
==Technical Reference==<br />
<br />
; [[GettingStarted | Getting Started]]<br />
: Broad introduction to UMIACS Accounts and services.<br />
; [[CoreServices | Core Services]]<br />
: Information about UMIACS service offerings including [[EMail]], [[LocalDataStorage | Data Storage]], [[Backups]], and our [[VPN]].<br />
; [[Orders | Ordering Equipment]]<br />
: Information on ordering equipment requests and best practices.<br />
; [[LabFacilities| Lab Facilities]]<br />
: Information on the various labs and centers within UMIACS.<br />
; [[HelpDesk | Getting help (UMIACS Help Desk)]]<br />
: Information on UMIACS Support and how to contact us.<br />
<br />
==General Information==<br />
* University of Maryland [http://it.umd.edu/aup Acceptable Use Policy (AUP)]<br />
* [http://www.umd.edu/web-accessibility Web Accessibility]<br />
__NOTOC__</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=GitLab&diff=8869GitLab2020-01-23T21:20:44Z<p>Liam: /* Make GitLab projects public */</p>
<hr />
<div>GitLab is source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 10 projects with a hard limit of 800Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab.<br />
<br />
To get started, navigate to the following URL in your browser, you will be redirected to UMIACS Single Sign On where you can login with your UMIACS credentials:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client. <br />
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.<br />
<br />
<br />
==GitLab Offsite Collaborators==<br />
Any UMIACS user can now create an unlimited number of offsite<br />
collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create<br />
repositories or groups, but may be given access to your repositories or<br />
groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
==User Documentation==<br />
GitLab provides user documentation that can be accessed at https://gitlab.umiacs.umd.edu/help<br />
<br />
Some of the most useful sections include:<br />
* Permissions and user roles - https://gitlab.umiacs.umd.edu/help/user/permissions.md<br />
* GitLab markdown for wikis and READMEs - https://gitlab.umiacs.umd.edu/help/user/markdown.md<br />
<br />
==Repository URLs== <br />
Users can clone git repos over either SSH or HTTPS. '''We recommend using SSH because it is more convenient for most users.''' The blue "Clone" button in the upper-right corner of your GitLab project page will contain the clone URL for whichever authentication method you prefer.<br />
<br />
===SSH===<br />
To use SSH, add an SSH key to your Gitlab account. Instructions to do so can be found [https://gitlab.umiacs.umd.edu/help/ssh/README here]. Once you have the SSH key added, you can authenticate without having to enter any credentials from the machine and account for which you created the SSH key if your keys is not password-protected.<br />
<br />
===HTTPS===<br />
The HTTPS URL can be used as well, but you will need to setup Personal Access Tokens in order to connect. Instructions to create one can be found [https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html here]. Once you have a token, you can use that as your password when prompted. You will have to re-enter your credentials for GitLab every single time that you attempt to commit to, push to, pull from, or otherwise access the remote repository.<br />
<br />
==Make GitLab projects public==<br />
Making projects public grants access to everyone. Projects can only made public by the owner. To make your projects on GitLab public, follow the steps below:<br />
<br />
1. Go to your project page.<br />
<br />
2. Click on '''Settings'''.<br />
<br />
3. Scroll down to '''Project Visibility'''. Choose '''Public''' from the drop-down menu.<br />
<br />
4. Scroll down and click on '''Save Changes'''<br />
<br />
5. Scroll down to '''Repository''' under '''Project Visibility''' and select '''Everyone with access''' from the drop-down menu.<br />
<br />
6. Click on '''Save Changes'''.<br />
<br />
Now your project has become public with its repository accessible by anyone.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=GitLab&diff=8868GitLab2020-01-23T21:20:22Z<p>Liam: /* Make GitLab projects public */</p>
<hr />
<div>GitLab is source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 10 projects with a hard limit of 800Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab.<br />
<br />
To get started, navigate to the following URL in your browser, you will be redirected to UMIACS Single Sign On where you can login with your UMIACS credentials:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client. <br />
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.<br />
<br />
<br />
==GitLab Offsite Collaborators==<br />
Any UMIACS user can now create an unlimited number of offsite<br />
collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create<br />
repositories or groups, but may be given access to your repositories or<br />
groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
==User Documentation==<br />
GitLab provides user documentation that can be accessed at https://gitlab.umiacs.umd.edu/help<br />
<br />
Some of the most useful sections include:<br />
* Permissions and user roles - https://gitlab.umiacs.umd.edu/help/user/permissions.md<br />
* GitLab markdown for wikis and READMEs - https://gitlab.umiacs.umd.edu/help/user/markdown.md<br />
<br />
==Repository URLs== <br />
Users can clone git repos over either SSH or HTTPS. '''We recommend using SSH because it is more convenient for most users.''' The blue "Clone" button in the upper-right corner of your GitLab project page will contain the clone URL for whichever authentication method you prefer.<br />
<br />
===SSH===<br />
To use SSH, add an SSH key to your Gitlab account. Instructions to do so can be found [https://gitlab.umiacs.umd.edu/help/ssh/README here]. Once you have the SSH key added, you can authenticate without having to enter any credentials from the machine and account for which you created the SSH key if your keys is not password-protected.<br />
<br />
===HTTPS===<br />
The HTTPS URL can be used as well, but you will need to setup Personal Access Tokens in order to connect. Instructions to create one can be found [https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html here]. Once you have a token, you can use that as your password when prompted. You will have to re-enter your credentials for GitLab every single time that you attempt to commit to, push to, pull from, or otherwise access the remote repository.<br />
<br />
==Make GitLab projects public==<br />
Making projects public grants access to everyone. Projects can only made public by the owner. To make your projects on GitLab public, follow the steps below:<br />
<br />
1. Go to your project page.<br />
<br />
2. Click on '''Settings'''.<br />
<br />
3. Scroll down to '''Project Visibility'''. Choose '''Public''' from the drop-down menu.<br />
<br />
4. Scroll down and click on '''Save Changes'''<br />
<br />
5. Scroll down to '''Repository''' under '''Project Visibility''' and select '''Everyone with access''' from the drop-down menu.<br />
<br />
6. Click on '''Save Changes'''.<br />
<br />
<br />
Now your project has become public with its repository accessible anyone with access.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=GitLab&diff=8867GitLab2020-01-23T21:19:04Z<p>Liam: /* User Documentation */</p>
<hr />
<div>GitLab is source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 10 projects with a hard limit of 800Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab.<br />
<br />
To get started, navigate to the following URL in your browser, you will be redirected to UMIACS Single Sign On where you can login with your UMIACS credentials:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client. <br />
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.<br />
<br />
<br />
==GitLab Offsite Collaborators==<br />
Any UMIACS user can now create an unlimited number of offsite<br />
collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create<br />
repositories or groups, but may be given access to your repositories or<br />
groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
==User Documentation==<br />
GitLab provides user documentation that can be accessed at https://gitlab.umiacs.umd.edu/help<br />
<br />
Some of the most useful sections include:<br />
* Permissions and user roles - https://gitlab.umiacs.umd.edu/help/user/permissions.md<br />
* GitLab markdown for wikis and READMEs - https://gitlab.umiacs.umd.edu/help/user/markdown.md<br />
<br />
==Repository URLs== <br />
Users can clone git repos over either SSH or HTTPS. '''We recommend using SSH because it is more convenient for most users.''' The blue "Clone" button in the upper-right corner of your GitLab project page will contain the clone URL for whichever authentication method you prefer.<br />
<br />
===SSH===<br />
To use SSH, add an SSH key to your Gitlab account. Instructions to do so can be found [https://gitlab.umiacs.umd.edu/help/ssh/README here]. Once you have the SSH key added, you can authenticate without having to enter any credentials from the machine and account for which you created the SSH key if your keys is not password-protected.<br />
<br />
===HTTPS===<br />
The HTTPS URL can be used as well, but you will need to setup Personal Access Tokens in order to connect. Instructions to create one can be found [https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html here]. Once you have a token, you can use that as your password when prompted. You will have to re-enter your credentials for GitLab every single time that you attempt to commit to, push to, pull from, or otherwise access the remote repository.<br />
<br />
==Make GitLab projects public==<br />
Making projects public grants access to everyone. Projects can only made public by the owner. To make your projects on GitLab public and make repo accessible to everyone, follow the steps below:<br />
1. Go to your projects page https://gitlab.umiacs.umd.edu/<username>/<yourProjectName>.<br />
For example: https://gitlab.umiacs.umd.edu/suzantrt/someNewAwesomeProject<br />
2. Click on '''Settings'''.<br />
<br />
3. Scroll down to '''Project Visibility'''. Choose '''Public''' from the drop-down menu.<br />
<br />
4. Scroll down and click on '''Save Changes'''<br />
<br />
5. Scroll down to '''Repository''' under '''Project Visibility''' and select '''Everyone with access''' from the drop-down menu.<br />
<br />
6. Click on '''Save Changes'''.<br />
<br />
<br />
Now your project has become public with its repository accessible anyone with access.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=GitLab&diff=8866GitLab2020-01-23T21:17:57Z<p>Liam: </p>
<hr />
<div>GitLab is source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 10 projects with a hard limit of 800Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab.<br />
<br />
To get started, navigate to the following URL in your browser, you will be redirected to UMIACS Single Sign On where you can login with your UMIACS credentials:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client. <br />
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.<br />
<br />
<br />
==GitLab Offsite Collaborators==<br />
Any UMIACS user can now create an unlimited number of offsite<br />
collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create<br />
repositories or groups, but may be given access to your repositories or<br />
groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
==User Documentation==<br />
GitLab provides user documentation that can be accessed at https://gitlab.umiacs.umd.edu/help. <b>Note:</b> you will need to log in to view this page.<br />
<br />
Some of the most useful sections include:<br />
* Permissions and user roles - https://gitlab.umiacs.umd.edu/help/user/permissions.md<br />
* GitLab markdown for wikis and READMEs - https://gitlab.umiacs.umd.edu/help/user/markdown.md<br />
<br />
==Repository URLs== <br />
Users can clone git repos over either SSH or HTTPS. '''We recommend using SSH because it is more convenient for most users.''' The blue "Clone" button in the upper-right corner of your GitLab project page will contain the clone URL for whichever authentication method you prefer.<br />
<br />
===SSH===<br />
To use SSH, add an SSH key to your Gitlab account. Instructions to do so can be found [https://gitlab.umiacs.umd.edu/help/ssh/README here]. Once you have the SSH key added, you can authenticate without having to enter any credentials from the machine and account for which you created the SSH key if your keys is not password-protected.<br />
<br />
===HTTPS===<br />
The HTTPS URL can be used as well, but you will need to setup Personal Access Tokens in order to connect. Instructions to create one can be found [https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html here]. Once you have a token, you can use that as your password when prompted. You will have to re-enter your credentials for GitLab every single time that you attempt to commit to, push to, pull from, or otherwise access the remote repository.<br />
<br />
==Make GitLab projects public==<br />
Making projects public grants access to everyone. Projects can only made public by the owner. To make your projects on GitLab public and make repo accessible to everyone, follow the steps below:<br />
1. Go to your projects page https://gitlab.umiacs.umd.edu/<username>/<yourProjectName>.<br />
For example: https://gitlab.umiacs.umd.edu/suzantrt/someNewAwesomeProject<br />
2. Click on '''Settings'''.<br />
<br />
3. Scroll down to '''Project Visibility'''. Choose '''Public''' from the drop-down menu.<br />
<br />
4. Scroll down and click on '''Save Changes'''<br />
<br />
5. Scroll down to '''Repository''' under '''Project Visibility''' and select '''Everyone with access''' from the drop-down menu.<br />
<br />
6. Click on '''Save Changes'''.<br />
<br />
<br />
Now your project has become public with its repository accessible anyone with access.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=GitLab&diff=8865GitLab2020-01-23T21:15:56Z<p>Liam: </p>
<hr />
<div>GitLab is source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 10 projects with a hard limit of 800Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups (called namespaces) and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab.<br />
<br />
To get started, navigate to the following URL in your browser, you will be redirected to UMIACS Single Sign On where you can login with your UMIACS credentials:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client. <br />
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.<br />
<br />
<br />
==GitLab Offsite Collaborators==<br />
Any UMIACS user can now create an unlimited number of offsite<br />
collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create<br />
repositories or groups, but may be given access to your repositories or<br />
groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
==User Documentation==<br />
GitLab provides user documentation that can be accessed at https://gitlab.umiacs.umd.edu/help. <b>Note:</b> you will need to log in to view this page.<br />
<br />
Some of the most useful sections include:<br />
* Permissions and user roles - https://gitlab.umiacs.umd.edu/help/user/permissions.md<br />
* GitLab markdown for wikis and READMEs - https://gitlab.umiacs.umd.edu/help/user/markdown.md<br />
<br />
==Repository URLs== <br />
Users can clone git repos over either SSH or HTTPS. '''We recommend using SSH because it is more convenient for most users.''' The blue "Clone" button in the upper-right corner of your GitLab project page will contain the clone URL for whichever authentication method you prefer.<br />
<br />
===SSH===<br />
To use SSH, add an SSH key to your Gitlab account. Instructions to do so can be found [https://gitlab.umiacs.umd.edu/help/ssh/README here]. Once you have the SSH key added, you can authenticate without having to enter any credentials from the machine and account for which you created the SSH key if your keys is not password-protected.<br />
<br />
===HTTPS===<br />
The HTTPS URL can be used as well, but you will need to setup Personal Access Tokens in order to connect. Instructions to create one can be found [https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html here]. Once you have a token, you can use that as your password when prompted. You will have to re-enter your credentials for GitLab every single time that you attempt to commit to, push to, pull from, or otherwise access the remote repository.<br />
<br />
==Make GitLab projects public==<br />
Making projects public grants access to everyone. Projects can only made public by the owner. To make your projects on GitLab public and make repo accessible to everyone, follow the steps below:<br />
1. Go to your projects page https://gitlab.umiacs.umd.edu/<username>/<yourProjectName>.<br />
For example: https://gitlab.umiacs.umd.edu/suzantrt/someNewAwesomeProject<br />
2. Click on '''Settings'''.<br />
<br />
3. Scroll down to '''Project Visibility'''. Choose '''Public''' from the drop-down menu.<br />
<br />
4. Scroll down and click on '''Save Changes'''<br />
<br />
5. Scroll down to '''Repository''' under '''Project Visibility''' and select '''Everyone with access''' from the drop-down menu.<br />
<br />
6. Click on '''Save Changes'''.<br />
<br />
<br />
Now your project has become public with its repository accessible anyone with access.</div>Liamhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=BashForWindows&diff=8825BashForWindows2020-01-13T15:46:03Z<p>Liam: nitpick: of -> for</p>
<hr />
<div>Microsoft has partnered with Canonical, the makers of [[Ubuntu]], to create a release of the [[Windows]] Subsystem for Linux (WSL), which allows Windows users to use Linux command line tools such as such as <code>grep</code>, <code>sed</code>, <code>git</code> on Windows files through [[Bash]]. <br />
<br />
==Prerequisites==<br />
In order to install Bash/WSL, you must be running a 64-bit version of either Windows 10 version 1607 or later or Windows Server 2019 or later. In Windows, open the Settings app > System > About to check if your Windows version is compatible. <br />
<br />
==Installation==<br />
<ol><br />
<li> First, turn on Developer Mode, open the Settings app > Update & security > For developers > Select the Developer radio button </li><br />
<li> Enable the Windows Subsystem for Linux, this can be done by turning on the feature through the Windows Features program or through a PowerShell session<br />
* For the GUI method: Go to Control Panel > Programs and Features > Turn Windows features on or off (this will require local administrator privileges > Check the box for Windows Subsystem on Linux<br />
* For PowerShell method (in an elevated/administrator session) use the command: <code> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux </code><br />
</li><br />
<li> Restart the system</li><br />
<li> Open a command prompt or PowerShell session, and then run <code>bash</code>. </li><br />
<li> After accepting the license, the Ubuntu user mode image will be installed. </li><br />
</ol><br />
<br />
==Use==<br />
Simply run <code>bash</code> in a command prompt or PowerShell session to enter bash. The first time Bash is installed on Windows, a prompt will appear to create a Unix user. This Unix user account is completely separate from the Windows user account and has <code> sudo </code> permissions on the WSL. There is no GUI that is installed, nor can be installed. <br />
<br />
The Linux installation is located at <code>%localappdata%\lxss\</code>, which is a hidden system folder. {{Note| Do '''not''' use Windows tools to edit the files or sub-files within this directory as corruption of the Linux files could occur.}} Windows storage and files can then be accessed from <code>/mnt/...</code>, such as <code>/mnt/c/Users/myAccount</code>.<br />
<br />
==External Links==<br />
*[https://msdn.microsoft.com/en-us/commandline/wsl/about Bash On Ubuntu On Windows]<br />
*[https://msdn.microsoft.com/en-us/commandline/wsl/install_guide Installation Guide]<br />
*[https://msdn.microsoft.com/en-us/commandline/wsl/reference Command Reference]<br />
*[https://msdn.microsoft.com/en-us/commandline/wsl/faq FAQ]<br />
*[https://msdn.microsoft.com/en-us/commandline/wsl/user_support Linux User Account Explanation]</div>Liam