https://wiki.umiacs.umd.edu/umiacs/api.php?action=feedcontributions&user=Suzantrt&feedformat=atomUMIACS - User contributions [en]2024-03-28T09:56:58ZUser contributionsMediaWiki 1.39.6https://wiki.umiacs.umd.edu/umiacs/index.php?title=GitLab&diff=7465GitLab2017-08-14T16:36:15Z<p>Suzantrt: Added note to update git client</p>
<hr />
<div>GitLab is source code collaboration software based on [[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 5 projects with a soft limit of 400Mb 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. The UMIACS [[ApplicationResource|AR]] system is '''not''' used with GitLab.<br />
<br />
To get started, navigate to the following URL in your browser and enter your UMIACS Krb5 credentials in the LDAP tab:<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 download and clone directories from the remote repository using git clone. There are two different URLs that can be used: HTTPS and SSH. <br />
You can view the URL underneath the Project title in the Project tab. Change the displayed URL by clicking on the URL type you want to see. <br />
===SSH===<br />
The SSH URL is more direct, though it is harder to set up. In order to do so, you will have to 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 log in without having to enter any credentials from the machine and account for which you created the SSH key. <br />
===HTTPS===<br />
The HTTPS URL is easier to set up- you just clone directly from the repository using the HTTPS URL. However, 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>Suzantrthttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Matlab&diff=7421Matlab2017-06-06T15:39:59Z<p>Suzantrt: /* Toolbox Shortnames */</p>
<hr />
<div>UMIACS has [[Matlab]] licenses that cover Linux, Windows and Mac. To access them you have to be using a university owned computer. If you would like to run Matlab on a machine that is not University-owned, you can check the pricing through OIT/SLIC [https://terpware.umd.edu/Windows/Title/1866 here].<br />
<br />
==Linux==<br />
Below are the different versions of Matlab across our supported Linux workstations and servers. The one in bold is our latest version. For more information, please see [http://www.mathworks.com/support/sysreq/roadmap.html this page].<br />
<br />
[[Modules]] are the preferred way to interact with Matlab. The Modules page will provide information on adding Matlab into your environment and using it.<br />
<br />
* /opt/common/matlab-r2007b<br />
* /opt/common/matlab-r2008a<br />
* /opt/common/matlab-r2008b<br />
* /opt/common/matlab-r2009b<br />
* /opt/common/matlab-r2010a<br />
* /opt/common/matlab-r2010b<br />
* /opt/common/matlab-r2011a<br />
* /opt/common/matlab-r2011b<br />
* /opt/common/matlab-r2012a<br />
* /opt/common/matlab-r2012b<br />
* /opt/common/matlab-r2013a<br />
* /opt/common/matlab-r2013b<br />
* /opt/common/matlab-r2014a<br />
* /opt/common/matlab-r2014b<br />
* '''/opt/common/matlab-r2015a'''<br />
<br />
==Windows==<br />
Below are the different locations of Matlab available for university-owned machines running Windows. The one in bold is the latest version we have available:<br />
<br />
* Matlab r2007a<br />
* Matlab r2007b<br />
* Matlab r2008a<br />
* Matlab r2008b<br />
* Matlab r2009a<br />
* Matlab r2009b<br />
* Matlab r2010a<br />
* Matlab r2010b<br />
* Matlab r2011a<br />
* Matlab r2011b<br />
* Matlab r2012a<br />
* Matlab r2012b<br />
* Matlab r2013a<br />
* Matlab r2013b<br />
* Matlab r2014a<br />
* Matlab r2014b<br />
* Matlab r2015a<br />
* '''Matlab r2016a'''<br />
<br />
==macOS==<br />
Below are the different locations of Matlab available for university-owned machines running macOS. We expect that all versions should run on macOS 10.8 and newer. The one in bold is the latest version we have available:<br />
<br />
* Matlab r2008a<br />
* Matlab r2008b<br />
* Matlab r2009b<br />
* Matlab r2010a<br />
* Matlab r2010b<br />
* Matlab r2011b<br />
* Matlab r2012a<br />
* Matlab r2012b<br />
* Matlab r2013a (macOS 10.8+)<br />
* '''Matlab r2013b''' (macOS 10.8+)<br />
<br />
==License Information==<br />
Campus has a limited number of seats for Matlab itself, as well as the various toolboxes. When calling functions in a toolbox, Matlab will automatically check out a license for that toolbox, making it temporarily unavailable to other users. If while attempting to use Matlab, you run into a license manager error stating that the maximum number of users for Matlab has been reached, this likely indicates that all of campus' available licenses are in use. To check the number of licenses available for a specific toolbox, please see the below sections:<br />
<br />
===Windows License Troubleshooting===<br />
On Windows machines, the necessary command is as follows. Please note that you may need to adjust the path to reflect the available Matlab versions and the installation path. Additionally, this assumes that you are using a 64-bit version. "win64" needs to be adjusted to "win32" on a 32-bit installation:<br />
$MATLAB_PATH\etc\win64\lmutil lmstat -c "$MATLAB_PATH\licenses\network.lic" -f $TOOLBOX_SHORTNAME<br />
<br />
As an example, here is how to query Matlab r2012b on a 64-bit Windows host for the Aerospace Blockset Toolbox: <br />
"C:\Program Files\matlab\r2012b\etc\win64\lmutil.exe" lmstat -c "C:\Program Files\matlab\r2012b\licenses\network.lic" -f Aerospace_Blockset<br />
<br />
===Unix License Troubleshooting===<br />
On Unix machines, the necessary command is as follows. Please note that you may need to adjust the path to reflect the available Matlab versions and the installation path. Additionally, this assumes that you are using a 64-bit version. "glnxa64" needs to adjusted to "glnx86" on a 32-bit installation::<br />
$MATLAB_PATH/etc/glnxa64/lmutil lmstat -c $MATLAB_PATH/licenses/network.lic -f $TOOLBOX_SHORTNAME<br />
<br />
As an example, here is how to query Matlab r2015a on our 64-bit RHEL6/RHEL7 hosts for the Parallel Computing Toolbox:<br />
/opt/common/matlab-r2015a/etc/glnxa64/lmutil lmstat -c /opt/common/matlab-r2015a/licenses/network.lic -f Video_and_Image_Blockset<br />
<br />
===Toolbox Shortnames===<br />
The toolbox names themselves don't always work with this command; rather, Matlab has a set of shortnames which can be passed to the lmstat command. The following are all the valid shortnames:<br />
<br />
Aerospace_Blockset <br />
Aerospace_Toolbox<br />
Antenna_Toolbox <br />
Bioinformatics_Toolbox <br />
Communication_Blocks <br />
Communication_Toolbox <br />
Compiler <br />
Control_Toolbox <br />
Curve_Fitting_Toolbox <br />
Data_Acq_Toolbox <br />
Database_Toolbox <br />
Datafeed_Toolbox <br />
Distrib_Computing_Toolbox <br />
Econometrics_Toolbox <br />
Excel_Link <br />
Fin_Derivatives_Toolbox<br />
Fin_Instruments_Toolbox <br />
Financial_Toolbox <br />
Fixed_Income_Toolbox <br />
Fixed_Point_Toolbox<br />
Fuzzy_Toolbox <br />
GADS_Toolbox <br />
Identification_Toolbox <br />
Image_Acquisition_Toolbox <br />
Image_Toolbox <br />
Instr_Control_Toolbox <br />
MAP_Toolbox <br />
MATLAB <br />
MATLAB_Builder_for_Java <br />
MATLAB_Coder <br />
MATLAB_Excel_Builder <br />
MATLAB_Report_Gen <br />
MPC_Toolbox <br />
Neural_Network_Toolbox <br />
Optimization_Toolbox<br />
OPC_Toolbox <br />
PDE_Toolbox<br />
Phased_Array_System_Toolbox <br />
Real-Time_Workshop <br />
Robotics_System_Toolbox <br />
Robust_Toolbox<br />
RTW_Embedded_Coder<br />
Signal_Blocks <br />
Signal_Toolbox<br />
SimEvents <br />
SimMechanics <br />
Simscape <br />
SIMULINK <br />
Simulink_Control_Design<br />
Simulink_Design_Optim <br />
Stateflow <br />
Stateflow_Coder <br />
Statistics_Toolbox <br />
Symbolic_Toolbox <br />
Video_and_Image_Blockset <br />
Virtual_Reality_Toolbox <br />
Wavelet_Toolbox<br />
<br />
If you are having problems, feel free to contact [[HelpDesk | UMIACS Staff]], however please note that the Matlab license servers are hosted by campus' Division of Information Technology.<br />
<br />
==Matlab Customizations==<br />
You can tweak your Matlab experience using a file "startup.m". If this file is present in the current working directory where you launch Matlab, it will be executed. You can perform a variety of tasks using this file. These include (but are not limited to) customizing the window environment, setting variables for later use, and enabling use of 3rd party toolboxes. Alternatively, you can use the userpath env variable to set a path other than the current working directory for startup and 3rd party toolbox locations. Please see the following links for more information:<br />
<br />
* [http://www.mathworks.com/help/matlab/ref/matlabrc.html Mathworks: Startup.m]<br />
* [http://www.mathworks.com/help/matlab/matlab_env/startup-folder-for-the-matlab-program.html#bs6j57e-5 Mathworks: Userpath function]</div>Suzantrthttps://wiki.umiacs.umd.edu/umiacs/index.php?title=GitLab&diff=7419GitLab2017-05-26T20:11:32Z<p>Suzantrt: added instructions to make GitLab projects public</p>
<hr />
<div>GitLab is source code collaboration software based on [[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 5 projects with a soft limit of 400Mb 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. The UMIACS [[ApplicationResource|AR]] system is '''not''' used with GitLab.<br />
<br />
To get started, navigate to the following URL in your browser and enter your UMIACS Krb5 credentials in the LDAP tab:<br />
<br />
https://gitlab.umiacs.umd.edu<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 download and clone directories from the remote repository using git clone. There are two different URLs that can be used: HTTPS and SSH. <br />
You can view the URL underneath the Project title in the Project tab. Change the displayed URL by clicking on the URL type you want to see. <br />
===SSH===<br />
The SSH URL is more direct, though it is harder to set up. In order to do so, you will have to 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 log in without having to enter any credentials from the machine and account for which you created the SSH key. <br />
===HTTPS===<br />
The HTTPS URL is easier to set up- you just clone directly from the repository using the HTTPS URL. However, 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>Suzantrt