{"id":23423,"date":"2020-11-16T13:53:53","date_gmt":"2020-11-16T18:53:53","guid":{"rendered":"https:\/\/www.rc.fas.harvard.edu\/?page_id=23423"},"modified":"2023-07-31T15:44:22","modified_gmt":"2023-07-31T19:44:22","slug":"software","status":"publish","type":"page","link":"https:\/\/www.rc.fas.harvard.edu\/services\/software\/","title":{"rendered":"Software"},"content":{"rendered":"\n<h3><b>Description<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Research software is the collection of tools, codes, libraries that allows a researcher to generate new data or analyze and make meaning of existing data.\u00a0 Some software is used across many disciplines, like MatLab, R, python, whereas most are very domain specific.\u00a0 The majority of software is provided by the researchers, however FAS has site or volume licenses for several packages for cluster and\/or desktop use, which are provided at no cost to faculty and students.\u00a0 Licenses are usually available upon request.\u00a0 For software that is needed on the cluster, FASRC can install codes in a common location.\u00a0 Desktops installation of software is self-service or can be done by your local HUIT Desktop support group.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">RC will also help you acquire any other software you may require for your research, or help you determine which packages are most appropriate for the types of analyses you want to do. These packages are purchased individually for each user and are charged to research accounts.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h3><b>Definitions<\/b><\/h3>\n<p><b>Software Types:<\/b><\/p>\n<p><i><span style=\"font-weight: 400;\">Open Source<\/span><\/i><span style=\"font-weight: 400;\"> - software in which source code is released under a license in which the copyright holder grants users the rights to study, change, and distribute the software to anyone and for any purpose. Typically, open-source software is developed in a collaborative public manner.<\/span><\/p>\n<p><i><span style=\"font-weight: 400;\">Commercial <\/span><\/i><span style=\"font-weight: 400;\">- any software or program that is designed and developed for licensing or sale to end users or that serves a commercial purpose. Commercial software was once considered to be proprietary software, but now a number of free and open-source software applications are licensed or sold to end users. Off-the-shelf software programs, to be used with little or no modification, are examples of commercial software.<\/span><\/p>\n<p><i><span style=\"font-weight: 400;\">Custom <\/span><\/i><span style=\"font-weight: 400;\">- software solutions that are specially developed for a specific user or organization and may include solutions that have been designed to run on specific hardware (embedded software). Such software is used to address user needs that cannot be met by more traditional and widespread off-the-shelf software.\u00a0 Custom software can also be modifications or extensions, for specific purposes, of Open Source and\/or Commercial software.<\/span><\/p>\n<p><b>Licensing Types:<\/b><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><i><span style=\"font-weight: 400;\">Perpetual license<\/span><\/i><b> - <\/b><span style=\"font-weight: 400;\">typically authorizes an individual to use an application indefinitely. Generally, outside of termination, a perpetual software license allows the holder to use a specific version of a given software program continually with payment of a single fee.\u00a0 Along with a perpetual software license, the vendor typically provides a technical support period of one to three years. During this initial period, the vendor also provides software updates often. However, updates may or may not be provided for free in perpetuity.<\/span><\/li>\n<li style=\"font-weight: 400;\"><i>Subscription License<\/i> - typically authorizes an individual to use an application for a defined period. This might be 30 days (a monthly subscription) or 365 days (an annual subscription.) Subscriptions typically have no defined end or termination date and they automatically renew after the initial term.<\/li>\n<li style=\"font-weight: 400;\"><i><span style=\"font-weight: 400;\">Individually Licensed <\/span><\/i><span style=\"font-weight: 400;\">\u2013 Individual Licenses can be based on per machine or per user and typically reflect the use of an application by an individual<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">.<\/span><i><span style=\"font-weight: 400;\">Floating License<\/span><\/i><span style=\"font-weight: 400;\"> - approach in which a limited number of licenses for a software application are shared among a larger number of users over time. When an authorized user wishes to run the application they request a license from a central license server.<\/span><\/li>\n<\/ul>\n<p><b>Buying and Installing specific software.<\/b><span style=\"font-weight: 400;\">\u00a0 Software for use on the (Linux) FASRC cluster can be purchased by an individual, lab, or through Harvard licensing.\u00a0 Installation will typically occur by the research computing group either generally (to be available to all users) or within a specific user's space and be available to a limited number of individuals.\u00a0 Responsibility of troubleshooting and the stability of an application will vary depending on the software title.\u00a0 Software titles specifically supported by the research computing group are the ones we provide annual training for.\u00a0 Ad-hoc installation requests will be supported as defined at the time of request.<\/span><\/p>\n<p><b>Service Expectations and Limits:<\/b><span style=\"font-weight: 400;\">\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Software installations are always done as a best effort, and fall behind other services like running the cluster, data storage, and VM infrastructure. \u00a0 Typical scientific software is \u201chome-grown\u201d at Universities over time, and quite sophisticated with little documentation.\u00a0 These codes are largely written in C\/C++ or Fortran and require compilation on our cluster to work effectively.\u00a0 This process can take a week or two depending on how many library dependencies must be rectified first.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Licensed software have a limited number of seats (or tokens), in which each job must consume.\u00a0 When a token is unavailable, the job will continue to pend and not start.\u00a0 Also, the FASRC license manager is a single server (not a high-availability setup), that provides license tokens for cluster jobs.\u00a0 If this server is unresponsive then, license tokens will not be available until the server is back in good health, please send in a support request.\u00a0 Also, licenses generally have an annual renewal date, which is up to the purchaser to renew and not FASRC.\u00a0 For example, SEAS maintains the license for ABAQUS, FASRC does not have the means to renew this license.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">At FASRC, availability, uptime, and backup schedule is provided as best effort with staff that do not have rotating 24\/7\/365 shifts.\u00a0\u00a0\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u00a0<\/span><\/p>\n<h3><b>Available to:<\/b><span style=\"font-weight: 400;\">\u00a0<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">All PIs with an active FASRC account from any Harvard School.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">All\u00a0access\u00a0requests should\u00a0be sent\u00a0via email to\u00a0<\/span><a href=\"mailto:rchelp@rc.fas.harvard.edu\"><span style=\"font-weight: 400;\">rchelp@rc.fas.harvard.edu<\/span><\/a><span style=\"font-weight: 400;\">\u00a0<\/span><span style=\"font-weight: 400;\">\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u00a0<\/span><\/p>\n<h3><b>Service Manager: <\/b><span style=\"font-weight: 400;\">\u00a0<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Service Manager:\u00a0<a href=\"https:\/\/www.rc.fas.harvard.edu\/about\/people\/raminder-singh\/\">Raminder\u00a0Singh<\/a>, Associate Director of Data Science and Research Facilitation\u00a0<\/span><\/p>\n<p>&nbsp;<\/p>\n<h3><b>Offerings<\/b><\/h3>\n<ul>\n<li style=\"font-weight: 400;\"><b>Software Installation.<\/b><span style=\"font-weight: 400;\"> \u00a0 Existing software on the cluster can be found on our portal <\/span><a href=\"https:\/\/portal.rc.fas.harvard.edu\/p3\/build-reports\/\"><span style=\"font-weight: 400;\">here<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\"><b>Software Downloads.<\/b><span style=\"font-weight: 400;\">\u00a0 Distribution of desktop software for research can be found <\/span><a href=\"https:\/\/downloads.rc.fas.harvard.edu\/\"><span style=\"font-weight: 400;\">here<\/span><\/a><span style=\"font-weight: 400;\">. <\/span><i><span style=\"font-weight: 400;\">Requires FASRC VPN access.<\/span><\/i><\/li>\n<li style=\"font-weight: 400;\"><b>Licensed Software.<\/b><span style=\"font-weight: 400;\">\u00a0 FASRC runs FlexLM software manager.<\/span><\/li>\n<li style=\"font-weight: 400;\"><b>Software purchasing.<\/b><span style=\"font-weight: 400;\"> \u00a0 FASRC works with vendors and Harvard Procurement to navigate Terms &amp; Conditions of software contracts necessary for HPC Cluster computing.\u00a0 FASRC does not need to be involved in SaaS contracts as those are hosted in vendor\u2019s cloud platform.\u00a0 Generally individual groups will purchase software for their Lab.\u00a0 Whole departments might pool resources to purchase software for their domain.\u00a0 <\/span><i><span style=\"font-weight: 400;\">Example: Chemistry and Chemical Biology purchase of Gaussian.<\/span><\/i><span style=\"font-weight: 400;\"> General purpose software might be purchased by FAS with an institutional license.\u00a0 <\/span><i><span style=\"font-weight: 400;\">Example: Matlab, Mathematica, Stata, \u2026<\/span><\/i><\/li>\n<li style=\"font-weight: 400;\"><b>Software Training<\/b><span style=\"font-weight: 400;\">:\u00a0 See <\/span><a href=\"https:\/\/www.rc.fas.harvard.edu\/training\/\"><span style=\"font-weight: 400;\">Training<\/span><\/a><span style=\"font-weight: 400;\"> for current offerings.\u00a0 Typical offerings include.<\/span>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">MatLab<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">MPI<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">R<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Python<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p class=\"lead\">Description Research software is the collection of tools, codes, libraries that allows a researcher to generate new data or analyze and make meaning of existing data.\u00a0 Some software is used across many disciplines, like MatLab, R, python, whereas most are very domain specific.\u00a0 The majority of software is provided by the researchers, however FAS has site or volume licenses for&hellip;<\/p>\n<p class=\"more-link-p\"><a class=\"btn btn-primary\" href=\"https:\/\/www.rc.fas.harvard.edu\/services\/software\/\">Read more<\/a><\/p>\n","protected":false},"author":111,"featured_media":0,"parent":8926,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"categories":[156],"tags":[],"class_list":["post-23423","page","type-page","status-publish","hentry","category-services"],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/P42YvN-65N","_links":{"self":[{"href":"https:\/\/www.rc.fas.harvard.edu\/wp-json\/wp\/v2\/pages\/23423","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rc.fas.harvard.edu\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.rc.fas.harvard.edu\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.rc.fas.harvard.edu\/wp-json\/wp\/v2\/users\/111"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rc.fas.harvard.edu\/wp-json\/wp\/v2\/comments?post=23423"}],"version-history":[{"count":6,"href":"https:\/\/www.rc.fas.harvard.edu\/wp-json\/wp\/v2\/pages\/23423\/revisions"}],"predecessor-version":[{"id":24884,"href":"https:\/\/www.rc.fas.harvard.edu\/wp-json\/wp\/v2\/pages\/23423\/revisions\/24884"}],"up":[{"embeddable":true,"href":"https:\/\/www.rc.fas.harvard.edu\/wp-json\/wp\/v2\/pages\/8926"}],"wp:attachment":[{"href":"https:\/\/www.rc.fas.harvard.edu\/wp-json\/wp\/v2\/media?parent=23423"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rc.fas.harvard.edu\/wp-json\/wp\/v2\/categories?post=23423"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rc.fas.harvard.edu\/wp-json\/wp\/v2\/tags?post=23423"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}