-
Notifications
You must be signed in to change notification settings - Fork 43
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #8 from yu71ng/virtual_campaign
Fill in some information into virtual_campaign.md
- Loading branch information
Showing
1 changed file
with
78 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,78 @@ | ||
# Virtual Campaign | ||
# Virtual Campaign (VC) | ||
|
||
**📅 When?** Thursday and Friday in January/February 2024 for four weeks | ||
|
||
Starting from 11th January we meet every Thursday and Friday (🕰 1 -- 5 pm UTC | 2 -- 6 pm CET | 8 am -- 12 pm EDT) | ||
|
||
--- | ||
|
||
## The overarching aim of the VC | ||
|
||
I.) People shall get to know each other and voice their research interest. We envision first definitions of **basic flight patterns** that everyone generally agrees with and list special patterns that we might need to cover during the campaign (e.g. radar calibration wiggle). Also, we should get a feeling for the boundary conditions for the campaign: what happens in case of a tropical cyclone or the like? | ||
|
||
II.) Start **collecting tools/scripts/datasets** that are useful during the campaign for flight planning or first data evaluation. | ||
|
||
--- | ||
|
||
## Schedule | ||
|
||
**Group work:** We envision groups of about 5 people to work in parallel to plan the flights and ship track. We suggest to divide the group work into two phases: | ||
- (Week 1 and 2) Come up with the ship track and a generic flight pattern based on the observed variability of the atmospheric conditions. | ||
- (Week 3 and 4) Handle a specific real-day case study from the past and come up with a realistic flight plan. | ||
|
||
**All times are CET.** | ||
|
||
--- | ||
|
||
### Week 1 & 2 | ||
|
||
| <div style="width:100px"></div> | <div style="width:100px">Time [CET] </div> | Topics | | ||
| -------- | -------- | --------------- | | ||
| Jan, 11th | 2 pm | Welcome and Introduction | | ||
| | 2:10 pm | Overview talks + most recent flight/ship track ideas of (sub-)programs <br> ( [ORCESTRA](https://orcestra-campaign.org/preparation.html) / [MAESTRO](https://orcestra-campaign.org/maestro.html) / [PERCUSION](https://orcestra-campaign.org/percusion.html) / [BOW-TIE](https://orcestra-campaign.org/bowtie.html) / [PICCOLO](https://orcestra-campaign.org/piccolo.html) / [SCORE](https://orcestra-campaign.org/score.html) ) | | ||
| | 4 pm | **break** | | ||
| | 4:20 pm | Overview of boundary conditions for flight planning | | ||
| | 5 pm | Tool(s) introduction | | ||
| | 5:10 pm | Topic collection, Group distribution | | ||
| | 6 pm | end | | ||
|||| | ||
| Jan, 12th | 2 -- 6 pm | Group work (Breakout sessions) | | ||
|||| | ||
| Jan, 18th | 2 -- 3 pm | General meeting | | ||
| | 3 -- 6 pm | Group work (Breakout sessions) | | ||
|||| | ||
| Jan, 19th | 2 -- 4 pm | Prepare summary within groups | | ||
| | 4 -- 6 pm | Group presentations / summary discussion | | ||
|
||
**Envisioned outcome of week 1 and 2** | ||
* METEOR ship track | ||
* generic HALO flight pattern | ||
* generic ATR flight pattern (+coordination with HALO flights) | ||
|
||
### Week 3 & 4 | ||
|
||
| <div style="width:100px"></div> | <div style="width:100px">Time [CET] </div> | Topics | | ||
| -------- | -------- | --------------- | | ||
| Jan, 25th | 2 -- 3 pm | General meeting: Planning the second half of the virtual campaign | | ||
| | 3 -- 5 pm | Discussing an ORCESTRA data concept| | ||
| | 5 -- 6 pm | Beginning of group work: Planning operations for specific dates | | ||
|||| | ||
| Jan, 26th | 2 -- 6 pm | Group work: planning operations for specific dates | | ||
|||| | ||
| Feb, 1st | 2 -- 6 pm | Group work: planning operations for specific dates | | ||
|||| | ||
| Feb, 2nd | 2 -- 4 pm | Group work: planning operations for specific dates | | ||
| | 4 -- 6 pm | Summary, conclusion, planning next steps | | ||
|
||
**Envisioned outcome of week 3 and 4** | ||
* Have some realistic flight plans | ||
* Ideas for special patterns | ||
* List of tools/scripts/datasets to prepare before the campaign | ||
* data policy agreement, a plan for a data concept | ||
|
||
--- | ||
|
||
### 📑📊 Materials: | ||
|
||
- Presentations will be uploaded here [*link still to come*]. | ||
- *tbc* |