|
| 1 | +--- |
| 2 | +layout: applicant |
| 3 | +# title: Information for Applicants |
| 4 | +description: OceanHackWeek (OHW) 2023 |
| 5 | +permalink: applicant-info.html |
| 6 | +--- |
| 7 | + |
| 8 | +# Information for OHW23 Applicants |
| 9 | + |
| 10 | +OceanHackWeek 2023 is a hands-on, interactive hybrid in-person and virtual workshop focused on data science in oceanography and fisheries that will be held on **August 7-11, 2023**. Join us for five days of tutorials, data exploration, software development and community networking! |
| 11 | + |
| 12 | +```{admonition} Applications will open around May 8, 2023 |
| 13 | +:class: important |
| 14 | +
|
| 15 | +Please come back in early May for updates. **We plan to open applications |
| 16 | +starting around May 8, 2023.** |
| 17 | +``` |
| 18 | + |
| 19 | +The **in-person** event will take place at the [University of Washington](http://www.washington.edu), in Seattle, Washington (US PDT, UTC-7), as an all-day workshop (approximately 9am - 5pm). We expect to accommodate approximately 20-25 participants. |
| 20 | + |
| 21 | +For the **virtual event**, formal daily activities will take place over a period of up to 3 hours per day. These activities include recorded tutorials with interactive discussions and project check-in with the entire group, but exclude actual project time. While plans are still tentative, we expect to hold these sessions in at least two time zones, likely USA PDT (UTC-7) and Australian EST (UTC+10). |
| 22 | + |
| 23 | +Please see the FAQs below for answers to common questions. |
| 24 | +For additional questions, please post in our [discussions on Github](https://github.com/orgs/oceanhackweek/discussions/categories/q-a) or email |
| 25 | +<a href="mailto:info@oceanhackweek.org" target="_blank">info@oceanhackweek.org</a>. |
| 26 | + |
| 27 | +--- |
| 28 | + |
| 29 | +## FAQs |
| 30 | + |
| 31 | +### Q: I am an undergrad / first year grad / faculty / etc. Is this program right for me? |
| 32 | + |
| 33 | +We welcome participants from all career stages and encourage applications from graduate students, |
| 34 | +postdocs and early career researchers. Advanced undergrad students with background in oceanography |
| 35 | +and data science are also welcome. |
| 36 | + |
| 37 | +Before applying consider what you can bring to the event: |
| 38 | +by pitching a project, |
| 39 | +by your knowledge of data sets, |
| 40 | +by your programming/computational skills, |
| 41 | +by your project management skills. |
| 42 | + |
| 43 | +We want you to grow/learn during the event! |
| 44 | +If in doubt, |
| 45 | +simply apply and explain your motivation for participation. |
| 46 | + |
| 47 | +We expect all participants to be engaged in the team projects and focus during the week. |
| 48 | + |
| 49 | +### Q: I am proficient in Matlab / other languages but have not used Python or R. Python or R has been on my list to learn. How can I make my application be stronger? |
| 50 | + |
| 51 | +We plan to accept participants with diverse skill levels and backgrounds in programming. |
| 52 | + |
| 53 | +However, to best benefit from and contribute to the program, participants are expected to have some experience with Python and/or R programming. |
| 54 | + |
| 55 | +Applicants with an extensive programming background in other languages (e.g. Matlab) are welcome to apply, |
| 56 | +if they are willing to get up-to-date on the expected basic skills before the program. |
| 57 | + |
| 58 | +Participants should familiarize themselves with the materials included in [Python novice gapminder](https://swcarpentry.github.io/python-novice-gapminder/) and [Python novice inflammation](https://swcarpentry.github.io/python-novice-inflammation/) for a Python focus, or [R novice gapminder](http://swcarpentry.github.io/r-novice-gapminder/) for an R focus. These are a good reflection of the level we expect participants to be at coming into the workshop. |
| 59 | + |
| 60 | +### Q: I don't know the first thing about version revision/control systems. Can I still apply? |
| 61 | + |
| 62 | +During the hackweek we will use Git and GitHub but you are not expected to be an expert on it. In previous years we have offered refresher in the week prior to the actual OHW event. The organizing committee is deciding whether we can offer this in OHW22. You are welcome to check back here for this info, but we want to emphasize that nothing is better than trying it yourself first -- we recommend the [Software Carpentry lessons](https://swcarpentry.github.io/git-novice/) for learning git basic. |
| 63 | + |
| 64 | +Note that we will require you to create a [GitHub account](https://github.com/) before completing the application. |
| 65 | + |
| 66 | +### Q: I do not have any programming experience. Is the program a good opportunity to get started? |
| 67 | + |
| 68 | +We believe that OceanHackWeek participants will benefit the most with some prior programming experience, |
| 69 | +and might not find the hackweek the best place to learn programming. |
| 70 | + |
| 71 | +If you do not have any programming experience we encourage you to start with some local or online training. |
| 72 | +Check if your institution runs a [Software Carpentry workshop](https://software-carpentry.org/workshops/). |
| 73 | + |
| 74 | +Once you have gone through some training you will have a better understanding of whether OceanHackWeek is right for you. |
| 75 | +We expect that you have basic operational knowledge of Python or R in advance of the program. |
| 76 | + |
| 77 | +### Q: Do I have to be a stellar Python or R programmer to be accepted? |
| 78 | + |
| 79 | +No. We aim to bring in motivated participants with a diverse range of programming skill levels. |
| 80 | + |
| 81 | +### Q: I already know a lot of what you plan to cover, should I apply / will I be bored? |
| 82 | + |
| 83 | +OceanHackWeek is not only a place to learn new skills but also a place to share expertise and build a community together. |
| 84 | +If you are already an expert but are interested in sharing and helping others, |
| 85 | +we welcome you to pitch project ideas, |
| 86 | +contribute to hacking, |
| 87 | +and assist other participants during the tutorials by being a teaching assistant! |
| 88 | + |
| 89 | +*Please mention this in the application. Send us an email if you have any questions!* |
| 90 | + |
| 91 | +### Q: I have strong computational skills but have not worked in oceanography? |
| 92 | + |
| 93 | +To ensure that participants will be interested in the oceanography problems they are solving and can give back to the field later on, |
| 94 | +we require that participants have had at least some familiarity or prior experience with oceanography data. |
| 95 | + |
| 96 | +### Q: I work in an ocean engineering / robotics / consulting company. Can I apply? |
| 97 | + |
| 98 | +<!-- We expect participants from the private sector to pay for their own expenses. --> |
| 99 | +Yes, we welcome applications from the private sector. |
| 100 | +Make sure to explain your motivation for participation in the application form! |
| 101 | +We may hold a career panel discussion, |
| 102 | +so please mention if you are interested in participating. |
| 103 | + |
| 104 | +### Q: I work in a non-US institution / organization / company. Can I apply? |
| 105 | + |
| 106 | +Yes, we welcome applications from abroad for both the in-person and virtual events. |
| 107 | + |
| 108 | +### Q: I was a participant in previous OceanHackWeek. Can I apply again? |
| 109 | + |
| 110 | +Yes, we welcome applications from previous participants, |
| 111 | +but priority will be given to new applicants. |
| 112 | +If you are interested in assisting as a project or tutorial helper during the hackweek, |
| 113 | +please mention that in the application. |
| 114 | + |
| 115 | +### Q: Am I supposed to participate in all tutorials and presentations? |
| 116 | + |
| 117 | +Yes. While we understand that not all topics may be 100% relevant to you we want to maximize engagement. Note that we post the lessons and videos online later, so if you are interested in only a portion of the OceanHackWeek consider that an option rather than taking someone's spot. |
| 118 | + |
| 119 | +### Q: My application was not accepted, what now? |
| 120 | + |
| 121 | +Sadly resources are limited and we cannot accommodate all the applicants we would like. |
| 122 | + |
| 123 | +It is important to note that a rejected application does not mean a bad one! The reasons are: |
| 124 | + |
| 125 | +- The organizer tries to accommodate a good balance from novices to experts. That means a candidate may be rejected one year and accepted in another due to the different pool of applicants. Rule of thumb? Always apply again next year if possible! Also, if you believe you can contribute to the OHW as a helper instead of a student, please get in touch! We are always in need of helpers. |
| 126 | +- Another important factor that goes into the selection of candidates is the motivation paragraph in your application. Boilerplate answers or short answers like: "I want to participate" or "It is important to me" may get lower ranking than those who read the past year materials and wrote a paragraph on how the OHW can really make a difference to them. In short: be informed, be honest, be you! |
| 127 | +- Also, please refer to the FAQ question: "I am proficient in Matlab / other languages but have not used Python or R. It has been on my list to learn. How can I make my application be stronger?" |
0 commit comments