December 19, 2014

Mathematica

mathematica
Mathematica is a software package used for communicating scientific ideas in a variety of ways, whether this is visualization of a concept in an intro-level course, or creating a simulation of a new idea related to research. Mathematica is available for free to UAB faculty, staff and students, thanks to funding from the College of Arts and Sciences and the School of Engineering.

Campus machines

Follow the directions below to download software from Wolfram and request the appropriate activation key. If you do not have administrator access to your machine, please contact your IT support for assistance.
    1. Create an account (New users only):
      1. Go to user.wolfram.com and click "Create Account"
      2. Fill out form using a @uab.edu email, and click "Create Wolfram ID"
      3. Check your email and click the link to validate your Wolfram ID
    2. Request the download and key:
      1. Fill out this form to request an Activation Key
      2. Click the "Product Summary page" link to access your license
      3. Click "Get Downloads" and select "Download" next to your platform
      4. Run the installer on your machine, and enter Activation Key at prompt

Computer labs

  • Please contact your College IT representatives for specific installation information.
  • UAB College of Arts & Sciences, contact IT at: 205-975-4500, casit@uab.edu, www.uab.edu/casit

Faculty and staff personally-owned machines

Fill out this form to request a home-use license from Wolfram.

Student personally-owned machines

Follow the directions below to download from the Wolfram User Portal.
    1. Create an account (New users only):
      1. Go to user.wolfram.com and click "Create Account"
      2. Fill out form using a @uab.edu email, and click "Create Wolfram ID"
      3. Check your email and click the link to validate your Wolfram ID
    2. Request the download and key:
      1. Fill out this form to request an Activation Key
      2. Click the "Product Summary page" link to access your license
      3. Click "Get Downloads" and select "Download" next to your platform
      4. Run the installer on your machine, and enter Activation Key at prompt
Are you interested in putting Mathematica elsewhere? Please let IT or Troy Schaudt at Wolfram Research know.

The first two tutorials are excellent for new users, and can be assigned to students as homework to learn Mathematica outside of class time. Follow along in Mathematica as you watch this multi-part screencast that teaches you the basics—how to create your first notebook, calculations, visualizations, interactive examples, and more. Provides examples to help you get started with new functionality in Mathematica 10, including machine learning, computational geometry, geographic computation, and device connectivity. Access step-by-step instructions ranging from how to create animations to basic syntax information. Search Wolfram's large collection of materials for example calculations or tutorials in your field of interest.

Mathematica offers an interactive classroom experience that helps students explore and grasp concepts, plus gives faculty the tools they need to easily create supporting course materials, assignments, and presentations.

Resources for Educators

Learn how to make your classroom dynamic with interactive models, explore computation and visualization capabilities in Mathematica that make it useful for teaching practically any subject at any level, and get best-practice suggestions for course integration. Learn how to create a slideshow for class that shows a mixture of graphics, calculations, and nicely formatted text, with live calculations or animations. Download pre-built, open-code examples from a daily-growing collection of interactive visualizations, spanning a remarkable range of topics. Access on-demand and live courses on Mathematica, SystemModeler, and other Wolfram technologies.

Rather than requiring different toolkits for different jobs, Mathematica integrates the world's largest collection of algorithms, high-performance computing capabilities, and a powerful visualization engine in one coherent system, making it ideal for academic research in just about any discipline.

Resources for researchers

Explore Mathematica's high-level and multi-paradigm programming language, support for parallel computing and GPU architectures, built-in functionality for specialized application areas, and multiple publishing and deployment options for sharing your work. Learn how to create programs that take advantage of multicore machines or available clusters. Learn what areas of Mathematica are useful for specific fields.

