Project

General

Profile

Project Team Meetings » History » Version 29

Corinna Gries, 07/18/2014 12:40 PM

1 1 Corinna Gries
h1. Project Team Meetings
2
3 27 Corinna Gries
h2. 7/18/2014
4
5
Matt: good idea to combine codefest with ABI workshop because there are other people working on similar technical issues. We may need a little time for specific community dynamics discussion.
6
7 28 Corinna Gries
Work on scientific manuscripts during codefest and add Thursday afternoon and Friday morning. Travel on Friday afternoon and Saturday morning.
8 27 Corinna Gries
9 28 Corinna Gries
Codefest will offer great exchange on scientific R programming. R open Sci will be there. Analysis and infrastructure.
10 1 Corinna Gries
11 29 Corinna Gries
Corinna send e-mail to commDyn group. Get quick notice of who wants to come. Ask what people still need to do for their manuscripts. Add Peter, Chris and Lauren to logistics e-mails. Put together an agenda: Thursday: present and do some usability work on the new collaborative tool and get feedback. Friday: work on manuscript, data analysis, 
12 28 Corinna Gries
13
Codefest Tuesday - Thursday noon.
14
15
Matt report: collaboration between three projects (DataONE, commDyn, ...) built in capabilities to share code during development. Library of community dynamics metrics. Lauren has started to develop a prototype. Have a prototype to show during codefest. Get input on how to extend for work in commDyn.
16
 
