swcarpentry / deprecated-boot-camps Goto Github PK

The following exercise (courtesy of Milad) in shell/Readme.md :

**Short Exercise**

Figure out how to get `wc` to print the length of the longest line in
`all_data`.

* * * *

Requires a non-POSIX extension to wc (wc -L, --max-line-length).

It does not work on OSX, whose wc does not have those options.

Out-of-date wiki instructions here:

https://github.com/swcarpentry/boot-camps/wiki/Boot-Camp-Pages#-4-test-your-changes

Here's the old command recommended from that page:

jekyll --pygments --no-lsi --safe

Here appears to be the new syntax (with a correctly configured yaml file)

jekyll build

I have no idea why they decided to get rid of command line options.

In trying to make changes to the necessary pages to support my upcoming bootcamp, we striving for a branch/edit/test/merge workflow. In modifying the HTML or jekyll based code, however, the test stage is difficult and/or undocumented. Is there an accepted/preferred way to do this prior to submitting a pull request?

This will prevent students from accidentally ending up in vi and not being able to get out.

The flip side is that if we happen to have a Windows user who is intentionally using something else we could end up messing with their configuration.

It's probably not important to fix this, but CSS is broken for workshop pages in this repo, e.g. http://swcarpentry.github.io/boot-camps/2013-05-13-ucdavis/

http://software-carpentry.org/css/bootstrap/bootstrap-responsive.css Failed to load resource: the server responded with a status of 404 (Not Found)
http://software-carpentry.org/css/bootstrap/bootstrap.css Failed to load resource: the server responded with a status of 404 (Not Found)
http://software-carpentry.org/js/bootstrap/bootstrap.min.js Failed to load resource: the server responded with a status of 404 (Not Found)
http://software-carpentry.org/img/favicon.ico Failed to load resource: the server responded with a status of 404 (Not Found)
http://software-carpentry.org/css/bootstrap/bootstrap.css Failed to load resource: the server responded with a status of 404 (Not Found)
http://software-carpentry.org/css/bootstrap/bootstrap-responsive.css Failed to load resource: the server responded with a status of 404 (Not Found)

See #18 (comment)

I had one Windows user at the workshop I'm at now who had some false negatives from swc-installation-test-2. I ran it myself and was able to reproduce the problems:

I reported the IPython script as found, but the ipython package as not found, even though IPython was working fine, and the install test script was being run with the same python as IPython.

The second was that it reported that it couldn't find a default web browser even though it seemed to successfully open/close tabs in the user's default Chrome.

Haven't had a chance to debug any further. But they were using a recent Python 3 install of Anaconda.

If this setting http://danlimerick.wordpress.com/2011/07/23/git-for-windows-tip-how-to-copy-and-paste-into-bash/ could be adjusted automatically in the Windows installer that would be handy, but if not adding it to the instructions might be useful.

I don't understand what the disclaimers about Windows are referring to (i.e., ~ doesn't work, use \ instead of /, etc). Is this for powershell or cygwin or the windows command prompt?

Recent Boot Camps that had substantial R coverage (may not be exhaustive):

• 2012 OCT 18 - 19 University of British Columbia
• 2013 MAY 16 - 17 NESCent
• 2013 MAY 20 - 21 Duke

Jenny Bryan put her materials that evolved over the course of these boot camps (and other non-SWC workshops) into https://github.com/jennybc/swcR_duke. Development is continuing there. In particular a known gap/mistake was addressed. Other clean-up and polishing ongoing but near completion.

Bernhard Konrad brought a snapshot (not the most current) of that repo PLUS other materials for more advanced R workshops into https://github.com/swcarpentry/boot-camps with this commit 99c4ccd.

With respect to the content that came from her, Jenny plans to redo the assimilation of the R teaching materials with these goals:

• include recent clean-up
• bring in a way that important aspects of history are retained

Since this workshop is now in the past, I think it's time to convert it from a branch to a tag (as recommended in the workflow docs). Thoughts (@jiffyclub and/or @douglatornell)?

Ethan and I are considering including Numpy in our workshop in a week. Does anyone have any curriculum they could share? I've used Numpy often, but I'm hardly an expert in it and if I were to teach it I think it'd be good to have a sense of what other folks have done.