In general, Mathematica is a high-level complete system, while MatLab is a low-level core with specialist toolboxes. Most engineering colleges at research universities maintain both products, including UAB. Because MatLab has separate toolboxes, each toolbox can only assume the functionality of the basic, core system; Mathematica is an all-in-one software which is interconnected nicely. For example, in Mathematica, purely numeric commands can perform symbolic pre-processing for richer and more accurate results, which is not possible in MatLab because of the design. This overall concept applies to the vast majority of Mathematica’s commands when compared to MatLab. Engineers and other groups on campus value the following functionality, which is unique to Mathematica:
  • Very sophisticated symbolic algorithms for closed-form solutions to problems
  • Much easier to create mouse-driven interfaces to visualize variations in equations or simulations,
  • The highest quality and most accurate graphics engine available for symbolic and numeric graphics,
  • Support for both machine precision and arbitrary precision,
  • Automatic switching between algorithms for best results,
  • Solves any order ODE (rather than only first-order in MatLab),
  • Integration for any n-dimensions (rather than only 3 in MatLab),
  • Wolfram Language included to program in procedural, functional, object-oriented, or rule-based style makes language easier to learn (rather than procedural only in MatLab),
  • Mathematica’s  high-level language requires less code to develop algorithms or ideas than MatLab
  • Text and equation typesetting document interface with slideshow mode (not available in MatLab),
  • Load-on-demand data sets to use in addition to importing a wide variety of types of data
  • IDE based on Eclipse, which researchers more commonly know and work with (rather than MatLab’s home-grown IDE).
  • Import of MatLab data sets supported for high-quality rendering of MatLab results in Mathematica

To learn more about Matlab and access it, click here.

For assistance with using the Mathematica software:
  • College of Arts and Sciences users can contact the CAS IT help desk by phone at 205-975-4500, by e-mail at casit@uab.edu or online at uab.edu/casit
  • School of Engineering users can contact Tommy Foley at 205-934-8477 or by e-mail at tfoley@uab.edu
  • All other schools/departments should contact Tony Schaudt, Wolfram Research Inc., at 800-965-3726, ext. 5588, or by e-mail at troys@wolfram.com

