All Projects → ContextLab → lab-manual

ContextLab / lab-manual

Licence: MIT license
Lab manual for the Contextual Dynamics Laboratory at Dartmouth College

Programming Languages

TeX
3793 projects

Projects that are alternatives of or similar to lab-manual

FindMyDoc
Documentations, manuels et guides d'utilisation
Stars: ✭ 36 (+125%)
Mutual labels:  manual
Clover-Crate
Clover Bootloader (with Quirks) and Clover Configurator explained. My attempt of creating a usable documentation for the popular boot manager.
Stars: ✭ 61 (+281.25%)
Mutual labels:  manual
ru102js
Source code for the RU102JS Redis for JavaScript Developers Course
Stars: ✭ 21 (+31.25%)
Mutual labels:  training-materials
pem-dataset1
Proton Exchange Membrane (PEM) Fuel Cell Dataset
Stars: ✭ 48 (+200%)
Mutual labels:  science-research
elm-from-ground-up
This lab is designed to be an adjunct to learning Elm. Go from the most basic "Hello World" through data types and more advanced features in this example.
Stars: ✭ 17 (+6.25%)
Mutual labels:  training-materials
robot hacking manual
Robot Hacking Manual (RHM). From robotics to cybersecurity. Papers, notes and writeups from a journey into robot cybersecurity.
Stars: ✭ 169 (+956.25%)
Mutual labels:  manual
Hangfire.MissionControl
A plugin for Hangfire that enables you to launch jobs manually.
Stars: ✭ 51 (+218.75%)
Mutual labels:  manual
Teaching-Data-Visualisation
Presentation and exercises for the Software Sustainability Institute Research Data Visualisation Workshop (RDVW)
Stars: ✭ 15 (-6.25%)
Mutual labels:  training-materials
k8s-school
Learn Kubernetes fundamentals / Formation Kubernetes et les micro-services
Stars: ✭ 30 (+87.5%)
Mutual labels:  training-materials
cruk-summer-school-2018
Summer school course materials collection
Stars: ✭ 24 (+50%)
Mutual labels:  training-materials
yoshimi-doc
A PDF advanced reference manual for the Yoshimi software synthesizer, generated using LaTeX. V. 2.2.0 2022-05-16.
Stars: ✭ 21 (+31.25%)
Mutual labels:  manual
factotum
general purpose curation of exposure science data
Stars: ✭ 3 (-81.25%)
Mutual labels:  science-research
python-functions-and-modules
Python3 teaching materials for functions and modules (1 day)
Stars: ✭ 13 (-18.75%)
Mutual labels:  training-materials
pyspedas
Python-based Space Physics Environment Data Analysis Software
Stars: ✭ 90 (+462.5%)
Mutual labels:  science-research
dgs19
Docker Getting Started
Stars: ✭ 22 (+37.5%)
Mutual labels:  training-materials
installation-guides
Centralized administration of dependency installation guides.
Stars: ✭ 59 (+268.75%)
Mutual labels:  manual
training-materials
No description or website provided.
Stars: ✭ 47 (+193.75%)
Mutual labels:  training-materials
Manuals-and-Tutorials
Manuals about everything I work with
Stars: ✭ 15 (-6.25%)
Mutual labels:  manual
newcomer
前端新人培训
Stars: ✭ 25 (+56.25%)
Mutual labels:  training-materials
javaparser-visited
Code samples for the book "JavaParser: Visited" https://leanpub.com/javaparservisited
Stars: ✭ 80 (+400%)
Mutual labels:  manual

Overview

This repository contains the lab manual (and associated source code) for the Contextual Dynamics Laboratory (CDL) at Dartmouth College. The lab manual describes the rights and responsibilities of all CDL members, and it introduces our general research approach and lab policies.

All new lab members are required to read (and modify!) this repository prior to joining the lab. New lab members are also required to complete a list of basic tasks (and signify that they have done so via a checklist at the end of the manual). The tasks are intended to ensure that every lab member is on the same page with respect to expectations and that every lab member has acquired a minimum viable set of skills needed to do research in the lab.

A PDF of the latest version of the lab manual may always be found here.

Why are we sharing this repository with the public?

Our lab manual is, in one sense, intended to provide information that is specific to the CDL. So it's possible it'll be useful only to CDL lab members. However, we hope that others might find some aspects of the manual useful. For example, perhaps you like the look of the LaTeX template we used. Or perhaps you like some of the contents and want to incorporate something like it into your own operating manual. Or maybe you don't like something, and you want to use our manual as a counterexample! Whatever you'd like to do with the contents, we offer this repository freely and in the spirit of openness and collaboration. By the same token, we make no claims as to the accuracy of the documentation or code herein, so we invite you to proceed at your own risk.

Contributing

The way we develop collaborative documents and code in the CDL is to have a central repository for each project (e.g. this page) that everyone on the project has read access to. This repository is public, so everyone with an Internet connection has access to the contents of this repository, and anyone can (in principle) submit a pull request to change the contents. In practice, however, any substantial (e.g. beyond simple typo and grammar corrections) changes will need to be discussed by CDL lab members in person (e.g. during our weekly lab meetings). (So: feel free to contribute whatever you'd like, but before taking the time to do so please recognize that if you are not affiliated with the CDL, or planning to become affiliated, then it's unlikely that we'd incorporate major changes into the manual without having discussed it with you first.)

In order to modify the central code repository, you need to fork this repository, add your content to your fork, and then submit a pull request to incorporate your changes (from your fork) into the central repository. This allows us to maintain a stable working version in the central repository that everyone can access and rely on, while also allowing individual contributors to maintain (unstable) working versions. If these terms (forking, pulling, pushing, etc.) are unfamiliar or confusing, you should read through these Git Tutorials before proceeding.

To set up your fork:

  1. Press the "fork" button in the upper right corner of the repository's website (link above).
  2. Clone your fork to your local machine (git clone https://github.com/<GitHub Username>/lab-manual.git).
  3. Set the central repository as an upstream remote: git remote add upstream https://github.com/ContextLab/lab-manual.git.
  4. Each time you want to make changes to your local copy, sync it with the central repository by running git pull upstream master.
  5. When you're done making changes, type git commit -a -m "<MESSAGE DESCRIBING WHAT YOU CHANGED> and then git push.
  6. Repeat steps 4 and 5 until you have something to share with the world. Note: you can push broken code to your local fork without damaging anything in the central repository, so we encourage frequent committing and pushing (even of broken code) to your local fork. This will ensure that (a) you always have a recent online backup of your work and (b) there is a clear record of what you did and the path you took to accomplish it.
  7. When you're ready to share your code with the world, go back to your fork's web page (https://github.com/<GitHub Username>/lab-manual), navigate to the "pull requests" tab (upper left), and press the "New pull request" button in the upper right. Describe what you did and submit your pull request by filling out the prompts. Then someone from the CDL will review the changes and merge them in, and everyone will have access to your changes.
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].