Instructors:
Erin Becker, Miklós Koren, Olivér Kiss, Arieda Muço, András Vereckei
Helpers:
Sergio Correia, Rachel Forshaw, Garro-Marín, M Nithin, Xinyu Ma, Charlotte Grace, Pavel Soriano, Benson Muite, Nagy Róbert
General Information
Data Carpentry develops and teaches workshops on the fundamental data skills needed to conduct
research. Its target audience is researchers who have little to no prior computational experience,
and its lessons are domain specific, building on learners' existing knowledge to enable them to quickly
apply skills learned to their own research.
Participants will be encouraged to help one another
and to apply what they have learned to their own research problems.
Who:
The course is aimed at graduate students and other researchers.
You don't need to have any previous knowledge of the tools
that will be presented at the workshop.
Requirements: Participants must bring a laptop with a
Mac, Linux, or Windows operating system (not a tablet, Chromebook, etc.) that they have administrative privileges on. They should have a few specific software packages installed (listed below).
Code of Conduct: Everyone who participates in Carpentries activities is required to conform to the Code of Conduct. This document also outlines how to report an incident if needed.
Contact:
Please email
korenm@ceu.edu
for more information.
To participate in a
Data Carpentry
workshop,
you will need access to the software described below.
In addition, you will need an up-to-date web browser.
Click on "Next" four times (two times if you've previously
installed Git). You don't need to change anything
in the Information, location, components, and start menu screens.
Select "Use the nano editor by default" and click on "Next".
Keep "Git from the command line and also from 3rd-party software" selected and click on "Next".
If you forgot to do this programs that you need for the workshop will not work properly.
If this happens rerun the installer and select the appropriate option.
Click on "Next".
Select "Use the native Windows Secure Channel library", and click "Next".
Keep "Checkout Windows-style, commit Unix-style line endings" selected and click on "Next".
Select "Use Windows' default console window" and click on "Next".
Leave all three items selected, and click on "Next".
Do not select the experimental option. Click "Install".
Click on "Finish".
If your "HOME" environment variable is not set (or you don't know what this is):
Open command prompt (Open Start Menu then type cmd and press [Enter])
Type the following line into the command prompt window exactly as shown:
setx HOME "%USERPROFILE%"
Press [Enter], you should see SUCCESS: Specified value was saved.
Quit command prompt by typing exit then pressing [Enter]
This will provide you with both Git and Bash in the Git Bash program.
The default shell in all versions of macOS is Bash, so no
need to install anything. You access Bash from the Terminal
(found in
/Applications/Utilities).
See the Git installation video tutorial
for an example on how to open the Terminal.
You may want to keep
Terminal in your dock for this workshop.
The default shell is usually Bash, but if your
machine is set up differently you can run it by opening a
terminal and typing bash. There is no need to
install anything.
Git
Git is a version control system that lets you track who made changes
to what when and has options for easily updating a shared or public
version of your code
on github.com. You will need a
supported
web browser.
You will need an account at github.com
for parts of the Git lesson. Basic GitHub accounts are free. We encourage
you to create a GitHub account if you don't have one already.
Please consider what personal information you'd like to reveal. For
example, you may want to review these
instructions
for keeping your email address private provided at GitHub.
For OS X 10.9 and higher, install Git for Mac
by downloading and running the most recent "mavericks" installer from
this list.
Because this installer is not signed by the developer, you may have to
right click (control click) on the .pkg file, click Open, and click
Open on the pop up window.
After installing Git, there will not be anything in your /Applications folder,
as Git is a command line program.
For older versions of OS X (10.5-10.8) use the
most recent available installer labelled "snow-leopard"
available here.
If Git is not already available on your machine you can try to
install it via your distro's package manager. For Debian/Ubuntu run
sudo apt-get install git and for Fedora run
sudo dnf install git.
Text Editor
When you're writing code, it's nice to have a text editor that is
optimized for writing code, with features like automatic
color-coding of key words. The default text editor on macOS and
Linux is usually set to Vim, which is not famous for being
intuitive. If you accidentally find yourself stuck in it, hit
the Esc key, followed by :+Q+!
(colon, lower-case 'q', exclamation mark), then hitting Return to
return to the shell.
nano is a basic editor and the default that instructors use in the workshop.
It is installed along with Git.
Others editors that you can use are
Notepad++ or
Sublime Text.
Be aware that you must
add its installation directory to your system path.
Please ask your instructor to help you do this.
nano is a basic editor and the default that instructors use in the workshop.
See the Git installation video tutorial
for an example on how to open nano.
It should be pre-installed.
Download and launch the installer: SetupStata16.exe
Once the installation is done, start Stata from the Start Menu. The first time you do this, you will have to activate your licence.
Enter the serial number provided and press enter
Enter the code and press enter
Enter the authorization and press enter
It should return “Good. The serial number, code, and authorization make sense. Shall we continue?” Type Y and press enter.
When it asks for the first line, it should say “EEA”
When it asks for the second line, it should say “2020”
It will ask for confirmation. Type “Y” and press enter.
Go to the link given by your instructor
Download and launch the installer: Stata16.dmg
Once the installation is done, start Stata from the Start Menu. The first time you do this, you will have to activate your licence.
Enter the serial number provided and press enter
Enter the code and press enter
Enter the authorization and press enter
It should return “Good. The serial number, code, and authorization make sense. Shall we continue?” Type Y and press enter.
When it asks for the first line, it should say “EEA”
When it asks for the second line, it should say “2020”
It will ask for confirmation. Type “Y” and press enter.
Go to the link given by your instructor
Download Stata16Linux64.tar.gz.
Open a terminal and navigate to the directory where your downloaded file is located (e.g. cd ~/Downloads/)
Get superuser rights (sudo su)
Create a new directory (e.g. mkdir stata_install)
Move the downloaded file to this new directory (mv Stata16Linux64.tar.gz. stata_install/)
Enter the directory (cd stata_install)
Extract the installation files using tar xzf Stata16Linux64.tar.gz
Create a directory for your stata installation (mkdir /usr/local/stata16)
Navigate to the stata directory (cd /usr/local/stata16)
Start the installation by executing the extracted install file (e.g. /home/username/Downloads/stata_install/install)
Whenever the installer asks if you want to proceed type “y” and press enter
Once the installation is done, type ./stinit to activate your licence
Whenever it asks you if you want to continue, type “Y” and press enter
Enter the serial number provided and press enter
Enter the code and press enter
Enter the authorization and press enter
It should return “Good. The serial number, code, and authorization make sense. Shall we continue?” Type Y and press enter.
When it asks for the first line, it should say “EEA”
When it asks for the second line, it should say “2020”
It will ask for confirmation. Type “Y” and press enter.
Try to start stata by ./xstata. If it gives you the following error message (./stata: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory), continue with the steps below:
Issue the following commands one by one in your terminal window:
In order to provide help in case you are stuck at any point, we will need you
to take screenshots of your code and send it to a helper via Slack. You can
see below how you can do it depending on your operating system.
Press the print screen (FN or ALT + PrtScn) button on your keyboard. You can insert into any Slack channel with CTRL + V.
To take a screenshot of your entire screen, press, at the same time, the keys Shift, Command and 3. Your screenshot will be saved on the Desktop. Navigate to your desktop, copy the screenshot with Command + C, and paste into Slack with Command + V.
If you want to capture only a part of your screen, press Shift, Command and 4. You will get a crosshair cursos with which you can select the area of the screen to save. It will be saved on the Desktop. Navigate to your desktop, copy the screenshot with Command + C, and paste into Slack with Command + V.
Press the print screen (PrtSc) button on your keyboard. This will (on most Linux systems)
save a screenshot to the Pictures folder in your home directory. You can send this file in the Slack app
or in its online version by clicking on the paperclip icon in the bottom right corner of the messaging area and selecting it from your computer.