Your Sid credentials are your HarvardKey e-mail address and password.
No. Please use Google Drive to transfer data into and out of your Sid session.
Sid will support classical batch-style processing in a future release. Currently, batch-style jobs can run indefinitely in the background without user input within an interactive job.
Scheduled jobs (CRON type jobs) are a special case of the above mentioned batch jobs. These jobs are currently not supported.
Alternatively, you could run cron jobs in Sid Desktop by first installing the cron daemon (sudo dnf -y install cronie) and then creating a crontab (crontab -e), but this will cease to operate when her Sid job is terminated.
Use the httr GET function, e.g.,
library(httr)
# Example World Health data
url <- 'https://pastebin.com/raw/V7DEMiDu';
r <- GET(url)
fil <- tempfile("data")
write(content(r, "text"), fil)
WHS_data <- read.table(fil, sep="\t", header=TRUE, quote="")
summary(WHS_data[,c(1,4,10)])
pairs(WHS_data[,c(1,4,10)])
Use df -h to display disk size. E.g., in the below example, the job has 92G of disk storage under Avail.
$ df -h $HOME
Filesystem Size Used Avail Use% Mounted on
overlay 105G 14G 92G 14% /
Select Site Settingsin your Sid Desktop browser tab:
Select Clipboard -> Allow
Different operating systems and keyboard configurations map copy and paste differently; but it is generally one of Ctrl-C, Option-C, Alt-C, or ⌘-C for copy (and Ctrl-V, Option-V, Alt-V, or ⌘-V for paste).
In the job launcher, select Google Drive under Connected Storage:
Screencast for a demonstration of attaching a Google Drive to a Sid job:
No. A CPU is a CPU and RAM is RAM. Sid does not allocate cheaper, worse-performing hardware based on request size. Additionally, running multiple jobs will not degrade performance. Sid users can run up to eleven jobs without any performance degradation (as each is allocated dedicated resources from AWS).
When Sid has completed provisioning your desktop environment, a link to it will appear below Access Url in the dashboard:
The Sid Desktop runs LxQT, The Lightweight Qt Desktop Environment. Like all desktop environments, the left-hand corner opens a menu of useful GUI X Windows applications including web browsers, terminal emulators, text editors, LaTeX editors, and more.
QTerminal is available under System Tools. It is a multi-tab terminal emulator, which can run command-line applications.
GNU Octave is a free alternative to MATLAB available in the Education menu.
LyX and TeXstudio are LaTeX authoring tools for academic papers.
Emacs is a popular text editor available in the Programming menu.
The Firefox browser is available in the Internet menu.
The Sid Desktop has hundreds of commands pre-installed such as the following:
R
docbook
emacs
gcc
git
gnuplot
imageMagick
java
lua
make
octave
perl
python2
python3
rpm
rxvt
screen
tcl
texlive
texstudio
tix
tk
tmux
vim
zip
The YUM package manager can list, query, and add additional command-line tools to the Sid Desktop.
For all applications, Sid mounts your Google Drive to the same location: /mnt/google-drive. Each Sid application has similar commands for navigating to this directory location.
{% hint style="warning" %} Google Drive in Sid does not currently support symbolic links. {% endhint %}
From QTerminal,cd to your Google Drive's mount point:
Start your application (e.g., R) and access your Google Drive data files:
setwd to the attached Google Drive:
Your Google Drive files are now visible from the File->Open menu:
From within a Python Notebook,cd (or %bookmark) to the mount point for your Google Drive:
You are now in your Google Drive's working directory for reading data, e.g.,
From within a Julia Notebook,cdto the mount point for your Google Drive:
From within an R Notebook, setwd to the mount point for your Google Drive:
Are you sure you don't want to use a Git hosting provider such as GitHub, BitBucket, or BeanStalk? If not, open the directory of your Google Drive File Stream:
From inside your Google Drive directory on your local computer, you can use standard git commands, and all of the git metadata in your repository will be synced in Google Drive, e.g.,
/Volumes/GoogleDrive/My Drive/my-repo $ git init
Initialized empty Git repository in /Volumes/GoogleDrive/My Drive/my-repo/.git/
/Volumes/GoogleDrive/My Drive/my-repo $ echo 1 2 3 > foo.txt
/Volumes/GoogleDrive/My Drive/my-repo $ git add foo.txt
/Volumes/GoogleDrive/My Drive/my-repo $ git commit -m "Add foo.txt"
[master c947c83] Add foo.txt
1 file changed, 1 insertion(+)
create mode 100644 foo.txt
/Volumes/GoogleDrive/My Drive/my-repo $
{% hint style="warning" %}
Warning: you can not run git commands of any kind on your Git/Drive repository from within Sid due to limitations of rclone.
{% endhint %}
{% hint style="warning" %} Google Drive File Stream will only connect to Google Drive accounts that are part of an enterprise G Suite (for example g.harvard.edu). If you need assistance with accessing Google Drive using some other method you can contact us for support. {% endhint %}
Screen cast showing Git + Google Drive workflow:
Google Drive in Sid is an object storage system synced by rclone to resemble a file system, but it is lacking some features of a standard POSIX file system (such as symbolic links and file permissions).
Because the features of Google Drive in Sid are not at parity with some POSIX file systems, you may encounter the following problems:
File modifications between Git and Google Drive may disagree, so for example:
$ git status
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean
The same directory used in Google Drive shows modifications to a file in Git:
$ git status
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: foo
The above discrepancy is due to the different handling of file permissions:
Non-Google drive:
-rwxr-xr-x 1 jane staff 6991 Nov 25 17:04 foo
Google drive (note the differing file permissions):
-rw------- 1 jane staff 6991 Nov 25 17:05 foo
Running a script containing a shebang line from your Google Drive directory can cause bad interpreter: Permission denied errors. For example, the below code runs fine in $HOME:
$ cat hello.sh
#!/usr/bin/bash
echo "hello"
$ ./hello.sh
hello
The same code fails in Google Drive with bad interpreter: Permission denied:
$ cat /mnt/google-drive/hello.sh
#!/usr/bin/bash
echo "hello"
$ /mnt/google-drive/hello.sh
sh: /mnt/google-drive/hello.sh: /usr/bin/bash: bad interpreter: Permission denied
One workaround is to invoke the shebang from the shell, instead of the first line (#! ) of the script:
$ bash /mnt/google-drive/hello.sh
hello
Install the requisite system library packages, install rJava, and run javareconf:
system('sudo apt-get update')
system('sudo apt-get -y install default-jre default-jdk libpcre3-dev liblzma-dev libbz2-dev zlib1g-dev libicu-dev')
install.packages('rJava')
system('sudo R CMD javareconf')Before you can use rJava, you need to restart R.
To restart R in Rstudio, click the Session menu and select Restart R.
Now you can use rJava:
library('rJava')