Difference between revisions of "CommunityData:Resources"

From CommunityData
Jump to: navigation, search
m (put some things in technical doc/setting up in alphabetical order that were not in alphabetical order)
(adding link to introduction to cdsc resources and fixed some typos, feel free to move introduction link)
 
Line 1: Line 1:
 
This page collects resources for Community Data Science Collective members.
 
This page collects resources for Community Data Science Collective members.
 +
 +
If you're new to the collective, check out the [https://wiki.communitydata.science/CommunityData:Introduction_to_CDSC_Resources Introduction to CDSC Resources].
  
 
== Technical documentation and getting setup ==
 
== Technical documentation and getting setup ==
  
 
* [[CommunityData:Backups (nada)]] — Details on what is, and what isn't, backed up from nada.
 
* [[CommunityData:Backups (nada)]] — Details on what is, and what isn't, backed up from nada.
* [[CommunityData:Beamer]] — Installing/using [[Mako]]'s beamer templates
+
* [[CommunityData:Beamer]] — Installing/using [[Mako]]'s Beamer templates
 
* [[CommunityData:Build papers]] — Both the TeX and Beamer templates above come along with a Makefile that makes some assumptions about your workflow. Learn about that here.
 
* [[CommunityData:Build papers]] — Both the TeX and Beamer templates above come along with a Makefile that makes some assumptions about your workflow. Learn about that here.
 
* [[CommunityData:Code]] — List of software projects maintained by the collective.
 
* [[CommunityData:Code]] — List of software projects maintained by the collective.
Line 11: Line 13:
 
* [[CommunityData:Exporting from Python to R]]
 
* [[CommunityData:Exporting from Python to R]]
 
* [[CommunityData:Git]] — Getting set up on the git server
 
* [[CommunityData:Git]] — Getting set up on the git server
* [[CommunityData:Hyak]] — Using the Hyak supercomputer system at UW for reserach.
+
* [[CommunityData:Hyak]] — Using the Hyak supercomputer system at UW for research.
 
* [[CommunityData:Hyak setup]] — Getting an account and getting setup on Hyak.
 
* [[CommunityData:Hyak setup]] — Getting an account and getting setup on Hyak.
 
* [[CommunityData:Hyak Spark]] — Documents how to use Spark on Hyak
 
* [[CommunityData:Hyak Spark]] — Documents how to use Spark on Hyak
Line 42: Line 44:
  
 
== Non-technical resources ==
 
== Non-technical resources ==
* [[Schedule]] — Deadlines, events, and simialr
+
* [[Schedule]] — Deadlines, events, and similar
 
* [[CommunityData:Logos]] — Like our visual branding, not like λόγος. Although we should always make sure we're good in that department too.
 
* [[CommunityData:Logos]] — Like our visual branding, not like λόγος. Although we should always make sure we're good in that department too.
 
* [[CommunityData:Advice on writing a background section to an academic paper]] — Once upon a time, Mako and Aaron submitted a paper with a mediocre introduction to a journal. Mac Parks, the editor of that journal at the time, set us straight with some very clear pointers. Save yourself the trouble and learn to follow these today!
 
* [[CommunityData:Advice on writing a background section to an academic paper]] — Once upon a time, Mako and Aaron submitted a paper with a mediocre introduction to a journal. Mac Parks, the editor of that journal at the time, set us straight with some very clear pointers. Save yourself the trouble and learn to follow these today!

Latest revision as of 21:39, 7 August 2019

This page collects resources for Community Data Science Collective members.

If you're new to the collective, check out the Introduction to CDSC Resources.

Technical documentation and getting setup[edit]

Project Pages[edit]

Ongoing and Future Meetings and Meetups[edit]

Meetings and Meetups of Past[edit]

Non-technical resources[edit]

University of Washington Resources[edit]

Northwestern Resources[edit]

Chat on IRC[edit]

A number of us are idling in #communitydata on OFTC (irc.oftc.net). IRC is basically a chat system that is similar to Slack in many ways. In fact, it was the inspiration for Slack!

To use IRC, you'll need a client. A really good one for folks new to IRC is IRCCloud. With IRCCloud there is a web interface as well as good Apps for iOS and Android.

One limitation of IRCCloud is that, after a 1-week trial period, the system will disconnect folks every two hours. There are a couple options for this. The easiest one is subscribing to IRC cloud which costs $5/month or $50 a year. You just pay for a year and send the receipt to User:Ashaw who will pay the bill! If you are totally new to IRC and just want something easy and straight forward, this is our recommendation.

The other options are more indirect, technical, and/or involve a bit more work or figuring stuff out:

Bouncer
On option is an IRC "bouncer" such as ZNC.
IRC Bridge/Matrix
Another option that a few people are doing is connecting connecting through a service with an IRC bridge. One popular one is the Matrix protocol. While there are numerous clients, User:Salt recommends Riot which is freely supported on every platform. Once you get Matrix Join the room #_oftc_#communitydata:matrix.org to bridge into IRC from Matrix. Get in contact with User:Salt if you want to go this way.

Registering your "nick" (i.e., IRC username)[edit]

Due to spam, we have on a couple of occasions in the past had to block "non-registered" users from posting to #communitydata. This helps a lot with the spam but has a big disadvantage in that if you speak on the channel but are not registered, nobody else will be able to hear you!

It's a good idea to register your nickname or "nick" in any case because it means that can essentially reserve your nickname so that nobody else can have it.

If you've already done this long ago, you can stop reading, there's nothing new to do. If you haven't gotten fully registered and verified, here are the four "easy" steps, heavily mediated by the NickServ bot:

  1. From IRC (irc.oftc.net), /msg NickServ register <<your password>> <<your email>>
  2. Verification is via the website, see: [1]
  3. Ask NickServ 'checkverify' and she'll tell you if you're verified.
  4. Please say something on the channel to test. If you do not get a response, your messages can still be seen by community members. /msg mako or ashaw for help.

Diversions[edit]

The light in the lab at UW is funny. We have three fluorescent lights. On flipping the light switch, only two turn on. The third turns on eventually. We are studying this arcane phenomenon over at CommunityData:Light events

Game IDs[edit]

  • CommunityData:GameIDs — A directory containing the game IDs for CDSC members to connect with each other across various gaming platforms.