Skip to main content
Ctrl+K
This is not yet fully debugged - report any issues!
Logo image
  • Introduction

Overview

  • Background

Preliminary Tasks

  • Pre-requisites
    • Pre-training tasks
    • Toolkit

Basics

  • Basic Concepts
  • Data citations and data availability statements
  • Generic data workflow
  • Assessing computational reproducibility
  • A guided walk through the Replication Report

AEA-specific training

  • AEA Jira workflow - A guide
    • In Progress
    • Prepare the working area
    • Code
    • Data
    • Write Preliminary Report
    • Verification
    • Code Review
    • Writing Report
  • AEA: Revision reports after author resubmission
  • AEA: Reviewing and (Pre-) Approving Reports
  • AEA: Monitoring Pending openICPSR Changes
  • AEA: Interfacing with the Journal Management System
    • Basic setup
    • Submitting to the JMS
    • Preparing openICPSR deposit
  • AEA: Instructions for Papers and Proceedings checks
  • AEA: Interfacing with openICPSR
    • AEA: Publishing a deposit
    • Adding the article DOI to the openICPSR deposit metadata

Sundry other guidance

  • External reproducibility checks

Appendix

  • Glossary
  • Setup Checklist
  • Privacy
  • Communication
  • Downloading Data
    • Using pre-publication openICPSR Projects
    • Alternate sources of data
    • Accessing privately provided data
    • Updating Replication Materials after Revisions
  • Access to Computers
    • Connecting to remote Windows servers
    • Connecting to remote Linux servers
    • Reproducibility Checks in Codeocean
    • Conducting reproducibility checks on WholeTale
    • Computing using Github Codespaces
    • Setting up your Bash environment
    • Additional setup instructions
  • Stata-related procedures
    • Using config.do in STATA
    • Running Code in Stata
    • Using scan_packages.do
  • R-related procedures
    • Using config.R in R
    • Running Code in R
  • MATLAB-related procedures
  • Docker-related procedures
  • Mathematica-related procedures
  • Ox-related procedures
  • Authentication-related issues
    • Bitbucket Authentication
    • openICPSR Authentication
  • Various templates for correspondence by AEA Data Editor team members
    • Preparing a Legacy Deposit for Updates by Authors
    • IPUMS Beta API request
    • Requesting Restricted-Access Data from Authors
    • Request for External Reproducibility Check (general)
  • Code of Conduct (Summary View)
  • References
  • Repository
  • Suggest edit
  • Open issue
  • .md

MATLAB-related procedures

Contents

  • Running MATLAB without the desktop GUI and with log file

MATLAB-related procedures#

In this section, we will show you a few things related specifically to running code reproducibly with MATLAB. For more general debugging tips for MATLAB and other computer languages, see our wiki.

Running MATLAB without the desktop GUI and with log file#

See these instructions for finding the Matlab binary on the system. However, this should work “out of the box” on CCSS-managed systems from the Bash prompt.

start matlab -nosplash  -minimize -r  "addpath(genpath('.'));main"  -logfile matlab.log

where main.m is the Matlab program you want to run (you omit the .m when calling it).

Note

This will still open a Matlab window in the background (check your taskbar).

Assuming MATLAB is in your path (check with matlab), the following will generate a logfile.

matlab -nodisplay -r "addpath(genpath('.')); main" -logfile matlab.log

where main.m is the Matlab program you want to run (you omit the .m when calling it).

If you do not have matlab in your path, check with system admins. For BioHPC, as long as you are on the ECCO nodes, you should have access. See BioHPC ECCO page for some details.

previous

Running Code in R

next

Docker-related procedures

Contents
  • Running MATLAB without the desktop GUI and with log file

By Lars Vilhuber, Michael Darisse, Sofia Encarnación, Leonel Borja Plaza, Hyuk Son, Linda Wang, David Wasser, Meredith Welch

© Copyright 2018-2023.