As part of the University's contract review process, UAB IT is responsible forcontract reviewing any University contract that includes an IT or IT related component prior to such contract being executed.  The information below, is provided to help facilitate the speedy processing of contracts once they are routed to IT for review. Questions on the process or requirements should be directed to UAB IT
 
 
  • Contracts* for software, subscriptions, or services (including software maintenance) that include  
    • Hosting/processing/transmission of UAB data external to UAB
    • PCI (Payment Card Industry) acceptance/processing of credit card transactions
    • Design, creation, maintenance, support, and/or hosting of any website/webpage
    • Personally identifiable information (PII) or personal health information (PHI) - does not include Health System Agreements which are managed by HSIS
    • Audit language
    • Custom software development
    • Agreements for products whare a similiar product or standard is already available/supported at UAB
    • Hardware purchase with embedded software with any of the above
  • *NOTE: For agreements that include the type of information listed above, documents/agreements must be executable, meaning they have signature lines for both UAB and the vendor.  Printing a 'click-agreement' or printing language from a website and submitting as an 'agreement' for review does not guarantee that the vendor will ever see changes/addendums that UAB may make or add to the agreement.

  • The primary goal is to minimize risk to you and UAB.  New agreements are normally subject to a more detailed review than renewal agreements. IT will review the checklist (see the FORMS section below) that you submit with your agreement for a quick determination of what review may be needed.
    • For new agreements:
      •  As necessary:
        • Confidentiality and Information Security provisions are reviewed to ensure appropriate confidentiality language is present, provisions to follow UAB on-site rules are present (if applicable), and the the vendor performs background checks on their employees. For agreemnts that include HIPAA or PHI a Business Associate Agreement (BAA) will also be required.  The BAA is handled by the UAB Legal and/or Privacy office and not by UAB IT.
        • For agreements where the vendor is hosting/processing/or transmitting UAB information additional language is needed: appropriate vendor controls are in place to protect UAB's data and that such controls are audited appropriately; that provisions are included for the return of UAB data at the end of the agreement; and that the vendor will notify UAB in the event of any security event involving UAB data. If the vendor is processing payment transactions language supporting the PCI (payment card industry) standards are required.
        • Indemnification and Liability provisions are reviewed to ensure that the vendor indemnifies UAB from any claims that their product breaches any copyright, trademark, or patents and that they will defend any such claim at their expense.  In addition, most vendors limit any claims for any breach to a small dollar amount...IT adds language removing that limitation when the breach is for confidentiality or information security claims.
        • Web/website development agreements are reviewed to ensure the vendor is aware of and will follow UAB branding requirements, security standards, and 508 compliance requirments. 
        • Audit language is reviewed and modified if needed (vendor's right to come on site at-will to audit);
        • Language is added that the "Written Agreement Governs". This is to prevent a conflict when a 'click' agreement may have to be accepted by a UAB employee to actually download, run, or maintain the product.
      • IT will aslo look to see if a similar service/product is already in place at UAB. If so, IT will work with the requesting department to understand and document the justification/business case for going outside the standard service/product. 
    • For renewals:
      • If the renewal inidicates it is governed by an existing agreement and that existing agreement was reviewed by IT initially, then the only IT review is to ensure no changes to any language are being requested by the vendor and that the renewal is consistent with the underlying agreement.  
      • If the renewal is for an agreement that was not reviewed by IT initially, then IT will need to review the underlying agreement and work with the department on what options may be available to make modifications based on the criteria above for new agreements.  Modifications to existing agreements may take more time and may ultimately result in modifications not being possible...potentially increasing the risk to UAB. 
    • Language to cover all of the items above are is provided in the applicable IT Addendum (see the FORMS LIBRARY section).  The addendum can be printed and submitted to the vendor for signagure prior to routing that agreement for signature at UAB. This will greatly speed up the review process in IT. 

  • Complete the IT Checklist and attach it to your contracting when routing (see the FORMS LIBRARY section);
  • If any of the items 'checked' on the list indicate an IT addendum is needed, go ahead and send the addendum to the vendor for signature prior to routing for UAB review/signature (see the FORMS LIBRARY section).  
  • UAB Contracts/Procurement also require a generic addendum be added in most cases. If you send the vendor an IT addendum, also include the UAB addendum. (See the FORMS LIBRARY section).
  • Provide any backup information such as master agreements, statements of work, etc.
  • Submit agreements that are 'execuatable'...they have signature lines for both parties and are not simply printed off of a web site.


Below are some items that should be considered when negotiating any agreement, not just IT related agreements. 
  • Don't base fees/costs on FTE numbers as these numbers can change each year;
  • No annual escalators; 
  • Include vendor service level expectations with remedies if they are not met/maintained;
  • Include 'piggyback clauses' where the agreement can be used by other institutions in the UA System;
  • Make sure any agreement with professional services clearly defines responsibilities and expectations of each party;
  • Limit travel costs for any on-site work to actual costs and to no more than 15% of the actual professional services you pay;
  • In most cases agreements should renew annually upon mutual agreement and with issuance of a UAB PO.  Agreements should not renew automatically or where you are required to notify the vendor xx days prior to the renewal date. 
  • Don't agree to pay for services/products up front.  Base payment on milestones or completion and UAB written acceptance;
  • For contracts that IT intiates a standard agreement review template is used to evaluate risk.  You can download a copy of that template here for your own use. 

  • Ggeneral UAB Addendum (found on the Financial Affairs contract website) - covers information related to State, University, and Legal issues/clarifications.  Any changes to the UAB addendum must be approved by University Contracts. 
  • IT Routing Checklist - should be completed and attached to the routing packet. This checklist should help you determine which (if any) IT Addendum may be required.
  • The UAB Information Technology Addendums cover additional confidentiality, information security, and liability language to mitigate any issues related to the items/concerns above. Portions of the IT Addendum may be applicable to only certain agreements and that applicability is detailed in the various sections of the addendum.  Any changes to the IT addendum must be reviewed and approved by UAB IT. 
  • For agreements that include HIPAA (health related information) a Business Associate Agreement (BAA) may also be required. For information related to the BAA see the UAB HIPAA website