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
Collaborative projects are a key component of OceanHackWeek, in which you get to interact with others closely and apply new skills to make something exciting happen: it can be creating tools to streamline access of a particular data source, visualizing some high density data interactively, testing existing models with new data sources, or anything else you may want to do at the intersection of oceanography and data science.
3
+
## How will the projects be conducted?
4
4
5
-
## What is a Hack?
5
+
We have put together a [few questions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning) that can help you propose a project in [GitHub discussions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning).
6
6
7
-
A "hack" is a small project that aims to solve a specific problem using computational tools.
7
+
On Monday August 15th we will have a brief “project setup” session for an overview of all projects already proposed up to that point, and give another opportunity to pitch new ideas that may be formed throughout the day. Project proposals must be submitted by the end of this day (Day 1). Each satellite may have its own, specific deadline time, so please connect with your satellite or the global event for details.
8
8
9
-
Examples of hacks include:
9
+
## Project overview
10
10
11
-
* Build a working demo of a new or modified algorithm
12
-
* Outline of a larger project, with some key features scoped
13
-
* Visualization of an old dataset in a new manner
14
-
* Modify an algorithm and apply it to a new dataset
15
-
* Combine two pre-existing pieces of code to perform some new function
16
-
* Create a tool to apply to work with existing code, datasets
17
-
* Transform code from one language to another to use with other tools
18
-
* Update old code to run faster, on new machines, and/or more efficiently
19
-
* Extend an existing project with an additional feature
20
-
* Simplify code to be more maintainable, aka "paying technical debt"
21
-
22
-
23
-
24
-
## Why hack at OceanHackWeek?
25
-
26
-
Increasingly, research and software development are conducted by groups of people with diverse skills and backgrounds. We believe this collaborative work leads to more innovative solutions to complex problems. At OceanHackWeek, our goal is to explore with you some of the skills needed to navigate technical and social challenges of working in these kinds of collaborative settings. We believe the best way to do so is to provide opportunities for you to gain hands-on experience in working together with others on a well-defined problem related to ocean sciences.
Collaborative projects are a key component of OceanHackWeek, in which you get to interact with others closely and apply new skills to make something exciting happen: it can be creating tools to streamline access of a particular data source, visualizing some high density data interactively, testing existing models with new data sources, or anything else you may want to do at the intersection of oceanography and data science.
3
+
## How will the projects be conducted?
4
4
5
-
## What is a Hack?
5
+
We have put together a [few questions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning) that can help you propose a project in [GitHub discussions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning).
6
6
7
-
A "hack" is a small project that aims to solve a specific problem using computational tools.
7
+
On Monday August 15th we will have a brief “project setup” session for an overview of all projects already proposed up to that point, and give another opportunity to pitch new ideas that may be formed throughout the day. Project proposals must be submitted by the end of this day (Day 1). Each satellite may have its own, specific deadline time, so please connect with your satellite or the global event for details.
8
8
9
-
Examples of hacks include:
9
+
## Project overview
10
10
11
-
* Build a working demo of a new or modified algorithm
12
-
* Outline of a larger project, with some key features scoped
13
-
* Visualization of an old dataset in a new manner
14
-
* Modify an algorithm and apply it to a new dataset
15
-
* Combine two pre-existing pieces of code to perform some new function
16
-
* Create a tool to apply to work with existing code, datasets
17
-
* Transform code from one language to another to use with other tools
18
-
* Update old code to run faster, on new machines, and/or more efficiently
19
-
* Extend an existing project with an additional feature
20
-
* Simplify code to be more maintainable, aka "paying technical debt"
21
-
22
-
## Why hack at OceanHackWeek?
23
-
24
-
Increasingly, research and software development are conducted by groups of people with diverse skills and backgrounds. We believe this collaborative work leads to more innovative solutions to complex problems. At OceanHackWeek, our goal is to explore with you some of the skills needed to navigate technical and social challenges of working in these kinds of collaborative settings. We believe the best way to do so is to provide opportunities for you to gain hands-on experience in working together with others on a well-defined problem related to ocean sciences.
Copy file name to clipboardExpand all lines: resources/projects.md
+23-6Lines changed: 23 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,6 @@
1
-
# Hacking at OHW22
1
+
# Project Overview
2
2
3
-
## How will the projects be conducted?
4
-
5
-
We have put together a [few questions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning) that can help you propose a project in [GitHub discussions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning).
6
-
7
-
On Monday August 15th we will have a brief “project setup” session for an overview of all projects already proposed up to that point, and give another opportunity to pitch new ideas that may be formed throughout the day. Project proposals must be submitted by the end of this day (Day 1). Each satellite may have its own, specific deadline time, so please connect with your satellite or the global event for details.
3
+
Collaborative projects are a key component of OceanHackWeek, in which you get to interact with others closely and apply new skills to make something exciting happen: it can be creating tools to streamline access of a particular data source, visualizing some high density data interactively, testing existing models with new data sources, or anything else you may want to do at the intersection of oceanography and data science.
8
4
9
5
## Tips for getting started
10
6
@@ -14,6 +10,27 @@ On Monday August 15th we will have a brief “project setup” session for an ov
14
10
* When discussing, pitch your explanation to the least experienced hacker in the group, and you'll end up better understanding what you're trying to do, or need to revise your idea.
15
11
* You can mix programming languages as needed in order to get started, but do check in with your project mentors and group members to make sure your efforts are straightforward to be absorbed into the project.
16
12
13
+
## What is a Hack?
14
+
15
+
A "hack" is a small project that aims to solve a specific problem using computational tools.
16
+
17
+
Examples of hacks include:
18
+
19
+
* Build a working demo of a new or modified algorithm
20
+
* Outline of a larger project, with some key features scoped
21
+
* Visualization of an old dataset in a new manner
22
+
* Modify an algorithm and apply it to a new dataset
23
+
* Combine two pre-existing pieces of code to perform some new function
24
+
* Create a tool to apply to work with existing code, datasets
25
+
* Transform code from one language to another to use with other tools
26
+
* Update old code to run faster, on new machines, and/or more efficiently
27
+
* Extend an existing project with an additional feature
28
+
* Simplify code to be more maintainable, aka "paying technical debt"
29
+
30
+
## Why hack at OceanHackWeek?
31
+
32
+
Increasingly, research and software development are conducted by groups of people with diverse skills and backgrounds. We believe this collaborative work leads to more innovative solutions to complex problems. At OceanHackWeek, our goal is to explore with you some of the skills needed to navigate technical and social challenges of working in these kinds of collaborative settings. We believe the best way to do so is to provide opportunities for you to gain hands-on experience in working together with others on a well-defined problem related to ocean sciences.
33
+
17
34
18
35
<!-- * Start with ideas that are close to home: your research, a project for your company, something you have always been interested in. -->
19
36
<!-- * Start with one simple idea first, and when it is built add complexity afterwards. -->
0 commit comments