17 27 Corinna Gries
h2. 6/16/2014
18 20 Corinna Gries
19 22 Corinna Gries
h2. 5/9/2014
20
21 23 Corinna Gries
Syd, Matt, Scott, Corinna
22
23
Syd and Scott at ASU working with Julie: 
24
late breaking poster for ESA
25
8 Konza datasets
26
7 Sev datasets
27
richness, timelag, 
28
comparing taxa at same site
29
grass community is changing, not so much creosote; composition is changing, not so much richness
30
not many community datasets at LTER sites
31
VCR small mammals are not usable
32
not as extensive a comparison as originally hoped
33
Konza data show tipping point with shrub encroachment
34
35
characteristics of datasets:
36
multiple communities at one site, producers, consumers
37 22 Corinna Gries
38 24 Corinna Gries
Matt: Lauren Walker has started working on project. Ben and Peter will join later.
39
work across several projects that are trying to do the same
40
define a model that allows people to upload R scripts, datasets and analytical output. All linked to understand what was done.
41
Share everything as the analysis is going on, through the DataONE repository.
42
How should that be related/linked to github. Git is good for actively working, but not archiving. I.e., the archival copy within DataONE needs a link to the living code in git. Version in DataONE will stay archived with DOI, while the version in git may go away.
43
Drawing up some preliminary design ideas.
44 25 Corinna Gries
Syd should document what worked and what didn't in git.
45
46
software un-coference in September, venue locked in. Science/software work-a-thons.
47
48
Scott: Follow up with other working group (Lauren, Lizzie, Elsa et al.) 
49 24 Corinna Gries
50 22 Corinna Gries
51
h2. 4/4/2014
52 20 Corinna Gries
53
Scott, Matt, Corinna, Syd
54
55
Scott and Syd going to ASU end of April to work with Julie
56
57
Syd: report from last group call
58
larger group participated, decided that each working group should meet separately
59
group 1: Syd, Julie, Eric
60
Eric posted diversity metrics on github
61
challenge: choose the metrics
62
datasets: how will they be chosen
63 21 Corinna Gries
plant community dataset, annually sampled, plus insect community dataset, or small mammal community - multiple datasets from the same sites, annually sampled. Limitation is co-location of datasets. SEV, KNZ, JRN, maybe VCR
64
65
Matt: discussion with Ben and Lauren where to go with the repository. Initially a web interface to drop things and search and find. Next step is to access them within the working environment (R, Kepler).
66 18 Corinna Gries
67 16 Corinna Gries
h2. 3/19/2014
68
69
Scott, Matt, Corinna
70
71
Annual report: Scott has submitted
72
reconvene the workshop group to continue work on papers. Possibly with ISEES meeting: possibly September 2 - 4 followed by commdyn workshop: September 5 - 7 
73
74
Action items:
75
Matt to write up and circulate specifications for Ben to work on starting in May, 2014, based on recommendations from the workshop
76
collaboration tool to share workflows should work across platforms, not only Kepler
77
78
Corinna send thank you e-mail to workshop participants. 
79
Corinna move everything from redmine to github.
80
81 17 Corinna Gries
set up times for paper working groups to meet online. Start with the one Syd already initiated, then follow with other groups.
82
set up structure in github for the four groups.
83 15 Corinna Gries
84
h2. 2/27/2014
85
86
Scott, Matt, Syd, Corinna
87
88
Possibly have a follow up workshop in September together with ISEES meeting in Santa Barbara
89
Important to keep the good momentum going for the different working groups that have started.
90
91
Syd:
92
write e-mail to remind everyone of what we agreed to do.
93
94
h2. 2/13/2014
95
96
Scott, Matt, Corinna
97
98
Discussion of the workshop outcomes.
99 13 Corinna Gries
100
h2. 11/22/2013
101
102
Scott, Syd, Corinna
103
104
Workshop preparation: What to ask people to do in preparation for attending:
105
bring a dataset - multi species and multi sampling
106
how do you want to analyze your data
107
bring R code if available
108
What questions can be asked across several datasets of different taxonomic groups and habitats
109
110
Syd:
111
list of indices that we already have identified on this website
112
R code to handle the four example datasets
113
114
Corinna:
115
Kepler workflow to access the data via EML and pass on a R dataframe
116 14 Corinna Gries
Or R code accessing datasets in DataONE
117 13 Corinna Gries
118 12 Corinna Gries
119 8 Corinna Gries
h2. 10/11/2013
120
121
Matt, Scott, Corinna
122
123
plans for the workshop:
124
125
treat part of the workshop as hackathon, combine ecologists, R specialist, and workflow specialist in groups to actually implement an analysis.
126
127 9 Corinna Gries
Data sets: people should bring their data sets.
128
129
Syd to find appropriate data sets and give feedback on how to find them. 
130
131 10 Corinna Gries
goals of workshop: 
132
133
list of analyses, list of data sets, what is need to move from raw data to analyses and visualization.
134
135 11 Corinna Gries
https://docs.google.com/spreadsheet/ccc?key=0AgZm2NvfJ87OdFlBdWRQMkNwWnpCT3FkcEJDb2gtZ0E&usp=drive_web#gid=0
136 9 Corinna Gries
137 8 Corinna Gries
h2. 9/17/2013
138
139
Matt, Scott, Syd, Sam, Corinna
140
141
Started list of potential invitees for the workshop in google docs.
142 7 Corinna Gries
143
144 6 Corinna Gries
h2. 8/27/2013
145
146
Matt, Scott, Syd, Sam, Corinna
147
148
reports:
149
Matt is still trying to hire a programmer
150
Corinna announced project at LTER IM meeting and got several responses regarding datasets available. Specifically GCE, LUQ, and VCR
151
Syd has started R programming for some community change indeces
152
153
workshop planning:
154
start document for goals, participants and agenda
155
156
action items:
157
Corinna start document for workshop planning
158
Syd and Sam communicate about R routines for data manipulation
159
Syd and Scot get names of datasets from SEV and KNZ to Corinna
160
Corinna and Sam work with Kristin and Adam to get EML for those datasets
161
162
163 3 Corinna Gries
h2. 6/13/2013
164 1 Corinna Gries
165 6 Corinna Gries
Matt, Scott, Syd, Sam, Corinna
166 5 Corinna Gries
167 2 Corinna Gries
Agenda
168 4 Corinna Gries
Action items from last meeting
169 2 Corinna Gries
Scott - report from the Science Council meeting re. datasets
170
Matt - intro to project management system and start of tracking Community Change indices
171
Corinna - start list of participants for first workshop at NCEAS
172 4 Corinna Gries
173
Notes
174 5 Corinna Gries
Scott announced the project at the LTER Science Council meeting
175
Important to remember is that we have support to clean data and document them in EML. We are not expecting the information managers at other sites to add this to their tasks. We can take datasets that have at least 10 data points at even time intervals.
176
177
Action items:
178
Matt: add functionality to this project management system to track datasets from a general idea of its existence to actually being in the NIS/DataONE
179
Corinna: start adding Community Change indices from the proposal to redmine. 
180 2 Corinna Gries
181 1 Corinna Gries
h2. 5/2/2013
182
183
Matt, Syd, Corinna
184
185
Today we filled Syd in a bit on her role in the project and talked some more about the first workshop in spring 2014.
186
187
Action items:
188
Corinna - doodle for the community workshop in February/March and set date
189
Syd - download and explore Kepler
190
Scott and Syd - start list of community change metrics that we want to encode
191
Matt - hire programmer
192
193
Next project team meeting: 6/13/2013 1 pm MDT