CSCWiki - User contributions [en]

Main Page

2016-01-15T15:02:14Z

Tbelaire: /* Miscellaneous */

This is the Wiki of the [[Computer Science Club]]. Feel free to start adding pages and information.

[[Special:AllPages]]

== Guides ==
<div style="-webkit-column-count:3; -moz-column-count:3; column-count:3;">
* [[ New Member Guide]]
* [[Budget Guide]]
* [[Club Hosting]]
* [[Web Hosting]]
* [[Exec Manual]]
* [[Imapd Guide]]
* [[MEF Guide]]
* [[Office Policies]]
* [[Office Staff]]
* [[How to IRC]]
* [[Talks Guide]]
* [[SCS Guide]]
* [[Kerberos | Password Reset ]]
* [[Disk Drive RMA Process]]
* [[ IPMI101 ]]
</div>

== News and Events ==
<div style="-webkit-column-count:3; -moz-column-count:3; column-count:3;">
* [[Meetings]]
* [[Talks]]
* [[Projects]]
* [[Industry Opportunities]]
</div>

== Machine/System Documentation ==
<div style="-webkit-column-count:3; -moz-column-count:3; column-count:3;">
* [[Authentication]]
* [[Backups]]
* [[ceo]]
* [[DNS]]
* [[Debian Repository]]
* [[Digital Cutter]]
* [[Directory Services]]
* [[Electronics]]
* [[Hardware]]
* [[Kerberos]]
* [[Machine List]]
* [[Mail]]
* [[Mailing Lists]]
* [[Mirror]]
* [[Music]]
* [[MySQL]]
* [[NetApp]]
* [[Network]]
* [[New CSC Machine]]
* [[NFS/Kerberos]]
* [[OID Assignment]]
* [[Printing]]
* [[Pulseaudio]]
* [[Robot Arm]]
* [[Scratch]]
* [[SNMP]]
* [[Serial Connections]]
* [[SSL]]
* [[Switches]]
* [[Syscom Todo]]
* [[Systems Committee]]
* [[UID/GID Assignment]]
* [[Webcams]]
* [[Webmail]]
* [[Website]]
* [[Virtualization (LXC Containers)]]
</div>

== Miscellaneous ==
<div style="-webkit-column-count:3; -moz-column-count:3; column-count:3;">
* [[Budget]]
* [[Executive]]
* [[Past Executive]]
* [[Frosh]]
* [[History]]
* [[Library]]
* [[MEF Proposals]]
* [[Term Notes]]
* [[Proposed Constitution Changes]]
</div> __NOTOC__

Proposed Constitution Changes

2016-01-15T15:01:00Z

Tbelaire: Creating the page

== Constitution Changes w.r.t Elections ==
Something about please withdrawing sooner.

Or letting people be nominated at the election iff there are no people running for that position.

New Member Guide

2015-01-20T16:34:42Z

Tbelaire: /* Machines */ Added link to machine useage policy.

Hello, and welcome to the Computer Science Club! Thanks for joining. The office staff who signed you up should have told you about this stuff, but just as a refresher, here it is again.

== Office ==

* Our office is MC 3036/3037 (we occupy both rooms) and we're across the hall (but distinct from) the Mathsoc office.

* Our club doesn't have weekly meetings or anything like that. If the door is open, we are open (even if it's 3 in the morning on Sunday). Feel free to drop in and say hi!

* The office closes when the last office staff leaves the room, and the office opens when somebody with a key comes by. If you're interested in becoming office staff, look out for the termly office staff training event or ask around the office.

* We have staplers by the door farthest from Mathsoc. Even if you're not a member, you're allowed to use them. You don't even have to ask (and in fact, we'd prefer if you didn't. Office regulars spend a good amount of time telling people that yes, they can use the staplers).

* We sell pop, chips, chocolate bars and other snacks. Prices are on the fridge door. Pay the red cup in the fridge.

== Events ==
We hold a different set of events every term, but the same types of events come up again and again. Watch out for emails about:
* Industry tech talks. In the past, we've gotten folks from various tech companies to talk about algorithms, database design decisions and other things.

