You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- We recommend storing all notebooks (.ipynb) or R files (as .qmd or .rmd) in the `notebooks` folder.
7
+
8
+
## How to use
9
+
10
+
- Copy this repository
11
+
- Edit `index.qmd` to change the main landing page.
12
+
- Edit or create `setup.qmd` to change the Setup instruction pages.
13
+
- Edit `_quarto.yml` to change the dropdown menu options.
14
+
- Add additional `*.md` files to the root dir to have them converted to html files (and add them to `_quarto.yml` to make them navigable).
15
+
16
+
- If using Python, use VSCode's [Quarto Extension](https://quarto.org/docs/tools/vscode.html) to render the project (recommended b/c it's easier/nice)
17
+
- If using R, type `quarto render` in the Terminal in RStudio (not the R command line, the Terminal tab!) - or use the buttons
18
+
- If you want to command line, run the below commands (after activating the correct Python environment, if needed)
19
+
20
+
## Note:
21
+
22
+
- If using Python, you will need to have Jupyter and Quarto installed to convert the notebooks and render them for the web.
23
+
- If using R, you will need rmarkdown, xml2 and X to have the notebooks generate properly and link out to the documentation, as specified in the `_quarto.yml` file.
24
+
- The building from Jupyter notebooks will NOT re-render all of the notebooks unless you use the `quarto render notebook.ipynb --execute` command
25
+
- Building from R will by default re-render all of the outputs
26
+
27
+
28
+
```
29
+
quarto render
30
+
#First time you create the file, add them to be tracked by github, e.g.
31
+
git add docs/*
32
+
git commit -am "your comments"
33
+
git push
34
+
```
35
+
36
+
You can browse the result locally by exploring the html files created (note: sometimes figures display locally but not on web and the other way around too.)
<h2class="anchored" data-anchor-id="course-pre-requisites-and-setup-requirements">Course pre-requisites and setup requirements</h2>
145
+
<p>No previous programming experience is required, but <strong>Session 1 is a pre-requisite for the other sessions</strong>. Training will be delivered online, so you will need access to a modern computer with a stable internet connection and around 5GB of storage space for data downloaded prior to the course. Participants are encouraged to setup a Python environment on their local computer (as per the <ahref="./setup.html">Setup Instructions</a> provided), but participation using other platforms/environments can be supported where necessary.</p>
<h4class="anchored" data-anchor-id="zoom-etiquette-and-how-we-interact">Zoom etiquette and how we interact</h4>
152
+
<p>Sessions will be recorded for attendees only, and it is set up to only record the host shared screen and host audio. We will try and get these uploaded to this site as soon as possible. Please interrupt whenever you want! Ideally, have your camera on and interact as much as possible. There will be someone monitoring the chat-window with any questions you would like to post there. Four hours is a long Zoom session so we have plenty of scheduled breaks combined with a mix of content to be delivered as demos, plus sections as independent exercises, but most of the course will be pretty-hands on with everyone writing their own code. We will use Zoom break-out rooms as needed with the Trainers and participants.</p>
153
+
</section>
154
+
</section>
155
+
<sectionid="code-of-conduct" class="level2">
156
+
<h2class="anchored" data-anchor-id="code-of-conduct">Code of Conduct</h2>
157
+
<p>We expect all attendees of our training to follow our code of conduct, including bullying, harassment and discrimination prevention policies.</p>
158
+
<p>In order to foster a positive and professional learning environment we encourage the following kinds of behaviours at all our events and on our platforms:</p>
159
+
<ul>
160
+
<li>Use welcoming and inclusive language</li>
161
+
<li>Be respectful of different viewpoints and experiences</li>
162
+
<li>Gracefully accept constructive criticism</li>
163
+
<li>Focus on what is best for the community</li>
164
+
<li>Show courtesy and respect towards other community members</li>
165
+
</ul>
166
+
<p>Our full CoC, with incident reporting guidelines, is available [here]https://sydney-informatics-hub.github.io/codeofconduct/).</p>
0 commit comments