* UNIX 10X tutorials. Don't know how to use the commandline? Come out and learn with us. Know how to use the commandline? Come out and help us answer questions.

* Member talks. Do you have a burning desire to talk about AVL trees? No? Well, if you want to talk about a computer sciencey topic that's close to your heart, send an email to exec at csclub.uwaterloo.ca with a talk abstract (a paragraph we can put on a poster to describe your talk) and we'll see if we can make something happen.

* Code parties. We eat food, talk and write code. Code parties happen several times a term.

== Machines ==
As a member of the club, you have access to our machines, both [[Machine_List#Servers|servers in the machine room down the hall]] and [[Machine_List#Office Terminals|desktops in our physical office]]. Keep in mind that your username is your quest userid (e.g. j7smith) and your password starts out as the one you set when you joined the club for the first time.

* As a member you must abide by the [https://csclub.uwaterloo.ca/services/machine_usage machine usage policy].

* Your files are accessible on all of our machines

* Keep in mind that the machines are shared among all of our members. Play nice. For example, <nowiki>caffeine</nowiki> is our web server. You are strongly advised not to run long, intensive jobs on it. Something like that is a better fit for <nowiki>hfcs</nowiki>, <nowiki>corn-syrup</nowiki> or even possibly <nowiki>taurine</nowiki>.

* use SSH for access to the machines in the server room.
** If you don't know how to use the commandline, you can wait for our approximately termly UNIX 101 event, google for "how to use the command line", or ask around the office.
** if you happen to be using Windows, you can use an SSH client such as PuTTY[http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html].
** If you have a Mac or you run Linux, you already have the <nowiki>ssh</nowiki> command installed. If your userid is <nowiki>j7smith</nowiki> and you want to use <nowiki>taurine</nowiki>, just open up a terminal window and type the following. You will be asked for your CSC password.

ssh j7smith@taurine.csclub.uwaterloo.ca

* Our office terminals are turned off, rebooted and otherwise reset somewhat frequently.

* If you forget your password, come by the office with your watcard and some other form of ID. Regular office staff can't reset your password for you, but if there's someone on our Systems Committee hanging around, they can do this for you.

* If you would like to change your password, log on to any of our machines and type <nowiki>kpasswd</nowiki> in a terminal. You will be prompted for your old password and be asked to type in your new password twice (just to make sure you didn't make a typo).

* We have a MySQL daemon running, but only on our web server <nowiki>caffeine</nowiki>. Check out [[MySQL|this page]] if you would like a database.

* for technical questions (including package installation requests), send an email to our systems committee, syscom at csclub.uwaterloo.ca.

== Web Hosting ==
You get web space with your CSC membership. Your website is visible at [http://csclub.uwaterloo.ca/~j7smith] (where j7smith is replaced with your own userid, of course).

* Files in the <nowiki>www</nowiki> directory inside your home directory (e.g. <nowiki>/users/j7smith/www</nowiki>) will appear on your web space.
* If you create a file called <nowiki>index.html</nowiki> and place it in <nowiki>www</nowiki>, it will appear at [http://csclub.uwaterloo.ca/~j7smith] instead of the directory listing that was there before.
* If the above information makes no sense to you, ask someone in the office for a gentler step-by-step introduction. Some day, there will be a guide like this on the wiki, but such a thing doesn't currently exist.

== IRC ==
We have an IRC (internet relay chat) channel. Come hang out with us in #csc on freenode. If you are unfamiliar with IRC, you may want to read [[How to IRC|this guide]].

== Mail ==
* see the [[Mail]] page.
* The CSC gets a lot of requests to distribute [[Industry Opportunities]] to our members. We have a special opt-in mailing list for the people that want to hear about such things.
* We have a low-volume general mailing list which we use to send out information about upcoming events.

== Library ==
There are books on the shelves lining the office. Feel free to drop by and read them.

Someone who knows more about the library checkout system than jy2wong should write something here.

Hardware

2014-11-19T03:48:32Z

Tbelaire: /* Hard Drives */

This page documents various random hardware around the office

=Graphics Cards=
==#1: ASUS ENGT440/DI/1GD5==

http://www.asus.com/ca-en/Graphics_Cards/ENGT440DI1GD5/specifications/

* nVidia GeForce GT 440
* 1GB RAM
* PCI Express 2.0 (double-size)

=Ethernet Cards=
==#1: Marvel Gigabit==

* it's gigabit
* PCI

=3.5" Floppy Drives=
==#1: Caffeine's old drive==

* IDE

=Hard Drives=
==#1 Gwem's Old Drive==
* 160 GB
* SATA

== Bit Shifter/Video ==
* 80 GB
* SCSI

== Strombola's old HD ==
* 750 GB
* SATA

== NF's Old Drive ==
* 320 GB
* SATA

== Drive 2 ==
* 250 GB
* SATA

== Drive 3 ==
* 500 GB
* SATA

== SKYNET DRIVE 4.{1,2} ==
* 36 GB
* SCSI

== Malto's Old Drive ==
* 400 GB
* SCSI

Hardware

2014-11-19T03:30:40Z

Tbelaire: /* Hard Drives */

Hardware

2014-11-19T03:20:07Z

Tbelaire:

Website

2014-10-19T22:23:49Z

Tbelaire: /* Committing changes to the website */

== Dependencies ==

You'll need to install a few dependencies to build the website; the following command will install all dependencies if you're using a Debian-based system:

sudo aptitude install python python-libxslt1 python-libxml2 python-tz git-core python-ldap

== Checking out the website ==

The website is managed in a [http://git.csclub.uwaterloo.ca/?p=www/www.git git repository].

Any member can checkout the website using git clone:
git clone /users/www/www

This creates a directory called "www" that contains the entire website and its history. If you want to make changes to the website, you'll need to ask someone on the [[Systems Committee]] to add you to the "www" group. You should also subscribe to our [http://csclub.uwaterloo.ca/mailman/listinfo/git git mailing list].

== Testing your changes ==

You should test any changes you make before pushing them out for all the world to see. The easiest way to see your changes without committing them is to create a symlink into your public "www/build" directory. For example, say your local copy of the website lives in "/users/$USER/csc/www". You could symlink "/users/$USER/csc/www/build" to "/users/$USER/www/csc". Do this by typing:

ln -s /users/$USER/csc/www/build /users/$USER/www/csc

Then you could see your copy of the website at this URL:

http://csclub.uwaterloo.ca/~USERNAME/csc/

= Committing changes to the website =

If you add a new file to the website, you can add it to git:
git add file

To delete a file type:
git rm file

And to rename or move a file type:
git mv old-file new-file

Once you're done modifying the website you can commit your changes:
git commit -a

The above command only commits the change to your local repository; you need to push the changes out to the master repository:
git push

The above command will also automatically rebuild the website and send out an email to the git mailing list with the details of your change, as long as you are on caffeine when you push.

= Building the website =

Once you've checked out the website, you can build the website by running:
make

This will build the website into the build directory. When git-pushing, the website will be built into /srv/www-csc.

You can remove the generated files by running:
make clean

= Modifying the website =

== XML ==

The website's data is contained in a series of XML files. A series of XSLT files are used to transform the XML data into HTML files. If you want to add new information to the website you'll want to modify the XML files.

Some notable XML files:
* events.xml - past and upcoming events
* news.xml - past and upcoming items
* media/index.xml - media items (e.g. talks)

XML should be fairly easy to work with. Some important things to remember:
* All opening tags must be closed.
* All tags should be in lowercase.
* Tag and attribute names are case-sensitive.

If you want more information on XML, the following are good resources:
* The XML specification: http://www.w3.org/TR/2006/REC-xml-20060816/
* XML tutorials and general reference: http://www.w3schools.com/xml/default.asp

== XSLT ==

If you want to change the HTML layout you'll want to modify the XSLT files. Almost all XSLT files are located in the 'xsl' directory. We are using XSLT 1.0 and a python front-end (xmlproc.py) to libxslt.

== CSS ==

If you want to change the style of the HTML you'll want to modify default.css. We primarily target Firefox 2.0 but every effort should be made to use CSS that renders correctly in Internet Explorer 6.0 and other browsers. You can test various Internet Explorer versions from Linux by installing [http://www.tatanka.com.br/ ies4linux]. There's also [http://browsershots.org/ browsershots.org], which will take screenshots of a page in various browsers.

== Data files ==

Data files, such as PDF's, should be copied to /srv/www-csc-misc. These files are accessible via http://csclub.uwaterloo.ca/misc/.

= Website vs Wiki =

In order to keep things organized, the following guidelines should be followed.

Website:
* Information not likely to change frequently (e.g. services, general information)
* Information that should only be modifiable by the exec
* Official documents (e.g. constitution, policies)
* Current and past executive
* User and club lists
* News, events, and media items
* Anything we want non-members to see when they first encounter our site

Wiki:
* Information that changes frequently
* Information that any club member should be able to add to or modify
* Exec and office staff guides/manuals
* System and hardware documentation
* Past funding opportunities and advice (assuming this can be publicly posted)
* Contacts (e.g. CSCF, SCS) (assuming this can be publicly posted)

Also note that we can protect various pages if they shouldn't be edited in general.

= Conventions =

== Email Addresses ==

'''Note''': this convention is not currently used and is not recommended for now.

Email addresses should be wrapped in <email> tags. For example, if you want to include the email example@csclub.uwaterloo.ca you should include the following xml snippet:
<email>example@csclub.uwaterloo.ca</email>
Leading and trailing whitespace will be stripped so it is safe to do this:
<email>
example@csclub.uwaterloo.ca
</email>
Currently this just generates an standard mailto link. In order to prevent spammers from harvesting address, I want to generate an image that contains the address.

My current plan is to generate the email images while running make. This would be accomplished by creating a csc:email function that generates and saves the image to http://csclub.uwaterloo.ca/images/. The image name would be generated from HMAC(email, key), where key is some secret key/phrase.

= Feature Requests and Ideas =

* Possibly move club list onto wiki.
* Convert cellspacing and cellpadding to CSS equivalents.
* Make RSS and ICS feeds more prominent.
* Replace or compliment /events with a web-based calendar?
* Replace all email addresses with generated graphics or javascript obfuscation?
* Replace <br>'s with <p>'s wherever it makes sense.
* Replace <strong>, <b>, <i>, etc... tags with CSS.
* Highlight (e.g. make left bar green) current page in directory header

[[Category:Software]]
[[Category:Guides]]
[[Category:Policy]]
[[Category:Projects]]

Main Page

2013-09-20T17:51:32Z

Tbelaire: /* Machine/System Documentation */ music page added

This is the Wiki of the [[Computer Science Club]]. Feel free to start adding pages and information.

[[Special:AllPages]]

== Guides ==
<div style="-webkit-column-count:3; -moz-column-count:3; column-count:3;">
* [[Budget Guide]]
* [[Club Hosting]]
* [[Member Hosting]]
* [[Exec Manual]]
* [[Imapd Guide]]
* [[MEF Guide]]
* [[Office Staff]]
* [[Talks Guide]]
* [[SCS Guide]]
* [[Kerberos | Password Reset ]]
</div>

== News and Events ==
<div style="-webkit-column-count:3; -moz-column-count:3; column-count:3;">
* [[Meetings]]
* [[Talks]]
* [[Projects]]
* [[Industry Opportunities]]
</div>

== Machine/System Documentation ==
<div style="-webkit-column-count:3; -moz-column-count:3; column-count:3;">
* [[Authentication]]
* [[Backups]]
* [[ceo]]
* [[DNS]]
* [[Debian Repository]]
* [[Digital Cutter]]
* [[Directory Services]]
* [[Electronics]]
* [[Kerberos]]
* [[Machine List]]
* [[Mail]]
* [[Mailing Lists]]
* [[Mirror]]
* [[Music]]
* [[MySQL]]
* [[NetApp]]
* [[New CSC Machine]]
* [[NFS/Kerberos]]
* [[OID Assignment]]
* [[Printing]]
* [[Robot Arm]]
* [[Scratch]]
* [[SNMP]]
* [[Serial Connections]]
* [[SSL]]
* [[Switches]]
* [[Sony Camera]]
* [[Systems Committee]]
* [[TS-7800]]
* [[UID/GID Assignment]]
* [[User-data]]
* [[Webcams]]
* [[Webmail]]
* [[Website]]
* [[Virtualization]]
</div>

== Miscellaneous ==
<div style="-webkit-column-count:3; -moz-column-count:3; column-count:3;">
* [[Budget]]
* [[Executive]]
* [[Past Executive]]
* [[Frosh]]
* [[History]]
* [[Library]]
* [[MEF Proposals]]
* [[Office Policies]]
* [[Projector]]
* [[Term Notes]]
</div> __NOTOC__

Robot Arm

2013-09-20T17:50:42Z

Tbelaire: /* Status */

= Software =

The robot arm was purchased with the intent of being used to create a mechanical turk.
The code going towards this goal lives in ~ssalbiz/arm, use "git clone ~ssalbiz/arm" to make a copy.

= Hardware =
The arm is a [http://www.lynxmotion.com/c-130-al5d.aspx Lynxmotion AL5D].

= Operation =
Currently the arm is controlled by interfacing directly with /dev/ttySx or /dev/ttyUSBx . The syntax for controlling this is by sending the following string to the board:
<pre>
#<servo id> P<position> S<speed> T<time>
</pre>

You can control multiple servos with one command
<pre>
#<servo id> P<position> S<speed> #<servo id> P<position> S<speed> T<time>
</pre>

S and T are optional parameters

Key:
* <servo id> - id of the servo being controlled (includes jaw)
* <position> - servo rotation position, generally between (500,2500)
* <speed> - speed of rotation; 100 means 10s to rorate 90°; leaving this off generates fast movement, 400 seems like a "safe" value?
* <time> - time it takes to complete the motion in ms; specified once for the entire motion

if both speed(s) and time are specified, time is a "minimum" and speed is a "maximum", i.e. the motion will take at minimum T milliseconds, but servoA will move no faster than speed SA

== Servo key and degree of motion ==
* 0 - Base
* 1 - Shoulder
* 2 - Elbow
* 3 - Wrist
* 4 - Grip
* 5 - Wrist Rotate

= Purpose =
The current purpose of the robot arm is to make an entity that can play chess against a human.

==Status==
Not being worked on. Need to complete the following:

* Complete physical modifications to robot arm to allow it to reach all pieces on the board
* Calibrate arm base mount against chess board squares
* Make the robot arm code talk to a chess program
* Make the chess program talk to the chess vision code
* Make the arm not have terrible things happen when the servos heat up

= External Links =
* a manual [http://www.lynxmotion.com/images/data/rios106h.pdf]
* j3parker's [http://csclub.uwaterloo.ca/~j3parker/arm.png 3D model of the arm]

Music

2013-09-20T17:48:54Z

Tbelaire:

Music is run off nullsleep, since that's the computer with the speakers attached.

Music is located in /music.

The command to get music running is ncmpcpp.

To view the keybindings of ncmpcpp, press 1 while it's running. The number keys switch between tabs in it. 1 is help, 2 views the playlist, 3 is browsing, etc.

Music

2013-09-20T17:48:42Z

Tbelaire: Created page with "Music is run off nullsleep, since that's the computer with the speakers attached. Music is located in /music. THe command to get music running is ncmpcpp. To view the keybindi…"

Music is run off nullsleep, since that's the computer with the speakers attached.

Music is located in /music.

THe command to get music running is ncmpcpp.

To view the keybindings of ncmpcpp, press 1 while it's running. The number keys switch between tabs in it. 1 is help, 2 views the playlist, 3 is browsing, etc.